yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Cybergr:
Sometimes I am experiencing forse close in my camera app.. expeciially when I play with camera settings.Is this a bug..?Anyone else experiencing the same problem!?

PS: I am on NScollab 1.0.50 with 27 franco kernel.
[Nexus S Android Development] jason62391:
Hey. Great kernel btw. Do you know how to change the refresh rate cap to 65?
[Nexus S Android Development] FL0OD:
Here it is for the day. Those large drop offs are after taking a picture then almost immediately rebooting the phone. Took a picture just fine, shut the phone off, then it would not come back on. I did a battery pull both times and rebooted the phone only to see HUGE drop offs in the battery. Also worth noting as you can see that towards the end the battery was actually gaining battery without being plugged in to any power source. I know its close to Halloween and all but I think your kernel has possessed my phone ;). Other than those two items the phone has been super fast and my 3g hasnt been this good on my phone since I bought it two months ago. Any comments?
[Nexus S Android Development] franciscofranco:
Nop, I didn't know that was even possible?

Hmm, seems the battery wasn't properly calibrated yet. Do a full charge and wipe battery stats in the recovery, then let it adapt itself to the new kernel for at least 24/48 hours ;)
[Nexus S Android Development] FL0OD:
I did calibrate it after I put it on last night. Just wanted to show you that. I hadn't ever seen that before. Thanks for the advice and work on the kernel.

Sent from my Nexus S 4G
[Nexus S Android Development] arshad14:
Hi Cybergr, I wasn't sure about how to get a screen shot but I'm no.87093 and got a score of 3137. I set my min at 200 and my max at 1000 with Smartass v2 governor.

Hope that helps!
[Nexus S Android Development] brenix:
Just compiled this kernel with the latest commits... seems I'm not getting the bsod issue anymore when waking the phone.. however wifi isn't working..seems like others have this issue to.

Very fast kernel btw.. love all the miscellaneous tweaks you've added.
[Nexus S Android Development] franciscofranco:
Wifi is working fine here, you have to copy the bcm4329.ko module from your compiled kernel otherwise wifi won't work...and no one complained about wifi, works fine ;)

Yes the latest commits just made this **** even faster, I'm gonna test this out tomorrow during my university class time.
[Nexus S Android Development] chdeul:
Hello,

No auto BLN in this kernel? (Same as Matr1x and Talon)
[Nexus S Android Development] xXfuzzXx:
Hm, have to quote myself: As you can see in the screenshots I had a constant battery drain during the night till 0% :D

Dont know how this could happen, at first I thought it was BSOD, but even after a batt pull the phone didnt wake up...

I'll stick to this kernel, would like to see if this will happen again.
[Nexus S Android Development] EdForce1:
Next release will have auto bln me thinks the dev wrote. :)
[Nexus S Android Development] doc_v15:
Confirmed for the FOREVER DEATH after taking camera.

Please fix this, I like your kernel

Also, this the first kernel in Nexus S that I have tried, that FULLY charged until 100%!
[Nexus S Android Development] al_madd:
Im sorry.

want to ask about battery calibrating..

wipe batterystat after we fully charged or after we drained the battery??
[Nexus S Android Development] martinsjt:
Hello,

My experience with Deep Idle:

I wiped my device and made a clean Oxygen 2.3.1 installation. Reboot cleaned cache and dalvik-cache and installed KalimochoAz kernel.

No issues.

I than installed all my usual apps, after that I could not wake up my device after screen lock.

The same story with Franco’s kernel.

So one of the apps was causing it, after testing I discovered the issue is caused by Autostarts.

https://market.android.com/details?id=com.elsdoerfer.android.autostarts

Not installing the app itself but after I remove some apps from boot.

If from the app I reactivate all apps on the boot no wake up issue.

Can anyone test this issue?

Best,
[Nexus S Android Development] xXfuzzXx:
Which app(s) exactly?
[Nexus S Android Development] martinsjt:
I disable system apps and apps installed by me as:

Calendar

Mail

Gmail

Titanium Backup

Best,
[Nexus S Android Development] skinniezinho:
Glad to see you here Francisco.

You've done a great job in the P500, hope you do the same in NS.

ASAP I will try your kernel =)
[Nexus S Android Development] martinsjt:
Let me just add, I love you kernel and your ideas about performance improvements but when I remove some Rom components or deactivate it at boot I get the wake up issue.

Calendar

Gmail

Mail

Music

etc

Can you please release a version without Deep Idle.

Best
[Nexus S Android Development] franciscofranco:
Good morning everyone.

Next update will have the option to turn on and off Deep Idle while you're using your device, Ezekeel released an update some hours ago to do that, so don't worry.

In the mean time please try to increase your minimum frequency to 200 up from 100.

Yes auto BLN is already running in my own build and it will be released in the next update.

About the battery wiping thing, do it after a full charge.

It's already stated that for miui you have to edit your build.prop to delete two lines that prevent the phone to enter full sleep with this deep idle mod. Go to miui's thread I'm sure you'll have the full procedure there. Other than that I think that was some app running in the background without sleeping.
[Nexus S Android Development] Cybergr:
Thank u ashad14 for your reply..!!It is possible u try running quadrant too and post back the results!?If u gonna do that just try to run it 2 or 3 times cause the results the first time u run the tests are somewhat inaccurate!!

As for the screen shot thing and NSCollab Rom is very simple..Just press the power button and hit screen shot!!
[Nexus S Android Development] arshad14:
So here are the quandrant scores after running it 3 times. My min had to be set to 400 now cause of BSOD and max set on 1000 with smartassv2 governor. Btw, GPS lock is super fast now too.
[Nexus S Android Development] saranyan:
I have a 99complete file in my /system/etc/init.d folder, Is that script part of this kernel or has it been leftover from a previous kernel installations.

Asking because i had three freezes on my phone today.
[Nexus S Android Development] Jonathon Grigg:
Deep idle should be enabled by default, but just confirm that first. The reason the live OC values are reset is because the change is only made temporarily. For it to "stick" you need to create an init.d script to enter that value each time you boot your phone. Search the thread and Nexus S forums to see if you can find some examples, I am certain there's some floating around if you need guidance. Init.d scripts don't work on stock roms though, this is something to keep in mind if things still don't work.

Hope this helps clear things up (:

Sent from my Nexus S
[Nexus S Android Development] vis80k:
just felt how it feels to live with deep idle!

so far before, I was lucky to have 40% battery when I step out of my office from full charge in the morning, but today with franco kernel, I still had 70%!

looking forward to your next update with the lazy+ governor :)

i guess another reason for loving this kernel is because franco is using Oxygen rom, which is the same rom I use and prefer over all other roms.
[Nexus S Android Development] saranyan:
I am also using oxygen , can you do me a favour.

Can you check in /system/etc/init.d folder and see whether you have file called 99complete?
[Nexus S Android Development] franciscofranco:
I don't get the stats, but pointed by FloHimself this may be the cause: https://github.com/franciscofranco/Nexus-S/commit/0c304350fcc71722be00df4993cf09afef6ca765

And no I don't get reboots if I use the camera and tap the power button. I tried with using the camera, going to home and screen off, tried screen off with the camera app open, none of this two scenarios made my phone to reboot, crash, freeze, whatever.

I remember that in one of my previous phones having a wrong or broken frequency table made the camera to flicker and sometimes to reboot the phone while going over X frequency. Maybe your problem lies there?

Yes the file is there.
[Nexus S Android Development] morfic:
Doubtful that it's a frequency table, as nothing happens with deep idle disabled ;P

It's a definite deep idle interaction.

I get no stats and i never applied the cpu idle backport, 3.0 and 2.6.35 are too different to just grab backports, just like BFS .413 which isn't meant for 2.6.35 ;)

Maybe i'll compare your .config to mine, i looked at Ezekeel's but with his very defconfig, the debugging just makes it hard to look through, with you i know there won't be a myriad of enabled debugging to deal with. :P
[Nexus S Android Development] waterface:
Need help here. Take a look

Uploaded with ImageShack.us

Phone was screen off, sitting unused for a while as you can see, and not receiving any text/email. And I still get that high battery drain. Nexus S i9023. Just did a fresh install of latest NSCollab and Franco's kernel 27 Oct. revision. Any ideas why this happens?

CPU usage stats show nothing. But I doubt that the phone was actually on deep idle. Is there a terminal command that can let me check the CPU state, or something like that?

Or am I wrong and this is completely normal?

Thanks to anyone who will shed a light on this.
[Nexus S Android Development] franciscofranco:
Yes it's doubtful that it's the frequency table, just threw it out in case it was useful information because I've seen this kind of behavior before.

But there is a difference between your stats and mine, I really get zero's in every field, you still get idle time count, but I don't.

About the backports, yes both kernels are substantially different but if nothing gets broken no harm is done, people do backports all the time and in this case I don't complain, no instability what-so-ever.

Go ahead, I'm sure you won't find a single debug **** activated besides Kallysms and BUG which I can't get rid off without some compiling problem, Kallysms obviously give me undefined references and BUG the usual function undeclared, so other than those two, no debug ****.
[Nexus S Android Development] franciscofranco:
That doesn't seem normal. Get cpuSpy and bring me a screenshot after a while.
[Nexus S Android Development] waterface:
Thanks man. Appreciate it a lot. Will post screenshot in another half hour or so.
[Nexus S Android Development] morfic:
I see, you meant all zeros, not just deep idle states being 0

EDIT: And it worries me if Con says the patches were meant for 3.0 only, that's all. Considering the bfs patches apply around code that does not exist in 2.6.35, if the code is not added, the result is essentially not BFS .413, but something else.
[Nexus S Android Development] franciscofranco:
I've seen the diff between versions I didn't see any problem with it. I'm not afraid of backports. Even if code isn't meant for X version there is always a way to get it working without issues. But I understand what you say.
[Nexus S Android Development] waterface:
Uploaded with ImageShack.us

Those 6 minutes or so are two calls I received.

Everything seems normal from here, but as you can see the battery is now 83%. Drains fast.

Thanks again for your attention franco, I really appreciate your support in this thread.
[Nexus S Android Development] franciscofranco:
That seems normal to me. Do this bump minimum frequency to 400 and see what happens the rest of the day.
[Nexus S Android Development] MultiCulti:
in which files are the voltages set? any in the init folder???
[Nexus S Android Development] mike216:
Have you been through 2 full charge cycles because if not that seems to happen to some but after a couple cycles its all good

Sent from my G1
[Nexus S Android Development] MultiCulti:
and also, where can i change the available frequencies??? ;)
[Nexus S Android Development] waterface:
I did that, and the phone froze, couldn't wake up when I pressed the power button. Running on default voltages and frequencies, no LiveOC...

Running now again, with 400 minimum frequency, will post CPUSpy and battery readings in a bit. Hope these tests help you devs somehow and I'm not just loitering in the thread!
[Nexus S Android Development] mike216:
What rom you using?

Sent from my G1
[Nexus S Android Development] waterface:
Latest NSCollab.
[Nexus S Android Development] mike216:
Go into cyanogen settings, performance, and uncheck dithering setting then reboot that should fix it I'm also on nscollab and after that I was able to liveoc on stock voltages

Sent from my G1
[Nexus S Android Development] mike216:
This setting surface ditthering should be disabled

Sent from my G1
[Nexus S Android Development] waterface:
Not OC'ing and bot interested in it, just want to understand why the bad battery drain when deep idle should be enabled. Thanks anyway.

---------- Post added at 07:56 PM ---------- Previous post was at 07:54 PM ----------

mike, question- say you play with your phone for a while, or you receive a call or send a mail/text message, and say you have data on and autosync on. Then you shut off the screen. The phone should enter sleep mode/deep idle. I would be curious to see a log of your battery drain log, in particular- if it goes down to ten or less mA as soon as you put the phone to sleep. Set the interval to 60 seconds for the history please, if you will.
[Nexus S Android Development] MultiCulti:
just tried with KelLMSKing 2.4.1 and your latest kernel LiveOC with 120 :D:D

Working great

NO voltage changes

NO DeamonController or SetCPU

conservative

max freq. set to 800000 ... so, the CPU is going up to 960000 with LiveOC ... more than enough!
[Nexus S Android Development] got2best:
Sorry for the off topic question.. but what rom or theme r u using?

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] MultiCulti:
do you ask me? :confused:

If yes:

KelLMSKing MIUI 2.4.1 with the DarkTheme 2.0 which i modified by myself :D
[Nexus S Android Development] waterface:
Uploaded with ImageShack.us

Not getting any better. I really wonder why. Phone has been just sitting there unused for all the extent of the log in in the screenshot... and CpuSpy does report phone being in Deep Sleep. Maybe it needs a few more charge cycles?

mike216 please read my previous post and see if you can provide me with that info!
[Nexus S Android Development] mike216:
It took me 3 full charge cycles before I noticed extremely good battery! Just hang on there I'm positive it will get better

Sent from my G1
[Nexus S Android Development] mike216:
This is where I'm at now running nscollab

Sent from my G1
[Nexus S Android Development] jark99:
I have nscollab and franco. How long has your screen on been? ? Your stats are wiping mine out....what do you do differently? Im on lazy govenor no oc.

Screen on 3.5 hrs. Deep sleep alot
[Nexus S Android Development] mike216:
I like conservative to sit over night and lazy when the screen is on also running no oc 400 1000

Sent from my G1
[Nexus S Android Development] doc_v15:
And how did you that? Two scaling governor??
[Nexus S Android Development] mike216:
Manually lol.. but I'm weird

The lazy that franco will include in the next release will be awesome! No more conservative on the next release because if will be perfect for kicking deepidle in quicker than any other governor, can't wait!

Sent from my G1
[Nexus S Android Development] franciscofranco:
The update will be out today 1st November, just took me a little longer because I wanted to make sure everything was working as it should ;)
[Nexus S Android Development] mike216:
Well then ill consider it my birthday present

Nov 2 actually but a lil early,thanks franco! Loving my phone lately

I really appreciate you test and make sure everything is great

Sent from my G1
[Nexus S Android Development] caleb1783:
lookin forward to the new kernel w new improved lazy...

Sent from Divinus Nexus S...
[Nexus S Android Development] mike216:
Little early :-)

Sent from my G1
[Nexus S Android Development] chinopski:
waiting and excited:D
[Nexus S Android Development] DoktorZero:
Me too

Enviado desde mi Nexus S usando CyanogenMod-7.1.0.1-NS
[Nexus S Android Development] got2best:
Same here! :))

sent from my Nexus S i9023 from XDA premium
[Nexus S Android Development] doc_v15:
Man! You rock! Thanks for the inspiration!

Btw, whats the sequence of the settings?

Which one goes first and scon, etc??

Cause I did liveoc first and then max freq., my nexus freeeze and had to pulled out the baterry over and over

Thanks
[Nexus S Android Development] ro_explorer:
Hi Franco, there might still be a small inconvenience in the battery charging methodology. I saw that if I'll let my phone charge over night, the battery will go to 100% and then it will just bounce between 99 and 100 for hours, until I'll take the phone out from the charger (basically is stressing the battery).

Is there a way of lowering the threshold where the battery will start to be charged again? Let's say .... 97%...

Sent from my green robot ...
[Nexus S Android Development] mike216:
100 % is cosmetic it really only charges to 96% default

Also blx is included so you could drop it down as low as you like

Sent from my G1
[Nexus S Android Development] MultiCulti:
here you go .... this are my settings
[Nexus S Android Development] from1989:
we are looking for the update~~~~~~
[Nexus S Android Development] caleb1783:
no need to rush him...

it will come when its ready...
[Nexus S Android Development] ro_explorer:
Yes and no ...

Originally the battery will charge up to ~94% then stay like this until it is dropping below 90% then it will get charged again up to ~94-96%.

Now, cosmetic or not, it goes up to 100%, it will stop charging until the battery is dropping to 99% then is charging again up to 100 and so on ...

This is just additional stress on the battery w/o any real benefit.

It would be much better to go up to 100% and re-start charging only if the battery will drom below 97 or 96%.

I can actually monitor the charging current and this is the way it goes.
[Nexus S Android Development] franciscofranco:
What, no. It charges up to 96% just fine, then the rest until 100% its just cosmetic.
[Nexus S Android Development] MultiCulti:
hmm .. so, i tested this as well the last day´s ... but as soon as it reached 100%, the charging stops and never goes under 100% as long as i left it on the plug! :confused:
[Nexus S Android Development] ro_explorer:
I'm not saying you're not right .. maybe is something wrong on my side.

I just saw that also the batt monitor widget is "seeing" the same behaviour as I saw with my eyes.

I'll do more digging and I'lll let you know my findings.
[Nexus S Android Development] MultiCulti:
i´m using battery monitor as well, and the line here is always on 100% as long as i have the nexus pluged in
[Nexus S Android Development] jark99:
How do i modify the kernal to only charge to 96% instead of 100%? I enter it thorough terminal emulator? Or...?
[Nexus S Android Development] v3rk:
anxiously awaiting the next release!

i've been running the oct 25 version, still wary of updating to oct 27 because, well, just look at the screenshot. after easily getting my battery to last 1.5-2 days while carefully monitoring wifi, data etc i decided to experiment this past saturday while my family and i went to the fair. i left EVERYTHING on (gps, data, sync, 4g, the works) for the entire duration of this charge, taking many pictures with my camera and uploading them to facebook. the results were nothing short of magical

thanks again for all your hard work, franco
[Nexus S Android Development] franciscofranco:
BLX mod already does that... Charges 96% but the remaining 4% is just cosmetic.
[Nexus S Android Development] ciwek90:
can i use this on rooted stock 2.3.6 rom?
[Nexus S Android Development] franciscofranco:
Yes.

Gogo update. I need a lot of feedback on this one, specially on the battery side and other bugs that might happen. The more feedback the better because it might help Ezekeel to improve his mods - that is the main priority. I need bug reports to include Rom version and phone version, if it's i9020 or i9023, otherwise it's useless.
[Nexus S Android Development] caleb1783:
new version is up~!
[Nexus S Android Development] al_madd:
I9020T

CM 7.1

So far so good...LIVE OC 10%...

previous version was terrible for my phone...SOD several times, reboots about 5 times....
[Nexus S Android Development] akshayf:
is the new lazy+ govrnr included in this release ?
[Nexus S Android Development] tylercarter:
Read the op again...
[Nexus S Android Development] akshayf:
Couldnt find it....would u be so kind to quote it ??
[Nexus S Android Development] Flying Fox:
Seems like changes of the lazy govenor, but no hint for a lazy + ...
[Nexus S Android Development] tylercarter:
All the latest bugfixes and implementations from Ezekeel including...yada yada yada

Just sayin
[Nexus S Android Development] franciscofranco:
Lazy+? What the hell are you guys reading? No one ever talked about lazy+, there is only lazy with the latest fixes from Ezekeel.
[Nexus S Android Development] Flying Fox:
When I open the path "/system/bin/sh" I only find "hyroglyphs" and no possibility to change any oc_value. I only find it in the path "/system/etc/init.d. There are two files: 92kernelconfig and 92kernelconfig.bak. When I set the oc_value of "92kernelconfig" to 120, I cannot see any changings under SetCPU. Obviously this is the wrong path ?

And @franciscofranco: thx for the new release!!!!!!

Just answered a question :)
[Nexus S Android Development] MultiCulti:
thaha ... i also didn´t understand xD

farnko, i switched now form MIUI to CM ... how can i set LiveOC now temp.? i don´t have the 83aroc and 92kernelconfig in the init folder :confused:
[Nexus S Android Development] franciscofranco:
I don't want to be rude, but everything you want is in the first post, I hate to repeat myself all the time =/
[Nexus S Android Development] MultiCulti:
:eek:

NONO .. you just have to change te 83aroc and 92kernelconfig to this settings ... the bak is just the backup file ...

and if you use this scripts, SetCPU isn´t working ;)

---------- Post added at 05:30 PM ---------- Previous post was at 05:30 PM ----------

sorry sorry fanko ... i´m usually reading very exact ... but i didn´t find the information :mad:

sorry again
[Nexus S Android Development] jodtalingchan:
Hi Franco, just flashed the newest one and to be honest it's faster than 27oct indeed. feel very snappy and responsive. Will report back again. Using lazy with 440/1100.

I really appreciate that you share this with us. Anyway that I can contribute to your work? Many thanksss
[Nexus S Android Development] skinniezinho:
Thanks for the update Francisco!It's the "bolinho" of 1 November for the Portuguese guys?:P

Well guess I broke a personal record:2908 in quadrant (2nd round.Latest English MIUI,1000mhz-1000mhz-performance, no overclocks at all.

With the previous kernel I had 2400-2600 I guess.

Seems fine for a rom like miui =)

THanks one more time!

edit:ran again with smartass v2: 3266!!!!
[Nexus S Android Development] MultiCulti:
OK franko ... i used 99complete in init folder for the live oc :D
[Nexus S Android Development] mike216:
Sorry franco I called the lazy with all the special tweaks to it lazy + when taking about it at different times didn't mean to confuse anyone :)

Sent from my G1
[Nexus S Android Development] mike216:
Could you point me to where you found it ,and would that make live oc stick

Could you tell is how to enable through that folder :)

Sent from my G1
[Nexus S Android Development] franciscofranco:
If with contribute you mean helping me with code etc, the best thing you can do is report back with detailed information, either if it's good or bad :)

Glad you like it. If you want battery backup go for Lazy, don't forget it ;)

Nah no problems at all eheh