Settings/CM Settings/Display/Automatic Backlight/Edit other levels...
I had to restore them to default from my previous settings to see Tickerguy's gradual stepping he placed on the softkeys in Beta 0.1, but you may not have to.
-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root [ROM][Beta][FINAL] CM7 Android For Triumph [Tickerguy Edition, Kernel: mine] 11/19
- Thread starter tickerguy
- Start date
-
- Tags
- motorola triumph
Settings/CM Settings/Display/Automatic Backlight/Edit other levels...
I had to restore them to default from my previous settings to see Tickerguy's gradual stepping he placed on the softkeys in Beta 0.1, but you may not have to.
tickerguy
Android Enthusiast
Has anyone seen a data drop with the latest update? I've not seen any comments saying they have......
If you are curious you can open the terminal emulator and start the following:
$ su
# logcat -b radio | grep bad
Then hit "HOME" and the program will remain running (unless you run low on RAM, at which point it will get whacked, but...)
The above line will not print anything UNLESS the "bad connection" tracking code gets hit. This will give you the ability to see an entry for each time the code finds a bad data connection and resets it. Note that the expectation is that this is the only way you'll ever see them, as the point where the drop gets detected is essentially instantly when it fails (e.g. it's not polling for status, it actually catches the state transition when the failure happens.)
It should also be pretty hard to get materially under 100Mb of free map space in RAM with this build, which helps the "user experience" a LOT. While it's not impossible to drive the system lower on free RAM it was pretty easy to get it down into the 50MB range before, and that's too low - Android does poorly when it gets RAM constrained, and the adjustments I made to the free space management routines in the latest update should make it almost impossible to get backed into that corner now. The code has was adjusted to be heavily prejudiced against services and data providers that do not have active consumers of their respective resources and to start protecting available memory in the 80-100MB range rather than allowing system RAM to fall into what IMHO are critical free space levels first.
Finally, if you want to get even MORE aggressive the "V6 Supercharger" script is in /system/xbin, as the author says is ok. I don't run it but you might want to; I suspect you get 90% of the benefit of doing so with the adjustments I made to the minfree maps.
If you are curious you can open the terminal emulator and start the following:
$ su
# logcat -b radio | grep bad
Then hit "HOME" and the program will remain running (unless you run low on RAM, at which point it will get whacked, but...)
The above line will not print anything UNLESS the "bad connection" tracking code gets hit. This will give you the ability to see an entry for each time the code finds a bad data connection and resets it. Note that the expectation is that this is the only way you'll ever see them, as the point where the drop gets detected is essentially instantly when it fails (e.g. it's not polling for status, it actually catches the state transition when the failure happens.)
It should also be pretty hard to get materially under 100Mb of free map space in RAM with this build, which helps the "user experience" a LOT. While it's not impossible to drive the system lower on free RAM it was pretty easy to get it down into the 50MB range before, and that's too low - Android does poorly when it gets RAM constrained, and the adjustments I made to the free space management routines in the latest update should make it almost impossible to get backed into that corner now. The code has was adjusted to be heavily prejudiced against services and data providers that do not have active consumers of their respective resources and to start protecting available memory in the 80-100MB range rather than allowing system RAM to fall into what IMHO are critical free space levels first.
Finally, if you want to get even MORE aggressive the "V6 Supercharger" script is in /system/xbin, as the author says is ok. I don't run it but you might want to; I suspect you get 90% of the benefit of doing so with the adjustments I made to the minfree maps.
idbl_fanatic
Android Enthusiast
areallytallguy
Lurker
No data drops for me since the most recent build, very pleased! Something I've noticed about the phone in general, both on stock and CM7, is that there seems to be a delay between when the lock button is pressed and when the screen actually turns on. Nothing extreme, but my Optimus V is nearly instantaneous in that aspect. I don't know if anything can be done to improve this, (and i'm SO glad that annoying flickering of the screen is gone) but this is still so much better than stock! Thanks TG!
TheBritton
Resident Galaxy Cat
No 3G data drops!! Thanks Tickerguy!!
Also, just want to say I love the softkey backlight. It was so nice watching movies at night without them shining so bright.
Also, just want to say I love the softkey backlight. It was so nice watching movies at night without them shining so bright.
TheBritton
Resident Galaxy Cat
@tickerguy...
no data drops as of yet!and my 3g is alot faster too... I will run that 3g thing in terminal emulator when I get home from school and give you the news at the end of the night.
Yes.. how is that even possible? I thought data speeds based on location and the network and couldn't exactly be improved through coding. As I posted earlier, my data speeds averaged around 128kbps and peaked in upwards of 250kbps with downloads not even reaching 100kbps.
I did a speed test this morning and I am at 1.5mbps download and 600kbps upload! How?
digi7alph0enix
Newbie
No data drops for me yet but I did get my first reboot on the beta build this morning. My alarm went off and I snoozed it but before it went off again I woke up and started to unlock the phone. Midway through the unlock swipe the alarm went off and rebooted the phone. The Motorola logo never showed up during the reboot though just the cm7 animation and the reboot took only a few seconds. I've also noticed that the gingerbread keyboard doesn't seem as responsive to me anymore and sometimes the screen taps register in a totally different place than I actually touch. I haven't had these issues with your previous builds and I'm still using the same apps as before so I'm not sure what could be causing them.
SamuraiFox18
Android Enthusiast
No data drops here. I even sent myself 3 text messages and got them in less then 10 seconds. Keep up the good work.
bobloadmire
Android Enthusiast
This shits on fire! even my wifi seems to be behaving better, faster connects and jumping from ap to ap at work.
frdmspoplr
Well-Known Member
Anyone have a recommendation on which V6 Supercharger setting to use?
Thanks KD for the update!
Does anyone have issue with their camera? When I use the back camera, I have to use the NO Focus option rather than Auto Focus...otherwise, the pic comes out blurry. Regarding taking a video, when I switch it to video...the screen is blurry. The video results are blurry as well. This has been happening even on prior updates...
On every update, I clear dav / battery / cache / and format all...so is a clean install.
Any ideas? TIA
Does anyone have issue with their camera? When I use the back camera, I have to use the NO Focus option rather than Auto Focus...otherwise, the pic comes out blurry. Regarding taking a video, when I switch it to video...the screen is blurry. The video results are blurry as well. This has been happening even on prior updates...
On every update, I clear dav / battery / cache / and format all...so is a clean install.
Any ideas? TIA
omgwtfmason
Newbie
You could just have a bad camera, the first Triumph I bought I had to exchange because every picture I took was blurry. Does this happen on stock too? If it does, I'd call VM and get a replacement..
TheBritton
Resident Galaxy Cat
I am testing mine out at the radio station I work at (several AP's throughout) and I can say the same for me as well. Also, thanks Tickerguy for the memory management enhancements. 100MB free RAM at all times and the phone is much snappier.
frdmspoplr
Well-Known Member
Between Ticker's memory tweaks and running the V6 Supercharger, I've got GO Launcher running just as smoothly as LauncherPro. Before, my calendar widget would cause it too lag really badly.
boomer_jmoore
Android Enthusiast
I got a question. I've read somewhere on this thread that they used setcpu to put the profile for screen off at high 245 and its set at smartass, an they got like 24 hours or more of battery life by barely browsing the internet, texting occasionally and listening to music throughout the day. My battery widget says I have 26 hours left when its at 100% full. I can get by at least 8 hours a day. Is wiping the battery in recovery necessary? I've never done it since I flashed this phone quite a few builds ago. I just want to get by the day in one charge. And yes with this build its lasted longer than stock. Keep it up Ticker! Your work is greatly appreciated.
Also yea I have the governor on smartass. I text occasionally, listen to music and barely browse the internet. I even have a profile in setcpu for the screen off to smartass and high 245. Thanks peeps
Also yea I have the governor on smartass. I text occasionally, listen to music and barely browse the internet. I even have a profile in setcpu for the screen off to smartass and high 245. Thanks peeps
TheBritton
Resident Galaxy Cat
Technically, there is absolutely NO need for a screen off setting if you are using the smartassv2 governor. The Smartassv2 governor automatically locks at your minimum CPU speed at screen off. That is the feature of it.
Anyone else, please correct me if I am understanding this wrong.
What I have done to gain battery life is lower my minimum CPU speed to 122mhz and set the "Screen Off" profile for the conservative governor min122 max245 that allows the CPU to idle at 122mhz when the screen is off but with the ability to increase to 245mhz to wake it up .. If you lock the CPU at anything lower than 245mhz during screen off you will have alot of problems waking up the phone. I have gained alot of battery life by lowering the CPU minimum to 122mhz but be careful because Smartassv2 will lock the CPU at that minimum by default if you don't have the screen off profile to something other than smartass.
lifeblows10
Android Enthusiast
Use SetCPU to drop the min to 122, and use smartassV2 as the governor. If you don't let it throttle all the way down to 122, you won't get the best performance with the best battery life.
digi7alph0enix
Newbie
Minor update- My phone seems to have dropped the data connection because the icons turned white but I opened the browser and it worked just fine. The icons turned green again a minute or so later so it seems your fix is working.
lifeblows10
Android Enthusiast
I have always had it set to SmartassV2 and Min at 122, Max at 1024 and have had 0 problems. Even if I have Spotify running with another app when I shut off the screen it pops back to life with no problem at all.
I just thought I would throw my 2 cents out there. Like britton1981 and many others have stated: "If you want the better battery life, it is a must to use Smartassv2." I say: "If you want the best, use smartassV2 and 122 as the min."
TheBritton
Resident Galaxy Cat
Thank you for that
I have not tried to use Smartassv2 with the 122mhz minimum since the 10/2 build so I will have to try it again. In the past, it would either take 30 seconds to wake up or not wake up at all. That is why I am now utilizing a screen off profile with a 122mhz min and 245mhz max with conservative governor.I will re-attempt the Smartassv2 on standby with 122mhz min per your suggestion.
What is so nice about the Smartassv2 governor is that there is NO need for SetCPU's screen off profile. Smartassv2 automatically locks at your set minimum during standby. If one has no problems with locking at that minimum during standby than I also agree in recommending that to anyone wanting to save battery life
I can say that so far every time I have gone to use data on my phone it is working and I always get notified of my incoming e-mails unlike before your latest update where I would have to cycle the data almost every time I pulled the phone out of my pocket.
Thanks for the great fix, I have had this problem on every VM phone I have had, the intercept and the optimus
Thanks for the great fix, I have had this problem on every VM phone I have had, the intercept and the optimus
lifeblows10
Android Enthusiast
Thank you for that
I will re-attempt the Smartassv2 on standby with 122mhz min per your suggestion.
What is so nice about the Smartassv2 governor is that there is NO need for SetCPU's screen off profile. Smartassv2 automatically locks at your set minimum during standby. If one has no problems with locking at that minimum during standby than I also agree in recommending that to anyone wanting to save battery life
I'm hoping it works for you just as it has me.