yashsingh1/xdaforums huggingface dataset:
[EVO 4G General] DomSim:
i would say average is a few weeks to a month based on previous ota getting rooted. however google seems to have done a good job at plugging all the holes and it may be considerably longer. no way to know how long really. just depends how much scouring it takes to find an exploit. take the rageagainstthecage exploit, that wasnt discovered until about 6 months after froyo was release iirc
[EVO 4G General] HipKat:
I get aggravated to, but the guy asked the question in a decent enough. non-naab way.

Truth is, if you have 2.3.3 and you're S-on, there is no root, currently.

Give it some time, be patient and use the time to read as much as you can and get an idea of what you want and how you want to set it up once a root method is developed.

Specifically, I'd learn APS2SD/SD Card partitioning, Which ROMS suit your needs the best and how you want to set your screens up
[EVO 4G General] DomSim:
op asked in a manner befitting someone who has not searched or tried to answer for himself hence is why he got some flammage. Schlenkerla, however, asked in an educated and obviously researched way which earned him a proper reply.
[EVO 4G General] iluvmyevo:
no root? How about another option?

ok, i have been reading every single day on how to re-root my evo. Now, im not asking if there is a root method yet, however i need to ask this.

Is is possible to revert the hboot, firmware, to a previous version. I an unable to install a ruu OS because im s-on of course. I would just like to know if there is ANY way to revert back to 2.2 so i can just root the normal way and start flashing roms daily again... It can be complicated, im highly technical, but i cant find anyhting talking about a way to do this.
[EVO 4G General] DomSim:
not possible at this point. the 2.16 hboot will not allow an older version to be flashed.
[EVO 4G General] iluvmyevo:
Crap, that sucks! thanks for the info.
[EVO 4G General] Schlenkerla:
I am guessing the same goes with a factory reset.

Btw - what all does factory reset do?
[EVO 4G General] Rem3Dy:
Forums also don't need the same question asked in 50 different threads.
[EVO 4G General] Arbron:
Or people running around being jerks on it. If a complete stranger asked you the same question for the 50th time in real life would you blow up in their face about it? No. So why would you on the internet? The internet makes people feel empowered to be rude because they aren't face to face. Let's just keep in mind that person on the other end is a human being, and we all are lazy and all don't search for stuff ok?

I can't tell you how many times my husband has said "I can't find the ketchup" and I say "did you look behind the milk?". The answer is always no, but that's where it is!

Maybe its just guys that have the problem with not knowing how to search.
[EVO 4G General] HipKat:
Because if someone asks you a question you've heard over and over, they may not be in a position to do a simple search for the answer before they ask....
[EVO 4G General] tejasrichard:
Look, I am not a flamer (at least , not where noobs are concerned). I normally just ignore questions that have been answered 1000 times. Believe it or not, I am actually a pretty polite dood, especially to people I don't know. That being said, the thought process that starts with "everybody does it" and ends with "fvk it, i'll just ask instead of bothering to search" is just wrong. Feel free to search through every thread I have ever started and show me were I started a thread asking a question that had already been done to death. Do it. People get flamed because others want the questions to STOP! They WANT noobs to be too afraid of flaming to ask a question. I was gone on vacation, and away from from XDA for basically a solid week. During that vacation, I managed to smash my phone's screen. As soon as I got home, I put in for my replacement, and immediately started searching for root methods for the newest OTA. It took less than 10 minutes to determine that there was no news...with the exception of this, which obviously is not very helpful.

In short: Don't start a new thread unless you are SURE that there is not already a thread about your topic. If you decide to do it anyway, don't complain when you get flamed. It is your own fault. Human nature is no excuse for anything. We are humans and have the power to observe both ourselves and the world around us, and we have the ability to modify our behavior based on those observations. For instance, I was absolutely positive, when I began writing this response, that at least one person would feel the need to flame me for it. Go ahead. I can take it. I put my big-boy pants on. ;):D
[XPERIA X10 Q&A, Help & Troubleshooting] BoiseMCSS:
Sorry if this is posted elsewhere, I couldn't find anything on it.

I'm having trouble accessing the internet by the phone.

I'm running 2.1 update1, BB 2.1.54, Kernal 2.6.29, Build 2.1.A.0.435

I found the problem trying to use Shopkick. It would continually say my phone is having trouble connecting. So I brought it to work (Best Buy) and had them look at it. All the settings are correct and he even tried to use the BBY wireless and it didn't pick it up at all. It was full bars on his HTC.

Just to be sure I reset the phones setting back to default a couple of times. Does anyone have any suggestions?
[XPERIA X10 Q&A, Help & Troubleshooting] agentJBM:
Could be the app. I saw someone else with the same problem in NYC.
[XPERIA X10 Q&A, Help & Troubleshooting] BoiseMCSS:
Re-flashed my phone and the problem is fixed.

Thanks!
[Hero, G2 Touch Q&A, Help & Troubleshooting] Symondo10:
Hi everyone,

I apologise if this is in the wrong forum but i feel it should be here as it is regards to development.

I found this on the Slashdot website

http://hardware.slashdot.org/story/11/06/16/2127255/New-Android-Malware-Attacks-Custom-ROMs

"Today Lookout disclosed a new form of Android malware found in Chinese markets which attacks third-party firmwares (ROMs). By using permissions granted to apps which are signed with the same private keys as the ROM itself, an app can update itself or install and uninstall other apps without user interaction. Most third-party ROMs use the private keys included in the Android Open Source Project, making them vulnerable to this attack. Last month's release of CyanogenMod 7.0.3 (and all subsequent builds) included an "important security fix" which a team member confirmed protects users against this vulnerability by preventing applications signed with the platform key to be installed to user or app-controlled storage."

I apreicate that the latest CM7 Roms will cover this vulnerbility but how does this apply to Eclair, Froyo roms?

Many thanks
[Hero, G2 Touch Q&A, Help & Troubleshooting] Habarug:
Pulser just fixed this in the Froydvillain 1.7.3, don't know about other roms though...
[Hero, G2 Touch Q&A, Help & Troubleshooting] k0zmic:
I think unless the Eclair and Froyo ROM's are patched they'd still be vulnerable?
[Hero, G2 Touch Q&A, Help & Troubleshooting] Habarug:
Yes, they are, it seems only froydvillain is parched, though :(
[Hero, G2 Touch Q&A, Help & Troubleshooting] perdita2000:
Elelinux latest roms and Tesla were based on CM 7.03 sources.

Perdita2000
[Hero, G2 Touch Q&A, Help & Troubleshooting] pulser_g2:
Yes, I fixed this in the middle of may, fairly quietly so as not to cause people to find out about the issue.

There was a period of responsible disclosure regarding this, and I know the researcher involved.

Either way, a workaround is in use in recent cm7 roms, although not a complete change of keys, but rather a way to alleviate the risks of the attack.

Anyone has access to the cm signing keys, meaning this was an issue before action was taken.

Hope that clears things up
[Hero, G2 Touch Q&A, Help & Troubleshooting] m4rk84:
Hey Pulsar, long time no IRC. Is the 'fix' or whatever you implemented transferable to roms that are < 2.3 ?
[Hero, G2 Touch Q&A, Help & Troubleshooting] erasmux:
Thanks for this discussion, I was not aware of this issue before.

I will patch up the final version of Floyo 1.4 as well.
[Hero, G2 Touch Q&A, Help & Troubleshooting] Symondo10:
Thanks for the clarification everyone.

I'm glad that measures are being taken to avoid this risk.

Thanks again

Sy
[Hero, G2 Touch Q&A, Help & Troubleshooting] pulser_g2:
Yes, as Froyd is a 2.2 ROM.

It's easy enough to fix without editing the sources too, or you can do the CM workaround which seems to work fine.
[Hero, G2 Touch Q&A, Help & Troubleshooting] notea:
sorry to dig up an old thread, i've been looking at using 2.2 again, but it seems like FroydVillain is *still* the only 2.2 rom with this fix? or did it get included in the CM source somewhere? (6.2.0?) Speaking of which, i can't find much documentation on 6.2.0, stops at 6.1.3. did i miss something in my noobishness?

i noticed he said he'd include it in his floyo 1.4 final.. but it never seemed to come out *cough* *cough*

is the fix available to do manually? and what is the CM workaround?

(sorry if this is info is somewhere else already.. i've not found it though =/)
[EVO 4G Android Development] shakuyi:
wow sounds like it could work but im too busy with work...hopefully this thread will get more people to try this fix and see if it works for them....my fingers are definitely crossed!
[EVO 4G Android Development] dgrobe2112:
thanks for this.. i will try it out.. i currently allready have the 1.77 on my phone.. dont know bout the radios.. last time i tried to flash radios i had net closing issues..
[EVO 4G Android Development] JBabey:
I have had issues like this as well, but only when I do the radio's through the recovery partition. That is why I enclosed it as a PC36IMG.zip file so that it could be done by the "official" HTC update method. I have had no issues doing it this way. Good luck, looking forward to hearing that your issue is resolved.
[EVO 4G Android Development] glennpettit:
Fails to install Can't find update script... any ideas??

CM7.0.3.1
[EVO 4G Android Development] dgrobe2112:
i dont have to reflash my rom do i?
[EVO 4G Android Development] dgrobe2112:
downloading now, should i clear battery stats?
[EVO 4G Android Development] JBabey:
Use AmonRA, the update script is not in EDIFY (I may have to fix that later)

You shouldn't need to. If you are clearing your battery stats, do that for the reasons its intended, and make sure you follow the top off/drain instructions when doing so or it could lead to false readings.

No, you are only updating your radio and thus will not lose your data or have to reflash your ROM. Please remember to follow the short instructions at the end for charging/reboot/2 hours before reporting back here please.
[EVO 4G Android Development] CheesyNutz:
flash the virus gps fix even if your not on the kingdom rom ?
[EVO 4G Android Development] glennpettit:
I am using RA.
[EVO 4G Android Development] xlGmanlx:
might give this a shot later, don't have high android OS, but might be interesting none the less
[EVO 4G Android Development] JBabey:
I re-uploaded the zip file, please redownload and lemme know if this one works for you.

Thanks!

If it aint broke..... lol (granted this will put you on the latest radio)

And.. I have found my GPS locks to be instantaneous on this driver.

I personally use CyanogenMOD Nightly 100 at the moment and it works like gangbusters on this ROM.
[EVO 4G Android Development] sag7392:
I used the GPS drivers provided by Vaelpak...and it worked! I'm using Salvage-Mod v1.2.1 GB 2.3.3 and my GPS pickup is now instant!

And to the OP, I haven't had this issue...but great work!!!
[EVO 4G Android Development] MizzouBrent:
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.
[EVO 4G Android Development] likwid687:
I assume when flashing a new nightly, I would need to reflash the GPS driver again?
[EVO 4G Android Development] GIGZ1971:
That's not even the problem for me, I'm on hardware 4 and with any of the 2.3.3 Roms the highest thing draining my battery is the display any ideas on how to reduce that. It's between 50%-right now at 86%. I have turned off auto display and notifications. Thanks in advance for any help.
[EVO 4G Android Development] A1Lonestar:
I had major issues with bat life and wake (android system) after flashing calkulins radiosfrom the ota 4.2.2 release. I downgraded radios to

Baseband 11.19

Pri 1.77

NV 1.77

Wimax 27167

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.

Cm 7.0.3.1

Sz 2.1.0 Cfs havs sbc

V0003
[EVO 4G Android Development] heartisall:
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
[EVO 4G Android Development] poppadoc:
Flashing it now while I'm at work (its slow today)
[EVO 4G Android Development] dgrobe2112:
i am finished with the install of the zips, and rebooting now.. you said 2 hours.. i will post back my findings.. to let you know what is going on..

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..
[EVO 4G Android Development] fitz420:
So I did what ropodope suggested with everything setup as instructed in the op and I ended up having a m.pokelock=1. I flashed back to the lastest wimax/baseband/pri combo and both values are now =0.

I must admit although I have been doing this for a while I don't fully understand the meaning of those values. I'm just going by the instructions provided by ropodope.

I actually suspected that the best battery life/performance I've had is with the latest radios/pri's and I don't think I'm gonna go messing around with those for a while.
[EVO 4G Android Development] jae04cc:
then what would you suggest?
[EVO 4G Android Development] ropodope:
there is no true fix at this time. The only thing that currently solves it is to wipe your cache/dalvik, then reboot and do the dumpsys power command to see. A dev I know is working on a fix and is close. When done I will be glad to spread it all over, until then there is no salvation.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] ropodope:
the latest radios, wimax and nv/pri are just fine. Most of the time I have no wakelock issue, but sometimes I do. When that happens, usually a wipe of the cache/dalvik, then reboot will fix it for the time being.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] MizzouBrent:
Ok so pokelock is 1 if I run that command. What does it even mean? It mentions phoneapp.
[EVO 4G Android Development] ropodope:
It means you currently have a wakelock issue. When you turn your screen off say for an hour and turn it back on your graph will show that your phone was awake the whole time.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] fitz420:
Alright.....I didnt think I had an issue....no mlocks or mpokelocks. After making one call mpokelocks=1. With the message:

poke lock 'PhoneApp': POKE_LOCK_IGNORE_CHEEK_EVENTS

So after rebooting no wakelocks....make one call and I have a wakelock. I've tried a bunch of stuff and no way to get rid of it.
[EVO 4G Android Development] lowspeed:
Same after 1st call.
[EVO 4G Android Development] MizzouBrent:
Spare parts doesn't list a dialer wakelock though. Does it not catch all wakelocks?

I'm running Deck 1.2 stable with Tiamat 4.0.5 for what it's worth.
[EVO 4G Android Development] ropodope:
Spareparts does not work correctly on gb.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] fitz420:
So does this issue affect all roms, kernels, radios etc, including stock or is this something specific to say aosp roms. Just curious.
[EVO 4G Android Development] wryun:
What is a "bmw graph"?
[EVO 4G Android Development] miguelfp1:
Battery Monitor Widget
[EVO 4G Android Development] wryun:
Which one is the best?

I am curious about this myself.
[EVO 4G Android Development] 18rmiller:
Its called" battery monitor widget "
[EVO 4G Android Development] wryun:
LMAO!

*facepalm*
[EVO 4G Android Development] garciajose8:
Does anyone know if I can use this fix with VirusROM Kingdom REVOlution | B1.3 | 2.3.3 | SENSE 3.0.
[EVO 4G Android Development] MizzouBrent:
Maybe this explains the weird battery drops that I have seen lately overnight with no apparent wakelocks. I don't get it though. With regular use I have had countless times of little to no battery drain while letting my phone rest overnight.
[EVO 4G Android Development] MizzouBrent:
Do we know what triggers the wakelock?
[EVO 4G Android Development] skcussrepolevedadx:
Why not try it and report if it does or not?
[EVO 4G Android Development] JBabey:
Absolutely correct, it does need to run and it does need to keep the system awake "sometimes". It just doesnt need to be outta control.

I to recieve it back in the top 70-80% if i Nandroid... i have no clue... anyone... anyone?.... Bueller.... Bueller.....

Check the front page for all of the alternates. I have not looked at SprintLovers in quite some time (Fresh is better IMHO), make sure you are using a root explorer program and navigate to the folder, im sure its there.

Kingdom will most likely work with sense properly... my running theory is that this particular driver is so wrapped up in sense that its looking for something it cannot find on AOSP roms and starts chewing up the CPU in an endless loop.

I have just tested the Cyanogen GPS fix from the OP on a sense phone that just came into the back (user complaining of ****ty battery life). Worked fine and the GPS still locked. Whatever method you choose, just report back please and let us know how it went for you on that ROM. Thanks!

My navigation absolutely does not drain this fast, and I to am using the vision driver, try the cyanogen one in the first post, and please let me know how that works out for you. That is quirky to say the least.

Did I mention how "Quirky" this issue is... .jeebuz... im glad you saw it through, i know how time consuming what you did was. Thank you for posting back, and .... yay!

=)

It is a really odd and bizarre set of instructions... even for XDA lol.

Android system stores the stat "Keep Awake" & "CPU Useage"

regardless, it works for me just fine, and my battery is gangbusters, typically 16+ hours w/ pretty decent useage. At this point in time if i am "suffering" then im happily doing it.

Who is this so-called dev that is working on and is close to a fix... what files is he working on? which source is he using, and most importantly what then, IS the actual issue? Im not being an ass, im honest to god curious about this black magic as this is no silver bullet, it just seems to work amazingly well for myself, and for many others that have visited the thread.

Anyways I cant say im not interested, so please post back here or start a new thread when you have a fix that is a little more stable and not so quirky.

I have no freakin idea, this combination seems to mitigate the issue for me so I am at a loss as to the actual root cause of the issue on this particular phone.
[EVO 4G Android Development] ropodope:
Hey man I don't think you are being disingenuous at all in anything you have posted and believe me when/if he solves this issue I will be more than happy to tell you, obviously I can't give his name right now because it isn't fixed. I and many others appreciate what your are trying to do.

EDIT: one thing I know is that pulling up the dialer causes a partial wakelock. Sometimes it sticks because the call was hung up but the app wasn't properly closed. After closing the app run dumpsys power again and you will see the partial wake lock gone. If it is still there, you need to open your dialer and close it again. If it doesn't remove the wakelock within a minute then run a killall com.android.phone command which will open about 5 different wakelocks, but will then shut them all down. This is what I have learned from one much wiser than myself but there is still no perm fix yet. Sorry i couldn't give you more to go on.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] Mazda:
Can you please tell us what NV is and how we can find out what version we currently have?

[EDIT]

After doing a little bit of research on my part and talking to a buddy of mine in NYC, I found out that NV and PRI have the same version number so if for example your PRI is 1.77.003 then your NV will be the same. NOW this isn't to say that NV and PRI are the same, all it is saying is that they share the same version number.....NV and PRI do two different things!!
[EVO 4G Android Development] ropodope:
yes but many people do not use the same two version numbers at the same time. They can each be flashed individually for whatever combo you want.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] ropodope:
NV is non volatile memory and there is currently no way to check your nv or pri numbers in an aosp rom and no way to check the nv on a sense rom that I am aware of. You know which one you have if you wipe cache/dalvik before flashing the file.

ropodope

Sent from my Vaelpak GB AOSP Preview Edition v0.2 for Evo 4g. Flash and ye shall receive.
[EVO 4G Android Development] MizzouBrent:
For what it's worth, last night I left my phone on the counter and it showed the m.pokelocks=1 and listed "phoneapp". I had 50% battery at the time and when I woke up this morning, I woke up with 9% battery. No wakelocks in spare parts and my battery usage shows 6% for Android System, with no crazy uptimes listed. m.pokelock=1 still showing the same as it was.

So I go into settings->apps and force close the dialer. I run the same terminal command and see that I now have a value of 0 in that field. I open the dialer and close it, same thing, still zero. I opened the dialer again, made a phone call and now it shows a value of 1. I guess I'm not sure if this really means anything, but if having a value of 1 means there's a wakelock, then my dialer is definitely causing a wakelock.
[EVO 4G Android Development] Beknatok:
May I make a constructive suggestion?

Why don't you privately contact JBabey & put him in touch with your associate? If they're both attempting to research and resolve the same issue, wouldn't a collaborative (public or private) effort hopefully yield more gain?

Aren't we all in this together?
[EVO 4G Android Development] Tattrpuff:
I also checked and I have the m.pokelocks=1 and listed "phoneapp". Battery is much better than it was with about 6-8 hours of battery is now about 14-16...but I used to get 24-28 hrs with mostly moderate use. I'm going to leave it as is until someone much smarter than myself can figure out. Let me know if you need any logs or dumps.
[EVO 4G Android Development] mmarks9156:
MikG 2.1

I'm on MikG v2.1 I flashed the PC36IMG.zip file and I have tried the GPS zip for both Vision and Kingdom and get stuck on HTC EVO 4G screen any ideas? Do I need to flash the GPS zip file?
[EVO 4G Android Development] JBabey:
It does hang on that screen for sometime after the flash, but it shouldnt be there for more than about 3 minutes. How long is it on that screen for, can you still get into your bootloader screen (the white one w/ 3 androids skateboarding at the bottom). Does your recovery partition still load.
[EVO 4G Android Development] mmarks9156:
I can still get into bootloader screen and Recovery still loads. I just tried flashing the NV_177 zip and GPS_Vision zip file waiting to see what happens.

Edit: Over 3 minutes still not booting up.