PPCGeeks

PPCGeeks (http://forum.ppcgeeks.com/index.php)
-   Android On TP2 Development (http://forum.ppcgeeks.com/forumdisplay.php?f=319)
-   -   [TESTING] - NAND OMGB (1.2.3) (http://forum.ppcgeeks.com/showthread.php?t=147260)

[ACL] 01-11-2012 02:59 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by vzihome (Post 2163973)
I was having a no sound issue until I replaced the csv file inside your acoustic test with the one I had been using on windows (the increased volume cab) and it now feels like I have the sound I had while I was on winmo(loud in call volume and loud speakerphone) will try "new" 12-24 this afternoon thanks again ACL

Sent from my Touch Pro 2 using Tapatalk

wait the 12-24 isnt new. Just the same old builds but into 1 so you wont gain anything from it.

If you are having no sound issues with your csv,s then thats good. because to be honest i dont recall which csvs i even packaged up. But it fixed gsm sound so i left it alone. The next release i'll reploy csvs for all variants. This way we can localize issues. But Haret builds seem to have dead sound after some usage, im trying to make sure i dont continue patching our code if its already working fine.

mayestik1 01-11-2012 03:06 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Thanks for uploading this version!
Quote:

Originally Posted by [ACL] (Post 2163974)
wait the 12-24 isnt new. Just the same old builds but into 1 so you wont gain anything from it.

Hmm.. this is the first build, where I have GSM network so now I'm happy and I'll have it until the new ver will be here :)
good works, ACL, thanks again

vzihome 01-11-2012 03:09 PM

Quote:

Originally Posted by [ACL] (Post 2163974)
wait the 12-24 isnt new. Just the same old builds but into 1 so you wont gain anything from it.

If you are having no sound issues with your csv,s then thats good. because to be honest i dont recall which csvs i even packaged up. But it fixed gsm sound so i left it alone. The next release i'll reploy csvs for all variants. This way we can localize issues. But Haret builds seem to have dead sound after some usage, im trying to make sure i dont continue patching our code if its already working fine.

10-4

Sent from my Touch Pro 2 using Tapatalk

mbellot 01-11-2012 04:49 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by [ACL] (Post 2163969)
also anyone having "no sound" or dying sound issue? i'm trying to leave code intact if it works. No need to fix something thats working flawlessly. I do know there was a volume issue, but that i patched up and will be released with the new bundle. \\:D/

I have had problems with ringtone audio, but had chalked it up to all the other mucking around I had been doing lately.

Notification tones (SMS, etc) work fine, which is (IMHO) truly odd since I would have thought they would route the same.

I have had a couple cases of no in-call audio, but it was in a bad reception area so I figured it was just poor signal.

EDIT: Just to be clear, incoming call ringtone is DOA even immediately after a reboot. RHOD400 FWIW.

The weirdest problem however (and not readily repeatable) is occasionally the LED will not indicate wake/sleep after a reboot, it just stays off. A reboot generally cures it.

I'll try to catch logs for the no ringtone problem tonight, the LED issue is pretty random so it may be had to log.

[ACL] 01-11-2012 05:05 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by mbellot (Post 2163981)
I have had problems with ringtone audio, but had chalked it up to all the other mucking around I had been doing lately.

Notification tones (SMS, etc) work fine, which is (IMHO) truly odd since I would have thought they would route the same.

I have had a couple cases of no in-call audio, but it was in a bad reception area so I figured it was just poor signal.

EDIT: Just to be clear, incoming call ringtone is DOA even immediately after a reboot. RHOD400 FWIW.

The weirdest problem however (and not readily repeatable) is occasionally the LED will not indicate wake/sleep after a reboot, it just stays off. A reboot generally cures it.

I'll try to catch logs for the no ringtone problem tonight, the LED issue is pretty random so it may be had to log.

Nahh, dont worry about the no ringtone. That's a hack in itself that I implemented. The ringtone fails because as soon as a call comes in, the routing gets sent to the earpiece instead of the speaker. THe hack i have just ignores the first initial route, and let it go to speaker. I put more debug messages in place for future debugging of this. So we can find the true root cause. It only happens on cdma (not gsm).

Led is because of acoustic. It turns off the led causing confusion with the debugging. I'll have to move us to the regime led code which will disable debugging in general.

Edit: just to be clear. i do have ringing on my cdma. I'll check on the new release to make sure this is working before i put it out.

sykosoft 01-11-2012 05:18 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by mbellot (Post 2163981)
I have had problems with ringtone audio, but had chalked it up to all the other mucking around I had been doing lately.

Notification tones (SMS, etc) work fine, which is (IMHO) truly odd since I would have thought they would route the same.

I have had a couple cases of no in-call audio, but it was in a bad reception area so I figured it was just poor signal.

EDIT: Just to be clear, incoming call ringtone is DOA even immediately after a reboot. RHOD400 FWIW.

The weirdest problem however (and not readily repeatable) is occasionally the LED will not indicate wake/sleep after a reboot, it just stays off. A reboot generally cures it.

I'll try to catch logs for the no ringtone problem tonight, the LED issue is pretty random so it may be had to log.

+1 for ringtone issue, on an older non-acoustic build.

mbellot 01-11-2012 05:28 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by [ACL] (Post 2163982)
Nahh, dont worry about the no ringtone. That's a hack in itself that I implemented. The ringtone fails because as soon as a call comes in, the routing gets sent to the earpiece instead of the speaker. THe hack i have just ignores the first initial route, and let it go to speaker. I put more debug messages in place for future debugging of this. So we can find the true root cause. It only happens on cdma (not gsm).

OK, then I won't worry about pulling logs.

Quote:

Originally Posted by [ACL] (Post 2163982)
Led is because of acoustic. It turns off the led causing confusion with the debugging. I'll have to move us to the regime led code which will disable debugging in general.

OK. Just thought I'd mention it since it seems random. Most times the LED works as expected to display sleep/wake.

Quote:

Originally Posted by [ACL] (Post 2163982)
Edit: just to be clear. i do have ringing on my cdma. I'll check on the new release to make sure this is working before i put it out.

Sweet.

I think I'll make it a total do-over with the next release instead of trying to upgrade. That way there won't be any ghosts to debug.

mayestik1 01-11-2012 05:30 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
I'd like to post my 'cosmetic' issues:
- problem with special characters on physical keyborad. looks like "FN" key doesn't work correctly, because when I press it, I get "@"
- in Clock app, when I'm setting an alarm I see numbers instead of days name of the week ;)

huckl3b3rry 01-11-2012 07:55 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
I installed the Dec 24 release and when I made calls to the phone I wasn't getting audio from the phone mic to phone that I called from, however I called out and the phone audio worked; then from that point forward incoming calls are working correctly also. Just wanted to through that out there in case someone was having the same issue. Of course I have the same no incoming call ringtone issue.

arrrghhh 01-11-2012 08:10 PM

Re: [TESTING] - NAND OMGB (1.2.3)
 
Quote:

Originally Posted by mayestik1 (Post 2163987)
I'd like to post my 'cosmetic' issues:
- problem with special characters on physical keyborad. looks like "FN" key doesn't work correctly, because when I press it, I get "@"
- in Clock app, when I'm setting an alarm I see numbers instead of days name of the week ;)

The first one is an issue that RHOD100 folk should have resolved on HaRET... the same keymaps are being used, so... yea.

The second one is kinda entertaining, and I forgot about it. Wonder why it does that?


All times are GMT -4. The time now is 06:08 PM.

Powered by vBulletin® ©2000 - 2025, Jelsoft Enterprises Ltd.
©2012 - PPCGeeks.com


Content Relevant URLs by vBSEO 3.6.0