yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kokwei:
Mind sharing what wasn't working so well on 2.4?
[Nexus S Android Development] alienmind:
@Ezekeel

On 2.5 logger.ko was separated on a kernel module. That's ok, but I still need logcat

What do we need to recover logcat? I just insmodded logger.ko /dev/log/* appeared, but logcat is empty. What else is needed?

Thx
[Nexus S Android Development] caliban2:
Reboots during standby.
[Nexus S Android Development] djjonastybe:
Ezekeel I may have found solution for bluetooth:

'bt_disable()' in 'system/bluetooth/bluedroid/bluetooth.c'

that function handles disabling bluetooth

It should be somewhere in there. I accidentally came across this Googling.

---------- Post added at 06:28 PM ---------- Previous post was at 06:25 PM ----------

did you try logcat in terminal?

It may have to be enabled in the init.rc as well I think... Or started.

Also make sure logcat doesn't save to /dev/null

That's all I can think of

To get to the init.rc try with Android Kitchen
[Nexus S Android Development] alienmind:
I'm doing from linux box:

adb shell
root@android:/ # logcat
Unable to open log device '/dev/log/main': No such file or directory
root@android:/ # cd /system/modules
root@android:/ # insmod ./logger.ko
root@android:/system/modules # lsmod | grep log
logger 1052950 0 [permanent], Live 0xbf03a000 (PC)
root@android:/ # logcat

And no output

My init.rc has adb starting but no logcat as I understand it is not a service, but a command run through adbd

Thx!
[Nexus S Android Development] stewarta:
Deep Idle

Deep idle patch was left out. This is not the same as deep sleep state.
[Nexus S Android Development] arifhn:
You must do insmod on boot

Set it on init script
[Nexus S Android Development] nexusphone:
flash logcat_script.zip in CWM

/system/etc/init.d/61logcat

#!/system/bin/sh

insmod /system/modules/logger.ko
[Nexus S Android Development] nexusphone:
We are waiting for the fix ;)
[Nexus S Android Development] AnthonyAldrete:
Question when using nstools and apply live oc to 110 with lazy gov and deep idle off with the screen off freq on do I still have to go in and adjust the voltages across the boared or just for the freq that I am currently at ? Like for instance, if I'm at 1100mhz max and 110mhz min, do I have to change all the voltages ?

The reason I ask is because today I had my phone at those frequencies above but with deep idle on and lazy gov. Applied and also shut off max freq on as well and was running smooth all day . Was streaming Pandora all day while working but I had gotten a phone call and in the middle of the phone call I couldn't hear the other person after about 1 min then looked at my phone and saw the google screen with the unlocked pad lock . My phone seemed to crash I didn't understand why. So when the phone booted back up I put everything back to how it was when I first flashed the kernel and I didn't notice it again . Currently I'm on stock ICS with gladdos 2.5 and not sure if this is important but I put my new battery I bought from amazon which is a 3200 ma seidio battery .

PS. Sorry for the typos I didn't feel like going through and editing all of them because I got lazy :) hopefully you guys understand it lol
[Nexus S Android Development] nexusphone:
Live OC & Deep Idle are essential to Nexus S!
[Nexus S Android Development] aLNG:
i miss ezekeel :(
[Nexus S Android Development] DynamicRam:
some people experience this problem too , just lower your LiveOC to 105 or 100 for now
[Nexus S Android Development] bmt25:
tun.ko

hey guys, does this kernel have tun.ko preinstalled?
[Nexus S Android Development] kokwei:
Just had the same issue today with less than 24 hours of uptime. How's 2.3 working for you?
[Nexus S Android Development] kokwei:
Can you share the 2.3 binaries?
[Nexus S Android Development] caliban2:
Sure

http://db.tt/CgTEmpJb

2.3 cfs is still stable for me, and working didle makes a difference in batt-drain. (25 hours and counting)
[Nexus S Android Development] djjonastybe:
I would like to report that Facebook for Android and/or Mercury MSN Messenger are preventing deep idle to work properly.
[Nexus S Android Development] kokwei:
2.4 bfs with BLN, no deep idle, ondemand governor, no OC (100/1000) on i9030 rebooted after few hours of uptime.

Anybody having reboots on similar configuration?
[Nexus S Android Development] got2best:
I notice something and idk if it was juat my phone but after listening to music for about 30min+ screen off my phone would freeze this happened 3 times.. the phone was plugged in. Running latest cm9 and 2.5cfs
[Nexus S Android Development] alienmind:
I'm on the same config and listen to music about 2 hours every day during workout, no reboots. but i still have some other random reboots while the phone is idle on the table

i found extremely useful to disable pin so i get the line back as soon as it reboots. i also wrote a small app that notifies me at boot with date and time, so i can see exactly when did it happened.

Swyped from my Nexus S
[Nexus S Android Development] suomaf:
Happy new year guys. Hope 2012 brings you happiness and health. Hope it also brings you otg and other super ezekeel mods! Have a good one Else.
[Nexus S Android Development] seriosbrad:
2.5 BFS, anyone have issues loading the sound module in Voodoo Control?
[Nexus S Android Development] DaX05:
Just had that reboot during a 2+3 min phone call on 2.4 bfs.

Beamed from my Nexus S
[Nexus S Android Development] mike216:
This is the only ICS kernel that's completely stable without issue for me! **** even one kernel I tried wouldn't boot and when I tried to reflash another kernel it wouldn't boot I had to do a full wipe format system and boot before I could get back up and running, that's what I get for being curious and trying other kernels when I didn't need to because glados is flawless and everything works fine

BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] mike216:
Happy new year Ezekeel and my precious fellow community members! I wish you all and your families to be happy with good health!

BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] astmacca:
Happy new year every body!

Tried Glados 2.5 on stock ICS. Reboots during calls so am back to stock at the moment. This has generally been a really good kernel for me on previous versions though.
[Nexus S Android Development] nexusphone:
Happy New Year!

Ezekeel, where are you? WIP?
[Nexus S Android Development] caleb1783:
have u liveoc?

Sent via Divinus Nexus S...
[Nexus S Android Development] DaX05:
Yeah is disabled it until the next rekease.

Beamed from my Nexus S
[Nexus S Android Development] phone_user:
Ezekeel'd been on vacation the last couple of days. :)
[Nexus S Android Development] Ezekeel:
I have released GLaDOS V2.6.

This version fixes the problem of the CAM module being active all the time preventing DEEP IDLE from being used.

The problem of BT not being properly disabled and thus preventing the DEEP IDLE state with TOP=OFF of being used still exists. This is a ROM problem and Jonathon Grigg is looking into it. So far he found that this is probably a feature of ICS to save a little time when activating BT.

It seems this feature can be deactivated by changing the bool variable com.android.internal.R.bool.config_bluetooth_adapter_quick_switch to false which can be found in frameworks-res.apk or frameworks/base/core/res/res/values/config.xml in the source. Jonathon told me this can either be achieved by extracting that apk, changing that value and re-compile it or by changing it in source and re-compile the ROM. He is currently working on modifying that apk for the ICS stock ROM for testing, but since this will only work for the stock ROM you might want to contact your favourite ROM dev and let him know of this.
[Nexus S Android Development] boostern:
Happy new year Ezekeel!
[Nexus S Android Development] DaX05:
Thank you, sir!

Beamed from my Nexus S
[Nexus S Android Development] xontax:
Awesome, happy new year!
[Nexus S Android Development] nexusphone:
Ah...
[Nexus S Android Development] mike216:
Finally trying bfs version when flashing 2.6 and its twice as fast as cfs! Nice work eze and happy new year to you and the community, thanks

BEST DAMN PHONE/TABLET BECAUSE WE HAVE THE BEST DAMN DEVELOPERS!
[Nexus S Android Development] phone_user:
v2.6, Still "reboot while calling" :confused:
[Nexus S Android Development] jodtalingchan:
Same here ...
[Nexus S Android Development] jodtalingchan:
I'd love to try 2.4 BFS. Could anyone share?
[Nexus S Android Development] nexusphone:
the most rapidly patched, AOSP+ rom :)

Jonathon Grigg was right about that!
[Nexus S Android Development] sspikey:
Same here,

was getting reboots on call with 2.5 BFS and again with 2.6
[Nexus S Android Development] gonintendo:
from a few pages back:
[Nexus S Android Development] caleb1783:
it reboots w liveoc; I tried 110 & 105. both reboots during callin... usin stock volts as well...

but ics w glados seems to be fast even without liveoc... even at 800/200...

Sent via Divinus Nexus S...
[Nexus S Android Development] caleb1783:
but didle doesn't seem to work w 2.6 as well. do we need to uninstall/close gtalk as before?

Sent via Divinus Nexus S...
[Nexus S Android Development] caleb1783:
oh sorry.. this is BT bug... I thought ezekeel was referin to top on..

Sent via Divinus Nexus S...
[Nexus S Android Development] nexusphone:
BT patch enabling deep_idle :)

but on ICS, reboot while calling still not fixed :( maybe due to LiveOC or Deep Idle?
[Nexus S Android Development] alienmind:
After flashing v2.6, on first boot, ICS started to prefetch apps or whatever it does after flashing. I have like 64 apps, no more. The phone starting to overheat clearly. It could never finish the task. It needed 3 reboots to finish prefetching all the apps.

It happened only on stock ICS. Didn't happen on CM9.

Any ideas?
[Nexus S Android Development] TrueYears:
2.4 has been the best one yet I hope 3.0 is good
[Nexus S Android Development] caliban2:
Just had SoD with 2.6 cfs. That's new... :screwy: apart from that it was stable for about 4 hours - not that this tells anything... ^^
[Nexus S Android Development] cahir_cz:
hi, ive out for a while. any progress with the usb otg?
[Nexus S Android Development] endursa:
i recompiled the framework-res.apk with the mentioned bluetooth adapter quick switch set to false and now my deep idle status shows TOP=OFF usage :)

please be aware that i only tested this file on the OTA 4.0.3 IML74K Rom!

just Flash from recovery!

any other rom on the same base could work with this zip file, but i don't assist in repairing any other roms!

To get the original framework-res file from your Rom back just extract the framework-res.apk file from the original rom zip and replace the one in my uploaded package!
[Nexus S Android Development] djjonastybe:
I am using pixel ROM. Apparently that one has that switch as well. Or maybe not. Anyway I am getting good TOP=OFF values there.

I am using:

100-1000

lazy

deep idle on

live oc 100

lazy screenoff_maxfreq off

bln on

Battery life is perfect.
[Nexus S Android Development] Harbb:
I can confirm this is working as described in OTA 4.0.3 with GLaDOS 2.6 BFS on an i9023, top=off usage is back on, good work and thanks endursa.

Maybe I missed something, but i had working top=off (when BT/music/GPS is off) in 2.4 CFS and working top=on (when BT/music/GPS is in use). That is, it logged expected times for each. I have not changed my ROM, though why is bluetooth now the culprit for lack of top=off while entirely idle in 2.6 without the recompiled framework apk?

As always, many thanks for the updates Ezekeel, it just gets better and better each version. Latest BFS is noticeably quicker than all the previous versions i've tried.
[Nexus S Android Development] endursa:
afaik ezekeel disabled the bluetooth check in 2.4, but didn't in 2.6! that's why now Top=OFF is used correctly!
[Nexus S Android Development] Ezekeel:
Exactly.

Good work with the patch. Works perfectly here. Also convenient packaging - I was able to flash this otg. Maybe you could see if you can reduce the size by using a binary patch instead of the finished apk.
[Nexus S Android Development] darksine:
Tried to install this on my ns4g with oICS v43 but failed because it looks like the install is looking for crespo only . Any chance you could remake this for the crespo 4g?
[Nexus S Android Development] 93ae8074:
Anyway new finished apk is 300 KiB less than ROM's one. :-)

Cheers.
[Nexus S Android Development] endursa:
there is a reason for that, because the file is only for ns 4.0.3 OTA! I'm not sure if your Rom is compatible to my patch...

but I look into that later, the and if needed I can compile a new file for your Rom!
[Nexus S Android Development] darksine:
Oh sorry didny understand your first post and thought that oics was off the ota but I guess its not. Looking forward to your release. Thanks.
[Nexus S Android Development] Pitel:
Logcat

How is the situation with logcat? I read it get disabled since 2.5. Is it true? Because I'm Android developer, I need it. And if it is, how can I enable it again? (I know I have to load some kernel module at init.d, but... which, and how?)
[Nexus S Android Development] endursa:
just make a file in /system/etc/init.d/97logger

content of 97logger:

"insmod /system/modules/logger.ko"

set permissions to rwxr-xr-x

and you got logcat functionality back!
[Nexus S Android Development] CrackDaddy:
So when you say that your bluetooth_adapter_quick_switch_disabled_OTA_4.0.3_IML74K.zip was recompiled for OTA 4.0.3 IML74K Rom, am I correct in thinking this will work on this NexusBeam 4.1.0 Rom? & to just flash through cwm recovery!? :confused: :D Thnx!
[Nexus S Android Development] endursa:
as long as the rom NexusBeam is based on the OTA 4.0.3 update, it should work. BUT any framework modifications that where included into NexusBeam will be reverted, as the patch is pure stock with the bluetooth fix :)
[Nexus S Android Development] CrackDaddy:
NexusBeam 4.1.0

Hi guys, today i am announcing a brand new ICS based ROM for the Nexus S.

The ROM is using the latest stock Android 4.0.3 IML74K firmware and works very smooth! The UI feels very fast because Google implented HWcomposer in the latest build and this gives you overall speed improvements.

By this statement I'm presuming that's a yes! If not, I don't suppose you could compile that patch based on NexusBeam could you!? Perhaps Ezekeel could confirm!
[Nexus S Android Development] xjerlzx:
Deep idle works....
[Nexus S Android Development] CrackDaddy:
We know this, but not Deep Idle (TOP=OFF) stats in GlaDOS 2.6! Always report as: Time (ms)=0 / Avg (ms)=0......................:confused::D

BT switch is not fully disabled by default for these stats to work in deepidle!
[Nexus S Android Development] 91franz:
Which is the difference between cfs and bfs??
[Nexus S Android Development] CrackDaddy:
The difference: http://www.cs.unm.edu/~eschulte/data/bfs-v-cfs_groves-knockel-schulte.pdf

Discussed here: http://xdaforums.com/showthread.php?t=689472 already! ;)
[Nexus S Android Development] Harbb:
Ahh, thanks for the clarification endursa and ezekeel.
[Nexus S Android Development] :
Here's a question. What is the difference between TOP=ON versus TOP=OFF? Is one deep idle state "deeper" than the other? i.e. more battery saving?
[Nexus S Android Development] DaX05:
Pretty simple. When the screen is on & off.

Beamed from my Nexus S
[Nexus S Android Development] xjerlzx:
no... it works.. using 2.6 CFC here..

ics stock 4.0.3 rooted.
[Nexus S Android Development] xjerlzx:
Does anyone know the difference btwn lazy and conservative governor settings? Which one saves more battery
[Nexus S Android Development] maniac2403:
From www.setcpu.com

CPU Scaling Governors

CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies. Most kernels have “ondemand” and “performance.” The availability

ondemand – Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.

interactive – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.

conservative – Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.

performance – Available in most kernels. It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.

powersave – Available in some kernels. It will keep the CPU running at the “min” set value at all times.

userspace – A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.

smartass – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
[Nexus S Android Development] jodtalingchan:
Hi, does BLN work on missed call? Mine is only work with sms ..
[Nexus S Android Development] xjerlzx:
How about the explanation for conservative and lazy governor settings?
[Nexus S Android Development] xjerlzx:
Yah doesn't work for missed calls
[Nexus S Android Development] jodtalingchan:
This feature is really useful. How to make it work for missed call? Any ideas?
[Nexus S Android Development] AnthonyAldrete:
Should I wipe delvik upon flashing this ?
[Nexus S Android Development] got2best:
Yes for sure!
[Nexus S Android Development] Harbb:
Wipe dalvik cache and cache. Always recommended, even though the cleaning script should do it from memory.

Top off and top on is about being in deep idle with music/GPS/Bluetooth ongoing (top=on) or in deep idle without these ongoing (top=off).

For info on lazy, http://xdaforums.com/showthread.php?t=1276092

Edit: also, missed call bln only works with the paid version of bln
[Nexus S Android Development] AeroEchelon:
There is no need since there is a script which does it for you. Wiping it an extra time doesn't make it extra clean.
[Nexus S Android Development] LancerEVA06:
Is there anyway that the 100% battery tweak could be put into this Kernel?
[Nexus S Android Development] jithinsarath:
Huge Lag After this Kernal

I installed this Kernal last night just before going to sleep.

I did a cache & Dalvik wipe before installing. Today morning, I see that teh OS has slowed down significantly.. It is literally crawlllllling... :)

I haven't modified any settings after installing the Kernel. I now moved to the Simple Kernel (Stock + BLN + Voodoo) and the phone is back to normal.. Strange :P

Thanks, J
[Nexus S Android Development] SPVlover:
hi all.

just wanted to say thanx to the op and to all participants in this thread.

The kernel is great and the tips and tricks given work well.

thanx for that.

since i was getting reboots (randomly) during calls, i have decided to change some settings.

previous:

liveoc 110

max1100mhz

didle on

lazy

i now changed to:

liveoc 101

max 1224

didle on

lazy

it seems to work. no more reboots. liveoc seems to be the culprit for the reboots for me.

thanx and keep those updates commin ;-)
[Nexus S Android Development] panousis:
Thnx for your work Ez !!!

I use glados 2.6 cfs and have no problems without using oc live.

But I have noticed that there is a flickering when I turn the screen off. Does anyone know why?
[Nexus S Android Development] Uni7:
Has anyone had any luck with USB OTG? Got a cable but nothing appears to be working (tried with USB keyboard and flash drive)
[Nexus S Android Development] nexusphone:
@Ezekeel

How about adding this governor - lulzactive - to GLaDOS?

https://github.com/tegrak/lulz-kernel_gt-i9100/tree/master/kernel/drivers/cpufreq

and The SIO scheduler

https://github.com/nubecoder/nubernel-2.6.35/commit/d0e570f0f25859a5ccf70b4949dff5400a3f3182#L0R57
[Nexus S Android Development] ale.landra91:
Can somebody explain me how schedulers works and what they are? I see two option but i dont know the effect
[Nexus S Android Development] drizzt:
lulzactive seems great!
[Nexus S Android Development] lucas4ever:
Hi

Anybody with Voodoo Sound Driver loading issue in Voodoo Control Apps on Glados 2.5 and 2.6 CFS?
[Nexus S Android Development] ale.landra91:
You don't have to load the driver from voodoo control app. They are included in kernel. To solve the issue uninstall voodoo, wipe dalvik and cache, reflash kernel, install voodoo and then you will see al driver green because loaded automatically. If you touch load you get an issue
[Nexus S Android Development] lucas4ever:
thx for answer
[Nexus S Android Development] ale.landra91:
Nothing :-)
[Nexus S Android Development] davioxx:
Anyone having painfully slow usb file transfers running 2.6 cfs and cm9
[Nexus S Android Development] Tordp:
I can't get any TOP=OFF with v2.6. I get some good TOP=ON numbers though. I've tested both CFS and BFS on stock ICS and bigxie's AOSP ROM.

Here's my current specs:

9023

100-1000

No Live OC

Lazy governor

Deep Idle

Screenoff Maxfreq

BLN

On a side note I haven't been able to use any OC (multiplier or Live OC) with any ICS ROM. I was running 110% on GB without problems but with ICS my phone reboots even with 101%. No matter what voltages I use for ARM/INT. My phone was also stable with 1200 using SetCPU on GB but not anymore with any ICS ROM. I have tested all GLaDOS versions for ICS with the same results.
[Nexus S Android Development] caliban2:
Well, after this one SoD yesterday, 2.6 cfs is stable for 18 hours. Before flashing the modded framework-res I had very high top on numbers and zero for top off (bt & GPS were off). After flashing this changed and didle seems to work perfectly now. (Stats and batt-drain)

I guess if one of the two incidents happen again I'll have to do a fresh install. Current sys is running 10 days and had many glados-versions flashed to it. Not sure if I can really blame the kernel... ^^

Stock-4.0.3, 2.6-cfs, didle-on, lazy, max-freq on. Rest is stock.
[Nexus S Android Development] cdpango:
this is due to a rom problem regarding Bluetooth, there is already patch for stock ICS rom in this thread.
[Nexus S Android Development] keb00:
Someone knows how can i restore my default bootanimation? I don´t like this... :o
[Nexus S Android Development] got2best:
All u have to do is before u flash the kernal open the zip and delete the boot animation then flash it after your rom :)
[Nexus S Android Development] Tordp:
I know about the Bluetooth conflict but I have BT and NFC turned off but still don't get TOP=OFF numbers.
[Nexus S Android Development] got2best:
Sorry for double post.... does any1 know what rom ezekeel is using?
[Nexus S Android Development] got2best:
I guess the problem is that even with it off something doesn't disable correctly making the top off not work correctly
[Nexus S Android Development] siffar:
I am getting reboots when on phone call on 2.6. My handset is i9023 and I am using stock ROM
[Nexus S Android Development] got2best:
R u using Cfs? Because I have i9023 2.6 cfs and talked on the phone last night for almost an hr 46 min exactly and no reboot or problems.. I am using cm9 kangs
[Nexus S Android Development] gismo2004:
the same problem here! (except the rom, i'm using CM9 alpha18)

reboot after completed call.

now will switching to CFS... maybe this will fix it *gg*

cheers
[Nexus S Android Development] developersdevelopers:
I believe he's using stock ICS at the moment.
[Nexus S Android Development] :
i have also problems with signal and reboots :(

btw awesome kernel :)
[Nexus S Android Development] mluu921:
just got a reboot after about 30 mins in the call. cfs glados 2.6 with stock ics rom + voltage
[Nexus S Android Development] siffar:
I always use CFS versions :)