yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] nitinvaid:
Any Sol For RILJ wakelock:(:(:(

Uploaded with ImageShack.us
[Galaxy S II Original Android Development] soulzero:
put phone in airplone mode

reboot

turn off airplane mode

think i remember it was this
[Galaxy S II Original Android Development] luexi:
Yup happen for me too.. Bad drain. Wasn't happening on b5~7

Dont know what to do now. :confused:
[Galaxy S II Original Android Development] Rawi666:
On rc2 sometimes when I launch random games my phone freezes so badly that I need to remove battery to unlock it

last_kmsg doesn't contain any error so I don't know if it's because of GPU 50mV UV change or not...
[Galaxy S II Original Android Development] androidkid311:
Hi mate what rom are you using I don't see no audio_out1 wake lock... hmmm...
[Galaxy S II Original Android Development] rauschkugl:
Did you under volt your CPU? If not try setting the -50mV from gokhan on gpu back. I had no problem though.
[Galaxy S II Original Android Development] nitinvaid:
Thanks it works for now
[Galaxy S II Original Android Development] nitinvaid:
Hi

I am on cm9
[Galaxy S II Original Android Development] :
Gokhan, do you realize that 100mhz costs more battery than 200mhz? I can't understand why you would set it as standard.
[Galaxy S II Original Android Development] itchetrigr:
GM I nandroid backup and restored to second ROM without a hitch... Used the second ROM for most part of the day and all seemed functioning as it should. Will I encounter problems? Should I re-install second ROM to avoid issues?

Backup and restore was done with v3.2rc1
[Galaxy S II Original Android Development] fxba77:
Gokhan,

i flashed LP9-Based Custom ROM as 1st ROM, and AOKP-Based ROM as 2nd ROM. If I boot my phone with the 2nd ROM, and after that restart-boot 1st ROM, all my widget freezing. The problem solved, if I restart the 1st ROM again. That's mean If I want to use the 1st ROM after restart from the 2nd ROM, I must restart it twice, otherwise my widgets freezing.

Do you have the solution for my problem?
[Galaxy S II Original Android Development] PedroMRP:
"your extweaks settings will be automatically reset after flashing this version"

My settings stay the same after flash 3.2
[Galaxy S II Original Android Development] soulzero:
I heard that too, can anyone explain why the sudden change in 18 steps?

Not saying its a bad thing, cause i dont really know. But its a big change!
[Galaxy S II Original Android Development] PedroMRP:
Having the 18 steps allows you to have all the intermediate steps between 200 and 1200 you don't need to set the min freq to 25 just set to 200.
[Galaxy S II Original Android Development] gokhanmoral:
according to andreilux's measurements, it doesn't.

but it may consume more for your usage pattern.

in that case you can set the minimum to 200MHz.

although the difference is not much, 100MHz seems to consume a little bit less.
[Galaxy S II Original Android Development] MatMaul:
Hi Gokhan,

Someone states here that having load_h higher than 35 disable the second core and I can confirm this (actually the "sweet spot" is 36). Verified by 2nd core app and the results of a threaded benchmark.

I think you should use lower load_h in the battery profile because it is currently at 40, which disable the second core.
[Galaxy S II Original Android Development] confusedmuse:
I have 18 steps (limited to 13) undervolted and i have a much better battery.

Having more steps means the total time spent on lower clocks increases.

Not like 5 sec @ 200MHz and 5 sec @ 500MHz, but 2 sec @ 100MHz, 2 @ 200MHz, 2 @ 300, 2 @ 400 and 2 @ 500MHz. (theoretically)

And with the right settings the usage is even.
[Galaxy S II Original Android Development] Evollution:
It's necessary to have 2 Roms?
[Galaxy S II Original Android Development] runedrune:
No.
[Galaxy S II Original Android Development] dirn1111:
Not necessarily, because it can still jump to 1000 immediately, but when it falls it will fall like what you described meaning spend more time on higher clock speeds but not straight to 200 mhz. Also when switching clock speed cpu consumes more battery.
[Galaxy S II Original Android Development] confusedmuse:
Theory failed. :) Clock usage is even. (CPUSpy) Battery is better. ;)
[Galaxy S II Original Android Development] gokhanmoral:
right. thank you.

I was removing ntfs-3g from the payload to make the kernel smaller (to go back to LZO) most of you need readonly access and it will be provided by using kernel's internal ntfs support. and I will also make the battery default 35. then I will upload 3.2.1
[Galaxy S II Original Android Development] mobilio:
Just flash v3.2, everything alright! Thanks a lot for the works :D

By the way, I cannot change the minimum voltage to 825……can only choose 850 as minimum. Anything need to do to allow 825 shows up?
[Galaxy S II Original Android Development] rlorange:
Not necessarily either. You are assuming ondemand behaviour with tuned lulzactive you CAN get even frequency use. Changing clock speed is irrelevant according to ACTUAL measurements.

This is a scientific exercise in myth busting. 100mhz consuming more than 200 as well as extra step switching consuming more are theories which have been floating around for long enough that everyone just accepted it as fact.
[Galaxy S II Original Android Development] ephraim:
Nah, it's optional. For me i like switching between stock ics and cm9 so dual booting is good for me. I started a few days ago :)
[Galaxy S II Original Android Development] Doeyourthing:
latest version

Latest version 3.2 (final) is given me a headache. On the phone backside around the camera is getting to hot. never got this before. Phone keep hanging after reboot.

Going back between version b6 en b8. At least b6 was great.
[Galaxy S II Original Android Development] Bene2k11:
Mhh, just updated to 3.2, using my old settings the phone gets hot and facebook is very sluggish... :/

(ondemand, 100-800mhz, UV, noop)

Edit: just like magic everything is smooth now, without doing anything. :D
[Galaxy S II Original Android Development] pikachu01:
Your governor is? Settings?
[Galaxy S II Original Android Development] Lady_Chloe:
I have a question about the battery level. I have noticed that with this kernel, I can drain the battery to 78% for example, leave it be during the night and when I wake up in the morning, I have 79% of battery left. Indeed, when I look at the battery graph, it looks like it was increasing for some time after I switched the screen off. This happens during the day as well, there are "dents" in the graph when I look at it. This did not happen with the stock cf-root kernel. Should I calibrate the battery or is this normal?
[Galaxy S II Original Android Development] slekkas:
I'm with wanamlite 11.5 with siyah 3.2rc2 and battery is great. 22 hours with 4 hours screen on. Wifi and 3g on.
[Galaxy S II Original Android Development] sam razzy:
If ppl as a massive battery drain problem... then please allow the battery to take one two charging cycle... battery life is superb on 3.2rc2
[Galaxy S II Original Android Development] shawnaye:
Hmm my cpu is still unevenly distributed.. Still hanging alot at 1000.
[Galaxy S II Original Android Development] confusedmuse:
You all shouldn't care too much about the battery gauge. It's an assumption based on the measured voltage. If you get 4 hours or more screen-on time and 2-4 days standby everything is fine.
[Galaxy S II Original Android Development] pikachu01:
Check what's causing your CPU to hang around 1GHz. BetterBatteryStats might offer a clue.
[Galaxy S II Original Android Development] Doeyourthing:
Everything was on default. I will give a try later @ home.
[Galaxy S II Original Android Development] olifee:
Nice idea ;).

You could also save a lot of space by stripping the ntfs-3g-binary (shrank by half the size, down to 400k after xz -9e), might be useful for the other binaries still left ;).
[Galaxy S II Original Android Development] gokhanmoral:
really? I never tried to strip it, I thought it would already be stripped :)

anyway.. it's already removed.

kernel's inbuilt ntfs support works good enough for read-only access.

and people who need read/write support are generally advanced enough to run some scripts to mount it.
[Galaxy S II Original Android Development] mrbuzz1967:
me too. using rohit miui with all default settings apart from bln enabled. already done 1 charge cycle and at the moment about 1% a minute, same as you.
[Galaxy S II Original Android Development] wallaceff:
gokhanmoral:

Not sure if you saw my earlier post, but it seems when installing a rom to the second rom that includes a script to wipe the dalvik cache, the dalvik cache on the PRIMARY rom also gets wiped?

I didn't see any comment on the updates about this. I like to play with different roms at the moment, and its a pain. Any chance of a fix (if its not too complicated)?

I have CM9 on primary and Epsylon secondary (as an example).
[Galaxy S II Original Android Development] olifee:
You're right, read access is by far sufficient and less error prone for the normal users ;).

I only noticed it by chance just a few minutes ago using the file-command (sadly not installed by default on many debian-based OS's). A small debian-arm-chroot on my laptop made stripping it really easy then, this is really helpful to try out binaries and even do a quick compile before trying them on the phone :).

Busybox appears to be stripped already, so sadly no further gains ;).
[Galaxy S II Original Android Development] kwerdenker:
Following the motto often found in teams "Whoever has the idea, has to do the work" I did a little snooping around to figure out the pseudo-color BLN stuff and I think I got it.

I began by finding the API to allow apps to set the LED color, which is part of the standard Notification-class and then tracing it's way through the different layers to the kernel hand-off point. For anyone interested to follow my steps: NotificationManagerService.java -> LightsService.java -> com_android_server_LightsService.cpp. From there it out of the framework and into libhardware/liblights. liblights is the hand-off point between OS and kernel and here it gets interesting.

The notifcations are handed down from the OS using the struct light_state_t ( defined in libhardware/include/lights.h), which has the color property. In our implementation of light.c, this property is largely ignored. On other platforms (I used msm7k as an comparison), you can see this property is used to feed the different brightness values to the corresponding LEDs. If you look at that lights.c implementation, you can also see they have three single LED interfaces for the different colors rather than one RGB interface. This would explain why you only know about the one parameter, gokhan.

Now, the conclusion from all this is:

1) liblight definitely needs to be patched to actually use the RGB values from the notifications

2) We need a way to let the kernel know these values. Either the kernel implements a new interface to accept the full RGB value/the three single colors as a parameter and then does the mapping internally or liblight decodes and maps the colors and then writes a selection value to the notification interface which then uses that value to display the selected effect. The first version is probably the preferable way but I admit to know too little about the kernelside to estimate the complexity of this.

I hope this helps you gokhan to figure things out. If you need me to provide you with more infos or if I can assist in some other way, just let me know :)
[Galaxy S II Original Android Development] bernard134:
i don't know why but when finish flashing siyah kernel v3.2, my phone Amoled display will show line of greyish color at the right side of the screen from top to bottom when displaying any grey color. It very obvious when i pull down the notification bar, because its grey, no issue with other color like black, white and all others. Also happen when i flash N.E.A.K kernel, but i tried CF-Root kernel no such issue.

any one encounter this issue?
[Galaxy S II Original Android Development] Canadoc:
OK I have a favour here. MY first priority is great battery life and second responsiveness. I do not care for BLN. I am currently on Wanamlite 11.5.

I have the free version of extweaks. So my question is :

Can someone recommend settings adjustments in EXTweaks that would provide me with the best battery life that would not sacrifice responsiveness in any significant way?
[Galaxy S II Original Android Development] confusedmuse:
I have a strange issue since v3.2... the app GestureContol doesn't start at boot anymore.

Also my UV settings in Rom Toolbox aren't applied anymore at boot.

Have to start all of them manually.... :confused:

Anyone else having this issue?

Edit: Everything else works at boot, only this 2 suddenly won't start anymore...

Edit 2: Reset Extweaks, wiped caches, fixed permissions, removed init.d scripts. Issue solved.
[Galaxy S II Original Android Development] gokhanmoral:
great info.. thank you very much. that was what I needed.

we have custom liblights and (of course) a custom kernel which can be made aware of that change.

since I don't want to break the other interface, I will create another device file in /sys/class/misc/notification named "color" and I will also echo the color code to that file. and actually, the notification checks the same color using this:

static int
is_lit(struct light_state_t const* state)
{
return state->color & 0x00ffffff;
}

and if is_lit(state) then we fire the notification.

now the hard part is to make it practical.

I can divide that RGB region into 6 part and let users to assign different pattern for each one.

I need to sleep on that :)
[Galaxy S II Original Android Development] erik07:
i have a problem since 3.2rc1 up to the current version, wifi tethering is not working, i can activate tethering but on the other phone it says error/no connection while on s2, i can still browse. can you fix it? and also the lag in games, that is also since 3.2rc1. s2's dxlp7 odexed. lulzactive/sio 1000max-200min (even if set to default 1.2ghz or higher, still experiences lags in games that didn't happen when s2's still in gb). pls fix this great kernel. :)
[Galaxy S II Original Android Development] kwerdenker:
I don't think you need to concern yourself with the whole RGB spectrum. I checked the options from Friendcaster (only app I currently have installed that has the LED color option) and you only can select between hardcoded values (Green, Blue, Red, Cyan, Yellow). These are probably just the sensible constans from androids color class, so I would wager you only need to map the real colors defined there (excluding the ones that make no sense like black, white, grays and transparent).

This way your mapping should automatically correspond to the values that are actually used :)

P.S.: It would be great if someone could cross-reference my findings with another app, that has this configuration option (GO SMS maybe?).
[Galaxy S II Original Android Development] :
Whatsapp also has white and purple

Sent from my SGS2 - SlimICS Rom & Syiah Kernel
[Galaxy S II Original Android Development] kwerdenker:
On second thought, white makes actually sense but purple destroys my theory :( Well, I still think using only the values defined in colors would give us ample options while keeping the whole thing more manageable. Let's see what gokhan comes up with in his dreams ;)
[Galaxy S II Original Android Development] jim-bo:
How about if you just mask out the MSB for each colour (which will mean we can ignore noise at the bottom if any app uses an actual colour-wheel to pick).

static int
is_lit(struct light_state_t const* state)
{
return state->color & 0x00808080;
}

That would leave us 8 possible values

0x00000000 - black, ignore it

0x00000080 - blue (any blue over half brightness)

0x00008000 - green (any green over half brightness)

0x00008080 - cyan (any blue and green both over half brightness)

0x00800000 - red (any red over half brightness)

0x00800080 - magenta or purple (any red and blue over half brightness)

0x00808000 - yellow (any red and green over half brightness)

0x00808080 - white (any red and green and blue over half brightness)

pretty much any "listed" colour would trigger the one with the closest name
[Galaxy S II Original Android Development] tb-killa:
I used BLN often, with 3Min Timeout too !

If I´m at work I Plug my SGS2 at my Charging Dock to have constant Power !

Great and Nice Idea would be if you implement charging detection interface for BLN and Timeout !

First: If we timeout it should only work if "Battery" usage so if I plugin Charger it doesn´t Timeout because it Power of Charger!

Second: If Battery Percentage have come under selected valued BLN shouldn´t done anything to get Battery saved !
[Galaxy S II Original Android Development] jim-bo:
Just use Tasker it can already do all of that, and it should really be a userspace solution, not a kernel one.
[Galaxy S II Original Android Development] ssauger:
I have a problem with Play Store and think its related to the dualboot/rom on the device. I only can install free apps on one of the two roms. Updates and download apps i have installed any time before are no problem. But apps i never had installed give me the error i attached in the picture. The only way i found is to clear data from Play Store and google services framework then reboot. But at this time i got this issue on the other rom and has to do the same there if i will download there a new app.

I am alone with this? And maybe can someone please tell me how to fix this for booth roms? Tanks in advance
[Galaxy S II Original Android Development] confusedmuse:
Clear data from play store and google framework & reboot.
[Galaxy S II Original Android Development] ssauger:
I know that. But is there a solution that it works all time on booth roms?
[Galaxy S II Original Android Development] irony17:
Hi,

A bit of an issue here.

My device constantly bootloops after flashing this kernel.

No pin code asked, no siyah animation but just the standard samsung anim.

I am running the xxlps rom.

Anyone has a clue ? I wiped all caches and reinstalled but same problem.
[Galaxy S II Original Android Development] confusedmuse:
For me all the issues that i ever had with play store are fixed since v3.5.16.

Which version do you use?
[Galaxy S II Original Android Development] ssauger:
Same version, You can download never installed apps on both roms? I use CM9 primary and stock LP9 secondary.
[Galaxy S II Original Android Development] blaex:
Use another google-acc?
[Galaxy S II Original Android Development] confusedmuse:
Well, i didn't start my secondary rom for a few days, but till now i never had a problem downloading apps to both.... No idea what could be the cause of your issue.

Have you tried a clean install?
[Galaxy S II Original Android Development] zoneeee:
Hello, i'm reporting a possible bug ( that i've reported also 1 month ago without luck ).

Sometimes, it happens randomly, my phone is not able to recieve/make calls and recieve/sens texts. The signal is stuck to whatever it is ( 1-2-3-4 bars, it doesnt matter it doesnt change ).

My phone doesn't call anymore, i can do what i want but it won't change unless i reboot it.

This is annoying coz i never know if i didnt recieve a text or i did but the cell is stuck, so i need to try to make a call and see if it works. If it's stuck, the phone won't be able to call, it will try to dial forever without any feedback.

I think it's kernel related.

Can you look at it GM ?

Do you think it's modem related? I have LPR modem.

Rom is neatrom LP3 ( all stock deodexed ), didnt change anything else but Siyah and a theme.
[Galaxy S II Original Android Development] BigShix:
best kernel ever !!!! very battery friendly and so many feature and they are awesome, especial Breathing BLN and dual-boot.

Thank you very much gokhanmoral. Keep the good works. I will donate you by Plus App.
[Galaxy S II Original Android Development] ssauger:
Yes, both roms are clean installs. If i clear play store and service framework it works, maybe i have to life with it :( thanks for your help.

Edit: Play Store was updated to 3.5.19 on CM9 rom, did this also on my stock rom, maybe its fixed now
[Galaxy S II Original Android Development] jack_p75:
I just like say my experience whit rc1 i do many times backup second rom and many restore without any problem just the restore take many time but no problem for me take one cigaret and whait :D:D my only problem is when the devaice is off and chargin one time i turn on and when i unlock i have a block and an other time seme devaice off and chargin i turn on the devaice dont start and apear somethin strange like many lines color moved i must take out bettery for restart .

The live battery for me is ok siyah kernel for me is the best and thanks for this hard work.

Ps forget primari rom cm9 second rom wanam

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Hannibal226:
Update to 3.2 and my phone freeze while playing...

Only me?

Will test in further...

But all in all it seems since the last betas the performance get down?!

Maybe just my impression but that what I recognized...

CHEERS

Sent from my Galaxy S2 - I9100 with SensatioN Rom!
[Galaxy S II Original Android Development] confusedmuse:
:(

Don't know if it's because of the change from CM9 0505 to 0509 or the change from Siyah 3.2rc2 to 3.2, but my undervolting became completely useless suddenly...

Have to raise most of the frequenzies by 25 to 75 mV to get it stable... :(
[Galaxy S II Original Android Development] ssauger:
I think its cause the lower gpu voltage. on 266Mhz my phone needs 1000mV. On step 2 its set to 950 by default. Tried it with nenamark2 from marked few times. Freeze with the new default gpu voltage, no problem if i set 266Mhz steps to 1000 mV. Give it a go ;)
[Galaxy S II Original Android Development] Hannibal226:
Give it a try, thanks ;-)

Sent from my Galaxy S2 - I9100 with SensatioN Rom!
[Galaxy S II Original Android Development] Frozenthunder:
First off, great work gokhanmoral. I think this is currently the best kernel out there. I especially love the dual boot feature and it works flawlessly.

But there are 2 things which confuse me:

1. Why is the voltage on 1600mhz so low ( I know you can change it) and why are the voltage steps so weird? When I OC to 1,6ghz my phone runs extremely unstable and usually crashes/reboots/freezes. I don't understand the voltage steps, from 1ghz until 1,2ghz it's 50mv each step and then suddenly it's only 25 each until 1400 then it's 50 again. And from 1500mhz to 1600mhz it is 25 again. Why is it like that?

I know a bit about overclocking and overvolting CPUs. And I know that the higher you go the bigger the steps to increase voltage have to be (assuming you always choose the lowest voltage possible on which everything is stable). That's just due to physics.

I'm currently wondering if it's possible for the CPU to do a normal job at 1600mhz while at 1,4v at all. I think the time which you give the transistors is not enough to do their job, so you would have to increase the voltage to make the system run stable.

But why is it so low by default?

Second: Why did you now choose sio as default I/O sheduler?
[Galaxy S II Original Android Development] glynnpel:
No problem here , thank you very much .
[Galaxy S II Original Android Development] gokhanmoral:
1) anything above 1450mV is potentially dangerous. I set it as max for the worst ASV value.

2) I was using cfq as it was default and give overall fairness. also, I was trying to figure out the reason of battery drain in v3.0betas. since we are on a good track, I set it as default as it was in GB kernel. why? because it is simple and effective. we do not need complex calculations/considerations for our flash drives. in other words, I set it as default because of my sympathy for the code and simplicity :)
[Galaxy S II Original Android Development] Frozenthunder:
What do you mean with anything above 1450? How do you know that? Just curios. Have there been people who wrecked their CPU with using more than 1450mv?