Quote:
Originally Posted by BrooMann
Dude...I am having the same issue. Deck...ne idea's on what we're doin wrong? I also tried just doin restorin app + data(not system data). But still get stuck on Android logo on reboot. I thought it might be the CM advanced settings...since u added CM's tablet tweaks in there...so I didn't retore that at all...but still get on Android logo with this too on reboot.
Finally...still have GPS drama! LoL. I still have to goto a sense rom 2 reset my GPS with ##GPSCLRX#. I then I also use the app GPS Status & Toolbox to reset it and then download GPS data.
|
please do not restore any system data with any backup program until a final release. too many changes to framework and whatnot for it to not cause problems. apps and data are fine.
Quote:
Originally Posted by amw1972
Deck...couple of things...I would very much like to ask you keep DSP Manager in the ROM...but if you don't (not a deal breaker) Just would like to see from someone a flashable .zip for it...think there might be interest.
Seeing that your base is off the same kernel as CM...wondering if the newest radio ( 2.15.00.04.08) would be an issue? Believe this was leaked along with latest GB build for the EVO.
Planning on giving it a go and see if things are better OR worse...hehe |
dsp is back in for you all. voicemail was removed but added to the OP. btw, how is the new radio working? i havent had time to play with it yet.
Quote:
Originally Posted by lkillen
I rolled back to pre 2. That was a good release for me.
As a developer, I know it is easy to have a ill-featured app slip out the gate.
|
pre3 was a mess. sorry about that. i cooked up pre4, which *hopefully* fixes the issues every1 was talking about. Also, i am running tiamat 3.3.7 sbc atm and am VERY pleased so far, hopefully it stays that way. For some reason CM's latest kernel breaks phone proximity sensors. thats why people were having issues with screen on and off at the end of calls, the sensor was simply not working. i didnt want to add the tiamat kernel into the release, but i am thinking about it depending on how things play out for the 1.0 release. as that is all out of the way, please give pre4 a shot and tell me if the problems have gone away. Besides the proximity sensors, i couldnt find anything else wrong with the stock kernel. so if it doesnt bother you, go ahead and run the stock kernel, i am sure cm will get it figured out soon. i have not ran the latest savaged-zen with it so i am not to sure how that will pan out. anyways, enough of my blabber, back to the OP and get the goods!
-deck
EDIT: once 1.0 is released, i may start tinkering around compiling a kernel or 2
