yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] :
If i don't personally use it, I'm not adding it. This is a personal kernel, I'm just sharing.

Hopefully the kernel developers here will all soon add mtp too, then the community will have more options.
[Nexus S Android Development] technogravy:
if you see fit try adding cfq scheduler, I've found it to be pretty good. I find deadline a bit laggy at times
[Nexus S Android Development] DaXmax:
Actually, its not that laggy. Im using ondemand + deadline + 1000/100 + BLN on + DI on, on my broken Nexus S. :)
[Nexus S Android Development] caliban2:
True, no lag at all with deadline and smartass. :)

v0.9 finally rebooted during last night, took at least 14 hours. now trying 0.9.1. min-cpu is still set to 200 with every reboot.

Bedalus, do you by any chance use touchwake? :)
[Nexus S Android Development] tommy0823:
@bedalus, do you think you'll ever make a gnex kernel? I gave the wife the ns4g, and definitely miss the stability of these things.
[Nexus S Android Development] :
Bit of a daft question tbh.

It's not, because I actually look at stuff before mindlessly merging. Commits for erratas are more likely to resolve issues than create them...don't you think?
[Nexus S Android Development] pan1980:
bedalus have you modified lcd voltage?

i see and more kernel modifying lcd voltage to lower states.
[Nexus S Android Development] :
Of course he is. Once a copycat...

Personally it's the last github in the world I would look at for inspiration.

The likelihood of that is extremely slim...

I would suggest you take a look at the code you have merged which isn't from mainline. Or your own changes. That will more than likely be the cause of the reboots.

When I said mainline caused subtle issues, I meant things like boot slowdowns and laggy performance.

I don't believe I can tie any reboots down to mainline, except perhaps the very rare PVR reboots, but equally that could come from a bug in the driver.
[Nexus S Android Development] :
I looked at them, but tbh had no idea what i was looking at. Have you seen my bln tweak? That should give you an idea of the code I'm capable of, i.e. fairly basic.

All i know about the mainline is that my phone went reboot crazy when i hit .40

Also, a few months back i tested mathkid95's kernel and he had reboots when he merged in .35

I know this isn't necessarily the mainline, perhaps just some incompatibility because the mainline might have conflicted with his previous tweaks.

I also know the mainline is there to solve issues, which is why I'm determined to follow it, so I've really no idea where the reboots were coming from. So far, since rebasing on stock, i haven't had any.
[Nexus S Android Development] :
No, i don't believe in UV. Check my battery benchmark thread, check my signature for the link!
[Nexus S Android Development] granets:
Here is a suggestion. Why don't you, bedalus and you thalamus work together on a kernel? I mean really work together to make the best one out there. You are both such capable devs that I think the result will be awesome
[Nexus S Android Development] :
I'd only slow him down. Besides, we want different things.
[Nexus S Android Development] sidnoit22:
Well doing great with Marmite 4.2.
[Nexus S Android Development] Imppy:
My phone freezes when coming from sleep sometimes with 4.2...I'm on paranoid android
[Nexus S Android Development] JokerAce:
I think it's the Database that slows things down over time. Well, I get this explanation from supercharging. I do supercharging's "detailing" script and the phone got snappier again after it, without the need to reboot it.
[Nexus S Android Development] :
See if you can collect a last_kmsg
[Nexus S Android Development] polobunny:
I got a freeze this morning with knzo CM+, just like you guys get. Screen turned black, couldn't bring it back on but soft keys reacted by lighting up. You know this is looking like a rom bug more than a kernel bug. Unless it's about one of the kernel mods. :banghead:
[Nexus S Android Development] :
I'm not sure yet. There's been no compelling evidence either way. I've had no problems on either of the last two versions.

In between the released test versions there are usually about ten incremental versions where i test out any code i add. These incremental versions usually have issues, because my code is faulty. However, if i make a mistake, normally there is a immediate reboot, and a last_kmsg that points squarely at my code and laughs. When that stops happening, i release!

These sporadic freezes are some other sort of problem entirely. There's something peculiar about a non-reproducible fault.

I keep an eye on all the kernel threads, and issues are being reported everywhere. It might just be jellybean. New rom, new code? Thalamus is pointing at the new gpu driver code. It might be that this driver gets patched, then perhaps everything will just work tm.
[Nexus S Android Development] CrackerTeg:
I know in the OP it says to not flash the bigmem patch if not having trouble with camera but I did anyway. I don't seem to be getting any lag after doing so and everything is behaving properly. I didn't have to but I felt the phone bogging down after 50 or so hours like others have reported. I'll report back if I experience the same thing with the bigmem patch.
[Nexus S Android Development] :
Interesting. See how it is in another 50 hours!
[Nexus S Android Development] CrackerTeg:
I'll let you know. If it matters, I'm running BAKED BlackBean with your 4.2. It feels as snappy as my old ICS combo of Rascream and Matr1x 22.0. Also, my free memory with the patch is identical to what I would get with that old combo. Never had to reboot to regain that snappy feel. I'm hoping I get the same behavior with what I did that I wasn't supposed to do. lol
[Nexus S Android Development] polobunny:
Yeah PVR bug. With my less than expert answer I can imagine that being true, since I'm pretty sure I could adb into the phone. Can't really adb unless you're near a computer though, so I haven't checked yet and I pretty much just end up pulling the battery. Irritating stuff though. :mad:
[Nexus S Android Development] :
ioplkj13 has been telling be to put those libraries into the kernel zip since ages ago...! If things are still running smooth for you in 50 hours, I'll put them in.
[Nexus S Android Development] Articudos:
Lol, How can I make reboot?

V4.3 test2 has no issues now..

BLN on, no blinking, BLD on, ondemand, deadline.

About the libraries,

No effects i guess.. just placebo:p

But, I don't think It won't update..
[Nexus S Android Development] :
Did you try blinking in BLN? It's got a new blinking pattern. It'd be nice to get some feedback about that :)
[Nexus S Android Development] Articudos:
Working great, I send myself sms and mms, (blinking 300times)

It blinks.(irregular):)

Quite nice:)

About my suggestion-

Nevermind. I just wondered those-related bug reports will bother you;)
[Nexus S Android Development] :
Those files are designed for ICS anyway, right?
[Nexus S Android Development] Articudos:
I guess not. Maybe kalim made new-libs for JB..
[Nexus S Android Development] xjerlzx:
Up time 50hrs! V4.2. Slimbean
[Nexus S Android Development] leap_ahead:
wow this bln pattern is very cool !!! also no problem
[Nexus S Android Development] caliban2:
v4.3 test2 doing fine so far. and yeah, that blinking pattern is nice. :)
[Nexus S Android Development] DarkhShadow:
On v4.2(yeah I should update so sorry if this has been fixed/rom issue) and got a completely random instant reboot(didn't hang, just rebooted) while updating a app and scrolling market comments

http://pastebin.com/25ZccsS6

Sent from my ice cream powered Nexus S
[Nexus S Android Development] linuxxp:
v4.3 test2 behaves well and stably. A few hours of playing games, music and GPS navigation. There are no delays or issues. And new blinking pattern is so cool :)
[Nexus S Android Development] :
Hello, unfortunately this is a log from cwm recovery.
[Nexus S Android Development] :
Huh. Has anyone else had a bug where you can't wake up the phone?

I wasn't able to pull the battery because I was busy. I then later tried to wake the phone, and it was fine, and it hadn't rebooted. Weird.
[Nexus S Android Development] leap_ahead:
No problem here for not many hour .
[Nexus S Android Development] :
bedalus hello, I'm testing kernel 4.3 with MIUI jb and everything works fine, no such problems for the moment
[Nexus S Android Development] towelboy:
V4.3 test 2 running fine no problems!
[Nexus S Android Development] CrackerTeg:
About 14 hours down and just as snappy as after a fresh reboot bedalus. Free mem still the same as before with the mem patch freshly added.
[Nexus S Android Development] shivasrage:
[/COLOR]

hello bedalus

i also had something weird...

kernel: 4.3 test 2, DX Stock ROM

i had a freezing issue after making a call

softkeys are freezing, also i couldn't swipe display, i have to turn display off and on.. then issue was eliminated.

S.R.
[Nexus S Android Development] subscope:
I would like to have BLD and BLN working but it doesn´t work and i don't know what to do more :/

I leave here a script that i made and it still doesnt work... I am using CodeName Android ROM maybe ROM side?

#!/system/bin/sh
echo 1 > /sys/class/misc/backlightdimmer/enabled
echo 5000 > /sys/class/misc/backlightdimmer/delay
echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 600 > /sys/class/misc/backlightnotification/max_blink_count
echo 100 > /sys/class/misc/batterylifeextender/charging_limit
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 20000 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo 95 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 1 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo 0 > /sys/devices/system/cpu/cpufreq/ondemand/powersave_bias
echo deadline > /sys/block/mtdblock4/queue/scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler
echo 100 > /sys/class/misc/liveoc/oc_value
echo 1000000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 6 > /sys/class/misc/backlightnotification/max_blink_count
[Nexus S Android Development] :
It might be that the ROM doesn't support init.d, or perhaps you need to check the permissions of your script. What filename do you use?
[Nexus S Android Development] DarkhShadow:
What? That's my last_kmsg? Is that where cwm(I use twrp) places the log?

Sent from my ice cream powered Nexus S
[Nexus S Android Development] subscope:
I think this ROM supports init.d: http://xdaforums.com/showthread.php?t=1839249

Permissions i check in Read and Execute ALL and in Write just OWNER ;)

I am using this file, see in attachement pelase ;)
[Nexus S Android Development] :
Yeah, cwm places it right smack on top.
[Nexus S Android Development] :
Group and others should have read/write.

Owner should have read/write/execute
[Nexus S Android Development] subscope:
Thank you dude i will try. But my script is good right? Without errors?
[Nexus S Android Development] :
You might want to lower the max blink count to a smaller number, because every blink is now worth 10 seconds.

A max blink count of 6 would be one minute.
[Nexus S Android Development] subscope:
One more time dude thank you ;) I will put 1 thus it will blinking 10 in 10 sec ;) i will flash your kernel again to test :P

Editing: Dude it really doesn't work for me :/ Don't know why :S I send a message for me and nothing :S

There's something that i can do?

Another question to install your kernel i just have to enter in recovery and install right? Nothing more?

Edit2: If i activate BLN in options of rom it works but with srcipt it doesnt work at all :S
[Nexus S Android Development] :
Yeah, just flash in recovery. I think you did it already.

Your script looks fine. If the permissions are correct the only thing I can think of is that CNA does not support init.d
[Nexus S Android Development] subscope:
Strange cause this rom have much scripts inside init.d

Can you send to me your script? if you have there offcourse ;) just to test please

thank you
[Nexus S Android Development] :
I also did a quick search in the CNA thread, could find no posts referring to init.d, so I guess that means no other users are having this problem.

Here is the script I use.

EDIT: Sorry if I forgot... did you say you don't use NSTools?
[Nexus S Android Development] subscope:
I used before NSTools but already unisntall that ... Neither your file works :/ Maybe the problem is in the ROM? What Rom you use?

Thank you

EDIT: Dude really sorry like i said it have and internal BLN control in ROM so BLN script just works if i have internal BLN activate... So i enable internal BLN and it works like a charm :P Really thank you and sorry about that :) BTW nice kernel :)
[Nexus S Android Development] gabling23:
hi i've got two question to ask but i don't know if they are kernel-related...

1) From today I've got the minimum freq stuck at 200mhz; i know that nstools could cause this problem but i used it only to take a part of a script (where i deleted all the lines except for those that regulate the bln and the bld) that i've pasted in the file 00check in the init.d folder; quite similar to the way that is described in the guide in te OP.

Now that i have uninstalled nstools i use setcpu to set the min and the max freq and even if i set the min freq at 100mhz it shows that the min is 200mhz..

2) Can someone explain me what cause the battery consumation of "android system" and "android OS" because i have a high battery drain from this 2 voices (for example now i have 32%screen 17% android system and 14% android OS)..

P.s.I'm using slim bean with the 4.2 version.
[Nexus S Android Development] :
Thanks for letting me know. I also still have not had any reboots. :D

I've been busy building several different versions of the same kernel, just with different versions of the mainline patch level. There doesn't seem to be any performance impact to me. I'm happy 3.0.34 is totally fine. I'm reasonably happy 3.0.38 is fine. I'm running 3.0.41 at the moment, but I may hold off pushing out a trivial update because thalamus may be able to release IDLE2 version 3.000 in the near future.

I finally got around to building a MTP and non-MTP version of the kernel with IDLE2 earlier today, and did some amp measurements (with a analogue multi-meter. Not high tech, but good enough to see some things more clearly). Unfortunately, as thalamus had already pointed out, IDLE2 and MTP are not compatible. So in the future there will be three versions, one for Stock OTA, one for MTP, and one for IDLE2
[Nexus S Android Development] :
Don't worry about your percentages. As long as you can get about 4 hours of screen on time in a day, your battery drain is normal.

It'd help to get your min frequency down to 100 MHz. Get the cpuSPY app (free) in the play store, just to make sure setcpu is telling the truth.
[Nexus S Android Development] gabling23:
It seems that the problem of the minimum freq is solved (I only rebooted the phone) even if it isn't stuck at 100 MHz but it change continuously between 100 and 200.

I can easily get 4 hours of screen time in a day but I guess that if I could have that values lower I could get 5 hours maybe..

Sent with Tapatalk 2
[Nexus S Android Development] polobunny:
I don't get the big fuss about mtp. It's not faster than normal mounted usb, its support is crappy on both Linux and mac and ends up being a pain with other more important kernel mods. Why is everyone touting it like it's some kind of holy thing? The only upside I can see is that the system still gets access to the sdcard even when "mounted" on a pc.
[Nexus S Android Development] xjerlzx:
Dude mtp is for windows. Majority of users use windows. Please read first page of this kernel
[Nexus S Android Development] temo2k:
I tested copying a folder with MTP vs normal.

MTP = ~30 seconds

Mass Storage = ~2minutes 30seconds

Yeah, it's a little wonky but I'll stick with MTP. Switching back is just a quick reboot of the phone anyway.
[Nexus S Android Development] asphantix:
So no version for Stock OTA with IDLE2? I'm really excited about thalamus IDLE2 :)

MTP will work well with linux. You'll need jmtpfs. See here: http://research.jacquette.com/jmtpfs-exchanging-files-between-android-devices-and-linux/

Or you use go-mtpfs.

But personally I couldn't care less about MTP.
[Nexus S Android Development] :
Thanks for the info about MTP on Linux.

You are right about the stock OTA, I will need to upload 4 versions!
[Nexus S Android Development] technogravy:
Sorry for the noob question, but how much more does blinking drain the battery as compared to non blink bln? I've never used a blink
[Nexus S Android Development] :
I've not tested it, but it keeps the CPU awake. Non blinking bln just wakes up to turn the lights on then goes back to sleep.

If you want to save power set max_blink_count to 0, and final_blink_state to 1. This does mean that if you get a notification in the night, your leds will be on for hours. That probably doesn't drain that much, although I've never properly tested it
[Nexus S Android Development] Jamalsid:
Bedalus, thanks for the great kernel. I have never experienced such low idle drain as with your kernels.

A quick question if you don't mind. Can you see anything wrong with this script?

#!/system/bin/sh
echo fave > /data/local/tmp/test.txt;

echo 1 > /sys/class/misc/backlightnotification/enabled
echo 1 > /sys/class/misc/backlightnotification/in_kernel_blink
echo 600 > /sys/class/misc/backlightnotification/max_blink_count
echo 1 > /sys/class/misc/backlightdimmer/enabled
echo 30000 > /sys/class/misc/backlightdimmer/delay
echo 0 > /sys/class/misc/deepidle/enabled
echo 96 > /sys/class/misc/batterylifeextender/charging_limit
echo ondemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo deadline > /sys/block/mtdblock4/queue/scheduler
echo deadline > /sys/block/mmcblk0/queue/scheduler
echo 1200000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

I can't get this to work. If there is nothing wrong with the script then I can only assume that Kalim's CM10 builds do not currently support init.d scripts.

What ROM do you use, out of interest?
[Nexus S Android Development] :
If permissions are correct then the only problem is with the ROM
[Nexus S Android Development] Jamalsid:
Thanks for the quick reply. What ROM are you using out of interest?
[Nexus S Android Development] :
I'm on euroskank's aokp from 15th August, until krarvind adds a brightness slider in the notifications.
[Nexus S Android Development] Jamalsid:
Kravind? Is that slimbean?
[Nexus S Android Development] :
Yes, that's the one
[Nexus S Android Development] alen1901:
I have 166 hours of mobile uptime with CNA 3.2.1 and bedalus 3.5 kernel(3.0.40 mainline). DI on but i didnt use it much. Great stuff. :D

Sent from SpeedMachine i9023
[Nexus S Android Development] :
I guess it's possible that the reboots people were experiencing were ROM issues. I'm at 12 hours on 3.0.41 and it seems fine
[Nexus S Android Development] sdhanjal15:
Bedalus!!! You need to update your colors to morics. He's changes them.
[Nexus S Android Development] CrackerTeg:
Bedalus, 36 hours of uptime with "unnecessary" bigmem patch. Still just as awesome. I've been tempted to reboot into recovery to flash different goodies but holding off for testing purposes of the patch. I think its safe to add the patch into the default kernel IMO. One other thing. you're kernel has given me the best battery life by far of the JB kernels I've tried. Running your modded smartassv2 governor.
[Nexus S Android Development] vis80k:
on slimbean now. it supports longpress on status bar to set brightness or hold and slide to your preferred brightness. like cm10 status bar brightness control.

only features I miss are volume wake/media skip and lockscreen customization.
[Nexus S Android Development] technogravy:
For some reason it seems like the Android OS battery drain only affects me.. I've tried multiple roms and different versions of bedalus kernel and the same annoying drain (3.5 doesn't have any drain though)

I'll be on matrix till an update in this kernel plays nice on my phone..

This kernel is otherwise just great.. I've noticed the Android OS keep awake its only with BLN enabled.
[Nexus S Android Development] polobunny:
So apparently some people say the slowdowns related to RAM never going back to what you booted with is only with CM10 sources. So jellybro being real popular you'd get that, same with official CM10. Other roms based off CM10 would get this. CNA would be good since it's from AOSP...

Well aren't you a smartie. It's developped by Microsoft.

Doesn't explain what all the fuss is about. It's a feature that was good in ICS to work around the slow file transfers. I don't seem to have slow transfers anymore in JB, and MTP implementation is keeping nice stuff like IDLE2 from working. The support of MTP is absolute s!@# on Mac and Linux yet everybody seems to like it. I just don't get it, so I'm wondering if I'm missing out something a bit less obvious than "mtp is for windows"...
[Nexus S Android Development] rrohanjs:
i see noop is removed, problem is i always thought smartass v2/noop was the best combination for battery or ondemand/deadline

whats the best combo now for battery ?
[Nexus S Android Development] CrackerTeg:
I'm running smartassv2/ deadline. Going on 32 hours with 2 hours of screen time. Sitting at 35% now. Mostly on wifi but I've only dropped 20% since I've been off wifi at work in 6 hours.
[Nexus S Android Development] linuxxp:
I'm with v.4.3_test 2 and now I have random reboot. Here is last_kmsg.txt

In this log there is only one line that repeats: [ ] s3c-i2c s3c2440-i2c.0: i2c_s3c_irq_nextbyte: called in STATE_STOP

Had a two conversation and then I used Advanced Task Killer, to kill unnecessary apps and 10 seconds after that the phone restarts himself.
[Nexus S Android Development] :
I've seen this before.

I don't know what causes it, but it's something to do with audio. My 100% guess is that something is asking for more audio data, which isn't allowed in state stop. Unfortunately I have no clue if this is a kernel bug!
[Nexus S Android Development] :
There was a flaw in the tests i did. Deadline and cfq are both fine choices.
[Nexus S Android Development] :
I'll provide a version without mtp so idle 2 works
[Nexus S Android Development] temo2k:
Have you actually tested it? The speed difference massive. If you're able to get anywhere near the same speed let us know how you do it and then we can benefit too.
[Nexus S Android Development] CrackerTeg:
Bedalus, now at 46 hours of uptime and free memory has dropped pretty low as before. Speed has degraded but not as bad as before. Running black bean plus settings mentioned before.

Edit-I take back what I said about memory. That moment I looked in settings, it dropped drastically low. I just checked again and it was back up to par. I don't have the lag reported by others when at this uptime. It does lag but slightly. Sitting at 13% battery which means a ridiculous battery life.
[Nexus S Android Development] polobunny:
Last time I transfered music it was decently fast. Do not recall the numbers, but I recall saying "looks like transfer speeds are back to normal". I'll try to check later.

QUOTE=bedalus;30492875]I'll provide a version without mtp so idle 2 works[/QUOTE]

It's not so much that than knowing if it's still really needed.

---------- Post added at 08:42 PM ---------- Previous post was at 08:33 PM ----------

Just tested while my chicken was cooking. Turns out im wrong, 1.2mb/s write speed. I cant believe this is still applying to JB...
[Nexus S Android Development] xjerlzx:
"Well aren't you a smartie. It's developped by Microsoft."

I'm trying to tell u it doesn't work well on non windows platform so stop complaining =]
[Nexus S Android Development] polobunny:
Which is annoying considering there's actually other people than just Windows users. I know all about that, but that's aside the point really.