yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] nathanson666:
Uptime after random reboot

I got a random reboot today while signing out of Talk. I'm not convinced that the reboot is kernel related but when I checked the uptime after the phone restarted it seems to show that the phone has been on since way before the reboot.

Is this normal? Shouldn't the uptime reset to 0 when the reboot happened?
[Nexus S Android Development] SilverEagle:
Its a bit silly that we need to increase voltage below 50% btw...never done it before and all was fine...btw its @ 77% now...long time before 50%
[Nexus S Android Development] polobunny:
Well, I think I got a drop but didn't know it.

Yesterday night I was texting and suddenly the convo stopped. Thought the person went away but turns out I didn't "answer" from what she said.

Just restarted my phone after 40 hours hoping to fix Google maps issue. Upon rebooting I got 2 texts that this person sent last night. :(

I'm turning off deepidle and seeing how it goes.
[Nexus S Android Development] bdpyo:
I'm here for the data drop gang bang, its only driving me nuts because I had a first date last Friday with this amazingly hot girl and are texts are not coming and going like they normally would. :(
[Nexus S Android Development] SilverEagle:
Rebooted @ 75%, so its not a below50% problem :\
[Nexus S Android Development] franciscofranco:
The reboots are definitely not normal, I don't have ANYTHING of that and I've running devnull rom. It's not broken for me at all.

Check your NStools if you're not undervolting somewhere.
[Nexus S Android Development] thegtfusion:
I dont have problems with reboots either. The 4 dec one is super silky smooth man :D.
[Nexus S Android Development] ellesshoo:
I like 20000us, 90% myself. 90% seems pretty good at keeping the CPU steady at a low frequency but still being low enough that things ramp up before they bog down at the lower steppings. Anyway, agreed, ondemand > lazy (especially when deep idle is not a factor).
[Nexus S Android Development] SilverEagle:
was all stock, im trying now a +25mv on min freq (200mhz in my case)
[Nexus S Android Development] ShadowVlican:
happened to me too

almost tricked me into thinking the phone was solidly stable.. until i caught it restarting lol
[Nexus S Android Development] franciscofranco:
I removed, re-added all the deep_idle code and did some cleaning. Will test deep_idle on for two days and see how it works how in terms of data loss.
[Nexus S Android Development] phone_user:
2 days, the fatal hour :)
[Nexus S Android Development] boostern:
@franciscofranco

After having disabled deep idle all the reboots vanished.

At least for me it seems a problem with the current implementation of deep idle.
[Nexus S Android Development] djjonastybe:
Ezekeel's kernels have the reboots too. I think the deep idle code needs to be rewritten or implemented differently.

I tried numerous combinations of kernels and roms.

Any news on a fix?

I think something is causing a kernel panic in the code. Which results into a reboot if kernel panic is enabled. I remember this from my previous phone.
[Nexus S Android Development] suksit:
I got random reboots on 25 NOV build but not the 4 DEC... Been rock stable for two days now.

BTW, deep_idle is always on.
[Nexus S Android Development] djjonastybe:
When I turned my screen on today, it froze, and next it was rebooting.

if you want a init.d script to log reboots

before you reboot to test the script make sure you do the following first:

start the android terminal emulator:

You can also replace >> by > So the filesize doesn't grow. But this will only cause to log the last boot time.

I suggest you read the file with your favorite root explorer/browser

Might be useful on ROMs without a bootsound :) Just remember when you manually reboot the phone.
[Nexus S Android Development] franciscofranco:
Im sorry I cant reproduce the freezings and reboots, I got nothing of that.

Running deep_idle now for a few hours and no data drops, been using sms, calls, 3g, no **** yet.

Lets hope it stays like this.

My setup is this:

Rom devnull 1.1

Kernel 06/12 (local build - not released yet)

Stock voltages

Live oc 110

1100/440 lazy screen_off_maxfrequency
[Nexus S Android Development] suksit:
Alright I will add the script to init.d to see if my NS will secretly reboot without me noticing it :D
[Nexus S Android Development] boostern:
Try without screen_off_maxfrequency, I think this option is what prevent you from rebooting issue...
[Nexus S Android Development] etoy:
i also had reboots with last version,never had one before.

and i never used deep idle and screen off maxfreq, so i can exclude it's the cause (at least for me).
[Nexus S Android Development] LordLugard:
Bom dia ... (only Portuguese I know)

Anyway, been running your kernel for the longest and I don't seem to have any of the issues some are describing. I'm running Carbon + Oxygen Mix on a Nexus S 4G, min 200/Max 1000, conservative, and everything else about the kernel default (deep idle and the voltage stuff).

Thanks.

Sent from my Nexus S 4G
[Nexus S Android Development] phone_user:
for 1 day, no data drop, no reboot with 04/12 on SuperOSR 2.2.4 rom

deep_idle ON / LiveOC 120 (240~960) / lazy / screenoff_maxfreq ON

800 MHz : 1225 / 1100 mV

400 MHz : 1050 / 1100 mV

200 MHz : 950 / 1100 mV

Give us 06/12 :)
[Nexus S Android Development] franciscofranco:
In my opinion it's a rom issue, so with a full data/system wipes and full re-flash that should be fixed. Like I said, I can't reproduce it with stock options.

CM 7.1.0.1 has been known for instabilities, its time to change roms.
[Nexus S Android Development] polobunny:
But I'll miss all the cool features. :(

It's not like the 259 nightly is any better though. Oxygen isn't bad but still missing a few things IMHO.
[Nexus S Android Development] djjonastybe:
franco, which rom do you recommend me?

Am I good with NSCollab? Since it's also CM7.1 based.

My device freezes and reboots now when I turn on my screen.

Using stock settings + lazy + deep idle + maxfreq + 100-1000

I would be happy if you suggest a good ROM for me. I may return to stock otherwise
[Nexus S Android Development] franciscofranco:
I recommend anything close to stock. I use devnull and I'm very happy. In my opinion both CM 7.1 and Oxygen 2.3.2 are rubbish, ****ing unstable. It's just my taste, doesn't mean everyone has to use what I use.
[Nexus S Android Development] Cybergr:
I was looking on etoy`s signature and he reports he is on CM7 1.0 not CM7 1.0.1..

Anyway...my ROM built is based on CM7 1.0.1 and all i have to say is that i don`t have any kind of those issues reported here Franco...neither someone using my ROM + your 04.12 stable kernel..No complains till now..!!

Brilliant work once again Franco!
[Nexus S Android Development] Zorrich:
I have never been happy with the stability of any CM7 based roms either. Just when I thought I found one, I ran into the voice bug where when someone calls me, I cannot hear them but they can hear me. This is unsatisfactory on a phone, and happens quite a bit.

I have always loved Oxygen 2.3.1 or Carbon ICS Mix (based off 2.3.1). These ROMs never let me down, and I am a harsh critic when it comes to stability. I agree with Franco that Oxygen 2.3.2 is not their best release. It had too many issues and I had to revert back to 2.3.1 within a few days.

EDIT: Spelling fix.
[Nexus S Android Development] polobunny:
I get the voice bug ALWAYS but ONLY when I call my Voicemail. Got to put it on hold then it works.

I'd still miss all the features CM has though. If I had more time I'd cook my own AOSP ROM but I don't. :(
[Nexus S Android Development] Zorrich:
Might want to try SuperOSR V2. I didn't run it for very long due to my preference for Oxygen/Carbon, but it appeared to run very smooth for the day or two I used it, and it has many CM features.

Link to ROM noted below encase you want to try it, on post #165

http://xdaforums.com/showthread.php?t=1201435&page=17
[Nexus S Android Development] polobunny:
Thanks for the suggestion. I'll make sure to check it out when I have some time. :)
[Nexus S Android Development] djjonastybe:
I am currently building my own rom started from scratch GRK39F.

I will just add the basic stuff to it and flash this kernel over it.

Current or coming features:

- busybox

- root

- deodexed, zipaligned

- google-crap-i-do-not-use removed (removing everything that'S downloadable on android market)

- init.d support

Shortly said stock-stable-fast and deep idle ready

If my problems are still present with my own ROM i will definately give up

---------- Post added at 07:55 PM ---------- Previous post was at 07:51 PM ----------

Well as far as I know I didnt have any random reboots because I didnt have any boot sound.

Only my lockscreen would freeze when turning on the screen again. And then I got the reboot.

Maybe there is indeed a bug. Maybe we should make a big thread with a summary so we can have a overview on which ROM it works and which phone. If there is a pattern off course
[Nexus S Android Development] etoy:
i'm still on cm7.1.0 and not 7.1.0.1. i'll probably stick with it for a little more, then upgrade to ICS/cm9 someday soon.

the previous kernels never gave me problems but i deleted the zip,unfortunately. does someone still have the 2511 one please?
[Nexus S Android Development] notabene:
25.11 here..don't forget, no support from franco to old version of kernels..

http://www.multiupload.com/69J73K972W
[Nexus S Android Development] SilverEagle:
nope..tried and rebooted.

btw it reboots ALWAYS on screen off...when the screen is on the kernel is stable and fast
[Nexus S Android Development] Bob889:
Just wanted to say this kernel rocks, I'm running Oxygen 2.3.2 with the latest Franco Dec 4 kernel with deep idle working. Its been running smooth and fast for the past 24 hours with no troubles. My battery life could not be better. Over 16 hours of moderate use and still 80% battery!
[Nexus S Android Development] boostern:
Maybe my post could be misunderstood. I mean, with screen_off_maxfrequency disabled, all the system can be more unstable because there's no fixed frequency with screen off. With the option enabled there's a fixed frequency (the maximum frequency) and maybe this is why franciscofranco isn't able to reproduce the reboot.

I started having random reboots with 04/12 release, infact by disabling deep idle it's all rock solid now.
[Nexus S Android Development] polobunny:
Just tried SuperOSR, not bad but it's missing a few key things. Like proper Canada French, it only has France French. Half the menus are still in English too. Guess I'm gonna stick with CM and it's quirks!
[Nexus S Android Development] Zorrich:
Doh, too bad.
[Nexus S Android Development] djjonastybe:
Deep Idle is working on my near-to-stock ROM :)

Those who don't mind a near stock experience and like to have deep idle working feel free to try my ROM. It doesn't have anything new except that it runs great with deep idle

http://xdaforums.com/showthread.php?p=20047151

Too bad the Devnull rom is outdated (2.3.5).

Thanks for the suggestion franco. I have had no reboots or freezes so far.

During the night I had a 4-5% drop in battery. I guess that is normal

Reason why lazy needs the screen off is simply actually. Going from 100mhz to 1000mhz needs a raise in voltage. Well the difference in voltage is lot bigger than the difference from 100 to 200 or from 100 to 400.

What I am saying is, conservative boosts its frequency more in steps based on usage. This may be why conservative can run great without maxfreq on.

Unless someone contradicts me.
[Nexus S Android Development] nosfaratu:
Franco, my nexus blocks at night, and after I have activated the deep idle, however I turn it off yesterday and did the same!

Some help?

Today I put the new kernel, and see the result during the night-

Another thing I do not understand is why I sometimes appear to put the new sim card code ..

What could it be?

Rom? Kernel?
[Nexus S Android Development] martinsjt:
Hello,

Yap the languages support is an issue with this ROM but for me it’s the best ROM for Nexus S.

From my experience whit this ROM when you change the language you should reboot the device so the change is applied to all menus.

Best.
[Nexus S Android Development] franciscofranco:
Another night and no problem with deep_idle. Seems like deleting and re adding the code fixed something.
[Nexus S Android Development] ellesshoo:
Can we try the new build now?
[Nexus S Android Development] franciscofranco:
Guess I talked too soon. After I entered the train I couldnt wake up the screen and it rebooted right after. GG for me, first reboot ever with the normal 1100/440 lazy, no uv. Deep_idle will be off by default in the next kernel, users that use it on a daily basis just have to turn it on.
[Nexus S Android Development] Cybergr:
That had to be done...as far for some is stable and for some other is not..turning Deep_idle off by default in kernel sounds a no way out solution for the moment!;)
[Nexus S Android Development] xanos01:
Noob question, how do you turn deep idle off?
[Nexus S Android Development] caleb1783:
you could use the following code on the terminal

echo 0 > /sys/devices/system/cpu/cpufreq/lazy/screenoff_maxfreq

or you can download NStools from the market... but its not really well incorporated...

or you can visit http://caleb1783.tistory.com/233 to download a script that will autorun everytime you start your phone.

so many choices...
[Nexus S Android Development] stojshic:
Isn't that the script for screenoff_maxfreq, and that ain't the same as deep idle mate...

Just download NStools from market, and you'll have many options for kernel, including deep idle on-off switch...
[Nexus S Android Development] caleb1783:
oh it is... sorry...

echo 0 > /sys/class/misc/deepidle/enabled

this is da right code... nstools is ok but i dont like it that it starts after phone is rebooted...

ideal script should run during boot time...

but thats just me....

Sent from Divinus Nexus S...
[Nexus S Android Development] polobunny:
Worry not, you're not alone. :D

Liking 4/12 kernel anyway, no problem with it so far.
[Nexus S Android Development] SilverEagle:
Looks like the franco+miui combo has some problems, same reboots in kelmiui...with matrix is all ok
[Nexus S Android Development] franciscofranco:
Useless feedback. If it works for you then use it.
[Nexus S Android Development] polobunny:
What if it doesn't? :p

Using 4/12 version, last reboot was 18 hours ago. No problem so far. Deep idle disabled. I'll try to go until 100. ;)
[Nexus S Android Development] SilverEagle:
It works but not as responsive as yours, i just want to get the max performance with the maximum stability
[Nexus S Android Development] franciscofranco:
Small update here. Updates will slow down a little because there's not much left to do and I got some real work coming in from university and some other side-jobs related to the IT world.
[Nexus S Android Development] frenccw:
Touchwake not working on latest kernel. Already used flashed nstools reset to no avail.

Edit: Ughh after flashing older kernel it doesn't work either. Will try to find out what's wrong

My ROM: Nexus MV 1.11.30

NStools/Ezekeel: Default settings with touchwake enabled, stock voltages and cpu

Kernel: 8/12 franco

BLN: On

Edit2 :Double ughh. Managed to brick my phone with too much flashing. After full wipe and flashing Nexus MV rom the touchwake works again. Kernel is on 25/11 though
[Nexus S Android Development] polobunny:
Excuses! :D

Rocking 4/12 'til I feel like rebooting for 8/12. So far so good with deep idle disabled.

Edit: 26 hours in btw.
[Nexus S Android Development] suksit:
Thanks for the update. Now testing 8 DEC build with deep_idle on (as always)
[Nexus S Android Development] xanos01:
Thanks
[Nexus S Android Development] phone_user:
Thanks for update :) If I have a problem, I will report you.
[Nexus S Android Development] r5xscn:
Hi, I have some problem with your newer kernels (25 November and newer). The Lazy governor is not behaving like before (before 25 November). When playing music, 1 GHz is used more than before. And it's behaving more like smartassv2 (before is like ondemand).

Anyone having this problem?

BTW thx for the new kernel:D.
[Nexus S Android Development] djjonastybe:
I am running stable deep_idle on near-to-stock ROMs. Running it on anything else seems to result in reboots. I think the reboots are mostly ROM-related

Unbelieveable I didn't have had a single reboot yet while I was having serious problems before.
[Nexus S Android Development] akshayf:
I think the data problems have been solved now due to the code rewrite.....uptime 8 hours on nscollab rom with deep idle enabled and smooth as yet.
[Nexus S Android Development] r5xscn:
I'm on stock and didn't have a single reboot, but data loss does occur (don't know for 8 November):D.
[Nexus S Android Development] 93ae8074:
I'm on stock too, no single reboot since 4-DEC and no data signal loads at all.

Cheers.
[Nexus S Android Development] bdpyo:
damn, everytime i get a great gb setup franco puts out another release. fml lol
[Nexus S Android Development] bdpyo:
@franco or anyone who knows, what ROM is franco running? O_o
[Nexus S Android Development] thegtfusion:
Devnull 1.1
[Nexus S Android Development] ro_explorer:
Yes, that's the one .. we were writing at the same time :)

@Franco ... buddy ... this is my last post in this thread :) ... a Galaxy Nexus is on the way to my home (I guess is in Santa's bag) .... so startting with ~2 weeks from now I'll start testing your other great kernel in the respective forum section :)

I want to thank you again for the great work you're doing and be sure I'll contribute to raise those funds needed for the GN you want.
[Nexus S Android Development] bdpyo:
please correct me if i am wrong but is that oxygen?

@ro, congrats dude!
[Nexus S Android Development] bdpyo:
i found it, may check that out. O_o
[Nexus S Android Development] ranasrule:
devnull i think
[Nexus S Android Development] djjonastybe:
devnull 1.1 last time I heard him

downloadable at oxygen.im
[Nexus S Android Development] franciscofranco:
Yes indeed devnull for my GB rom.
[Nexus S Android Development] doc_v15:
Just some thought, I think so far the best kernel for me are

- 1 Nov BFS

and

- 25th Nov

The newest one, Dec 8th, for me it still has some issue with the network and data connection.

But, I think I'm gonna stop at Nov 25th version for a long time now :D Thanks franco for blessing us with your hardwork!
[Nexus S Android Development] Dr_Ownage:
havent reported any of my experiences with this kernel in a while if ever. but just to let everyone know i have been running it for almost a month now flashing to the latest as they come out. I have not had a single issue with 4th Dec it has been rock freaking solid! battery is amazing! everything is snappy! loving it!

Just hoping that when i get my Galaxy Nexus the Franco kernel there is half as good! xD

loving everything about this kernel so far! not a single reboot and i have had it on for a solid 80hours now. charged my phone last night from 20% after 2days 3hours of moderate usage. VERY VERY HAPPY!

my setup:

latest CM nightly.

KD3 radio.

franco 4th kernel.

Deep idle Off

Max freq Off.

lazy.

today i swapped to ondemand to give that a go. i will be running 15000 98

will post results after some testing
[Nexus S Android Development] polobunny:
I'm on 14 hours and a half of battery with 1 hour 45 minutes of gaming (airplane mode) and I still have 32% left. Got a call earlier, texted a bit, read some jokes this morning too.

NSCollab 1.0.50

KB3 radio

Deep idle off

Ondemand 90% 20000 (trying that for the moment, will likely switch back to 98% 15000)

A good undervolt

WiFi timeout when screen off set to 30 seconds instead of like 10 minutes

50 hours uptime too. :cool:
[Nexus S Android Development] bgdxv:
Yes. So it is a problem of the i9023. I see that you have one too. I hope that they will make a patch for us too :(
[Nexus S Android Development] ragnarokx:
Getting consistent 100% charges on my i9020T

Sent from my Google Nexus S
[Nexus S Android Development] kecinzer:
I have 9023 and get 100%. Just take a time :). It's a miracle for me - I don't see 100% battery on my phone since I had HTC Desire :)

BTW. Ezekeel just released new patch for LiveOC.
[Nexus S Android Development] as6:
It's not really a problem for me. At the moment there is no Nexus S model that's loading to 100% and there aren't a lot of moments where my phone is fully loaded .

I think there are a lot of other things that could be improved.
[Nexus S Android Development] franciscofranco:
My phone always charges to 100%, but from 97% to 100% takes some time!
[Nexus S Android Development] Yusei:
BLN not working here
[Nexus S Android Development] skinniezinho:
read some pages back, there is a "temporary solution"...

it's flashing morfic's kernel, then flash franco's kernel, voilá bln working.
[Nexus S Android Development] franciscofranco:
Yes, there is a lib file that is needed and not all the roms ship with that file. Next update will have that bundled, no worries.
[Nexus S Android Development] ragnarokx:
Unzip a Trinity kernel, in the extracted folder navigate to "/system/lib/hw/", then copy "lights.s5pc110.so" to the same folder on your phone's internal memory. This will fix BLN.
[Nexus S Android Development] thedudejdog:
I've tired this and I get this weird bug where if the screens off and you touch a soft key bln goes off. Kinda defeats the purpose. Ns4g brainmasters miui
[Nexus S Android Development] ragnarokx:
Hey, you're right. Touching a soft key with the screen off lights them up (I'm on the same ROM btw). But why would you be pressing soft keys with the screen off?

Sent from my Google Nexus S
[Nexus S Android Development] thedudejdog:
accident, maybe while slipping the phone into my pocket or while laying the phone down.
[Nexus S Android Development] franciscofranco:
Update postponed for tomorrow, I gotta do more testing.
[Nexus S Android Development] caleb1783:
I m using 9023 and charges to 100% without problem...

Try using nexus mv tomorrow or try enabling stay awake...

Sent from Divinus Nexus S...
[Nexus S Android Development] noobhero:
your kernel combined with supercharged script is plain awesome

ps. will there be any conflict with the scripts?
[Nexus S Android Development] kecinzer:
This morning I was very suprised. Because over night I lost only 2% of battery! I have special night profile with all data connection off, but GSM is on.

This is awsome!
[Nexus S Android Development] ro_explorer:
I'm also loosing only 2% over night but I'm not turning off anything :) ....
[Nexus S Android Development] eiabea:
Really great kernel, with great battery life, but i just had my first BSOD...only BLN leds were lighted up --> battery pull :(
[Nexus S Android Development] franciscofranco:
Increase minimum frequency. Next update should have that fixed for good with the latest bugfix from Ezekeel.
[Nexus S Android Development] mixtapes08:
What is the default clock speed of your kernel sir?
[Nexus S Android Development] r5xscn:
Newbie here.

What is "Ondemand 90% 20000"?
[Nexus S Android Development] polobunny:
My ondemand governor settings. You can change those advanced settings using SetCPU. 90% threshold and 20000 sampling rate.