yashsingh1/xdaforums huggingface dataset:
[Thunderbolt Android Development] Absolute_Zero:
Was that proven? I only saw someone suggest that it might. I mean it may and that's fine, just no reason to take a random user's word as gospel until they provide evidence. It seems with the same settings in each (no profiles in setcpu just the same min/max and gov set) they'd react nearly identically or at least enough for the difference to be negligible. That may not be true but all I can say is I've used both and I've gone back to setcpu for the time being (mostly for the profiles as you mentioned).

Btw, SetCPU is free: http://xdaforums.com/showthread.php?t=505419
[Thunderbolt Android Development] keith.mcintyre26:
I don't use setcpu and my lock screen lag is my only issue with the rom.
[Thunderbolt Android Development] julian.o.neill:
Still having Network Location Service issues when GPS is turned off. My Thunderbolt believes it is in Alabama when GPS is off. Turning the GPS on results in the correct location being resolved - Missouri.
[Thunderbolt Android Development] cam30era:
I have not seen any scientific evidence. But from my own personal experience, I have no lockscreen lag with the CM7 governor. I think users on this forum should be aware of the option. Each can do the experiment themselves and make their own decision. It's easy enough.
[Thunderbolt Android Development] JBAeroEngineer:
does anyone not have 3G/4G signal with the new radio right now? Went to bed with no problems, today 2 grey bars
[Thunderbolt Android Development] ilovesoad:
You probably have an app preventing your phone from sleeping.
[Thunderbolt Android Development] SomeGuyDude:
Opposite! The battery is AMAZING. That's what I meant. On Sense ROMs I could go to bed with 40% battery and if it was still alive when I woke up it'd barely have a charge left.

Last night I laid down with my battery at 48% and played a few rounds of solitaire plus downloaded some stuff, then I went to sleep. Woke up this morning and it was at 45%.
[Thunderbolt Android Development] destroyerbmx:
I have been real reluctant to run this on my TB, as I started cyan with the eris days, but I finally gave it a go and it works fine, to me it worked better than the BAMF sense 3.0 so far but both are in development. I got so used to sense that an AOSP rom scared me, but its so light and everything loads fast. I have some minor issues w/ some apps crashing but as a phone it works.
[Thunderbolt Android Development] Derek1267:
I've searched through a bunch of pages (no time to go through all of them =O ), but after I wiped twice/wiped cache/dalvik/batt stats, when it booted I had no market access and couldn't sign into my google account.

Could someone be helpful and tell me what I'm missing

Thanks in advance <3
[Thunderbolt Android Development] dashaund:
I've experienced lag issues with the lockscreen off and on, usually after a kernel flash. If I go into recovery, wipe cache, wipe dalvik cache, and fix permissions, it's resolved. If that doesn't work, I reflash CM7 (without wiping), then wipe cache, dalvik, and fix permissions, and it fixes the issue.
[Thunderbolt Android Development] bilbobrian:
You have to install gapps after you flash the rom...;)
[Thunderbolt Android Development] toebee76:
Last friday I bricked using CM7 1.2 and the MR1 radio so I have a hard time believing this is radio related. I was using the MR2 earlier that day, but I was having trouble with wifi. I switched back to MR1, things seemed fine, I was charging when I noticed the light sensor for auto-brightness wasn't working. I decided to do a reboot, for some reason that's all it took. Started boot looping at CM7 load screen. Tried going into recovery but it would reboot itself before I could choose to restore a backup.

My guess would be a hardware problem.
[Thunderbolt Android Development] Odinist:
Totally unrelated to CM, but I *had* to give you a shout for your avatar... Satan from that Mark Twain show... SUCH A CREEPY EPISODE. Well done. =)
[Thunderbolt Android Development] bradgog:
When you say bricked what are you referring to, a actual unrecoverable hard brick or a soft brick?
[Thunderbolt Android Development] Absolute_Zero:
That actually has a little bit to do with why I feel the difference is negligible. The governor is not a result of setcpu or the CM7 cpu settings. It's built into the kernel itself. The only possible difference I could see is with setcpu being an app that has to run and change the settings but they should be changing the same things.

That said, I do completely agree that users should be aware of both and feel free to experiment.
[Thunderbolt Android Development] destroyerbmx:
It could be 100% emmc just failing, any one know if there had been any stock bricks?
[Thunderbolt Android Development] stearic:
Thanks for the correction, that's what i get for trying to help out when i should be sleeping. I was partially right though in regards to killing 4g wont' effect being able to use voice/data at the same time at least, haha.
[Thunderbolt Android Development] toebee76:
Unrecoverable. Like I mentioned it boot looped even in recovery.
[Thunderbolt Android Development] Bimmer323:
Were you getting into recovery through rom manager, or straight to recovery?
[Thunderbolt Android Development] bratliff:
Yes there are stock bricks.. if you read through the data collection thread.. 100% stock..
[Thunderbolt Android Development] toebee76:
Kinda hard to use rom manager when it wont even fully boot up :p

Honestly I can't remember the last time I used rom manager for anything.
[Thunderbolt Android Development] gixxertriplezero:
If I can't post in a forum it says data type null or something like that. Was I blocked?
[Thunderbolt Android Development] scriz:
Anyone notice that CM7 doesn't reset battery stats when the phone is plugged in or restarted? Is that just Gingerbread..or ..?
[Thunderbolt Android Development] youneek:
Let it charge for 24 hours and still wouldn't work. Once the battery was totally discharged it never could recharge again...
[Thunderbolt Android Development] sundar2012:
this is a feature of gingerbread. it will reset when u charge up to 100%.
[Thunderbolt Android Development] cam30era:
Do you have 10 posts yet?
[Thunderbolt Android Development] DaRkL3AD3R:
Honestly...... that's insane lol Can you please elaborate on your setup? I don't want to seem invasive but if you could indulge us with a full listing of all installed apps and a general idea of running services along with your radio signal that'd be great. Also do you turn Plane mode on at night or do you let it sit, connected to Voice and Data?

I'm finding quite the opposite as you :( looking more like 15-20% battery loss per night. But that's without turning off data or voice and letting it sit idle.

Sooo if you can like, hook us up with the run-down on that sick 2%/8 hours, it'd be greatly appreciated lol.
[Thunderbolt Android Development] dB Zac:
This port is so clean!! Than you for all the hard work. My only bug has been the jitter issue, witch is an easy fix. Wifi hooks up fast for me!
[Thunderbolt Android Development] simonmiller1:
FWIW I selected CDMA/EVDO Auto and I was unable to receive phone calls. I have switched back to CDMA + LTE/EvDo auto for now.
[Thunderbolt Android Development] :
are we going to get hooked up with nightlies soon?
[Thunderbolt Android Development] simonmiller1:
I'm not getting stellar battery life either. Hmm.
[Thunderbolt Android Development] Mustang302LX:
That's weird because I'm always in CDMA/EVDO mode and I haven't had an issue receiving phone calls.
[Thunderbolt Android Development] gixxertriplezero:
Yes I was able to post before
[Thunderbolt Android Development] sundar2012:
SetCPU is not a governor - it is an app that runs in the background and changes your min/max clock settings and cpu governors based on conditions. CM7 has a built in CPU settings menu where u can set the overclock stuff and the governor but it doesn't do conditional changes.

With that said, the whole point of a cpu governor is to conditionally change the cpu speeds. Screen Off profiles that underclock do little - because when your phone is screen off or idling the governor automatically brings the clock speed that the cpu is running at down. If anything, a low cpu speed while screen off could cause more battery drain as more cpu cycles are used at a lower speed to process background tasks.

The only reason to use setcpu is if you like it and/or are doing some hardcore overclocking/overvolting and you need temperature based failsafe profiles. SetCPU will not save battery and the consensus, amongst most pwoer users, is it will actually drain battery as it runs as a background process and if u artificially lower cpu max speeds you create inefficiencies (high cycles at low speed) that the cpu governor would have otherwise managed on its own.
[Thunderbolt Android Development] kmthomas2009:
I have between seeing people saying they are getting bricks with this and the official mr2...is this true or am I misinterpreting?? A little confused here and really wanna flash this
[Thunderbolt Android Development] Eddog4DROID:
Is there a specific radio that should be used in RC 1.2 in order to get successful 4G hand offs? I am still having problems off of wifi and on reboot. I am using the Official 2.0.
[Thunderbolt Android Development] dalingrin:
Setting wifi sleep policy to never does wonders for battery life when you are around wifi networks that you can connect to.
[Thunderbolt Android Development] dB Zac:
My battery life ain't to bad
[Thunderbolt Android Development] CBMC:
I have seen people getting bricks on mr1 and mr2. I think these phones are prone to bricking.
[Thunderbolt Android Development] kmthomas2009:
Damn :/ I really like cyanogen but I don't like bricked phones lol
[Thunderbolt Android Development] 2k10MBC300SPT:
Sent from my 4G ThundaBolt, 1.8Ghz Processor, w/XDA App!
[Thunderbolt Android Development] 2k10MBC300SPT:
Sundar sound like he/she really knows a thing or two about setcpu..point well taken..

Sent from my 4G ThundaBolt, 1.8Ghz Processor, w/XDA App!
[Thunderbolt Android Development] Mustang302LX:
Thanks for the write-up! I just recently got rid of it and I'm glad I did. I also found that setting my min freq. to 368Mhz was making my lockscreen and some other stuff lag. I'm not set to run 768Mhz-1.1Ghz using CM7 settings with interactive governor.
[Thunderbolt Android Development] n0thing2bdone:
whenever i looked at time-in-state on imo's kernels, 368 was hardly ever used, regardless which governor or usage scenario. i wouldn't be surprised if setting that as your min. is problematic
[Thunderbolt Android Development] ShanDestromp:
I've got to break in here and point out that this is...wrong. A given task will consume the same amount of processing cycles regardless of how fast the processor is set to. The only variable is in how long it takes the task to complete, as at faster processor speeds, more cycles are performed per second.

Given that at lower processor speeds, less power is consumed a lower max speed is directly beneficial to your battery, particularly when the device is not being actively used. The only exception to this is when the device IS being used, and the screen, which is generally the largest power hog, is artificially kept on longer because of the user waiting for a task to complete.

To give you an analogy; if your car consumes one gallon of gas driving five miles; there will be no difference in the amount of fuel consumed if you drive those five miles in an hour at 5mph; or in 5 minutes at 60mph. You can exclude any "start/stop" and "wind resistance" variables from this analogy as computers don't suffer from any "idling" waste or such; except in cases where you have a low memory situation and the device needs to swap data in and out of RAM frequently. But we're not; so we wont go there :-)

While its true that having setCPU running WILL cause a background service to be running (and thus consume some cpu cycles) it is not "overriding" the governor exactly; and is certainly not confusing it or causing inefficiencies. setCPU works in conjunction WITH the users selected governor to change clock speeds based off of profiles the user selects; such as low power situations.

Governors only control how and when a processor changes its clock setting; and does nothing in regards to the absolute min or max available. In theory, most governors are supposed to clock down when not in use, and back up when the processor reaches a specified load %; however in practice many aren't forceful enough in this regard; and take the slightest use of the processor as an opportunity to ramp up to full speed, and are quite sluggish in going back down; using setCPU and a screen off profile (for example) can limit the amount of excess drain on your battery a process can have.

Ultimately does it "save" your battery? Depends on how you use it and how much you really care. If your phone manages to last you all day, does it really matter if you have 60% when you plug it in vs 30%?

Before I go sundar2012, I hope you don't take this to be an attack on you; as that is most certainly not my intent; but just trying to help squash some of the misinformation that manages to continue to hang around the android world. I do the same thing regarding the "benefit" of task-killers.
[Thunderbolt Android Development] n0thing2bdone:
^you left voltages out of the equation and your driving analogy is just wrong
[Thunderbolt Android Development] ShanDestromp:
Most people don't tamper with voltages and leave then to whatever the kernel is set to. AS For my analogy, it works in the context it was given, no its not perfect but that's why its an analogy. If I was striving for absolute perfection I wouldn't have used one.
[Thunderbolt Android Development] CBMC:
I didn't mean that cm7 was the cause of these bricks. What I meant is that these bricks seem to be happening across the board on all roms and all radios. There probably is some hardware issue, but who knows.
[Thunderbolt Android Development] mojonation1487:
That was a horrible analogy to use because of different fuel economies. But back to the phone stuff. This isn't necessarily true because having a task go longer at a slower speed can drain more battery just from the length of the app, then powering it with more processor and zapping that task away. Food for thought.
[Thunderbolt Android Development] mojonation1487:
probably user related bricking. The gingerbread bricking that was seen in large numbers (not really but barely enough to draw attention) was for sense based roms. CM7 was in the clear on that.
[Thunderbolt Android Development] ScoobarSTI:
can not for the life of me get GPS to lock.

I read around, flashed back, and made a back up and went back to CM7. Other then that I didn't see any other fixes. Any ideas?
[Thunderbolt Android Development] chykal:
I am on CM7 1.2, OTA MR2 Radio 1.39.00.0627r and deamkernel 2.3.0 and CallRecorder is working. I installed it from TiBu and it did not work on the 1st call out but after that it has worked for all of 3 calls I have made/taken. I also ran the app 1st from the app drawer for it to gain root permissions before making a call.

Thank you Slayher for this great ROM!
[Thunderbolt Android Development] minazaki:
Need more info to help:

Radio, kernel, CM7 version, wipe before installing? Were you able to get a lock on stock/sense based roms?

Also, from the sequence you listed, it's not exactly clear what steps you took to try to do the fix. The appropriate steps would be to do the following:

1. Backup CM7 in Clockwork.

2. Flash a Sense based ROM, such as BAMF.

3. Get a GPS fix.

4. While your GPS is locked, reboot to recovery.

5. Restore the CM7 backup you made in step 1.

6. Your GPS should now be working.

Also, check these threads for fixes to some of the more common problems:

http://xdaforums.com/showthread.php?t=1163043

and

http://xdaforums.com/showthread.php?t=1125466
[Thunderbolt Android Development] SolZer:
I was having this exact problem, no matter what I tried. Over the weekend I installed Retrokid223's Official 1.70.605.0 MR2 OTA with new radio. After installing I let it settle for a bit, enabled GPS, waited for lock (locked quickly), etc. After using for a bit, I wiped all (cache/dalvik/data/system), installed CM7 RC1.2, and I've had 0 GPS issues. Might be worth a try...
[Thunderbolt Android Development] SOGJC:
This is just information, you can try if you want.

I'm running cyanogen rc1.2 mr2, now I'm using the new radio 1.39.00.0627, 0.01.69.0625r and I notice an improvement in the battery life, I have extended battery, I unplug from charger at 6:30am and now is 5:30pm and the battery is at 78 percent, which before by this time I was around 60 percent or less. Tomorrow I will try with stock battery and see what happen. The GPS lock in less then 8 second and the 4G is still same speed, but when I first install the radio it was a little weird because when I was using the data network by just two seconds disconnect the network and then right away pick it up, but now is working just fine. In my phone I have exchange account with push notification also, Hotmail, Gmail, yahoo, Facebook, fancy widget and other regular stuff.

This is just a report so others can have ideas.

Thanks
[Thunderbolt Android Development] ScoobarSTI:
Yeah I followed those steps.

I'm running CM7, new OTA radio, Lean kernel. Always did wipes before installs. Sense based roms specifically Gingeritis i had GPS lock in 5-6 seconds.

I'll check those threads though thanks
[Thunderbolt Android Development] WBMc36:
GPS works fine for me, 4g is still not working for me on the new MR2 OTA radio, and battery life has been horrible. Any ideas on what to do?
[Thunderbolt Android Development] SikYou:
Read this thread (-:

Sent from my ThunderBolt
[Thunderbolt Android Development] minazaki:
Would recommend trying the following:

full wipe -> CM7 install with included kernel -> backup in clockwork -> full wipe -> install Sense based ROM that you know works for you -> get a lock -> while locked, hold power button and reboot to recovery (i.e., don't exit maps or whatever program you are using to obtain a lock) -> wipe -> restore CM7 backup.

Probably pretty close to what you did, but probably also worth another try.
[Thunderbolt Android Development] ScoobarSTI:
I'll give that a shot, thanks!
[Thunderbolt Android Development] WBMc36:
alright dude, that doesn't help me at all. I have read the thread and read the radio thread. If you have something that will help me let me know. Believe it or not there are over to 700 pages on here, maybe i missed something.

So far nothing in there has been helpful.
[Thunderbolt Android Development] Cg006:
My GPS has been the best EVER. Locks almost instantly

im using the MR2 official radio.

Try reseting the gps data with that gps status app and turn on the wifi before opening maps (worked for me on the mr1 cyanogen rom)
[Thunderbolt Android Development] Mustang302LX:
8 hours on battery down to 59% with basically no useage due to workload today. About to go back to my old ROM. That's terrible.

Sent from my Thunderbolt running CyanogenMod 7 using the Tapatalk app.
[Thunderbolt Android Development] bobby janow:
You might want to buy another USB cord or extra battery if you can't live over 16 hours on one charge, don't you think?
[Thunderbolt Android Development] WBMc36:
I have a 1700mah battery and would easily get 20 hours or more on rc1.2 with the mr1 radio. Switched to mr2 and charged twice today. Something is funny about this radio, or maybe i had a bad flash idk but this great battery life i heard about is not happening for me. Thinking about going back to mr1, just don't know if there are going to be any more builds with it.
[Thunderbolt Android Development] psufan5:
Just an FYI your 1700 battery is probably just as good if not worse than the stock battery the phone comes with. Those companies lie about their battery power.
[Thunderbolt Android Development] youneek:
I disabled Google+ updates, set wifi to never sleep and disabled 4g. You can see only 20% of the time it was connected to wifi and STILL have 64% battery after almost 24 hours. Pulse reader, tweetdeck, etc are all still on and updating like normal.
[Thunderbolt Android Development] WBMc36:
in my experience it is way better than stock. I had a battery from the same site in my incredible and it does wonders. Whether or not they lied about it or not i get far better results than the stock battery. If i used a stock battery i would have charged around 4 times today.

Jeez so much negativity on here today.

Can't get any suggestions with 4g help, and debbie downers everywhere.
[Thunderbolt Android Development] cj1896:
Had my first reboot today, running MR2 OTA radio. I was listening to Pandora, checking e-mail and reading the web so it was getting quite a workout.
[Thunderbolt Android Development] 2k10MBC300SPT:
The only thing I could recommend you to do is to try the approach that a lot of people have taken (including myself) and have had great success in general; wipe all (factory reset, dalvik cache, wipe battery stats), Load a stable GB rom like DasBamf or Synergy, use the mr2 radio {leaked or OTA (preferred myself)}, once you successfully load rom, let phone sit (don't sign in to google) for a few minutes and let rom settle in w/kernel, once that is fine, sign in to google, let phone do it's syncing, now access gps accordingly (have an actual address lock in), once that is all fine, be sure to d/l a clean and good file of CM 7, repeat first step with the wiping, load CM7 , let rom settle accordingly then sign in to google, once that is fine, you really shouldn't have any issues locking in GPS. if after all this, gps issue remains, I have no idea what to recommend from here. I've done "EXACTLY" what I'm recommending and I am enjoying CM like so much, I no longer have any roms , mods, themes of anything else related to any other rom other than CM on my SD. Talk about clearing up memory on my card..Good luck and hope you're as patient as I and most people are in order to achieve these GREAT results. Keep in mind, no two devices will react the same...again, I wish you well..

Sent from my 4G ThundaBolt, 1.8Ghz Processor, w/XDA App!
[Thunderbolt Android Development] SikYou:
When I said "read this thread" is wasn't trying to be a jerk, rather I was saying you are not the only 1 with poor battery life or poor GPS signal or even poor 4g. There seems to be an inconsistency here; many of us, myself included, are pushing 36+ hours on a single charge with the stock or stock-equivalent battery. I am not sure what the pattern is, neither is anyone else, read the thread and that is the conclusion that one should come to. Either "we" are doing something right or "you" are doing something wrong. I suggest looking at what apps are syncing and are "awake" when they shouldn't be, causing constant drain of the battery. Also look at your settings and make sure you are optimizing everything for battery life, i.e. don't use auto backlight and turn off push email ( these are standard battery saving tips compliments of Google). Also give the rom some time, I never see optimal battery life out of any rom until it has "settled" for a battery cycle or 2.

Sent from my ThunderBolt