yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Original Android Development] naveediftikhar:
I jus cant echo my deepsleep level to 6 ...m using 2.6.7 conservative..noop...wid scripts of ma own ill post it so that someone can point out why it doesnt change even though everything is perfect!

#!/sbin/busybox sh

echo "80 133 267" > /sys/class/misc/gpu_clock_control/gpu_control

echo "90% 25% 90% 40%" > /sys/class/misc/gpu_clock_control/gpu_control

echo "800000 800000 950000" > /sys/class/misc/gpu_voltage_control/gpu_control

echo "35" > /sys/module/pm_hotplug/parameters/loadl

echo "90" > /sys/module/pm_hotplug/parameters/loadh

echo "60" > /sys/module/pm_hotplug/parameters/loadl_scroff

echo "0 0 0 1 1 2 2" > /sys/devices/system/cpu/cpu0/cpufreq/busfreq_static

echo "200000" > /sys/devices/system/cpu/cpufreq/ondemand/suspend_freq

echo "6" > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel

echo "1" > /sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel
[Galaxy S II Original Android Development] pikachu01:
Try running it in Script manager. See what error it gets. You might have saved it not in the UNIX format.
[Galaxy S II Original Android Development] naveediftikhar:
All editing in the script is done through my phone...but ill try the script manager n report back!
[Galaxy S II Original Android Development] pikachu01:
What editor are you using? Can you check if there are spaces at the end of all the lines? Delete the empty space if you do see it using the Script Manager editor.
[Galaxy S II Original Android Development] naveediftikhar:
Ran it through the scripy managet..the only error i get is the suspended freq error on ondemand which is obvious as my governer is conservative...other then thag nothin...the buslevel changes to 1 but cpulevel stays unchanged!
[Galaxy S II Original Android Development] PedroMRP:
I think that gokhanmoral limited the deep sleep so you can't change it to a value lower than 500MHz so if you try to echo 6 it won't change the deep sleep value.
[Galaxy S II Original Android Development] naveediftikhar:
Awesome....*sarcasm*...thx or the rep though!
[Galaxy S II Original Android Development] Honusnap:
Try 4 to see if it stay setted..
[Galaxy S II Original Android Development] gg13:
Big thanks for this job!!

Have a nice day.
[Galaxy S II Original Android Development] Holgott:
Had the same drain like yesterday. I charged before goin to bed and unplugged few hours later when phone was fully loaded. When i woke up in the morning, my battery was at 90%. (2-4% w/o tb)

I uploaded screenshots og bbs and cpuspy
[Galaxy S II Original Android Development] Holgott:
Damn... Wrong thread. Should be in the thunderbolt thread
[Galaxy S II Original Android Development] Steve_max:
Try to comment out the line where you got the error. If it's a "file not found" type, the script will stop and the deep sleep part never gets set.

Sent from my Nokia 3510 via telepathy
[Galaxy S II Original Android Development] Lulavc:
Originally Posted by droidphile: 1000 mhz or 800 mhz is NOT the frequency at which CPU operates during deep sleep. It is the frequency at which CPU need to be statically set just before entering deep sleep.

During deep sleep, CPU is almost completely turned off, except for very few sub-components in Soc like cell radio.

Enviado do meu GT I9100.
[Galaxy S II Original Android Development] Honusnap:
Seems that you're right ... mine do not remain at 6 as setted...
[Galaxy S II Original Android Development] Entropy512:
Yup. Specifically, apparently somehow the bootloader comes into play during resume (this is from a Samsung kernel developer's post, I don't have the link with me right now.) Most Exynos bootloaders resume at 800 MHz - but don't touch the regulators. So the order is something like:

Normal op -> Lock to 800 -> Complete shutdown of CPU (wait for a timer or wakeup interrupt) -> Bootloader resumes at 800 (no way to control this) -> Kernel operating, locked to 800 -> Normal operation

So during suspend, the frequency must be locked (CPU frequency transitions during suspend/resume can do weird things) and the regulators must be locked to support the suspend lock frequency before regulator control goes away. (The CPU can turn the regulators on/off without any software when it enters/leaves suspend, but it can't change the voltage settings.)

So the regulator voltage must be set to allow reliable operation at 800 MHz prior to the regulators going away - If it's too low, the device crashes on resume.

Setting suspend frequency lower than 800 while keeping the voltage high enough to support 800 may have no benefit - Unless Samsung did something stupid (like looping while waiting in an IRQ handler somewhere), dropping suspend frequency to 500 will just reduce time spent in idle states, potentially actually increasing power consumption.
[Galaxy S II Original Android Development] Cpasjuste:
Hi, just a little note to say that i did add SiyahKernel compatibility to my OC/UV tool PimpMyCpu. I will also add GPU OC/UV in the next update :)

It has not been tested on GS2, so reports would be welcome :)

Thanks,

Cpasjuste.
[Galaxy S II Original Android Development] o0boiboi0o:
Yea! From Volt Control, all my BUS freq is at 133.

So you mean I have to change the freq as reco. by PedroMRP? Any harm to remain them @ 133?
[Galaxy S II Original Android Development] PedroMRP:
Imagine this... You have a Ferrari and if you drive it on the highway you can reach high speeds but if you drive the Ferrari in a country road its impossible to reach the same speeds that you reached on the highway.

If your device is using a BUS Freq of 133MHz at 1200Mhz you are strangling the cpu speed.
[Galaxy S II Original Android Development] veyka:
10% isnt a crazy drain overnight, and anyway, nothing there looks like a kernel problem.

The following apps are the problem:

1) some stupid antivirus app, remove it

2) 3G watchdog doing something

3) facebook, turn down the refresh frequency (its a known battery hog).

4) something was generally using the network connection, thus svnet, probs facebook.
[Galaxy S II Original Android Development] SirCanealot:
Is anyone else having problems with notifications recently? I remember someone a few pages back having some trouble. Facebook messenger isn't giving me notifications on the latest version. It was fine on the .11 though!

Any ideas? Cheers!
[Galaxy S II Original Android Development] xuxuzao:
so what values do u recomend to

/sys/devices/system/cpu/cpu0/cpufreq/deepsleep_cpulevel

/sys/devices/system/cpu/cpu0/cpufreq/deepsleep_buslevel

?
[Galaxy S II Original Android Development] stevehkim:
i use echo 4 for cpufreq and echo 1 for buslevel.

Beast of a SGS2/SIYAH
[Galaxy S II Original Android Development] ernest101:
just asking, the CWM v3.0 app in my drawer, is it installed in my phone because I flashed this kernel?
[Galaxy S II Original Android Development] CamoGeko:
Have you had CF-Root kernel installed before?

Communicated using an S2 type Droid while floating in CM9 Galaxy
[Galaxy S II Original Android Development] MemoryController:
@gohkanmoral

How about usb dac support :)?
[Galaxy S II Original Android Development] ernest101:
I doubt so but it is possible... but I have stumble onto his thread before when I wanted to root my SGS2 (good God how long ago was that D: ) should I flash Chainfire's kernel?
[Galaxy S II Original Android Development] PedroMRP:
Yes, this Kernel installs CWM v3 app
[Galaxy S II Original Android Development] ernest101:
cheers mate ;)
[Galaxy S II Original Android Development] bala_gamer:
anyone............?
[Galaxy S II Original Android Development] veyka:
I would imagine ICS kernels will not work with GB roms due to differences in the kernel > userspace interfaces.

As far as everything else, why dont we wait for kernel src and see what needs to be added/can be added/etc.
[Galaxy S II Original Android Development] Entropy512:
Yeah - it's indeterminate what things from the kernel need to be added to the new one - the ICS kernel might make some things redundant. (For example, GM has backported some functions from newer Linux kernels - those become redundant with ICS.)

For example, the cpuidle backport from the Tab Plus Honeycomb kernels will be redundant in the ICS kernel unless Samsung REALLY ****s up. If anything, the ICS kernel should have better cpuidle code.

So until ICS kernel source drops, it's going to be indeterminate what needs to be done/can be done with it. Without a doubt, ICS kernels won't work with GB.
[Galaxy S II Original Android Development] Holgott:
Dude plz read the text under this one. I spoke about thunderbolt and it was definitely more drain with thunderbolt in the night. I changed nothing else in the system just tb. I removed it in the morning and now it seems to be better again with stock siyah setting. i just compared MY drain between stock siyah and with tb settings.

But nvm ..thanks for the battery saving tips ;-)
[Galaxy S II Original Android Development] chadouming:
haha, seeing how samsung is used to **** the things up, we will keep this backported cpuidle xD. However, the ICS kernel load different things, no ?
[Galaxy S II Original Android Development] veyka:
From what I read about what samsung was doing with the stock kernels, it seems like that where hacking things together seemingly haphazardly, but I suppose we can always live in hope.

But its all stupid conjecture, because a 3.0 kernel is going to be quite a bit different from 2.6.35.x (not that 2.x.x to 3.x.x was a big jump, but 2.6.35 is old however you cut it).

Its all just more "wait and see".

Its not like its even a upstream 3.0.x kernel, theres all the out of tree android patches, like the whole wakelock system :P

ICS is a huge jump from GB.

Yeh, sorry, I didn't connect the post afterwards to yours, my bad.
[Galaxy S II Original Android Development] pikachu01:
Hmm, weird. Haven't had any reports on this except you on Siyah :/

Could it be an addon? Did you install the 3G addon? 3G addon is not compatible with SGSII.

You have BBS dumps for with ThunderBolt! and without right?

Can you upload both and see the comparison from there?
[Galaxy S II Original Android Development] jbarol:
Hi All,

I am new to bug reporting, so please let me know what info you need and I will supply it.

I am running LA2 and SK2.6.12

I am having SOD and random reboots on 2.6.12. On 11 it only happened every now and then, but now it happens several times per day.

I know that you need more information to advise me on what to do. What would you like me to upload?

Thank you in advance.

-Me
[Galaxy S II Original Android Development] pikachu01:
Try not to UV/OC?
[Galaxy S II Original Android Development] jbarol:
Thank you for your response.

I had on 11 uvd, but i was under the impression from the first post that 12 contained stock voltages, and would overwrite anything that I put in prior to that using Voltage Control.

Is that correct?

Is there a way to verify my current voltages against stock?
[Galaxy S II Original Android Development] pikachu01:
Here is the default for each (100MHz-1200MHz)

900 900 950 1025 1125 1225 - NEAK

950 950 950 1050 1150 1275 - Siyah

925 925 950 1050 1175 1250 - Redpill

Play an MKV file from these samples in software decoding for 10mins when undervolting each frequency (you limit the frequency you want to test by limiting min/max):

http://xdaforums.com/showthread.php?t=1054962
[Galaxy S II Original Android Development] Holgott:
Hmmm... I think i got the reason for the more drain and im sorry for the dumbness :-P ..as i was goin to bed last night i forgot to switch off mobile data usage - dont ask!!!shame on me!!

Will flash tb again and will compare battery usage without data connection. Sry again especially to pikachu but thought first it was a tb issue :-(
[Galaxy S II Original Android Development] jbarol:
Thank you for the information.

After 1200, what should it be?

Also, If i am running .12, does that mean that I should run the Redpill numbers or the Siyah numbers? I don't understand that..

What do you mean by "play in

software decoding

for 10min"?

And, I am sorry, what do MKV files show me?
[Galaxy S II Original Android Development] pikachu01:
No worries :)

I'm more concerned in fixing whatever's troubling you actually :)
[Galaxy S II Original Android Development] stylez:
An mkv is just a video file format and software decoding could be any video player capable of playing mkv.

Its an easy way to see glitches and alter CPU levels.

Sent from the valley of the shadows....
[Galaxy S II Original Android Development] zaphod777:
Clear your dalvik and system cache from recovery.
[Galaxy S II Original Android Development] pikachu01:
I don't OC, hence I didn't take note of that. I will flash back to Siyah later and take note of it.

If you're running Siyah .12, you refer to Siyah's? After that undervolt from there.

Download MX Video Player. Play those MKV files in software decoding mode. (You'll understand when you've played the file).
[Galaxy S II Original Android Development] Lownita:
I need your help folks! I see a massive battery drain on my phone and I don't see where it can come from. I am on latest hyperdroid + siyah kernel.

I attached a dump of BBS and I hope anyone can tell me why there is 1.5 h screentime vs. nearly 6 hours of waketime :(

Thanks!
[Galaxy S II Original Android Development] kwerdenker:
I named the script 96undervolting for a reason :p If you want to do the other stuff, you'll have to check out the second script in my earlier post :)
[Galaxy S II Original Android Development] AndreiLux:
Well I found an easy method: just leave your charger connected and that will prevent sleep too :p

Conclusion: Disreagard everything I've said: Profiles work perfectly. ondemandx won't go over 500MHz, smartass won't go over whatever I set up in the manual offscreen profile.

The 800MHz thing has nothing to do with profiles I guess, it's the suspend process bugging out :(
[Galaxy S II Original Android Development] kwerdenker:
Dumb question but I like to check this: did you reboot after putting the script in the folder?

Could anyone who has problems with my init-scripts please run this script on your phone? Download it, put it in the root of your internal SD and then execute the following command in adb shell or terminal emulator:

sh /sdcard/dump.sh > /sdcard/dump.txt

After that please post the resulting file.

p.s.: anyone who already used that script in the past, please redownload. I added a new printout to see the content and the permissions in the init-folder.

p.s.2: I'm currently working on an updated version of my scripts. Maybe I can integrate some more feedback/checking to smooth everyones experience.
[Galaxy S II Original Android Development] GDT:
I used your script named "96undervolt" and tried "96undervolting" too and copied under /etc/init.d

But it doesn't work for me. Surely I'm doing something wrong but I don't know how to debug...
[Galaxy S II Original Android Development] GDT:
Obviously yes.
[Galaxy S II Original Android Development] Galaxy_Fan:
Could it be that the governors not working probably working correct?

I used smartass and the battery consumption was high, then I switched to ninphetamine again with SetCPU proflie for screenoff and battery is way better.

Tested on 1.7.8b4.

Do you changed something in rc1 so I should test again?
[Galaxy S II Original Android Development] jcrompton:
Attached are my files:

The dump and the script (I just zipped it)

Thanks!!
[Galaxy S II Original Android Development] gokhanmoral:
you can still use screen off profile with smartassv2 as it has no screenoff max freq limit.

if you have noticably better battery with screenoff profile you need to find out what is preventing deep sleep.

also, I don't believe monitoring several hours would make a fair test about battery comparison.

I made some changes in beta5 and it is already rc1. so yes, I think you should try rc1.

but again, keep in mind that smartassv2 doesn't limit the upper frequency. v1 does and I will introduce more governors in v1.8. if you have background tasks which require cpu power you should definitely use screenoff profile with smartassv2.
[Galaxy S II Original Android Development] kwerdenker:
Could you then please do the same as jcrompton and post the dump and a zip of all scripts in the init-folder (or just your version of my script, if there is nothing else in it)
[Galaxy S II Original Android Development] gokhanmoral:
good to hear that :) I am still testing locking to 500mhz during deep sleep.

it prevents jumping to 800MHz but it feels laggy (maybe placebo effect)

anyway... I think I will revert it to 800mhz as we have tested it already.
[Galaxy S II Original Android Development] kwerdenker:
Could you please post a zip of all scripts in the init-folder? I'm curious if they mess with anything :)
[Galaxy S II Original Android Development] Galaxy_Fan:
sync in background is always on. Is that possible a reason?
[Galaxy S II Original Android Development] hausmanis:
Gokhanmoral are you going to release the speedmod modified with siyah kernel ? and also witch do you reccon got the best batterylife the speedmod modified one or 1,7,8rc1 ?

Greatfull for a reply as my phone is soon burning up from all the reflashes :D
[Galaxy S II Original Android Development] gokhanmoral:
I don't think so. i also have background sync on and I don't need screenoff profiles with smartassv2. 1-2 mins more @800-1200mhz shouldn't matter too much.
[Galaxy S II Original Android Development] gokhanmoral:
I will if smaberg chooses to use it in his rom. if not that means it is not worth releasing. i am also waiting for his decision :)

i named it v1.6reTOUCHed. my first kernel was also based on speedmod's patches. I have only added some more to fix reboots and lockups.

I cannot comment on battery life yet but it was smooth and stable. all the versions are stable on my phone anyway or I would not release them :)
[Galaxy S II Original Android Development] chadouming:
Mahhgg, thats too stable, i hate when my phone is not even crashing 3-4 times a day :P
[Galaxy S II Original Android Development] hugotr:
nice work!
[Galaxy S II Original Android Development] jcrompton:
Hey thanks - here is the zip of the entire folder ....
[Galaxy S II Original Android Development] gokhanmoral:
:D

I have already created a 1696MHz version for you to crash your phone at your pleasure :)

unfortunately, my phone is not holding at that freq to break antutu benchmark record...
[Galaxy S II Original Android Development] chadouming:
I'm sure my phone would hold it :D ^^
[Galaxy S II Original Android Development] o0boiboi0o:
Thanks for this analogy! It is much clearer now! :D So i guess I will change the freq as suggested by you. Btw I can change it using Volt Control right?

What should we expect to happen? Bcos from what I have tested, 100/100 at lowest volt which is 850v, my phone never hang nor freeze. Even at 500/500 at 850v, nothing happened too. What should i do?
[Galaxy S II Original Android Development] eric-filth:
1 - Yes you can use Voltage Control

2 - Try 800mV using 100mhz.
[Galaxy S II Original Android Development] Auridran:
Unless you have Voltage Control Extreme, you can't go lower than 800mV.
[Galaxy S II Original Android Development] eric-filth:
Humm i dont knew that i always used Extreme version.

Tegrak Ultimate can do that too.
[Galaxy S II Original Android Development] pikachu01:
You can also use scripts to apply it ;)

There's a file called cpugputune in /bolt_scripts in ThunderBolt!. You can use Script Manager to run it at boot and it'll work fine with Voltage Control (Voltage Control will show the correct voltages after boot even if you can't physically tone it down to 800mV).
[Galaxy S II Original Android Development] john3166:
gokhanmoral, I've always used your kernel for the gingerbread roms i've installed but now i'm now on ics xxlb 4.0.3. Would you be so kind & generous to work on xxlb too? Thanks in advance. :)
[Galaxy S II Original Android Development] MistahBungle:
No.

Until/unless Samsung release kernel sources this is not possible.
[Galaxy S II Original Android Development] cckc17:
@john3166

why u guys always ask.this meaningless quesion/request., the new kernel for ics will be released when samsung releases their kernel sources for ics, be patient and views the reply please. and think.of the developers
[Galaxy S II Original Android Development] 11768:
What is the way to mount usb otg with write capability?

Previously I was using this and it works fine:

ntfs-3g -o rw /dev/block/platform/s3c_otghcd/sda1 /mnt/sdcard/usbStorage

Now I notice there is no s3c_otghcd folder in it.
[Galaxy S II Original Android Development] omniwolf:
2.6.12 partial SODs

I've started getting pretty regular (once an hour or two?) partial SODs* with 2.6.12. i've tried reflashign the kernel, restoring from backups, deleting cache. i don't UV or OC at all, and i run no scripts. I've gone back to 2.6.9 to see if that fixes it, i'll post again in a few days with my results.

*partial SOD - according to entropy512 with an SOD you can't do anything on the phone, but when i have my SODs i can still view the active kmsg via ADB, if i get a phone call the phone will ring, but i just can't turn the screen on.
[Galaxy S II Original Android Development] eric-filth:
I dont know why but i only had SOD using voltage control before change to tegrak ultimate never more.

yes i use undervolt
[Galaxy S II Original Android Development] ole12:
You should ask in the bbs thread.

As far I could see, you have some big kernel/wifi wakelocks.

On second thought, it might be you router how are sending lots of packets to you phone, and keeps your phone awake. I had that problem with a dlink router.

Try without wifi and see if you have the same awake time.
[Galaxy S II Original Android Development] Lownita:
It seems that it really is the router! Drain is much less without wifi. I checked the router log and about every 30 seconds it says "sending ack to phone-ip". Is there anything I can do? :/

Gesendet von meinem GT-I9100 mit Tapatalk
[Galaxy S II Original Android Development] ole12:
I have no idea, when I googled the wifi issue, it seems it was especially dlink dir-655 that drains battery. Search and you might find a solution. I said gtfo to my router.
[Galaxy S II Original Android Development] fatjivi:
Hey guys i wanted to ask if anyone felt battery life was better with 2.6.11 than with 2.6.12

im using checkrom revodhd v4 and magic config volts
[Galaxy S II Original Android Development] Entropy512:
FFS, READ!!!!!

YOU WILL NOT SEE CUSTOM KERNELS (other than initramfs repacks) FOR ICS UNTIL ICS BECOMES OFFICIAL. SO STOP ASKING.

Do you REALLY think that every single kernel developer here is sitting on their asses ignoring ICS? Have you considered there might be a major reason NO ONE is working on custom kernels for ICS yet? WE DO NOT HAVE SOURCE CODE BECAUSE ICS FIRMWARES ARE LEAKS.
[Galaxy S II Original Android Development] MistahBungle:
Thank-you.
[Galaxy S II Original Android Development] chadouming:
First time i see you getting that much pissed :P
[Galaxy S II Original Android Development] CamoGeko:
I would say .11 is slightly better.

Communicated using an S2 type Droid while floating in CM9 quadrant
[Galaxy S II Original Android Development] tolis626:
Dude,get over it.Chill out and tell these guys "It's okay man,flash it.I just hope you like it when your black screen suits your black phone-I like it minimalistic and it rocks" or something!They don't seem to take it seriously,so we shouldn't take them seriously and we could have a laugh. :D

PS:No,I wouldn't feel bad or ashamed or responsible if a noob of the I-don't-wanna-read-a-thing family bricked their phone because of my "advice" to flash the kernel on their ICS device.They don't take the minimal time they'd need to read,so they only deserve it.
[Galaxy S II Original Android Development] MistahBungle:
^^

+ lots this. People seem less and less willing to read/and take responsibility for trashing their phones on here lately :-/
[Galaxy S II Original Android Development] incubus_fr:
Hey GokhanMoral, I wonder if I can flash Siyah on my Windows7 workstation :p
[Galaxy S II Original Android Development] tsubus:
I always do that when flashing, I still get the issue

Sent from my HTC Vision on ILWT CM7