[Q] [P] Broken Offline Charging & Underclocking Resets After Screen is Off - Sony Xperia P, U, Sola, Go

Hello everyone ..
Well I have two problems here that happened after I unlocked my bootloader and flashed the awesome Nemesis Kernel ( over stock firmware with Fidelity JB 2.0 rom ).
Actually I wanted to post these issues at the Nemesis thread, but due to new membership limits I couldn't, so I hope that you guys can help, and especially @nicolassp
----------------
1. Offline charging is broken. I searched for this issue and came up with that it may be due a corrupted charger file after flashing a new cwm ( the one bundled with Nemesis maybe ) over a previous cwm. I don't know if a flashable undamaged charger file could do the job or not.
2. Underclocking issue. I was trying to underclock the cpu to 800 mhz using NoFrills app, it works at the beginning, but after you lock the screen and wake the phone up again it resets to default 1 ghz! I tried other cpu control apps with the same result ( Could it be some sort of conflict with Fidelity? ).
Anyway I appreciate any help from you guys, thx in advance

oliveri5 said:
Hello everyone ..
Well I have two problems here that happened after I unlocked my bootloader and flashed the awesome Nemesis Kernel ( over stock firmware with Fidelity JB 2.0 rom ).
Actually I wanted to post these issues at the Nemesis thread, but due to new membership limits I couldn't, so I hope that you guys can help, and especially @nicolassp
----------------
1. Offline charging is broken. I searched for this issue and came up with that it may be due a corrupted charger file after flashing a new cwm ( the one bundled with Nemesis maybe ) over a previous cwm. I don't know if a flashable undamaged charger file could do the job or not.
2. Underclocking issue. I was trying to underclock the cpu to 800 mhz using NoFrills app, it works at the beginning, but after you lock the screen and wake the phone up again it resets to default 1 ghz! I tried other cpu control apps with the same result ( Could it be some sort of conflict with Fidelity? ).
Anyway I appreciate any help from you guys, thx in advance
Click to expand...
Click to collapse
2. If you installed CWM before flashing nemesis than that is why you cannot charge offline, known problem, and it is still active BTW if you wait after nemesis CWM turn inactive pressing the volume down will bring up old CWM.
To fic this simply copy stock chargemon to /system/bin/ and set permissions to 755.
2. The ROM mod may have installed scripts that change cpu max/min frequency.

Thanks very much Chike, btw, can you kindly upload this file to me? ( and if it's a flashable zip I would appreciate this very much ).
And if it's a script by Fidelity that is causing the clocking issue, where could it be so that I can modify it?

oliveri5 said:
Thanks very much Chike, btw, can you kindly upload this file to me? ( and if it's a flashable zip I would appreciate this very much ).
And if it's a script by Fidelity that is causing the clocking issue, where could it be so that I can modify it?
Click to expand...
Click to collapse
Are you 6.2.A.1.100 based ROM?
The file can be extracted from system.sin in the ftf file, if not I can upload the one from my phone.
I don't know that ROM, I am guessing one of the files in /etc/init.d/ search for "/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" and comment it out ("#" at the beginning of line.)

ChikeD said:
Are you 6.2.A.1.100 based ROM?
The file can be extracted from system.sin in the ftf file, if not I can upload the one from my phone.
I don't know that ROM, I am guessing one of the files in /etc/init.d/ search for "/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq" and comment it out ("#" at the beginning of line.)
Click to expand...
Click to collapse
Yes please upload it for me because I don't have the ftf at the moment and my internet connection is so bad ..
Also I uploaded the screen-state script so that you take a look at it ..

oliveri5 said:
Yes please upload it for me because I don't have the ftf at the moment and my internet connection is so bad ..
Also I uploaded the screen-state script so that you take a look at it ..
Click to expand...
Click to collapse
You see the lines
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $max_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
and
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
You can simply comment the out or replace $max_freq with different value
Code:
#max_freq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`;
max_freq="800000"
Rename old chargemon to chargemon.cwm in case you choose to use stock kernel again, and change it's permissions to 644 (no execute bit) copy chargemon to /system/bin and set permissions to 755 (read all, write owner, execute all)

ChikeD said:
You see the lines
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $max_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
and
Code:
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq;
echo $min_freq > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq;
You can simply comment the out or replace $max_freq with different value
Code:
#max_freq=`cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq`;
max_freq="800000"
Rename old chargemon to chargemon.cwm in case you choose to use stock kernel again, and change it's permissions to 644 (no execute bit) copy chargemon to /system/bin and set permissions to 755 (read all, write owner, execute all)
Click to expand...
Click to collapse
You are right.. The script sets the max speed of cpu and there is no problem with Nemesis Kernel.Thank you

Thank You!
It worked! Thank you very much Chike and yes nicolassp your kernel is working like a charm!

Related

hw_config.sh updating using echo command

firstly i'd like to apologize if this has been brought up before (i can't seem to find it), or if i'm posting in the wrong subforum. i originally made a thread in General but it seems that the entire subforum has far less visitors than here...
now idk if anyone's figured this out yet, but i just tried it and it works.
instead of pulling out hw_config.sh, editing it, then pushing it back again or just plain editing it from the phone itself, we can use the "ECHO" command...
from the shell:
# remount
# echo "whatever you want to put here" >> /system/etc/hw_config.sh
Click to expand...
Click to collapse
it will append whatever it is you typed within the " " to the END of hw_config.sh
still haven't figured out how to do insert new line in it tho apart from multiple echo commands.
i think this can be particularly useful for devs like doixanh who's said that he needs to create a custom zip for different ROMs? maybe something like that can be put into the xrecovery update script? idk how to go about editing that file so i didn't wanna try it.
maybe something for his for example mddi module can have a command like
echo "insmod /system/lib/modules/x8mddi.ko # fix mddi lags" >> /system/etc/hw_config.sh
Click to expand...
Click to collapse
or something like that
Simple universal solution: don't edit hw_config. Use chargemon, that way only one update zip is needed.
can't say i know what it is or how to use it i'm still quite new to all this hehe. will look it up tho. i do know a little basic linux and command line things so i was just trying it out to see if it works since DX said he won't be making custom zips for all the different ROMs out there but many ppl seems to be asking for one. just thought maybe it would help :shrugs:
add to the second (empty one) line in chargemon this:
insmod /system/lib/modules/ModuleName.ko
You can add more insmod lines, one bellow another.
Then everyone should update recovery with FlashTool 0.2.9.1 to avoid any issues, and push new chargemon to /system/bin
Of course, you can modify the positioning in chargemon, for example, place insmod lines after keypress check - for booting into recovery, to make it still possible to boot into recovery if modules cause bootloops.

[kernel module/beta] OPPtimizer Projekt - OMAP4 Overclocking

Just wanted to let you guys know I got some kernel modules up for testing. These are unverified on nook tablet. So far reports are that "0.1 modules" with top frequency manipulation only work pretty flawlessly on devices tested. "0.2 modules" with top frequency and voltage manipulation, seem to work on Motorola Droid RAZR & Droid 3. Motorola Bionic & Atrix 2 don't like voltage manipulation at this point. I need beta testers.
opptimizer.googlecode.com
More info can be found and the original thread on RootzWiki:
http://rootzwiki.com/topic/14511-op...g-kernel-modulesofficial-thread/page__st__200
I downloaded and installed this. I ran linpack a few times and had a moderate jump in scores. I have not been able to play with it much more, however. I can do some more testing too.
Thank u for this post. I had been asking this question in a few other threads and people were naysaying that it couldn't be done. Im glad to see that I was on the right track.
Any idea on how to make if persistent? All is lost on reboot, however works well with setcpu. No noticeable battery drain or heat in beta 0.2 with 1200000000 1388000. Linpsck 57, Antutu 5390. Excellent discovery! Anything. Above 1200mhz is not stable and may crash. I had one crash the tablet froze; held down the power button 10 seconds to power off and then reboot.
Works very well. A permanent solution would be great.
Sent from my Nook Tablet using XDA Premium App
You need init.d to run at startup. There is a thread on how to get init.d scripts working here:
http://forum.xda-developers.com/showthread.php?t=1390093
You don't need all the build.prop stuff to overclock, just the init.d support at the top.
I have a post on where the file should be put, and what it should look like here:
http://rootzwiki.com/topic/14511-op...g-kernel-modulesofficial-thread/page__st__190
The init script was created by frostincredible for running at boot on Motorola Droid Bionic. His thread is here:
http://rootzwiki.com/topic/14698-in...or-tekahunas-omap4-overclock-modules-1-10-12/
Using the last link in your post, here is what I found to have the Nook Tablet boot persistently into the desired overclocking speed.
1. Extract the init.d folder from the init scripts created by frostincredible and using ES File Explorer, copy to /system/etc directory
2. Download tekahuna version 1.0 files, (symsearch.ko and opptimizer.ko) and extract and copy them to /system/lib/modules directory. Create the modules directory if it does not exist.
3. Reboot and use Rom Tool or Setcpu for your desired CPU speed. I'm using 1.2GHZ on the Nook Tablet. I did try to flash the files using CWM, however the system partition identified in the zip file is not correct for the Nook Tablet.
4. I thank everyone involved for their work on this as this mod really perks up the Nook Tablet. See my previous post above on the new benchmarks at 1.2GHZ.
UPDATE I broke the persistence and caught He** trying to figure out what I did wrong. A step not mentioned above requires you to edit clrbootcount.sh located in /system/bin. You must add the init.d code below to end of the code in the file. From that point forward the tablet will boot at the script speed you have placed in /system/etc/init.d. I do not recommend anything above 1200. Set permissions on clrbootcount.sh to rwxrwxrwx. You can shrink the permissions once you get it running.
bb=/system/xbin/busybox
if [ -f $bb ]; then
/system/bin/logwrapper $bb run-parts /system/etc/init.d
else
for i in $(ls /system/etc/init.d/*); do
sh $1
done
fi
rapcon said:
Using the last link in your post, here is what I found to have the Nook Tablet boot persistently into the desired overclocking speed.
1. Extract the init.d folder from the init scripts created by frostincredible and using ES File Explorer, copy to /system/etc directory
2. Download tekahuna version 1.0 files, (symsearch.ko and opptimizer.ko) and extract and copy them to /system/lib/modules directory. Create the modules directory if it does not exist.
3. Reboot and use Rom Tool or Setcpu for your desired CPU speed. I'm using 1.2GHZ on the Nook Tablet. I did try to flash the files using CWM, however the system partition identified in the zip file is not correct for the Nook Tablet.
4. I thank everyone involved for their work on this as this mod really perks up the Nook Tablet. See my previous post above on the new benchmarks at 1.2GHZ.
Click to expand...
Click to collapse
I followed instructions using the1200 package, but setcpu and rom toolbox still show 1008 max frequency. What else can I be missing?
I had this problem and I can only suggest the following:
*Ensure you are using version 1.0 of the kernel modules
*check all permissions on the init.d folder in /system/etc and /system/lib/modules
If all goes well after the reboot, the tablet should be reporting 1200 in the Rom Toolbox CPU panel.
Version 2 of the kernel modules allow for voltage manipulation and the scripts in the init.d directory are not written to take advantage of that and therefore will not run. The scripts can be modified however.
rapcon said:
I had this problem and I can only suggest the following:
*Ensure you are using version 1.0 of the kernel modules
*check all permissions on the init.d folder in /system/etc and /system/lib/modules
If all goes well after the reboot, the tablet should be reporting 1200 in the Rom Toolbox CPU panel.
Version 2 of the kernel modules allow for voltage manipulation and the scripts in the init.d directory are not written to take advantage of that and therefore will not run. The scripts can be modified however.
Click to expand...
Click to collapse
It runs great from the command line, but the init.d fix isn't working for me. I've set all permissions to 777. I'll have to fiddle around with it some more. I'm running at 1.2GHZ until I reboot.
I actually didn't get mine to stick at boot until i set the permissions on the file in the init.d folder (00cpufreq_modules) to rwxr--r--. I believe thats what did the trick for me. (I had it at rw-r--r-- before).
Can we OC the GPU as well? Thanks
Awesome, it works and it does seem snappier. I also couldn't get it to stick at boot, but I made the /system/lib/modules/*.ko files with full permissions (777 I think?) The rest of it, the init.d file, the 0.1 files, etc are all as posted. What did people set the .ko files permissions as?
UPDATE:
Tried it with rwxr--r-- and rw-r--r-- on both the ko files as well. Still didnt stick at boot. Also then tried to make a script in Rom Toolbox to run, and it said it ran successfully, but didn't show any change when I checked it (still at 1008). Using Rom Toolbox because SetCPU wouldn't install btw. And Script Manager just hangs and force closes after a while.
Any ideas?
I'm all for development and "lets see what this puppy can do" but I have to ask - Isn't this puppy fast enough? How fast do you want it? Any faster and it would be answering the questions before your asked.
It's a dual core. It's just a question of how much you want out of it, same as the Nook Color before it. I'm 100% behind overclocking because of the principle - if it's possible, why not?
neoage said:
It's a dual core. It's just a question of how much you want out of it, same as the Nook Color before it. I'm 100% behind overclocking because of the principle - if it's possible, why not?
Click to expand...
Click to collapse
My only thought is, how much actual difference would it make? Will things run smoother? Will graphics be sharper, flow more easily?
Sent from my rooted Nook Tablet using Tapatalk 8)
What about if you find out you can have 2x1.2Ghz without any battery penalty or thermal problems?
rapcon said:
UPDATE I broke the persistence and caught He** trying to figure out what I did wrong. A step not mentioned above requires you to edit clrbootcount.sh located in /system/bin. You must add the init.d code below to end of the code in the file. From that point forward the tablet will boot at the script speed you have placed in /system/etc/init.d. I do not recommend anything above 1200. Set permissions on clrbootcount.sh to rwxrwxrwx. You can shrink the permissions once you get it running.
bb=/system/xbin/busybox
if [ -f $bb ]; then
/system/bin/logwrapper $bb run-parts /system/etc/init.d
else
for i in $(ls /system/etc/init.d/*); do
sh $1
done
fi
Click to expand...
Click to collapse
...I haven't tried this, but looking at this script I'm wonderingif the "sh $1" should really be "sh $i" ...this should make it run all init.d scripts if busybox is not installed at the expected location.
(As it was written it will instead try to execute $1 which is probably the first argument passed to the clrbootcount.sh script unless otherwise defined in the script... without my suggested change the for loop doesn't do anything with the init.d scripts)
I hope the project's going well! Took a look at the rootzwiki site and saw how it was going for the other devices...Just wondering if it's still happening for the Nook Tablet, since CM7 is right around the corner...
neoage said:
I hope the project's going well! Took a look at the rootzwiki site and saw how it was going for the other devices...Just wondering if it's still happening for the Nook Tablet, since CM7 is right around the corner...
Click to expand...
Click to collapse
Cm7 is OUT mh friend, and its AWESOME
Sent from my CM7 Nook Tablet

[FIX] Xperia U Touchscreen not working on JB & KitKaT ROM

Some guys have problem using a JB or KitKat because though their Boot-loader is Unlocked, they can not Use the ROM after flashing. Because the Touchscreen will not respond after the new ROM Boots up. So, they are stuck with the ICS Stock that Sony gave. There is a Thread Touch does not work
I was one of these guys.
Well Guess what I got a solution.
So, I am going to write the procedure directly. But first, go and thank these two people...
1. erw1n for this post http://forum.xda-developers.com/showpost.php?p=46276864&postcount=81
2. bangladeshi for this thread. [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
I Got the Idea from them.
Special Note: I'm not responsible if you brick or damage your phone.
The procedure goes as follows. I'm giving the detailed Instructions later.
Download the desired ROM
Extract Touch Screen Firmware and related files from Stock Official Sony FTF or any other source
Open ROM with 7-Zip or any other Zip Software and replace the Firmware Files with Stock ones.
Modify the hw_config.sh file in the ROM if necessary.
Close the ZIP
Flash the ZIP with CWM
Now Goes the Details-
Step One: I Did it with only [ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES. So it's not tested on any other ROM. Theoretically It should work on any ROM. So, Cheers Download your ROM.
Step Two: If you dont want to do all these, then just download the zip file in the attachment and unzip it. for the official Sony firmware files
Else,
You will need FlashTool and Stock Official Sony ICS FTF and Notepad++ or any similar code/text editor and 7-zip for this. You will also need ext2explore (If you know what you are doing then you can also download the CWM flashable one ROM.)
First Open the FTF in 7-zip. Extract the System.sin file and put it in a folder lets say, "ICS_Stock". Now open FlashTool. Go to Sin editor.Browse for the sin file and click on Extract Data. Now after it finish, you will see four extra files in the ICS_Stock folder. with different extensions. one will be ext4. (something like "system_S1-SW-LIVE-3065-PID1-0002-S1-PARTITION.ext4")
Close FlashTool, Open ext2explore (as administrator). Go to file, Open Image, and select the ext4 you just extracted.
browse through the files,
Go to system/etc/firmware, right click on ttsp_fw.hex, save it.
Go to system/bin, right click on cyttsp_fwloader, save it.
Go to system/usr, right click on the folder idc, save it.
Close the ext2explore
Step Three: Now open the downloaded ROM with 7-Zip. Now Pay very careful attention
Go to system/etc/firmware, and delete ttsp_fw.hex if exists.
Go to system/bin, and delete cyttsp_fwloader if exists.
Go to system/usr, and delete folder named idc if exists.
Go to system/etc, and extract file named hw_config.sh after extract and save it in the same folder as other files, delete the file from the zip.
Now again
Go to system/etc/firmware, and drag and drop the ttsp_fw.hex file you just saved. (There will be a warning "Are you sure, you want to copy files into archive.... bla.. bla.. bla..." just say Yes)
Go to system/bin, and drag and drop the cyttsp_fwloader file you just saved.
Go to system/usr, and drag and drop the idc file you just saved.
Now comes the vital Part,
Open the hw_config.sh file with Notepad++ you will find some lines like this one,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex
# Audio jack configuration
if it is just like my example then, change the lines to
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
(Just add a -force)
If its not like the example and you don't have a clue what to do, Ask in this thread, If I'm there, I'll reply what to change.
it could be something like below, (taken from the Chienise Guy ROM 6.2.A.1.100 Xiangxin X3
Code:
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
fw=ttsp_fw.hex
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags="" ;;
esac
case "$app_id" in
"0x3030") flags=-force ;;
*) echo $app_id > /data/ttsp_appid ;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/$fw $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Here you may or may not change. but if you really want to change, change it to,
Code:
# Touch FW loader
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /etc/firmware/ttsp_fw.hex -force
# Audio jack configuration
Then save and close the hw_confif.sh file.
Now again go to your ROM opened with 7-zip, and Go to system/etc, and drag and drop the hw_confif.sh file you just saved.
Close the ROM Zip.
Step Four: your Fixed ROM is ready. Take all the Backups you need and don't need . Go to CWM, and also take all the NANDROID backup.
Now keep your fingers crossed and flash the Modified ROM as the instructions say in the Main Thread from where you downloaded the ROM.
If this solution works, Thank the ROM Builder first and then me.
Please Note: Do not distribute the Modified ROM without the permission of the Original Developer.
and Don't Blame Me or the Developer if the solution don't work for you. It worked for me.
If it worked for you, then Please tell us, for which ROM the solution worked. We can make a list of Compatible ROMs for this Modifications.
Up to now, this trick is confirmed to work on Two ROMS.
[ROM] [UB] [Kitkat] [4.4.2] CyanogenMod 11.0 NIGHTLIES
JB Thunder Strike
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
erw1n said:
im really2 thank you.. for your tips..
yeah ,, now my xu rom JB Thunder Strike..!!
touchscreen problem solved..
Click to expand...
Click to collapse
The KitKat Nightly Is very stable and fast for me. Sometimes the Touch hangs again. I just remove the battery and re-insert it again. And Viola. it Works.
Glad that it worked. Now what I am going to work on is, how to make, Recovery Mode Touch work. I know it's tough, but possible.
CWM Flashable ZIP for recovery touch
I had noticed that, though the ROM Touchscreen works, but in recovery, the touch don't work. So, have made a CWM Flashable ZIP file, if you flash it, hopefully the touch will start to work inside the Recovery. Please note, This is not a permanent solution. You have to flash this file each time you go in recovery.
Once again, I tasted it with only CM11 Nightlies.
If it works, I will try to modify this file to act like a patch for all ROMs. So that, you can flash any ROM and after that you can flash this patch to make touch usable.
@[B]jatinrungta[/B] Can you test it for me?
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
evilfox7 said:
I tried to extract from system.sin but I only got system.partinfo and system.yaffs2 files. I am trying to fix my mini pro (mango) touch screen and I used the stock ROM SK17i_4.1.B.0.431_(1249-7380).ftf to get the system.sin. Any thoughts?
edit:
Can you also provide an updated CM11 that has a fix on it for sk17i (mango)? I will really appreciate it.
Click to expand...
Click to collapse
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
pollob666 said:
Sorry for the late answer.
But problem is, I don't have SK17i the set in my hand. So, I am not sure, the fix, I did, will work on your one.
Still, I'm going to download and make a cwm installable zip from the Sony stock ftf. I'm gonna download the FTF tomorrow, i have transfer cap and provide you a CWM file for CM11. Need to search the sk17i (mango) forums. But, you can try with a yaffs2 explorer, it'll work as ext2explorer.
Click to expand...
Click to collapse
I will look forward for it. Anyway, I will try to use the yaffs2 and hopefully it has the same structure with your original post.
i have this trouble but is was like this when i flash GB back (i was on ICS stock rom)
But i try to revert and back to ICS and dont work
Can anyone help me please!
Xperia sola unresponsive touchscreen
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
The code is below.
# Touch FW loader
dev=/sys/bus/spi/devices/spi9.0
app_id=`cat $dev/appid`
case `cat /data/ttsp_fw_update` in
"in_progress") flags=-force ;;
*) flags=-no-downgrade ;;
esac
case "$app_id" in
"0x3030")
flags=-force
;;
esac
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev $dev -fw /system/etc/firmware/ttsp_fw.hex $flags
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
bhatadarsh said:
Hi,
I tried the steps that you have suggested, But in the final part(hw_config.sh) with the code, i had something different. I dont know how to alter it. Can you help me out??
Click to expand...
Click to collapse
Yes, Just replace the lines with these below,
Code:
# Touch FW loader
#dev=/sys/bus/spi/devices/spi9.0
echo "in_progress" > /data/ttsp_fw_update
cyttsp_fwloader -dev /sys/bus/spi/devices/spi9.0 -fw /system/etc/firmware/ttsp_fw.hex -force
echo "done" > /data/ttsp_fw_update
# Audio jack configuration
Go to system/usr, right click on the folder idc, save it.
Go to system/usr, right click on the folder idc, save it.
There is no IDC folder .....help me....

[09.01][Script]schedtune.boost - making Pixel XL (and eas) even more smoother

hello guys and girls,
I am quite sure everyone knows and feels that our pixels are already super smooth. However few of us are never completely satisfied and are looking for ways to make the device even more smoother.
Some of you might be aware, that the sched governor, which is bound to eas, isn´t as customizable as the old interactive governor. This is the main reason we don´t have any scripts or tweaks touching the governor.
So I did some digging and finally found a tunable that allows the cpu to be even more aggressive. This will result (at least for me) in a tremendous effect on overall smoothness. Battery life will take only a slight or a grave hit, depending on the boost you choose. @Alcolawl you are free to do benchmarks
The schedtune.boost (s) reside in the directories /dev/stune, dev/stunde/foreground and dev/stune/background
You can apply values from 0 to 100.
When setting it to 100 your device will run constantly with all cores maxed out.
I found values from 2 to 10 to have the most efficient effect.
I am currently using a boost value of 8. Battery life is still awesome. But oh my god how smooth the device runs now.
Remember: you can also set the values higher yourself
For your convenience I made scripts that you can either put in system/etc/init.d or system/su.d. I am planning to refine and maybe add more tweaks to our pixels. So stay tuned and lets all work together. The script does not look like much, but try it before you judge.
Download links will be in the second post.
Instructions:
1. Download the desired file. sched2 means a boost value of 2 will be applied. sched6 means a boost value of 6 will be applied. I think you get the concept.
2. Extract the script from the download
3. Copy the script to either system/etc/init.d or system/su.d
4. set permissions to 0755 (rwxr-xr-x) via terminal or your preferred root explorer.
5. reboot and wait a minute (there is a sleep timer)
6. profit
7. to check if the script got applied correctly do in terminal on your phone
su
cat dev/stune/schedtune.boost
Attention:
su.d only works when you have working root via supersu from chainfire.
Credits:
google for integrating eas to our pixels
@Alcolawl for letting me use his scripts on the HTC 10 and inspiring me greatly in the process. If he did not exist I probably wouldn´t have looked into finding this
Downloads:
init.d and su.d:
https://www.androidfilehost.com/?w=files&flid=140794
01.07.2017
I added an all in one package. The all-in-one package has all scripts with boost values including 2,4,6,8 and 10. So you do not have to start multiple downloads.
09.01.2017
v1:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 15
- schedtune.boost for all other activities (that are not getting categorized) is set to 10
v2:
- decreased the default boost value for top app from 50 to 25
- foreground-app has a boost of 12
- schedtune.boost for all other activities (that are not getting categorized) is set to 8
Freak07 said:
Downloads:
init.d:
https://www.androidfilehost.com/?w=files&flid=140135
su.d:
https://www.androidfilehost.com/?w=files&flid=140130
Click to expand...
Click to collapse
Trying to execute it through root browser and get this: http://i.imgur.com/WbUsV6g.png
Put it in su.d directory. Not sure if it is applying on boot.
XtraArrow said:
Trying to execute it through root browser and get this: http://i.imgur.com/WbUsV6g.png
Put it in su.d directory. Not sure if it is applying on boot.
Click to expand...
Click to collapse
What kernel are you on?
Did You run it from sdcard or su.d?
did you set the right permissions?
Freak07 said:
What kernel are you on?
Did You run it from sdcard or su.d?
did you set the right permissions?
Click to expand...
Click to collapse
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.
i like this.
just great!
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.
Click to expand...
Click to collapse
kirschdog1 said:
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
Could you please try this file?
Edit: see new link in second post!
Put it in system/etc/init.d
Permissions to rw-r--r-- (644)
Reboot
Navigate to dev/stune/schedtune.boost and see if the value gets changed to the one your script should set.
It seems like the the scripts did not like the laptop at my Patents home
Click to expand...
Click to collapse
kirschdog1 said:
XtraArrow said:
On elemental kernel. I tried running from both SD card and su.d directory mate. Upon trying to change permissions it says it cannot be changed.[/QUOTE
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
make sure there are two lines
for some reason there must be a space below the text. this worked for me.
Click to expand...
Click to collapse
kirschdog1 said:
Also unable to get this working says error some file system do not allow permission changes. ....? Using Root Browser.
Click to expand...
Click to collapse
Try it with one of these and copy them to system/etc/init.d please. Permission 644 for the script and reboot.
https://drive.google.com/folderview?id=0BxbxiBXaZVu-d3NOQlFqd3QzMVU
Hello all
I updated the second post. The scripts should work now please report back! Also regarding smoothness.
sorry for any inconvenience.
Have a nice day.
Freak07 said:
kirschdog1 said:
Could you please try this file?
Edit: see new link in second post!
Put it in system/etc/init.d
Permissions to rw-r--r-- (644)
Reboot
Navigate to dev/stune/schedtune.boost and see if the value gets changed to the one your script should set.
It seems like the the scripts did not like the laptop at my Patents home
Click to expand...
Click to collapse
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse
Freak07 said:
Hello all
I updated the second post. The scripts should work now please report back! Also regarding smoothness.
sorry for any inconvenience.
Have a nice day.
Click to expand...
Click to collapse
Same issue unable to change permissions
airmaxx23 said:
Freak07 said:
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse
I have the same structure i found su.d in root but not the other.
Also how would i go about determining if it has taken effect?
Click to expand...
Click to collapse
Jerreth said:
I have the same structure i found su.d in root but not the other.
Also how would i go about determining if it has taken effect?
Click to expand...
Click to collapse
The value in dev/stune/schedtune.boost and /dev/stune/foreground/schedtune.boost should be changed to the value of the script you picked. You can probably change them manually without the script.
airmaxx23 said:
Freak07 said:
In system/etc I do not have an init.d folder, just init.
I'm using Elemental X kernel.
Click to expand...
Click to collapse
Did you Flash Elemental X kernel Prior or after rooting your device. I am not entirely sure but elex should have init.d Support.
can you install the app universal init.d from playstore, open it, scroll down and do the test to determine if init.d is supported or not?
airmaxx23 said:
The value in dev/stune/schedtune.boost and /dev/stune/foreground/schedtune.boost should be changed to the value of the script you picked. You can probably change them manually without the script.
Click to expand...
Click to collapse
yes that is correct. you can Change the values manually but they will not survive a reboot. that is why i made the scripts.
Click to expand...
Click to collapse
kirschdog1 said:
Same issue unable to change permissions
Click to expand...
Click to collapse
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.
Freak07 said:
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.
Click to expand...
Click to collapse
I can change them manually but upon rebooting they reset to 0.
Freak07 said:
are you able to Change the files manually? either via root Explorer or terminal?
for terminal do:
su
echo x > /dev/stune/schedtune.boost
x is a value between 0 and 100 ( try between 1 and 10 to be on the safe side battery wise.)
afterwards check if the value got changed correctly.
Click to expand...
Click to collapse
How do I check?
XtraArrow said:
I can change them manually but upon rebooting they reset to 0.
Click to expand...
Click to collapse
Okay. I was in a hurry. I told you all to set the permissions to 644. You have to set them to 755 (rwxr-xr-x).
kirschdog1 said:
How do I check?
Click to expand...
Click to collapse
check with a root Explorer. it is the easiest way.
or via terminal
cat /dev/stune/schedtune.boost
But first set the permissions of the script to to 755 (rwxr-xr-x). I was in a hurry and did not think correctly
then reboot and wait a Minute.
I edited the instructions in the op and all should be working now. It will not matter if you put it in system/etc/init.d or in system/su.d.
I somehow mixed the permissions with somethings else up. yeah, 755 and all will be well. stupid me.
have a nice evening.

How To Fix CPU Core1 Always Offline

I have seen so many people facing this problem. Since they used a rom that's build with dev_harsh1998 source code (before 13April). Then, i made this Thread about how the way to fix (trick) it.
Step :
1. Go to /sys/devices/system/cpu/cpu0 , and you will find file named 'online'
2. Open it and see if there listed as 0 (mean offline) change to 1 (mean online), save. Set permission file 'online' to r-r-r (read only).
* You have to do this in every reboot
Or
You can Flash this :
Set CPU0 AlwaysOn.zip
https://drive.google.com/file/d/0B6DpzXcsAckTYzduYUY0dnNnT0k/view?usp=drivesdk tested with twrp 3.1.0
* Make sure your system rom run Init.d in every reboot or turn-on "Emulate Init.d" through KernelAdiutor.
* Some Suggest if you still in Old Builds with min_freq 800mhz.
You can add 533333:75 , in KA/CPU/CPU Gov Tunables/target_loads. Between 1 and 800000.
Then, change the min_freq to 533mhz.
## For the latest Build Rom and you still facing this freq bug. Try change to 400mhz first and look to the core. Someone told it will make the first core online again. Then, after u do it. You can freely change the freq whatever u want.
### Latest build after 20170422 doesn't have this bug. Dev already solved it.
Hit Thanks if I help you
Not a good solution if we have to do the same thing after each reboot.
Actually there are two things here we need to fix .
1. CPU0 offline issue .
2. Frequency automatically goes up . I mean when we set max frequency to 800mhz , it automatically jumps to 1200mhz.
Harsh!t already provided a simple solution. We need to flash stock lollipop first to get latest firmware & modem . Then flash other rom. It will fix these issues.
I have not tried it yet , but I am going to download stock rom because I am facing these issues in official mokee rom.
@shivdroid, you should GIVE THIS A TRY too. This has the updated firmware files.
sasukay said:
@shivdroid, you should GIVE THIS A TRY too. This has the updated firmware files.
Click to expand...
Click to collapse
Thanks for these files . I will try it in free time . I will report back after flashing.
But a little bit confusion here . Since I don't want to go back to KitKat which file should I use ?
Do you know which flashable zip contains firmware/radio of stock lollipop rom ?
shivdroid said:
Thanks for these files . I will try it in free time . I will report back after flashing.
But a little bit confusion here . Since I don't want to go back to KitKat which file should I use ?
Do you know which flashable zip contains firmware/radio of stock lollipop rom ?
Click to expand...
Click to collapse
Yeah, the KK2L one. Actually, its me who has prepared those zips.
shivdroid said:
Not a good solution if we have to do the same thing after each reboot.
Actually there are two things here we need to fix .
1. CPU0 offline issue .
2. Frequency automatically goes up . I mean when we set max frequency to 800mhz , it automatically jumps to 1200mhz.
Harsh!t already provided a simple solution. We need to flash stock lollipop first to get latest firmware & modem . Then flash other rom. It will fix these issues.
I have not tried it yet , but I am going to download stock rom because I am facing these issues in official mokee rom.
Click to expand...
Click to collapse
I've already tried it. Still didnt work. Just to let u know. Everytime before i flash a rom, i will flash a firmware.zip (by @sasukay) lollipop first. Then, the rom. It has no fix. Im also flashed firmware.zip given by hasrhit, but still no luck. So, those trick is the last option to fixed it.
Flash it, then tell here. It fixed the cpu bugs or not. So, people will know.
sasukay said:
Yeah, the KK2L one. Actually, its me who has prepared those zips.
Click to expand...
Click to collapse
Yeah, thanks bro. I've used it always before flash a rom. It's helpes me down/upgraded base firmware ? Since im A6000+ user. If i A6000 user, i better choosen firmware from rahulsnair
GuestStar said:
I've already tried it. Still didnt work. Just to let u know. Everytime before i flash a rom, i will flash a firmware.zip (by @sasukay) lollipop first. Then, the rom. It has no fix. Im also flashed firmware.zip given by hasrhit, but still no luck. So, those trick is the last option to fixed it.
Flash it, then tell here. It fixed the cpu bugs or not. So, people will know.
Click to expand...
Click to collapse
Then a script would be better which execute on every boot set the value automatically.
I flashed mokee build today....
Full wipe
Flashed Kk2L.zip
Then Rom & other things.
But the frequency and core 0 offline issue is still there .
Now Going to try the full lollipop zip ...
Deleted
sasukay said:
@GuestStar, @shivdroid - I wrote the init.d script to automate the process of setting CPU0 online. Can you please test this for me. Its a flashable zip.
Click to expand...
Click to collapse
??
shivdroid said:
?
Click to expand...
Click to collapse
Working on it.
Still couldn't understand why it isn't working.
the 01cpuon init.d scipt
Code:
#!/system/bin/sh
#Sets CPU0 online
echo "1" > /sys/devices/system/cpu/cpu0/online
#Sets permission to r--r--r--
chmod 0444 /sys/devices/system/cpu/cpu0/online
updater-script
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
package_extract_file("01cpuon", "/system/etc/init.d");
set_perm(0, 0, 0755, "/system/etc/init.d/01cpuon");
unmount("/system");
Can anyone help me with it.?
sasukay said:
Working on it.
Still couldn't understand why it isn't working.
the 01cpuon init.d scipt
updater-script
Can anyone help me with it.?
Click to expand...
Click to collapse
I can try to make it works
I've remake the flashable zip
Set CPU0 AlwaysOn.zip
Here :
https://drive.google.com/file/d/0B6DpzXcsAckTYzduYUY0dnNnT0k/view?usp=drivesdk already tested using twrp 3.1.0
Thanks to me and @sasukay for the Init.d script
@GuestStar, Gg bro. So, what I did wrong was I didn't mount the system correctly. Bro, but can you point out why this didn't work.
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
Actually, I'm a newbie and picked that line from some other updater-script. So, technically it should've worked.
sasukay said:
@GuestStar, Gg bro. So, what I did wrong was I didn't mount the system correctly. Bro, but can you point out why this didn't work.
Actually, I'm a newbie and picked that line from some other updater-script. So, technically it should've worked.
Click to expand...
Click to collapse
Yeah, you forgot to mount system.
Wht do you mean dint work?
GuestStar said:
Yeah, you forgot to mount system.
Wht do you mean dint work?
Click to expand...
Click to collapse
Code:
mount("ext4", "EMMC", "/dev/block/bootdevice/by-name/system", "/system", "");
This didn't work for me. I tried to mount system with this command but the twrp recovery still showed error 6.
sasukay said:
This didn't work for me. I tried to mount system with this command but the twrp recovery still showed error 6.
Click to expand...
Click to collapse
Those command is right as well. If still didnt work. Then, the problem could be from the update-binary files
Have u looked into my zip i made.. To mount system i better used busybox/sbin. For update-binary i get from harsh flashable zip (the zip is about copying modules). I've tried to use that, and its works
GuestStar said:
Those command is right as well. If still didnt work. Then, the problem could be from the update-binary files
Have u looked into my zip i made.. To mount system i better used busybox/sbin. For update-binary i get from harsh flashable zip (the zip is about copying modules). I've tried to use that, and its works
Click to expand...
Click to collapse
Well thanks for the info. There were two things that I saw in your zip that weren't reqd. 1) online file was not reqd. 2) setting its permission to 644 was not reqd
Anyways, it is working. That will be enough for us.
sasukay said:
Well thanks for the info. There were two things that I saw in your zip that weren't reqd. 1) online file was not reqd. 2) setting its permission to 644 was not reqd
Anyways, it is working. That will be enough for us.
Click to expand...
Click to collapse
Yeah, i know it ? forget to remove. At the first time, i just want to make sure file online listed as '1'

Categories

Resources