Related
Introduction:
---------------------
TeamWin Recovery Project, or twrp for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features that we deemed missing from current recoveries. After a lot of hard work for weeks, we are happy to announce the release of twrp in anticipation of unrEVOked & AlphaRev's revolutionary release.
Key Features:
---------------------
- Clean, simple, intuitive Menu System
- Ability to save custom recovery settings
º Default partitions to back up
º Default zip folder location
º Default color theme (lots to choose from) (Thanks to ffolkes!)
º Default Time Zone (for more accurate time stamps; US time zones only for now)
º Zip Verification
- Ability to select which individual partitions to backup, and restore.
- Ability to choose compression or no compression backups.
º Compression takes longer of course, but you save roughly half the space. EVO3D's stock system uncompressed is ~800mb, 380mb compressed. You choose.
- Ability to auto restore GAPPS on zip flash (for CM based ROMS)
- Ability to auto reboot after successful flashes (for the lazy)
- Capacitate Button functions (removed for now)
º Home - Main Menu
º Menu - Advanced Menu
º Back - Up a Menu Level
º Search - Select Current Selection
- Battery Level and Timestamp (battery meter not working right for now)
Known Issues:
---------------------
- Battery % issue is still there until we can fix the kernel
- Capacitative Buttons are disabled for now, while we fix HTC's broken kernel.
- While working on twrp, TeamWin's top race horse ran off, if you find him please let us know. (he must be getting really really lonely now) - Our horse was found by mttneedham, thanks for returning him safely! -
Disclaimer:
---------------------
As usual, use at your own risk. TeamWin is not responsible for anything bad that may occur from using twrp. We do however take responsible for the awesomeness that comes with it. Don't be a d3rp and use twrp for bad. With great power, comes great responsibility.
Special Shout Outs:
---------------------
- TeamWin
º toastcfh - for his under appreciated dedication to the community.
º agrabren - for his leading the way to freedom for numerous devices with fre3vo.
º Dees_Troy, joeykrim, shift, vividboarder, onicrom, netarchy, kevank, myndwire, bigbiff, dkelle4, shinzul, spiicytuna, eyeballer, OtisFeelgood.
- Amon_RA - for his great Recovery for which we gained a lot of inspiration from.
- Koush - for his dedication to the community and ClockworkMod.
- unrEVOked for their great work and dedication to the community.
- AlphaRev for their great work and dedication to the community.
Source Code:
GitHub
Download:
---------------------
TeamWin twrp Page
(All future updates will be updated on TeamWin's site.)
---------------------
Donate to TeamWin Recovery
Changelog:
2011-08-05 v1.0.3
new features:
- Added timezones that should cover everyone
- Added twrp spam feature (twrp settings)
- Added fix permissions (advanced menu)
- Added wipe cache and dalvik into Flash Zip menu
- Added copy recovery.log to /sdcard (advanced menu)
- Added output spam/no spam to restores
- Added mke2s prebuilt to /sbin
bug fixes:
- Fixed SD-EXT issues, (no partition SD-EXT features yet)
- Fixed EFS partition issues
- Changed the way we do backups on mtd devices, which should fix any boot partition issues
(we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G)
2011-08-01 v1.0.2
bug fixes:
- Fixed SD-EXT issues
- Added Format SD-EXT into format menu
- Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
- Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
- Rearranged the format menu
2011-07-30 v1.0.1
bug fixes:
-fixed small but with not detecting .android_secure
-fixed charge percentage (unfortunately capacitive buttons won't work for a bit, sorry!)
-fixed back to nandroid menu bug
-crash of recovery is fixed by flashing the zip instead of using fastboot
2011-07-29 v1.0.0 - initial release
FAQ
FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG86IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG86IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-shooter-1.0.0.img
How do I use MD5 checking?
First you need a .md5 file for the .zip you are trying to flash. This can be generated by running:
Code:
md5sum myzip.zip > myzip.zip.md5
This will generate a file with the checksum in it. It is important to do this from the directory containing the .zip so the file looks like lkadjflkadjflksadfjsal myzip.zip and not alkjdalfkdjsfdsflkajfd /subdirectory/myzip.zip since those directories can change.
Place this .zip and .zip.md5 file in the same directory and try to flash. It should show the md5 is being verified and flash if it checks out. Twrp will always TRY to verify the md5 file if it's found. If it is not found, it will say 'none found' and let you flash UNLESS you have 'Force md5' checked.
Error message when making phones calls
This appears to be due to Revolutionary and not our recovery, but for everyone's reference just stay on the line after the error plays. You will then be connected to Sprint where they will walk you through re-syncing your phone with the network. Start to end you are looking at like 5 min.
Battery Level Indicator is not working
It was tested on other devices, but appears to only show 10% right now on the EVO 3D. Requires a kernel fix on our part. Hang tight.
Error when flashing superuser zips
Flash this one instead: http://techerrata.com/toastcfh/Shooter/su-2.3.6.3-efgh-fixed-unsigned.zip
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
Why don't the buttons at the bottom work?
It seems the kernel source HTC gave us has issue with the daemon that controls offmode charging. As a result charging was having issues and not showing current current battery levels. That said... we had to make a choice until the issue in the kernel or daemon can be fixed, use the stock kernel (which all testing was done on and everything worked fine with) and lose the buttons at the bottom (touch screen is not configed right in the stock kernel) or use the custom configed kernel compiled from the sopurce HTC gave us. the lesser evil was to make sure charging was working correctly as it's far more important and use the stock kernel.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG86IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod or Amon Ra?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support (Should be back soon)
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.
SWEET!!!!
OMG let the games begin!!
Going to check out. Keep it going......
Sent from my PG86100 using www.psvitahacks.co app
Sweet Jesus
Now I am super excited. Thanks for all the under appreciated work, wife is going to hate me this weekend ;-)
Sent from my PG86100 using XDA App
is this like clockwork mod?
Woah! Raw!
Sent from my PG86100 using Tapatalk
Niiiice! Great work guys!!
Can't wait. Downloading now to avoid server overload tonight.
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
Automation?
xxxgeooegxxx said:
Now I am super excited. Thanks for all the under appreciated work, wife is going to hate me this weekend ;-)
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
+1
Sent from my PG86100 using XDA App
thanks...now how do i use it?? that is if i can use it
Awesome!
I am super excited to try this! You guys keep rolling out awesome stuff. I can tell that with S-OFF around the corner there will be lot's of cool projects for this phone. GJ
xxxgeooegxxx said:
Now I am super excited. Thanks for all the under appreciated work, wife is going to hate me this weekend ;-)
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
+2
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
phonetec said:
thanks...now how do i use it?? that is if i can use it
Click to expand...
Click to collapse
Can't until we get to use the tool that's coming soon. (Most likely tonight)
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
YAYYYY
Rydah805 said:
Can't until we get to use the tool that's coming soon. (Most likely tonight)
Sent From My HTC Evo 3D Using Tapatalk On The Now Network From Sprint!
Click to expand...
Click to collapse
the f5 key is broken on my laptop from tapping it all day. i saw this and wet my self just a lil lol. awesome thanks to all who put in the work much luv
Well this is exciting.
Sent from my fingers.
rtbluver said:
is this like clockwork mod?
Click to expand...
Click to collapse
Yes, it's similar. But our take on it. We added a lot of features to it, some eye candy, some functionality. Lots more planned!
Code:
#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
AOSP+ 0.8 - Android 4.3
AOSP+ is a collaboration ROM from myself and Lloir. Lloir enjoys using pure vanilla AOSP whereas I have always enjoyed the features from CM or AOKP. After trying out AOSP I was impressed with its speed and smoothness and found I actually only missed a few small things from those other ROMs so decided to port over just those features. The result: AOSP+
For all the changes over AOSP, see the second post.
All code that is not built directly from the google repositories can be found on github here https://github.com/AospPlus/
3rd party apps included in the ROM:
Superuser by Koush
LockClock from CM - much as Lloir hates it, i quite like it so it's gone in
Torch from CM
ShareLogs from cornedor - we will provide NO support unless the logs from this app are included with your post!
We welcome suggestions of other things people like from other ROMs that you want included but we want to try and keep all changes as light as possible to stay as close to AOSP as we can. Also, feel free to add your own features and make pull requests to our repos to have them included.
Kernel
Source: https://github.com/AospPlus/android_kernel_htc_enrc2b-BLADE
The boot.img in the ROM is the BLADE kernel. This contains ramdisk changes required for 4.3 so must be flashed.
Downloads
ROM
GAPPS
Installation
Extract boot.img from ROM zip and install from bootloader
Code:
fastboot flash boot boot.img
A factory reset and system wipe is always recommended (use Titanium to backup/restore your apps and data) but may not be required. If you have issues, please try and recreate them after a factory reset/system wipe before reporting them.
Install ROM and GAPPS from recovery
Wipe cache/dalvik
Reboot.
Thanks to...
@Lloir for working with me to get 4.3 working
@maxwen for his BLADE kernel
@corne for his ShareLogs tool
CyanogenMod Team
XDA:DevDB Information
AOSP+ 4.3, a ROM for the HTC One X+
Contributors
tombriden, Lloir
ROM OS Version: 4.3.x Jellybean
Based On: AOSP
Version Information
Status: Testing
Created 2013-09-16
Last Updated 2013-10-28
Everything seems to be working except for...
Known Issues
Camera only at 5MP
MHL
SELinux is disabled
HD videos don't work
Video recording now works but freezes when you press stop
Some issues with calls over BT
Changelog
2013-10-28 - 0.9.0 - Experimental
Updated audio blobs to official enrc2b JB 4.2 blobs!!! (huge thanks to Thömy in the endeavoru forums for this one)
Back to a stock based kernel to work with new audio blobs, all BLADE features are now missing
Removed Advanced Settings menu as none of them are applicable to the current kernel
2013-10-14 - 0.8.9
Updated to AOSP 4.3.1_r1 (JLS36I)
Reverted KSM changes to see if that was the cause of random reboots
2013-09-20 - 0.8.8
Re-added T-Mobile theme engine
Re-added overlay to disable Nfc by default
Fixed bluetooth
Updated sources to AOSP 4.3_r3.1
No more Superuser countdown
2013-09-17 - 0.8.7
Fixed superuser daemon not starting from ramdisk
Enable KSM
Updated AOSP sources to 4.3_r3 (JLS36C)
2013-09-14 - 0.8.6
Fixed double tap home
Synced device tree with cm
2013-09-04 - 0.8.5
All other 4.2.2 libs that can be updated, now have been updated.
Synced up with the CM device repos to make my life easier when working on both
Fix for hardware decoding/encoding video (so HD videos and camcorder work (though now a different issue with recording))
SELinux now on in permissive mode
Fix audioflinger crash on receipt of notifications
2013-08-26 - 0.8.4
Update to android-4.3_r2.2 (JSS15Q)
Updated a whole bunch of blobs from 4.2.2 OTA
2013-08-19 - 0.8.3
Only override the picture-size-values if the string is actually broken (fixes issue with front camera resolutions also being overridden and so causing it to crash)
fix ramdisk issue that cause Torch to FC
2013-08-18 - 0.8.2
Modified camera wrapper to return picture-size-values from previous vendor lib as new one is >256 chars
2013-08-18 - 0.8.1
Back to using BLADE rom; still too early days for mine
Re-added Advanced Settings to control BLADE options
2013-08-17 - 0.8
New kernel based closely on HTC stock
Updated camera proprietary libs from latest HTC 4.2.2 dump
Option to map double-press on home
Existing AOSP+ features rebased on Android 4.3
Volume wake option
Disable safe headset warning
Hardware keys remapping option
Improved display of metadata on lock screen music widget
Green LED at 100% when charging, not 90
Reboot option
Swapped round the Wifi QuickTile press/longpress functionality (ie press to enable/disable, long press to go to settings)
Rearranged of the quick tiles to what I think is a better layout, with radio/network icons grouped together, ending with Airplane mode that disables them all
Integration of SuperUser into Settings
FAQ
Titanium Backup won't restore/backup apks
Open Preferences
Select Backup folder location
Press back until you get back to /
Select /sdcard
Press use current folder
Select 'No' when asked to move backup files
\o/ i suppose i better sort out PaP soon
Am I stupid or what, cause I see the EndeavorUParts.apk in the zip but no Advanced settings in the settings?
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
tombriden said:
Oh yeh, I forgot to exclude it from the build. Normally you'd get to if from Settings but as the ROM doesn't come with BLADE it'd only confuse things to have it there as none of the options would work
Sent from my One X+ using Tapatalk 4
Click to expand...
Click to collapse
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Ranomez said:
Does the kernel have S2W support so I can activate it from an app on the market, and also should I flash the blade patched kernel after I flash the rom, cause I flashed it before and ended up with no signal at all, and then flashed the included kernel and everything works?
Click to expand...
Click to collapse
No this doesn't have s2w, and i just realised that the script to copy the BLADE modules is in the ramdisk so won't be there once you've repacked it. What you can do though, is download this https://github.com/AospPlus/android.../aosp-plus_4.2.2-r1.1/scripts/01-module-check
then push to init.d while in recovery and make it executable
Code:
adb reboot recovery
adb shell mount /system
adb push 01-module-check /system/etc/init.d/
adb shell chmod 755 /system/etc/init.d/01-module-check
then flash blade and hopefully it'll work
failing that, it might be worth giving an existing blade-42 a try; i know it didn't work on open master (pre 4.3) but i don't think i've tried it on 4.3 itself
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Hi,
I just installed this ROM but I am having no sound
Is there a way to fix it?
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
tombriden said:
Hmm, audio's working here; can you just try reflashing the kernel followed by
Code:
fastboot erase cache
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Hi,Yes I just tried but the sound is still not working
ForceField said:
Hi,Yes I just tried but the sound is still not working
Click to expand...
Click to collapse
Ranomez said:
In a call I get no sound if I try to switch to speackers, only normal calls working, also Viper4Android doesen't want to install the driver and gives an error asking if I am rooted and having busybox, installed busybox installer from sterycson from the play store and it says just Busybox installed and where it is, no version, Installing fails.....any help, allready reflashed the rom so thats not the problem?
EDIT: also included Camera app can only go to 5MP, and Focal can go to 6
Click to expand...
Click to collapse
Ok, can you guy's flash this for me please:
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
tombriden said:
Ok, can you guy's flash this for me please: http://downloads.kanger.me/getdownl...lusINTER/aosp-plus/boot-BLADE-43-20130818.img
It's a 43 build of @maxwens BLADE kernel, compiled inline using his source here (as always, huge thanks to him for his work on it)
Hopefully that'll sort the audio issues and i'll take a look at the Camera next
Click to expand...
Click to collapse
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
ForceField said:
I just flashed another ROM.
OK,I will reflash AOSP+ and the new kernel and report back
---------- Post added at 09:58 AM ---------- Previous post was at 09:44 AM ----------
Ok,I Reflashed ASOP+ with the new kernel
Sound is Working but Wifi is broken
Click to expand...
Click to collapse
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
tombriden said:
Ok, i kind of expected that but now i know the audio is fixed i can do a new build. Thanks for testing
if you want wifi back you can do: adb shell su -c 'insmod /lib/modules/bcmdhd.ko'
Click to expand...
Click to collapse
Ok thanks I will try this command. Really liked the speed of this ROM.It's a Porsche compared to others
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
tombriden said:
0.8.1 uploaded with built-in BLADE kernel and EndeavoruParts accessible from Settings -> Advanced
Camera still at 5MP though :/
Click to expand...
Click to collapse
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Ranomez said:
Perhaps using an other camer app would let us use the 8MP, because Focal lets us use 6MP?
Anyway your rom is great, close to perfection for me, the only thing missing would be any kind of lockscreen shortcuts but that's only me and I wanna say your rom is great.
Click to expand...
Click to collapse
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
tombriden said:
Thanks
Other camera apps will have the same issue. It's down to the new camera libraries from the 4.2.2 dump returning a 302character string for the supported picture sizes but they get read into a 256 string buffer thus cutting off all the higher resolutions :\
I've put a fix into our camera wrapper so it just returns the same supported resolutions as the previous library did. It's uploaded in a new ROM, 0.8.2 but the only file changed is camera.tegra.so so if you don't want to reflash, extract it from system/lib/hw and push in recovery with
Code:
adb shell mount /system/
adb push camera.tegra.so /system/lib/hw/
adb shell chmod 644 /system/lib/hw/camera.tegra.so
Click to expand...
Click to collapse
Thank you, and thanks god I don't need to reflash, cause I started flashing 8.1 at my previows comment and just finished seting up all my things (xposed, touchwiz, playstation certs, viper4android and some others) and really don't want to flash again, lol.
Hey guys, this is just a version of @franciscofranco's kernel built with DoubleTap2Wake and Sweep2Wake from Bricked Kernel merged in.
(By downloading and installing the kernel you assume all responsibility for any damage to your device, but I don't post images with the intention of this occurrence and test them to the best of my abilities.)
Download:
r57
boot image - https://sundergaming.com/downloads/hammerhead/franco.Kernel/boot-franco.Kernel-r57-dt2w.img
md5 - 9ba11b4c3f5cd963c69d54bbfd919fe1
zip - https://sundergaming.com/downloads/hammerhead/franco.Kernel/zips/boot-franco.Kernel-r57-dt2w.zip
*Color tweak is integrated since r30, check 2nd post for information on how to enable.
Want a dedicated build for color tweaks because your boot animation isn't pretty enough? Build it yourself. Sources below.
**Test builds posted throughout the thread.
Kernel is for 4.4.1/2 since r19
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in recovery
Sources
Kernel - https://github.com/PhantomGamers/hammerhead
Ramdisk - https://github.com/PhantomGamers/ramdisk_hammerhead
Credits
@franciscofranco for his kernel - http://forum.xda-developers.com/showthread.php?t=2508284
@show-p1984 for the dt2w and s2w additions - http://forum.xda-developers.com/showthread.php?t=2524557
@flar2 for his on-the-fly color tweak, power key touch to wake suspend, and other general dt2w improvements. - http://forum.xda-developers.com/showthread.php?t=2519607
I do accept and appreciate any donations but I urge you to first donate to the amazing developers listed above for their work because my contributions are minimal and without them this kernel variant would not exist.
Franco's original thread for reference only:
franciscofranco said:
Hi all.
Currently does not work with recent CyanogenMod nightlies or any rom has uses CM sources as a base because they made underlying changes that are now incompatible with Kernels that don't follow their path.
Installation:
fastboot flash boot boot_name_img
or
flash the .zip in the recovery
Changelog:
http://kernels.franco-lnx.net/Nexus5/4.4/appfiles/changelog.xml
franco.Kernel updater Free apk: http://forum.xda-developers.com/showthread.php?t=1867127
Nexus Display Control Free apk: http://forum.xda-developers.com/showthread.php?t=2424467
Got any questions that you couldn't find after searching?
FAQ: http://forum.xda-developers.com/showthread.php?t=2532422
Disclaimer to moderators:
Slight OT is fine, but when users decide to act stupid they should be dealt with with the appropriate means - its really annoying for me when OT turns crazy. Please put the warning/ban hammer anytime any of you think there's lack of respect and/or too much unwanted OT crap - but if it doesn't meet this criteria let the OT posts alone. Thank you.
Cheers!
Click to expand...
Click to collapse
XDA:DevDB Information
franco.Kernel+DT2W/S2W, a Kernel for the Google Nexus 5
Contributors
PhantomGamers, franciscofranco, show-p1984, flar2
Kernel Special Features:
Version Information
Status: Stable
Created 2014-02-06
Last Updated 2014-02-06
Kernel Settings
Disabled by default. To enable execute the code next to terminal in adb shell or terminal emulator as root.
If you wish for it to be automatically enabled on boot you can create the file named in the boot section.
After creating this file you can still execute the terminal code to enable it immediately or you can just reboot and have the kernel enable it for you.
[DT2W/S2W]
S2W
terminal -
Code:
echo 1 > /sys/android_touch/sweep2wake
boot - Create /sdcard/fkSettings/fks2w
DT2W
terminal -
Code:
echo 1 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2w
Bottom Half Screen DT2W (Only allows you to double tap bottom half to turn screen on, instead of above.)
terminal -
Code:
echo 2 > /sys/android_touch/doubletap2wake
boot - Create /sdcard/fkSettings/fkdt2wps
S2Sleep
terminal -
Code:
echo 1 > /sys/android_touch/s2w_s2s
boot - Create /sdcard/fkSettings/fks2s
PWRKEY_SUSPEND (Turns off touch to wake when display is turned off with power button, reenables when turned on, useful for long idle periods, unaffected by sweep to sleep)
terminal -
Code:
echo 1 > /sys/module/qpnp_power_on/parameters/pwrkey_suspend
boot - Create /sdcard/fkSettings/fkpwrks
Touch Wake Timeout
terminal -
Code:
echo 15 > /sys/android_touch/wake_timeout
(15 is an example, include the number of minutes you prefer)
boot - Create /sdcard/fkSettings/fkwt with number of minutes to delay timeout (IE: text file with "15" inside)
[COLOR]
*This tweak is experimental and you use it at your own risk.
**Breaks gamma calibration apps.
terminal -
Code:
echo 1 > /sys/module/mdss_dsi/parameters/color_preset
boot - Create /sdcard/fkSettings/fkcolor
[WIDGETS]
*Thanks to @JsChiSurf
http://forum.xda-developers.com/showthread.php?t=2626476
[App]
*Thanks to @casperpas
http://forum.xda-developers.com/showpost.php?p=51682981&postcount=839
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
kashix said:
just giving my 2 cents, franco's kernel intention is to deliver a stable, optimized and battery efficient kernel for the n5, by baking in these S2W/DT2W features into the kernel, aren't you defeating the purpose? If I would want those features built in, I could have flashed Elementalx, Bricked etc. No offense but that's what occur to me, to others, it may be godsend. :good:
Click to expand...
Click to collapse
Elementalx and Bricked don't have Franco's custom hotplug driver, personally that's the main selling point of his kernel to me.
I don't particularly care for these features anyway though and just used this as a learning experience to build kernels.
(I am currently running this build though to play around with it, haven't noticed a huge difference in battery life myself)
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
This is very tempting to try out.
Thank you!
---------- Post added at 07:57 PM ---------- Previous post was at 07:57 PM ----------
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Flashify seems like it'd do the trick, if original Franco kernels are any indication.
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
durhamite said:
I am used to flashing zips, I guess I am not advanced enough to flash img files. Can I get more detailed instructions on how to flash this?
Click to expand...
Click to collapse
Yeah Flashify seems like your best bet if you're rooted.
I might try and include zip releases in the future, sorry for the inconvenience.
grumphy said:
Well, I tried it, and it works!
Thanks OP!
Tip: if u have FKU, put the img in the franco.kernel_updater bkp folder and restore if it were bkp. Most easy!
Sent from N5
Click to expand...
Click to collapse
Thanks for the confirmation!
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Nastybutler said:
Thanks for doing this. Will you be updateing this to keep up with Franco's releases, or was this a one time experiment?
Click to expand...
Click to collapse
Yeah that's my plan, I'll most likely keep this going until franco includes his own DT2W feature or unless I run into some technically difficulty.
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Nastybutler said:
Welp. I'm having trouble getting the dt2w working. Here's what I'm entering in terminal emulator (after "su" of course) without the quotation marks: "echo 1> /sys/android_touch/doubletap2wake"
Nothing happens in the terminal after I hit enter, it just goes to a new command line, and if I turn the screen off it won't wake back up with a double tap. Did I enter the command in wrong?
Click to expand...
Click to collapse
The space between the 1 and the > is essential.
PhantomGamers said:
The space between the 1 and the > is essential.
Click to expand...
Click to collapse
Eureka! That was my problem. Thanks! Works a treat.
Gonna give this a whirl
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Also so glad you carried over francos screen calibration too! you rule! And so glad you'll be supporting until (if) franco implements it.
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
tyrellcorpnexus said:
edit: works great thanks so much! for subsequent kernels you release, will one have to put in that command every time?
Click to expand...
Click to collapse
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
tyrellcorpnexus said:
Also so glad you carried over francos screen calibration too! you rule!
Click to expand...
Click to collapse
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Yeah it's essentially a straight franco build so anything he implements will be included as long as he pushes it to github
This isn't currently a feature of the kernel but I do agree that doubletap2screenoff and sweep2screenoff would be really neat.
I'm going to TRY to implement this myself but I wouldn't hold my breath because I'm not really experienced with this level of coding.
Click to expand...
Click to collapse
I see I see. Thanks again! Hitting that button one time to go to sleep is better than waking every time as well that is for sure!
I'm used to putting my device to sleep with a gesture on Activator with my JB'en iPhone 5. But I still have to wake it using home or lock button so I guess its still needed on that as well..
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
This is too good
tyrellcorpnexus said:
What are you guys doing to put the device to sleep without hitting that button? I'd like to do without it all together
Click to expand...
Click to collapse
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
---------- Post added at 11:47 AM ---------- Previous post was at 11:40 AM ----------
PhantomGamers said:
Currently you need to do it every time you reboot but you can put a file in /etc/init.d to do it automatically.
Click to expand...
Click to collapse
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Nastybutler said:
I have the LMT Pie controls and one of buttons on my second row is a key that turns the screen off. So now, in theory, I'll hardly ever have to use the power button. :good:
Click to expand...
Click to collapse
Do you have a link to the APK and maybe a screenshot of what it looks like? I'd only be interested in this toggle.
tyrellcorpnexus said:
I don't think double tap to sleep would be the best, what about when getting text to fit the screen on Chrome and such? Double tap is a relatively common gesture once the device is awake.
Click to expand...
Click to collapse
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
tyrellcorpnexus said:
Also, any way you can walk me through how to make sure it automatically kicks in on a reboot?
Click to expand...
Click to collapse
Nastybutler said:
Would you be kind enough to walk noobs like me through how to set up that file? Right now I've got a note saved with the command that I copy & paste into the terminal each time now, but I can tell that's going to get old pretty quick.
Click to expand...
Click to collapse
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
PhantomGamers said:
I meant like the G2 does it, where it's only when you double tap on the notification or nav bar in certain apps etc
Trying to figure this out now, it would appear that the kernel doesn't actually have init.d support as my script isn't working... maybe I'm doing something wrong here.
Click to expand...
Click to collapse
Ah, in that case, that'd be awesome!
No worries, appreciate your work thus far.
This is so great :highfive:
oZoP Development Projects are on the way!!!
ONE ZIP ONE PLACE
System Transition Animations mod
By flashing this zip you will be given a bunch of choices for different system animation style for screen/window transitions, keyboard/toast views and many others. You will get an additional option to tweak a little for unique styles!!
So I give you this, UNIVERSAL for MOST devices Aroma installer to give users the option for different choices!
This zip will work for MOST device running ANY Rom with ANY version Android 5.0+!
How to use the ozop-restore.zip to revert/recovery quickly without the need to restore or reinstall the whole Rom:
And just to be safe, I have included in my scripts and files a method that will create a flashable restore zip of your files before the mods does its thing!
The restore zip will be inside the new "ozop" folder that has been created and the zip is named "ozop-restore.zip"
If something doesn't play nice, just flash the zip and you'll be back to the way it was before you flashed the mod
NOTE: the script will delete any existing restore zips EVERY TIME you flash a new option, meaning that if you flash the mod again, your original system files will be replace with the file you flash previously!
If you want to have a permanent back up of the original file, you will need to rename the zip inside the ozop folder to whatever, just can't have the same name or it gets replaces everything you flash the mod
BUG REPORT:
Code:
MIUI choice causing boot issues for some users (works fine for me), so be prepared to you the restore.zip if needed. Will look into a fix for future releases
Report bug properly to get my support
Of course there are many way to properly report bugs and ALL of these ways have one thing in common, THEY ALL REQUIRE VERY DETAILED NOTES of the issue!
I'm not going to go deep into how detailed you could get because lets face it, most people that report improperly are the ones who don't read and probably are going to read this! HaHaHa...
To get support from me I only ask for some simple things
1. What device, and rom you are running
2. What is the issue (no boot, fc everywhere, fc only certain app etc...)
3. Which option did you select
4. Did you get the install log
5. Did you use the restore.zip option to get back running
6. Do other choices share the same effect
That looks like a lot, but it really is the minimum amount of info need to troubleshoot!
Provide me that and I'll do my best to fix things and make this fun for everyone.
If you post things like
"Doesn't work", "bootloop" or anyone other similar post that have no value and help development is no way, actually these kinds of post only put development behind and slow progress die the fact that anyone who cam help has to waste their time reading it!
If these kind of post ever come up, its best to ignore the lazy person and not clog the thread with flaming replies as that too slows development!
Anyway, I don't expect there to be many if any bugs! Been tested by myself and confirmed with users of this device!
Now grab the download and enjoy!
DOWNLOAD v1.1 HERE
SYSTEM ANIMATIONS PREVIEW PAGE:
Note: the animation have unique motions and some may look better with some minor adjustments to animations speeds. Some are better set to quick speed, others set slow. You will have to decide as per your needs.
You can access these adjustments via developer options in settings (activate if not shown by clicking about device/software version/build number 7 times)
List of the current animation:
COMPLETE SYSTEM ANIMATIONS
"oZoP Custom Missing Link Animations",
"Nexus 7 Ported Animations",
"Blur Animations"
"iOS Animations",
"Flyne OS Animations",
"Stock Animations",
"Google Pixel Animations",
"MIUI Animations"
ANIMATION ADJUSTMENT ADD-ON FOR POP-U AND DIALOG ANIMATIONS
"Bounce Style Dialog Animations",
"Drop In Style Dialog Animations",
"Flip in Flip mix Style Dialog Animations",
"Fold Style Dialog Animations",
"Slide Style Dialog Animations",
DEVICE COMPATIBILITY
Confirmed compatible devices for this version:
LG
OnePlus
Confirmed NOT compatible with the version:
?Samsung
PREVIEWS:
Credits:
spanna for the original vrtheme script
changelog:
v1.1
*added support for OnePlus and possibly more devices..
*cleaned up Aroma code
*added ext sdcard calculation to device info and mount info
v1a
*removed incompatible Samsung styles
*changed text style in Aroma UI
*fixed mounting
*fixed install log recording
v1
*initial release
XDA:DevDB Information
oZoP Development - System Animations, Theme for the OnePlus 3T
Contributors
stangdriver44
Version Information
Status: Stable
Stable Release Date: 2017-07-30
Created 2017-07-30
Last Updated 2017-08-06
Cool mod
Great... All in one place... Missing link is my favourite... Many thanks dev
Missing link animation is great.... Will try more animation on oos 4.1.6
Welcome
@stangdriver44, great to see you here! your amazing work for the Galaxy S6 was the only reason I kept it for as long as I did. Ultimately touchwiz killed me and I switched to the 1+3T.
Miui animation giving bootloop...
Does it provide Miui recent apps horizontal thumbnails style?
Sent from my LG-H870DS using XDA-Developers Legacy app
Does it require root and trwp?
PashaF said:
Does it require root and trwp?
Click to expand...
Click to collapse
Yes
---------- Post added at 08:41 PM ---------- Previous post was at 08:41 PM ----------
EMJI79 said:
Does it provide Miui recent apps horizontal thumbnails style?
Click to expand...
Click to collapse
No
Whoever wish to use this theme first pls make sure that u took a original backup of system animation as said by OP otherwise you can stuck on bootloop. However most of the animation is working on my oos 4.1.6
It broke most of my apps running 7.1.2 resurrection remix CAF version with stock kernel (whatsapp, contacts, playstore, GMS) , i had to revert back using the restore zip and waiting for it to boot up. thanks anyway.
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
stangdriver44 said:
OP updated with the Preview page
SYSTEM ANIMATIONS PREVIEW PAGE:
I am also looking at the MIUI animations that some users are having trouble with.
Hopefully a fix and possibly more animation options coming soon...
Click to expand...
Click to collapse
hope you can make this more modular, i like missing link keyboard animation, and like ios transition
so for now i use missing link + drop down transition
hope more option coming on next release
Missing link and iOS animations worked fine for me on RR . Using missing link right now. Missing link working on my son's nexus 6 running RR as well
Now my smartphone looks much better.
I use the Nexus 7 Style.
Thank you for your work .
Can you add the OxygenOS animations? The fading etc that they add is very nice.
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
lucassilvas1 said:
I can't flash the zip through TWRP, when i try it says that it cannont be installed and it gives me error 255.
Model: Asus Zenfone 2 Z00A
ROM: LineageOS 14.1
I tried mutiple times and also tried moving the zip from the SD to internal storage but it gave me the same error again.
I really hope you can help me because i really want those iOS animations since LOS ones suck.
OBS: This is the only info i can give to you since i can't even see the Aroma GUI, the error happens as soon as i try to flash the zip.
Edit: Through a little research i now think is because me phone is x86 and not arm, would you kindly make it x86 compatible? Please?
Edit 2: Here's the recovery log i copied right after the error appeared: https://pastebin.com/6q1cwdeA (the flashing process starts at line 1022)
Edit 3: Managed to fix the 255 error by replacing the "update binary" file with one compatible with x86 (from lineageOS). But now i get another error, this time error 6, which apparently has something to do with the "updater script" file i think.
Click to expand...
Click to collapse
This mod is made keeping the OnePlus 3T in mind, buddy. You should have expected it to not work on the ASUS Zenfone. Moreover, ARM - x64 v/s Intel - x86 (32 bit). It was bound to fail.
No updates??
Will it work on one plus 3t 5.1 oxygen os
Mod edit: Thread closed on owner's request.
exNoShadez-EAS Kernel
Hey Pixel XL forum. I'm a Pixel/Sailfish owner, who also enjoys hacking on kernel code. I recently released a Kernel in the Google Pixel forum => but we are all using the same kernel, sooo.... I thought after pushing my second stable release, that I should probably post on the XL forum too.
My kernel is a bit different than most kernels available, you will quickly notice. Lots of interesting features and some unique ones too.
FEATURES
- Current LTS release -> Linux-3.18.114
- Energy Aware Scheduling
- Schedutil (default Cpu Governor)
- RCU infrastructure backport (with expert mode enabled)
- Cpu-Boost / Input Boosting (enabled by default)
- BINFMT_MISC support (NOT mounted on boot).
- Kernel Hardening/Protection (CopperheadOS/Grsec/Pax Marlin kernel hardening features)
- leds-qpnp: Notification LED control - V1.1c (Boeffla) - Adapted for Marlin
- Binder_rt = My own re-implementation of AOSP Binder that uses rt_mutexes; supporting priority inheritance
- Improved scheduling/determinism for high priority threads/tasks
- Backported Scheduling, Locking and Workqueue subsystem code from Newer Linux kernels.
- Audio Driver enhancements / backports (from Wahoo/Pixel 2)
- Sound/Audio driver Tweaks (bug fixes, scheduling improvements)
- forced Interrupt threading enabled
- Wifi Mac Address Randomization
- WireGuard (VPN) kernel module support
- KCal Advanced Colour control
- Improved ASLR (in kernel)
- USB Fast Charge
- Wake Gestures
- GCC 6/7+ Fixes
- Built with GCC-8.x-dev
- and more
Contains code from everywhere: Code Aurora, Flar2/Marlin, CopperheadOS, AOSP, Project-EAS, Freak7/Kirisakura, Linaro, Pixel 2 kernel sources, mainline linux and elsewhere. Modifications and backports by me, as well.
BACKGROUND
I wanted a kernel for My Pixel that had 'all of the things', it didn't exist... So I'm working on my own kernel. I try to balance Security/hardening, experimental features with high Performance and battery life. <- not an easy task! ... Some of the security features do come with overhead, but if you use apps that are CPU heavy / processing and/or require low latency - they will perform well (at the cost of chewing some battery life, of course).... Battery life and SOT are very reasonable though.
WARNING / VERY IMPORTANT: This kernel isn't compatible with installing TWRP ~> meaning; you must use the fastboot version of TWRP (used in RAM) , flash the kernel and NOT install TWRP to your system (the kernel is too big for TWRP to co-exist).... This may sound inconvenient, but there are a number of valid reasons to avoid reducing a kernel's size in order to support TWRP installation, in the boot partition.
***Fun facts on not supporting TWRP below => 2nd post: PLEASE READ: to understand my motivation***
TWRP REMOVAL
*To remove TWRP from your system; You need the stock boot.img from your running/current firmware (which is inside of the factory image zips) or use the Nov Stock boot.img provided here. Then it's as simple as flashing the boot.img to wipe TWRP;
fastboot flash boot_a /path/to/boot.img
fastboot flash boot_b /path/to/boot.img
Stock 8.1 July 2018 Boot.img => https://github.com/nine7nine/Apps/raw/master/MarlinStockJulyBoot.img
Now you can proceed with using the TWRP fastboot boot.img to flash my kernel, magisk/supersu or whatever else....
Fastboot twrp boot image => https://dl.twrp.me/marlin/twrp-3.2.2-0-marlin.img
WARNING: This shouldn't need to be said, but we did have someone on the Pixel forum who did this, so I'm adding a sticky/warning here; do NOT EVER re-lock your bootloader after flashing any kind of custom software, kernels, etc to your device - *it will brick your phone*. Meaning you are screwed would need an RMA / replacement device ... everyone in the XDA community should know better, but still; worth mentioning....
IMPORTANT:
Before asking questions; Please read through the thread (starting with the last few pages) - I shouldn't need to be repeatedly answering the same questions over and over again. It's good practice to get into the habit of reading through threads before asking questions in any thread on XDA, as more often then not; you're question has probably been answered. Thanks!
EXNS-EAS KERNEL DOWNLOAD:
JULY 2018 OREO 8.1 RELEASE exNoShades-eas Kernel Flashable zip
https://github.com/nine7nine/Apps/raw/master/exNoShadez_eas_v2.8.2_f94351f.zip
It is stable, high performance and very responsive...
Important: You will need root; I don't support non-rooted devices && some features require it. I recommend using Magisk; https://forum.xda-developers.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589 ...
NOTE: Make sure to flash the latest Magisk beta *before* flashing the kernel zip ...
More Background / Important Notes:
Binder_RT:
My own port and re-implementation of the Binder Kernel Driver; a slightly modified version of The AOSP binder.
Binder_RT uses rt_mutexes as oppsed to mutexes for locking in Binder, ion, ashmem, etc... rt_mutexes support priority inheritance and should improve determinism in Binder, speed up IPC, Ion and Ashmem => Allowing applications that require low-latency, tight deadlines, low jitter and deterministic behaviour to perform better ~ This re-implementation is proving to be the great for those types of applications. The goal here is to help ensure that the Kernel and Binder's high priority && time critical threads and tasks are properly prioritized... Example; audio buffers arriving on time / no buffer underruns... *Further development work is planned to research, experiment with and improve Binder_RT.
rt_mutex documentation, for those interested;
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex.txt
https://github.com/nine7nine/Marlin_exns-eas/blob/EXNS_EAS/Documentation/locking/rt-mutex-design.txt
CPU-Boost / Input Boosting:
Touch inputs boost CPU frequencies (thus improves performance and responsiveness).
# Cpu-boot / Input boost settings
write /sys/module/cpu_boost/parameters/input_boost_enabled 1
write /sys/module/cpu_boost/parameters/input_boost_freq "0:1363200 1:0 2:1900800 3:0"
write /sys/module/cpu_boost/parameters/input_boost_ms 100
IO/ CPU Governors:
This kernel doesn't include a thousand io/cpu governors. IO-wise; CFQ is the default, but we've got a few in there. chose your poison, but know that the majority of my testing is centered around cfq and deadline. CPU Governor-wise the common Linux CPU governors are there; along with Sched and Schedutil....
Stick with Schedutil - on idle, it draws very little power and in most 'peak performance situations, it should do very well..... I'm getting great battery life, sot and performance.
Managing Kernel Settings:
Get EX Kernel Manager - my original code on github was forked from EX kernel, before rebasing it - but EXKM will give you access to 99% of my kernel's settings.
My 8.1 Kernel Sources: https://github.com/nine7nine/Marlin_exns-eas
Donations via PayPal very much appreciated. I do put a significant amount of energy and time into researching, development, testing / QA and also providing support/help to end-users... It's definitely not mandatory to donate; but If you appreciate the effort, see value or benefits from using my kernel on your device and can afford to; Use the "Donate to me" button or the below link... It makes a big difference. thanks!
https://www.paypal.me/jrdnjhnstn
Why TWRP Installations are NOT supported:
CONFIG_CC_OPTIMIZE_FOR_SIZE=y
(and why I'm not using it!)
Most custom/android kernel devs are using the above configuration in kernel compilation, which is arguably very BAD... I understand that boot partitions are small and the desire to install TWRP to them, thus there is a need to reduce the kernel's size....and yes, this will achieve that - However;
1. SUSE, RedHat, etc (Enterprise linux) disable CONFIG_CC_OPTIMIZE_FOR_SIZE -> it's original use case has proven to be invalid. Even Google (in their own documentation) advise against using this; https://source.android.com/devices/tech/perf/boot-times ....
2. It suppresses useful compiler warnings....
3. As SOCs have become more powerful, google has come to the same conclusion that Enterprise Linux did back in 2012.
4. by turning off CONFIG_CC_OPTIMIZE_FOR_SIZE, we achieve better performance, boot time and better cache utilization.
Clark Williams / Redhat Bugzilla said:
* Cause: CONFIG_CC_OPTIMIZE_FOR_SIZE set with assumption that smaller code would yield hot cache lines and good performance
* Consequence: this config caused gcc to generate jump-to-jump code which causes cache line bouncing, hurting performance
* Fix: turn off CONFIG_CC_OPTIMIZE_FOR_SIZE
* Result:slightly larger kernel but better cache utilization
Click to expand...
Click to collapse
(The Above is quoted from Clark Williams, A Senior Software Architect @ RedHat -> https://bugzilla.redhat.com/show_bug.cgi?id=796297)
I know of no other way to significantly reduce kernel size. Disabling some debugging, unneeded features, etc helps - but not enough.... I am focusing on optimization, using newer builds of GCC/Linaro, performance enhancements, fixing compilation errors, etc, etc -> these things are more important than trying to support TWRP installation.
Therefore; I do NOT support installing TWRP....
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
spr33 said:
This sounds incredible. All those features.. and then some. Hard for me to test as I rarely use my PC but I may have to go and give this a try.
Edit: would it be possible to create a build for those who do want to use TWRP? Would be great to do some benchmarks (real work using DiscoMark and synthetic using geekbench/AnTuTu/etc) to see differences between the two.
Click to expand...
Click to collapse
No. like I said. I don't/won't support installing twrp. it would require reverting a bunch of patches/ work that I've already put in... and also not using linaro GCC 7.2.1 compiler, either...
the time invested would be a complete waste for me and I would have maintain another separate branch. test another build, etc, etc'... i'm not doing it. my current goal is to reduce my branches into one single branch/build;. ... which will end up hopefully being binder_rt... not create more.
feature wise, pretty much a 'best of' what any other custom kernel offers for Marlin, all of the hardening stuff (I think I'm the only Marlin kernel on XDA with that), etc... afaict, I'm the only one rolling in EASv1.4, cpu-boost, dynamic stune boost; all of which I've ported myself... some of the audio driver stuff I personally ported (more coming) and binder_rt is my baby; I ported aosp binder and researched / Inplemented all of the changes to Binder...
in my yet-to-be-released binder builds I also have backported a large chunk of the linux locking, workqueues and scheduling code and some other bits from newer mainline linux kernels (which allow me to pull in some new features and use them).
so I'd rather work on this kind of stuff, over caring about twrp, doubling my workload to support running synthetic benchmarks between gcc's -Os vs. -O2 optimization levels...
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
housepabldroid said:
All those features are welcome in this poor Oreo pixel community! thanks for your work..
i'll try it as soon as possible!
Click to expand...
Click to collapse
haha. pixel community isn't too bad. there's just not a lot of custom oreo ROMs.... myself, I wouldn't want to run any of those custom roms anyway. they usually are built without odexing or proper signiture key signing = less secure and way less optimized... Stock ROM is great, just needs root and a few apps to modify / customize it a bit.
for me, the kernel has always been the issue. lol... therefore, roll my own. lol....
ya, for sure give it a try... I honestly would say binder_rt is the best build... the 'stable build' is a bit of a misnomer - all of the builds are stable, just the binder ones are running more experimental code... binder_rt blows the socks off any other Marlin kernel for certain kinds of workloads... I'm aiming fir it to become my default build...
Donric13 said:
Thanks for the new kernel. Sounds very interesting. Can't try it atm because i am on dp1 from 8.1. Hope you gonna also support 8.1 when official sources are out. For me battery life is already great on dp1.
Click to expand...
Click to collapse
yup. I have to wait until kernel sources are released. you got it!. but when they are / 8.1 is released; I will be upgrading to 8.1, so no worries - there will be an 8.1 version...
I've heard heard that battery life is pretty good on 8.1, there's a thread in the pixel forum about it... but by what they were saying, it didn't seem that much better than what I see from my kernel.....
I'm more interested to see what performance improvements are in 8.1 kernel sources... I've found stock kernel to be a bit crappy for some stuff...
well, if at some point you are bored and want to test my kernel on 8.1, go for it. ya never know: maybe it will work. the reason I say that?
IIRC - it was tested with my old kernel / sources build... could've been a bug, not present in the new one.... or something else. IdK.. being as I'm on 8.0 I can't even look into why that might be or have been...
just make sure if u do ever try it, keep the stock boot.IMG for 8.1 around, in case it doesn't work..... and report back, if it does work. lol
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
JS.zip said:
Gotta say super smooth. Thanks for sharing. Maybe it's just a glitch in ex kernel manager but zram "stopping..." Or nothing to worry about.
Click to expand...
Click to collapse
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
nine7nine said:
Ah yes, I should've mentioned that ~ zram is working fine - but EXKM is being denied permission to read those files on the file system - I think it's due to a change in cgroups code (from merging in EASv1.4), but I haven't gotten to the bottom of it yet....
No worries though ~ I HAVE completely verified that zram is working, mounted swapon and behaving as it should... Honestly, the defaults for zram are fine ~ if they ever weren't; you would have bigger problems on your hands, that changing swapping wouldn't help. lol
Which build are you using? (just curious)
Click to expand...
Click to collapse
Thanks that's what I thought. The bad boy "Binder RT" lol
JS.zip said:
Thanks that's what I thought. The bad boy "Binder RT" lol
Click to expand...
Click to collapse
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
nine7nine said:
bad boy eh? haha.
Ya, no worries - I check that sort of stuff, when it crops in... fixing that particular issue just hasn't been a huge priority, over other stuff that I'm working on. (and because I think it's pointless that EXKM even displays it to begin with - it just gives users the false impression that they are tweaking something, that in 99.99999% of cases - is absolutely pointless to touch).
Anyhoo, cool - let me know how things are working out with the binder_rt build, as you get some more use in ~ I really want it to become my main focus / implementation. (I personally won't be going back to using any other build day to day, anyway.)
Click to expand...
Click to collapse
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
AlkaliV2 said:
I just wanted to point out that I grabbed your stock kernel from the OP and had planned to use that to flash my stock image. However, I happened to have the latest boot.img release decompressed on my drive so I compared it to the one I had on hand.
MD5 for your Stock Image: 7A2D92981FDE96E5D60D806019ACFA0C
MD5 for Google's Stock Image: BF9EDA2888C8C6A1FCD0A7DB6E37F739 (Latest November build)
Now I don't want to sound like the suspicious type, because in reality the stock kernel you provided is just to get TWRP off the device before flashing your kernel, but I'm forced to ask why your stock image is not identical with the main stock image? Unless your stock kernel isn't from the latest release but instead from a prior month or something of that nature (It would take me quite awhile to download the other month's releases just to check so I was hoping to ask you instead)
Click to expand...
Click to collapse
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a download/link to me, so I can add it in. thx
nine7nine said:
Easy explanation - I'm on Sailfish, you aren't; so the md5 wouldn't match...
I can do one of two things; you can post a upload/link to your boot.img and I will replace the link for Marlin's nov boot.img (adding it to my github) OR I will remove the link from the post and Marlin users will have to fend for themselves. (have to download 1.8GB firmware themselves for a boot.img... Obviously i'm NOT downloading your guys Nov Firmware images).
nothing suspicious at all here, dude.
EDIT: I've removed the link to the sailfish Nov boot.img, as a sign of good faith; I can replace it with the Marlin Nov boot.img - but that will require you to post a downlink to me, so I can add it in. thx
Click to expand...
Click to collapse
No problem, I download every Marlin release so I'll just update my AFH folder to include the monthly kernel release and users can download it from there. You can either link to my folder or download from it to add to your repository; either one is fine with me Thanks, and I do appreciate what you're doing but I have a 'verify first' stance since these devices are a big part of people's lives. I'm going to give your kernel a spin now, I appreciate you getting back to me so quickly. If only AFH was this fast, I just spent 25 minutes trying to get it to create an empty folder...
Link to Marlin Stock Images: https://www.androidfilehost.com/?w=files&flid=231142
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
AlkaliV2 said:
Edit: I attempted to flash the "exNoShadez_eas-3.18.83_Binder_b0b66e0.zip" from the fastboot installed version of TWRP after flashing the stock boot to slot_a and slot_b, but it is failing with an error that states, "New image larger than boot partition. Aborting..." Then updater process Error 1. Any idea what would cause that?
Click to expand...
Click to collapse
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
nine7nine said:
Hey, I added your nov boot.img to the OP. put it on github to save a few clicks for people.
The error you are seeing would suggest that TWRP is installed to the system. That is the only time anyone has ever bumped into that message. So, I'm not sure what's going on with your end but it would seem you have twrp actually installed...?!
the TWRP that you are supposed to use, is this one;
https://dl.twrp.me/marlin/twrp-3.1.1-1-fastboot-marlin.img
that loads and runs from RAM. twrp can't be "installed from fastboot" ~ it installs to the boot partition; leaving not enough room for the kernel.
Click to expand...
Click to collapse
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
AlkaliV2 said:
Yeah, that actually explains it. I was using a kernel with TWRP installed last go round and now it seems just flashing the factory boot.img is not getting rid of the installed TWRP. I'll figure out how to get TWRP removed for good this time; thank you for letting me know where to look.
Click to expand...
Click to collapse
Yup. TWRP can't be installed along side. Running it from RAM has to be used. ie: I don't support TWRP installations. lol
Flashing the factory boot.img DOES get rid of TWRP for good ~ you just have to make sure to use the TWRP fastboot boot.img for flashing my kernel after (since fastboot/twrp doesn't install to the boot partition)...
I've added a link to the OP to Marlin's twrp fastboot boot.img....
I also updated all of the download links and double-checked to make sure that all of the Marlin zips are packed properly with AnyKernel2 + relabelling every file on my github (by re-packing all of them all... This is mostly just paranoia on my part - but now that I'm supporting 2 devices, best to make sure that nothing gets tangled together.)
@everyone
just a few notes, since you guys are just getting exposure to my kernel, the way I do things; in regards to development, etc.
-> I post test builds (this usually happens when I make big changes.). reports are helpful on these builds.
-> Development happens fast; *I routinely add new features, bug fixes, etc and i'm almost always ahead on LTS updates over the Stock kernel.
examples;
=> lts -3.18.83 build available on the day of release
=> my Binder_rt branch is currently 140+ commits (code changes) ahead of the the other branches.
(changes since in the current downloads/releases)
=> There are a number of bug fixes, a few added features (mostly in-kernel stuff), some optimizations *and* there are massive upgrades to parts of the kernel's subsystems. (100+ commits are related to that)...
(changes since the current downloads/releases)
NOTE: The binder Branch (non-rt) will see the majority of the above changes code, but the Stable branch will only see a subset of these commits + bug fixes.
I probably won't roll out a test build for Binder_rt builds, until I've had the newest code running for a couple of days.... At that point, once things have proven to be stable good ~ i'll roll out a test build for anyone who wants to help out and dogfood test builds....
Then, I will push back changes back into the Binder builds, Stable, etc... I usually try and line up actual releases to LTS and/or => more importantly monthly android security / firmware updates....
**So the gist is; there will be frequent updates. Update as you see fit - anyone who wants to help out - run test builds and report back issues.
So pending a detail or two, I likely will be phasing out my other builds in favor of the Binder_rt build.
- I've had quite a lot of feedback via the Pixel forum, PMs and email (and a couple of friends using it too).
- The Binder_rt build seems to be very stable for everyone.... not too mention just all around better.
- there seem to be no drawbacks and quite a few benefits to that build over the others.
The one thing I'm waiting on is; I've joined the Android Kernel Developers Google Group and am currently waiting to see if I can't get some help with porting a missing Kernel function into Marlin's sources ~ this particular kernel function is what's stopping me from having Binder be sync'd with the AOSP binder implementation.... I'm hoping to resolve this sooner than later, at which point I will be able to merge in those commits (and test them).
In the meantime I'm working on a few backports to the audio driver and a few other bits (taken from Wahoo/Pixel 2 kernel sources). I've also pulled in a few fixes to binder from Wahoo, as well....
So I might post a test build for Binder_rt tomorrow - as it's accumulated a number of changes, bug fixes, etc.... I'm not sure If I will have any resolution to the missing kernel function - but that doesn't affect pushing a test build....