yashsingh1/xdaforums huggingface dataset:
[Nexus One Android Development] pershoot:
dunno. seems to be running well (rc4 and .38), over here. but i'm not hammering it.
[Nexus One Android Development] knightnz:
Excellent thanks Pershoot.

Were the RCU patches merged into 2.6.38 in the end?
[Nexus One Android Development] manicmoose:
I find that using launcherpro (plus) makes an immense difference to the laggy'ness of CM ROMs....it makes it all smoooooth again.
[Nexus One Android Development] RogerPodacter:
I use only launcher pro, which is smooth. But in general most things are not. Tapatalk threads, engadget app comments, any list of items, all scroll in chunks with lag.

And the now known one, plug in the charger with battery percent enabled in status bar, and launcher pro starts to lag badly after 20min till you unplug, or charge completes. Previous cyan ROMs temp disable battery percent when charger is plugged in, so we need to get this behavior into cyan 7 I'm trying to look thru the source to find where the change needs to be.

And running a quadrant test while plugged in with percent enabled, scores drop to 900. There's definitely a performance conflict with it. After 1 hour of charging, the process called status bar has been pegged at 10% CPU usage the entire time. Charging with percent disabled stops this from happening. It needs to automatically disable when plugged in.
[Nexus One Android Development] Spakainz:
This morning the phone won't wake up, had to take off battery... The phone was left with wall charger pluged in.
[Nexus One Android Development] pershoot:
Pls post logs.

Thx.
[Nexus One Android Development] fuske:
Great battery life on this kernel! Benchmarks are not as good.. Smoothness and speed are great so..

Used IR's kernel the past months but i switched back to Pershoots now!

Thnks!
[Nexus One Android Development] elban:
I've been using all the CM7 RCs with stock kernel, IR, redstar etc. and constantly getting 1400 in quadrant without overclock, up to 1600 with.

The system is smooth, very fast and responsive and I'm using the stock ADW launcher.

I guess you have some widget/application that's slowing down because for me CM7 is lightning fast, much faster than stock froyo.
[Nexus One Android Development] oo0:
maybe possible to make another version without AudioBoost if you don't want to remove it. anyway for many devices even adjusted AudioBoost will be too loud.
[Nexus One Android Development] mynameisjon:
phone just randomly rebooted twice in five minutes... is there anything I can look for in regards to the log?
[Nexus One Android Development] djmcnz:
adb pull /proc/last_kmsg
[Nexus One Android Development] mynameisjon:
pulled.. here it is.. I have no idea how to read it though...
[Nexus One Android Development] pershoot:
the kernel did not fault/panic. looks clean from quick glance (aside from the i2c xfer errors at startup, which were already there). i see no stack traces.

[ 4724.998016] Restarting Linux version 2.6.38.2-cyanogenmod+ (root@pershoot-ubuntu) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #1 PREEMPT Wed Mar 30 20:09:40 EDT 2011

[ 4724.998077]

No errors detected
[Nexus One Android Development] mynameisjon:
I'm sorry to be bothering you, but what would be causing it to restart like that?
[Nexus One Android Development] pershoot:
are you getting a soft reset (back to animation) or a hard reboot (back to X)? i didnt see a fault in the kernel logs you sent, so i assume soft reset?

if soft, check logcat, and then track back and see what you have changed (if any).

see if there is a newer nightly available and flash that. this may have a resolution to your current issue (you can check twitter.com/cmsrc for changes).
[Nexus One Android Development] RogerPodacter:
that is too weird, i will have to try IR kernel again. i dont think we've seen anyone hitting 1600 on cm7 but i could be wrong...
[Nexus One Android Development] ch33kybutt:
Well on QuadStd I regularly get 1500+ @998Hz & 1600+ @1113Hz. But I tend to have little faith in so-called 3 minute benchmarking.
[Nexus One Android Development] mynameisjon:
full on hard reboot to the X...
[Nexus One Android Development] mynameisjon:
not sure what just happened but I couldn't wake my phone. I've attached the logs that I pulled from recovery. had to pull the battery to reboot
[Nexus One Android Development] djmcnz:
@pershoot:

Just for my edification, we would see "panic" still in the kernel logs if it fell over or has the nomenclature changed? Just so I can help keep noise out of this thread.

And thanks for the new Nexus kernel, I've always preferred your work and am glad to be back. No problems so far.
[Nexus One Android Development] laslow:
Not sure what's up, whether it's the phone, the kernel or the build of CM7 I'm using, but after flashing the .38.2 kernel my N1 has been hard locking with the screen off. Can't receive calls, can't power off with the power button - all I can do is pop the battery out and reinsert it, then power on. No /proc/last_kmsg, either.

Gonna roll back to the stock kernel and test that for a few days and see if the same thing happens.
[Nexus One Android Development] mynameisjon:
same thing happened to me.
[Nexus One Android Development] fcisco13:
I got this one time

N1
[Nexus One Android Development] pershoot:
ill loook in to it.

i cant reproduce it on my end.

i dont have a SIM in, so the radio isn't enabled.
[Nexus One Android Development] laslow:
Rolled back to an official CM nightly - no issue. Flashed this kernel - random locks with the screen off. Reflashed one of my own builds without the .38.2 kernel - everything is fine. Very annoying that there's no /proc/last_kmsg to help out with.
[Nexus One Android Development] djmcnz:
When it locks, do you have adb or console access?
[Nexus One Android Development] laslow:
No adb access. On appearance, the phone might actually be off as I can't get anything out of it when it's in that state. The only way to get it back up-and-running is to pull the battery, then boot it again. The delay between boot and it locking up is anywhere from 2 to 6 hours.
[Nexus One Android Development] kmalinich:
Mine hard locked two nights in a row after charging all night. Had to battery pull in the morning. Also had a random reboot. But... the BFS scheduler makes the phone FLY!
[Nexus One Android Development] dnichols4:
Are you using DT a2sd? If so, which version?

I had the same issues with 2.7.5.3b04, but switched to the modified 2.7.5.2 and haven't had any issues since.
[Nexus One Android Development] laslow:
No A2SD.

10chars...
[Nexus One Android Development] pershoot:
BFS isn't in here.
[Nexus One Android Development] pershoot:
for those receiving the inability to wake, please test:

http://droidbasement.com/nexus/kern..._2638.2_gb-oc-uv-xtra-btn-aud-ram-neon_fp.zip

pls report back.

thx.
[Nexus One Android Development] kmalinich:
Oh. hmm. well, the kernel still rocks. fastest i've used.

EDIT: I'm testing the one you just posted now, will report results tomorrow.
[Nexus One Android Development] ocujos:
I've noticed that the call quality is much better than the stock kernel. Also, the earpiece volume is noticeably louder than the IR kernel.

I charge my phone every night (all night) and after first night still no lockups (initial release, not the updated one).

As observed by others, it's not the fastest kernel in Quadrant, but it's very responsive and battery friendly.

Keep up the good work Pershoot!
[Nexus One Android Development] mynameisjon:
so far so good.. keeping my fingers crossed.
[Nexus One Android Development] fcisco13:
Testing also.

N1
[Nexus One Android Development] Chosen_on184:
Quite funny experience with that test kernel. So had a lock up and decided to try out the test one .. Flashed and it booted up fine and 2 minutes later went to wake the phone and nothing .. Locked up ...

Will continue testing ..
[Nexus One Android Development] pershoot:
Pls post logs, otherwise im taking guesses.

Thx.
[Nexus One Android Development] Chosen_on184:
At work so unfortunately no logs. :( will keep a eye on it when i get home though and keep it hooked up and see if i can catch anything
[Nexus One Android Development] pershoot:
any more inabilities to wakeup?
[Nexus One Android Development] :
Had the same lock after a night of charging. Killed my alarm. Thankfuly I made it to class on time.

Didn't grab a log though...
[Nexus One Android Development] pershoot:
pls grab some logs if u can.

thx.
[Nexus One Android Development] mynameisjon:
Had my phone turned on through the night and it woke up on command.
[Nexus One Android Development] laslow:
Using the updated kernel posted in http://xdaforums.com/showpost.php?p=12658091&postcount=72, and no hard locks for me. Whatever you did seems to have done the trick!
[Nexus One Android Development] pershoot:
cool. ill rls this then a bit later.

unless i get logs from any others who are still receiving the issue (which is related to the kernel).
[Nexus One Android Development] laslow:
I have to say, too, that the battery life on this kernel is amazing. I flashed the updated one yesterday, and noticed that since I took the phone off the desktop dock 7 hours ago, the battery is still at 91% (with light usage). On the stock CM kernel, the best I've been able to get is ~75% after the same amount of time.
[Nexus One Android Development] RogerPodacter:
do you guys know any values for the current draw during idle for this kernel? (sorry pershoot i havent had a chance to test this yet cause i'm testing another kernel!!) but i may have to give this one a shot. i'm seeing -5mA of idle standby current draw overnight.
[Nexus One Android Development] Chosen_on184:
Currently got it hooked up running logcat .. Will that suffice or you need a diff type of log .

Never seems to happen when phone is charging though ... Weird i know :confused:

..trackball lights up fine if i had a notification there already ...sadly when this is happening i am at work

I will leave this till 11:30 and see if no lock up ..then i will leave it off .. if it locks up and i connect back hopefully logcat will pick it up

Using logcat console in droidappz
[Nexus One Android Development] uoY_redruM:
Think this will work on Evervolv's ROM (I'd assume so)
[Nexus One Android Development] pershoot:
Chosen,

Dmesg/last_kmsg

Pls make sure your on the test kernel.
[Nexus One Android Development] pershoot:
nexus - 2.6.38.2 - refreshed - gingerbread ; http://droidbasement.com/db-blog
[Nexus One Android Development] tribaleps:
Sorry...got it.
[Nexus One Android Development] pershoot:
refresh working out ok?
[Nexus One Android Development] djmcnz:
Yes... but no real heavy usage yet, just day-to-day stuff, a few calls, msgs, and a bit of browsing and music... probably not a good stress test.

No lock-ups.
[Nexus One Android Development] mynameisjon:
Hate to be the bearer of bad news, but had a lock up last night.

kmsg attached.
[Nexus One Android Development] pershoot:
this does not show me what ocurred (its not a log from my kernel).

after this ocurrs next time, head back to recovery and grab the last_kmsg file (if one exists).

while your at it, flash the latest nightly (clear dalvik, flash rom then refreshed kernel from this morning), then observe.

while plugged in at night, try to have adb shell cat /proc/kmsg running, so if it stalls, youll be able to snap what ocurred.

thx.
[Nexus One Android Development] mynameisjon:
Will do that tonight.. at work..

I have this nagging suspicion its the latest nighlty cuz I just hardlocked on the old fix kernel that ran fine the previous nightly
[Nexus One Android Development] pershoot:
i just built fresh from the cm7 repo, for passion. i still can't reproduce this issue.

on rc4, lasted about ~3.5-4 days on idle before it shutoff.

ill put a SIM in the nexus and run with it if it persists for you, to try and reproduce the issue (to see if there is something related there).

please make sure to be on the refresh for re-testing, and after updating/flashing clean (i.e. clearing dalvik, flashing.. etc.).

thx.
[Nexus One Android Development] mynameisjon:
okay I've flashed the latest of fits morningly, and wiped cache + dalvik and flashed the refreshed kernel.

running adb shell cat /proc/kmsg.

just wondering, how do i export the captured log? Ctrl-c paste?
[Nexus One Android Development] pershoot:
Yea

......
[Nexus One Android Development] pershoot:
i see a1026 there. did you receive a call and your device went haywire?

i also see the i2c bus errored out on transfer, which would lead me to speculate that that, was the situation you just ecountered.
[Nexus One Android Development] laslow:
I wonder if this relates at all to the call wonk issue....
[Nexus One Android Development] RogerPodacter:
Looks similar to the call issue, but I don't know for sure since I haven't looked close at the other logs.

I'm running this kernel and so far no issues today.
[Nexus One Android Development] pershoot:
yea..

ill pop a SIM in there (ill try for this wknd), and try to reproduce the call issue on my device.
[Nexus One Android Development] Chosen_on184:
Here is the log i pulled .. Not sure exactly what i was suppose to be looking for so this is the whole thing.

This was while i was at work . pulled battery .. booted up ..used root explorer to pull the file from the proc folder .

hope it helps
[Nexus One Android Development] pershoot:
you have the same issue.

i2c bus gets 'stuffed up'.
[Nexus One Android Development] Chosen_on184:
Ok .. and this when it was just sitting idly no call incoming so based off that i don't think this is related to call wonk .. That seems like a whole different beast of a bug
[Nexus One Android Development] pershoot:
a1026 was active. so telephony was trying to activate/de-activate (for a call? recent call you had?).
[Nexus One Android Development] Chosen_on184:
Possibly .. ... had a recent call but it was a missed call possibly 5-10 before phone long slumber ... maybe related after all.

Any idea if you might be able to debunk and possibly fix it
[Nexus One Android Development] mynameisjon:
hmm no calls.. I was using whatsapp a lot, as well as the occasional text... phone was idle for a long while i think.. I left it for a bit, then when I looked at the cmd prompt i realised it stopped recording kmsg.
[Nexus One Android Development] kmalinich:
I've been receiving and making a lot of calls, and on the refreshed kernel, i've had no issues.
[Nexus One Android Development] pershoot:
It seems to only happen to certain devices.
[Nexus One Android Development] mynameisjon:
I read in the nightly and the dewonkificator thread that it's the dewonk app that's causing it. just to be safe i uninstalled it, as well as setcpu. so far no lock ups for the past 18 hours.
[Nexus One Android Development] pershoot:
awesome.

please let me know how things go.

if you can ride for 48hrs, this is a good sign.

setcpu should be fine to run with tho.

i'll add it to the posting, if it pans out.
[Nexus One Android Development] mynameisjon:
locked up again... no calls, just locked up 10-20 minutes after i sent a whatsapp message...
[Nexus One Android Development] pershoot:
similar issue. i dont see a1026 in this snapshot in time, but your i2c bus froze up/errored during data xfer.

[36648.9920)5] msm]i2c msmi2c.0: erRor, status c8

[37648.993682] mrm_h2c msm_i2c.0: ErroR during data xfer 48 ()5)[3'648.994110] tps65023 0%0048: Write For reg x6 dailad

Please flash off of this kernel for the interim, for your specific device.

I will try to reproduce this with my own device and a SIM in, soon'ish.

-pershoot
[Nexus One Android Development] mynameisjon:
Alright.. anything to do with the recent commit in the nightly that "fixes background data"?
[Nexus One Android Development] pershoot:
update coming in a day or so.

sorry, been busy with wrapping up the oc-uv on the gtab/zpad.
[Nexus One Android Development] RogerPodacter:
How dare you concentrate on another device! Kidding, can't wait.
[Nexus One Android Development] GarJones27:
Any chance you will incorporate your updates in the Kernel Manager app? I'm sure a lot of people could benefit from this especially people like me who love your kernels.
[Nexus One Android Development] pershoot:
sorry all, got tied up.

will def sort this beginning of this week.
[Nexus One Android Development] pershoot:
promise, i will focus on this next, for an update.

sorry for the delay!
[Nexus One Android Development] pershoot:
nexus - 2.6.38.4 - gingerbread - http://droidbasement.com/db-blog ; RM updated.
[Nexus One Android Development] Ertavarez:
this kernel work with stock gingerbread?
[Nexus One Android Development] pershoot:
it will work, but camera will not.
[Nexus One Android Development] pershoot:
how's this working out?
[Nexus One Android Development] mynameisjon:
so far so good. no lock ups, no reboots.
[Nexus One Android Development] lolobabes:
Just flashed it on my cm7 N1 wanna see its new awesomeness. Ahihihi
[Nexus One Android Development] apratomo:
Working so smooth and fluid. Great job. Thanks!
[Nexus One Android Development] phewizzo:
Best battery life ive gotten in a while. Thanks Pershoot.
[Nexus One Android Development] eug89:
Hi pershoot,

I'm using your last kernel I've downloaded yesterday through rom manager with cyanogenmod 7 and I've experienced this issue:

I was using the usb tethering on my laptop and suddenly connection dropped so I took the phone but I wasn't able to wake it. I disconnected the usb cable and the green led remained on, there was nothing to do to wake it up so I took off the battery and rebooted.

Here's the last_kmsg I've pulled after rebooting http://pastebin.com/vGAVpBA9
[Nexus One Android Development] pershoot:
i see some pm_wait fails during sleep.

ill look in to it.
[Nexus One Android Development] dyndragon:
I get a similar last_kmsg on my wife's phone. Can't wake up, have to pull battery.
[Nexus One Android Development] ratson:
same for me.
[Nexus One Android Development] pershoot:
yea.

working on this (although i can't reproduce it). i reverted a change which i had in for a long time. so may have opened up other things, which need to be amended.

ill send out a rls sometime today, and then refresh it 2-3 times after feedback.
[Nexus One Android Development] pershoot:
wont post it yet on db..

but, pls test:

http://droidbasement.com/nexus/kernels/2638/3/

pls report back, with full logs in hand.

thx.
[Nexus One Android Development] pershoot:
how does this look so far (i know it may be a bit early to tell)?
[Nexus One Android Development] dyndragon:
Sorry, I can't check until later tonight, but I will. Wife's phone, not mine...
[Nexus One Android Development] laslow:
Just flashed the test kernel you posted -- will report back tomorrow after I've had a chance to play with it.
[Nexus One Android Development] laslow:
Hmmm, still hard locking. Connected mine to my desktop dock with the screen off and the charge light didn't turn. Sadly, no last_kmsg.
[Nexus One Android Development] pershoot:
Ok ill post a refresh test.
[Nexus One Android Development] pershoot:
please test:

http://droidbasement.com/nexus/kernels/2638/test/
[Nexus One Android Development] dyndragon:
this is the last_kmsg from the kernel posted on DB. However, it doesn't appear that the log is actually from that kernel...

http://pastebin.com/TqbKeCEL

So it would appear that the problem isn't actually leaving a last_kmsg...any ideas what to do?
[Nexus One Android Development] pershoot:
please test the test kernel that i just posted (above you).

pls report back.

thx.
[Nexus One Android Development] dyndragon:
yup doing that now
[Nexus One Android Development] dyndragon:
so far so good...would have usually froze up by now while sleeping...but maybe it's because i keep waking it to check.
[Nexus One Android Development] dyndragon:
seems like it is working great! I will run this until morning, and if it wakes up in the morning without an issue, i think the problem will be fixed for me.
[Nexus One Android Development] pershoot:
nexus - 2.6.38.4 - refreshed - gingerbread - http://droidbasement.com/db-blog
[Nexus One Android Development] dyndragon:
6 hours sleeping and woke up no problems on the test kernel. I think we are good!
[Nexus One Android Development] pershoot:
Hows the battery? Similar to what it was before? Respectable?
[Nexus One Android Development] dyndragon:
I'll report back at the end of the day when the wife comes home
[Nexus One Android Development] pershoot:
How's the refresh doing?

Battery ok?

No more sleep issues?

I want to bring the change back that i reverted for the refresh but need to pick apart why some of you were getting sleep death.

Will pm a test to some of you (maybe this wknd) and well go from there.

Thx.
[Nexus One Android Development] Chosen_on184:
Well Pershoot as i have noticed the sleep/wake issue only happens when i have the dewonk app running. Once i uninstall this app no more sleep wake issues, granted the 2-3-10 second delay on incoming calls start back up again though.

Will test the test kernel when i get home over the weekend, then test it with dewonk app running and see
[Nexus One Android Development] dyndragon:
Wife just reported that she got a wake death case while at work, unfortunately. But, as the poster just noted, I do have the dewonk app installed on her phone. I have not tested without the dewonk. I will attempt to get any last_kmsg but doubt there is one...
[Nexus One Android Development] pershoot:
yea remove the dewonk app.

this nullifies the test.

i will put another test kernel with the change i reverted for the refresh and you all can test both, later on.

please leave the dewonk app uninstalled.

thx.
[Nexus One Android Development] dyndragon:
I will do my best to test this. Do you think we could reinstall the dewonk app after we get this figured out? It really helps the wife not blow a blood vessel when answering phone calls!
[Nexus One Android Development] pershoot:
you can reinstall it, but you may not need to. if you do reinstall it, you may need to flash off of the kernel.

i probably cannot attenuate for it, as it seems it is literally force kiling/purging the mic structure and reintroducing itself (from what i gather), and this may leave undesirable results (as you are receiving).
[Nexus One Android Development] superg81:
no dewonk app here,was running test kernel and it wouldnt wake. unfortunately i wasnt near a computer at the time. just giving a heads up. thanx for staying on this
[Nexus One Android Development] pershoot:
pls try to get logs.

if your by your machine have adb shell cat /proc/kmsg running.

thx.
[Nexus One Android Development] superg81:
i will try. im usually at work when this happens. no access from there. :(
[Nexus One Android Development] pershoot:
ill work through this, this wknd, reverting/mergin few things, and send out tests.
[Nexus One Android Development] superg81:
it seems to be completely random, the test kernel was doing well, no issues at all. i hadnt touched my phone for about an hour and went to wake and it wouldnt. earlier this morning,i left it alone for atleast 3 hours and it woke right up.im not running any a2sd,dewonk,or anything odd. look forward to testing new kernels. thanx
[Nexus One Android Development] dyndragon:
testing the test kernel now, no dewonker app. will report back
[Nexus One Android Development] pershoot:
pls reply in pm.

thx.
[Nexus One Android Development] pershoot:
nexus - 2.6.38.4 - refreshed - http://droidbasement.com/db-blog
[Nexus One Android Development] Chosen_on184:
Are you pushing the updates to Kernel Manager ?
[Nexus One Android Development] pershoot:
im not in there at the moment.
[Nexus One Android Development] mynameisjon:
i know battery life is one of those things that are subjective, but the latest kernel has given me really horrible battery life. 10% drain per hour on idle with full HSPA reception.

The previous versions (the one that I had to flash off) gave me 2% per hour.

Granted in the 10 hours I've been on (till shut down), the phone didn't lock up.

Was there a change to the way power is managed?
[Nexus One Android Development] pershoot:
Calibrate your battery using the app, and then report back.
[Nexus One Android Development] phewizzo:
Battery life is great with the latest kernel, 13 hours of good use and phone is still at 52% good job Pershoot.