Update: I got ICS SuperCharged! See Post 92!
And hey, rank the thread n click thanks n stuff
So I had indeed been working on V8 SuperCharger and when V6 got really hot, I kept pretty busy making it better and better.
Of course, this leads to a much better V8 than would have been possible.
At the time, it was very much Milestone specific in that I made an overclocking feature that makes a file just like 10overclock as below.
Code:
#!/system/bin/sh
echo "5 1100000000 66" > /proc/overclock/mpu_opps
echo "4 800000000 45" > /proc/overclock/mpu_opps
echo "3 600000000 35" > /proc/overclock/mpu_opps
echo "2 400000000 27" > /proc/overclock/mpu_opps
echo "1 200000000 22" > /proc/overclock/mpu_opps
The new file will be /system/etc/init.d/99sc-overclock
10overclock is untouched.
The 99sc-overclock settings will stick because it will run after 10overclock.
UnOverclocker simply deletes 99sc-overclock
Big thanks to skadude66 for helping me with testing out the Overclockerthingie!
This V8 Alpha also has an early implementation of 3g TurboCharger and user selectable colours.
I have these older screen caps that I'm using since I had lost my Milestone...
This is what it looks like....
Code:
\\\\ V 8 S U P E R C H A R G E R - M E N U ////
==============================================
1. SuperCharger & Launcher Status"
2. Aggressive 1 Settings {6,8,24,30,40,50 mb}
3. Aggressive 2 Settings {6,8,25,30,35,35 mb}
4. Balanced 1 Settings {6,8,24,26,28,30 mb}
5. Balanced 2 Settings {6,8,26,27,28,28 mb}
6. Balanced 3 Settings {6,8,26,28,30,32 mb}
7. MultiTasking Settings {6,8,22,24,26,26 mb}
8. Gaming Settings {6,20,40,70,80,90 mb}
9. MegaMemory Device {6,12,75,125,150,175 mb}
10. Cust-OOMized Settings {See Slot 3 Tips!}
11. OOM Grouping Fixes + Die-Hard Launcher
12. OOM Grouping Fixes + BulletProof Launcher
13. UnDo Kernel/Memory Tweaks
14. UnSuperCharger
15. 3G TurboCharger + Hardware Acceleration
16. Overclocker {99sc-overclock SuperCedes OC}
17. UnOverclocker {Removes 99sc-overclock}
18. REBOOT! (WARNING - There is NO Warning!)
19. Exit
WARNING: This is only for goofing around with!
The overlocker and unoverclocker are the ONLY useful features as the current V6 SuperCharger has different OOM groupings and the current 3G TurboCharger, which was just released, has 5 different configurations to choose from
If you do apply SuperCharging with this early V8 version, UNSUPERCHARGE V6 BEFORE supercharging with this V8.
Other ROMS on other phones, I don't know what would happen if you tried the Overclocker
Lastly, if you can donate, please do since it will help make further updates and a more polished V8 much quicker
Installation Instructions are the same as found in the monster V6 SuperCharger thread
Wow!
I loved the V6 and i'm using it right now!
I'm downloading this V8 and ill post a feedback.
Thanks for this great work man!
Good work Zeppelin! I got caught up in all of the V6 supercharger and haven't been keeping up with the latest betas! I'm keen on trying this out
If you lost your Milestone, what phone are you using right now? :O
A crappy samsung thingie... updates from over a month ago till now are done "in my head"
Engine Flush, Nitro Lag Nullifier, the new 3G TurboCharger, KAK... I haven't seen them running with my own eyes as of yet LOL
Of course, V8 Alpha was done before that... I think this was done in May/July...
Oh and I forgot to thank you in the OP for assisting with the OCing at the time
zeppelinrox said:
A crappy samsung thingie... updates from over a month ago till now are done "in my head"
Engine Flush, Nitro Lag Nullifier, the new 3G TurboCharger, KAK... I haven't seen them running with my own eyes as of yet LOL
Of course, V8 Alpha was done before that... I think this was done in May/July...
Oh and I forgot to thank you in the OP for assisting with the OCing at the time
Click to expand...
Click to collapse
Hehe, no worries about the OC, just a simple idea to implement!
At this point, it's pointless to get a new Milestone, the new GSII is supposed to release sometime soon on Telus
Sent from my Milestone using XDA Premium App
Keyboard?
I wonder if droid3/milestone3 will make it's way here
zeppelinrox said:
Keyboard?
I wonder if droid3/milestone3 will make it's way here
Click to expand...
Click to collapse
No keyboard, but it's rumored to have a 4.5" screen. The Droid 3/Milestone 3 is on Bell, so if you can buy it no term, you can just enter in the APN for Telus afterwards I guess!
Sent from my Milestone using XDA Premium App
V8 is working nicely!
Thx man!
Im using Gamming Mode
skadude66 said:
No keyboard, but it's rumored to have a 4.5" screen. The Droid 3/Milestone 3 is on Bell, so if you can buy it no term, you can just enter in the APN for Telus afterwards I guess!
Click to expand...
Click to collapse
When the time comes, I will definitely look into it
afonsolage said:
V8 is working nicely!
Thx man!
Im using Gamming Mode
Click to expand...
Click to collapse
Cool indeed
zeppelinrox said:
When the time comes, I will definitely look into it
Cool indeed
Click to expand...
Click to collapse
Some more info on the Samsung GS2 for Telus codenamed "Hercules" :http://mobilesyrup.com/2011/08/17/telus-samsung-galaxy-s-ii-hercules-surfaces-again/
I'm going to try out V8 Alpha tonight and let you know how it goes
Nice work zepp, I'll do some testing on my Evo 4G and post an update with my results! Glad to see you progressing! V8? What's next, V12?!
Thanks for testing guys...
It's pretty much the same as V6 update 1 if I remember correctly except for the added colours, 3g and overclocking.
Oh maybe you can test this command out...
Code:
busybox | head -1 | awk '{print $1" "$2}'
Going by this page it should spit out the busybox version that you're using
Also...
Code:
id | awk '{print $1}'
If you could post the exact output... that would be great
zeppelinrox said:
Thanks for testing guys...
It's pretty much the same as V6 update 1 if I remember correctly except for the added colours, 3g and overclocking.
Oh maybe you can test this command out...
Code:
busybox | head -1 | awk '{print $1" "$2}'
Going by this page it should spit out the busybox version that you're using
Click to expand...
Click to collapse
I'm getting an error saying that it is an unknown option. The switch for -1 should work with head, but it isn't working. When you type only busybox, head is one of the options, I think there might be something missing in the call for head.
Also, I don't know 100% if appending the " " in the awk will work. I'm pretty sure the , will interpret the fields with spaces, and that is not needed.
EDIT: Just invoking "Busybox" in an instance of Terminal Emulator will spit out a sort of help page, with the first line having the Busybox version number on it.
yeah going by that page...
busybox | head -1 by itself should work... and it doesn't?
Howabout....
busybox --help | head -1 | awk '{print $1" "$2}'
zeppelinrox said:
yeah going by that page...
busybox | head -1 by itself should work... and it doesn't?
Howabout....
busybox --help | head -1 | awk '{print $1" "$2}'
Click to expand...
Click to collapse
busybox | head -1 gives an unknown option error.
busybox --help is the same as just running busybox in Term Emulator.
I tried running id | awk '{print $1}' and it gave me "awk: applet not found".
EDIT: Running busybox --help | head -1 |awk '{print $1 " " $2}' gives me the applet not found error for awk and head.
can you possibly have an incomplete busybox or something?
How can it not find awk
zeppelinrox said:
can you possibly have an incomplete busybox or something?
How can it not find awk
Click to expand...
Click to collapse
I have no idea
I just ran the Busybox Installer, installed 1.18.5 and then I ran the commands, even after doing a su and it gave me the same applet error.
ah... try 1.18.2 or lower.... LOL
You lost your Milestone? Where did you ever find it?
zeppelinrox said:
ah... try 1.18.2 or lower.... LOL
Click to expand...
Click to collapse
BINGO! I installed Busybox v1.17.1 and doing
Code:
busybox | head -1
Spat out
Code:
BusyBox v1.17.1 (2010-08-12 23:44:34 CDT) multi-call binary.
EDIT: Everything is working fine right now.
Code:
busybox | head -1 | awk '{print $1" "$2}'
Working.
Code:
busybox | head -1 | awk '{print $1,$2}'
Same output as with " " in the awk call.
Related
HTC released gingerbread via OTA but they did not support additional modules. This thread has flashable zips for both the leaked kernel and the one from the "OTA".
Added flashable modules to attachments that are flashable in recovery.
I have created a zip of some of the more useful modules for our device:
Code:
cpufreq_conservative.ko
cpufreq_smartass.ko (thanks Chad for the help here)
ext4.ko
jbd2.ko (necessary for me to load ext4)
tun.ko
perflock_disable.ko (I actually compiled this one a little different but confirmed it would load and not get the exec format error)
Update: Smartass is working now with assistance from chad in resolving those errors. Decided to not worry about interactive for now.
Further information:
If you don't use the CWM flashable zip you will need to load perflock_disable a special way as it needs to be called with a special parameter to make it work correctly. Try adding below to a script. Credit to Calkulin for the script.
Code:
if [ -e /system/lib/modules/perflock_disable.ko ]; then
insmod /system/lib/modules/perflock_disable.ko
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
addr=`awk '$3 == "perflock_notifier_call" { print "0x"$1; }' /proc/kallsyms`
if [ -n "$addr" ]; then
insmod /system/lib/modules/perflock_disable.ko "perflock_notifier_call_addr=$addr"
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
echo "ERROR!!! Perflock could NOT be DISABLED"
fi
fi
fi
fi
Credits:
Conap (for BootManager and helping me test ext4 on an SD ROM)
XDA (for teaching me so much about Android)
HTC (for the kernel source)
Chad0989 (for assistance in getting smartass CPU governor working)
Coolbho3000 (perflock_disable)
Calkulin for the module load script
anyone else who inspired me (apologize if I forgot)
I have attached a zip file to this. If you are not a dev you can still use the modules here but some basic ADB/terminal knowledge would be needed. The modules are open for testing though.
Attached zip files and CWM-flashable zip files for both OTA and leak-based ROMs.
inc_modules.zip - Just the loadable modules.
inc_modules_ota.zip - just the loadable modules - OTA-based ROMS (August leak)
inc_modules_ota_091811.zip - just the loadable modules - OTA-based ROMS (actual OTA from September)
inc_modules_CWM_flashable.zip - flashable zip that will also autoload modules at boot.
inc_modules_ota_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (August leak)
inc_modules_ota_091811_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (Actual OTA from September)
I'm glad some one took this up I had been wondering the same thing since HTC opened the dev section. I had found another site that had a more extensive write up on how to build kernels but I'm not very fluent in linux and was a little intimidated at trying. At least I now know that it can be done. Maybe we can get Chad to try and port it over?
Awesome. A ray of hope.
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
jermaine151 said:
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
Click to expand...
Click to collapse
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
tiny4579 said:
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
Click to expand...
Click to collapse
--prefix
Sent from my ADR6300 using XDA App
hightech316 said:
--prefix
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually got them to build but they won't load still. I will play around with it more.
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
oh wow this is incredible great job tiny!!! and the reason you probably cant get those other governors to work is because htc released an uncomplete source
jskolm said:
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
Click to expand...
Click to collapse
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
tiny4579 said:
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
Click to expand...
Click to collapse
would i need to make one for every module?
JoelZ9614 said:
would i need to make one for every module?
Click to expand...
Click to collapse
Joel,
No, just one script should work. I believe Synergy ROM already has the init.d script for some of them. See 00cpufreq_modules in /system/etc/init.d
All,
Updated OP with latest zip file. If you have downloaded previously, redownload to get the latest.
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
JoelZ9614 said:
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
Click to expand...
Click to collapse
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
tiny4579 said:
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
Click to expand...
Click to collapse
eeh im not good with init.d scripts lol
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Every shell script should contain
#!/system/bin/sh
Sent from my ADR6300 using XDA App
JoelZ9614 said:
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Click to expand...
Click to collapse
Exactly!
Then just make a line for each module.
EDIT: Though you could just write it like this:
Code:
#!/system/bin/sh
insmod /system/lib/modules/tun.ko
Though to be safe and to make sure you are running that particular insmod command you can leave it the way you have it.
ok done its in my rom RLS3 Thanks Tiny Great work
JoelZ9614 said:
ok done its in my rom RLS3 Thanks Tiny Great work
Click to expand...
Click to collapse
No prob! It's been a good project for me.
**** Do Not Repost! Link back to this thread! ****
*** Update: This works on Thrill/Optimus 3D. There are seperate kernel modules for Froyo/GingerBread/CyanogenMod kernels***
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
This uses SYMSEARCH by Skrilax_CZ
https://github.com/SkrilaxCZ
Inspired by Milestone Overclock by Tiago Sousa, but totally rewritten for omap kernel 2.6.35-7 and above.
http://code.google.com/p/milestone-overclock/
This is a stripped down version. I'm working on a fully featured version, that will allow you to play with voltage as well. There are some hurdles to overcome before that is ready for prime time... In the mean time, lets see what stock voltage can do... 1188 is my sweet spot on stock voltage, what is yours? I get up to 1235 without reboots, or real noticeable lags but the linkpacks are all over the place, where it stays in the 80's at 1188. And remember, the number is in hz a.k.a. cycles per second, so to get Mhz, you must add 'Six Zeroes' to the end of your desired Mhz.
* Note2Devs: Feel free to put this in your ROM, but please do credit me for the Overclock in your release, and link back to this thread. You can also post a link to your ROM here as a way to make myself and other aware of it. Thanks...
* Echts shows us how he integrate's the module into his own ROM. TY, Echts...
http://forum.xda-developers.com/showpost.php?p=19542521&postcount=52
* Thanks to greenbats for helping figure out the O3D gingerbread kernel issue!
** And don't ask to put it in an app. I won't be happy about that. I'm serious! **
Here go some of my Recording Engineer work...
http://www.youtube.com/watch?v=Je8K_hCej3s
http://www.youtube.com/watch?v=yfBfcdSL1pc
http://www.youtube.com/watch?v=iIU8DO4rdKI
http://www.youtube.com/watch?v=msavF7LIdvY
Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.
It's the same hardware
omgomg said:
Essentially, hardware wise, the Thrill has exactly the same specs as the Optimus 3D ? I mean, CPU wise.
Click to expand...
Click to collapse
Yes, give this a go on the O3D, the module is actually compiled against the cyanogenmod cosmo kernel, which is really for the O3D. Should work.
for test \
How do I install this on the optimus 3D?
greenbat said:
How do I install this on the optimus 3D?
Click to expand...
Click to collapse
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.
tekahuna said:
No real installing... It's just the modules... You can throw them in /system/lib/modules, and then use an init script to load them up, then set the frequency, but don't do that until you know what works *STABLE* for you.
If you have a favorite ROM, let the dev know about this, and maybe they'll integrate it.
I'm not sure if custom kernels like acurateam's might be too different to work properly at this point. But it won't hurt to try. Just don't start loading it at boot right away.
Click to expand...
Click to collapse
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.
greenbat said:
Thanx for your advice and Great find!!!
I have send your xda link to acura. Hopefully he can integrate it.
Click to expand...
Click to collapse
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah
Great invention
tekahuna said:
I didn't find this. I made it! First OC'd OMAP4 period! Unless you count RAZR's... hah
Click to expand...
Click to collapse
Great invention and congratulations!
Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App
tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse
Type this in scriptmanager shell.
greenbat said:
tekahuna said:
**** Do Not Repost! Link back to this thread! ****
Here ya go... I prefer this method rather than hard coding changes in the kernel. Assuming you have both kernel modules extracted to /sdcard
Switch to root
Code:
$ su
Copy files from sdcard to /system/lib/modules directory - You only do this once
Code:
# cp /sdcard/symsearch.ko /system/lib/modules/symsearch.ko
# cp /sdcard/opperator.ko /system/lib/modules/opperator.ko
Load modules, always do symsearch.ko first - You do this every time you reboot
Code:
# insmod /system/lib/modules/symsearch.ko
# insmod /system/lib/modules/opperator.ko
Set Frequency - You do this when you want to change frequency - in hz, that's 6 additions Zero's to make Mhz
Code:
# echo 1188000000 > /proc/opperator
Is it possible for you to change this into a scriptmanager file?
Click to expand...
Click to collapse
What I'd really like is for the ROM making dev's to come to a consensus as to how to integrate this... Mainly, the best place to throw the script that does this at boot on these phones. I know how we did it on droid X, but I haven't dug deep enough into this phone just yet to be sure... I'll update the OP as methods improve and I get more feedback.
Click to expand...
Click to collapse
Or use callmearia kernel and make script for system/etc/init folder... havent tried his kernel but it should support the script at boot up. Acura roms should work that way too.
The way most roms use overclock is the init script that starts at boot...
Sent from my LG-P925 using XDA App
rdannar said:
Great job.... we use to use this type of script in motorola defy and moto bravo. It was easier with those because of the 2nd init recovery booting.
Sent from my LG-P925 using XDA App
Click to expand...
Click to collapse
Those would have been based on Milestone Overclock... Which is where I gained most of my knowledge by contributing to getting the droidx/2 side of things working. MO's method of manipulating frequency and voltage no longer works on OMAP4, or rather kernel 2.6.35+... I had to come up with a new way of doing things, which didn't fit well under the existing framework of MO. So, I started from scratch... This is just the tip of the iceberg... Basic, basic, basic...
i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?
I also get the same error: insmod: init_module '/system/lib/modules/symsearch.ko' failed (exec format error)
Is it because I have gingerbread?
Must I use froyo?
borelis said:
i get insmod: init_module /system/lib/modules/symsearch.ko failed (exec format error).
What am i doing wrong?
Click to expand...
Click to collapse
Both O3D's, huh? What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source
tekahuna said:
What kernel are you running? give me output of
# dmesg
and
# busybox uname -a
And if it's acurateam, a link to their kernel source
Click to expand...
Click to collapse
"LINK Boot_2.0 More RAM, No Lags, More Speed.." from acura. Think he uses stock kernel. Im on GB by the way.
Outputs is a bit over my head. Tell me how and i´ll provide it for you.
I know that a lot of people are asking how to make voodoo settings stick. I found the following to work even on roms without init.d. I suppose this means Rom Toolbox could be used to run all your scripts
For those that do not know how to write scripts this is easy.
This works on roms without init.d as well.
Download ROM Toolbox from market. Open scripter. Create new script. Copy and paste the following:
#! /sys/bin/sh
echo 2309122400 >/sys/class/misc/voodoo_color/red_multiplier
echo 2309122400 >/sys/class/misc/voodoo_color/green_multiplier
echo 2701672960 >/sys/class/misc/voodoo_color/blue_multiplier
echo -44 >/sys/class/misc/voodoo_color/blue_v1_offset
echo -50 >/sys/class/misc/voodoo_color/red_v1_offset
echo -53 >/sys/class/misc/voodoo_color/green_v1_offset
These settings are from samoled. You can change the numbers to your preference. Save the script. You can then run the script and set to run at boot all from ROM Toolbox.
damnmisur said:
I know that a lot of people are asking how to make voodoo settings stick. I found the following to work even on roms without init.d. I suppose this means Rom Toolbox could be used to run all your scripts
For those that do not know how to write scripts this is easy.
This works on roms without init.d as well.
Download ROM Toolbox from market. Open scripter. Create new script. Copy and paste the following:
#! /sys/bin/sh
echo 2309122400 >/sys/class/misc/voodoo_color/red_multiplier
echo 2309122400 >/sys/class/misc/voodoo_color/green_multiplier
echo 2701672960 >/sys/class/misc/voodoo_color/blue_multiplier
echo -44 >/sys/class/misc/voodoo_color/blue_v1_offset
echo -50 >/sys/class/misc/voodoo_color/red_v1_offset
echo -53 >/sys/class/misc/voodoo_color/green_v1_offset
These settings are from samoled. You can change the numbers to your preference. Save the script. You can then run the script and set to run at boot all from ROM Toolbox.
Click to expand...
Click to collapse
Sweet! Do you know if there's a way to make the sound settings stick as well? (bass booster)
derekwilkinson said:
Sweet! Do you know if there's a way to make the sound settings stick as well? (bass booster)
Click to expand...
Click to collapse
I can post more script for that in a bit.
edit: damn if I can't find the files for the bass boost settings.
Sent from the bowels of hell
Those are my exact settings preference, thanks
Sent from my Nexus S
Doesn't the voodoo control app work?
Voodoo settings aren't sticking with ics based roms.
Sent from the bowels of hell
Does this work on stock cm7.101? (stock cm7.1 kernel)
This works on all roms I believe. The files are in the system folder which are common between roms. Correct me if i'm wrong.
Sent from the bowels of hell
Erm.... What the heck are Voodoo colors?
Voodoo control plus on the market if you don't know about it you better find out
sent from my Nexus NScollab
evoschecter said:
Erm.... What the heck are Voodoo colors?
Click to expand...
Click to collapse
Voodoo colors offer an adjustment to rooted phones. Its like the color adjustment on a t.v.
Sent from my Nexus S using xda premium
Damnmisur, can you create a script to automatically change the "Background Process Limit" to at most 3 processes?
Seems like this is another one of those things that don't stick upon restarting. Many people like to set their limits instead of letting apps stay in memory.
Thanks!
Enhanced said:
Damnmisur, can you create a script to automatically change the "Background Process Limit" to at most 3 processes?
Seems like this is another one of those things that don't stick upon restarting. Many people like to set their limits instead of letting apps stay in memory.
Thanks!
Click to expand...
Click to collapse
Didn't realize that didn't stock either lol thanks for the heads up
Sent from my Nexus S 4G using Tapatalk
Enhanced said:
Damnmisur, can you create a script to automatically change the "Background Process Limit" to at most 3 processes?
Seems like this is another one of those things that don't stick upon restarting. Many people like to set their limits instead of letting apps stay in memory.
Thanks!
Click to expand...
Click to collapse
Wish I could. I'm a noob and figured out the voodoo colors script by looking at system files. I don't really know how to make the script for what you are asking for.
Sent from the bowels of hell
damnmisur said:
Wish I could. I'm a noob and figured out the voodoo colors script by looking at system files. I don't really know how to make the script for what you are asking for.
Sent from the bowels of hell
Click to expand...
Click to collapse
Just need to figure out where those values are stored at just like the voodoo ones
Sent from my Nexus S 4G using Tapatalk
Someone figure it out!
sweet!! gonna try this out. now i can stop using franco.Kernel 11/25 lol
Hoping a dev stumbles on this thread for an answer to process limits. This will be most likely solved when Nexus S ICS code is released.
Sent from the bowels of hell
Omg you're a god! And the options you chose actually look really nice! My screen looks juicy and bright instead of neon!
damnmisur said:
I know that a lot of people are asking how to make voodoo settings stick. I found the following to work even on roms without init.d. I suppose this means Rom Toolbox could be used to run all your scripts
For those that do not know how to write scripts this is easy.
This works on roms without init.d as well.
Download ROM Toolbox from market. Open scripter. Create new script. Copy and paste the following:
#! /sys/bin/sh
echo 2309122400 >/sys/class/misc/voodoo_color/red_multiplier
echo 2309122400 >/sys/class/misc/voodoo_color/green_multiplier
echo 2701672960 >/sys/class/misc/voodoo_color/blue_multiplier
echo -44 >/sys/class/misc/voodoo_color/blue_v1_offset
echo -50 >/sys/class/misc/voodoo_color/red_v1_offset
echo -53 >/sys/class/misc/voodoo_color/green_v1_offset
These settings are from samoled. You can change the numbers to your preference. Save the script. You can then run the script and set to run at boot all from ROM Toolbox.
Click to expand...
Click to collapse
Awesome now I don't need to manually do it
Sent from my Nexus S using xda premium
This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 4.x
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
-Call Forwarding
I'm constantly updating only this main thread and I will answer only in it, I have no time to update and control every thread in sub-forums.
I'm using this thread only for major notifications.
Mentor.37 said:
This is a patch to fully enable GSM on every rom and on every Android version.
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
The patch and the guide are available here.
If you want you can download a specific patch for the CyanogenMod 10.1.2 here.
Click to expand...
Click to collapse
it's worked on XT894 with Hashcode's CM10.1.2, i have tried it
such a nice work :good:
Does this enable the US GSM bands as well?
No, I'm sorry but it can't enable US GSM.
Awesome, added this to my GSM guide. Thank you.
Lum_UK said:
Awesome, added this to my GSM guide. Thank you.
Click to expand...
Click to collapse
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Mentor.37 said:
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Click to expand...
Click to collapse
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Lum_UK said:
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Click to expand...
Click to collapse
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Mentor.37 said:
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Click to expand...
Click to collapse
Can I use LTE (gsm networks sim) in my country with this patch (Be, Europe) ?
You have to se what are lte frequencies in Belgium.
The lte on xt894 only works at 700 mhz.
Maybe next time you should give credits to the original author... *cough cough*
Are you talking with me?
I'm the original author.
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
But they differ in a few lines, I think that tobby disabled the LTE. Anyway for nightlies is better to replace only the lines needed.
The world is full of people there is a chance that two of them to work on the same thing.
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Regards
Sent from my XT894 using xda app-developers app
lucize said:
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
Click to expand...
Click to collapse
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
lucize said:
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Click to expand...
Click to collapse
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
With copy, I was telling the way that you implemented the patch, and regarding to apn it was only a comment because in other cm releases(not motorola), the apn list is full (~180kb vs 17kb).
I personally downloaded the tobby zip first, but I use this device only recently (previous was d3) so who was the original poster I can't say.
Regards
Sent from my XT894 using xda app-developers app
I do not understand why you think I would have copied the way to implement the patch, patches are all made in the same way.
Personally I use my stock rom but several users who use AOSP roms have contacted me exposing the gsm problem and so I easily fixed with this patch using the settings that I use in my rom file build.prop.
At short will release a new version of my rom with a new build.prop file with new settings and I'll update this patch also.
I honestly did not know existed nor Tobby nor his zip, I created this patch because asked me.
Regarding the file APNs-conf.xml depends on the fact that the phone is born to the CDMA network Verizon and therefore not serving the other APNs, the file APNs-conf.xml in the stock rom is ~ 43KB.
What is the Tobby's zip?
Mentor.37 said:
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
Click to expand...
Click to collapse
Ah c'mon. Take a look into your own files. In apns-conf.xml is still my copyright... Its not extracted from Motorola Stock-ROM. Also not from CM. It's based on several sources on the internet (most of it is based on CM, but several more sources were added). It took days to combine the sources, remove duplicates, sort it, use the same style for every entry and so on. It's not a problem to use or copy this. But to say you did this yourself is not fair.
But apns-conf.xml is only one part of your mod. Second part is the automatic build.prop changer. (GSMbyMentor.sh)
Look at your GSMbyMentor.sh:
Code:
#!/sbin/sh
#
# Patch to enable GSM on Verizon by Mentor
# Build: 17.07.2013 17:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=GB/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.modem.mode =1/persist.ril.modem.mode =2/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.vzw.cdma.mdn=/persist.radio.vzw.cdma.mdn=deleted/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc = 1/ro.telephony.gsm-routes-us-smsc = 0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.ap.phonetype=2/persist.radio.ap.phonetype=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
Now let's take a look at the Bash-Script of "TobbysMod":
Code:
#!/sbin/sh
#
# Tobbys build.prop Anpassungen für das Droid 4
# Stand: 15.03.2013 04:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.language=en/ro.product.locale.language=de/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=DE/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.ecclist=911\,\*911\,\#911/persist.ril.ecclist=911\,\*911\,\#911\,119\,118\,999\,08\,000\,112\,110/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc=1/ro.telephony.gsm-routes-us-smsc=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.hwKeyboard.capsLockNoAlt=true/ro.hwKeyboard.capsLockNoAlt=false/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.lte.mm.disable=0/persist.radio.lte.mm.disable=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.lte_on_cdma=1/ro.mot.lte_on_cdma=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dateformat=MM-dd-yyyy/ro.com.android.dateformat=dd.mm.yyyy/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dataroaming=true/ro.com.android.dataroaming=false/g" /system/build.prop > /system/build.prop
Let's take a look at the differences.
- You removed my credit and changed the date
- you removed a few lines which were necessary for the keyboard-mod included in the original mod and necessary for European date-format and emergency calls
The rest stayed the same. Even the sequence/order. And you use exact the same trick for removing spaces. You can't say this was coincidence...
Third part of your mod is the edison install script. This looks different. Seems to be your own work.
Two of three parts in your mod copied from me. It's ok! I always wanted to remove the parts which are necessary for my German friends so everybody can use it, but I didn't have enough time. So it is good someone (you) did that. But please don't say it's your own work when you just copy files...
Link to original Thread for "TobbysMod": http://www.android-hilfe.de/motorol...82-tobbys-automatische-rom-modifizierung.html
Google translation: http://translate.google.de/translat...82-tobbys-automatische-rom-modifizierung.html
I added that apns-conf.xml at the suggestion of an user that tested my patch, I repeat that I'm on stock rom so I have not tested directly the patch. If you wont I can give you his email address.
In a first moment I made this patch as you can see here with the apns-conf.xml that I personally extracted and that I use in my rom for months without any problem. Anyway I removed that file.
About the sed is a common command for any linux user to manipulate text.
About the sequence/order it is different, I used the same in the build.prop.
About the point of the gsm patch, so the build.prop settings there are a lot of differences:
My:
Code:
telephony.lteOnCdmaDevice=0
persist.ril.modem.mode=2
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
persist.radio.vzw.cdma.mdn=deleted
ro.telephony.gsm-routes-us-smsc=0
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
Yours:
Code:
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
ro.mot.phonemode.vzw4gphone=0
persist.radio.lte.mm.disable=1
ro.mot.lte_on_cdma=0
These lines are missing in your:
Code:
persist.ril.modem.mode=2
persist.radio.vzw.cdma.mdn=deleted
persist.radio.ap.phonetype=1
and the lines that are equal in the two files have known each other forever and they are everywhere in the forums so what are you saying?
With the settings in my build.prop users solved their problem on aosp roms.
#Postedit
I found this and this with your patch and then this and this with my patch.
apns-conf.xml: As I said: You don't need to remove the file. It's ok I created this file to help users. Additionally because of the sources, I am not allowed to forbid the usage of this file for some users. You also don't NEED to give credits, because it's already included. I just wanted to mention you are not using your own file. Not more ore less.
Bash-Script: Yes, sed is a common linux command. But it's usage on the phone was a little bit different than on a normal linux machine and the trick with the spaces (sed -i "s/\ =/=/g") is not necessary for the function of this script. It's just to make some things a little bit easier. That's why it's hard to believe you found out the exact same thing as me and used it in exactly the same way. If you did: Grats mate! You must be a soulmate of me If you just used this because you saw it "somewhere" else: please don't remove my credit.
To the missing 3 lines: two of them are included in version 1.3 of 07/16/2013, one day before you created yours. Just "persist.radio.vzw.cdma.mdn=deleted" is not included in my Mod. I am just curious: What does this line do?
But we schouldn't argue about it. As I said: Feel free to use my work. I hope I am allowed to do the same with your work. Instead of argueing we should combine our work!
I reinserted the apns-conf.xml that I use in my rom.
I used the sed command intuitively how I use it.
The line "persist.radio.vzw.cdma.mdn=deleted" deactive the mdn on cdma network. I use these settings from time.
You can use my work without problem.
I just answered your allegations because I spent a lot of my free time for this my mod.
About a possible collaboration I like this idea, the work is much, time is short and one hand is always a pleasure.
Introduction:
Hello everyone!
This script is created with the goal of improving both battery life and performance on our Xperia 1 / Xperia 5 devices, and should be seen as a simple, and customized, under-the-hood kernel configuration with a lot of neat, and carefully selected, adjustments for a notable better device experience.
Note: This script is not recommended to be modified or customized by the user.
The latest release can be found here.
Features:
Reduced battery consumption
Device specific enhancements for best possible balance between battery life & performance
Disabled a lot of useless stuff at kernel level (Improves battery life as well as performance)
Power efficiency enhancements
Wide IO block tuning (Reduces the possibility of hiccups, lags and overhead)
Possibly other miscellaneous things I've forgotten to write down here, both big and small.
Requirements / what you need for getting this script fully working:
An unlocked bootloader
Your own specific choice of kernel
Latest supported version of Magisk
Busybox for Android NDK Magisk Module by @osm0sis
Patience
Installation / How-To use & abuse:
1) Download the attached ZIP
2) Extract the script(s)
3) Move the script to the following location;
/data/adb/service.d and give it the following & needed file permissions (0775)
4) Reboot your phone, let Android boot to the launcher and let Magisk boot service do its crucial magic (takes a few seconds before the scripts is fully up and running around behind the scenes)
5) Enjoy!
Telegram:
If you want to try out betas / previews of my script before they are officially released, or just hangout and chat a little, then join the official Telegram group here
Disclaimer:
This is presented as "what if". If this modification screws up or breaks anything for you, I am not the one to be held responsible. It's a free will to try out this kind of changes/modifications/addons/tweaks, just don't blame the inventors for eventual bad results and/or screw-ups.
Credits:
@pkgnex for inspiring me walking into this partially unknown territory.
@flar2 for his excellent EXKM application
@osm0sis for his Magisk Busybox module
Everyone that I've forgotten to mention here
To-Do list:
Optimize and properly tune things even further for best possible balance between battery life, system responsivness and performance
Contributors:
@xFirefly93
Created: 2019-09-12
Last updated: 2020-01-23
Update!
Note: This kernel profile / script requires the Busybox for Android NDK Magisk module for fully working as intended.
Version v1.0 (Initial release):
- Initial release for both Xperia 1 as well as Xperia 5
- Adjusted a lot of things both here and there for better performance and lower than lowest amount of overhead
- Added the recommended Schedutil governor values that the Pixel devices have been using since the stone age
- Enabled the schedtune.prefer_idle flag for foreground and top-app (improves overall throughput and responsivness)
- Properly adjusted the default cpu_input_boost driver for keeping the device smooth while maximizing battery life
- Shifted to RCU_NORMAL for overall improved power efficiency, real-time latency and CPU processing utilization
- Enabled a few ULPS kernel hooks that reduces the power consumption that is being "wasted" by the display panel
- Disabled a lot of useless kernel debugging and logging
- A few additional minor tweaks both here as well as there
If you optionally want to donate a beer or five as a way to show your appreciation for all the dedicated hours and work that I am putting into this mod on a daily rate - then this link is the way to go:
https://paypal.me/pools/c/8aGYOw1k6h
Enjoy!
mod
I've down everything but nothing happens at boot and service file still in services d
Shsl said:
I've down everything but nothing happens at boot and service file still in services d
Click to expand...
Click to collapse
Have you set the file permissions to 0755? Isn't any folder named 'logs' generated at your internal storage?
d
I have seen the log it says done
Shsl said:
I have seen the log it says done
Click to expand...
Click to collapse
Then everything should be just fine!
any kernels
What kernels are available
Shsl said:
What kernels are available
Click to expand...
Click to collapse
Only stock for now. I am though debating for myself if I should get everything sorted out with a Linux distro and start working on a unified kernel for Xperia 1 and Xperia 5 or not..
Code:
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t auto /;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /proc;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t [B]data /[/B];
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t auto /sys;
For the 3rd line do you mean
Code:
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t [B]auto /data[/B];
instead?
neekless said:
Code:
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t auto /;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime -t auto /proc;
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t [B]data /[/B];
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t auto /sys;
For the 3rd line do you mean
Code:
busybox mount -o remount,nosuid,nodev,noatime,nodiratime,noblock_validity,noauto_da_alloc,barrier=0 -t [B]auto /data[/B];
instead?
Click to expand...
Click to collapse
Oh crap, I made a typo.
Sorry for that, I'll fix it asap! Thanks for the notification / head-up.
slow
This mod made my mobile slow most apps take time opening sometimes it's like got sluggish
slow
After reboot it fixes ???
Shsl said:
After reboot it fixes ???
Click to expand...
Click to collapse
Reboot and see if it fixes it
I'll push a update with a lot of personal performance biased customizations once my new home network arrives in the middle of this month, if my broadband provider now doesn't fail to deliver it in time.
My Xperia 1 is currently fully nuked and not in use because of a semi-softbrick and downloading the FTF-firmwares through 4G on a limited data plan isn't really my cup of cake so..
Stay tuned and hold on just a few more days!
:highfive:
slow
Nice I had sometimes poor performance on mobile whilst using normal apps but when I reboot it fixes any ideas why it happens to me
Shsl said:
Nice I had sometimes poor performance on mobile whilst using normal apps but when I reboot it fixes any ideas why it happens to me
Click to expand...
Click to collapse
It happens because I made things far too conservative without any real major nor deeper testing.
I'm working slowly on fixing it step by step at the moment.
@xFirefly93I see some users reporting slowness on the device .... good if you want I can help improve your mod.
Marília de Oliveira said:
@xFirefly93I see some users reporting slowness on the device .... good if you want I can help improve your mod.
Click to expand...
Click to collapse
If you want to? What device are you using, Xperia 1 or 5?
xFirefly93 said:
If you want to? What device are you using, Xperia 1 or 5?
Click to expand...
Click to collapse
I have Xperia XZ but I see some lines of your mod that could be improved.
Marília de Oliveira said:
I have Xperia XZ but I see some lines of your mod that could be improved.
Click to expand...
Click to collapse
Send me a PM / DM instead!