I think it is a sense gps driver taken from kingdom, sense roms do not need it but should work in any aosp rom.
how long are the batteries lasting like this.. i am using REVOlution 1.3.. not sure how long it will last for a day..
People pl stop quoting long-ass posts ...sheeesh
Sent from my PC36100 using XDA Premium App
What is acceptable for Android System usage? I'm at 23% right now and it's third on my list behind Cell Standby and Phone Idle. Is 23% high? I know I've seen it higher before. I am interested to hear more feedback on this fix.
I assume when flashing a new nightly, I would need to reflash the GPS driver again?
Still have issues though. Is it safe to flash radios that many times. I have heard it can scree stuff up so should I flash your combo. Also my GPS works fine using cm 7.0.3.1 do I stool need to flash your GPS fix.
I did this for the hell of it even though I wasn't having too many issues on Virus revo 1.3 however this fixed my intermittent wifi issue and seems to have improved my battery too. Thanks a lot
also.. as others have mentioned.. i havent been having any issues with the kingdom revo 1.3 rom.. other than battery drainage.. i dont have wake issues.. but wanted to see if this fixes anything.. will give updates..
This should work with kings alliance ROM right?
And can anyone confirm that this is working also my GPS locks at 10m should I do the gps drivers or is that good enough?
Ok couldn't wait, flashed! Just an observation, gps fix says cyanogen gps fix when run in recovery. So apparently not sense based.
So after flashing this cause I assumed it would be a good set of radios. I NOW have this issue when system never showed up before hand.
So after flashing this cause I assumed it would be a good set of radios. I NOW have this issue when system never showed up before hand.
So after flashing this cause I assumed it would be a good set of radios. I NOW have this issue when system never showed up before hand.
First I would like the thank the OP for bringing some attention to the issue. This thread seems to have started going in the wrong direction so I will make an attempt to clear some things up and shed some light on the situation with my findings. In my tests so far I cannot really find a combination of radios and pri to solve any of the problems mentioned in this thread. All my findings are using and testing aosp roms. Cm7 really but most aosp roms are based off of cm so this post should be helpful if you use an aosp rom and are having a unreleased pokelock caused by the dialer and/or high android system in the battery usage after phone calls. If you use a sense rom I do not recommend any of these fixes for you. If you use these on a sense rom you will probably mess something up and/or experience boot loops and lots of other problems. That being said lets get started:
Problem 1: The pokelock not being released after a phone call is made or received. This problem comes from the phone app and not the radios as far as I can tell from my tests.
Solution: http://www.mediafire.com/?xzw0zhonmnjw1xs
This file is a flashable zip of a new phone app that releases the wakelock after making a phone call the way its supposed to. I take no credit for this new phone app. It was made by Scott Brady (The same dev that fixed the mms problems on the evo in the cm nightlies about a month ago). I just got this from him. We haven't thoroughly tested it yet so please FLASH AT YOUR OWN RISK. Make a nandroid. I will say this though. In my current tests I have made about 40 calls with no pokelock and it seems to work wonderfully. The only reason I'm posting it early is because if you're like me and you know something is wrong then you want an immediate fix. Also using the killall command in terminal emulator or adb after every call can get tiresome... I have also tested with multiple radios In case anyone was wondering.
Problem 2: Android system spikes in the battery use in settings after a phone call is made or received.
Solution: I'm close but not finished yet...
Please read what I am about to say all the way through. What I have found is that the current proximity drivers for the evo are causing the android system in the battery use to go bonkers. I'm not really sure how much it affects your battery because it seems that it causes all your apps to not even show up in your battery stats. Proof? I have supplied two files in a zip:
http://www.mediafire.com/?mxks9k60shlckk5
THIS IS NOT A FLASHABLE ZIP. USE AT YOUR OWN RISK. One file is "sensors.supersonic.so" where I edited it so that android cannot find the drivers for your proximity sensor so it never comes on. The second file is "sensors.supersonic.so.bak" which is a backup of the original .so file that you can use if you want to turn your proximity back on. When I edited my sensors.supersonic.so file so the proximity wouldn't come on android system no longer spiked in my battery stats after a phone call!!! Also I tried to add a command to the build.prop first to disable the proximity sensor which would have been better practice but the command didn't work. Not sure if that's because cm overrides it or what. I can pretty much guarantee that this is an aosp problem and not a sense problem so if you use a sense rom you don't even need to worry about this. I doubt HTC has faulty proximity drivers on a stock rom... I could be wrong but I doubt it, they have screwed up in the past...
So what now? Well if you're on an aosp rom and the current proximity drivers work for you then you know what they say, "If it ain't broke don't try to fix it." For the rest of us I am in the process of trying to find some proximity drivers that don't make battery stats go haywire. Lets try to keep the thread relevant to findings so that we as a community can come closer to a fix instead of all the repetitive questions and things that don't help us get closer to a true fix... Don't forget the thanks button if you found this useful =P
Thanks for your time.
Edit: I would also like to add that I am on the most current radios, nv, and pri with no wakelock or spike in my android stats. And If you flashed the combo from the Calkulin thread you are probably missing the newest NV file because its not in there.
Is there a pokelock on sense? If so it wouldnt be as easy to fix since Sense is closed source and you cant just change the code, compile it, and then pull out the phone apk. Let me know and i'm sure we can get to the bottom of it. As I stated earlier I havent been on sense roms for my findings.
I have updated my OP if you dont mind with your comments and I really appreciate you and rope chiming in on this thread to help everyone in the community understand where the actual root of the issue lies. I am assuming the proximity sensor is what turns the screen off when you hold the phone close to your ear. I have inner ear problems and cannot hold a cell phone to my ears, as such I use an auto-speakerphone program and it turns my screen off when the speakerphone comes on after I answer the phone. This may account for all of my testing w/ radios not triggering the wake-lock, and when I test the phones, I place test calls and set them on the tech-bench and let them run.
I am pretty amazed how it all came about like a "perfect storm" of inaccuracy, and a little more amazed how well the previous fix seemed to work for a lot of members in the community. My assumption is that the GPS was just borked on a lot of peoples customs.
I look forward to a full bout of testing, and corrected drivers that can be incorporated into the source code for cyanogen and that the authors basing roms off of their branch all see relief from this issue going forward.
Thank you very much for your help, and I look forward to an approved, tested, fully functioning fix here shortly.
If you need any help from myself, I have access to near unlimited phones so please PM me.
Yeah i don't think it has anything to do with the radio combo.
GPS driver maybe.
I'm surprised Google is not working on this issue.
So I think I just found an unwanted side effect... my accelerometer has stopped working.
Fyi, I've applied both fixes. I'm assuming its the replaced driver.
Would someone else confirm?
Sent from my PC36100 using XDA App
First I would like the thank the OP for bringing some attention to the issue. This thread seems to have started going in the wrong direction so I will make an attempt to clear some things up and shed some light on the situation with my findings. In my tests so far I cannot really find a combination of radios and pri to solve any of the problems mentioned in this thread. All my findings are using and testing aosp roms. Cm7 really but most aosp roms are based off of cm so this post should be helpful if you use an aosp rom and are having a unreleased pokelock caused by the dialer and/or high android system in the battery usage after phone calls. If you use a sense rom I do not recommend any of these fixes for you. If you use these on a sense rom you will probably mess something up and/or experience boot loops and lots of other problems. That being said lets get started:
Problem 1: The pokelock not being released after a phone call is made or received. This problem comes from the phone app and not the radios as far as I can tell from my tests.
Solution: http://www.mediafire.com/?xzw0zhonmnjw1xs
This file is a flashable zip of a new phone app that releases the wakelock after making a phone call the way its supposed to. I take no credit for this new phone app. It was made by Scott Brady (The same dev that fixed the mms problems on the evo in the cm nightlies about a month ago). I just got this from him. We haven't thoroughly tested it yet so please FLASH AT YOUR OWN RISK. Make a nandroid. I will say this though. In my current tests I have made about 40 calls with no pokelock and it seems to work wonderfully. The only reason I'm posting it early is because if you're like me and you know something is wrong then you want an immediate fix. Also using the killall command in terminal emulator or adb after every call can get tiresome... I have also tested with multiple radios In case anyone was wondering.
Problem 2: Android system spikes in the battery use in settings after a phone call is made or received.
Solution: I'm close but not finished yet...
Please read what I am about to say all the way through. What I have found is that the current proximity drivers for the evo are causing the android system in the battery use to go bonkers. I'm not really sure how much it affects your battery because it seems that it causes all your apps to not even show up in your battery stats. Proof? I have supplied two files in a zip:
http://www.mediafire.com/?mxks9k60shlckk5
THIS IS NOT A FLASHABLE ZIP. USE AT YOUR OWN RISK. One file is "sensors.supersonic.so" where I edited it so that android cannot find the drivers for your proximity sensor so it never comes on. The second file is "sensors.supersonic.so.bak" which is a backup of the original .so file that you can use if you want to turn your proximity back on. When I edited my sensors.supersonic.so file so the proximity wouldn't come on android system no longer spiked in my battery stats after a phone call!!! Also I tried to add a command to the build.prop first to disable the proximity sensor which would have been better practice but the command didn't work. Not sure if that's because cm overrides it or what. I can pretty much guarantee that this is an aosp problem and not a sense problem so if you use a sense rom you don't even need to worry about this. I doubt HTC has faulty proximity drivers on a stock rom... I could be wrong but I doubt it, they have screwed up in the past...
So what now? Well if you're on an aosp rom and the current proximity drivers work for you then you know what they say, "If it ain't broke don't try to fix it." For the rest of us I am in the process of trying to find some proximity drivers that don't make battery stats go haywire. Lets try to keep the thread relevant to findings so that we as a community can come closer to a fix instead of all the repetitive questions and things that don't help us get closer to a true fix... Don't forget the thanks button if you found this useful =P
Thanks for your time.
Edit: I would also like to add that I am on the most current radios, nv, and pri with no wakelock or spike in my android stats. And If you flashed the combo from the Calkulin thread you are probably missing the newest NV file because its not in there.
Those files removed your proximity sensors for testing purposes. restore back to where you were so that the proximity sensors work. Take this single file and replace it with the one you have. Now your proximity sensors will work again and be very very responsive like they should be. This is not a flashable file. The file goes in /system/lib/hw with rw-, r--, r-- permissions. No reboot needed. Works instantly.I took the zip that was posted here, put the two files in the directory with my existing driver, so it overwrote the old file and I also had the one with the .bak at the end. What was I supposed to do? I read the instructions that were posted back on page 31.