! ! ! THIS IS A GINGERBREAD KERNEL FOR STOCK ROMS ! ! !
Click to expand...
Click to collapse
hi all,
i present you the very last version of my streetware-kernel for gingerbread. i think everything is working correctly now, so i can spend all my time on a new project.
if something unfortunately doesn't work, please leave a comment or write a pm.
and now, have a lot of fun with the new streetware-kernel...
disclaimer:
remember that you flash your device at you own risk. i am not responsible for bricked devices, lost data, lost warranty or anything else, that may be the result of flashing or using this kernel.
Click to expand...
Click to collapse
advice:
don't foget to make a backup of your custom files like init.d-scripts, modules, bootscripts, bootanimations, bootsounds and so on. i have done my best not to touch them, but don't blame me, if they are lost.
Click to expand...
Click to collapse
warning:
i have added an older version of chainsdd's superuser because the new version available on the play store ist still buggy and currently unusable.
if you want to update anyway, you are free to do so, but i recommend you to read the comments on the play store first.
if you accidentally updated superuser and want to get rid of the new version, do the following:
menu-button
settings
applications
manage applications
superuser
uninstall updates
make sure you have unchecked 'allow automatic updating' for chainsdd's superuser until the new version is working correctly.
Click to expand...
Click to collapse
changelog 0.5.1 - 0.5.2:
clockworkmod recovery v5.0.2.8
busybox v1.19.4-cm7
installed in [/sbin]
supersu v0.95
installed in [/system/app]
streetware-tool v0.5.2
this is a command-line tool used to modify kernel-settings and many other things. type 'streetware -h' or 'streetware --help' in your preferred terminal application for more information.
Click to expand...
Click to collapse
general features:
clockworkmod touch recovery v5.0.2.8
busybox v1.19.4-cm7
installed in [/sbin]
busybox v1.20.2-stericson
installed in [/system/xbin]
supersu v0.95
installed in [/system/app]
superuser v3.0.7
not installed per default
cwmmanager v3.0
installed in [/system/app]
cifs-support
module in [/lib/modules]
j4fs-support
module in [/lib/modules]
ntfs-support
module in [/lib/modules]
'ntfs-3g' in [/sbin]
efs-backup
stored in [/mnt/sdcard/streetware/backup/efs]
insecure kernel
settings in [/default.prop]
integrated kernel-tweaks
tweaks in [/misc/streetware/tweaks]
cf-root compatible
properties in [/misc/streetware/settings/cfroot]
cpu frequencies [default]
[200] 400 600 800 1000 [1200]
governors [default]
[abyssplug] aggressive aggressive_x conservative gallimaufry gallimaufry_x hotplug interactive interactive_x lionheart min_max ondemand ondemand_x performance powersave smartass_v2 userspace
schedulers [default]
bfq cfq deadline noop [sio] vr
custom bootscript-support
copy your 'bootscript.sh' in [/system/streetware/bootscript] or [/mnt/sdcard/streetware/bootscript]. if files with the same name are placed in both folders, only the newer one will be used.
custom init.d-support
copy your init.d-scripts in [/system/streetware/init.d] or [/mnt/sdcard/streetware/init.d]. if files with the same name are placed in both folders, only the newer one will be used.
custom modules-support
copy your modules in [/system/streetware/modules] or [/mnt/sdcard/streetware/modules]. if files with the same name are placed in both folders, only the newer one will be used.
custom bootanimation-support
copy your 'bootanimation.zip' in [/system/streetware/bootstyle] or [/mnt/sdcard/streetware/bootstyle]. if files with the same name are placed in both folders, only the newer one will be used.
custom bootlogo-support
copy your 'logo.jpg' in [/system/streetware/bootstyle] or [/mnt/sdcard/streetware/bootstyle]. if files with the same name are placed in both folders, only the newer one will be used. you have to remove the famous yellow triangle or custom bootlogos won't be displayed.
custom bootsound-support
copy your 'PowerOn.wav' in [/system/streetware/bootstyle] or [/mnt/sdcard/streetware/bootstyle]. if files with the same name are placed in both folders, only the newer one will be used.
Click to expand...
Click to collapse
special features:
streetware-tool v0.5.2
this is a command-line tool used to modify kernel-settings and many other things. type 'streetware -h' or streetware --help in your preferred terminal application for more information.
Code:
~ # streetware --help
streetware: display help
usage 'streetware [OPTION]'
-a switch between supersu and superuser
-o toggle cifs-support on and off
-n toggle ntfs-support on and off
-b toggle bootscript-support on and off
-i toggle init.d-support on and off
-m toggle modules-support on and off
-t toggle integrated kernel-tweaks on and off
-f change default cpu-frequency-range
-g change default governor
-s change default scheduler
-l remove custom bootlogo
-u uninstall all changes and files made by this kernel and reboot into recovery-mode
-k backup your current kernel-settings to sdcard
-r reboot with your backup-settings from sdcard
-c check your current kernel-settings for errors and display them
-h display this help
-v display version information
advanced users should try 'streetware --display-all-options' to see a complete list with all options
report bugs at http://forum.xda-developers.com/showthread.php?t=1647393
~ #
advanced-mode
advanced user should try 'streetware --display-all-options' to see a complete list with all options.
Code:
~ # streetware --display-all-options
streetware: display all options
usage 'streetware [OPTION]'
--install-busybox
--uninstall-busybox
--toggle-busybox
--install-cwmmanager
--uninstall-cwmmanager
--toggle-cwmmanager
--install-supersu
--uninstall-supersu
--install-superuser
--uninstall-superuser
--toggle-superuser-application
--enable-all-hubs
--disable-all-hubs
--toggle-all-hubs
--enable-gamehub
--disable-gamehub
--toggle-gamehub
--enable-musichub
--disable-musichub
--toggle-musichub
--enable-readershub
--disable-readershub
--toggle-readershub
--enable-socialhub
--disable-socialhub
--toggle-socialhub
--enable-samsungapps
--disable-samsungapps
--toggle-samsungapps
--enable-cifs-support
--disable-cifs-support
--toggle-cifs-support
--enable-ntfs-support
--disable-ntfs-support
--toggle-ntfs-support
--enable-bootscript-support
--disable-bootscript-support
--toggle-bootscript-support
--enable-initd-support
--disable-initd-support
--toggle-initd-support
--enable-modules-support
--disable-modules-support
--toggle-modules-support
--activate-kernel-tweaks
--deactivate-kernel-tweaks
--toggle-kernel-tweaks
--change-cpu-frequency
--change-governor
--change-scheduler
--change-scheduler-mmcblk0
--change-scheduler-mmcblk1
--install-intro-as-bootlogo
--remove-custom-bootanimation
--remove-custom-bootlogo
--remove-custom-bootsound
--uninstall-kernel-reboot-download
--uninstall-kernel-reboot-normal
--uninstall-kernel-reboot-recovery
--uninstall-kernel-shutdown
--backup-kernel-settings
--restore-backup-settings
--check-kernel-settings
--check-backup-settings
--display-current-settings
--display-intro
--display-readme
--display-all-options
--help
--version
report bugs at http://forum.xda-developers.com/showthread.php?t=1647393
~ #
application-switch
you can switch between supersu and superuser. it's your choice!
backup-option
backup your custom kernel-settings to sdcard. reboot your device with your custom kernel-settings instead of the default settings.
bloatware-option
you can toggle gamehub, musichub, readershub, socialhub and samsungapps with all of their contents on and off.
frequency-settings
change cpu-frequency-range permanently. no need for other applications to do that!
governor-settings
change governors permanently. no need for other applications to do that!
kernel-tweaks
you can toggle the integrated kernel-tweaks on and off. just in case if you want to use your own tweaks.
scheduler-settings
change schedulers permanently. no need for other applications to do that! different schedulers for internal and external storage are also supported!
survival-mode
you will never lose root, even if you delete your su-binary. just reboot your device!
toggle-option
you can toggle things like bootscript-support, cifs-support, init.d-support, modules-support and ntfs-support on and off.
uninstall-option
uninstall all changes made by this kernel on your system-partition and reboot into download-mode or recovery-mode. just in case if you want to flash another kernel and make sure there is no trash left on your device.
Click to expand...
Click to collapse
credits goes to:
chainfire, chainsdd, hanny562, sakindia123, stericson, superatmos and all the others i forgot... :good:
Click to expand...
Click to collapse
thanks goes to:
patschi_ for testing again and again and again... :good:
vehlan for testing :good:
Click to expand...
Click to collapse
latest version:
streetware-kernel-0.5.2-final-release.tar.md5
flash with odin
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5.2-final-release.zip
flash with cwm recovery
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5.2-README
complete readme, changelog and detailed explanation
Click to expand...
Click to collapse
older versions:
streetware-kernel-0.5.1-final-release.tar.md5
flash with odin
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5.1-final-release.zip
flash with cwm recovery
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5.1-README
complete readme, changelog and detailed explanation
streetware-kernel-0.5-final-release.tar.md5
flash with odin
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5-final-release.zip
flash with cwm recovery
the first boot after flashing needs a little bit more time (~60 seconds on my device). please be patient.
streetware-kernel-0.5-README
complete readme, changelog and detailed explanation
streetware-kernel-0.4.4-final-release.tar.md5
flash with odin
streetware-kernel-0.4.4-final-release.zip
flash with cwm recovery
streetware-kernel-0.4.4-README
complete readme, changelog and detailed explanation
Click to expand...
Click to collapse
last but not least:
if you like this work, please hit the thanks-button...
Click to expand...
Click to collapse
Thank you for new Kernel testing it
Street79 said:
hi all,
the last few days i spent my time on learning how to compile a kernel, add new features to the source code and so on. the most time i spent on writing scripts, to make many things as easy as possible. and that's the result:
streetware-kernel-0.4 #final-release
i've been testing this kernel the last days and everything seems to work fine. but if something unfortunately doesn't work or if you have any suggestions, please leave a comment...
and now, have a lot of fun...
Click to expand...
Click to collapse
thanks ! i'm testing
i cant download..when i click the link..it show nothing..can you give me another link..
edit...now i can download it ..my connection was sux ...nice kernel..thanks for your gud work..
Sent from my GT-I9100G using XDA
testing...
Hope a good kernel. Testing ...
cant use pattern pin or password lock
Street79 said:
hi all,
the last few days i spent my time on learning how to compile a kernel, add new features to the source code and so on. the most time i spent on writing scripts, to make many things as easy as possible. and that's the result:
streetware-kernel-0.4 #final-release
i've been testing this kernel the last days and everything seems to work fine. but if something unfortunately doesn't work or if you have any suggestions, please leave a comment...
and now, have a lot of fun...
Click to expand...
Click to collapse
Great ~! Will try it ~
Gonna give it a try
xguestx said:
cant use pattern pin or password lock
Click to expand...
Click to collapse
thanks for the hint. i will fix it soon...
Good kernel...great batery life..
Sent from my GT-I9100G using Tapatalk 2
It looks good!!! thanks!!
rascal123 said:
Good kernel...great batery life..
Sent from my GT-I9100G using Tapatalk 2
Click to expand...
Click to collapse
What rom u are using ?
@Street 79- Galaxy S2 i9100G kernel has a ton of bloat ,i can help u strip it if u want and make the kernel faster and smaller.What say?
sakindia123 said:
@Street 79- Galaxy S2 i9100G kernel has a ton of bloat ,i can help u strip it if u want and make the kernel faster and smaller.What say?
Click to expand...
Click to collapse
okay, let's do it... thanks for the offer!
i will upload my kernel source later, so we can have a look together what to do...
Sent from my GT-I9100G using xda premium
Thank you for the new kernel. I will try it, when I have chance to download my connection are to bad atm
Gesendet mit meinem I9100G - GaLaXy Rom 5.1 & Lucifr 1.6 200 Ver
Ratheesh143 said:
What rom u are using ?
Click to expand...
Click to collapse
im on this rom
http://forum.xda-developers.com/showthread.php?t=1629030
xguestx said:
cant use pattern pin or password lock
Click to expand...
Click to collapse
fixed...
Hi Street79
When you mention "place an empty file called..." do you mean empty FOLDER ?
great kernel by now...
thanks for the good work. this kernel makes my i9100g realy faster and without any problems by now. still using it and will report any problem, but seem flawless.
thanks,
and i hope some day we could be able to overclock our processors, just wondering how good the benchmark scores can go up.
Related
I won't write long and fancy descriptions... I am planning to keep both kernel and the OP as clean as possible.
This kernel is for Xperia-T only and supports only Sony ICS ROMs for now.
FEATURES:
Autoroot
Some optimizations by cherrypicking from others & upstream
Some change-this-and-that kind of optimizations on governors
Some additional I/O Schedulers (sio, v/r)
Undervolting support
Overclocking support (192-1890MHz) with some modifications on thermal throttling to prevent overclocked values to be used during boot.
Custom CWM-based recovery with touch gestures (thanks to sk8erwitskil for the gesture support)
STweaks support (included in the kernel or from Google Play). it is an opensource app which generates dynamic UIs based on /res/uci.sh script interface and lets your set some kernel parameters easily. It will be auto-installed.
Fast-dormancy is disabled as default. You can enable it using STweaks.
KNOWN ISSUES:
Some STweaks settings are not effective
kernel needs some time to apply settings and you may feel some lag for the first 2-3 minutes. this will be fixed soon.
TODO:
cm10 support
Xperia TX support
dual-boot
more features...
THANKS TO: Codeworkx, Kali, all CyanogenMod contributors, sk8erwitskil, krabappel2548, Ninphetamine, Chainfire,... (please remind me if I forgot anyone)Download: http://d-h.st/users/siyah/sony-xtSources: http://github.com/gokhanmoral/siyah-xt
Ramfs: http://github.com/gokhanmoral/ramfs-xt (only updated each time I make a release. for test versions you will have to extract it from the kernel image)
reserved
for FAQ
Many thanks
I will test this on my rom and link it to the all in one thread.
Works fine ROM-Assaye
Touch recovery is excellent!
No vibration on prompt to recovery, but has purple LED, I would appreciate the vibraion back please.
Will test other feature in time.
EDIT:
Unexpected error in STweaks
i've just installed this kernel.....works great!! smoother and faster.... now trying !!! thanks!!!
Reserved for a probable, long and boring FAQ post...
Just installed
Thanks GM
TX can not flah cwm.zip, the script is wrong....
but use fastboot can.
Sent from my LT29i using xda app-developers app
r35471853 said:
TX can not flah cwm.zip, the script is wrong....
but use fastboot can.
Sent from my LT29i using xda app-developers app
Click to expand...
Click to collapse
I have not tested it on TX and that is why I wrote "Xperia-T only" to the first post.
also, make sure you read TODO..
if you use it on TX, use it at your own risk.
i will give this kernel a test on pacman and latest paranoid roms if you want.
y2grae said:
i will give this kernel a test on pacman and latest paranoid roms if you want.
Click to expand...
Click to collapse
I haven't tested it on cm10 although I put some init files to the ramfs.
it will probably not boot on CM10 or anything based on that.
it is still on my todo, but will send you a message when I need it to be tested on an additional device.
gokhanmoral said:
I haven't tested it on cm10 although I put some init files to the ramfs.
it will probably not boot on CM10 or anything based on that.
it is still on my todo, but will send you a message when I need it to be tested on an additional device.
Click to expand...
Click to collapse
no worries.
i know the cm10/paranoid kernels have no boot animations, which was offputting for the first few boots.
as greg asked before, can we keep the vibration for cm prompt if possible?
oops.. tested STweaks now and it doesn't work. seems like I will upload 0.2 in 20 mins
and I will put the vibration before cwm amber light toggle.
damn.. I think I will never be able to have a first release fully working
gokhanmoral said:
oops.. tested STweaks now and it doesn't work. seems like I will upload 0.2 in 20 mins
and I will put the vibration before cwm amber light toggle.
damn.. I think I will never be able to have a first release fully working
Click to expand...
Click to collapse
thats what first releases are for...just checking backup and restore in .tar mode now
---------- Post added at 02:28 PM ---------- Previous post was at 02:22 PM ----------
Another problem..sorry. its not really a bug, just something that could be made better
The backup option does not have a confirm option, which i found painful on non touch versions becuase i sometimes hit the power button instead of volume up or down and start a backup by mistake.
I have just done the same again because as son as it finished a backup I went to pick the phone up and touched the screen on the enter butoon and another backup started....could you implement an "are you sure" option like on other screens where you have to scroll up and down through a load of no options before you hit yes...
I have uploaded v0.2
-added vibration during boot, just before cwm prompt
-fixed stweaks xml file (the problem was related with a last minute addition of sched_mc parameter)
Hi gok, if you want it moving over to Original Development let me know as your work generally couldn't get much more original
I won't be round till later but will move it then if none of the other mods see it first.
Thanks as always for sharing your work :good:
AvRS said:
Hi gok, if you want it moving over to Original Development let me know as your work generally couldn't get much more original
I won't be round till later but will move it then if none of the other mods see it first.
Thanks as always for sharing your work :good:
Click to expand...
Click to collapse
thank you for your kind comment but for now the kernel is not so original.
it has some cherrypicks and influences from some other repos although some parts are carefully corrected.
I want to make an example of "it is not who you are which makes your posts to be placed in original development but it is what you do"... and kernels can be unoriginal work as well.
I will ask for your evaluation once I feel like the work is more original
thank you again.
V0.1 Restore failed twice in .tar mode.
gregbradley said:
V0.1 Restore failed twice in .tar mode.
Click to expand...
Click to collapse
thanks for reporting it. honestly I haven't checked it yet, but I will tonight.
updating known issues for now
gokhanmoral said:
thanks for reporting it. honestly I haven't checked it yet, but I will tonight.
updating known issues for now
Click to expand...
Click to collapse
no problem. It failed on both the backups i made with this recovery and now just failed on a known good .tar backup i made with a previous recovery.
It fails at different times, once on restoring system once on a md5 ismatch (On the new backups) and on the known good backup it failed on restoting data
"Error while restoring /sdcard/ .android /.androi_secure!"
But its a good looking recovery, I will be using it when these wrinkles are ironed out.
Again, many thanks, and if the confirm option for the backup is implemented as well, I would be over the moon.
gregbradley said:
no problem. It failed on both the backups i made with this recovery and now just failed on a known good .tar backup i made with a previous recovery.
It fails at different times, once on restoring system once on a md5 ismatch (On the new backups) and on the known good backup it failed on restoting data
"Error while restoring /sdcard/ .android /.androi_secure!"
But its a good looking recovery, I will be using it when these wrinkles are ironed out.
Again, many thanks, and if the confirm option for the backup is implemented as well, I would be over the moon.
Click to expand...
Click to collapse
did you backup to internal or external card?
and do you have any app moved to .android_secure? (move2sd)
I have just run backup to internal and restored it successfully. EDIT: no .android_secure backup
I will also try to backup to external sd
Hi folks,
There seem already many AOSP builds for NS, but I'm just pleased to share my personal build with you. I took the Google source and CM kernel/vendor as a base and have done lots of optimization work. My changes for NS after forking CM vendor were listed in the changelog of the initial build. Devs can check out commits on my github. It may worth a note that it's AOSP so never request extra features. No doubt I will keep it as stock as possible.
Credits:
clearly go to CM Team and all worked for our NS
steven676 for SurfaceFlinger and other patches
Download:
Final Build | MD5: 47af680bd273732d751de65656f62f7e
I don't hold the Nexus S any more, so if something in the final build does stupid for you, fall back to Build 6. And at last thank you again for your support.
Issues:
panorama preview. Check out CataHd's reply for the fix.
android-4.4.3-r1.1 build can be found in this reply. Panorama issue has been fixed.
You can find out all changes on my Github. Remember that AOSP ROM doesn't include Gapps, you have to install/flash it yourself.
Cheers,
Changelog:
Final Build
android-4.4.2_r2
merged some fixing patches from CM etc
Build 6
fixed random rebooting issue
saved about 3MB memory from the Kernel, thanks to pawitp
Build 5
android-4.4.2_r1
added swipe the pull-down panel to switch between Notifications and QuickSettings, thanks to CM/Slim
speed up statubar/notification drawer, thanks to kufikugel
changed dalvik heap parameters to reduce memory footprint (CodeAurora)
used double buffering instead of triple buffering
disabled hardware Vsync completely
fixed Screen record function, but in landscape only
increased the extra free memory to 12MB (you can change it in build.prop at any time.)
alpha 4
increased EGL cache size
switched to SW-based Vsync implementation by Google
fixed Keyguard layout for some languages
added a workaround to suppress the SU binary deprecated warning
few patches in Kernel and other minor fixes in SurfaceFlinger
alpha 3
merge in AOSP 4.4_r1.2
WebView black square issue was gone. Thanks to klusark for the wonderful porting work.
fixed app to sdcard function
enable low RAM feature in 4.4
root access fixed in Superuser with ART enabled
add Emoji support
Changes from init alpha Build:
merge the extra free kbytes patch from 3.4 Kernel
enable Swap for zRAM and KSM in Kernel side
Kernel 3.0.101
I will test this tomorow !
It's working fine. Very stock-ish feel. No FCs whatsoever (except for apps that are yet to be updated to fully support 4.3)
excellent rom thanks !!!!
only problem with superuser..I must install zip from recovery !!
then all ok !!
leap_ahead said:
excellent rom thanks !!!!
only problem with superuser..I must install zip from recovery !!
then all ok !!
Click to expand...
Click to collapse
Thanks for trying. But Superuser was fixed for weeks and works for me.
cn.fyodor said:
Thanks for trying. But Superuser was fixed for weeks and works for me.
Click to expand...
Click to collapse
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
leap_ahead said:
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
Click to expand...
Click to collapse
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD
leap_ahead said:
no my friend .. I flash 3 times to make it sure and no work
if you go to settings superuser then u will se that u cant change anything in superuser settings..
also check with root checker..
but don't worry !! this is nothing for this super rom !! I try all aosp 4.3 rom and this is the best for me !!
Click to expand...
Click to collapse
cn.fyodor said:
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD
Click to expand...
Click to collapse
Works fine here.
cn.fyodor said:
I tried changing settings in Superuser, every option works like charm. I always chased the changes of Superuser by Koush and the hack in that Superuser zip was included in my ROM. Afaik the tweak is just to run '/system/bin/su --daemon' for the root requirement.
OK, anyone else got superuser issue? xD
Click to expand...
Click to collapse
I don't know ..is not work here for that I flash the zip ..
sorry but is ok to flash the zip ? or I must try again without the zip ?
*now I remember that I get notification that su is out date and I forget to click ...
Downloaded and installed the latest superuser.zip and the su binary out of date notification is gone
Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.
Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.
Great job, I hope the project continues.
@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.
Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...
Greetz
lagloose said:
Hey,
just had a closer look at your build and found the interesting property 'ro.sys.fw.bg_apps_limit' in your build.prop which is set to 8. Are you sure this works in your build ? (I only ask because this was seen only in CM until now)...
Greetz
Click to expand...
Click to collapse
Yeah, CM merged that commit from Codeaurora afaik. Bet you haven't checked out my github yet. xD
velishka said:
Very good job. So happy to see the deveopment for our old phone continues.
Now, I can confirm Superuser doesn't work. Flashing SuperSU from recovery fixed the issue pretty fast.
Other than that the ROM is very solid and smooth. I tested SMS, Location services, Wi-Fi, left phone without a charge for a night. No problems so far. Will test bluetooth streaming later today in my car.
I have the same issue with calendar like any other non google build has, I have two of them, one is AOSP build another is Google's from the play store. That doesn't bother me.
Also, I still want to know what kind of "optimization" was done. Also, can anyone test MTP for me? I turned it on using USB Switcher, but my computer didn't recognize the device.
Great job, I hope the project continues.
Click to expand...
Click to collapse
I connect the phone to car radio so it ok !
for root you can flash the superuser from koush too ...
use marmite kernel for mtp ...
I use other gapps so I don't have the problem with two calendar ..only one I get the green one ...
---------- Post added at 05:26 PM ---------- Previous post was at 05:25 PM ----------
cn.fyodor said:
@leap_ahead, velishka:
Let's rule out some exceptions about Superuser issue. Did you do factory reset before flashing? I hope the old Superuser app didn't make noise. Although you guys have fixed it manually, I still hope someone can paste the output of command 'getprop persist.sys.root_access' and check if the /system/xbin/su is running when you can't get root permissions. Thank you.
Click to expand...
Click to collapse
yes I make full wipe and ofcource factory reset ! with twrp recovery !
cn.fyodor said:
Yeah, CM merged that commit from Codeaurora afaik. Bet you haven't checked out my github yet. xD
Click to expand...
Click to collapse
Indeed, i didn't check it out yet. Link ?
lagloose said:
Indeed, i didn't check it out yet. Link ?
Click to expand...
Click to collapse
link :https://github.com/Juansheng
I can just say, very nice work, I'll try the rom soon
cn.fyodor said:
[*]Superuser fails (Workaround is to run '/system/xbin/su --daemon' via adb shell, then go to Superuser settings -> allow root access. Then it'll be fine even after a reboot. Thanks to leap_ahead for bug report)
[*]Gesture typing not working?
[/LIST][/HIDE]
Click to expand...
Click to collapse
or you can flash via recovery the superuser zip from here :http://download.clockworkmod.com/superuser/superuser.zip
for gesture I use other gapps that gesture is working without any problem
Wanna try this Rom, seems great..
Sent from my Nexus S i9023 using Tapatalk 4 Beta
Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.
Greetz
lagloose said:
Used this baby for 3 days now and have to say that it has the best memory management for 'low-memory' devices i've seen until now. Whatever you did cn.fyodor, very good work. !
I've noticed that CM has already reverted the commit for property 'ro.sys.fw.bg_apps_limit'. You should take care that this is not reverted in your sources because IMHO this is one of the essential things which gives us this better memory management. The relevant part can be found in line 105 of https://github.com/Juansheng/androi...s/java/com/android/server/am/ProcessList.java in your github.
Greetz
Click to expand...
Click to collapse
Thanks for your suggestion. Actually I once changed MAX_HIDDEN_APPS back the default value in Gingerbread for low memory devices nine months ago. Check this commit. ro.sys.fw.bg_apps_limit was just introduced by Codeaurora recently. And yeah CM have already reverted this prop and added a new prop for high memory (> 1.5GB) devices since more CM supported devices hold more memories nowadays. I'll ignore that commit.
Cheers,
Introduction
Hello dear developers and android hackers,
On this thread, I will share with you a project I am developing as I am learning kernel programming / hacking. This kernel is based on Sony kernel sources with some enhancements for battery saving and performance.
Click to expand...
Click to collapse
Features
Based on Sony 23.5.A.0.570 kernel sources
Compiled with linaro GCC 4.9.1 toolchain, -O3
Governors : interactive, ondemand, performance, conservative, smartassV2, intellidemand2 and intelliactive.
Fast hotplug
CPU overclock up to 2.8 GHz Thank's to Faux123 and DooMLoRD
Changed GPU frequency table to 27 - 657 MHz Thank's to Myself5
Sony RIC disabled
Undervolt
TWRP recovery included, fota partition support
Breathing notification light thank's to glocklee
Force Fast Charge
KCAL Advanced color control Thank's to savoca
Click to expand...
Click to collapse
Installation instructions
Code:
Use this kernel at you own risk !
I am not responsible for any damage or problem.
Flash the zip via recovery
Reboot
Click to expand...
Click to collapse
Download
Please read FAQ and second post if you have any issue
Recovery flashable zip :
Abricot kernel v8.1.zip
mirror
Kernel Source :
Kernel
Ramdisk
Click to expand...
Click to collapse
Changelog
Abricot kernel v8.1 : 12.05.16
Disable RIC at kernel level (Fixes partition mounting in recovery)
Add KCAL Advanced color control Thank's to savoca
Abricot kernel v8 : 10.05.16
Based on Sony sources 23.5.A.0.570
Updated TWRP to version 3.0.2-0
Abricot kernel v7 : 01.04.15
Updated to Lollipop kernel sources 23.1.A.0.690
Update TWRP to 2.8.5.0
Add Force Fast Charge
Removed splash screen
Abricot kernel v6 : 24.12.14
Fix default freq not applying for all cores at boot
Fix -O3 compiler optimization
Fast hotplug : plug in cores in descending order
Abricot kernel v5 : 15.12.14
Increase voltage of higher frequency for better stability
Add support for displaying the number of tasks running
Add VR, SIO and FIFO schedulers
Add lagfree governor
Update TWRP to 2.8.1.0
Fix scaling_max_freq permissions
Set default frequency to 2.3GHz
Abricot kernel v4 : 11.12.14
Add CPU overclock up to 2.8 GHz (Thank's to Faux123 and DooMLoRD)
Change GPU frequency table to 27 - 657 MHz (Thank's to Myself5)
Disable Sony RIC
Remove msm_mpdecision
Set qcom mpdecision as default
Abricot kernel v3 : 07.12.14
First public release
Check my github to see all the changes.
Click to expand...
Click to collapse
FAQ
Q : With what ROM can I use this kernel ?
A : With any ROM based on Sony stock Marshmallow
Q : Your kernel isn't working / My phone isn't booting anymore
A : Read this whole post once more, search for your problem in thread and report it if you haven't found a solution.
Q : Can I install this kernel on locked bootloader ?
A : No ! This kernel is only for unlocked bootloader.
Q : Does this kernel include recovery ?
A : Yes ! You can access by pressing buttons when the led is lighting. Volume down to go to TWRP and Volume up to load recovery from FOTA..
Q : What are mpdecision and fast hotplug ?
A : This is what manage your cpu cores and decide which core will be online. Fast hotplug is a brand new hotplug that I wrote. See next post for more information
Click to expand...
Click to collapse
Thanks To/Credits
* Sony for their sources and device
* @DooMLoRD
* @thewadegeek for his Tutorial
* @show-p1984 for his mpdecision
* @glocklee for his breating notification mod
* @Envious_Data for his help and links
* @dssmex
* @Androguide.fr for Pimp my Z1
* bbedward
* Erasmux
* faux123
* The xda community for making me discover android and for answering so many of my questions
* Google for kernel sources and its search engine
* Apple for making expensive phone so that I never bought one of theirs
Click to expand...
Click to collapse
Please let me know per pm if there is any mistake or misspelled word in this thread. Automatic correction does a great job but since english isn't my mother thongue I'm pretty sure I made mistakes.
XDA:DevDB Information
Abricot kernel, Kernel for the Sony Xperia Z2
Contributors
pec0ra
Source Code: https://github.com/pec0ra/abricot
Kernel Special Features:
Version Information
Status: Testing
Created 2014-12-07
Last Updated 2016-05-20
About Fast hotplug
Motivation
I wasn't convinced by show-p's msm_mpdecision nor faux123's intelli_plug ( I don't even talk about qcom mpdecision ). I also wanted to start working on a bigger programming project to learn more about kernel developing so I decided to write my own hotplug.
Main features
I tried to make fast hotplug the lightest possible, so that it consumes the less resources possible when it is not needed (mainly at idle). One of the second goals was to make it customizable.
How to use
Deactivate qcom mpdecision (Pimp my Z1 will do this automatically when you choose fast hotplug)
Activate fast_hotplug
Code:
adb shell "echo 1 > /sys/module/fast_hotplug/parameters/fast_hotplug_enabled"
Tune it to your liking
How to configure
Unfortunately, there isn't yet any user friendly application to configure fast hotplug. The only way to configure it is to manually edit the module files with adb or a file editor.
I modified Pimp my Z1 to be compatible with fast hotplug. You can find the modified version at post 12
You can also find all the parameters at
Code:
/sys/module/fast_hotplug/parameters/
and edit them with adb command
Code:
adb shell "echo [COLOR="Navy"]<value>[/COLOR] > /sys/module/fast_hotplug/parameters/[COLOR="Navy"]<variable_name>[/COLOR]"
You can configure the following parameters :
fast_hotplug_enabled : 0 for disabled, 1 for enabled
boost_duration : Duration of boost in ms when screen is touched
threshold_to_boost : Instead of automatically pluging in cores on touch, fast hotplug checks that the load is above this threshold. This avoid cores coming online when reading file or website.
max_cpu_on : Maximum number of online cpu when screen is on
min_cpu_on : Minimum number of online cpu when screen is on
idle_threshold : Threshold under which fast_hotplug will remain almost idle and won't perform any check. This applies when only 1 core is online
plug_in_core_X_threshold : with X between 1 and 3. This is the threshold to plug in coreX.
plug_in_core_X_delay : This is the number of fast_hotplug cycles (see refresh_rate) to skip before pluging in coreX.
plug_out_core_X_threshold : Like plug_in_core_X_threshold but to plug out.
plug_out_core_X_delay
refresh_rate : Time in ms between fast hotplugs checks
screen_off_singlecore : 1 for activated, 0 for deactivated; Allows only one core to be online when screen is off.
If you are using linux, you can easily change the configuration with this small program : https://github.com/pec0ra/fast_hotplug_controller
You will probably want to create init.d script to make your configuration stay after reboot. If enough users want it, I can create an example of script.
Bugs / stability
Due to some conflicts with qcom mpdecision, it is possible that you encounter some bugs / reboots when both are enabled.
Configuration doesn't stick after reboots
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Please tell me your impression, your custom configuration and / or your recommendation so that I can make it better in future releases.
Good luck.
Will try as soon as I can. :good:
Welcome! :good:
pec0ra said:
Help needed
If you are a java developer (or want to learn ) and want to help in developing an app (or editing an already existing one) to control the hotplug, please send me a pm
Click to expand...
Click to collapse
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
B1nny said:
Regarding this, there is already an app out there that is FOSS, licensed under the GPLv2 license, looks sexy and should be easy to modify. It's called Pimp My Z1, I think it offers pretty much everything you want.
Other than that, cool that you're developing something new, I'll give it a shot!
Edit:
You may want to disable Sony's RIC it prevents you from writing to /system. This should help you.
Click to expand...
Click to collapse
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
FrosteezBR said:
I can't seen to get notification breath effect,i didn't do the mpdecision step,so could this make the diference?
Click to expand...
Click to collapse
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
vendetta718 said:
Is this kernel compatible with franco kernel apps?
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
pec0ra said:
Thank you for the link
I'll see if I can do something with this app when I have more time (I've never made any android app).
Disabling ric is a good idea I'll do this for next version.
No, mpdecision won't affect it. Have you tried it on YadliKernel ? Did it work for all the notifications ? It seems like on abricot kernel they work for most of the notifications but not for sms.
It is probably compatible (I didn't tried it) but you will probably not be able to change most of the configurations since they are not implemented in my kernel. Some configuration from my kernel (like fast hotplug) are also not implemented in the app so you can't change them from there.
Click to expand...
Click to collapse
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
FrosteezBR said:
i try with facebook,whatsapp,messaging and gmail
with a led tester its the same blink as stock
would i send you a dsmeg or anything?
Click to expand...
Click to collapse
There's no printing in the mod I think so dmesg would be useless. I'll try again with WhatsApp. Have you tried it on other kernels? Was it working ?
Edit : ok, maybe there is an error... In this case dmesg could be useful. If you have time you can send it, yes.
And I reconfirm that it works for telegram
Hey, can someone show us the notification mod?
Pimp my Z1
As @B1nny suggested, I tried editing Pimp my Z1 to add fast hotplug support. Everything seems to work and I even added some tweaks for a better support for our Z2 ( some default values were not really compatible with our device ). There are probably bugs for configurations other than fast hotplug. If I have time, I will fix them but for now, please use another app to set your frequencies / governors / voltage or live with the bugs. If you have questions about the app, you could also take a look at the official thread to see if it is already there or maybe just to give the dev a thanks.
I'll probably make a pull request to @Androguide.fr with the changes but until then you can use my own build linked to this post. If you already have the app installed, you will have to uninstall it first because signature is different.
You can see the full source and the changes on my github : https://github.com/pec0ra/Pimp_my_Z1
Special thanks to @Androguide.fr for his great app and to @B1nny for his link
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
nreuge said:
@pec0ra
Good news to have a new kernel dev for our beloved Z2 !
However, I've tried to flash your kernel, the flashing process seems to work correctly but actually I stay stuck to the last doomlord advanced stock kernel. Any suggestion ?
Click to expand...
Click to collapse
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
pec0ra said:
You should try to extract the .elf from the zip and flash it via fastboot
Code:
fastboot flash boot <name>.elf
Anyone else experiencing the same issue ? Maybe I did something wrong in my zip.
Click to expand...
Click to collapse
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
B1nny said:
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
I was going to post the same thing
Waiting for confirmation...
B1nny said:
I think you mean the .img file instead of .elf.
Other than that, the kernel works fine for me. I did manually flash it via fastboot. (because I prefer to flash it via fastboot)
I took a quick look at your updater-script and compared it to Doomlord's updater-script and this is what I found:
Your script tries to write the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/Kernel
While Doomlord's script writes the kernel to this partition:
Code:
/dev/block/platform/msm_sdcc.1/by-name/boot
Maybe that's the culprit?
Click to expand...
Click to collapse
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
pec0ra said:
Thank you
Yes, I meant .img. It seems like it'll take some time to get used to this new device. The kernel destination you pointed out is probably the issue, yes. And that's probably the notification problem too. Seems like the kernel never got flashed so it's logical that notification mod doesn't work...
I'll change this tomorrow morning
Maybe someone can test it until then.
Click to expand...
Click to collapse
Yes, this was indeed the issue, I've just succesfully flashed your kernel changing "Kernel" to "boot" in the script.
Now testing
I can't rename mpdecision.. I tried with root explorer and root browser
sh4d1t0 said:
I can't rename mpdecision.. I tried with root explorer and root browser
Click to expand...
Click to collapse
That's due to Sony's RIC being enabled by default. If you look at my previous post where I mention it there is a command you can run in ADB to temporarily disable it, not ideal but it will help you rename the file.
Hey, it's been a while since my last (and failed) release, so let's see if you can help me on this one.
As you might have guessed, I have compiled our latest kernel, and this is my own version!
Right now, people have reported battery life improvements, I'd love to hear what you think!
Changelog
Code:
V2.0
* Enabled some CPU governors.
V2.1
* Updated KSM with uKSM.
* Added Thunderplug hotplugging driver.
* Added PMC and Smartmax CPU governors.
* Added Init.d support. (Make sure the file has the proper permissions)
V2.2
* Updated GPU drivers to be compatible with EMUI 4.1.
* Added Intelliplug hotplugging driver.
* Improved GPU performance.
Downloads
V2.2 (New): https://github.com/XePeleato/ALE-L21_ESAL/releases/tag/v2.2
Instructions
Download the .zip
Flash from recovery
Done!
You can get the source here: https://github.com/XePeleato/ALE-L21_ESAL/tree/v2?files=1 (v2 branch)
Guide
I am going to try to help you to decide what settings you should apply
First of all, I recommend to install Kernel Adiutor.
If you prefer battery life:
Start Kernel Adiutor:
Go to CPU in the drop-down menu and set as governors PMC or SmartmaxThen go to CPU hotplug and don't enable many cores, since more online cores means more power used. You can also set the Endurance level to Quad-core
If you prefer performance:
Start Kernel Adiutor:
Go to CPU in the drop-down menu and set as governors performance (will set the CPUs to their max frequency)/ondemand/interactiveThen go to CPU hotplug and make sure to lower the load threshold, having a low load threshold will make your phone use more cores (if you experience lag while playing, maybe it's set too low, so use a wise value, do your testing.)
To conclude, I just mentioned where the settings are and some example values, if you love to play games you won't use the same settings as someone that just likes to read emails and use Google Chrome, find the settings you are comfortable with, and don't forget to set Apply on boot!
Now some screenshots of AnTuTu and 3DMark with Performance governor and Esalv2.1:
http://imgur.com/a/iRDpD
As you can see, even 3DMark detects that my score is higher than the average, try to beat that with stock kernel!
I hope you enjoy it, and please, I'd love to hear your suggestions!
just a quick question if you dont mind : any way to flash it via twrp ? so in case that something goes wrong i can easily restore the old one with a backup .
Firicel69 said:
just a quick question if you dont mind : any way to flash it via twrp ? so in case that something goes wrong i can easily restore the old one with a backup .
Click to expand...
Click to collapse
I'll upload a flashable zip, but it shouldn't be a problem, if you take a backup of your Boot partition and restore it, it will overwrite the kernel.
thanks! i will try it and see how it goes.
Sim gets detected but stucks at the point of unlocking it.
waiting for comments on the kernel
VenityZ said:
Sim gets detected but stucks at the point of unlocking it.
Click to expand...
Click to collapse
I've noticed it too, it finally unlocks in my end, can you please check if it gets unlocked?
XePeleato
Tnx bro)
Great job.
Finally , I have the full root, before either he could not edit the folder systems
XePeleato said:
I've noticed it too, it finally unlocks in my end, can you please check if it gets unlocked?
Click to expand...
Click to collapse
I kept the screen active and it worked after 40s
Basic stuff works , so god for daily usage I guess. Is rep on github up to date of this kernel because I compiled it myself and nothing worked. I either think my toolchain is the problem.
---------- Post added at 03:18 PM ---------- Previous post was at 03:00 PM ----------
Also the governors do work , I don't know if all do but theres a noticeable performance change when chaging it. Over/Undercloking still doesnt work , but its not the kernels problem. The power genie of emui controls it.
VenityZ said:
I kept the screen active and it worked after 40s
Basic stuff works , so god for daily usage I guess. Is rep on github up to date of this kernel because I compiled it myself and nothing worked. I either think my toolchain is the problem.
Click to expand...
Click to collapse
Yes it is, the v2 branch, you'll need to edit build.sh to point it to your toolchain.
XePeleato said:
Yes it is, the v2 branch, you'll need to edit build.sh to point it to your toolchain.
Click to expand...
Click to collapse
Thanks I compiled the "v1" branche....
Wi-Fi, Bluetooth, NFC works.
I will test mobile data, GPS tomorrow.
"Bug": SIM unlock takes a lot more time than stock kernel.
Great work! May I ask what features are you going to add into? OTG maybe?
Anyway: Great! Keep it up!
EDIT:
How can I change governor? I'm looking for extra governos (PMC, Smartmax) in Kernel Auditor but I can't find them
LG*L70 said:
Wi-Fi, Bluetooth, NFC works.
I will test mobile data, GPS tomorrow.
"Bug": SIM unlock takes a lot more time than stock kernel.
Great work! May I ask what features are you going to add into? OTG maybe?
Anyway: Great! Keep it up!
EDIT:
How can I change governor? I'm looking for extra governos (PMC, Smartmax) in Kernel Auditor but I can't find them
Click to expand...
Click to collapse
Hi, can you find ondemand, interactive, powersave...? OTG is enabled, the problem is at the rom.
XePeleato said:
Hi, can you find ondemand, interactive, powersave...? OTG is enabled, the problem is at the rom.
Click to expand...
Click to collapse
Hi,
Yes, I can.
Thank you for the heads up about OTG, I didn't know that
XePeleato said:
I'll upload a flashable zip, but it shouldn't be a problem, if you take a backup of your Boot partition and restore it, it will overwrite the kernel.
Click to expand...
Click to collapse
I'd also appreciate flashable zip please
TheATHEiST said:
I'd also appreciate flashable zip please
Click to expand...
Click to collapse
Done! Check the OP, I added the link there.
XePeleato said:
Done! Check the OP, I added the link there.
Click to expand...
Click to collapse
Thanks :good:
Init.d support would be really nice xP
VenityZ said:
Init.d support would be really nice xP
Click to expand...
Click to collapse
It will be added on the next release!
Working fine for me. The Unlocking the SIM takes about 40 seconds. Governor's work. Thanks man, keep up the good work.
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.