yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] morfic:
After adding the GPIO save/restore patch to TEUV build on 16/11 i started to get reports of unresponsive touch screens after the power button woke up the device, SoD and apparent increased drain with screen on (when in use)

They did report improved screen off battery drain however.

I'm working on my G2x kernel, so i have that with me at work and thus can not add any personal use experience of my own. It idles just fine with only wifi on, but no radio (SIM removed), laying on my desk. The drain seems higher than it used to be pre deep idle iirc, but has improved over the previous deep idle revisions.

I don't have enough use data in this state to call those hard facts, it's a subjective evaluation.
[Nexus S Android Development] caliban2:
I'm running 259 perfectly fine since i did a wipe and stopped using titanium backup of apps (just guessing, but i think it could be the gapps not playing nicely). Had fc's and freezes before with backups. Now it's up for 16 hours. Happy camper here.

Ezekeel, 1.7 did it!!! 3% batt-loss overnight. :)

Lazy, didle, Max_CPU on, no oc, all voltages -25mV.

Finally. If you remember, i was the one complaining when 1.2 came out. :D now starting my day, let's see how it behaves.
[Nexus S Android Development] 1PATRIK:
So far so good :)
[Nexus S Android Development] AndiTails:
1.7 BFS working great here, too.

Nexus MV 11.08 ROM.

Voltages -15mV.

I flashed 1.7 when my battery was really low (5%) but on charge, and when the phone booted back up (1 min later, that's all!), the phone was at 36%... Bit of a weird jump?

I dropped back to recovery, reset the battery stats and left it on charge overnight.

Was surprised to see my phone at 100% battery this morning which it said it achieved by 2.14am... But whilst using the phone still on the charger, it dropped to 98% before I took it off the charger and went to work.

And yet, I have BLX set to 96..?

I'm sure it'll settle down now I've reset the stats - but a little bit strange!
[Nexus S Android Development] caliban2:
You can only adjust voltage in 25mV-steps.

Regarding batt:

All "normal", you get the same behaviour with stockrom. Blx is just a cosmetic fix, charging-behaviour itself isn't changed. And it's not included in glados anyway.
[Nexus S Android Development] yaronyud:
i found a bug...

whenever i uninstall app's using "leatest app installed" it sais it uninstall it then loading and than boom restart 4th time in a row in less than 5 minuts
[Nexus S Android Development] endursa:
sounds more like a bug with your rom, than the kernel, i wouldn't know why the kernel shoud interfere with a software feature like that!
[Nexus S Android Development] AndiTails:
Ah, thank you. I have dropped another 10mV then ;)
[Nexus S Android Development] moinsheriff:
Went to sleep and it dropped the signal.. Never happened before.. This is the first time. And battery started draining
[Nexus S Android Development] franciscofranco:
Like the user above me I lost my signal as well. First with Oxygen then I thought it would be nice to try with some other rom so I flashed Devnull, completely fresh install. I went to bed, plugged in my charger and when I woke up 2/3 hours later I was with "No service" . I had to reboot, then disabled deep_idle and changed to conservative and it's been fine for 5 hours without any issues. I have a i9023 btw.
[Nexus S Android Development] FloHimself:
What device and radio are you using?

What radio are you using?
[Nexus S Android Development] franciscofranco:
KD1 because it gave me better results than KF1.
[Nexus S Android Development] moinsheriff:
I9020xxkd1
[Nexus S Android Development] FloHimself:
You both seem to run roms > 2.3.4 (GRJ22) and should use the KF1 radio.
[Nexus S Android Development] franciscofranco:
No, I use 2.3.5. I will try KF1 again.
[Nexus S Android Development] FloHimself:
No? Yes! 2.3.5 (GRJ90) > 2.3.4 (GRJ22)
[Nexus S Android Development] FloHimself:
Ezekeel, the kernel seems to work nicely with Google Music here.
[Nexus S Android Development] y3mita:
hmmm.... same thing happened to me last night I lost connection for a while.... reboot fixed it! And keeping lazy governor UV -25 min-max: 100 - 1000 is not doing a good job! :( A couple of reboots and freezes! :((

Fresh install of Oxygen 2.3.2 and Glados CFS 1.7

I reverted back to Franco's latest to try and with same settings I also experimented two freezes. So I had changed governor to Conservative keeping the same voltages (-25) Min- Max: 100-1000 and see what happens!

PS. I also have KD1 radio been using it for about a week now. I had KB3 before.
[Nexus S Android Development] franciscofranco:
Yes, I misread the > character. Just flashed back KF1, lets see what happens now.
[Nexus S Android Development] caliban2:
Oh boy, i better hold on to this 1.7 then. :D

stable, GREAT batt-life and no issues at all so far.

PS:

Fast too. Antutu @ performance-gov, no overclock:
[Nexus S Android Development] phone_user:
It is not a matter for radio. Alternately, I flashed franco, GLaDOS and SG. For my own part, I did not lost the signal but got 6 radio-dumps on SD. :confused: Now I am using SG-cpuidle backport version (17112011) for test.

device : 9020

rom : GPA19 23-10-11

radio : KC1
[Nexus S Android Development] y3mita:
Yeah I saw that other version where cpu idle backport is used instead! Might do the same and test that.
[Nexus S Android Development] coloxim:
With kf1 no issue ..good battery life..with extra UV..and without idle..ill try with idle too..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] franciscofranco:
No issues yet with KF1 for me.
[Nexus S Android Development] Mariusrapi:
had problems with the wifi connection. My nexus couldn't connect, or better, couldn't keep the connection to my house's wifi for more than 2-3 minutes. It was connected, and then disconnected... back and forth. Until i had to go back to matr1x.

Anyhow, it was doing great! at 1 ghz i got 200 quadrant points more than before! something around 2800...
[Nexus S Android Development] HeavenlyWinds:
Are you using bfs version? Try cfs and tell me how it goes.
[Nexus S Android Development] Ezekeel:
Tested GLaDOS V1.7 the entire day while on-the-go and made some additional tests later at home and the battery runtime really is phenomenal with DEEP IDLE finally working as intended. I experienced no drops of the mobile data connection, but from time to time I lost connection to the Google servers (icon turned white). The WiFi works fine for me with no lost connections. I did have some trouble with the touchkey backlights reactivating on touch while the device should be in SLEEP and I will look into it.
[Nexus S Android Development] asb123:
I also was/am experiencing mobile data loss / text messages not being sent or received until reboot
[Nexus S Android Development] supercluver:
I've been using 1.7 since 6 pm last night, so not quite 24 hours. It seemed awesome last night already, and I've had no problems such as drop of mobile data or wifi or anything like that. I charged overnight and on my way into work today (got to 95%). Unplugged and really haven't touched the phone since then, 1 quick call for less than 5 minutes. Screen on time of about 15 minutes. Just checked, and I'm at 86% still. So 8 hours and 15 minutes, and a drain of 9%. And I have poor coverage here (though I am on wifi, all but 1.5 hours of it where I was at lunch). Best I've seen ever. Stock ROM, NS4G. Running 800/100 lazy, deepidle on, UV quite a bit:

800: 1150 mv ARM, 1045 Int

400: 970 mv ARM, 1030 Int

200: 885 mv ARM, 1000 Int

100: 870 mv ARM, 950 Int
[Nexus S Android Development] raulillo88:
I'm trying this kernel and the battery life is simply the best. But after 4 or 5 hours i feel the system a little laggy. The free ram is only 35 mb and the system run slow

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] invd:
Which ROM? Which Apps are running? A little more infos might be needed.
[Nexus S Android Development] MSgtSimon:
Ezekeel, 1.7 is pure gold for me. Unplugged my phone at 8:30 this morning, I'm at 59%. I was on wifi pretty much all day, but I use my phone pretty much constantly and I have a loooot of stuff running, so this is awesome.

LiveOC 110

min 110

max 1100

deepidle on

gov ondemand
[Nexus S Android Development] mixtapes08:
Ive flash this kernel yesterday so far no hiccups what so ever... i havn't experience any bugs that been reported here..

Didle on

Cpu max freq on

Governor lazy

Live oc 110

Arm volt

1230

1180

1030

905

905

Int volt stock.

___________________________________

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] phone_user:
No radio-dump issue yet with SG-cpuidle backport version (17112011).
[Nexus S Android Development] steve.garon:
Radiodumps are highly dependant on what radio you use. Undervolting also produce more dump I find. Its true that I see more dump with deepidle on than with it off.
[Nexus S Android Development] Rem3Dy:
Love the boot animation!!!!!!"
[Nexus S Android Development] phone_user:
Thanks, I will try KF1 with deep-idle version kernel :)
[Nexus S Android Development] polobunny:
Problem similar to the one I described (touchkeys)?

I honestly have no idea what is doing it, yet. Sometimes it's fine, sometimes it's not. I posted a video though in an earlier post, along with your mods settings showing them turned off. Not sure if you're seen it, but it's a strange issue and I don't recall this happening back when I was running netarchy stuff.

I have noticed the problem does not happen when the device is plugged in, but can be there right after it's unplugged. Deep idle is off, I'm thinking it might be something with BLD even though it's off messing with BLN. I'd need some time to test out, but I'm just too busy lately. :(

Edit: I was having the issue just now, went into BLN app, turned BLN off. Turned screen off, tested, still same problem with touchkeys. Turned BLN back on, turned screen off, tested, still same problem. Back to the BLN app tested the notification with the option at the bottom, turned screen off, hammered all the keys while it was flashing, turned screen back on and quit BLN app. Turned screen off, now it's fine my keys don't light up when I press them with screen off. I'm gonna try running with BLN off for a bit and see if the problem comes back. @_@
[Nexus S Android Development] Ezekeel:
Never had any radio dumps on any release version of GLaDOS with baseband I9020XXJK8. It is quite old, but works without a hitch.

Also the occasional disconnects from the Google servers have stopped. So I guess this was most likely a temporary issue with my cellular provider data network or some trouble at Google.

I have exactly the same problems as in that video. I believe it is related to BLN and I have made some modifications to the code to prevent such issues. I will post a test kernel in a few minutes which should have this problem fixed.

Test kernel: http://www.multiupload.com/J2IULWAXRI
[Nexus S Android Development] polobunny:
Never had any dump with KB3 either. :)
[Nexus S Android Development] vis80k:
battery pratically melted overnight in my case.

Oxygen 2.3.2, deep idle enabled, deafault clock and voltage, ...

Over 5 hours it went from 95 to 23... was using franco's 1611 kernel before and just flashed glados 1.7 over it... but everone else seems to be getting great battery out of it.... my phone musy not like glados as the 1.6 test version also drained quite a alot and SODed on me...
[Nexus S Android Development] JmPTaz09:
I'm getting the touch keys lighting up if I touch them while the phone is off also... on 1.7 cfs, been running it all day, no other issues really
[Nexus S Android Development] some_random:
wow ok that some serious drain... did you take a look at battery usage? what was using up the battery the most?
[Nexus S Android Development] vis80k:
i should've checked, but having changed kernel only And nothing else, I didn't doubt that it could've been the apps....
[Nexus S Android Development] raulillo88:
i9023 + oxygen 2.3.2

Glados 1.7 cfs

Apps: Tapatalk, opera, tuenti, trillian, badoo, twitter, email .(not always at same time)

Enviado desde mi Nexus S usando Tapatalk
[Nexus S Android Development] some_random:
i would advice flashing franco's 17th and just see if you get the same results you might need to clean your init.d folder
[Nexus S Android Development] raulillo88:
How can I remove the bootsound? And where the bootsplash is saved?
[Nexus S Android Development] kfjunky:
system/media

Sound is in the poweron folder.

You will need to mount r/w to delete.

Cheers
[Nexus S Android Development] invd:
I don't know all of your apps but I would suggest trying to run the ROM and to kill all apps not used from time to time (for one day or so, just for testing). I think the ram issue depends on one of the used apps, not the kernel.
[Nexus S Android Development] raulillo88:
The kernel has the taskiller of the system and depending the kernel you can have always between 70 and 90mb or have 30 - 40 that make the system a little laggy
[Nexus S Android Development] bharadwaj1991:
I would like to add that my battery drain is also very bad. Overnight with data and wifi switched on it loses over 30%. CPU spy shows the phone is in idle.....but... still loses battery. My old x10 lost 2-5% while I slept for 8hrs. I have stock 2.3.6 running with glados 1.7 and no other modifications or tweaks. I do have the BLN on could that be a cause? My battery usage looks normal so no app is a culprit.
[Nexus S Android Development] raulillo88:
Which governor are you using? If you are using lazy, have you got enabled cpuoff maxfreq? I'm having the best battery drain since I got the phone
[Nexus S Android Development] bharadwaj1991:
Yes I am using lazy...and have no idea cpuoff maxfreq. Would I do that in SetCPU?
[Nexus S Android Development] 93ae8074:
Nope, you can't, use NSTools, they're free and you can get the program in the Market.

Cheers.
[Nexus S Android Development] matmat07:
I left the phone overnigth discharge (7.75h) and lost 13% of battery. Thing is 50% of it went into Cell standby...

Does this feels ok to you? I just can't go more than 1 day on battery, need to recharge everynigth
[Nexus S Android Development] phone_user:
Thanks for your great MODs and GLaDOS! :) How about adding "Screen Refresh rate at 65 Hz" to your kernel? (Trinity, franco, Steve Garon adopt that)
[Nexus S Android Development] franciscofranco:
Ezekeel more users are reporting gsm/data connection losses over my kernel thread too (along a few others in your kernel thread). What might be causing that?
[Nexus S Android Development] Ezekeel:
If you have problem with the touchkey backlights lighting up on touch while the screen is off, try the above test kernel.

I got about 0.5% per hour in SLEEP, so this seems too much. You should check the wakelocks.

I guess I can do that on the next release. The changes are only small.

Not having any trouble with the mobile connection. I guess it could be an issue with the baseband as well as the ROM used.
[Nexus S Android Development] franciscofranco:
Nah, I changed ROM and baseband and after my alarm went off this morning I looked and was without GSM with the No Service signal. Last time it happened after my alarm went off too.
[Nexus S Android Development] Ezekeel:
Just checked the alarm function and it does not trigger any problems on my device. Did you try the baseband in my sig?
[Nexus S Android Development] endursa:
I'm using 1.7 and I got the random backlight problem so I decided to switch Bln off, now when I go to nstools I can't switch it on again, nstools reports not supported, strange

I try the test kernel now

Sent from my Google Nexus S
[Nexus S Android Development] polobunny:
I can vouch for bln seeming to be the problem. Turned bln off past night and haven't had any problem so far. Trying the test kernel right now.
[Nexus S Android Development] 1PATRIK:
Used today BT HF for 13 hours straight. NO PROBLEMS :-P
[Nexus S Android Development] some_random:
that seems like a large amount of cell usage.. and could have something to do with the radio, what radio are you running?

---------- Post added at 03:42 AM ---------- Previous post was at 03:40 AM ----------

jk8 that seems very old? any reason your still running that and not something like kf1?
[Nexus S Android Development] phone_user:
Thanks a lot :)
[Nexus S Android Development] matmat07:
KF1, the latest one I think. But cell usage has always been like that on differend radio I think.

And so far from what I understand the wakelocks seems to be fine. I'll try airplane mode tonight..
[Nexus S Android Development] catchsomezz:
how many people set liveOC to +20% or greater? i originally had it set at +20%, but some reports of scrambled EFS folders had me back off to +15%.

corrupted EFS an isolated instance or common occurrence? what does everyone else think?
[Nexus S Android Development] raulillo88:
I don't know why do you need more than 10%. It's a great risk to gain a few performance.

Yesterday after using the phone all day at night the phone was very laagy. When I try to unlock the phone, the screen freezes a few seconds before unlock it and finally I had a reboot. U'm using the last test kernel
[Nexus S Android Development] phone_user:
GLaDOS test version battery use

deepidle enabled, lazy, live oc 110 (440~1100MHz), screenoff_maxfreq ON
[Nexus S Android Development] mixtapes08:
Ezeekel.. what is the diff between noop and deadline scheduler?

___________________________________

Device: Nexus S

Rom: Latest MIUI

Kernel: Latest GlaDos cfs

Baseband: I9023XXKD1
[Nexus S Android Development] franciscofranco:
http://lmgtfy.com/?q=deadline+and+noop
[Nexus S Android Development] some_random:
having some serious data drop issues.. I was watching a couple of movies in a row with my girlfriend probably around 5 or 6 hours so I didn't touch my phone the entire time... I did think it strange that I didn't hear it go off with an email or two.. turn it on it down from 85% to 28%!!! in 6 hours the culprit google sevices trying to check gmail but it couldn't because data was screwed up why I don't know, some insight would be very nice
[Nexus S Android Development] franciscofranco:
I've been reporting that issue and some of my kernel users report that kind of behavior as well. The best person to enlight us is Ezekeel, this goes well beyond my knowledge.
[Nexus S Android Development] matmat07:
1 night later: With airplane mode, I only lost 2% in 8.5 hour. BBS crash so I can't have a look at the wakelocks, but with only 2% lost I guess everything is fine on that side.

So, what should be my next step now?
[Nexus S Android Development] FloHimself:
You should really include rom, radio, kernel version, active apps etc. in a bug report.
[Nexus S Android Development] roshga:
It's wierd. Everybody are talking about data drop issues and all I had on that past 3 days is 1-2 freezes and that's it.

I dont oc, UV all around the place with -25 to -100 on all fields.

rom: BM's MIUI

radio: KF1

model: i9020T
[Nexus S Android Development] caliban2:
Not everybody. :)

I've been running 1.7 together with cm nightly 259 (a rom that's said to be unstable itself) absolutely flawless since they've been released.

Funny thing is that 1.7 cured the bugs for me it released for others.
[Nexus S Android Development] Ezekeel:
So far only one person in this forum reported such problems, but he said he knew others which had the same issue. As long as you have a backup of your efs partition this is nothing to worry about.

I wish I knew what causes this problem on your devices. Judging from the feedback, for the majority everything seems to be working fine. And I have not managed to see any pattern in the reports from those with problems. I guess we have to collect some more data and hope that something sticks out, because right now I cannot even say if it is an issue with the kernel, ROM, baseband, an app or maybe even just some setting.

Looks like the increased battery drain is indeed caused by the mobile connection. Do you have 3G/4G activated and live in an area with a bad reception. Something like that might cause to the baseband to have problems maintaining this connection and to have an increased battery drain. Did you test if the increased drain also happens without DEEP IDLE?

Does anyone have some feedback on the test kernel? Are the problems with BLN resolved?
[Nexus S Android Development] polobunny:
Test kernel solves my bln problem. I can see it flash on/off real quick when turning the screen off sometimes, so I gather for some reason bln status wasn't properly "dismissed" before?

Either way it works fine for me so thumbs up! :-)
[Nexus S Android Development] :
I hit myself over the head with a rod-like object, and now I feel amazing!
[Nexus S Android Development] thegtfusion:
i noticed that if I get a notification (when the phone sleeps), BLN lights up, but only the menu button lights up. anyone with the same issue?

overall great job :D

---------- Post added at 04:23 PM ---------- Previous post was at 04:22 PM ----------

i noticed that if I get a notification (when the phone sleeps), BLN lights up, but only the menu button lights up. anyone with the same issue?

overall great job :D
[Nexus S Android Development] info[]box1:
I been on it since jump st. pretty hard so I can't tell yet. In the morning I'll know.
[Nexus S Android Development] notabene:
[/COLOR]i noticed that if I get a notification (when the phone sleeps), BLN lights up, but only the menu button lights up. anyone with the same issue?

overall great job :D[/QUOTE]

Me also having this ''problem''.. don't care about it..
[Nexus S Android Development] Ezekeel:
Always note your hardware model and ROM when reporting a bug please.
[Nexus S Android Development] MultiCulti:
BLX is set to 96, am i right? but why can't i change it with NStool?

Or do you not recommend to use this tool?
[Nexus S Android Development] Ezekeel:
This kernel does not include the purely cosmetic 100% charge 'fix' and it never will except this modification would be added to the Android stock kernel in some future update. Thus the maximum value BLX will accept for the charging_limit is 96. You should be able to set that to a lower value with NStools (which I fully recommend for those users unfamiliar with init.d scripts).
[Nexus S Android Development] notabene:
i0923 + Brainmaster 1.11.4
[Nexus S Android Development] MultiCulti:
ok, thanks ... thats fine ;) ...

and i don't want to use the NStool ... i created for frankos kernel a own file in the init folder ...

so, if i want change liveoc or voltages or whatever, which file in the init folder do you recommend to use? placeholder?
[Nexus S Android Development] JmPTaz09:
Flashed on 2.3.7 rom from Drew Garen, so far no issues. Everything seems fast and smooth! Using 105% liveoc, stock voltages. Kudos, nice to see a kernel by Ezekeel!
[Nexus S Android Development] bgdxv:
I get the same on my i9023, but i find it way better looking than all the buttons lighting up :D I really like it this way
[Nexus S Android Development] Corra:
same here. stock rooted 2.3.6 i9023

Gesendet mit Tapatalk von Nexus i9023
[Nexus S Android Development] Mecid8:
are you add ext4 tweak for this kernel?
[Nexus S Android Development] MultiCulti:
ok .. perfect for now :)

live oc to 110 ... and NO BLN issue .. all lights are shinning :p

i9023 on Nexus MV 11.01
[Nexus S Android Development] Lultima:
All sounds good !!! ON DEVNULL-Sourge ...
[Nexus S Android Development] thegtfusion:
yes sorry. i have a i9023 with GPA19
[Nexus S Android Development] Ezekeel:
For those i9023 owners having trouble with BLN, please try the following test kernel and tell me if the change I made fixes it for you.

Test kernel: http://www.multiupload.com/J9SB7VXZJ7
[Nexus S Android Development] antoniouslj:
I too have the typical data problems (on stock setup, no liveoc) on CM7 w/ latest nightly.

Baseband: I9020XXKF1

EDIT: Now I'm getting loads of bootloops and not a cache wipe or fix perm will fix it. Don't know what's going on.