|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
also, it seems that after i place a few calls with my bluetooth headset, then charge the phone (usb cable, activesync option), and then i unplug the usb cable, i'll lose sound. i won't be able to listen to any songs, and when i call someone i can't hear anything on my end...
|
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
Quote:
|
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
i'll try hard reset..while i'm here. i want to confirm: can u reg edit the color highlights in tf3d? i'm able to reg edit everything in standard today screen..
|
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
Quote:
Usually when i have no bars in my house the phone doesn't like to connect to the internet or doesn't send text messages. Its just weird. |
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
Quote:
Now at this bar, I should have full service (or pretty close).. now I only have 2 bars max while a person w/ the same phone was grabbin nearly full service. But like others have said, I cant figure out why this is happening over a rom flash. |
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
My music tab can be a little glitchy on sound too. The only couple times it's happened I was using my stock headphones. Enabling replstordoimmaculate in filters has helped after a couple of reboots. I do not plan on keeping it on though.
Also, I got the US_Cities_manila (Courtesy of the ppckitchen's OEM VGA folder) to work on 4.3. Let Me know if you are interested and I'll post more. It's basically a US Focus with every town&city in all 50 states. fyi: It's a 1.5MB file instead of a 345K file. |
|
||||
Re: [12-18-08] Juicy ROM 4.3 [SYS OS 5.2.20764 Build 20764.1.4.3] [UC]
Just flashed 4.3 today. Looks good.
One thing I notice is that a 3rd party SIP does not "stick" with this rom, even if using the SIP Changer program. I had this problem with a custom build I put together recently and found that it was caused by using the EZ Input 1.5.32638.1. When I rolled back to the EZ Input version 1.5.32437.0 the problem was solved. Hope that helps. |
|
|
|