yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] Frozenthunder:
Have you read throught the thread?

You have to format secondrom data and cache first (mounts and storage). Not sure if you have to wipe 2nd rom dalvik and format 2nd rom system, I did it just in case.
[Galaxy S II Original Android Development] rlorange:
Try these steps:

1. Manage apps or Titanium backup> clear extweaks app data.

2. Clear super user app data.

3. Clear extweaks profile in siyah recovery

4. Reflash siyah kernel.
[Galaxy S II Original Android Development] confusedmuse:
Try updating su.

Even if it's up-to-date, press "update anyway".
[Galaxy S II Original Android Development] sam razzy:
Even I had d same problem... read some few post before ... he as said what dat cozzz

Okie... I'll tell you.. you must go to mount n storage --- den format secondary rom data n cache.. den install rom to secondary rom... it works...
[Galaxy S II Original Android Development] sam razzy:
I tried formatting data from secondary rom... but why it takes long time... I guess it is stuck there. Or sud I wait for next hour or few?
[Galaxy S II Original Android Development] Thialala:
it took some time. Just wait !
[Galaxy S II Original Android Development] scanja500:
wait about 8 min.!
[Galaxy S II Original Android Development] MrMastodon:
Can not boot 2nd ROM

Hi

Just flashed my first 2nd ROM, but I can not boot it. Running stock LPQ with Siyah 3.2.1 and flashed Resurrection Remix ics v1.8.1 for 2nd ROM. Wiped 2nd ROM dalvik.

When I reboot I do not get the option to boot into 2nd ROM.

Any any thoughts how i can boot it?
[Galaxy S II Original Android Development] MyLifeRocks10:
Please read 1 Page back and u will find ur solution.
[Galaxy S II Original Android Development] MrMastodon:
Booting 2nd ROM

Thanks, I've tried to read it (three times actualy), but the only thing I found about this was wiping 2nd ROM cache and dalvik cache. I have no option to wipe 2nd rom cache, only dalvik, but when i choose this action, it does not appear to do anything, just goes back to the top of the meny and that's it. No prompt to "do you really want to" and no text-log.

Have I still missed it?
[Galaxy S II Original Android Development] rauschkugl:
Mounts and storage area. Please start to read and use search. The procedure has been explained dozens of times the last days. This is still a development thread.
[Galaxy S II Original Android Development] DinKapach:
thank you, i reinstall the su and now it works fine :)
[Galaxy S II Original Android Development] illuminato 67:
Help me!

I am using the Gokhanmoral's kernel and always it gave me great satisfaction.

Now I am on Siyah kernel 3.2.1 and CyanogenMod 10/05.

Suddenly yesterday, the ringing disappears.

Used audio manager and the like: nothing.

Two wipe (cache and Dalvik cache) + fix permissions: nothing.

Restore nandroid up two days before: nothing.

Changed kernel: nothing.

Tried exorcism: nothing.

A thanks to whoever helps me solve the mystery.

Thank you and look confident.
[Galaxy S II Original Android Development] vijaysivakula:
Thank you all. Got some more information on the process which is definitely helpful. However this doesnt answer my question as to when i should press the Volume Down key. Could someone please help with that. Thanks in advance.
[Galaxy S II Original Android Development] Happy_Jack:
It never was true. In reality the differences are so small it won't make any noticeable difference to battery life or performance which you use.

If you're interested the case that 100MHz uses more power than 200MHz is largely based on two flawed arguments:

1) 200MHz is more efficient than 100MHz in that the cpu can do more processing per mW of power. In fact that's irrelevant because if the cpu is doing a lot of work at 100MHz the governor will increase the clock speed anyway. At very low load (i.e. screen on displaying static text, like an e-book or web page) 100MHz will probably be using less power. My phone spends more time at 100MHz than any other frequency when the screen is on. Contrary to what many on here seem to believe, staring at the screen doesn't make the cpu work harder.

2) 100MHz and 200MHz use more-or-less the same voltage. That's true, but power is proportional to frequency x voltage squared, so at the same voltage 200MHz should use twice the power. In practice this is more complex because we're talking about an active semiconductor which is not strictly linear in this respect, but the argument is still flawed.

There are some measurements on a Nexus S (which uses the Exynos 3110) and an S2. You will see there is not a great deal of difference between 100MHz and 200MHz in either case.:

https://docs.google.com/spreadsheet/ccc?key=0AntDDKv-lS6IdEY4T3dXWVFDWk9lREdJNGFfU2NwRlE#gid=0]

http://www.android-hilfe.de/samsung...80670-info-akkuverbraucher-des-galaxy-s2.html
[Galaxy S II Original Android Development] asaf-g:
Happened to me too. Flashed 3.2 again and it solved it.
[Galaxy S II Original Android Development] Crescendo Xenomorph:
@Gokhan: When I install tabletUI script (from Ressurection Remix v1.8.1 ROM) to SecondROM (via Dual-Boot menu), it installed to FirstROM.

I tried that several times and still it goes to FirstROM.

Here's the link: http://www.mediafire.com/?cmd5tt8cmcb1grb

The Black Themed App for that ROM is installed OK to SecondROM.

Thanks very much Gokhan... ^^
[Galaxy S II Original Android Development] Napalm Candy:
@Gokhan, Hi, I want to ask you if anything is possible with the LUX meter, so only read 0-10-100-100-10000-16000 lux only this steps, but if you go to dialer and call to *#0*# and test the sensors, you will see that measuraments are not in this 6 steps, so you can see "2635 lux" for example, so the steps are by 5 (0-5-10-15-20-25... etc)
[Galaxy S II Original Android Development] Lady_Chloe:
Voltage is squared, not frequency - that's why it is so useful to undervolt the CPU.
[Galaxy S II Original Android Development] Napalm Candy:
I have 3.2.1 and Wifi doesn't work too fine, I see how disconnect and connect again every... 5 or 10 min aprox. This do after I flashed 3.2.1 (before I had NEAK kernel)
[Galaxy S II Original Android Development] vijaysivakula:
Got it. Loving it!
[Galaxy S II Original Android Development] Bonscha:
Flashed it and tried out connecting an 3.5" external 1TB NTFS formatted HDD (plugged into power) via USB-connector... I am unable to browse that HDD, it says I should delete the USB-device.

edit: I just saw that the "here" was a link to the ntfs3g, but it's down... Please fix that, would be great :)

After 10-20 Tests using a FAT USB-flashdrive which worked just fine, that also doesn't work anymore... The OTG cable produces the message it should on connecting, but not one USB device does anything when connected. No error message, no reaction, just as if the OTG cable would be attached without any device connected!

Also, my WLAN keeps reconnecting repeatedly. I can say that it's pretty much every time I plug in sth. via OTG cable. I don't know if it happens while normal use, too... but it seems like it.

And my phone sognal gets lost completely from time to time.

After downgrading to v3.2 none of the problems were solved.
[Galaxy S II Original Android Development] danfalcas:
It's ok to use the SGS2 when it's really hot? Does it have like a knock sensor if too hot or it will just keep on?
[Galaxy S II Original Android Development] Vaedryn:
Yes, it turn off
[Galaxy S II Original Android Development] coloxim:
Gm...I've try fluxi kernel with same radio app and rom...and it stay much more in deep sleep...with your I've secril interfece wake lock...I don't know if is a kernel problem...but sometime doesn't go in deepsleep

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] Happy_Jack:
Quite right, it is voltage that's squared, my mistake. Frequency still has more effect than voltage when considering the battery life of a smartphone though, because you can't under-volt by much. And, using the simplistic theory, 100MHz should use half the power of 200MHz at the same voltage (yes, I know in practice it's not that simple).

http://xdaforums.com/showpost.php?p=22126806&postcount=2
[Galaxy S II Original Android Development] pilgrim011:
Every time I reboot my device, there is a message "Android is upgrading". I'm on v3.2, dual boot Sammy & Res. Remix. I'm just rebooting - not wiping dalvik or cache, not installing kernel etc. - just plain reboot... Any idea?
[Galaxy S II Original Android Development] gokhanmoral:
v3.2.2 is up.
[Galaxy S II Original Android Development] evolutiontheory:
Still unable to enable BLN for messaging. tried go launcher anf DROID notify lite. Still not working. Sorry to bug you guys again and again. Can anyone help please
[Galaxy S II Original Android Development] evolutiontheory:
Once again very sorry to ask this repeatedly. About to give up on this.
[Galaxy S II Original Android Development] Redsoldier:
Been using 3.2.1 for a few days now and have been seeing considerable battery drain. Been getting around 2 hours screen on time over the course of a day. Attached is a better battery stats dump to see if anyone can see if I'm doing something stupid app wise or if the problem lies deeper.

http://pastebin.com/KqFmD5vC
[Galaxy S II Original Android Development] kwerdenker:
If you use a Samsung ROM, there is no way you will have BLN with the standard SMS/MMS app. You'll either have to switch to something like GO SMS, find a modded version of the app or switch to another ROM like CM9.

To be absolutely clear: This is an app problem, not a kernel problem. Basically, because the SGS2 has no notification LED, Samsung didn't program their app to throw the notification needed to use it. Since BLN is dependent on the same mechanism, it just wont work with that app.
[Galaxy S II Original Android Development] anrichp:
B2g

Hey guys I've noticed the latest release supports boot to gecko. is there a download available for b2g that can be flashed from Cwm? I noticed that there is an odin version available.

Cheers
[Galaxy S II Original Android Development] Markox89:
I'm on a stock rom and with 3.2.2 auto brightness stops working, it's only my problem?

Sorry, my bad, works fine :)
[Galaxy S II Original Android Development] dnyeah:
Works fine here.

Can someone explain the led-fadeout in extweaks please?

Verstuurd van mijn GT-I9100 met Tapatalk
[Galaxy S II Original Android Development] rlorange:
The the ultra-slow down bug again on 3.2.1 happened going into sleep while downloading via Wi-Fi.

Seems like lulz scaling is still buggy getting stuck on 25mhz or something.

It also seems like Gokhan is not taking this bug seriously yet but I can hardly blame him with all the recent NOOB activity.

Please this is a DEVELOPMENT thread. If too many noobish post keep appearing it just makes real dev related bug reports harder to read.
[Galaxy S II Original Android Development] BrandoHD:
Why not just raise the minimum clocked speed?

Samsung Galaxy S II Tapatalk2
[Galaxy S II Original Android Development] Frozenthunder:
Because he wants to increase battery life :D

I think 200mhz is best. When I'm on 100mhz and listen to music and increase/decrease volume I hear some ugly noises and the song lags.
[Galaxy S II Original Android Development] bgx:
I would like to change the power of the led via script but couldn't find it in rootexplorer. Where must I search?

Forget it i have found it.

echo 3000 > /sys/devices/virtual/sec/sec_touchkey/touchkey_brightness

Gesendet von meinem GT-I9100 mit Tapatalk 2
[Galaxy S II Original Android Development] Lady_Chloe:
I sort of solved the battery drain by rebooting the phone every time after charging. Without this workaround, the battery drained 14% in airplane mode within 8 hours, with no apps running and (according to battery stats) no awake or screen on time. I hope this gets fixed in an update. I can post a screenshot tomorrow if that's of any use. The xda app says that the extension is wrong so I can't post it from my phone.
[Galaxy S II Original Android Development] kem1337:
3.2.2 is out ;)

Hydrog3nics siyah 3.2.2
[Galaxy S II Original Android Development] Frozenthunder:
Try resetting battery stats. My %gauge was messed up too, but then I deleted batery stats and now it's very precise.

It will never stop.
[Galaxy S II Original Android Development] tolis626:
It's not lulzactive,it's not the 25MHz minimum clock,it's not SIO and...that's about it.My setup is completely different from everything I've seen being blamed for that thing.Lulzactive?No,I'm using ondemand(Yes,even selected as default in ExTweaks).25MHz?Nope,never thought it made any sense using it,I'm using 100MHz.SIO(Wasn't that blamed at some point?I fail to remember everything in here for obvious reasons)?Lately(Last 2 months or so) I've used deadline,noop,cfq and vr.Yes,everything but sio.I think it happens with all these.Wifi?Maybe...Maybe not,it seems more random than that.I have a hunch that it has to do with wifi disconnecting from a router while still being turned on.But still,this isn't proven.The bad thing is that every single time it happened,except for the first time when I didn't know it was a common problem,I wasn't on my PC,so I don't have any logs of any sort.I hope next time it happens I'll prove to be more useful. :)

Btw,things are quite good with 3.2.2.No issues so far. :)
[Galaxy S II Original Android Development] rlorange:
I set min 100. I'm using the same settings I've always used. This bug is new, it Wi-Fi and lulzactive related and reported by several users right here.

I'm only guessing it goes to 25mhz because of extreme slow down. But I don't know for sure.

Btw it happens on both cm9 and LP7 2nd rom.
[Galaxy S II Original Android Development] rlorange:
Thanks for the input! I too feel like its Wi-Fi dropping out related. I generally use lulz so have only had it happen on lulz.

Anyways I'm now on 3.2.2 so hopefully it has fixed itself although there is nothing specific GMs Changelog.

Also it was happening more on my mum's Wi-Fi which has a terrible ADSL connection dropping out all the time
[Galaxy S II Original Android Development] MaKTaiL:
I found a bug on default settings. I didn't touch the settings once but the value seems to be incorrect. I just flashed 3.2.2. The default is 10000 but it's set to 50000.
[Galaxy S II Original Android Development] rlorange:
Nope it's been like that since the beginning. The text is wrong not the setting default is 500mhz... but I prefer 800 :)
[Galaxy S II Original Android Development] rlorange:
Gokhan: the new LED fade-out is VERY cool! :) I thought you might have forgotten about this. Should never doubt you man
[Galaxy S II Original Android Development] MaKTaiL:
It's awesome! So smooth transition.
[Galaxy S II Original Android Development] olifee:
Yep, it really looks cool ;).

For those on Sammy-based ROMs, it appears to work only if an LED-timeout is set which is shorter than the LED-timeout the ROM implements.

So, if you set LED-timeout to 1 second, it works fine here ;).

In extweaks, you can only select 1.5 seconds (which is too long for Sammy ROMs). So you'll have to use

echo 1000 > /sys/devices/virtual/misc/notification/led_timeout

for now ;).

Happy fading! :)
[Galaxy S II Original Android Development] MaKTaiL:
My brightness settings are broken now with 3.2.2. I can only have auto or low settings. I can't manually adjust anymore.
[Galaxy S II Original Android Development] Visentinel:
Boot 2 gecko sounds really cool.

Can I install it as a 2nd rom? I assume I could... hehe

That ultra slowdown bug happened to me only once after receiving a txt msg but I was still able to just select reboot, took several minutes but was able to graceful reboot, so no biggies. Seems like a rare bug.
[Galaxy S II Original Android Development] rlorange:
You can change Sammy rom time out in settings. Maybe setting high in the rom will allow higher in extweaks to work?
[Galaxy S II Original Android Development] rlorange:
Yeah I hope to catch it in a log next time to provide GM with something to work with.
[Galaxy S II Original Android Development] stark_br:
Is the lulz one broken on 3.2.2?

Mine is stuck on 500mhz all the time.

Tks
[Galaxy S II Original Android Development] danfalcas:
Thank you :) it's really helpful to know that
[Galaxy S II Original Android Development] kalpik:
+1 the slow bug happens to me to even on ondemand, and 200 MHz min Step (5 steps total). This is the only bug stopping me from using this awesome kernel!
[Galaxy S II Original Android Development] ShadowSkills:
not too rare in my case, had them a few times a day, although after changing gpu voltage and set to 5 step I haven't had any slowdowns.

Sent from my GT-I9100
[Galaxy S II Original Android Development] olifee:
You are totally right!

How did I not see that option in settings up to now ? ;-)

So for Sammy ROM, one has to set timeout in settings and in ExTweaks, fading is wonderful then :).
[Galaxy S II Original Android Development] rlorange:
There used to be a similar bug many versions ago where lulzactive screen off min set too low my default because of the extra frequency steps.
[Galaxy S II Original Android Development] g00ndu:
I was on dual rom (Sammy and Miui) previously and i have tonnes of problems. I have some immediate freezes and also the so called slow bug, where the phone goes into stand still. Whatever extweaks settings i have done does not help.

I eventually took the plunge and do a clean re-install of my phone (both Sammy and Miui). I also re-install all my programs instead of using backups from TB or from Miui.

Right now, I do not have freezes or slow down anymore, and the phone is working mighty fine.
[Galaxy S II Original Android Development] toinktoink:
i was wondering what's causing these wakelocks...

http://imgur.com/UeHX5
[Galaxy S II Original Android Development] gamal001:
Good Morning,

any body have idea why my device getting restart on time every day.

after flash 3.2.1 (only one time every day)
[Galaxy S II Original Android Development] gokhanmoral:
your device has the answer.

attach /proc/last_kmsg file so that we can see the reason.
[Galaxy S II Original Android Development] gamal001:
View attachment last_kmsg.zip
[Galaxy S II Original Android Development] aegeuss:
I also had this problem and could get rid of it by raising GPU voltages 50 Mv. I hope it helps.

Regards.
[Galaxy S II Original Android Development] gokhanmoral:
there is no info about crash or reboot in this file. try to capture it just after having the reboot.
[Galaxy S II Original Android Development] Visentinel:
Hey gokhan hopefully I catch u before u go, there is the occasional bug where the lights for the keys don't turn on when I wake the device. Doesn't happen often, but something to look into eventually.

Edit. The lights are set to always on regardless of light sensor, I'm using the f1 b4 rom.
[Galaxy S II Original Android Development] kalpik:
Let me try that! Thanks :)
[Galaxy S II Original Android Development] gamal001:
When my device restart not coming any msg.

no crash no lag no hung.

only restart.

thank you very mush for you help.

I'm sorry for my bad english.
[Galaxy S II Original Android Development] vizdak:
Gokhan can you check this last_kmsg? I'm checking Manage Apps in Menu then suddenly phones hangs up and then when screen off it's on slow mo. When I push home button it open up again but in slow mo. So I have to force off the phone. I'm on Siyah 3.2.
[Galaxy S II Original Android Development] shr33kant:
I'm not getting any of these slowdowns you're all going on about.. I'm using 3.2.2, ondemand, sio, 200-1200, 5 steps no undervolting , 3 gpu steps at 160, 200, 267 @ 900,950,1000mv at 80%,70%,80%, 60% thresholds. In regards to wifi recently I've changed the broadcast channel to 13 on my router, and I've never had problems with it cutting out since. I think when it was on default (6) it was getting interference from the bluetooth phone calls that I usually make.

Sent from my GT-I9100 using Xparent ICS Blue Tapatalk 2
[Galaxy S II Original Android Development] d3f1ant:
I've had a very funky slowdown too, and I using OnDemand (kernel stock settings). It's only done it twice in the entire time on 3.2.1. Everything seems to work but goes extremely slowly, like in slow motion.
[Galaxy S II Original Android Development] bokil:
Gm,

I am on 3.2. Just had a slo mo freeze. I am using 18 steps ondemand sio. Uv cpu and gpu. Here is the last kmsg.

This happened when i opened play store. One time before it happened when i opened camera. If u need to know my undervolts plz let me know. Hope this helps

Plz open in wordpad
[Galaxy S II Original Android Development] alcurtis93:
I have also had a slowdown when I was on 3.2.1 unfortunately didn't get log as thought it was something I did
[Galaxy S II Original Android Development] alcurtis93:
I have also had a slowdown when I was on 3.2.1 unfortunately didn't get log as thought it was something I did wrong
[Galaxy S II Original Android Development] maczaros:
I also noticed few slowdowns (2-3 times) on 3.2r8 and 3.2 (current) - I didn't notice it on previous versions.
[Galaxy S II Original Android Development] jim-bo:
I was reading through some of the slowdown posts as I walked into work this morning, thinking about the fact that I have been lucky enough not to suffer from them, when I suddenly realized, while reading one of the posts, that I actually have suffered exactly the symptoms described..... but they weren't a kernel bug, or a governor crash, or a stuck at 25MHz, or anything like that. They were just a app that had stopped responding.

Some of you may not realize that in ICS the delay before you get an "App xyz is not responding, Wait / force close / report" type message seems to be massively longer. Now, some app stalls can give you a state where your screen is on, none of the buttons respond, not even home, and it seems like everything has frozen, though the notification bar is still alive, the time updates, the power button works, but it would be easy to think that someone had filled it with treacle. Sadly, this is only indicative of a stray app that has crashed, nothing more, and the only way to know this is the case is to wait.... a frustratingly long time.

I know that many / most of the reporters are actually seeing some sort of slowdown, but at least a couple of them have definitely looked like a mis-interpreted app crash.

You will often see an app stall in this way if it is performing IO to the internet when it suddenly loses connectivity, which could be related to the WIFI reconnects people are linking to this.

To those who really are suffering slowdowns, there are two things that can cause such an effect. One is that the CPU is being clocked way too slow, which seems to be the assumption, and the other is that some process has gone runaway and is pegging the CPU at 100% active. If any of you could get an adb shell open from a PC, and

cat /sys/devices/system/cpu/cpu0/cpufreq/cpuinfo_cur_freq

and

top -n 1 | grep CPU

it should give us some clues as to whether is is running slow, or running busy.
[Galaxy S II Original Android Development] crypticc:
Were you Plugged in to top up at all? Power manager service also means a summary of all user space kernel wakelocks.

Consider posting in better battery stats thread, that's where wakelock experts tend to frequent.

Chris
[Galaxy S II Original Android Development] omniwolf:
I have actually experienced these slow downs (not on Siyah mind you) and eventual app crashes when under volting. no OC or UC. so i would say if you UV or UC, turn that **** off and see if you still get app crash/slow downs.
[Galaxy S II Original Android Development] crypticc:
Or set to on in settings, then set to always off. Seems to stick with the extweak setting then which is handy.
[Galaxy S II Original Android Development] Lady_Chloe:
I can report that my problem with battery drain really goes away if you reboot the phone after disconnecting it from the charger.

I got 5 hours 30 minutes screen on time and after I turned on airplane mode, the battery went up from 8 to 12% during the night.

Without the reboot, it discharged from 24 to 10% over the same period in airplane mode.