Related
Hi all,
since knzo have decided to stop developing Nova v7 despite certain little bugs, I've decided to create my own post to share with you a package to solve all the solvable bugs until the date.
In this first version, the flashable package contain/solves:
- SmartassV2 governor Issue (with modified nova script).
- Updates Superuser 3.0 from Beta3 to Beta4 and /system/bin/su permissions set to 7777.
- Autoset I/O Scheduler on boot (with modified 11nov init.d script).
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1.zip
(MD5: 004bedbdd3cec21779af2538d32f75c4)
Problems with Superuser? Try some of the following packages. First mantain 3.0 Beta3 and second contains the latest stable version. Both with su permissions set to 7777.
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1-beta3.zip
(MD5: 3e93990b79bf8c2d70001c4d3f72babf)
http://dl.dropbox.com/u/4629711/nova opt/huexxx-nova7-twk-v1-stable.zip
(MD5: 4373fb38d9f8fac857ed77b046285ffe)
Instructions: Put it onto sdcard root and flash it whrough CWM.
I tried the package and working ok but I am not responsible for any damage that may result in your devices.
So many thanks to Antonio1475 and knzo, good work dudes! ... and thanks to all who have helped into Nova project!
I hope this thread will please everyone involved.
Regards!
Meh, even though I know the bugs are there and I can fix them, I just said it wasn't worth a new version.
For now at least. If more appear, I can release another one.
I'm tired.
You could rename it to v7.1 patch by the way, I'm fine with it. It's more of a bug-fixer than optimizer!
P.S. It's the I/O sched autoboot feature that was fixed, not governor.
which i/o is best? what are the differences between them?
thank you, all is going well so far
No need to new versions IMHO. The work is done.
Relax and rest for 2.3 arrive...
Feel free to take it, rename it and post onto nova's thread, it's in your hands.
Optimizer is not the word i guess too... i'll rename it.
I hope to release new versions with true opts or enhanced existent features.
Regards.
Sent from my LG-P970 using XDA App
IMHO InteractiveX is the best, but i don't mind lower performance but better battery last.
There are explanations inside nova's thread. Use the search...
Sent from my LG-P970 using XDA App
Huexxx, he was talking about I/O Scheduler, not governor.
Sent from my LG-P970 using xda premium
do i have to wipe all data? and install this?
memeru said:
do i have to wipe all data? and install this?
Click to expand...
Click to collapse
no men
just flash it
whats the different between the two
memeru said:
whats the different between the two
Click to expand...
Click to collapse
read 1st post plz
Sobralobo said:
Huexxx, he was talking about I/O Scheduler, not governor.
Sent from my LG-P970 using xda premium
Click to expand...
Click to collapse
Ops... I'm not used to tapatalk!!!
v(r) seems to be the best overall but with ups and downs in performance while sio is more consistent performance.
Try them for yourself... if you don't see the difference... both are good for you.
From what I've read on the main Nova ROM thread, on v7 for Froyo, WiFi meter readings do not correspond to true signal strength. This is due to the more important tweaks knzo did.
Just a thought, if those tweaks weren't in older versions (such as v4.5, which is imho, already a fast version, but WiFi signal readings are true), is it possible to modify Nova v7 (meaning, ditch the tweak or tweaks that make signal readings erratic) so that WiFi readings are true without ruining the performance?
It's possible... when I know which tweak has generated it and where is it...
After applying this patch has increased the power consumption of the system (in Тутор the System process and the Kernel). In a Terminal at one and the same Governor SmartassV2. Returned to made a backup.
PaulBort said:
After applying this patch has increased the power consumption of the system (in Тутор the System process and the Kernel). In a Terminal at one and the same Governor SmartassV2. Returned to made a backup.
Click to expand...
Click to collapse
Aha,
then:
- modify a caracter at nova in order to operate well with SmartassV2 (the same if you had applied the smartass patch, and you had already applied it because you are using it before according to your probes)
- modify a caracter at 11nov in order to set iosched on autoboot (if the same iosched is set, its the same)
- change superuser beta3 to beta4 (in your case you already have beta4 because freezing with beta3)
makes a difference in power compsumption at your OB...
You have different power comsumptions at different moments, I'm sure it isn't by the patch itself... because you had all implemeted yet!
Huexxx said:
Aha,
- change superuser beta3 to beta4 (in your case you already have beta4 because freezing with beta3)
Click to expand...
Click to collapse
Yes, I do patch SU yesterday, today - do your patch, but freezing (black screen when the application is started) sometimes present.
PaulBort said:
Yes, I do patch SU yesterday, today - do your patch, but freezing (black screen when the application is started) sometimes present.
Click to expand...
Click to collapse
Certainly the included versión (Beta4) is not the same as knzo's version (the date soesn't match) so i've created an alternative package for all who have problems with su.
Regards.
ajcantonio said:
From what I've read on the main Nova ROM thread, on v7 for Froyo, WiFi meter readings do not correspond to true signal strength. This is due to the more important tweaks knzo did.
Just a thought, if those tweaks weren't in older versions (such as v4.5, which is imho, already a fast version, but WiFi signal readings are true), is it possible to modify Nova v7 (meaning, ditch the tweak or tweaks that make signal readings erratic) so that WiFi readings are true without ruining the performance?
Click to expand...
Click to collapse
Hi there, I've already tried that method, modifying Nova v4.5 with kernel v7. first time try, I don't get overclock, still the same 1 GHz, and the WiFi signal still the same. But I notice that actually it work (even on Nova v7), the signal update in minutes. I've test it, if the phone connected to AP, wait for a minutes, and the signal will full. Then, go a little far away from AP, then the signal updates to low signal also in a minutes.. Well I don't know what's the problem.
Second try, I include overclock_p970_22.ko from Nova v7 (which I don't include it at first try), but it hang/freeze after come to "desktop". Well, it mean that v4.5 and v7 are not compatible
So I release battery, start it again, and go to recovery mod, and apply Nova v4 and v4.5 to have normally system. And when I came back to this forum, I see post that contain fix for Nova v7. Well, I have to try it
Thanks Huexxx, will trying it... Here we go with another night flashing and flashing again
Huexxx said:
IMHO InteractiveX is the best, but i don't mind lower performance but better battery last.
Click to expand...
Click to collapse
Well the same as i was.. I use InteractiveX that I think had more battery..
First post modified again...
The su fix from knzo only repush the program and set different permissions.
I've created three posibilities: beta4, beta3 ans latest stable.
I'll look into wifi problem.
Regards!
No wifi problem here.
And superuser works fine
Sent from my LG-P970 using xda premium
Disclaimer :
I am not responsible if you brick, break, blow up, drop, lose, or get your device pregnant. Everything you do is your responsibility.
This kernel is only made for the GT-P6810 WiFi only Tablet, It is not compatible with Locerra CM9 nor CM10, and it may not work on everyone's device. I'm not a real developer and I don't know how to fix your device if you break it!
This kernel is forked (a direct copy to be more specific) from the EzyICS Kernel v1 and I thank again Ezynow for his hard work. I took his changes from his topic and adapt this kernel to the P6810. Actually, I took the .config and compare line by line which was for the P6800 and which was for the P6810. So, I disabled all the gsm/modem devices.
This kernel is not perfect and needs be to improved so don't be harsh if there's some kind of problem. I've tested it again tonight and I did not brick or whatsoever other problem... I'll list on the features which one are working and tested and others which don't.
There's only one file to download and flash it with the locerra's cwm. So, you have to install locerra's cmw first ! See below
Bugs
None known yet
Features
Removed MMC_CAP_ERASE (BrickBug) (tested ok) like Dedrak's one I did this :
Code:
//mmc->caps |= MMC_CAP_SDIO_IRQ | MMC_CAP_ERASE;
mmc->caps |= MMC_CAP_SDIO_IRQ; // Brick Bug Fix
Built from GT-P6810_ICS_Opensource_Update1.zip;
Support for bootanimation. Place the bootanimation.zip in /system/media folder.
Various compiler optimizations (neon, cflags :-O2 -fomit-frame-pointer etc.) (Debug stuff remains for now but will be taken after some more mods are added);
Mali state tracking disabled;
/etc/init.d/S* script support (Add here your tweaks / ramscripts from custom roms etc.) (tested ok)
Added Governor :
Pegasusq (by default) - (recommend as it deals better with multi-cpu devices like our tabs but may require some tweaking)(tested ok)
interactive;
lulzactive;
lulzactiveq;
smartassV2;
hotplug.
I don't know if these governors will suit to our tab and they need to be tested.
Overclocking Support up to : 1600 mhz. It test further but the tab was not stable enough and as Ezynow said : ICS changes how frequency control is implemented so not as easily overclockable as honeycomb was. Fixed CPU Boot Up frequencies to default values / not overclocked settings (tested ok)
Undervolting Support:
Same frequencies as Eznow used : 200 / 500 / 16000 hz (As these are the most used)
So far running pretty stable on:
Code:
1600 mhz -------------------> 1300mv
1400 mhz -------------------> 1250mv
1200 mhz -------------------> 1175mv
1000 mhz -------------------> 1075mv
800 mhz ---------------------> 1000mv
500 mhz ---------------------> 875mv
200 mhz ---------------------> 875mv
ALL DEVICES will have different values but these values gave by Ezynow worked for me. Use SetCpu to change voltages or cpu overclocks. (tested ok)
Slightly undervolted GPU voltages and thus reduced by 50mv for default GPU levels. (tested ok)
in built CIFS support. Changed Max_BUFFER Size to max 130084 (Thanks to Pinkowl for first supporting this).
In cifs options put: rsize=130048. (tested ok)
NFS share mounting. (not tested)
UDF & ISO support - i.e native bluray disk support. (not tested)
Here is information on it This is configurable using a tool known as NSTools on the PlayStore. When using this 100% means the bus frequency is at 100% try not to get confused. So 100% of 100MHz would be 100MHz so if you increase it to 120% so it would be 120% of 100MHz would be 120MHz and this value applies to all CPU frequencies, GPU ect.
Compatibility listIt seems to work on all stock ICS releases or derived custom ROMs.
CM9 - Not working;
CM10 - Not working;
XXLPL - Tested: (tested ok)
InstallGo into CWM.
Make a nandroid backup.
Install zip from sdcard.
ProblemsGo into CWM-> Advanced restore -> restore boot.
Changelog:v1.1
Default cpu scaling governor set to pegasusq (siyahkernel version).
Enabled bootanimation;
pegasusq cpu scalling governor added (siyahkernel version : more stable);
interactive cpu scalling governor added;
lulzactive cpu scalling governor added;
lulzactiveq cpu scalling governor added;
smartassV2 cpu scalling governor added;
hotplug cpu scalling governor added.
v1
First release (see features)
DownloadsP6810 wifi only
Stock Kernel XXLPM : Download
v1: Download (2012-08-23)
v1.1: Download (2012-09-24)
Special Thanks
Ezynow (of course)
Chainfire for his work
Locerra to be the first on the 7.7
UpInTheAir (who was very supportive)
Dedrak to be the first user of my tutorial
gokhanmoral for his governor's tweaks
And others on this forum
If you want to add features or just want to ask questions feel free to do it
Oh nooo I on P6800..
If I on P6810...will whack this on my Tab
Nice...keep it up mengpo, any chance for P6800?
I have a suggestion for the Pegasusq governor. You could perhaps tweak it according to siyah kernel like on the sgs2?
Astrix Ashburn said:
Oh nooo I on P6800..
If I on P6810...will whack this on my Tab
Nice...keep it up mengpo, any chance for P6800?
Click to expand...
Click to collapse
The P6800 is available for a while now see this thread and have a good flash : http://forum.xda-developers.com/showthread.php?t=1807193
lambstone said:
I have a suggestion for the Pegasusq governor. You could perhaps tweak it according to siyah kernel like on the sgs2?
Click to expand...
Click to collapse
Ok I'll seek into this Have you got any link where I can read some stuff ?
Thanks
mengpo said:
The P6800 is available for a while now see this thread and have a good flash : http://forum.xda-developers.com/showthread.php?t=1807193
Click to expand...
Click to collapse
Yup..I been using it since it release till now
Thinking you can put up more tweak..etc? I will flash it
mengpo said:
Ok I'll seek into this Have you got any link where I can read some stuff ?
Thanks
Click to expand...
Click to collapse
I really can't remember if there was any link describing the pegasusq governor when it was first introduced but however, the link below is for the sources. not really sure if it will be of any use to you though. perhaps some features could be implemented over?
https://github.com/gokhanmoral/siyahkernel3
there are also some information about the ICS kernel for sgs2
http://forum.xda-developers.com/showthread.php?t=1572937
lambstone said:
I really can't remember if there was any link describing the pegasusq governor when it was first introduced but however, the link below is for the sources. not really sure if it will be of any use to you though. perhaps some features could be implemented over?
https://github.com/gokhanmoral/siyahkernel3
there are also some information about the ICS kernel for sgs2
http://forum.xda-developers.com/showthread.php?t=1572937
Click to expand...
Click to collapse
Thanks for the links I'll try to tweak a bit more this kernel to do the same the SGS2
Hi Mate,
Great to see the development you've made! Excellent work :good:
Still away right now and hopefully missus will have sorted out a place to stay (and ADSL) by the time I return.
Need to (want) to get started on a new ROM build for P6810 (P6810XXLPM), but that won't happen for 2 weeks.
Would love to take your kernel for a run then
Keep it up
I have many self-reboots with this kernel... What can I do?
diamond_lover said:
I have many self-reboots with this kernel... What can I do?
Click to expand...
Click to collapse
Simple. Don't use it. This is just the first version created by Mengpo and is bound to have issues here and there. I'll wait for him to post an update (whenever that happens) before evaluating and trying it.
diamond_lover said:
I have many self-reboots with this kernel... What can I do?
Click to expand...
Click to collapse
Are there just random or when you use a specific app ?
lambstone said:
Simple. Don't use it. This is just the first version created by Mengpo and is bound to have issues here and there. I'll wait for him to post an update (whenever that happens) before evaluating and trying it.
Click to expand...
Click to collapse
I got some issue with my internet connexion and got some problem with my computer too... The update could take a while... Well I'll see with dedraks if I could use some help
wrong post.
mengpo said:
Are there just random or when you use a specific app ?
I got some issue with my internet connexion and got some problem with my computer too... The update could take a while... Well I'll see with dedraks if I could use some help
Click to expand...
Click to collapse
Just installed stock -> CWM -> kernel, then I boot up, then I have random reboots (and the speakers make a little sound like click click click..)
diamond_lover said:
Just installed stock -> CWM -> kernel, then I boot up, then I have random reboots (and the speakers make a little sound like click click click..)
Click to expand...
Click to collapse
Did you undervolt or overclock the tab with that kernel ? (using setcpu or else)
mengpo said:
Did you undervolt or overclock the tab with that kernel ? (using setcpu or else)
Click to expand...
Click to collapse
nope, just fresh installed... that's weird..
diamond_lover said:
nope, just fresh installed... that's weird..
Click to expand...
Click to collapse
Hummm yup that's weird... I'm looking into it
diamond_lover said:
nope, just fresh installed... that's weird..
Click to expand...
Click to collapse
I did an update and changed the scalling governor (pegasusq with pagasusq (siyah version). I think the problem went from there and thus you won't have this random reboot issue.
good luck !
The v1.1 download link seems bad; says file is deleted.
Also anyone use this on Skyfire Rom, which seems based on the same stock firmware?
mengpo said:
I did an update and changed the scalling governor (pegasusq with pagasusq (siyah version). I think the problem went from there and thus you won't have this random reboot issue.
good luck !
Click to expand...
Click to collapse
Nice, I'll try, but I can't download, could you check the link?
Thanks in advance.
diamond_lover said:
Nice, I'll try, but I can't download, could you check the link?
Thanks in advance.
Click to expand...
Click to collapse
I don't know what happened... I've updated the link
*** THIS KERNEL ONLY SUPPORTS SAMSUNG TW JB 4.1.2 ROMs (STOCK and CUSTOM). DOES NOT WORK IN CM or AOSP!!! ***
*** The Kernel is Safe (MMC_CAP_ERASE disabled) and the included PhilZ Recovery uses delete recursive and avoids brickbug, but please be aware that, i take NO reponsibility if something happens kernel related! ***
*** This kernel has GPU OC to 400MHz that can make phone hot while playing GPU intensive games and wear out your device faster. So, I take no responsibility if the provided KERNEL causes any problem to your phone, so you are warned again! ***
Long story short, there are only a few DEVs currently developing a TW based kernel. Although they are awesome, sometimes having more options is good. So here you have my own compiled kernel a.k.a. c.o.h.'s HelloWorld kernel.
I named it "HelloWorld" because it is my first compiled kernel and am still learning although i have previous programming experience.
FEATURES:
* It is safe kernel based on latest official Samsung JB Sources.
* 3 steps GPU control, (no lag in games now!).
* 200 -1400 MHz CPU. If you want UV, use a CPU Adjuster program like "cpu adjuster"(recommended as it shows current GPU state), "cpu master", "voltage control" etc.
* Samsung original initramfs with modded recovery that combines PhilZ v4.93.6 touch recovery (with bootloop fix!), root and busybox thanks to Phil3759, and Samsung.
* More scheduler and governor options.
* Defaults noop and ondemand, however i recommend using noop-pegasusq combination (anyway you try and find the most suitable for you)
CHANGELOG:
Current:
Changelog v1.3.7 --> v1.3.7b:
Reverted GPU thresholds to v.1.2.28 (still 134, 267 and 400MHz) as it was not battery friendly, rest is the same as v1.3.7.
It could be my last build, let's see if i can continue later...
Changelog v1.2.28 --> v1.3.7:
Used Linaro GCC 4.7.3 (Even faster now!)
Optimized GPU thresholds (Can really go to 400MHz in load now)
Enabled SWAP and ZRAM support (need to be configured manually, so just for experts)
Possible fix for MIUI TW based MIUI ROMs (all should work without problem now, not tested!)
v1.1.15 --> v1.2.28
Create from scratch, no more based on Hydracore. Less (maybe no) bugs.
Samsung video player no more force closes, it is fixed.
Added CPU Hotplug support from Speedmod kernel (only 1 core when not in load as it's in Speedmod kernel, bettery battery life)
Disabled logcat and dmesg and unnecessary Samsung debugging (from Speedmod kenel) See 2nd post on how to enable logcat.
Added UV capability (Please use with caution as it is very risky to change the CPU voltages).
Increased Touchscreen sensitivity even when charging (Best touch response to date in Note ).
Added FSYNC Control 1 (from Ezekeel's GLaDOS kernel for Nexus). See 2nd post to see how to disable FSYNC (not recommended nor explained for noobs).
Tweak GPU, it is now : 100-114, 267, 400 MHz (3 steps, first step dynamic)
Added HYPER cpu governor.
Defaults are noop-ondemand now (noop-pegasusq is still recommended for balance)
Fix for wifi drain on standby (disabled all multicast).
Use GCC 4.6 for optimum performance.
Some minor changes...
v1.1.15:
Initial release with fixed modules and initramfs.
GPU steps set to : 133, 267 and 300MHz.
Speedmod K5-3 fixes included.
Hydracore sched and gov options.
Siyah Kernel GPU optimizations.
Includes PhilZ v4.93.6 touch recovery (with bootloop fix!) and root with busybox.
TODO List:
Will only support v1.2. onwards... (1600 MHz not supported natively, You can use Tegrak Overclock for 1600MHz)
Fix for Blackclipping using AndreiLux mdnie suggestions (almost impossible, but i will do my best. Needs a lot of time, don't ask for ETA)
Support exFAT and NTFS (seems trickier than i thought to make it native, so maybe)
Tweak min. brightness. (it can be adjusted from build.prop, so no need to do it from kernel)
Increase touch sensitivity even when charging -DONE
Add HYPER governor -DONE
Add multi core aware hotplug support -DONE
Change default scheduler to noop -DONE
Add U/V -DONE
FSYNC control -DONE
Experimental MIUI TW support (Only for Touch Wiz based MIUI versions!) -DONE
Swap support. -DONE
Tweak third GPU step threshold. -DONE
That's all for now.
INSTALLATION:
1. Flash the attached kernel CWM flashable zip using any SAFE custom recovery like PhilZ kernels, or Speedmod kernels, or Hydracore kernels.
2. Wipe cache and dalvik cache and reboot.
3. Enjoy. (it takes around 2-3 reboots to the ROM and KERNEL to settle down and get really fast and smooth.
CREDITS;
Samsung, for the source code (although it could be much better),
Maxfu, for keeping Hydracore development and providing his source code and allowing me to fork it,
Hardcore, for his legendary Speedmood kernel and sources,
Gokhan Moral, for his Siyah Kernel sources helped me to fix GPU bugs and optimize it further,
Neobuddy89 for some of his scheduler tweaks in NXKernel,
Phil3759 for his legendary PhilZ Touch Recovery.
For Developers/Modders: You can use the HelloWorld kernel in your CUSTOM ROMs as long as you give links to this thread.
Source code including the initramfs: Attached below.
!!!The attached source code (source_HelloWorld_v1.2.8.tar.gz) is for DEVELOPERS only.!!!
Please hit THANKS button if you think that it is helpful for you. If not enough, you can even buy me a beer from the link in my signature
TWEAKS:
From Ezekeel's GLaDOS:
[FSync Control]
Enable/disable single file/filesystem sync.
/sys/class/misc/fsynccontrol/fsync_enabled
enable = 1, disable = 0 (default enabled)
Disabling single file/filesystem sync increases the risk of a data loss on a crash/freeze and potentially can lead to other side-effects.
From Hardcore's Speedmod:
Here is how to change some of the kernel configurations:
[HOW TO ENABLE LOGCAT]
If you are a developer or want to re-enable logcat for whatever reason, do this:
adb shell
su
mount -o remount,rw /system
echo ANDROIDLOGGER >> /system/etc/tweaks.conf
mount -o remount,ro /system
[HOW TO DISABLE AUTO-ROOT]
Create a file called ".noautoroot" in either /system or /data. This will disable the auto root installation. This example, shows how to remove root completely:
adb root
adb shell
mount -o remount,rw /system
rm /system/xbin/su
rm /system/app/Superuser.apk
rm /data/app/Superuser.apk
touch /system/.noautoroot
mount -o remount,ro /system
sync
reboot
[HOW TO RE-ENABLE AUTO-ROOT]
adb root
adb shell
mount -o remount,rw /system
rm /system/.noautoroot
mount -o remount,ro /system
sync
reboot
reserv2
downloading...and flashing......finger cross
1. Awesome works...boot ok and rom is alot smoother, all working fine
Glad to have another kernel in Hub !!
Seems this kernel will definitely make TW roms much smoother and silky smooth
Immortal Nerd said:
Seems this kernel will definitely make TW roms much smoother and silky smooth
Click to expand...
Click to collapse
That's what it did to my ROM
Super cool ..... Lolz ... Seems i gotta try your rom !!
crime_of_heart said:
That's what it did to my ROM
Click to expand...
Click to collapse
Definitely gonna try your rom as m searching for super stable rom ........ Looks to me that m not quiet satisfied these days ..... Have about 25 gbs of roms on my disk ( GB .... ICS ..... JB ) !! Going insane !! Anyways I'll try your rom
Immortal Nerd said:
Definitely gonna try your rom as m searching for super stable rom ........ Looks to me that m not quiet satisfied these days ..... Have about 25 gbs of roms on my disk ( GB .... ICS ..... JB ) !! Going insane !! Anyways I'll try your rom
Click to expand...
Click to collapse
Wait for the new version will be up tonight
Thanx 4 the info ...... I'll wait
crime_of_heart said:
Wait for the new version will be up tonight
Click to expand...
Click to collapse
I'll wait tonight and flash ur rom !! My thnx button is dead coz only have 8 thnx up to date !! Btw thnx for the info ..... Will try it as soon as u r done uploading
crime_of_heart said:
Wait for the new version will be up tonight
Click to expand...
Click to collapse
Unlimited thanks given..
Sent from my GT-N7000 using Tapatalk HD
custom voltage is in plan or not? tq
p/s: pls say yes
go go go , bring more light into the world !! hello coh !!!
arinsms said:
custom voltage is in plan or not? tq
p/s: pls say yes
Click to expand...
Click to collapse
i will not sey NO, but not soon. Maybe in 2-3 weeks, maybe...
Hi crime_of_heart,
Been starving for a new kernel for our Note.
Thanks a lot
Thanks for this kernel!!! Had a long time wit for this.
So far working great!!!
crime_of_heart said:
i will not sey NO, but not soon. Maybe in 2-3 weeks, maybe...
Click to expand...
Click to collapse
take ur time :good: as long is in plan is good enough :good::good:
Awesome..
Great mate. Downloading and flashing right away.
Tons of Tons of Thanks:good::good::good::good:
crime_of_heart said:
Wait for the new version will be up tonight
Click to expand...
Click to collapse
Pls revert back to standard configuration of the sdcard and externalsd.
Sent from my GT-I9100 using xda app-developers app
legola said:
Pls revert back to standard configuration of the sdcard and externalsd.
Sent from my GT-I9100 using xda app-developers app
Click to expand...
Click to collapse
The ROM uploaded already :S
But just flash the provided CWM file to revert SD change (it is in the OP) in recovery after installing the new ROM and it will be as you like it
Cheers mate. Thanks for this. I'm going to try it now :good:
Thunderoar Kernel For SM-T113
(Tab 3 Lite 7.0 Wifi)
* Your warranty is now void.
* I am not responsible for bricked devices, dead SD cards, corrupted partition, nuclear disasters
* Please do some research before using this mod!
* YOU are choosing to make these modifications,
* If you point the finger at me for messing up your device, I will laugh at you.
Features:
Overclocked
Deferred Timer for KSM
USB Fast Charge
Arch Power
Frandom
Powersuspend for battery life/saving
QuickWakeup for battery life/saving
Dynamic Sync Control
Fsync control on/off
Voltage Tweak
NVS hibernate driver
Multicore Power Saving
Schedule workqueues on awake CPUs to save power
CPU Boost
Adaptive Low Memory Killer
Software CRC control toggle
Gentle Fair Sleepers toggle
and so on...
CPU Hotplug:
AutoSMP
Added CPU governors:
Sprdemand
Conservative
Ondemand
Userspace
Powersave
Interactive
Performance
and so on...
Planned Update
-nothing i guess (but u can suggest somethin to me that possible)
Bugs(s)
-No MORE BUG!
Custom kernel Installation:
Download the kernel from here
Choose the tar.md5 if flashing from odin
Choose the zip files if flashing from custom recovery
Choose the latest version
Odin Instruction:
Open any version of odin
Choose your tar.md5 file from AP Tab
And Start
Custom Recovery Instruction:
Reboot into recovery if usin zip files (recommended to make a nandroid)
Flash the kernel zip
Reboot and enjoy!
Stock kernel Installation:
Download the stock kernel from here
Enter recovery mode, choose install, choose install image,
and then go to the directory of your downloaded stock kernel
choose it and then check mark on the boot circle.
And then flash it
Notes:
20/12/2107
Kernel Update!!
Thunderoar-Kernel 5.0 Codenamed "Angel Beats!"
Fix all issues regarding MTP not working
and random reboot, is this a comeback? xD, i don't know xD
It appears that my kernel uses a lot more memory than i expected,
Possibily some problem with memory patch in the kernel source
The workaround for this problem is you have to increase your disksize
In the kernel adiutor, if it stays at 300mb, it will not enough and cause a problem
Which is stuck or complete crash of device. Recommended size is 500mb or more if
you encountered it again and set swappiness into 60
XDAevDB Information
Thunderoar Kernel, Kernel for the Samsung Galaxy Tab 3 7.0
Contributors
@Thunderoar
Credits:
@Osm0sis-For the Anykernel2
@stathis95194-For the stock kernel
Github:
Kernel source
Version Information
Status: Stable
Current Stable Version: Angel Beats! || 5.0
Stable Release Date: 2017-12-24
Created 2016-12-26
Last Updated 2017-12-24
Press the "Thanks" button if you appreciate my work or if i helped you
Changelog:
V5.0 Codenamed "Angel Beats!" (2017-12-24)
+Kernel upstream version 3.10.17->3.10.108
+Gpu update
+Fix MTP
+CPU Frequency change 200MHz upto 1.5GHz
+Entropy Update
+Multicore Power Saving
+CPU Boost
+Arch Power
+Power Suspend
+Quickwakeup
+Read-ahead set to 512kB
+Adaptive Low Memory Killer
+Software CRC control
+Gentle Fair Sleepers
+Fsync On/Off
+Built from scratch and fixed random reboot
+Dynamic Fsync
-Removed Obselete Cpu Governor
-Removed Obselete I/O Scheduler
-Removed UKSM and use normal KSM
V4.1.1 update (2017-7-5)
+Fix some devices not booting
+New CPU Hotplug: AutoSMP
V4.1 update (2017-7-3)
+Just another update for stability
V4.0 update (2017-7-3)
+No more Reboot or similar effect - Tested
+Linux kernel downgraded into 3.10.32 temporarily because rebuilt from scratch
+Auto cpu boost on input without predefined frequency
+UKSM(Ultra Kernel Samepage Merging)
+LZ4 Z-RAM - Faster Memory
+Asynchronous Fsync -Faster storage management
+USB Fast Charge are back
-Removed cpu governor: OndemandX, Zzmoove, Scary *Temporary*
V3.4 update (2017-6-22)
+The most stable kernel that i've ever built
+Linux Kernel 3.10.44
+No more frequent reboot or similar effect
+Bug fixes
V3.3 update (2017-6-17)
+Linux Kernel 3.10.40
+Properly fix the bug that mentioned on the v3.2 update and lower the risk of instability
+A bunch of cpu governor
*Hotplug
*Lionheart
*Reworked version of intelliactive
*Ondemandplus
*OndemandX
*Hyper
*Zzmoove
*Nightmare
*Wheatley
*Badass
*Scary
*All of them are properly functioning and tuned for compatibility
and if you want the hotplug features, use the hotplug governor provided
+Bug Fixes
-Adaptive cpu governor removed parmanently
V3.2 update (2017-6-8)
+Update: Linux Kernel 3.10.37
+Update: Using the latest Anykernel2 zip
+Update: Minimum frequency change into 254MHz and also voltage change for nice battery lasting
+Update: cpu-boost set to 765MHz and running for 3 seconds when touch detected
+Update: Set CFQ as default scheduler
+Fix: Bug that cause long running app either in the background or foreground to freeze/lagging/reboot etc.
+Fix: Bug that cause the device to reboot randomly
+Fix: Bug that cause the graphic being not working/properly lagging or some sort
+Fix: Bug that cause the device to reboot or freeze when standby
+Fix: Bug that causing the kernel to working improperly/lagging/rebooting/unstable after a while
+Bug fixes
V3.1 update (2017-5-7)
+CPU Frequency minimum change -> 384MHz
+Fix Frequency bug stuck at 768MHz
+Faster charging
V3.0 update (2017-5-7)
+Kernel version updated from 3.10.22 - > 3.10.26
+Using updated Anykernel zip
+Frequency: changed into 1600Mhz and minimum is 386Mhz
+GPU: function updated
+Deferred Timer working as it is
+LZ4 compression
+"Schedule workqueues on awake CPUs to save power" are back
+Remove conflict between Samsung touch booster and my CPU-Boost so you can actually set the amount you want
for boost
+Sync threshold for cpu-boost are not set
+I/O scheduler default to deadline
+Fsync are on by default
+TCP Congestion Algorithm set default to Westwood which is the fastest for network usage
+Additional TCP Congestion Algorithm are added
+Additional tweak to make the kernel faster
+Camera Fix!!!
+MTP Function (unconfirmed)
+A whole lot of bug fixes
-sprdemand governor
-Fastcharge (for now)
V2.8 update (2017-1-31)
+Frequency: changed into 1660Mhz and minimum is 580Mhz
+Cpu-boost: defined stable values
+Less OS tearing
+Fastcharge updated
+Audio functionality improved
+Voltage: change for low-power use
+Many bug fixes
+Selinux: updated
-Automatic Cpu Hotplug: removed for better stability but with little to no battery drainage but you still can deactivate the cores through Kernel Adiutor
-Sprdemand: removed
V2.6.1-MR1 update (2017-1-1)
*Note:This is maintenance release therefore some features may temporarily unavailable
Add: cpu-boost currently disabled but provided as an option
Add: voltage change
Add: frequency change from 386Mhz to 1600Mhz for more stable
FIx: serious bug that causing switching off mobile data make it freeze/crash
Fix: bug that causing the device freezing/crash throughout all my kernel update release
V2.6 (2016/12/27)
+Initial release
After flashing all apps start to crash.
Jimbus369 said:
After flashing all apps start to crash.
Click to expand...
Click to collapse
Quick note on the crashing apps.
T113XXU0APE2: Does not have this issue
T113XXU0APH5: When I use this ROM, than indeed everything goes bananas after booting up the tablet.
Before flashing the kernel I advice to disable all unnecessary services and with that I mean everything with Samsung in the name and also all of the google apps you don't use. It seems that com.google.process.gapps is causing a crash chain reaction so do disable this services as first. I'm using lucky Patcher for disabling services and for those who are unfamiliar with this my advice is to not uninstall an app but first disable it and later when you are satisfied you than may safely uninstall the unwanted app/service.
Bugs
Camera doesn't working
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Jimbus369 said:
My apps continue to crash in the latest version Also after a Dalvik wipe.
Build: T113XXU0APH5
Click to expand...
Click to collapse
All the app?
Thunderoar said:
All the app?
Click to expand...
Click to collapse
Yes, all apps.
This is extremely exciting and can't wait to try it out!
Build T113XXU0APA5
Will let you know how it goes....
Wanted to ask (not that it's a huge deal) is there init.d support in this kernel?
If so do I need to do anything special to enable it?
Going to go ahead with it anyway and see what happens!
Thunderoar said:
* If you point the finger at me for messing up your device, I will laugh at you.
Click to expand...
Click to collapse
Better start laughing, 'cause my finger's pointing directly at you! And also twitching slightly out of frustration!
....Nah, it's all good. :highfive: I screwed things up all on my own by getting flash-happy. :crying:
On the plus side: It worked GREAT! :highfive: Thanks so much for putting this together for us tiny-tab users, you did a great job.
Not only did Byron (my T113's name) run smoother and faster than I've seen yet (yay!), but suddenly Mounts2SD had no issues whatsoever. Up till now it's been a supreme struggle to get /sd-ext to mount properly, to be used properly, etc. etc. - but after flashing this kernel, on first boot boom, everything just worked. Without changing anything I'd already done.
Should have just left it the way it was, eh? But noooo, I had to go "try something else" and made a stupid mistake somewhere, and now no combination of ROM / kernel / nandroid backup (meticulously organized and annotated) is booting up. I even lost TWRP for a little bit.... As penance for my sin of wanting "more", I've gotta dig up Odin, go back to stock, and start from scratch.
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Not going to wait for an answer/s before moving ahead, but any response here will serve as documentation for myself and others in future!
(How don't we have a smiley for "pointing finger"? There's at least TWO in Unicode but I'm too lazy to go get it right now....)
PushyPhoenix said:
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
Click to expand...
Click to collapse
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
PushyPhoenix said:
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
The kernel is in the md5 file or in the zip file, named boot.img
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's awesome to know, and came to the same conclusion when stock setup started asking personal questions and wanted a wifi password. Rooting it this very moment, though if I'd waited *just* a little longer I wouldn't have to. Wow you're fast!
That boot.img file info will come in handy when I screw up on any ROM, thanks! This one is going ASAP into a safe and accessible place for "just in case"....
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Feel free to point me elsewhere to learn more about how these things work, I've followed a lot of guides but want to understand the "why" as well.
Click to expand...
Click to collapse
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
By the way, great to see development on this tablet. I am going to be testing this kernel in a personal build and see if I can squeeze as much out of it as I can get. So thank you dev.. Awesome work and greatly appreciated. : )
glockman4519 said:
I do believe that when flashing a boot.img through TWRP with the image flasher, the file needs to say boot.img I may be wrong but I had issues before when I changed the name of the file to keep track of which one it was....lol... I have since started putting the boot.img files in their own folders with the appropriate name on the folder.
Click to expand...
Click to collapse
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
Thunderoar said:
Yes, it will revert itself to its normal condition such as stock rom, stock kernel and everything
Click to expand...
Click to collapse
So I've run into a bit of a problem. Tried outFyrestone ROM and i love it, but it's based on PH5 firmware and doesn't play nice with your wonderful kernel. Which means my sd-ext is broken...
I know you're very busy (and I haven't a clue what kind of work is required), but wondered if you know when we can expect to see an update?
Thanks so much for all your hard work!
Sent from my SM-G900W8 using XDA Labs
PushyPhoenix said:
That's a great idea... Ugh, adding another folder to the folder full of folders on my computer frightens me. But if that's what it takes!
Sent from my SM-G900W8 using XDA Labs
---------- Post added at 11:28 PM ---------- Previous post was at 11:23 PM ----------
I get it, it clutters things s bit. But I am one who like an organized setup anyways so adding more folders is common for me. It may not be everyone's cup of tea so to speak.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
It works for me and above all, works for TWRP.
Click to expand...
Click to collapse
First of all, sincere thanks for replying; this advice may help others as well
glockman4519 said:
PushyPhoenix said:
Ugh, adding another folder to the folder full of folders on my computer frightens me.
Click to expand...
Click to collapse
I get it, it clutters things s bit.
Click to expand...
Click to collapse
My apologies for not being more clear on what exactly 'frightens' me about this idea. There have been times when I've backed things up this way and couldn't get into them again because of the number of characters in the path and file name - they were just too long!
Mind you, this was tens of years ago on WinXP and it never occurred to me to try finding a fix.
But on my PC and in my external SD , on my tablet, I have a folder named tab "what ever", then inside there are folders named mods, ROMs, kernels and then gaops. In the kernel folder I have sub folders for just this reason and those folders will have the kernel name on it and then inside will be the standard "boot.img"..
Click to expand...
Click to collapse
That's a fantastic system, very similar to the one I'm now using, and will add new folders as you've suggested. Hopefully reading this will benefit those who are new to this world so they don't wind up with folders full of mysterious files and untagged backups for various devices, that made perfect sense at the time. (Like the one folder for my first few devices, which now looks like gobbledygook....)
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Topic:
Lollipop ROM for T113 (Samsung Tab 3 lite "7 wifi-only)
Is there any lollipop/marsmallow/Nougat ä ROM that works in my T113 (Samsung tab 3 lite "7)? This device runs natively Android 4.4.4, but I Really need Android 5 or higher! Lollipop would do just fine.. I took a look at most popular custom roms to this device, but most were 4.x.x.. And nothing for t113! And all of those were to T221 or so, in the list they're were few supporting T110/T111, but now T113. Does those work in this T113? Isn't it just same device?
Please tell me if you have any idea of rom with Android 5 or newer that works in this T113!
It would be awesome to have Lollipop-Slimrom or Resurrection remix with Android 5/6/7..
Even Stock Lollipop would be adequate, android 4 lacks important features...
There's many roms to this device, but they are for T2XX or T110/T111... Does any of those run in t113?
I have already rooted this tablet and installed TWRP.
Thank you so much for help in advance! Any information that gets me closer to have Lollipop or newer is very very much appreciated!
Sincerely,
tatu-o aka. mlc
PushyPhoenix;[email protected] said:
SO! QUESTION FOR YOU! (OR ANYBODY REALLY....)
When I fire up Odin and restore the official stock ROM (eg from Sammobile or Samsung), does that include the stock kernel too?
If the stock kernel IS a separate file, where should I look? (Your OP for the T116 kernel includes a link for that model, but not OP in here. I'm sure I can find it on my own but right now I'm just whiny.)
Click to expand...
Click to collapse
1.Yep
2.The stock kernel is in the md5 file which is boot.img, the md5 file I mentioned is in the stock rom
I guess I double answered this question, my bad :silly:
PushyPhoenix said:
Hey, I've always wondered and maybe you can tell me:
When flashing this type of file in recovery or adb, does the filename matter? If I rename it "T113-[build]-boot.img" for example, will anything go wrong?
Click to expand...
Click to collapse
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Thunderoar said:
I guess I double answered this question, my bad :silly:
Click to expand...
Click to collapse
Hahaa, thought it sounded familiar! No problem, better to get the answer multiple times than not get an answer at all.
---------- Post added 01-29-2017 at 12:01 AM ---------- Previous post was 01-28-2017 at 11:59 PM ----------
Thunderoar said:
It varies, sometimes when flashing thing through adb or recovery with filename had a space in it, it would not detect it cuz the name is spaced and separated and it didn't recognize it as a file cuz the file extension doesn't connected to the name cuz it separated/spaced.
Click to expand...
Click to collapse
Good to know! I've had so many issues over the years, with spaces in filenames, that any renames for files like this get an underscore or dash instead of spaces. Helps in lots of other ways, too.
ENDURANCE REBORN ESSENTIALS for Z5 Series
- This MOD will modify the system parameters of your Z5 for ONLY ONE PURPOSE: to increase BATTERY LIFE
- Only battery tweaks, only useful tweaks (tons of tweaks is not the good strategy...)
- No performance tweaks (most of time, performance tweaks result in decreasing battery life...)
- Marginal loss of performance, device still smooth and reactive
- Very significant gain of battery life
- +useful guides in posts 2 & 3
This mod has been developped, tested and optimized with @HaoZeke's crDroid (LOS based) rom, but it works perfectly on stock based roms (I use Kryptonian at the moment) and probably on any other roms.
Features:
- build.prop battery tweaks (without modifying build.prop file)
- VM battery tweaks
- Innovative and effective memory management (LMK settings)
- ROW I/O Scheduler (best ratio performance/battery drain)
- I/O tweaks
- disable some useless wakelocks
- FS-TRIM partitions at every reboot
- DeadPool interactive governor profile
Requirements:
- Root
- Busybox
- init.d rom support
Installation:
- First, REMOVE all other system mods/tweaks (clear /system/etc/init.d folder, restore your original build.prop, uninstall LSPEED) from your device or it will be a mess!!
- Download the attached Z5_Endurance_Reborn_Essentials_v1.zip
- Flash it in TWRP recovery
- Enjoy
Warning:
- init.d enabler Magisk modules sometimes don't work at all depending of the Magisk version, best thing to do is using the init.d enabler of Kernel Adiutor
Note:
- Wait a little before to draw any opinions on this mod
- Feedbacks and suggestions for future versions are strongly encouraged
Changelog:
- 26 fev 2018 - v1.3 final version: Heimdall v5 governor profile replaced by DeadPool governor profile
- 8 dec 2017 - v1.2: fixed big cores tunables not applying at boot
- 24 nov 2017 - v1.1: small scripts modifications to ensure that all the tweaks are effectively applied
- 11 nov 2017 - v1: initial release
Credits:
@xperator for his amazing governor profile
@.hEiMDaLL. for his amazing governor profile
@korom42 for his governor profile script
GUIDE 1
For an even better battery life:
1. Install the app Naptime and switch on "agressive doze"
You will still receive your GCM or FCM instant notifications when screen off.
Push reception will no longer work in your email client. So select scheduled sync (every 5 mn for instance). If it still doesn't work, use aquamail, it will work.
Some apps need to be doze whitelisted to continue to work when screen off.
2. Use Sony Power Optimizer
Install it as a regular app AND systemize it with Systemizer Magisk module or Link2SD and reboot.
Launch it and select the apps you want to optimize: they will be frozen and evicted from RAM when screen off.
As an alternative to Sony Power Optimizer, you can use Greenify.
3. If for some reason, idle drain with wifi on is greater than idle drain with wifi off and data on, go in settings - wifi - wifi configuration and select standby mode for wifi: never active or only if the device is plugged. In this way, wifi will be off when screen off and on when screen on.
GUIDE 2
For an even even better battery life, the following xposed modules are useful:
- Smart Network xposed module
I use it to automatically turn off location when screen off (and when screen on, location is automatically reactivated)
- Amplify xposed module
With this module, you can block or restrain wakelocks. But beware, some wakelocks are necessary and must not be blocked or restrained.
This is the list of the wakelocks I have restrained without any issue:
NlpWakeLock: allowed every 240 seconds
NlpCollectorWakeLock: 240s
NetworkStats: 800s
*net_scheduler*: 7200s
GCoreFlp: 7200s
Wakeful StateMachine: GeofencerStateMachine: 7200s
Icing: 7200s
NfcService:mRoutingWakeLock: 7200s
res
Hello Nreuge, for amplify, I have a nice post to optimized battery life ! Can I put the post on your topic ?
parydia said:
Hello Nreuge, for amplify, I have a nice post to optimized battery life ! Can I put the post on your topic ?
Click to expand...
Click to collapse
Yes, for sure ^^
https://forum.xda-developers.com/showpost.php?p=60429417&postcount=4
gonna give a shot.... nice work here buddy!!!
---------- Post added at 12:02 PM ---------- Previous post was at 11:02 AM ----------
can i used dis profile with tha mod?
thanks buddy....
nreuge said:
GUIDE 2
For an even even better battery life, the following xposed modules are useful:
- Smart Network xposed module
I use it to automatically turn off location when screen off (and when screen on, location is automatically reactivated)
- Amplify xposed module
With this module, you can block or restrain wakelocks. But beware, some wakelocks are necessary and must not be blocked or restrained.
This is the list of the wakelocks I have restrained without any issue:
NlpWakeLock: allowed every 240 seconds
NlpCollectorWakeLock: 240s
NetworkStats: 800s
*net_scheduler*: 7200s
GCoreFlp: 7200s
Wakeful StateMachine: GeofencerStateMachine: 7200s
Icing: 7200s
NfcService:mRoutingWakeLock: 7200s
Click to expand...
Click to collapse
I'll give it a shot with stock 7.1.1, I have a question, what version of xposed do you use and do you still can pass safetynet?
crisout said:
I'll give it a shot with stock 7.1.1, I have a question, what version of xposed do you use and do you still can pass safetynet?
Click to expand...
Click to collapse
I use Xposed v88.2, not the magisk version because I don't care of safetynet...
0755 permission is right for scripts as per your zip? I thought folders have 0755 and files use 0644. Please correct me if I misunderstood.
Thanks
Offtopic: Do you use Viper ? Is it works with speaker ? If so which version it is? As I cannot get speaker working with viper as it says processing no always but works with Headphones.
GryTEcHoG said:
0755 permission is right for scripts as per your zip? I thought folders have 0755 and files use 0644. Please correct me if I misunderstood.
Thanks
Offtopic: Do you use Viper ? Is it works with speaker ? If so which version it is? As I cannot get speaker working with viper as it says processing no always but works with Headphones.
Click to expand...
Click to collapse
Hey bro
init.d scripts need to have 755 permissions.
No, I don't use v4a.
With crDroid, I was using the DIVA soundmod and the JamesDSPManager.
Now, I use Kryptonian stock based rom, for the moment I use the DIVA soundmod and the Sony stock equalizer.
Hey..
Did you use universal init.d app?
Or is there another way to enable init.d ?
Im on stock 7.1.1 rooted
SAMURAI6969 said:
Hey..
Did you use universal init.d app?
Or is there another way to enable init.d ?
Im on stock 7.1.1 rooted
Click to expand...
Click to collapse
Creta the init.f foder if it doesn't exist (in/system/etc/)
Then, use the Magisk module init.d linker.
Unfortunately i dont use magisk (i don't like it )
I enabled init.d using the app on playstore but i cant make sure if your script is running (human nature you know) ?
Looks like this mod little increase battery, thank you!
Performance of device steel on good level.
Im using Lineage OS 14.1 on Z5c
Yesterday I got about 4 hours Sot with 13% left(8am to 11pm), when I used to get about 3 hours with the same usage, great work and thanks for your time!
crisout said:
Yesterday I got about 4 hours Sot with 13% left(8am to 11pm), when I used to get about 3 hours with the same usage, great work and thanks for your time!
Click to expand...
Click to collapse
Good to know, thx!!
Update v1.1
24 nov 2017 - v1.1: small scripts modifications to ensure that all the tweaks are effectively applied
We can just flash 1.1 over 1.0, correct? Love the mod, cheers.