yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cjsimokat:
Tried the launcher.apk from 3.6.5 and still happening; also, tried the HTC Launcher from the original dump of Rogers Rom, but also happens with this.

Looks like its happening for me using both HTC and Google builds with any launcher.
[G1 Android Development] dwang:
Do you have a lot of widgets running that is taking up a lot memory?
[G1 Android Development] Amdathlonuk:
Bang on..........
[G1 Android Development] cjsimokat:
Nope. Used Advanced Task Launcher to kill all unneeded applications. No widgets running except for the calendar widget.
[G1 Android Development] cyanogen:
Interestingly, I found that having the battery icon and the charge meter on the lock screen actually eats battery. The reason is that the trigger fires way more often than I thought since the value fluctuates so much. There is a reason Google coded it the way they did, I guess. Some of you might hate me for this, but I've removed the battery icon and only show the percentage of charge while plugged in now. The nice layout that Stericson did is still there. I also put the provider name back in place of the battery.
[G1 Android Development] revwillie:
Me. I think you have to backup data and restore after the flash bit I keep forgetting
[G1 Android Development] pinetreehater:
Holly bat turds...that is a significant improvement.

Some things CM implements are under-the-hood changes that we don't get to enjoy. This, makes any extra battery drain very worthwhile...

However, anecdotally, this ROM seems on par with the other CM ROMs for battery drain. CM 3.9.4 wasn't...it was noticeably worse.

Without benchmarking, I would say what ever he did made a significant improvement.
[G1 Android Development] pinetreehater:
Is this for the next release? I don't see any of those changes.
[G1 Android Development] bkmo:
I think I will like it better the new way with the provider and percentage.

Can you just post the updated launcher?
[G1 Android Development] ubernicholi:
Any way to code a time until download finishes and a current download speed addon into the browser?
[G1 Android Development] Do0zman:
I don't see them either.
[G1 Android Development] bmozaffari:
Anyone got a IPSec PSK VPN working?

I'm trying VPN on 3.9.5 and can't get it working. I'm wondering if anyone else has been able to get IPSec and with PSK in particular working. I'm attaching my logcat error log.

The good news is that our app (get-a-robot-vpnc) still works with this version. :)
[G1 Android Development] c0t0d0s2:
I was going to play with this at the office tomorrow.

This leadsme to ask the next question: Where do I set settings like key lifetime, etc?

My ipsec vpn specifies things like phase 1 and phase 2 types/lifetimes and I didnt see those. I will wor with this again tomorrow and see if I can find it, but has anyone gotten an ipsec vpn working at all?
[G1 Android Development] Binary100100:
Themes Can Cause Fuel Gauge Force Close

I installed the new 3.9.5 and checked out the Fuel Gauge. Looked great Cyan. Thanks! I then used the above mentioned method of setting the colors of the text on my status bar. I edited the theme template with the colorchange program mentioned above and flashed that without making any other changes just to make sure it would work. Everything went smoothly.

I returned to the Fuel Gauge and I got a force close. Logcat here.

So although my text is a different color (white) and everything seems alright so far.

So if anyone installs a theme and get a force close on the Fuel Gauge (about phone > Battery Use) this is very likely your problem.
[G1 Android Development] drpfenderson:
I can confirm that this is a theme issue with the color-changing script. Just a warning to people with themes who get this issue.
[G1 Android Development] borodin1:
Hate you-no. A little ticked of that bunch of complainers made you take this perfectly fine mod out-yes, yes and yes. That screen was beautiful and some of us were just fine trading few minutes of battery life for that. Could you post the files needed and some basic instructions to revert to this mod in your future releases?

And finally:

[rant]

People that complain about battery life, read this!!!! You own a phone that has been known to have $hit for battery life. You can complain and analyze all you want but it is what it is. Battery life has been bad since the day this phone came out. If you want to discuss battery life -start your own thread, don't hijack this one !!!! Or better yet....get a damn spare battery, that will give you double the life, imagine that. Most people here do not want read 20+ consecutive posts about battery, then one that says "flashing now!" and 20+ more about battery, each one with a signature that lists your every asset including the phone that you had 5 years ago.​

​

​

[/rant]

Thank you Cyan for all your work, wish I could send a full beer delivery truck to compensate for all this non-sense here, but I certainly will donate enough for a 12-pack of cold ones once I get paid.
[G1 Android Development] uwonsum:
3.9.4 was very stable and I had not a single issue (absolutely zero). I Upgraded to 3.9.5 for 2 reasons; new battery use feature and terminal being pulled out of Dev tools.

Thanks again for another solid release.

Edit: Glad to see green on black is back on.
[G1 Android Development] c0t0d0s2:
Anyone else having problems reading network features with this ROM?

Many things under "Call Settings" seem to be having issues since I flashed to this rom.

Most notably:

call settings -> call forwarding

and

call settings -> additional call settings

Both seem to reliably kick out an error message every 3 out of 4 times or so.

Not sure if it's tmo having an issue right now, or the rom, but its been this way for a few hours now.
[G1 Android Development] teflon252:
any 1 notice text messages disappearing....or the send button not working?....i have even gone backwards to the STABLE rom and the problem is still prevalent considering my apps are still there after timeless wipes....
[G1 Android Development] Roger3778:
I am not able to activate bluetooth or Wifi on 3.9.2 or 3.9.5 ( havent tried the others. I have gone batch to the 'stable' version 3.6.8.1 which works fine but of course doest have the later browser and other enhancements
[G1 Android Development] MrBlueEyez:
Second that my man, you're absolutely right! Will do a donation as well, i simply love the work of Cyan...

Anyone has remarks about my compass suggestion a few pages ago?
[G1 Android Development] cyanogen:
The donut sources are missing the code for racoon (ipsec-tools). I don't know if they've made any extensive modifications to it, but I can try to build it myself. I think we might have to wait for the next drop if not. I only tested PPTP.
[G1 Android Development] scrappyabs2:
Easily wipe EXT + Data

Cyanogen,

I think this would be a great addition to your recovery image.

http://xdaforums.com/showthread.php?t=543617
[G1 Android Development] cyanogen:
The lock screen still looks pretty damn nice. I actually like it better :cool:
[G1 Android Development] Do0zman:
Mine still shows battery on lock screen

Im guessing its because i didnt wipe before i flashed though.

side note

AGREED!
[G1 Android Development] constellanation:
i prefer it gone, not because of battery issues, but rather i can see two battery icons at one time, why do i need two? ehhh that's my opinion. you know what would be cool is if there could be a picture frame widget there... maybe not...
[G1 Android Development] uwonsum:
Works for me...
[G1 Android Development] cyanogen:
I'm guessing it's because it's not released yet :rolleyes:

By the way, I'm trying out your 128/528 with 200 powersave_bias with great results. The device is still smooth and it spends much less time in the highest cpu state. I am probably going to make this the default. I was previously messing around with the "conservative" governor, but it just doesn't ramp up fast enough and the device gets choppy.
[G1 Android Development] TheGreenJester:
I'm in favor of the battery-less lock screen. The percentage is the valuable information, and I only see that screen for a second anyway.
[G1 Android Development] revwillie:
I agree. It also makes more sense from a usability perspective. The notification bar already tells you the amount of battery you have. Instead of pulling down the notification bar to see your carrier, it's reflected in the lock screen. So both items of information are immediately available when the screen is first awakened and before unlocking. I'm glad for this change.
[G1 Android Development] cyanogen:
What's the error, and can you provide a log please..

If you switch back, get us a log of when you try to enable BT or wifi please.
[G1 Android Development] Do0zman:
Sorry about that i guess i missed that. usually pretty good about reading before i post... oh well still looks good without the the battery icon by the way

I was using the browser and opened a new window(now i have two windows) at that point the phone stopped responding no "FC" and then when straight to the android boot screen and pretty much rebooted itself. I have not been able to reproduce this problem but if i do figure out what caused it ill let you know.
[G1 Android Development] pistol4413:
port power widget to 3.6.8.1

is there anyway to do this and maybe the fuel gauge? i need something fun to play with untill the next stable comes out.

Originally Posted by haykuro

add 2 different system folders into your updates, 1 contains a plethora of beastiality and the other is the real image, have it run a small binary that gets a random number, if the number is divisible by 3 it gives you bad rom

I think i was one of the poor bastards that got hit with the beastiality LMAO:D
[G1 Android Development] uwonsum:
This is good news. I was really hoping that other folks who knew how to play with these settings would have tested and confirm...I am glad you can confirm there is benefit without performance drawback. Am not sure how you have time to fix bugs, add new features and test/debug...Thanks for all the hard work.
[G1 Android Development] borodin1:
It's your rom so you can do it whichever way you want. I was just asking for some info on how to do it myself on your future roms without undoing your mods. If you could provide that once it would be great... otherwise I can talk to the XML-god (Stericson) and figure it out myself. I don't really care for big "in-your-face" T-mobile on the lockscreen and I did like that battery.

In any case.... this certainly will not be a deal breaker for anyone... I hope

Thank you for all the hard work you've put into this.
[G1 Android Development] rob.turner:
Just had the same thing happen here, only I was using the Steel Browser from the market. Its only happened once, and I haven't been able to recreate it, ironically it happened after clicking a link in this thread. Am I right in assuming they both use the same browser engine? I haven't had it happen in the stock browser, though.
[G1 Android Development] userfriendlyme:
I know its a pain but it worked for me some updates back and thats just doing a fresh reformatt of the card. Do a nandroid restore afterwards and you should be cool. Have you tried that?
[G1 Android Development] mianosm:
I've had a battery on the lock screen since JF1.5, it seems odd that now it is causing the drain....

I'm assuming this change will be effecting the services.jar for the /framework?
[G1 Android Development] dan0zone:
If you guys remember ,late last year when everyone complained bout battery life ,thats what google did ,removed the battery percentage form the lock screen some complained,but it did seem to help .... in theory with the battery percentage , animation on the lockscreen and in some themes percentage in the status bar ,,theres to many constant pegs on the battery .. so cyanogen I think your right
[G1 Android Development] ultra spikey:
I don't know about everyone else, but I'd rather sacrifice a little battery consumption for the percentage at the lockscreen. If we don't have this, people will probably end up using battery widgets to monitor battery. From my experience, those battery widgets drain the battery also, maybe even faster than the lockscreen. This is not a complaint, just my opinion.
[G1 Android Development] itp:
I know you said you wouldn't discuss it anymore, but perhaps this will be of interest to someone else. Hopefully I'm not just cluttering the thread.

I think you're too quick to dismiss 528/528. The detail you're missing (in my opinion) is that it's important to consider different use cases. For a situation where you're primarily making interactive use of the phone, I think your dead on (or working in the right direction) with your analysis of scaling min and max plus powersave_bias.

That said, 528/528 makes a _ton_ of sense where people are leaving their phone to sit quietly and do stuff every so often. If I'm leaving my phone on my desk to have twidroid wake up every so often to check mail, then the comments a while back about the difference between a modern processor's power consumption at true idle become very important -- 528/528 lets the processor do what it needs to do _fast_, and then get back to idle, which has way lower consumption even than the 128 in your approach.

I'm trying out 128/528 with 200 powersave_bias now, and the phone is very usable. I had some problems with some games, which got a bit choppy, I suspect because of the fact that the kernel is essentially employing frequency dithering. I wonder if you've noticed anything like this?

The root of the problem is, it's very hard to tune cpu scaling and power save settings for some kind of "magical" perfect values that work in all cases. Everyone uses their phone differently. I use my phone differently from day to day! There are some configurations that are generally better than others, but it's probably possible to construct usage patterns that favor many different configurations.

Unfortunately, asking people to tune their own settings is beyond most people in this audience (and it's not sane to expect them to figure it out). But I think saying "528/528 defies common sense and makes absolutely no sense if your intent is to save power" is far too simplistic and dismissive to further the conversation (which, to be fair, you don't seem interested in having).

Please take this as an attempt to engage in constructive dialog with the community in general, though. I'm really frustrated seeing so many posts that just say "you must be wrong/an idiot/too stupid to breath, because i'm not seeing the same thing you're seeing." With the exception of those posters who refuse to read anything that came before in the thread, or use the search function, I think it's important to consider a range of experiences, suggestions, and do our best to think through the options (and provide Cyanogen what information he can use, if he so chooses, to make changes).
[G1 Android Development] bkmo:
The way I am seeing the change is that the battery graphic is removed, but the percentage is still being shown. I know what a battery looks like, and really don't camp out on the lockscreen, so this is not a show stopper for me.
[G1 Android Development] cyanogen:
I think I'm going to add a very simple option in the settings app to control it. Just 3 options, performance, normal, and powersave.
[G1 Android Development] userfriendlyme:
Very well said. I guess in the long run where going to need some option setting like how a laptop is. to somewhat use power based on high low or medium usage....
[G1 Android Development] userfriendlyme:
This thread moves so fast. Perfect can't wait for the update.:D
[G1 Android Development] ScottGood:
Cyan said that the percentage will only be shown when charging. so the percentage left while on the go will not be shown.

On another note:

I like being able to see if my battery is at 15% vs 5% when the indicator is in the red, but if it's gone it's gone and nothing I can do will lmake cyan bring it back, I will have to learn how to change this look on my own.
[G1 Android Development] stellarman:
@uwonsum: I guess there is something about this that I don't yet understand. If the setup that you are proposing causes the CPU to run at 384 Mhz most of the time, why not just clock it back to 384 all the time (like it comes from T-Mo). How is this different and better. I am asking, not to challenging or argumentative, but to try to see what is going on there. Can you give me the difference in a nutshell? Thanks.
[G1 Android Development] userfriendlyme:
I honestly think seeing the battery change from green to red at like 65%made me want to throw it on the charger just to not see it red. it looked more critical then it really was to charge the phone. Im sure charging the phone more frequently has and effect on the battery as well as the battery life. Im glad to see the battery icon removed.
[G1 Android Development] ericman77:
vpn

So what is the vpn feature in wireless settings?
[G1 Android Development] aceo07:
It's to allow you to connect to a vpn server. Virtual Private Network. Only useful if you have access to a vpn. Usually for companies to provide a secure connection for their employees when working outside of the office.
[G1 Android Development] d2dthetide:
If you want the battery.... theme it. Cyan is trying to get the max from his ROM without sacrificing stability. The fastest smoothest greatest ROM and battery life is part of it. If he can find a way to improve battery life and create not only the fasted but longest running ROM well lookout cause he might start changing water into wine...oh excuse me beer. I wouldn't be surprised to see him walking on water either cause he seems to be quite the magician
[G1 Android Development] skaterA223:
help

would i have to wipe first i have cm 3.9.1 with themes so i think but not shure thanks
[G1 Android Development] borodin1:
I already regret the "big red post" because now, that I thought about it, some people may prefer longer battery life over other things. I was just getting frustrated with flipping thru 200 posts in a row about it. I'm staying with CM roms because of perfomance and if battery lasts me 6 hours but phone runs like a champ - I'm all for it. I don't even know what my battery will last me, phone is on the charger more time then not.... I've got a charger at work, home, at mom's place, in the car, couple portables (like this ) so I don't care if I waste a little battery life on some eye candy

In the end, I have no problem adding or removing things myself, I just don't want to break the stuff that Cyan adds in to the rom so I asked if he could give us a little rundown on that. And that's exactly what I said here

I wouldn't be surprised to see Cyan walk on water neither though lol
[G1 Android Development] borodin1:
Flash away w/o wiping. If you have problems (which you most likely will not) then wipe and reflash.

Good luck.
[G1 Android Development] skaterA223:
"Flash away w/o wiping. If you have problems (which you most likely will not) then wipe and reflash.

Good luck."

Hay thanks man
[G1 Android Development] sullitf:
I wipe between all rom flashes, even cyanogen's but I don't think its necessary. Since you're using a theme I'd recommend flashing the 3.9.1 update without wiping just to override any changes the theme made. After you're back to the original theme then try flashing 3.9.5 and see if it works out.

Worst case scenario is you try it and end up having to wipe and reflash. Themes can change some of the frameworks and break things, so its best to go back to the original 3.9.1 rom first. Can't guarantee that'll fix everything the theme may have done but its worth a try
[G1 Android Development] intervigil:
wifi driver revision?

I compiled my own kernel to run with 3.6.9.5 and it runs fine, however there is a problem when I go to the wifi settings. If I enable wifi from a previously disabled state, it works fine, however if I then try to disable the wifi, I can no longer disable or re-enable the wifi. I'm using the donut head revision of ti_wlan and msm kernel. I'm wondering what combination of kernel and wlan revisions you are using to get it to run on 3.6.9.5.
[G1 Android Development] andrew richardson:
I posted this earlier, but wasn't really clear on my question/suggestion.:( Since Cyan has done so much (Wonderful! :D ) work to the kernel, can we be seeing conflicts with the radio driver? It seems most people have started to complain about battery life with this rom branch, which uses alot of donut code. On some phones I have had in the past, the phone would dynamically alter the power to the radio hardware to boost a low signal, maybe it's not scaling properly now? I have noticed on my phone, if I use 3g alot at work, with good signal, it uses less power than at home with poor signal. It would be interesting to note whether the varience in power consumption between different people might be influenced by their signal strength. Just a thought to maybe suggest another possible influence to look into. I do love the work Cyan puts into his roms, he has taken our G1's so far, it's amazing!
[G1 Android Development] jklong03:
You two clones? Twins separated at birth??

Never mind, figured it out, SkaterA233 was simply replying using "cut and paste" for the quote! My bad!

Yet another reason I wish we could Delete our own posts!!
[G1 Android Development] Janis:
Lagg sufferers, f/c sys apps, I might have found something

When I flashed to 3.9.2 I got stuck on G1 screen because I had a custom userinit. I was tired of my funky lag stuff, too, so I decided to clean off and try again from scratch. I've loaded everything I had before that run in the background, and haven't noticed any lag (OK, a smidge, but barely), and so far only 1 fc on Home when I booted once. Campared to what I had, it's like a new dang phone. I see now why everyone is raving.

I did 2 things differently this cleanup/reflash:

I deleted and repartitioned my ext4 partition. Last time I just deleted everything I could see and reformatted to ext4 from ext3 (and resized) in GParted. Reformatting in GParted doesn't clean things off. I don't know if there was a hidden file, something in the lost&found or what, but if that's what helped, maybe an expert can shed some light.

I also flashed straight from RC29 instead of stopping at JF 5.1 for the Terminal Emulator and Telnet (I had it already so flashing it was easier than downloading 2 apps). I have no clue what files go into an Android ROM, but I wonder if something from the JF series got left in somehow, somewhere, out there (thank you Lenny).

Again, any expert explanation is welcome, but at least there's something for people whose system apps are force closing a lot and getting a lot of lag.

I also never enabled anyswapping on 3.9.2.

And since I had to throw a birthday party and download a bushelful of apps, I've missed two releases. It sure keeps the thread up top.

Not worth its own post: I don't think people are griping about battery, they are reconizing this as an optimization series, and want to help with optimization. I'm happy enough with 1700mAh and 3.9.2. (I didn't realize *how much* of a battery dud this phone was until I got it - you'd think my 5-inch X7501 screen, no GPS shut off, would have been worse, but it wasn't, uh, isn't. If the idea is to win over new Android users, this is an optimization that's worth some time.)

I have a question, though, couldn't a graphic get a battery level read and just use whatever it reads when it loads without using any animation? You know, like stop action film, old-style animation. Just an idea.

And thanks for the screenshot! I like the screen, it does the trick, and it's got some benefit, and an extra bonus to those of us who travel, since the carrier name isn't available afaik without a few taps.
[G1 Android Development] Ohsaka:
(Yes I read the previous 15 pages before posting)

After installing 3.9.5, it looks like compcache isnt working.

Here are the contents of my /system/sd/userinit.sh file:

#!/system/bin/sh

insmod /system/modules/lib/modules/2.6.29-cm/compcache/xvmalloc.ko;
insmod /system/modules/lib/modules/2.6.29-cm/compcache/ramzswap.ko memlimit_kb=15360 backing_swap=/dev/block/mmcblk0p3
mknod /dev/ramzswap0 b 253 0;
echo 30 > /proc/sys/vm/swappiness;
swapon /dev/ramzswap0;