yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Psych0Chimp:
Logcat's working fine for me using the instructions I posted a few posts back.

I'm on GLaDOS 2.8 still by the way, not that it should make any difference as the logger.ko module is present in 2.9 as well.

Check your /system/modules folder and make sure that logger.ko is present. If it's not there, then that's your problem...

Also make sure to check permissions and busybox.

---------- Post added at 03:22 PM ---------- Previous post was at 03:22 PM ----------

Have you checked that the log level is set to 'Verbose' so that you see all the messages?
[Nexus S Android Development] possebom:
I can load module fine, adb logcat works , but it show ONLY system messages and not app messages and system messages like a default kernel.

I need it because I am a app developer.

Thank for everybody tried help me.
[Nexus S Android Development] theAman:
This is exactly the behavior I get.
[Nexus S Android Development] AeroEchelon:
Recently flashed the test kernel coming from eugene373's speedy-5 and noticed that I get a green flash when I turn the screen on. This goes away if I turn up the brightness. However using eugene's kernel and the same brightness settings there is no green flash. I am not using any Voodoo Colors.

Does the removal of the 65fps hack have to do with this?
[Nexus S Android Development] DarkhShadow:
Change gamma hack to 2.3.3 defaults in voodoo control and it will go away

Sent from my ice cream powered Nexus S
[Nexus S Android Development] AeroEchelon:
It's not 2.3.3 by default? I never ever used Voodoo control as I said earlier.
[Nexus S Android Development] michalurban:
Title

Could anyone please explain to me the title of the thread (ie. GLaDOS V2.9 Reboot problems fixed? Try test kernel!)? Are the problems

a) fixed, OR

b) am I supposed to use the TEST KERNEL to help the author with testing the kernel?
[Nexus S Android Development] AeroEchelon:
People have reported that the TEST kernel hasn't had any reboots so far with phone calls ... but it hasn't been tested that heavily yet to confirm.
[Nexus S Android Development] michalurban:
Kernel

So, should I use the TEST or v2.9 kernel? I know I can use any of them, but ... :)
[Nexus S Android Development] nathanson666:
It is not 2.3.3 by default. You have to install the vodoo app from the market and change the v1 gamma back to default settings.
[Nexus S Android Development] gotjazz:
Okay so meanwhile I have had some reboots on the test kernel too. Way less than on 2.9 though.
[Nexus S Android Development] nathanson666:
What are your settings?
[Nexus S Android Development] djjonastybe:
Ezekeel can you add lulzactive governor???

Lulzactive improved my battery life enormously compared to lazy. I think this one can easily be integrated without any changes... It already has something like a screen off frequency.

Your fans would be very happy!
[Nexus S Android Development] gotjazz:
Bln, bld, deep idle and all that off. 100/1000 lazy
[Nexus S Android Development] reapsor:
With v2.9 cfs my phone flies like an eagle!

I using it since release now and had no Reboots, SOD's or something else, also getting a good battery life.

Here are my settings using an init.d script.

Deep_Idle: OFF

BLN: OFF

Touchwake: OFF

BLD: ON

No Live_Oc

Frequency's: 100/1000 MHz

Governor: conservative

Love it! :D
[Nexus S Android Development] tchaari:
and smartassV2 too :) but let him fix find the cause of the reboots before ;)
[Nexus S Android Development] caliban2:
Stockrom and 2.9 cfs (not the test version) - I love it! Perfectly stable since release.

BLN: on

Touchwake: on / 15 sec

Governor: lazy

CPU: 100-1000

Didle: on

Max freq: on

Rest is stock.
[Nexus S Android Development] Ezekeel:
Do you also have reboots with others kernels? Maybe try a clean ROM install (format /system and /boot and reset to factory before) and only install the bare minimum of apps you really really need. I read reports before that reboots were indeed caused by a misbehaving app. So far you are the only one having serious issues while the problems for other users that had issues before seem to all have been fixed. This suggests the problem is not with the kernel (anymore).

I will not integrate any new stuff until I have the cause for reboot problems tracked down. I will look into lulzactive, but I definitely will not include smartass since it is an inefficient governor.
[Nexus S Android Development] nexusphone:
On test version, that reboot problem has not happened

btw, your wheatley only for GN? :)
[Nexus S Android Development] gotjazz:
Will do. Meanwhile: updated to the latest aosp+ and reflashed the test kernel before going to bed. No reboot overnight.
[Nexus S Android Development] endursa:
ezekeel i'm sorry to disappoint you, but, as I was walking to my lecture I was listening to music and all of a sudden I had a freeze, with the last second of music looping forever. only a battery pull helped :-(

my settings:

200/1000, lazy(max freq on), 100%oc, no uv, bln on(no blink), bld on, deep idle on, I don't know why I had this all of a sudden... had a phone call for 15 in the morning without any troubles!
[Nexus S Android Development] eezak:
Same here using test version had a freeze while listening to music,

phone is i9023

100/1000, lazy, 100%oc, no uv, bln off, bld on, deep idle on
[Nexus S Android Development] tchaari:
I don't know if this will help you but try to turn deep idle off just to check if it is the cause of freezing when screen is off. if it doesn't help, please try to change the min frequency to 400 Mhz. Just to try helping in finding the cause of this issue...
[Nexus S Android Development] caliban2:
Are you by any chance using cyanogen music-app?

I got full system-freezes with it, doesn't happen with stock-app and winamp.
[Nexus S Android Development] eezak:
Nope, I am using PowerAmp
[Nexus S Android Development] caliban2:
So, are you able to reproduce it with another app?
[Nexus S Android Development] shockem:
Can someone please post a mirror? I have been waiting for days and no one has provided one :(
[Nexus S Android Development] IIIV:
I've been playing hours of music (using PowerAmp) with the latest v2.9 with Deep Idle: ON and never had any issues.

I use ondemand. So, my speculation would be the Lazy governor that's causing the freeze.
[Nexus S Android Development] att1cus:
-removed outdated link-
[Nexus S Android Development] Uni7:
Getting reboots whilst idling with deep idle on 2.9 test kernel with ondemand.

Also when playing music via PowerAmp, get the stuttering phone freeze (only fixable by battery pull) that the guy described before.
[Nexus S Android Development] gotjazz:
2.9 is not the test kernel if I'm not mistaken.
[Nexus S Android Development] IIIV:
v2.9 test kernel: http://xdaforums.com/showthread.php?p=21703959#post21703959
[Nexus S Android Development] shubu000:
finally had a reboot during call on 56fps test kernel

NO liveOC... i9020T on cm9 1.1

ondemand sampling size3 15000 uplimit 98

would the reboot be related to sampling size? since lazy is around 15000 from memory?
[Nexus S Android Development] aLNG:
as far as i remember i started get reboot while calling when updating to v2.5

it must be something in v2.5 that cause this thing
[Nexus S Android Development] endursa:
nop stock ics music app
[Nexus S Android Development] nathanson666:
Charging icon while not plugged in

I'm not sure if this is a kernel issue but this morning, after I unplugged my phone, the battery charging icon remained. The battery statistics also showed the phone as charging (the charge level went down though.)

It only went away after a reboot.
[Nexus S Android Development] Pitel:
Music freeze

I can confirm the freeze while listening to music. I have very similar settings, and while I was listening to music, while the phone being plugged in charger, I suddenly wasn't able to wake the phone up. The buttons are lit, but nothing on the screen. The music was still playing playing when I tried to wake it up, but now, after I disconnected everything to plug it to usb and acquire logcat, the sound is gone. So I can't confirm nor reject the sound repeating behaviour, maybe it happened between reconnecting the phone. Also, logcat is dead, adb says "waiting for device", I'll tryu to acquire last kmsg after reboot by battery pull...

Note it happened after changing min freq from 200 to 400 MHz.

EDIT: There is no last_kmsg in proc, so I can't provide more information.

Anyway, my setting are:

dimmer off

bln on (timeout 0, blink off)

charge limit 96

touchwake off

deadline scheduler

lazy governor

cpu freqs: 200/1000 (happened after changing to 400/1000)

oc 100

deep idle on (and working, getting lot of top off numbers)

screen off max freq on

default voltages

ROM: CM9 1.1
[Nexus S Android Development] gotjazz:
well since reflashing rom and kernel yesterday I've had no reboots - about 24 hours now. I later realized I had flashed older gapps earlier - maybe that was causing my issues.

anyway: no reboots since yesterday with all optional mods off 100/1000 on demand.

Come to think of it - i was using lazy earlier - will give that a test day tomorrow
[Nexus S Android Development] aLNG:
test also calling some1 for about 2-3 minits or getting called
[Nexus S Android Development] IIIV:
It finally happened to my I9020T. Had a SoD while playing music (PowerAmp) while screen is off. I'm currently using v2.9 / BLN / CFS / ondemand / 120% / 240-960 MHz / Deep Idle: ON.

I used the same settings above with the non-65fps v2.8+ test kernel and didn't have any reboot or SoD for more than a week of extensive use. So, I'm going to flash back for now.
[Nexus S Android Development] gotjazz:
will do but I've never had reboots during calls even before sqitching from 2.9 to the test kernel
[Nexus S Android Development] Petarsson:
have no problems with calling or listening to music so far...

but BLN is not working correctly. it starts blinking, but does not stop when i unlock the phone. it simply blinks on...

anyone got this issue? i am using nstools for BLN-settings.

setup: ICS stock with glados 2.9 bfs-version.
[Nexus S Android Development] CrackDaddy:
Can we have another mirror for the v2.9 cfs version please!? I'm getting: Attention! Connection limit has been exhausted for your IP address! Please try in 1:25 hour(s). Even after closing & reopening browser :confused:Thnx in advance!
[Nexus S Android Development] djjonastybe:
v2.9 CFS

Here it is mate. My link will be deleted when 2.10 comes out or at Ezekeel's request.
[Nexus S Android Development] CrackDaddy:
Cheers for that djjonastybe, downloading now ;)
[Nexus S Android Development] Ezekeel:
Since some people are still having reboot trouble I have compiled another test kernel. This one is based on V2.9 and has the V2.4 kernel config (like the previous test kernel) and additionally all optimizing Makefile flags removed.

Download: http://depositfiles.com/files/l0681ax7x
[Nexus S Android Development] R-TEAM:
Hi,

haved with the first 2.9 testkernel reboot at DeepIdle=ON too ... (this time after 4 min music playing..) and try now the testkernel2 ... with deepidle=OFF, 2.9 runs very stable and nice and i hope the bug will be squashed down very hard ;)

Have Ultimate ICS V4 as ROM and this have the BT fix not (so not real deepidle is reached ...) but this should make no problem .. or ?

Regards

R-TEAM
[Nexus S Android Development] phone_user:
Thanks :)

---------- Post added at 12:53 PM ---------- Previous post was at 12:42 PM ----------

reboot after calling

last_kmsg
[Nexus S Android Development] CrackDaddy:
Ok, had to battery pull this morning after leaving on charge over night with v2.9 cfs (not test!) version!

Settings are:

bln=on (blink=on)

bld=on

no live-oc

200mhz/1200mhz

ondemard

deepidle=on

:(
[Nexus S Android Development] caliban2:
Same here, same kernel. Problem is: I have 3 possible causes...

- kernel (would be the first since 2.6 or 2.7)

- g-alarm (hadn't used it in a while, activated last night)

- youtube-app (watched some videos before sleep until suddenly the sys got a bit slow and video wasn't shown anymore, just sound; had that before weeks ago and decided not to restart this time, see if sys sorts itself out overnight)

My bet is on YouTube incident, but who knows... no last kmesg and of course I didn't enable logging after everything was fine for several versions... ^^
[Nexus S Android Development] CrackDaddy:
Can I ask what your settings are? as it's usually rom or kernel related!
[Nexus S Android Development] caliban2:
http://xdaforums.com/showthread.php?p=21781485
[Nexus S Android Development] CrackDaddy:
Hmm strange, seeing that you had max frequency set to on! Gonna leave my settings as they are for now apart from maybe changing from 1200mhz-1000mhz, and see if the problem recreates itself!
[Nexus S Android Development] caliban2:
I've been running these settings stable for weeks now, so I'm not ready to blame the kernel yet. Funny thing is, 2.3 was the first stable for me, next versions rebooted in standby again. And from 2.6 or 2.7 onwards I'm fine again. So I'm not gonna try this new test kernel based on 2.4. ^^
[Nexus S Android Development] CrackDaddy:
Well the clue's in the name "test", & it seems from what I've been reading that the problems have mainly been "reboots", & not SOD's in standby whilst playing music with the test version! We seem to have different circumstances, (SOD's) whilst charging with the v2.9 cfs version! :confused:
[Nexus S Android Development] caliban2:
So you wouldn't call it SoD what happened on my phone last night, I see. Well, whatever suits you. Oh, and the test-kernel is primarily for those experiencing reboots during calls. Thanks for the lecture-attempt anyway!
[Nexus S Android Development] phone_user:
http://xdaforums.com/showthread.php?p=21837470#post21837470

leejunha32 (not me), quadrant champion!

GLaDOS v2.9 cfs, @1.4GHz, LiveOC113 (1.58GHz)

arm 1500mV / int 1250mV

ROM : Neapolitan's AOSP+
[Nexus S Android Development] CrackDaddy:
Did you not read correctly?? QUOTE: We (AS IN YOU & MYSELF!) seem to have different circumstances (NOT REBOOTS!), (SOD's) whilst charging with the v2.9 cfs version!

But if you want to be funny, then yes fine, SUITS ME!!
[Nexus S Android Development] caliban2:
yeah, but it "could" still be kernel related. Way too much funny business with ics and custom kernels. So trying the test kernel would make sense. I don't want to because 2.4 gave me reboots during standby, don't want that back.

You on the other hand, IF you get the SoD again, could give it a shot. After all you didn't experience anything similar to my yt/vid-playback issues before, right?

Regarding music-reboots/freezes: got them myself with cyanogen 9 app, read about poweramp and never get them with stock-app and win amp -> rather app-related?

Same for call reboots: long time since I read about one on stockrom -> rom-related?
[Nexus S Android Development] CrackDaddy:
I'm not saying anything (I wouldn't want it to seem like I was attempting to lecture anyone!)

But if I do remember correctly, it were you who quoted me to begin with!? Besides, I've aleady posted what I'll attempt doing to rectify "MY" situation!
[Nexus S Android Development] endursa:
the only thing I'm curious about is why the reboot on call problems only occur with glados and no other custom kernel, on custom as well as stock roms!

because of that I hardly can imagine any Rom related problems.

just downloaded test 2 and start testing right now, but can't call right now, so only music test till later tonight
[Nexus S Android Development] CrackDaddy:
Thankfully, I've been fortunate enough not to experience any call related reboots with any version of the GlaDOS kernel, maybe something to do with different phone models?? no problems whilst playing music either, but look forward to your results all the same!
[Nexus S Android Development] caliban2:
wait, there have been call-reboots on stockrom? I mean without oc and stock voltages? You sure? (The reasoning in testing for stability while overclocking at the same time eludes me)

I never had them, but phone-app is very laggy in ics. Would be interesting if it also happens with exdialer etc...
[Nexus S Android Development] CrackDaddy:
Are you sure you can read? :D He said call-reboots *JUST* with the GlaDOS kernel, & on custom *AND* stock roms! :cool:
[Nexus S Android Development] caliban2:
Yeah, I can. And I can't remember reading about any reports about call reboots on non-oc stock in here. Are you able to follow a thread or do you only read the last page?!

Wait, scratch that last question. You weren't even able to check my last posts to see if I already posted my setup.
[Nexus S Android Development] CrackDaddy:
I'm on the last page because I've *READ* the rest of the thread thnx! :p :D

ps: I probably missed your setup because I wasn't interested in what you had to say!
[Nexus S Android Development] endursa:
hmm, I can't say for sure that there are reboots on stock rom while calling! because i switched to aokp before 2.4, but since I only really use it because of notification toggles I guess I'll try with stock tonight, just to be sure!

I just have no problems with reboots on aokp with Steve garons sg-ics kernel!

sorry for causing an argument :-P
[Nexus S Android Development] caliban2:
Huh? You didn't. :D

But I really can't remember any reboots with stock frequencies and voltages. Doesn't mean I'm right.
[Nexus S Android Development] phone_user:
I hope you have a good showing. The stability of GLaDOS and MODs included is essential for the whole community. :)
[Nexus S Android Development] endursa:
ah don't missunderstand

I am on stock frequency and voltages I just don't use the stock ics update, but a aosp compiled rom with some slight mods!(only graphical changes nothing. deep down in the system though)

I always use 100/1000 without any undervolting,

even tried 200/1000 but also the reboot problems!

but we will see downloaded the stock update already :-)
[Nexus S Android Development] IIIV:
Most stable GLaDOS version for me is the non-65fps 2.8+ test kernel. Silky smooth and no reboots or SoD after almost 2 weeks of extensive use. My settings: BLN / ondemand / 120% / 240-960 MHz / Deep Idle: ON / default voltages.

You guys try it and let me know your experience.
[Nexus S Android Development] caliban2:
got you right the first time. :-)

As you say, it's modded. But somehow I got the bad feeling you'll report a reboot within the hour... ^^
[Nexus S Android Development] steve17360:
Hi, what's the difference between BFS and CFS? Thanks.
[Nexus S Android Development] aLNG:
CFS is better for mutitasking and normal usage

BFS is better when play a lot of games, because it give more performance for foreground activity
[Nexus S Android Development] steve17360:
Thank you.
[Nexus S Android Development] keb00:
I had a reboot after leaving the camera and I have a bug with the light sensor, which is always getting more than necessary, as well as a baterry drain .. :(
[Nexus S Android Development] endursa:
damni it i can't get my asop update to acept superuser, so no root, no fun, flashing back my nandroid now, so kernel test on asop has to wait will i got time to figure out whats going on with root :/

edit: nevermind, had the wrong su zip file :) flashed clean asop with glados2.9, let the reboots begin, or hopefully not :D
[Nexus S Android Development] Ezekeel:
I have compiled yet another test kernel. This one has the V2.4 kernel config and the standard Makefile without optimization (like test kernel 2), but is compiled with the Google toolchain (thanks to Morfic for providing it) instead of the CodeSourcerey TC.

Download test kernel 3: http://depositfiles.com/files/zlm0ztx8y
[Nexus S Android Development] phone_user:
Thanks for the test version. As always, gave it a try :)

"reboot while calling"

last_kmsg
[Nexus S Android Development] AeroEchelon:
Tried test version three and reboot while calling with DEEP IDLE ON. Never tested it with DEEP IDLE OFF.

Deep idle is the only reason I want to use this kernel ...
[Nexus S Android Development] endursa:
Begin Test series IV - 27.01.2012

#Phone: i9023
#ROM: asop(patched BT framework), no other mods,
#SETTINGS: BLN off,BLD(2sec),DI:ON(bt patched framework),ondemand,100/1000,display autooff(1min), bt off, gps off, wifi on
#Conditions: no proximity interaction, phone on table, just dailed time number

#KERNEL: GLaDOS-cfs-2.9 (no test version)
first call - 09:09
- 9:34 no reboot but, can't wake up the device with power button
- could wake up after moving finger over proximity sensor!
- call ended by me (27min)

test will continue, and i will switch to glados test as soon as a reboot on call occurs

note - difference from my first three test series is that i changed rom from asop back to stock yesterday evening

(had awesome standby over night, lost 4% with data on!)

edit:

two calls made, no reboots.

But i made an observation that is worth mentioning, despite having deep idle active, nstools deepidle status actually shows no deep idle usage, neither TOP=ON nor TOP=OFF.

I don't know whats going on, but i have restarted my phone now and test further.

another difference in settings: i had wifi on the whole time, set to be active also in standby all the time <- is that the cause of not using deep idle? does wifi sleep policy interfere with DI usage?

yes wifi never sleep policy actually interferse with deep idle, or my reboot solved the problem, despite i had no app running in background before...

second call - 10:34
- call time 10min, no reboot

third call (bln on) - 11:20
- call time 15min, no reboot

listening to music, google music online content, 10minutes
- no reboot
listening to music, google music offline content, 20minutes
- no reboot
[Nexus S Android Development] caliban2:
goddamit, now i'm getting call-reboots too. first time ever. and by the looks of it, i'm getting all those i never had in the past weeks at once: 5 calls in a row, doesn't take 2 minutes to occur. :(

so much for "doesn't happen on stockrom at stock freqs"...

still deciding what i'll do now, try test3 or go back to 2.7 (kept that as a fallback because with it i had the longest streak of a stable sys)
[Nexus S Android Development] endursa:
i guess i brought the voodoo upon your phone oO

sad to here that you got reboots :/, i had not a single one with 2.9 (non test) today

but i have done a clean system re install yesterday with titanium restore of all my apps!

Do you know you exact settings? Wifi(policy?), Gps, BT, (nstools settings, are the same as you posted a few pages back i guess?)

edit: i thought of something new, could it be related to being connected to 3g or 2g, when the call reboots happen? i'll take a look what type of reception i'm on, with my next tests!
[Nexus S Android Development] caliban2:
voodoo? yep, seems so. ^^

regarding settings:

- nstools as it were

- wifi is on in standby only when attached (was off today though)

- gps on (not used)

- bt off

regarding network:

funny you should mention that, i had some thoughts myself and came to the same conclusion. actually i had set 2g-only today, normally i don't ever use this. but i was in an area with shaky 3g-reception, so to preserve batt...

hasn't there been some 2g-bug on the galaxy nexus right after release?!

edit: there was, but it was about ringtones off when in 2g-mode.

using 3g now and 2.7, but i think i'll test the 2g-theory with 2.9 later today.
[Nexus S Android Development] endursa:
I just forced 2g mode made a call and boom, reboot

I think that could really be the issue!
[Nexus S Android Development] caliban2:
back to 2.9, made & received some calls with forced 2g - "no luck" so far.

the silly thing is stable... :p but maybe i'll get some reboots when the sys has been running a few hours.
[Nexus S Android Development] endursa:
yeah same here,

after the reboot i made a call with 3g forced, no reboot for 15 min

back to forced 2g, no reboot since 11 minutes, call still running

btw i love the contracts in austria, couldn't do this without my quota of free call minutes :D
[Nexus S Android Development] caliban2:
Question is, how much longer we will have them, with only 3 providers being left soon... but yeah, until now we're the lucky bastards of Europe. ^^

Still no luck getting reboots.