yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] HellRazorGod:
Hey pikachu

I have a galaxy s2 CheckROM v4 using neka 1.2 and thunderbolt 2.3.3

After a lot of experimenting I finally figured what was causing me SOD as soon as I would switch off my screen after boot after applying thunderbolt. I'm using Voltage Control too but it wasn't causing SOD. It was the S98bolt_siyah script. What exactly does it do? I removed it and used voltage control and today, no SOD. Is there a certain value of the script colliding with the kernel? I was using lulzactive btw.. Is it OK to use thunderbolt without this script? Or maybe you could tell me a value to adjust in this script to avoid SOD. Thanks
[Android Software/Hacking General [Developers Only]] stevehkim:
If you open the script and look at the deep sleep state echo 5 and echo 2. Change the 5 to a 4. save and exit. reboot. No more SOD. I was having the same issue and once I changed that 5 to a 4 no more SOD. Been 2 days now without one. Good luck.
[Android Software/Hacking General [Developers Only]] PedroMRP:
Pikachu01 it appears that ondemandx on latest thunderbolt have a delay on turn the screen on when receiving phone calls on others governors that don't happen.
[Android Software/Hacking General [Developers Only]] PedroMRP:
pikatchu01 I've comment the ondemandx tweaks lines on system_tweaks script and the delay disappeared. You need to change those tweaks.
[Android Software/Hacking General [Developers Only]] PedroMRP:
I've replace the ondemandx tweaks with the tweaks on droidphile tweaks thread and now everything is fine.
[Android Software/Hacking General [Developers Only]] HellRazorGod:
No use Bud. I even tried modifying echo 5 to echo 3. But the moment I switch off the screen, it wont turn back on at all. Instant death with the S98BOLT_SIYAH script :S
[Android Software/Hacking General [Developers Only]] pikachu01:
You don't have to use those governors if they are not included. Use others?

Are you undervolting/overclocking?

Fixed that in the next version ;)

It's the deepsleep level. I'll tweak it and release a fix in the next version. bolt_siyah tweaks some of the SGSII settings.

Yes. The suspend_freq should be 200MHz by default. Also, I've raised the threshold and reduced the sleeping sampling rate for that. Fixed in the next versions. Sorry about that :(
[Android Software/Hacking General [Developers Only]] Sepharite:
Sorry, I'm a complete noob. I tried installing CWM using ROM manager on my i9000m (Canadian Bell), and whenever I try loading CWM, it doesn't allow me to go into any other essential options. It says my signature isn't verified.

I'm assuming I have the older version of CWM?

Will ROM manager premium install the later version of CWM?

Cheers
[Android Software/Hacking General [Developers Only]] Thunder22:
Does this work on cm9 by chance?
[Android Software/Hacking General [Developers Only]] senotrius:
same question here
[Android Software/Hacking General [Developers Only]] saszseb:
No. It doesn't.
[Android Software/Hacking General [Developers Only]] sideeffects:
It does work on CM9 if you use Glitch kernel with init.d support and the latest scripts with new update-binary.
[Android Software/Hacking General [Developers Only]] HellRazorGod:
Still SOD after applying thunderbolt 2.3.4

S98bolt_siyah is causing it.

I guess it's incompatible wih nerk's kernel

is there any modification to the script which might help pikachu?

Thanks
[Android Software/Hacking General [Developers Only]] eliteforce:
No sir! No undervolting/overclocking
[Android Software/Hacking General [Developers Only]] jocke_lulle:
If I only want to revert back to Android default lmk-values, can I just delete the supercharger script from init.d and reboot?
[Android Software/Hacking General [Developers Only]] keuda:
I think you have to delete local.prop too.
[Android Software/Hacking General [Developers Only]] kanye92:
Hi there

I have a big problem - everytime my i9100 goes into a deep sleep, it will not come back on and I have to pull the battery. Not sure what has caused this - have used all addons except the 40/60/80 mb ones. any help is appreciated. also I am using the NEAK kernel 1.2x so not sure if it is a problem with the kernel - not sure how to check. Thanks in advance guys :)
[Android Software/Hacking General [Developers Only]] yani2000:
With Ondemand I still get the same problem.

My only stock ROM was based on Eclair. :)

Every ROM onwards was a deodexed custom ROM hence it always included a modified "Dialer" app.

Since nobody else has the same problem as me, it could be a mod in the "Dialer" app that's causing "Favourites" tab to lag, but it's funny that only "Favourites" tab lags when scrolling (it's not that terrible), everything else is butter smooth (yes, even the Browser in currently used odexed Surface ROM is smooth as silk). :)

Thanks for showing me the root cause of the problem (modded "Dialer" app).

Might check back with another, more severe problem, but back then I wasn't using your scripts.

Will see how things go with your scripts in a few days and when this thread cools down a bit.

Thanks again pikachuuu~! *pika* *pika* :)

---------- Post added at 02:08 PM ---------- Previous post was at 02:02 PM ----------

This is for all users out there!!!:

If you want to revert back to stock from a previously flashed CWM update zip, you need to open that zip with WinZip/WinRar/7Zip and inspect which files were overwritten in which folder!

Then with Root Explorer you can copy from stock backup or if file didn't exist in stock ROM, you can just delete it.

Remember always have a backup near you!
[Android Software/Hacking General [Developers Only]] PedroMRP:
pikachu01 I think you shouldn't set any governor tweaks in system_tweak script and let be the users to make those tweaks by using scripts or an app.
[Android Software/Hacking General [Developers Only]] pikachu01:
Try using other CFS settings (stock maybe?).

NEAK kernel has a problem with SOD. Try deleting the bolt_siyah script and see if you're still getting SOD. If not, then tweak the bus deepsleep level to be 0.

Which governor tweaks aren't good for the users?

Only lulzactive can be tweaked using an app. Others require a script (which ThunderBolt! is one of them?). You mean I shouldn't tweak lulzactive?
[Android Software/Hacking General [Developers Only]] pikachu01:
News

Updated ThunderBolt! to v2.3.4 (and 1.4.3 screenstate_scaling) with some fixes towards governors (ondemandX, ondemand, lulzactive). Also tweaked the bolt_siyah script to have a lesser aggressive deepsleep level. Also tweaked the smooth_offset/smooth_step to scale faster. Disabled the voltage tweaks in bolt_siyah to let users configure it themselves. Also fixed S98graphics. It wasn't saved as a unix file, hence it didn't take effect (not that it will take effect as most phones won't have any reaction to it).

Changelog:

1/2/2012 (2.3.4, screenstate_scaling 1.4.4, graphics 1.0.3)

- Fixed OndemandX, lulzactive, ondemand governor suspend_freq, pump_up_step respectively and sampling_rate (for all governors).

- Commented out graphic voltage settings

- Set deepsleep levels 1 level higher, prevents SOD.

- Fixed S98graphics, save as unix file.

1/1/2012 (2.3.3, screenstate_scaling 1.4.3)

- Updated lulzactive governor to check for minimum/maximum frequency so that it can scale properly

- Updated ondemandX governor to check for minimum frequency so that it can be the suspend frequency, in which previously it was set to 200MHz by default.
[Android Software/Hacking General [Developers Only]] PedroMRP:
The tweaks are good for the users but for example if a user want to tweak some settings, that settings might be overwritten by your tweaks and that can cause some confusion.

If I create a script with governor tweaks I have to make sure that the script will run after the system_tweak and I think that is useless to be setting your tweaks and after that change to my tweaks.

In conclusion should be the user (noob or not) to set the tweaks and learn how to set them via script or if possible by an app like lulzactive and not by changing your scripts so everytime a new release is out the users have to change the tweaks again.
[Android Software/Hacking General [Developers Only]] pikachu01:
You can rename the script to be S99* so that your own tweaks will always override ThunderBolt!'s :)
[Android Software/Hacking General [Developers Only]] Mopral:
Last update works great for me!

Still do not know if graphic tweak works or not but flashed it anyway...
[Android Software/Hacking General [Developers Only]] kanye92:
[/QUOTE]NEAK kernel has a problem with SOD. Try deleting the bolt_siyah script and see if you're still getting SOD. If not, then tweak the bus deepsleep level to be 0.[/QUOTE]

Thanks mate I see - I've switched to Siyah 2.6.2 for the time being and it seems to work fine now :) whats the best kernel to work with THunderbolt! Cheers
[Android Software/Hacking General [Developers Only]] lunchboxVA:
question about sys directory

majority of the scripts included in this package error out because they cannot modify the sys directory...I was wondering if there was a way to manually modify the required directory...add them...so that the scripts would work.

also the wifi suplicant scan interval is set at 60 in this script package...but is set at 150 in the build.prop of the rom i use...

there is also a discrepency between the values of windowsmgr.max_events_per_sec which is set in this script package and what is set in the build.prop of the rom i use...is the discrepency going to cause conflict...which value is going to take precident...and which value is recommended

i run a samsung galaxy sii "epic 4g touch" Blazer ROM Rogue EL26 Kernel and EL26 modem
[Android Software/Hacking General [Developers Only]] bhu1:
Can anyone confirm if thunder is working properly (no reboots and freezes) with cm9 build 12+ glitch??

Also lmk and sqlite?

When I try to install lmk it shows error and no install happens.
[Android Software/Hacking General [Developers Only]] Mopral:
Do not know if all works on CM9

Some of the zip files still have the "old" update.binary file and that is why you have the installation error

Just take the new update.binary file from the OP and upgrade the zip you want to flash with it
[Android Software/Hacking General [Developers Only]] DROCSID:
Or just take the 2.3.1-2.3.4 ones, the DO work.
[Android Software/Hacking General [Developers Only]] seeraj15:
So how do i know if this works after running it as instructed with sciprt manager? I used 3 files, the main thunderbolt one, lmk 50 and 3g. Thanks.
[Android Software/Hacking General [Developers Only]] pikachu01:
I'm using 2.6.4 with ThunderBolt! without problems :)

The init.d scripts will take precedence. You can modify them in init.d (rather than build.prop). Those values won't make much of a difference anyways actually. Wifi scanning 60 as opposed to 150 will be a bit draining, but if you take care to switch off your wifi everytime you go out of range, it won't be an issue.

The windowmanager events also can't produce a visible difference with 60 and 120.

For those that sysfs can't find, it means you're not root or those tweaks aren't meant for your phone. Take note that I'm using the same CWM package for 9 different devices. :) Not all of them will work (they'll just be skipped).

Check the section "How do I know if it works" in ThunderBolt! thread.
[Android Software/Hacking General [Developers Only]] lunchboxVA:
I was wondering if there was a way to modify the s78 enable touchscreen script so it will work on my phone...or if there is a way to add the directories it needs to work to the SYS directory...

the script is:

echo 7035 > /sys/class/touch/switch/set_touchscreen;

echo 8002 > /sys/class/touch/switch/set_touchscreen;

echo 11000 > /sys/class/touch/switch/set_touchscreen;

echo 13060 > /sys/class/touch/switch/set_touchscreen;

echo 14005 > /sys/class/touch/switch/set_touchscreen;

and is supposed to alter the touch screen sensitivity...I noticed it is included in the script package...but when i try to run it it errors out because it cannot create the directories as needed...
[Android Software/Hacking General [Developers Only]] pikachu01:
What phone are you using? The touchscreen tweaks are only for i9000.
[Android Software/Hacking General [Developers Only]] PedroMRP:
pikachu01 I found a small bug in system_tweak script on the disable iostats section you have in the for a "k" variable and in the if the variable is "i".
[Android Software/Hacking General [Developers Only]] lunchboxVA:
interesting...thank you i have an sgsii varient...one of the rom devs for my phone also included the script in their rom which is where i first learned about it...this explains why it errored out thank you
[Android Software/Hacking General [Developers Only]] pikachu01:
Will release the fix in the next version. Good catch. Thanks!

Yeah, your ROM developer would need to check if things work before putting them in :S
[Android Software/Hacking General [Developers Only]] lunchboxVA:
first question

just wondering why there isnt a min free kbytes script ie."echo "4096" > /proc/sys/vm/min_free_kbytes" in the vm tweaks...is it not necessary?

also I saw this on a website " vm.dirty_ratio = 90 : vm.dirty_background_ratio = 55 :

vm.vfs_cache_pressure = 20" and he suggests using "90 : 70 : 1" to squeeze more power out but says that a manual or timed flushing would be needed... in your script you have dirty ratio= 80 background= 65 and 1 for cache pressure... my question is with the settings is a flush of some sort required and how...

last question in your script you have:

"sysctl -w vm.dirty_expire_centisecs=3000; sysctl -w vm.dirty_expire_centisecs=500;"

and then

"#echo 3000 > /proc/sys/vm/dirty_expire_centisecs; echo 500 > /proc/sys/vm/dirty_writeback_centisecs"...first i assume that the sysctl is supposed to read dirty writeback cent= 500...to match the echo script

but how come

dirty expire centisecs = 3000 and dirty writeback =500

when another battery tweak has

dirty expire centisecs= 500 and dirty writeback = 1000; instead of the dirty expire and dirty writeback values switch to read "DEC"= 1000 and "DWC"= 500

sorry for being so bothersome.
[Android Software/Hacking General [Developers Only]] pikachu01:
Yup. min_free_kbytes is calculated automatically by the kernel at boot. It's supposed to be a percentage of your total RAM.
[Android Software/Hacking General [Developers Only]] acras:
pikachu01

This code in system_tweak causes my CPU stacks on highest frequency - 1200MHz

# ==============================================================
# smartassV2
# ==============================================================
echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/awake_ideal_freq;
if [ "`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq` -eq 200000" ]; then
echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;
else
echo "100000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_ideal_freq;
fi;

echo "800000" > /sys/devices/system/cpu/cpufreq/smartass/sleep_wakeup_freq;

echo "95" > /sys/devices/system/cpu/cpufreq/smartass/max_cpu_load;
echo "90" > /sys/devices/system/cpu/cpufreq/smartass/min_cpu_load;

echo "1000000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_down_step;
echo "200000" > /sys/devices/system/cpu/cpufreq/smartass/ramp_up_step;

Could it be because of kernel has 6 CPU stages instead of 5 in stock?

I'm on i897 with re-oriented corn kernel 1.02
[Android Software/Hacking General [Developers Only]] pikachu01:
It's always on the highest frequency? As in never sleeping at all?

Hmm, it might be the cpufreq.c code itself that is modified by the kernel author.
[Android Software/Hacking General [Developers Only]] eliteforce:
Pika

Im now on [ICS] Onecosmic's ICS Port Android 4.0.3 RC2.1

and Kernel Glitch ICS-RC2.1-i9000-Glitch.zip

After installing

ThunderBolt-CWM 80MB LMK Others addon v1.0.4.zip

ThunderBolt-CWM bin files addon v1.1.1.zip

ThunderBolt-CWM libsqlite addon v1.0.1.zip

ThunderBolt-CWM v2.3.4.zip

Phone doesnt startup - bootloop (
[Android Software/Hacking General [Developers Only]] acras:
Not always, rarely frequency goes to 1000 and 800MHz but never to deep sleep.

With this raws commented it does.
[Android Software/Hacking General [Developers Only]] pikachu01:
Don't flash the bin files as well as libsqlite!

Others might work.
[Android Software/Hacking General [Developers Only]] pikachu01:
The kernel author might've modified the smartassV2 code or the cpufreq scaling.
[Android Software/Hacking General [Developers Only]] eliteforce:
thankz mate!

I think you must add to OP

Others works good:) phone is smooth now
[Android Software/Hacking General [Developers Only]] saszseb:
It doesn't work with me.
[Android Software/Hacking General [Developers Only]] Kurre:
Well it says in requirements "Android 2.3.x", so ics isn't even supported.. ;) and flashing something without proper support is always little risky..so I'm gonna try it out soon also (TH's ics build 12) :D

Sent from my CM'd SGS
[Android Software/Hacking General [Developers Only]] pikachu01:
You need the newer updater_binary. It's in the 2nd post.

Yeah, some don't work well :(

I'll begin making it compatible once ICS is stable enough for daily use.

Yup. 2.3.x is the minimum requirement. Hence, it'll only work partially.
[Android Software/Hacking General [Developers Only]] iamsmallpang:
hi pikachu01,

(S98system_tweak) had not found that code in (/system/etc/init.d/)

that mean i flashed a wrong way
[Android Software/Hacking General [Developers Only]] lunchboxVA:
lol u respond really fast you responded minutes before i was able to edit my question...if you havent seen it already would you mind answering:

also I saw this on a website " vm.dirty_ratio = 90 : vm.dirty_background_ratio = 55 :

vm.vfs_cache_pressure = 20" and he suggests using "90 : 70 : 1" to squeeze more power out but says that a manual or timed flushing would be needed... in your script you have dirty ratio= 80 background= 65 and 1 for cache pressure... my question is with the settings is a flush of some sort required and how...

last question in your script you have:

"sysctl -w vm.dirty_expire_centisecs=3000; sysctl -w vm.dirty_expire_centisecs=500;"

and then

"#echo 3000 > /proc/sys/vm/dirty_expire_centisecs; echo 500 > /proc/sys/vm/dirty_writeback_centisecs"...first i assume that the sysctl is supposed to read dirty writeback cent= 500...to match the echo script

but how come

dirty expire centisecs = 3000 and dirty writeback =500

when another battery tweak has

dirty expire centisecs= 500 and dirty writeback = 1000; instead of the dirty expire and dirty writeback values switch to read "DEC"= 1000 and "DWC"= 500

sorry for being so bothersome.
[Android Software/Hacking General [Developers Only]] pikachu01:
Yup. Did you mount /system and /data before flashing?

What is "another battery tweak"?

The flush is optional actually. Linux's memory management is good enough to flush cache when it is needed (I tested it out and it works well). I did include the script to drop caches (it's in /bolt_script/drop). You can run that or do a cron script to launch it at intervals.

The sysctl and echo is doing the same thing. Sysfs interfaces can sometimes be referenced by using the sysctl command.

About the dirty_expire and dirty_writeback, dirty_writeback kicks in every 5 seconds to write expired data. dirty_expired marks each data as expired after 30 seconds.

The 5 and 30 seconds are actually default in the 2.6.35 kernels. It is well tuned enough to be the default (after reading the source code). It is for this reason, the dirty_ratio being high is tolerable (as dirty data is written out promptly). As for the vfs_cache_pressure, it's something unrelated, but mapped in the same memory space. It just favours active data being kept in RAM rather than being written out at the next opportunity.
[Android Software/Hacking General [Developers Only]] lunchboxVA:
another build.prop tweak question

when i asked you before about the build.prop tweaks included in thunderbolt you said int.d scripts take precendent over whats included in the build.prop...

i was wondering if those build.prop tweaks included in thunderbolt add to/alter what is included in the build.prop or if they completely replace whats in the build.prop as in remove whats already there

i am think add/alter....but please if you dont mind confirming?
[Android Software/Hacking General [Developers Only]] pikachu01:
Add/alter :)
[Android Software/Hacking General [Developers Only]] saszseb:
You said this 3 weeks ago,as well.

It has been stable enough.
[Android Software/Hacking General [Developers Only]] pikachu01:
LOL. When ICS is stable means it's Samsung ICS. I still need the video calling ability :P
[Android Software/Hacking General [Developers Only]] saszseb:
Also the answer is the same.

Sent from Onecosmic's ICS using Glitch kernel
[Android Software/Hacking General [Developers Only]] SAEVARM3:
Sooo .... Is ThunderBolt so powerful that it jumped into the future " 1/4/12 " ? :)
[Android Software/Hacking General [Developers Only]] Vipitus:
In America (and some other countries) date format is mm/dd/yy ;)

In Europe we use dd/mm/yy.

Galaxy S - Tapatalk
[Android Software/Hacking General [Developers Only]] DROCSID:
It's stable for a long time imho. I use it as daily ROM for a lomg time now. CM9 has it except a few things i don't care as a stable ROM :).
[Android Software/Hacking General [Developers Only]] SAEVARM3:
That would make it 1 April 2012 haha ...

But yeah, I all of a sudden realized that there are time differences LooooL ;)

Peace
[Android Software/Hacking General [Developers Only]] Vipitus:
ROTLF, I thought that today is 4 January :D

Sorry for that ;)
[Android Software/Hacking General [Developers Only]] Mopral:
Do not forget that where Pikachu01 live, it is already 4 january...

http://24timezones.com/fr_heure/malaysia_penang_horloge.php
[Android Software/Hacking General [Developers Only]] RaymondPJR:
Thunderbolt!

Correct me if I am wrong, but isn't it more likely that Passion is based on CM7 and that is why the bin files and patched libsqlite won't work. That much is in the OP, (warnings for CM7:))
[Android Software/Hacking General [Developers Only]] pikachu01:
LOL.

CM9 is currently not supported. You could try the main CWM and screenstate_scaling as well as the LMK, but that's it.
[Android Software/Hacking General [Developers Only]] sherpa25:
I also tried Onecosmic's ICS a couple of days ago and although the UI seemed to work fine, I had several FC's running some apps, so I had the impression these apps are not yet ready for ICS, and had to revert back to Simplicity/Semaphore/TB!.
[Android Software/Hacking General [Developers Only]] pikachu01:
News

Updated ThunderBolt! to v2.3.5 (and 1.4.5 screenstate_scaling) with some fixes towards governors (ondemandX, ondemand, lulzactive). Also tweaked the bolt_siyah script to disable smooth_target/offset/step. Fixed the iostats bug also.

Changelog:

1/4/2012 (2.3.5, screenstate_scaling 1.4.5)

- Decreased the up_threshold for lulzactive, ondemand, ondemandx, smartassV2 for faster scaling.

- Disabled smooth_target/smooth_step/smooth_offset. Brings stutters to ondemand/ondemandX.

- Fixed iostats bug - Thanks PedroMRP.
[Android Software/Hacking General [Developers Only]] RaymondPJR:
Thunderbolt!

No, the point I was trying to make was that I think the Passion ICS ROM has a CM base so that is why that guy maybe had problems with the bin files and the libsqlite. Not sure, but think so.
[Android Software/Hacking General [Developers Only]] hackeron:
A problem, when I turn off the screen it flashes green? Using all tweaks except 3g fix, and jw1 and latest semaphore 2.4 any ideas?

Edit: I removed all tb scripts and it still flashes green so not tb's fault :)

And pika the restore zip did not remove the bolt siya script.
[Android Software/Hacking General [Developers Only]] bgx:
Getting error with screenstate_scaling -> unexpected "fi"

Have edit it with jorta texteditor reloaded and try again. Same problem...

Something wrong with the script?

EDIT: Forget it; it's working