Related
DroniX 0.6 The RUN
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FACEBOOK OFFICIAL PAGE
TWITTER
The ROM DroniX it’s a particular ROM created only for this particular device.
The graphical interface is structured for the performance,it’s useful and fluid. There are no more app installed by default, we found the original Google app and some app of a particular interest.
TEAM:
Stefano Viola aka estebanSannin (founder)
Ivan Morgillo aka hamen
Antonio Gisondi aka Harlem88
In the last version that i call "hybrid" more parts are been rewritten for setting up a new and innovative base.
In this ROM you can find pieces from U8160 port, pieces from DroniX 0.4 and new pieces compiled from source code.
Let’s have a look at the new characteristics of this version:
Optimized Launcher for a better fluidity.
New DroniX Extended Menu:
It’s one of the new things introduced in this ROM. It’s been developed with the purpose of provide new important functions.
One of most important function it the "Theme Switcher" or the new "Power Management".
Here’re some screens:
Power Management
This is one of the most important news.
It permits the managing of the freqs according to the screen state.
Configuration is very simple, and it allows you to set freqs and governor to active when display is on and when the display is off. You can also enable "Data Feature" which permits to disable data when display is off, and enable it again when display is on.
Kernel USB HOST
Simply choose from the menu in Settings---> DroniX then reboot the device.
For using the kernel usb host you have to build a powered cable otherwise the device will not be recognized.
This is the schema of the cable:
There is the possibility of interconnection with USB Storage, which is hdd, keyboard,mouse, ethernet usb adapters,Universal USB converters an example is the arduino support.
This is a video that explain the use of the functionality USB-HOST:
http://www.youtube.com/watch?v=4o9TPQxEXQs
WARNING
If you enable USB HOST mode you’ll lose gadget mode, so you can’t mount your ideos as media storage. Also ADB will not work.
Here are the list of specific fetures:
Code:
- New Theme
- Kernel with patch 2.6.35 of qualcomm
- MAX Underclock 30mhz
- MAX Overclock 748mhz
- Default kernel clock max 600mhz
- ext4 support
- ext3 support
- CIFS support
- NFS client and NFS Server support
- Added Governor: Conservative, Smartass, MinMax
- Custom Conservative governor
- ADB Rooted
- Rooted phone
- Deodex application and framework
- ZipAlign
- Fix shell adb in a standard GNU/Linux
- Enabled /etc/init.d standard GNU/Linux
- SSH Client
- SCP
- tcpdump
- nmap
- ncat
- sqlite3
- Kernel UnderClock/Overclock + Turbo Mode
- Set LauncherPro last version to default launcher
- mini_httpd
- dropbear
- bash 4.2
- bc
- DroniX Web Manager
- ssh-on
- ssh-off
- interprete ruby
- Input utility
- zip
- mountro
- mountrw
- frkrw
- htpasswd
- new Bootanimation
- change the default splashscreen with DroniX Logo
- Multitouch (thanks tj_style) on Synaptic LCD
- added new Frequncies for OverClock CPU
- fix icon framework
Useful link for install a debian distro on ideos: http://www.myppc.it/web/community/viewtopic.php?f=125&t=5460
Installation Tutorial:
DroniX, for optimizing free space for applications, use /cust partition (present in lots of other ROMs).
If in the past you have installed a stock ROM without /cust partition phone will probably stuck on an infinite loop during the bootanimation.
For a correct installation you should flash before a stock WIND rom:
LINK
than re-flash the modded recovery and go on with the standard installation (wipe and flash)
For the installation of the DroniX we use any recovery and make the wipe.
I recommend the ClockWorkMod: LINK
As you may have noticed some feature and utility in low level are added.GNU/Linux Users are happy for this decision.
A particular utility is the SSH client used for the connection tunnels to a remote Server,
In particolare, c'e' SSH client che puo' essere utile per creare dei tunnel di connessione verso server Remoti, some people understands what I'm saying
SHELL
The Dronix Shell is complitly different from the other ROM. Is very close to the standard of the Linux systems. The use is simple, you just enter with:
Code:
adb shell
or enabling ssh from DEM,abilitando ssh da DEM and once inside, type:
Code:
bash
in this way we have a standard shell with all path arranged just like a normal Linux system.
Here a screenShoot:
DroniX Web Manager:
The Web Manager setup is very simple:
- Connect your ideos to your wifi network.
- Go to Settings-->DroniX and tick ON in the “Web Server” option.
- Write the IP address that shows you the DEM.
Warning: Web Manager won’t work with Internet Explorer, but it has no problems with any other Web Browser.
Another very important option is the underclock, that allows you to save battery.
If you want set-up advanced settings of the freqs i suggest you to install SetCPU utility or something similar.
In case of problem with this ROM you can use the forum for bug reporting, or, if you want to help with the developing you can connect to the IRC chat (you’ll probably find only italian people):
Server: AzzurraNet
Channel: #hacklabproject
ROM VERSION:
DroniX 0.6 The RUN
MIRROR --- ROM DroniX 0.6 The RUN - Mediafire
Thanks:
- hamen
- harlem88
- VanniX (logo and other minor graphical things)
- tj_style
- myppc.it
- paolinosix86
- Master94ga
- LeoDeos (ICS theme included into the ROM)
- ShAdOwNeT (English Traslation)
and all the other developer that i can’t remember the name and the nick(forgive me)
If you like the ROM a FREE donation it’s possible(I will invest the money for new devices and porting the DroniX) Sostieni DroniX
The project 'ambitious and we want to aim high ;-)
Great to hear DroniX 0.6 for u8150/c8150 formal announcement, I will test it and feedback to you soon!
Is this Android 2.37 (gingerbread)ROM ?
Did you fix the "brightness could not adjust" and "booting black image" bugs in DroniX 0.6 raw version ?
dronix 0.6 ginger
i hope some bugs/problems (e.g. when you press the menu button in lockscreen, it will unlock, and the phone will lock when you press the end call button) would be fixed. its a great rom, just needs some polishing. thanks
another problem is the battery life, almost life a timer (really). seems like 5minutes or so, the battery will drop by 1-2%
jackson0829 said:
Great to hear DroniX 0.6 for u8150/c8150 formal announcement, I will test it and feedback to you soon!
Is this Android 2.37 (gingerbread)ROM ?
Did you fix the "brightness could not adjust" and "booting black image" bugs in DroniX 0.6 raw version ?
Click to expand...
Click to collapse
you may download "brightness level" (it has a widget) in play store to adjust the brightness
After installation DroniX 0.6 in V8150 , I reconfirmed which is Android 2.2.2 version.
I am confusion why previous DroniX 0.6 raw version already upgrade to Android 2.3.7
but DroniX 0.6 formal release change back to Android 2.2.2 ??
Do you have plan to formal release Android 2.3.7 of DroniX ROM??
The 2.3.7 DroniX based is under working, Because the kernel is differente drom 2.2.2 version and some function content in a new DroniX Extended Menu not working well..
dronix 0.6
Been running (dronix 0.6 the run) for about 4 days now, everything I use is working well and seems nice and quick to do anything I ask of it.
Thank you Esteban for this great rom.
please help me
it reboots everytime i connect it to usb. how to fix it?
representing Nairobi Kenya
Esteban Sannin said:
DroniX 0.6 The RUN
FACEBOOK OFFICIAL PAGE
TWITTER
The ROM DroniX it’s a particular ROM created only for this particular device.
The graphical interface is structured for the performance,it’s useful and fluid. There are no more app installed by default, we found the original Google app and some app of a particular interest.
TEAM:
Stefano Viola aka estebanSannin (founder)
Ivan Morgillo aka hamen
Antonio Gisondi aka Harlem88
In the last version that i call "hybrid" more parts are been rewritten for setting up a new and innovative base.
In this ROM you can find pieces from U8160 port, pieces from DroniX 0.4 and new pieces compiled from source code.
Let’s have a look at the new characteristics of this version:
Optimized Launcher for a better fluidity.
New DroniX Extended Menu:
It’s one of the new things introduced in this ROM. It’s been developed with the purpose of provide new important functions.
One of most important function it the "Theme Switcher" or the new "Power Management".
Here’re some screens:
Power Management
This is one of the most important news.
It permits the managing of the freqs according to the screen state.
Configuration is very simple, and it allows you to set freqs and governor to active when display is on and when the display is off. You can also enable "Data Feature" which permits to disable data when display is off, and enable it again when display is on.
Kernel USB HOST
Simply choose from the menu in Settings---> DroniX then reboot the device.
For using the kernel usb host you have to build a powered cable otherwise the device will not be recognized.
This is the schema of the cable:
There is the possibility of interconnection with USB Storage, which is hdd, keyboard,mouse, ethernet usb adapters,Universal USB converters an example is the arduino support.
This is a video that explain the use of the functionality USB-HOST:
http://www.youtube.com/watch?v=4o9TPQxEXQs
WARNING
If you enable USB HOST mode you’ll lose gadget mode, so you can’t mount your ideos as media storage. Also ADB will not work.
Here are the list of specific fetures:
Code:
- New Theme
- Kernel with patch 2.6.35 of qualcomm
- MAX Underclock 30mhz
- MAX Overclock 748mhz
- Default kernel clock max 600mhz
- ext4 support
- ext3 support
- CIFS support
- NFS client and NFS Server support
- Added Governor: Conservative, Smartass, MinMax
- Custom Conservative governor
- ADB Rooted
- Rooted phone
- Deodex application and framework
- ZipAlign
- Fix shell adb in a standard GNU/Linux
- Enabled /etc/init.d standard GNU/Linux
- SSH Client
- SCP
- tcpdump
- nmap
- ncat
- sqlite3
- Kernel UnderClock/Overclock + Turbo Mode
- Set LauncherPro last version to default launcher
- mini_httpd
- dropbear
- bash 4.2
- bc
- DroniX Web Manager
- ssh-on
- ssh-off
- interprete ruby
- Input utility
- zip
- mountro
- mountrw
- frkrw
- htpasswd
- new Bootanimation
- change the default splashscreen with DroniX Logo
- Multitouch (thanks tj_style) on Synaptic LCD
- added new Frequncies for OverClock CPU
- fix icon framework
Useful link for install a debian distro on ideos: http://www.myppc.it/web/community/viewtopic.php?f=125&t=5460
Installation Tutorial:
DroniX, for optimizing free space for applications, use /cust partition (present in lots of other ROMs).
If in the past you have installed a stock ROM without /cust partition phone will probably stuck on an infinite loop during the bootanimation.
For a correct installation you should flash before a stock WIND rom:
LINK
than re-flash the modded recovery and go on with the standard installation (wipe and flash)
For the installation of the DroniX we use any recovery and make the wipe.
I recommend the ClockWorkMod: LINK
As you may have noticed some feature and utility in low level are added.GNU/Linux Users are happy for this decision.
A particular utility is the SSH client used for the connection tunnels to a remote Server,
In particolare, c'e' SSH client che puo' essere utile per creare dei tunnel di connessione verso server Remoti, some people understands what I'm saying
SHELL
The Dronix Shell is complitly different from the other ROM. Is very close to the standard of the Linux systems. The use is simple, you just enter with:
Code:
adb shell
or enabling ssh from DEM,abilitando ssh da DEM and once inside, type:
Code:
bash
in this way we have a standard shell with all path arranged just like a normal Linux system.
Here a screenShoot:
DroniX Web Manager:
The Web Manager setup is very simple:
- Connect your ideos to your wifi network.
- Go to Settings-->DroniX and tick ON in the “Web Server” option.
- Write the IP address that shows you the DEM.
Warning: Web Manager won’t work with Internet Explorer, but it has no problems with any other Web Browser.
Another very important option is the underclock, that allows you to save battery.
If you want set-up advanced settings of the freqs i suggest you to install SetCPU utility or something similar.
In case of problem with this ROM you can use the forum for bug reporting, or, if you want to help with the developing you can connect to the IRC chat (you’ll probably find only italian people):
Server: AzzurraNet
Channel: #hacklabproject
ROM VERSION:
DroniX 0.6 The RUN
MIRROR --- ROM DroniX 0.6 The RUN - Mediafire
Thanks:
- hamen
- harlem88
- VanniX (logo and other minor graphical things)
- tj_style
- myppc.it
- paolinosix86
- Master94ga
- LeoDeos (ICS theme included into the ROM)
- ShAdOwNeT (English Traslation)
and all the other developer that i can’t remember the name and the nick(forgive me)
If you like the ROM a FREE donation it’s possible(I will invest the money for new devices and porting the DroniX) Sostieni DroniX
The project 'ambitious and we want to aim high ;-)
Click to expand...
Click to collapse
this **** is amazing, i love it, usb host working beautifully
The USB-HOST is the best feature of this ROM..
with usb-host you can plug any device ;-)
remove
How do I flash Wind ROM
I've been searching everywhere, and I can't figure out how to flash the .rar or .zip files for stock. I've put the dload/update.app in the sdcard, and went to the update screen, but all it said was update failed, and i tried putting the update.app in the main dir, but still failed, tried flashing the zip, but "Installation abort". How exactly do I flash a stock rom.
this is a great rom ! But battery drain faster if i compare this with 0.5.4 dronix. Which settings can i use on power management ? Is there somebody reach best options ?
To The Great Makers
After Using 5 Hours.
I will give this this Rom 8.2 out of 10
:good::good::good:
1.The usbHost is the main new feature as You say.
2.Thanks For The Colorful Setting Menu
3.Really Fast Rom.
4.nearly all features working like a charm.
5.new Theme switcher
6.......11........................
:crying::crying::crying:
1.First of all it is really battery draining.
2.Secondly its Android 2.2.2 .
3.no File Manager Included
4....5..
Overall Looks Like an Advance Version Of Ideos U8150 Default Rom.
Thanks Again
boot loop!!
Thank Esteban first. this is the faster rom i try.
i flash the rom from 0.5.4 fast, but got boot loop,how come? :crying:
anyway, thanks you hard work again.
someone please help me and tell me how i can partition the SD card, i have tried installing the rom but i never get out of the boot loop...thanks
nairobery said:
someone please help me and tell me how i can partition the SD card, i have tried installing the rom but i never get out of the boot loop...thanks
Click to expand...
Click to collapse
Partition the SD card by "MiniTool Partition Wizard Home Edition" from PC :victory::
http://download.cnet.com/MiniTool-Partition-Wizard-Home-Edition/3000-2094_4-10962200.html
XScizzor
How To Flash a Stock Rom Forcefully
Force Download ( Recommendation : When the OS of handsets could not start up successfully)
1:Copy dload to SD card
2:Switch off the handset ,then press "Volume Control Upper Key +End Key+ Power Key"
3:Showing successful
4:Remove battery one second ,then power on ,waiting till the os start up
Hope This Will Solve your Problem
XScizzor said:
I've been searching everywhere, and I can't figure out how to flash the .rar or .zip files for stock. I've put the dload/update.app in the sdcard, and went to the update screen, but all it said was update failed, and i tried putting the update.app in the main dir, but still failed, tried flashing the zip, but "Installation abort". How exactly do I flash a stock rom.
Click to expand...
Click to collapse
1. copy folder "dload" to the root of the SD card,
2. press RED button + Volume UP, then power on the phone,
that's all. :laugh:
The fast version is available on the site: http://www.dronix.org/blog/
In download
XScizzor said:
I've been searching everywhere, and I can't figure out how to flash the .rar or .zip files for stock. I've put the dload/update.app in the sdcard, and went to the update screen, but all it said was update failed, and i tried putting the update.app in the main dir, but still failed, tried flashing the zip, but "Installation abort". How exactly do I flash a stock rom.
Click to expand...
Click to collapse
here's a guide: http://forum.xda-developers.com/showthread.php?t=1011527
osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc.
General Information
In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller scripts and zips I've created that I don't think merit their own separate threads. This is partially for my own sanity and will hopefully make it easier for others to find some things as well. A lot of the stuff here was developed with the GN, N4, N5, N7s or N5X, OP5/T, OP6/T, OP7Pro/T, OP8Pro/T or OP9Pro (my devices) and Windows in mind, but could generally be applicable to most devices either out-of-the-box or with some slight modification. If you see something that inspires you, go ahead and mod it, just let me know and give me some credit somewhere. If anyone would like to know the specifics of what's in a particular script that I haven't already linked to more information on, just let me know and I'll post that in here as well.
Note: Older zips with a "cwm-" prefix are NOT only for the now-defunct ClockworkMod Recovery, the prefix was used to denote a flashable zip before I adopted Chainfire's "UPDATE-" prefix. Please use a currently maintained recovery, like TWRP, for all zips to ensure the best compatibility/results.
My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!
Misc./Batch Tools
AnyKernel3 (many devices) - link
AnyKernel was a simple template for an update.zip that could apply any kernel to any ROM, regardless of ramdisk to reduce the chance of any issues arising from the custom kernel pairing. The drawback to this is that some kernels require modifications to the ramdisk to enable/set up kernel features, and in the old AnyKernel format there was no way to do this. AnyKernel3 pushes the format even further by allowing kernel developers to modify the underlying ramdisk for kernel feature support easily using a number of included command methods along with properties and variables to customize the install experience.
APK-Patcher (many devices) - link
A proof-of-concept, simplifies APK modification to make it easier for modification creators to keep creating. Using JesusFreke's brilliant bak/smali and iBotPeaches' excellent apktool, modified to run on-device along with the various binaries required, allows on-the-fly APK modifications to be applied via recovery, to whatever ROM APK is present, taking the constant update burden off of the modification creator. The zip is smart and automated, using the APK name to run all the various parts involved for complicated patches and is extensible to any number of APKs in a single zip.
Android Image Kitchen (many devices) - link
A collection of Windows/Android ports of the necessary Linux utilities for Android image (kernel+recovery) mod work, and my own automation script to unpack, edit and repack the ramdisk. Other guides/scripts exist but none of them are universal for target device, compression and/or developed for Windows/Android. Now also Linux builds to bring my improved featureset back to where it came from, recently extended to macOS as well. Has been extremely useful for me in my messing around with kernel ramdisks.
ADB Screenshot (many devices) - attached
Take screenshots while in recovery. Useful for development of recovery apps or error reporting. Original method had lots of different threads around with the general method for various devices but I figured out a couple tricks required for getting it working on the Galaxy Nexus and then automated the process. Tested and confirmed working with both pixel formats of CWM and TWRP. More information in this GN Q&A FFmpeg thread. New method uses fb2png and should work on all ARM devices.
ADBsync sdcard Backup (many devices) - attached
Backs up the entire sdcard so that you can have a complete snapshot of your device when you make periodic backups, and be able to restore things exactly as they were. Automates the sync process of Renate NST's great adbsync utility which makes only newer files get pulled, significantly decreasing backup time for the sdcard compared to "adb pull". Original version posted in the old adbsync thread. Defaults for devices with /data/media/ internal sdcards (Nexus devices, etc.), but is easily customizable to backup other mountpoints or backup via ADB over WiFI.
Flashable Script Zips
TWRP A/B Retention Module script (many devices) - link
We need an interoperable root ecosystem again. A/B and system-as-root were a big setback to the root community in this respect. To help alleviate this issue, this atypical Magisk script zip "module" will keep TWRP installed to both slots when flashed from Magisk Manager after an A/B OTA has installed in the background, but before you use Manager to install Magisk to inactive slot.
Nexus BootUnlocker script (GN, N4, N5, N7 '13, N10) - attached
I don't know about everyone else but sometimes I find I've rebooted into the bootloader only to realize I've forgotten to unlock it in segv11's excellent BootUnlocker App beforehand. Well, I decided to make a BootUnlocker Script for my Galaxy Nexus so I could just boot to recovery quickly, unlock, then adb reboot-bootloader (or use my Reboot To Bootloader script below) to get back without having to fully boot the OS to make the change. Also extremely useful in the case you aren't able to boot. As with the app there is no data loss like there would be with fastboot, allowing you to relock for safety. Originally posted in the GN EDIFY Scripting thread. Modified for the newer Nexus devices and combined into a single Nexus BootUnlocker zip with tamperbit reset support added using information from the BootUnlocker App Dev thread. For newer devices using Factory Reset Protection (N6 and later), the BootUnlocker Script can't directly toggle the lockstate due to new security tokens, but it does now toggle the ability to use "fastboot oem unlock" without needing a booted device.
N7 BootUnlocker script (N7 '12) [creation guide] - link
The Nexus 7 2012 is a special case. Per-device encryption of an entire partition makes it impossible to support the N7 '12 in a simple root app, or flashable zip as above, however using my guide and included script you can now create a working BootUnlocker Script Zip for your specific device. As with the above scripts there is no data loss like there would be with fastboot, allowing you to relock for safety.
sdcard Fix Permissions script (many devices) - attached
A little flashable zip script to fix ownership and permissions of files and directories on the sdcard to what they would be if Android OS had put them there itself, since some apps can't access pushed files that have root.root as owner/group. This is useful when restoring to your sdcard backup, as with my ADBsync sdcard Backup batch script above, since generally, pushed files get root.root from adb shell and higher permissions than usual. Also a solution for a bug where sdcard files get lower permissions somehow, resulting in similar access problems. Currently written for devices with /data/media/ internal sdcards (Nexus devices, etc.), but could easily be modified for other mountpoints. No longer required on Oreo since it fixes these itself at boot.
Recovery SLAM script (many devices) - link
Recovery "Simple Legacy Auto-Mount" (SLAM!) is for devices that have been updated to SAR, but there are older zips that break in TWRP because they rely on the mounts occuring a certain way, especially during a ROM OTA. Recovery SLAM mounts them more as the zips would expect, generally allowing them to proceed. Most useful for premounting /system before a legacy zip with my FlashAfterUpdate addon.d script.
SUmount script (many devices) - attached
Another tool for the toolkit of anyone using Chainfire's SuperSU or topjohnwu's Magisk systemless root, this simple flashable zip script toggles the mounting of the su.img, magisk.img and magisk_merge.img while in recovery to allow easier access to the /su, /magisk and /magisk_merge filesystems, simplifying manipulating it via ADB shell, AROMA Filemanager or TWRP's terminal/file manager. Especially useful to anyone who uses su.d/post-fs-data.d scripts or can't boot due to some issue with a user addition in /su/su.d, /su/bin or a Magisk module.
unSU script (many devices) - link
While experimenting with Chainfire's brilliant SuperSU systemless root, I discovered that uninstalling the older style system-modifying root through his app (<2.60) didn't restore all of the modified system files correctly, so I wrote this script to do so and aid in people wanting to unroot from recovery. Expanded to support uninstallation of Koush's SuperUser, phh's Superuser, SuperSU Systemless (su.img and BINDSBIN), Magisk, LineageOS addonsu and custom ROM su binaries.
Adreno Systemless Installer script (N5, N6, N7 '13) - link
For use with Qualcomm's official updated preview GPU drivers packages for Adreno 3xx/4xx-powered Nexus stock images. This is a different frontend to take whatever device zip from Qualcomm is in the same directory as it (also searching /sdcard), then unpack and install it as a Magisk module or into the SuperSU systemless root /su filesystem, instead of the usual /system.
Kernel MultiROM Injector script (many devices) - attached
Intended for use in Chainfire's excellent FlashFire app to automate re-injecting the current boot image ramdisk with Tasssadar's brilliant MultiROM's trampoline bootmenu; this avoids having to do this as an extra step in MR-TWRP following an OTA, ROM Delta or SuperSU update. Should work for all EMMC devices with MultiROM installed.
GN PIT Editor script (GN) - link
Dumps and alters the Galaxy Nexus' Partition Information Table (PIT) to reclaim unneeded space from the /cache partition and add it to /system to allow for larger ROMs and GApps packages to make continued support for Lollipop+ easier. The resulting file is byte-for-byte identical to those created by external tools like PIT Magic, so that it may be flashed back to the device in Odin Mode to complete the repartitioning.
Kernel Emergency Reset script (many devices) - link
Basically a go-to cure-all for custom kernel users experiencing issues after an upgrade due to old settings left over in a kernel control app (eg. franco.Kernel updater, Trickster, etc.), or problematic init.d/userinit.d scripts. It's also useful if you just want to make sure you're running clean defaults without conflicts.
Reboot To Bootloader script (all devices) - attached
Those who preferred using CWM may have noticed a couple of things missing that the other popular custom recovery, TWRP, has built-in. One of these is a file explorer/manager, which is answered by amarullz' brilliant AROMA Filemanager. Another thing I found myself wanting was a way to reboot back to the bootloader once I'm in recovery, so I created this very very simple flashable zip script. (No longer required on CWM >=6.0.3.5). Note: Once in the bootloader, "Start" will boot you back to recovery. Not sure why, but it's not a big deal, just reboot normally from recovery at that point.
Flashable Installer Zips
Flashlt Installer (many devices) - attached
Installs my Flashlt script to allow easy flash and dump of boot, recovery and radio/modem (possibly others) EMMC or MTD partitions while booted, and trimming of null characters from files. Also installs a script zip that makes flashing boot.img (kernel), recovery.img, and radio.img/modem.img (baseband) files via recovery simple. It aims to save the average user the hassle of repacking their own image zip, or using the command-line or fastboot to flash it. Place an appropriately named file in the same directory as the zip and flash away! Should work on all devices with normal partition naming ("boot", "recovery" and "radio" or "modem") which accept Android standards-compliant images (including a/b slot devices like Pixel). Extremely handy when used with amarullz' brilliant AROMA Filemanager, and/or my Android Image Kitchen: Mobile Edition (linked above).
Busybox Installer (all devices) - attached
A byproduct of building my own static busybox compiles in all Android architectures for my AIK-mobile package, I figured I might as well offer them up separately as well since there weren't any providers making Android x64 builds when I was researching. Detects device (ARM/64, x86/_64, MIPS/64) to install the busybox binary, cleans up symlinks from any previous install and generates new ones. Detects and supports SuperSU/Magisk systemless installs. Please read the release post about applet inclusion and special features.
nano Terminal Editor Installer (many devices) - attached
An installer to push my own static Android ARM build of the nano editor and required files to /system/xbin and /system/etc/terminfo, with a wrapper adding a --term option to try terminfo profiles more easily. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted. When flashed in recovery also allows temporary recovery use by pushing a script to /sbin/nano with the required setup, so you can trigger it from adb shell or TWRP Terminal. Makes it extremely easy and worry-free to tweak and mod on the go, knowing you can edit the faulty build.prop or startup script if something goes wrong.
adb + fastboot Installer (many devices) - attached
Marshmallow removed adb from the /system/bin directory. For those wanting this functionality back, here's an installer to push static compiles of adb and fastboot to /system/xbin, with a wrapper to point adb to the correct HOME directory and set TMPDIR for compatibility. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
Nexus Media Installer (many devices) - attached
Custom ROMs usually don't include Google ringtones/notifications/system sounds and bootanimation, instead including numerous terrible sounds and often less-than-desirable visuals. This installs the media from old Nexus devices systemlessly (SuperSU and Magisk supported), or to system with an addon.d script to survive a ROM update or dirty flash, and using the zip name (also reading from /data/.nexusmedia) to allow user choice.
mtd-utils Installer (many devices) - attached
mtd-utils (flash_erase, nanddump, nandwrite) are necessary for mod work on a number of Android devices using mtd/char devices instead of the more standard emmc/block devices, and where the busybox versions have been less reliable in the past (especially where it doesn't include flash_erase), using the official suite is preferable. The older ARM builds available on XDA were about a decade old, so I worked out how to configure and cross-compile from the latest source. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted
ZipSigner + Zip Installer (many devices) - attached
Signing zips and APKs on-device has always been a tricky proposition due to memory requirements of the old SignApk.jar, running a jar on an Android device, and other complications for script-based zips. Android has always been missing a zip binary (for unzip see my Busybox Installer). ZipAlign is also handy if you do APK work. To remedy this once and for all, here's an installer to push my dexed version of topjohnwu's brilliant zipsigner.jar and static ARM compiles of zip and zipalign to /system/xbin, with a wrapper to run zipsigner with Android's dalvikvm. Detects and supports SuperSU/Magisk systemless installs. Can then be used from Terminal while booted.
odex Script Installer (all devices) - attached
Based on the great work and binaries from this thread, a simple installer to push my odex script along with the required dexopt-wrapper and zip binaries to /system/xbin and set the appropriate permissions. Automates the procedure to odex any apk or jar from the commandline to potentially improve performance. Dalvik runtime (KitKat and below) only. Also uses cut from busybox.
N5X/6P BLOD Workaround Injector (N5X, N6P) - link
When, unfortunately, my Nexus 5X was recently stricken with the abominable Bootloop of Death, I looked into the well-publicized workaround and turns out it was all contained in the ramdisk and cmdline of a Android image. This is the perfect application of AnyKernel2, so I made an AK2 add-on zip to patch both the current boot and recovery partitions with all the current workarounds to help others afflicted by this issue to hopefully regain their data/device as easily as possible. Linked is the Nexus 5X thread, the Nexus 6P thread may be found here.
N7'13 TWRP flo2flox Injector (N7 '13) - link
The Nexus 7 2013 (flo) has seen a bit of a resurgence with official Lineage 18.1 support repartitioned as "flox". Since official TWRP is still automatically being built only for flo and this isn't compatible with flox, and the minor changes required for flox support were a great application of AnyKernel3, this zip automates the patching process so making official TWRP from flo2flox is easy for all going forward.
GN Synapse Support Injector (GN) - link
This AK2 kernel add-on for the Galaxy Nexus injects support for the Synapse tweaking app into the current boot partition ramdisk, including all the Synapse interfaces for the GN I've maintained since the Franco Kernel and DirtyV Kernel days.
GN Recovery Color Correction Injector (GN) - link
The aging screen on the Galaxy Nexus was looking pretty rough in recovery until I discovered the recently added new OMAP kernel color correction was also present in the most recent TWRP recovery versions. So this add-on zip uses AK2 to patch the current recovery partition ramdisk to add the command to reduce that green/yellow SAMOLED nastiness.
Kernel init.d Support Injector (many devices) - attached
An experimental proof-of-concept. Following from great ideas by Captain_Throwback in my AnyKernel2 thread and using script from my Flashlt script above, this AK2 zip will inject basic init.d bootscript support into any kernel ramdisk on any emmc device with normal partition naming and using the Android bootable image standard, without having to bloat a ramdisk using a busybox binary. This zip is also signed, so could potentially be used with non-Nexus stock recovery on a locked bootloader.
CMSetup Fix for GApps Installer (many devices) - attached
Installs a su.d script fix to work around the CyanogenMod/LineageOS 13 ROM issue of a broken Quick Settings pull-down when CMSetupWizard is removed as part of a GApps installation. Removing CMSetupWizard is useful because it allows Google's SetupWizard to grant apps default permissions, so the workaround automatically executes the only required command at the appropriate time following first boot. Requires a SuperSU/Magisk installation (for su.d/post-fs-data.d support). Flash after the SuperSU/Magisk zip and your GApps.
Dev Team init.d Pack Installer (all devices) [see "950iosettings, etc." below] - link
A simple installer I wrote to create the /system/etc/init.d/ directory, extract the latest init.d scripts as published by the "Franco's Dev Team" tuning collective (of which I was a member), then set correct owner, group and permissions to the entire init.d directory. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask.
Scripts
950iosettings + 875mntsettings + 925vmsettings + 975experimental init.d scripts (all devices) [with Franco's Dev Team] - links
Also available bundled in an installer. The scheduler tunables have already gained a bit of attention/adoption on various devices and kernels, but this is the init.d script I wrote to set the new custom scheduler tunables values as "default" by an independent loop, sleeping in the background and detecting each time the scheduler is changed. There is no effect on idle drain or deep sleep. The settings included are the complete work of the "Franco's Dev Team" (or "Team Franco") tuning collective, of which I was a member. We strove to perfect the scheduler, vm and various other settings for the smoothest and fastest experience available. The collective was: malaroth, osm0sis, joaquinf, The Gingerbread Man, pkgnex, Khrushy, shreddintyres. If you are a developer and would like to include these tunables/scripts in your kernel or ROM please provide credit. A lot of time and effort has gone into this project and that's all we ask. Lollipop(+) updated versions now also available through the continued excellent work of pkgnex.
999-flashafterupdate.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs that don't have "Flash After Update" support built into their delta/update process. During an upgrade, this script will flash zips from an sdcard directory, with several options (listed in the script header) for displayed output, after all other addon.d backup/restore actions have completed. This can be used to flash SuperSU and then an AnyKernel2 kernel on LineageOS, for example. Only zips that specifically support addon.d-v2 can be supported on A/B devices. See this how to for instructions for use with A/B devices. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
98-twrp_ab.sh addon.d-v2 script (many devices) - attached
Allows you to keep TWRP installed in a boot partition through A/B OTAs with Magisk installed by copying the TWRP ramdisk from the current slot to the updated one, before Magisk's addon.d-v2 script patches it. Requires a current Magisk installation since we need the tools and Magisk's the only way to ensure a working addon.d-v2 environment across ROMs at the moment. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
97-dumpimages.sh addon.d+addon.d-v2 script (many devices) - attached
For ROMs with boot.img, etc. inside an OTA payload.bin or otherwise inaccessible, it dumps the updated chosen partitions before further modifications (TWRP, Magisk, etc.), saving it to /sdcard/Download/boot.img or to/from other customizable locations at the top of the script. Unzip once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-omnirootfix.sh addon.d-v2 scipt (many devices) - attached
OmniROM appears to include 69-gapps.sh automatically in its /system/addon.d directory despite not shipping with any GApps; when not rooted this doesn't appear to present a problem, but really this is only because the script doesn't have enough permissions to run how it's supposed to since Omni's sepolicy doesn't let addon.d-v2 work correctly. Once Magisk is installed, providing more privileges to the addon.d-v2 update_engine, Omni's 69-gapps.sh would remove important system files during an A/B OTA when no GApps were installed, so this script will simply prevent that for those wanting to run Omni minimally and with root. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
00-resizesystem.sh addon.d script (many devices) - attached
One common solution for aging devices is to resize the /system partition so that it can hold newer, larger ROMs and, of course, GApps packages. On devices where the /system partition has been resized to hold larger GApps packages, but the ROM in use has system.dat format zips with no resizing functionality, the extra space would get lost in a ROM delta flash, breaking things when GApps attempted to restore. This script will resize the system partition to its maximum before the GApps restore occurs on EMMC-based devices with standard partition naming. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
10-extract-lineage-kernel.sh addon.d script (many devices) - attached
Nowadays with systemless root and other boot.img mods out there, it's good to have a backup of your ROM's unmodified boot.img handy in case you want to do a clean flash of your boot partition. Since LineageOS moved their update zips to a /data/data subdirectory that made this harder to get to, I automated the procedure as an addon.d script so that the newest gets extracted on each update. The output directory may be changed by editing the script. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions.
999-customkernel.sh addon.d script (many devices) - attached
Addon.d is awesome at restoring your GApps, root app, and other things after a ROM Delta, update, or dirty flash, but of course this can leave a lot of stuff out that you'd also have to re-flash (see below for a personal addon.d script you can modify to cover anything else you want to save). This script aims to help remedy the issue for custom kernel users on EMMC-based devices with standard partition naming by dumping the current kernel as part of the addon.d backup process, and then restoring it after the ROM has flashed its included kernel. Remove the .txt extension once downloaded and place in /system/addon.d/ with rwxr-xr-x (755) permissions. This is deprecated by my FlashAfterUpdate addon.d script, above.
logohack.sh (GN) - link
Galaxy Nexus bootloader image replacement hack script. Inspired by bitdomo's brilliant imgdata tool and replicating the functionality of Ezekeel's abandoned, broken paid Logo Me app, this script improves upon the app version by working on all Galaxy Nexus bootloaders and on-the-fly, to allow replacement of the Google logo and lock images within the sbl partition. Remove the .txt extension once downloaded and place in /system/bin/ or /su/bin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
flash_image (many devices) - attached
MTD devices require a little extra finesse when flashing partitions from the command prompt and multiple commands, versus MMC devices, for which we can just use the dd command both ways. I wrote this little script to simplify the process for myself in my MX Box tinkering. It parses /proc/mtd so you only need to enter the partition name. It requires _n0p_'s excellent MTD-Utils compiled for Android, and uses grep and cut from busybox. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from the Terminal.
getprio (all devices) - attached
Android doesn't allow you to check the priority (or "niceness") of a process with the getpriority command as you would with normal Linux, and busybox doesn't provide this functionality either, so I wrote this reasonably simple script to allow you to check the niceness of a process. Some kernels have been experimenting with increasing the priority of com.android.systemui for smoothness, so this command can be used for testing different levels and whether the renice command set it correctly. Remove the .txt extension once downloaded and place in /system/xbin/ with rwxr-xr-x (755) permissions. It can then be run from Terminal with either the pid (default), class or a class name search string. Uses pidof and pgrep from busybox.
gappsintegrator init.d script (many devices) - link
ROM GApps Auto-Integration of /data/app GApps into /system, complete with libs (unlike Titanium Backup), for Jelly Bean through Marshmallow. It should process things early enough in the boot that afterwards Dalvik will immediately do the cleanup ("Android is upgrading..."), much like following an OTA. An initial GApps installation is one requirement and there are some important notes for support of Lollipop and above. Intended for ROMs with a busybox installation. Can also remove libs from and zipalign the integrated APKs if those binaries are present in the ROM.
lmkwhitelist init.d script (all devices) - link
Users running ROMs or kernels with extremely aggressive custom lowmemorykiller (lmk) driver settings may notice their launcher redrawing frequently. Some kernels/ROMs also include an exclusion for this by making stock (or the included) launcher unkillable, however that still leaves all the 3rd party launchers out there that people use. I wrote this init.d script with a community created list of the most common launchers to make whichever one is installed unkillable. This also has instructions for how to set up init.d scripts. If your launcher isn't included in the list, you can modifiy it by adding the application class name (from the Play Store URL) to the list within quotes, separated by spaces. Also part of the 975experimental Franco's Dev Team init.d script, linked above.
dalvik2cache init.d script (all devices) - link
Bind mounts the dalvik-cache directory to the cache partition. Useful on devices where the cache is sizable and unlikely to be used for OTAs (custom ROM, etc.), and the data partition is not. Every little bit counts!
settingsdump.sh (all devices) - attached
In comparing vm settings from various kernels and ROMs to see what's out there, I wrote this script to generate a list of the values of all the relevant sysfs files and directories. Now expanded to cover cpu and governor as well. Remove the .txt extension once downloaded. To run it, assuming you just put it in /sdcard/, open Terminal Emulator and type: "sh /sdcard/settingsdump.sh" (without quotes). It will output the file to /sdcard/r*-output.txt where * is the revision of the kernel you're running. This makes it easier to compare what's changed between different nightlies, for example.
Other
BootUnlocker app (many devices) [with segv11] - link
With a number of users researching and contributing the bootloader lockbit and tamperbit offsets in threads around xda and to the development thread for seg11's excellent BootUnlocker app, I have begun making beta builds with these new devices added. With hopes of adding any/all that can be, it now supports all the older Nexus devices, OnePlus devices and several others. We are accepting Pull Requests and collaborators for further device/design updates. Check my original revival post for more details.
G-Box Midnight MX2 g18ref ROM, recovery and kernel osmods (MX Box) [with BenniBenassi & relol] - link
I bought one of these unbranded Android TV boxes and was immediately determined to tweak it as much as possible following my work on the Galaxy Nexus. Flashing the official Matricom stock ROM over the generic included one I also discovered the recovery didn't have any A/V output to my old CRT TV. I set out to dump the kernel and recovery images, fix the recovery images and tweak the kernel defaults for the most performance.
Holo Stock Notification Icons for Notification Toggle (many devices) - link
This was likely my first post ever on xda. It is a "Notificon" pack for j4velin's fantastic Notification Toggle App, bringing a seamless stock look to this indespensibly useful app. Also a great way to get back to Settings easily from the notification shade since Android 4.2, and add shutdown/reboot menu functionality to stock/vanilla ROMs.
My GN Kernel Settings + 900colorsettings init.d script (GN) - link
I was being asked a fair amount for my kernel settings over in the GN f.K thread where I helped out, so I posted them up. I also put up an init.d script for setting color values on boot, which can drastically change the outcome on older panels, and at least makes custom values seamless. Instructions for how to set up init.d scripts are included.
Galaxy Nexus Baseband Collection: maguro - i9250 / M420 / SC-04D Radios (GN) [with josteink] - link
Original thread author josteink moved on to other devices and asked me to take over the thread. Lots of great information on the GN radios, posted alphabetically by region and chronologically by the build string date I found embedded in the images. Huge respect and massive thanks to josteink for seeing the need for a baseband thread almost as soon as the Galaxy Nexus was launched, way back in December 2011, and maintaining it diligently.
TK GApps (many devices) [with TKruzze] - link
After helping TKruzze with some of the concept and script work for his famous Paranoid Android Google Apps packages (PA GApps 2.0), we decided to collaborate again for his return to XDA after a much-needed hiatus, with me doing the thread setup and management with DevDB, and a Q&A section so things don't get overwhelming for those trying to follow along. The main thread remains locked and can be subscribed-to for those wanting notification only when there's a new GApps release, and the Q&A functioned as the main discussion thread where people can help each other. Much of the script is the same from PA GApps but TKruzze has added some impressive new features, made many fixes and revamped a large portion of the documentation. I also continued as an adviser and submitted script when needed.
Nexus Louder Audio Improvement Patch (GN, N4, N5, N7 '12, N7 '13) [with Misledz] - link
One of my earliest forays into EDIFY scripting, I wrote the flashable zip install/revert scheme for this great volume boost mod by Misledz. The scripts check to see if the mod is already installed and if so recommends you flash the version-specific revert that goes with it. More on that in the Intelligent EDIFY thread. During install the script also backs up the ROM files it replaces so that you don't need to reflash your whole ROM if something goes wrong, just use the revert to restore the backups. I eventually rewrote this completely in shell script with a Universal install/revert, that detects which files to backup and leaves a list for itself to revert. I also wrote automation batch scripts for Misledz as the "Louder Build Farm" to simplify his work for all the versions of the mod he maintains for various devices, linked in the knowledge base below. GN/Dev thread linked; Other links can be found there.
Payload-Dumper-Go for Android Magisk Module (many devices) [with ssssut] - link
payload-dumper-go arm compile and wrapper for use extracting from payload.bin on-device.
Git for Android Magisk Module (many devices) [with Termux] - link
Hacked arm64 git commands for use on booted Android.
Google Experience XML Magisk Module (many devices) [with Google] - link
Hacked Google Nexus/Pixel/Android One sysconfig feature xml entries for use on non-Google devices.
Digital Wellbeing Add-on Magisk Module (many devices) [with Google & Open GApps] - link
Digital Wellbeing for Android 12L and 13 GApps that don't properly support it (like MindTheGapps).
Model Mod Magisk Module (many devices) - link
Experiment to append _SN to the existing device model to get CTS passing again after the September 2021 server-side SafetyNet changes, (superceded by kdrag0n's excellent Universal SafetyNet Fix module).
Xposed Framework Installer Zip (many devices) [with rovo89 & Tungstwenty] - link
When JB4.3 broke all previous root methods I made this simple frontend script to install rovo89's brilliant Xposed Framework for modding ROMs until they could release a new version themselves. Xposed Framework files and the install.sh used are the work of rovo89 and Tungstwenty; I have only created a recovery flashable zip and shell script to function as an alternative frontend for the framework installation process. Then updated to mimic the APK installation and allow devices with /system write protection like HTC's S-ON to install the framework. (Deprecated as of Xposed 2.5).
BBCode for my xda Signature (n/a) - link
Last and definitely least. A number of people have asked me about the formatting of my signature, so here are some simple BBCode tricks and workarounds I thought others might like too. Keep in mind that my signature can be significantly larger because of my RC status.
Enjoy!
Questions, comments and feedback welcome.
Credits & Thanks: All authors of any included binaries and libraries for their amazing work. Anyone who's helped me with these projects along the way.
Disclaimer: Naturally, you take all the responsibility for what happens to your device when you start messing around with things.
Knowledge Base
Links to information/research posts I've made and other experiments.
----
avbtool-arm (zip package) - link
AOSP's BootSignature.jar for AVB v1 was relatively simple to run on-device for boot.img modifying flashable zips like SuperSU and AnyKernel2 but avbtool for AVB v2 is written in Python, so that makes things a bit trickier. For experimentation I whipped up a little wrapper script to run avbtool on-device with an actual Python interpreter.
Omni SoundPacks (and Nexus Stock pack) - link
My suggested expansion to the Omni SoundPacks feature to allow it to cover all SystemUI sounds.
OnePlus FingerPrint Material Icons (Information) - link
My preferred fingerprint icon for the in-screen OP6T sensor using Zacharee1's excellent OPFPControl app.
----
Complete Shell Script Flashable Zip Replacement + Signing Documentation (Reference) - link
Using a shell script instead of an update-binary in flashable zips can make them universal for architecture and put a lot more power in the hands of the developer. This reference documents all of the analogous functions myself and others have written to make this easy.
Booted Zip Flashing Shell Setup Script (Reference/How-To) - link
My implementation of booted zip flashing, originally for AnyKernel2 in Franco Kernel Updater (now Franco Kernel Manager) and since expanded to support AK3's ability to be flashed from anywhere and support most other flashable zips on devices that allow remounting /.
Unified ext4/f2fs ramdisk + ROM installer (Reference) - link
Supporting multiple filesystems like ext4 and f2fs in a custom kernel boot.img ramdisk required some work before custom ROMs were updated to do this themselves and use fallback fstabs. This is the roll-up post gathering all the changes necessary for someone to add this pre-official support to their ramdisk, kernel and ROM installers.
FlashFire Recipe Book (Reference/How-To) - link
Just a quick reference of common tasks (OTA flashing, etc.) for people figuring out how to use Chainfire's brilliant flashing app.
personal addon.d (How-To/Template) - link
I was tired of having to redo a number of tasks (remove files, backup Nexus sounds and replace the AOSP ones, etc.) to get my device back to where I wanted it after flashing a newer nightly, so I wrote an addon.d script to do it all for me. Provided if anyone wants to modify it for their own personal setups.
KBox2: Set Up A Build Environment On Android (How-To) - link
Very cool Linux-like command prompt environment on Android. I originally had it set up as a native build environment with rudimentary git support. You can follow my steps to do the same.
Keeping SafetyNet Passing With Incremental Google OTA on Virtual A/B Devices (How-To) - link
Post-reboot checks added to the incremental OTA process for Virtual A/B devices using Google's servers made it impossible to remain rooted throughout the OTA process, but following these instructions you can complete the OTA then re-root without SafetyNet catching you.
Cygwin-Linux Cross-Compiler (How-To) - link
Compiling from Cygwin with a Linux target required some fixes to the toolchain, so I detailed them for future reference.
N4/N5/N7 '13 Qualcomm Optimized Bionic/Dalvik Patch Comparisons (updated zips) - link
Using Qualcomm optimized files on Snapdragon devices improves performance greatly on KitKat. Especially good on Nexus devices or AOSP ROMs. I took the time to dissect the required files and see what worked best.
AIK Build Farm (desktop shell script) - link
The Cygwin shell script "build farm" I wrote for my Android Image Kitchen project to perform all of the cross-compiles required for the mobile and Linux versions. Allows someone to setup the repos from scratch and build.
Louder Farm (zip packages) - link
The Nexus Louder project was a pretty massive system file modifcation undertaking. This details my work to make building the patch zips easy for co-dev Misledz, and includes the farm packages at various stages.
----
N7 '13 Bootloader cracking (Information) - link
Sat down with my parents' Nexus 7 2013 (before I got my own) over Christmas and cracked the bootloader for unlock support via my Nexus BootUnlocker Script zip and later the official BootUnlocker App.
N7 '13 Unbricking (Information) - link
Instructions I put together for recovering from a hard brick (bad bootloader flash usually), via the exposed Qualcomm/Marshall London "HS-USB Diagnostics 9006" mode.
Default System Alarm Setting Script (Information) - link
A script snippet function to allow easily changing the default alarm sound on ROMs that hide this ability, like OnePlus' OxygenOS.
SELinux Audit2Allow Script (Information) - link
A script snippet for turning SELinux audits in a logcat into allow statements ready for supolicy or magiskpolicy.
Partition Dumping Script (Information) - link
A script snippet for dumping all non-userland partitions from any eMMC device, useful for bootloader lockstate hacking.
GN Partition Information Table (PIT) Research (Information) - link
Wanting to push the GN as far as possible, several remaining users came together to discuss how it could be repartitioned to add more space to /system to better support Lollipop+ and I contributed a large amount of R&D over several posts throughout the thread which resulted in the PIT Editor script zip (posted above). Could be useful for other devices using PITs as well.
GN/N7 '12 tunables post (deprecated) (Reference) - link
The list of supported basic tunables on franco.Kernel for the Galaxy Nexus and Nexus 7 2012 back when those were my primary supported devices.
GN scheduler tunables HZ scale (Information) - link
The Galaxy Nexus scheduler (and other) tunables opperate on an odd scale due to the the device's HZ value in the source being weird. This post experiments with that and finding the method/equation behind it.
LMK boot timing (Information) - link
The Android lowmemorykiller module default tunables go through a bizarre sequence during boot, so I experimented and came up with a script to allow setting alternates as soon as possible.
LMK Launcher Whitelist/Niceness settings reversion (Information) - link
Setting oom_adj values and changing the niceness on launchers and systemui improved responsiveness and helped avoid these important processes being killed by LMK. Then I noticed sometimes they spontaneously reset; experimentation followed.
MTD partition flashing (Reference) - link
My MTD-based MX Box set-top device gave me a few hours of headaches until I figured out how to dump and flash the boot (kernel) partition correctly. This details my experiments and the correct procedure I discovered.
nano Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get the nano terminal editor utility to build for Android from the official git repo source.
mtd-utils Android static build instructions (Reference) - link
A little documentation of all the dirty tricks I used to get mtd-utils to build for Android from the official git repo source.
Pixel Launcher bind mount instructions (Reference) - link
I was annoyed that on stock Nexus 5X and 6P Pixel Launcher wasn't available and when sideloaded lost the Google Feed pane, so I replaced Google Now Launcher with Pixel Launcher using bind mounts.
Netflix broken DRM workaround instructions (Reference) - link
Custom Nexus 7 2013 ROMs Nougat+ have all had issues with Netflix due to some peculiarities of the DRM libraries the ROMs use, but some found that intentionally semi-breaking DRM using files from other devices allows Netflix to work again, but this broke Google Play Movies. I did some more testing, resolved the Play Movies issue and wrote up how to install the single needed replacement library either to system or with a systemless bind mount.
----
Thanks for the interest! More to come, I'm sure!
What can I say...
SUBSCRIBED
Sent from my Galaxy Nexus
Far superior
thanks
Franco Team always made a great work .... Keep it up.
Thanks for these great useful infos!
Bookmarked, subscribed and rated a well deserved 5 stars :good:
Thanks for sharing. Very useful.
Nice...
Envoyé depuis mon Galaxy Nexus avec Tapatalk
Nice collection osmosis
Many thanks osm0sis, to you and all the team for all your contributions Almost feel as though I know you since I've been hanging round GNex and N7 franco.Kernel threads for so long and if you pop up on the N4 thread it's like seeing an old friend I'm mostly quiet, but really appreciate all you do :thumbup:
Sent from my Nexus 4 using Tapatalk 2
Subscribed... Thanks dude...
-3StarsAndaSun
Subscribed. Thanks
Thanks back to you, everyone! I've learned a hell of a lot about Linux and Android in the year since I got my GN, and I mostly have xda to thank for that, even though I've always been the type to tinker and Google things. Still lots more to learn though! But, at the very least I guess nobody can say I haven't been busy since becoming a RC, huh?
Nice to see all these settings are adopted by others, also the interactive tuneables are used in ak kernel now.
Verstuurd van mijn Nexus 7 met Tapatalk
Subscribed :good: !
New version of testvalue.sh up. I added the input value to the output.txt file to make it easier to read since it starts at 0. Right now we're trying to work out the equation for the scale of certain cfq and deadline tunables on the GN, which is a bizarre one:
7, 15, 23, 31, 39, 46, 54, 62
Increases by 8s but occasionally (on the 5th jump, though sometimes 6th) it increases by 7.
Edit: Every 3rd increase of 7 occurs on the 6th instead of the 5th.
Edit 2: Stats genius of the group, @pkgnex worked out what the trick was; dropping the decimals once calculated.
So in Excel: y=TRUNC(x*7.8125,0)
:good:
The "why" of the GN tunables working this way, with a value of 125/16 is a very good question. No ideas there, personally. Something to do with the GN having a HZ value of 128 (where on others it's 100 or even 200) I'd assume, but I don't see the direct connection.
This was very handy to know though, because the cfq+deadline source requires the number of jumps (x) to hardcode the values, not the actual desired numbers like you'd expect.
Perfect!!!
Very interesting
Created a getprio script last night for use in /system/xbin as a runnable script to check the niceness of a process. It's up in the 2nd post now. It attempts to make up for Android not having "getpriority", and not displaying the niceness in "top" or "ps" like it would on mainstream Linux.
Code:
usage: getprio [-p] <pid> | -c <class> | -s <search string>
note - class name search will only use the top result
So you can either -p the numeric pid of a process if you know it (this is the default so the -p argument is optional), -c the class name of the process (eg. com.android.systemui), or -s a search string using part of the class name (eg. systemui). If there is more than one result for the search only the top result will be returned so if you are trying something like "-s mms", you'll only see the system mms process and not com.android.mms until you get more specific with "android.mms" or something. It's likely you've got a lower level process if you get the response "Warning: empty class name!" so that's your tip your search was too broad. Naturally, processes must be running in order to return info as well. :good:
Edit: ps -p will display niceness on Android, but it's not ideal if you want it only for a specific process like with getpriority. Thanks boype.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hello everyone,
with this post i present you my Customized LineageOS 11.0 build (based on Android 4.4.4) for the Samsung Galaxy S Plus (GT-9001).
This Rom is based on the work from the ADC-Team and their CyanogenMod 11.0 ROM. The included Kernel is based on Christopher83's UV K^Kernel.
I made this Rom mostly for myself, because i still use this device as my daily driver.
Please take a look at the feature list to see if you like them or not. Also, please read the installation instructions carefully!
Disclaimer
Your warranty is now void.
We are 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 us for messing up your device, we will laugh at you.
Click to expand...
Click to collapse
Features
Latest LinageOS version with current security patch level
Kernel 3.4.113 compiled with latest Linaro 7.3.1 Toolchain
Rom compiled with latest UberTC 4.8.5 Toolchain
Build with optimization flags and added misc performance optimizations
F2FS support for Data and Cache
SDFAT driver for ExFAT and vFAT support
Hardened Kernel and ROM configuration
A lot of fixed security vulnerabilities (e.g. the spectre bug)
Debloated by removing some apps and more stuff (like the theme engine)
microG support
Build with NoAnalytics
Removed some of Google's proprietaries
Up to Date Fennec web browser
Some Vendor Blobs got replaced with open source alternatives (rmt_storage, libgemini and rild till now)
Some upstream updates (Font, tzdata, APN, ...)
Rom and APKs signed with private keys
a lot more...
Installation
If you are installing this Rom for the first time, please do a clean installation:
Download this Rom and the latest TWRP recovery from the ADC-Team with F2FS support (look inside the Download section)
Optional: Download a Gapps package, even tho i strongly suggest not to install them, because of possible performance issues and privacy concerns
Put all of the downloaded files on an external SD card (if you don't have one, you can copy the Rom (and Gapps) on the internal SD card via MTP after the wiping step)
Optional: Backup all of your data
Install the new recovery, then reboot into recovery again
Change the filesystem for the Data AND Cache partition to F2FS (Wipe -> Advanced Wipe -> Select Data -> Repair or Change File System -> Change File System -> F2FS -> Swipe -> Redo steps for Cache)
Wipe Dalvik Cache, Cache, System and Data partition
Install the ROM
Optional: Install Gapps
Reboot the system
If you want to update from the 03.08.2018 build or older to a newer version you have to flash a migration zip first.
Read more about it in the second post.
If you already installed this build, then you can just update it:
Download the new build and copy it to your device
Wipe Dalvik Cache and Cache
Optional: Wipe System (I do this step every time. Its usually not needed and will (hopefully) tell you if it's necessary)
If you are using Gapps you have to install them after the Rom update again
If you are using Adaway, you have to download your Hostfiles after this step again
Install the Rom update
Reboot the system
Changelogs
04.11.2018 build:
LineageOS
-september security bulletin
-added disclaimer to the security patch level
Kernel
-a few patches from lineageos' msm8974 kernel repo and jdc teams kernel repo
-more spectre patches
-changed default governor to interactive
-fixed a "few" compiler warnings
Rom
-update tzdata to 2018g
-update apns
-remove more debug programs
-speed up (scroll-)animations and shutdown
-moved gps hal to the device tree
-add rom informations to the updater script
Apps
-updated fennec to 63.0
Again: if you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
Old Changelogs:
10.09.2018 build:
LineageOS
-august security bulletin
Kernel
-misc security patches
-updated ancora defconfigs (because of a request)
-implemention of a quickwakeup driver
-use gzip instead of xz for compression
-overclock GPU to 275MHz (thanks to marcindevelopment)
-some more small things
Rom
-updated apns
-removed some debug programs
-removed recovery resources from the zip
-misc cleanups
-readded all the languages and fonts! (thats why the build is about 30mb larger)
-signed builds!
Apps
-updated fennec to 61.0.2
Again: if you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
ZIPs
-addonsu zip
-addonsu-remove zip
-migration zip
Click to expand...
Click to collapse
03.08.2018 build:
LineageOS
-july security bulletin
-added some missing September 2017 patches
Kernel
-added LineageOS' SDFAT driver, removed ExFAT driver
-added Spectre V1 and V2 patches
-some security patches from LineageOS' samsung_msm8974 kernel tree
-added some more hardened kernel configurations from AndroidHardeningArchive's Kernel tree
-use optimizations for the memory manager again
-updated android-alarm driver
-a lot of firmware loader updates
-reverted all of the latest binder updates
This fixes the broken touchkey backlight timeout option
-added some K^Kernel patches i somehow missed
-switched some I/O schedulers and governors
-added an interface that lets you disable the logger
-removed execution domain support
Rom
-renamed Rom from UNOFFICAL to customized
-reworked brightness fix, now it works for every brightness value
-whitelisted some OpenGL ES methods (Google Maps and some other Apps my run faster now)
-readded arabic language and font (because of a request)
-disabled LineageOS statistics by default, only relevant for a clean installation
-removed CM's recovery keys
-updated Wallpaper Picker
-updated APNs
Click to expand...
Click to collapse
13.07.2018 build:
Kernel
-Compile GPU driver and crypto modules with -O3 again
-Reverted a faulty commit
-Removed F2FS encryption support (not supported for Kernel 3.4)
-Implemented CPU boost (thanks to MarcinDevelopment)
-Small performance optimizations
-Fixed some compiler warnings
Rom
-Deleted one unnecessary vendor blob
-Disabled GPS by default, only relevant for a clean installation
-Updated APN's
-Use low-res bootanimation
-Boot with 1/4 of the maximum brightness
-Implemented the hacky maximum-brightness-after-boot workaround
-Small cleanups
Apps
Fennec
-Updated Fennec (they forgot to build some languages)
If you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
08.07.2018 build:
Kernel
-Kernel compiled with -Os flags instead of -O3
This should fix the hw button bug (thanks to outofmemory13)
-a lot of binder updates
-properly implemention of UID-based routing
-some more things from LineageOS' samsung_jf kernel tree
Click to expand...
Click to collapse
06.07.2018 build:
Since this Changelog would be too big to add every change that was made from the latest CyanogenMod Rom from the ADC-Team, this is more a of a mashup, I am sorry if I forgot something important.
Notable CyanogenMod/LinageOS changes
-rebranding to LineageOS
-new Bootanimation
-updated translations
-some layout fixes
-some fixed FCs
-updated APNs
-some security vulnerabilities got fixed (like Krack and Blueborne)
-implementation of the security patch level
Current version is June 2018
Kernel
-updated Kernel version to 3.4.113 (EOL)
-compiled with latest Linaro 7.3.1 Toolchain
-changes from the ADC-Teams cm-12.1 branch
-switched to the UV configuration per default (if you notice stability issues related to the undervolting, you can manually change the voltage tables)
-update BFQ scheduler and make it default, also removed some other schedulers
-switched to Lulzactive as the default governor, also removed some others
-misc performance optimizations (e.g. disabled CRC check, some disabled logs, stats and debugging, LZ4 compression, disabled LMK and more)
-updates for F2FS and ExFAT (1.2.9 -> 1.2.19)
-TCP changed to Westwood
-build with some optimization flags (O3 and Graphite optimizations)
-mark SD card as non removable
-included power efficient workqueues
-a lot of fixed vulnerabilities
-hardened build configurations/changed some configs, that were really bad for security (e.g. disabled devmem, disabled AIO, updated LSM_MMAP_MIN_ADDR value and more)
-raised default min CPU frequency (this fixes the audio stuttering in Apollo music player)
-lowered min display brightness
-disabled virtual terminal (this means 1MB more available RAM OMG!!!)
-a lot more
Rom
-synced with latest CM/LOS changes
-compiled with latest UberTC 4.8.5 Toolchain
-changes from the ADC-Teams cm-12.1 branch (the ones that are applicable for cm-11.0)
-compiled with Archidroid Optimizations V3 (I cleaned them up a bit)
-F2FS support for Cache and Data
-upstream changes to the media drivers (CAF media, audio and display driver)
-implemented ioprio for a more responsive phone (thats why i recommend to use BFQ)
-switched from Superuser to SU (you can enable root inside the developer options, there is also a new SU panel inside the advanced privacy guard)
-microG support (fake signature support can be enabled inside developer options)
-replaced Google Analytics with a self-compiled NoAnalytics version
-hardened SQLite (enabled secure delete)
-hardened WPA Supplicant
-updated APNs from the lineage-15.1 branch
-updated time zone data
-optimized GPS (with a security fix)
-some vendor blobs got replaced with open source alternatives (rmt_storage, libgemini and rild till now)
-more volume steps
-improved performance (e.g. by optimizing the scrolling cache, by showing simple dialog for optimizing apps, or disabling some debugging)
-sounds cleanup
-updated fonts and emojis
-you can now pull down the status bar when your device is locked
-smaller touch target for the emergency call button on a locked screen
-updated wallpaper
-misc hardening (e.g. by increasing the maximum password length)
-use Cloudflare DNS servers instead Google's
-remove some precompiled stuff (like old face recognition files)
-removed theme engine (even when not in use, it used about 5MB of RAM)
-removed some apps (like Terminal, SoundRecorder, STK, CMAccount, CMHome, VoiceDialer, VoicePlus, VideoRecorder, LiveWallpaper, CMUpdater, Email, PrintSpooler and even more)
-removed some languages
-added ASCII art and real-time installation infos
-added lockscreen rotation option
-speed up some animations
-some upstream fixes
-new power off charging animation
-a new bootsplash logo
-a lot more
Apps
Browser
-changed it to Fennec 61.0 from F-Droid
The security issues in the original browser and Kitkat's webview are too terrible.
CMFileManager
-removed the exit warning
Apollo music player
-fixed back button
-remind the last song that was played
LockClock
-fixed the interface for low font sizes
-removed Google proprietary
Trebuchet
-updated all apps icon
Settings
-updated icon
-updated battery/system icons (gingerbread is now dead!)
-updated german translations
-new contributors cloud
-removed theme options
-support for microG and SU
Click to expand...
Click to collapse
Downloads
04.11.2018 build
Old Downloads:
10.09.2018 build
03.08.2018 build
13.07.2018 build
08.07.2018 build
06.07.2018 build
Sources
LineageOS sources: https://github.com/LineageOS
My repositories: https://github.com/wangenau?tab=repositories
My manifest files: https://github.com/wangenau/android
Credits and Special Thanks
LineageOS/CyanogenMod
Mozilla
ADC-Team
JDC-Team
LegacyXperia
CopperheadOS/thestinger
Christopher83
sirmordred
coldwindofnowhere
DafabHoid
outofmemory13/MarcinDevelopment
ArchiDroid/JustArchi
XDA:DevDB Information
Customized LineageOS 11.0, ROM for the Samsung Galaxy S Plus I9001
Contributors
wangenau
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP Recovery with F2FS support
Based On: LineageOS
Version Information
Status: Stable
Created 2018-07-07
Last Updated 2018-11-04
Additional Informations
Signed Builds
Starting with the 10.09.2018 i will start to sign my builds with my own private keys. That includes the Rom itself, but also the APKs inside of it (instead of precompiled apps i include, which is only fennec till now).
This means you (or someone else) can only update the Rom and the system APKs with files that are signed by me. With this noone should be able to install a bad system APK or a bad build on your device.
To update your device from an older build, you have to add those keys to your device first. I made a flashable zip for that purpose. So if you want to update from an build that is older than the 10.09.2018 you have to flash this zip first.
Download migration zip
You only have to do this procedure once. If you do a clean installation you don't even have to it.
But that also means you can't go back to an older build after going to signed builds. (If you really want to for whatever reason, edit the migration zip for that purpose, or ask me how to do it)
To check if one of my builds has the correct signature, simply use:
Code:
keytool -J-Duser.language=en -list -printcert -jarfile zip_name.zip
The resulting fingerprints of my builds (after the 03.08.2018) are listed as follows:
Code:
Certificate fingerprints:
MD5: A2:42:4C:F5:4E:DD:3A:A2:C8:20:3A:AF:A1:D6:B9:99
SHA1: F2:13:38:21:53:55:89:CD:30:96:18:99:DD:7B:6D:81:DF:18:79:5F
SHA256: 94:56:09:A6:38:84:CB:BD:82:A5:A9:30:2F:D7:7C:EC:95:AA:57:FE:88:3B:9B:16:79:61:64:B4:AC:79:53:CC
SU
This Rom comes with su preinstalled. This means you have the ability to use Apps that need root permissions. If you don't want this you can remove su with this flashable zip.
Download addonsu-remove zip
If you want to add su back after removing it, you can do that with this zip.
Download addonsu zip
Simply flash these zips inside your recovery and reboot your device afterwards.
Bugs
There are a few small bugs, that will probably never get fixed (if you know how to fix these write me how to do it )
Bugs that can be fixed with a reboot:
no mobile data connection
SD Card stops working
Other Bugs:
MX Player does not work (and it will also freeze your system)
apparently this applies to RAR and Solid Explorer too
a user reported FC's and slowdowns inside the app "Aliexpress" with the lulzactive governor
Tips and Tricks
To get access to the Performance and Developer options go inside About phone inside Settings and tap 7 times on the Build number.
The default governor is interactive. Personaly i use lulzactive. Switching the governor may give you better performance and/or batterylife. But using interactive should be more stable. You can change the governor in the Performance section inside.
Under Performance Settings you can also overclock the cpu. I would say it is pretty save to overlock the cpu, since i am running my device for 5 years at 1.82 GHz (unless you have a different hardware revision)
If you experience random shutdowns after overclocking, you should lower the maximum cpu speed or raise your cpu voltage.
Using this Rom without Gapps is recommended. If you need some Google services you can use MicroG instead. To use it activate Signature Spoofing under Developer options. Google Maps i use, in combination with MicroG and Mozilla's Unified Nlp Backend. Also i use a rather old Maps version (9.14.0). But if you don't need the newest features und just some Maps, this version performs really good, even on our old device.
If you are using Adaway (also a recommendation) don't forget to add mtalk.google.com to your whitelist.
If you want an open source app store i can recommend F-Droid.
These pages (including the following posts) also contain useful informations about Rom and Kernel:
ADC-Teams CM11 Thread
Christopher83's K^Kernel Thread
Hello everyone again,
i finally created this thread and uploaded my rom. I had this in mind for a long time and i use my own LineageOS version since quite some time (i made my first commit in November 2015 i guess) and now it is in time for the 7th birthday from this device . I tried to make this device more secure, while still providing good performance and battery life.
I hope you like this rom, but again: I made this mostly for myself. And since i am not a power user (which is quite impossible with this device ), there might be some things that are broken that i didn't noticed, or stuff got removed because i didn't needed it. If you notice something of this or you find some bugs or have a question, feel free to post about it and i will take a look at it.
You can see all of my sources in the first post and even my manifest to make the build as reproducible as possible.
You can also take a look at the changelog for more informations (creating this changelog really took some time), at the two screenshots i uploaded and most important at the installation instructions.
I guess i don't have more to say for now, so happy flashing!
wangenau said:
-compiled with latest Linaro 7.3.1 Toolchain
Click to expand...
Click to collapse
HW Keys bug exist because of linaro. Switch to other toolchain or remove O3 flag (change to Os)
I'll use rmt_storage from sources you provided. I've used rmtfs all time, but seems that there's better replacement. Thanks!
outofmemory13 said:
HW Keys bug exist because of linaro. Switch to other toolchain or remove O3 flag (change to Os)
I'll use rmt_storage from sources you provided. I've used rmtfs all time, but seems that there's better replacement. Thanks!
Click to expand...
Click to collapse
You are welcome
And thank you for the infos about the hw buttons, i will definitely test this out!
Update
Hey, here is a small update. It should fix the hw button bug. I also merged some other changes to the kernel, but nothing big.
Changelog:
Kernel
-Kernel compiled with -Os flags instead of -O3
This should fix the hw button bug (thanks to outofmemory13)
-a lot of binder updates
-proper implemention of UID-based routing
-some more things from LineageOS' samsung_jf kernel tree
Click to expand...
Click to collapse
Download 08.07.2018 build
md5sum: 759dc4d116a68888e5bdfbd929b607bb
Update
Hey, here is another small update. This one fixes the brightness bug after booting. I couldn't find the cause of this, but I used my high-class scripting skills *cough* to create a workaround. I think there are no more major bugs left, unless you find one
Changelog:
Kernel
-Compile GPU driver and crypto modules with -O3 again
-Reverted a faulty commit
-Removed F2FS encryption support (not supported for Kernel 3.4)
-Implemented CPU boost (thanks to MarcinDevelopment)
-Small performance optimizations
-Fixed some compiler warnings
Rom
-Deleted one unnecessary vendor blob
-Disabled GPS by default, only relevant for a clean installation
-Updated APN's
-Use low-res bootanimation
-Boot with 1/4 of the maximum brightness
-Implemented the hacky maximum-brightness-after-boot workaround
-Small cleanups
Apps
Fennec
-Updated Fennec (they forgot to build some languages)
If you browser starts to crash after updating, you have to clean Fennec's data. I am sorry if that happens.
Click to expand...
Click to collapse
Download 13.07.2018 build
md5sum: 175f19c16373524fa16a56389b5ecc31
thanks, I have this phone locked in the drawer, I'm installing the rom, I'll let you know how it goes, thanks for everything.
If you have time and desire can you make a ressurection remix?
pablonik79 said:
thanks, I have this phone locked in the drawer, I'm installing the rom, I'll let you know how it goes, thanks for everything.
If you have time and desire can you make a ressurection remix?
Click to expand...
Click to collapse
You are welcome!
I am excited to hear your feedback.
Sadly I don't think that I will spend my time on another rom for this device, just because I still use this phone as my daily driver and I don't want to experiment to much with it. And my internet connection is also not the fastest, so downloading a whole new source code takes really long for me.
Hi Wangenau, This is to let you know thatI am very happy with this ROM, it is snappy, secured and almost everything is working. It looks like mobile data is not working. Any chance that you look into this?
noltha said:
Hi Wangenau, This is to let you know thatI am very happy with this ROM, it is snappy, secured and almost everything is working. It looks like mobile data is not working. Any chance that you look into this?
Click to expand...
Click to collapse
I am glad you like it!
But it is strange that mobile data is not working for you, for me it is working fine. Sometimes there is a rare case where mobile data randomly(?) stops working. You could try to reboot the device, while making sure that Settings->Mobile network settings->Data enabled is marked, wait a bit and see if the problem persists.
Let me know if this will fix your problem :fingers-crossed:
Edit: Removed second option because it is not a good tip
Solve my phone problem
I hope to solve the problem of a phone when I install the ROM is installed and does not work please respond quickly
hhssa said:
I hope to solve the problem of a phone when I install the ROM is installed and does not work please respond quickly
Click to expand...
Click to collapse
Hey, I just saw your post. Sorry if I don't understand, but what is your problem exactly?
wangenau said:
I am glad you like it!
But it is strange that mobile data is not working for you, for me it is working fine. Sometimes there is a rare case where mobile data randomly(?) stops working. You could try to reboot the device, while making sure that Settings->Mobile network settings->Data enabled is marked, wait a bit and see if the problem persists.
If that won't help, you could try to download , move it inside the zip under system/bin/ to replace the existing rild file and flash the zip again (after wiping cache, dalvik cache and system).
Let me know if this will fix your problem :fingers-crossed:
Click to expand...
Click to collapse
Thanks for your suggestions, a simple reboot fixed everything! Many thanks for all your time and efforts you put into this rom, highly appreciated!
noltha said:
Thanks for your suggestions. So maybe I will need to do a re-flash of the rom. I live in the Netherlands, maybe a different band or so. Will try all suggestions and come back
Click to expand...
Click to collapse
A reboot fixed it, so now everything is working!
Really like this Rom!
Many thanks for all efforts!
wangenau said:
Hey, I just saw your post. Sorry if I don't understand, but what is your problem exactly?
Click to expand...
Click to collapse
My problem is after installing the rum does not work the phone
hhssa said:
My problem is after installing the rum does not work the phone
Click to expand...
Click to collapse
I really need more informations to help you. Here are some:
Are you able to boot the device or did the flashing process fail? If it failed, is there an error message in the recovery terminal?
Did you followed the installation guide from the first post exactly?
Did you make a clean Installation, installed the needed recovery version und formatted data and cache as f2fs?
Do you have the right device? (this rom only works in the Galaxy S Plus, not on the Galaxy S or others)
wangenau said:
I really need more informations to help you. Here are some:
Are you able to boot the device or did the flashing process fail? If it failed, is there an error message in the recovery terminal?
Did you followed the installation guide from the first post exactly?
Did you make a clean Installation, installed the needed recovery version und formatted data and cache as f2fs?
Do you have the right device? (this rom only works in the Galaxy S Plus, not on the Galaxy S or others)
Click to expand...
Click to collapse
I've done all the steps but the phone stays in the animation mode for a long time and the phone is not working
hhssa said:
I've done all the steps but the phone stays in the animation mode for a long time and the phone is not working
Click to expand...
Click to collapse
That is strange. Have you tried to redownload the build and reinstall it?
And what was your rom before updating?
Kirisakura-Kernel for the One Plus 7 Pro
Hello everyone,
Kirisakura - Kernel is designed to bring a handful of beneficial features to the device, while ensuring excellent performance and smoothness to get you safely through the day!
This project aims to keep most of the subsystems updated, way ahead of the stock kernel, thereby improving security and performance, while keeping stability as the foucs during testing! This includes Linux-Stable, CAF-Upstream and kernel/common.
Kernel Control Flow Integrity (Kernel-CFI), which is achieved by linking the kernel with LLD and Link Time Optimization (LTO), more precisely ThinLTO, are quite unique security features.
The only kernels made by OEMs offering this security feature by default are the ones for the Pixel 3, 4 and 5 devices.
The recently released Kirisakura-Kernel for the OnePlus 8 Pro was featured on the XDA-Portal due to the inclusion of CFI. The featured article explains CFI in great details, is easy to understand and definitely worth to read.
If possible the latest Kirisakura-Kernel releases for various devices aim to include CFI in enforcing mode so users can benefit from this security features.
Another security feature is Shadow Call Stack (SCS). Similar to CFI, only the Pixel 3, 4 and 5 kernels use this security feature.
SCS is another security patchset that is aimed at preventing attacks via return oriented programming (ROP).
ROP is a technique where the attacker gains control of the kernel stack to overwrite function return addresses and redirect execution to carefully selected parts of existing kernel code.
If you´re interested here are a few good links:
Google Security Blog explaining SCS.
LLVM doc about SCS
Android DOCs documenting SCS
If reading about upstream in the paragraph above got you curious,have a read about Linux-Stable and why it is important here. The stable-process is not the same for every subsystem, but the general idea, rule of thumb and benefits are applicable for other subsystems as well.
Quick explanation of CAF-Upstream. CAF is short for Codeaurora-Forums. This is the place where development from Qualcomm for their SoCs happens. This includes the Snapdragon 855/+ that´s built into the different SKUs of the OP7/T/Pro.
The kernel-bases available on the Codeaurora-Forums, are basically the foundations OEMs use, to build their own kernel additions on top for devices featuring Qualcomm SoCs.
The Qualcomm developers push regular updates to the bases of the different SoCs, a bit similar to how Linux-Upstream works. Most OEMs usually stop updating the initial base after the phone is released, and only cherry-pick certain commits to be in line with the android security bulletin.
This kernel focuses amongst the other features to merge CAF-Updates in a regular manner, to provide updates, improvements and enhancements for SoC specific drivers and subsystems! This might take a while, because a lot of device specific testing is done on my end to ensure stability.
The EAS implementation from 4.19 CAF (sd865/+) was ported to this kernel. There are several interesting mechanisms qcom worked on. The basic layout of the soc architecture ( 4xLittle- , 3xBig- and 1x Prime-Core(s)) has not changed from SD855 to SD865. That means instead of revolution there was a very nice evolution the scheduler underwent.
The kernel includes a lot of improvements and contributions from other developers as well. Without this kernel would not exist.
Many of the improvements originate from @arter97´s, @kdrag0n´s, @RenderBroken´s and @Sultanxda´s work. Many others contributed in some way or another to this kernel.
A big thanks to all of them at this place!
Now lets continue with a list of features in the next paragraph!
Main Features:
- Based on latest kernel sources from OnePlus for Android 11 primarily intended for use on OOS stock firmware
- Upstreamed against latest CAF
- Linux-Stable-Upstream included to latest 4.14.243
- compiled with Clang 13.0.1 prebuilt from Google
- built with -O3 speed optimizations
- Link-Time-Optimization (ThinLTO)
- Kernel Control-Flow-Integration (CFI)
- Shadow Call Stack (SCS) Security-Feature
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Preview Kernel instead of full LTO for full program visibility (needed by CFI)
- fix CFI-Violations found in various subsystems like OnePlus/device specific drivers and qualcomm drivers
- Link the kernel with LLD and use RELR-Relocation
- include important fixes/improvements from kernel/common
- Flashing the kernel will keep root!
- Anykernel zip is based on the Anykernel3 repo from @osm0sis
- include vDSO 32 patches to improve 32-bit performance
- devfreq backports from 5.4 (sd 888 qcom kernel base)
- disable various debugging configs, that are not needed in a perf build kernel according to google.
- Removed RTB(interrupt) logging entirely
- disable selinux auditing (we don´t have to adress selinux denials running a stock rom)
- fix several coding issues detected by newer Clang-Toolchains
EAS related features:
- EAS scheduler backported from 4.19 CAF and 5.4 CAF / QCOM SOurce(SD865/SD888)
- adjust powerhal to account for scheduler backports
- disable autogroups and use cgroups for more efficient task placement!
- updates from kernel/common
- scheduler updates from Googles Pixel kernel
CPU related features:
- dynamic WALT-Windows based on FPS (more information here and here )
- Power saving workingqueues enabled by default (toggleable in EXKM)
have a read here: https://lwn.net/Articles/731052/
this complements EAS in general
- Change various drivers ( MM, audio) to user power efficient workingqueues. This should work well in conjunction with EAS
- include cpuidle patches from CAF
- improvements to cpufreq/times/stats
- improve memory allocations in binder driver
- vdso32 patches as found on Google Pixel devices (brief documentation here)
- arm64: lse: Prefetch operands to speed up atomic operations
- improve bluetooth performance
- improve /proc performance
- remove VLA-usage (info)
- option to disable touchboost in msm_performance
- disable coresight, enable coresight placeholder and add proper disabled clocks for sd 855
File System related features:
- improve memory allocations in sdcardfs
- improve memory allocations in kernfs
- writeback: hardcode dirty_expire_centisecs=3000 based on this commit
- ufs improvements from pixel 4/ pixel 5 kernel
- default IO scheduler to CFQ and readahead to 128
Usability related features:
- High Brightness Mode for increasing backlight level related to brightness accessible via EXKM app
- Vibration Intensity adjustable via EXKM app
- DC Dimming setting now fully functional
- add support for steam controller
- add support for nintendo switch controller
Display related features:
- KCAL to control the display
- KLAPSE integrated
- KCAL/KLAPSE: changes safety measures -> allow completely disabling two RGB values (this was requested to, for example, only have red values on night dimming)
- display tweaks to save power on statically rendered images (taken from samsung galaxy source, which uses a very similar panel)
- improve memory allocation
GPU related features:
- Ability to use the new 675mhz GPU step officially introduced by CAF (OP7/Pro is set to only use 585mhz as max)
more information and benches in the 1.2.0 release post
- add low_prio_worker thread for gpu driver (Improves performance when tearing down processes (eg, via LMK) and not blocking currently running UI from submitting work to the GPU
- remove debugging tracing from GPU driver
- improve memory allocation
Network related features:
- Wireguard Support (Details)
- advanced TCP algorithms enabled
- includes new bbr and bbrv2 (default to bbr as advised by @kdrag0n )
Memory related features:
- Memory Management patches from mainline kernel
- Speculative Page Faults (1. 2) (CAF-default)
- Fix various memory leaks in different subsystems
- allow ZRAM to use higher swappiness values than 100
- default ZRAM algorithm set to lz4 (fastest compression/decompression speeds)
- possibility to use lzo-rle as default ZRAM compression algorithm (more information here and there )
- possibility to use zstd as default ZRAM compression algorithm ( higher compression ratio, slightly lower compression decompression speed, more information and benchmarks here)
- free up memory by removing unused memory regions from dts
- improved performance for unity based games
- improved lz4 performance
Security related features:
- Control-Flow-Integration (CFI) and Link-Time-Optimization (LTO) ported from 4.19 kernel/common and Pixel 4/XL Kernel
- Use ThinLTO which was first used in the Pixel 4 XL Android R-Kernel instead of full LTO
- Shadow Call Stack (SCS) Security-Feature
- fix various CFI-Violations found in various subsystems like Asus/device specific drivers and qualcomm drivers
- enable init_on_alloc for even more security, more information can be found in the commit message
WLAN Driver:
- use CAF wlan driver and compile it inline, the only way to ensure working wlan with this kernel
- the kernel cannot even force load prebuild WLAN module as the kernel base is way to far from stock!
- do no longer rely on the pre compiled wlan driver module
- completely removed qcom_rx wakelock in the wlan driver
- removed debugging from wlan driver
- removed logging from wlan driver
Scheduler Setup and Kernel Settings:
- kernel setting get automatically applied at boot
- an AK3 helper module is automatically installed during flashing ( do not remove it in magisk manager)
Misc Features:
Wakelock Blocker:
- advanced wakelock blocker with the ability to block any wakelocks (dangerous, use with caution)
- please read [URL="https://arstechnica.com/gadgets/2018/08/p-is-for-power-how-google-tests-tracks-and-improves-android-battery-life/"]this for further info
- blocking a kernel wakelock should only be done in case of firmware incompatabilities (WiFi network at work (can´t be changed) causes deep sleep to not work on the phone.) That´s the only use case I see for this feature. The kernel does not features this to improve battery life!
Requirements
- unlocked Bootloader
- USB-Debugging in developer options enabled
- latest adb and fastboot binaries
- working adb and fastboot environment
- magisk root
- be aware kernel is primarily made for OOS, certain custom roms might not boot or have features broken
How to flash the Kernel:
1. Download the latest kernel.zip
1a. Optional: While it may not be necessary all times, you may want to restore stock boot.img, re-root with magisk and optionally install twrp.zip if coming from another kernel. Before reporting issues make sure you do that! Thank you!
1b. Optional: The stock kernel can be restored by either dirty flashing the firmware.zip or by restoring the stock dtbo.img as well as boot.img. Those can be extracted via payload extractor from the firmware.zip.
2. Make sure to use latest Magisk stable.
3. Flash the kernel.zip via latest EXKM or FKM app. Alternatively via TWRP if TWRP is working.
4. Reboot and profit. After flashing the kernel in magisk manager there will be a module called AK3 Helper Module, do not delete it.
DOWNLOAD:
Download is located always in this folder:
Android 11:
Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
Android 10:
https://www.androidfilehost.com/?w=files&flid=300422
Android Pie:
https://www.androidfilehost.com/?w=files&flid=294636
Important: Read after Download
Please take a look at the second post after flashing the kernel!
Changelog:
Android 9/Pie
1.0.0 Initial Release
1.2.0 https://forum.xda-developers.com/showpost.php?p=79657888&postcount=133
1.3.0 https://forum.xda-developers.com/showpost.php?p=79681205&postcount=212
1.4.0 https://forum.xda-developers.com/showpost.php?p=79715609&postcount=266
1.5.0 https://forum.xda-developers.com/showpost.php?p=79759064&postcount=369
1.6.0 https://forum.xda-developers.com/showpost.php?p=79812896&postcount=533
1.7.0 https://forum.xda-developers.com/showpost.php?p=79870285&postcount=624
2.0.0 https://forum.xda-developers.com/showpost.php?p=79958105&postcount=732
2.3.0 https://forum.xda-developers.com/showpost.php?p=79994692&postcount=821
2.8.0 https://forum.xda-developers.com/showpost.php?p=80174759&postcount=1003
2.9.0 https://forum.xda-developers.com/showpost.php?p=80246585&postcount=1062
Android 10/Q:
1.0.0 https://forum.xda-developers.com/showpost.php?p=80519841&postcount=1164
1.0.1 https://forum.xda-developers.com/showpost.php?p=80533419&postcount=1186
1.2.0 https://forum.xda-developers.com/showpost.php?p=80606335&postcount=1275
1.3.0 https://forum.xda-developers.com/showpost.php?p=80789819&postcount=1381
1.4.0 https://forum.xda-developers.com/showpost.php?p=81033561&postcount=1472
1.6.0 https://forum.xda-developers.com/showpost.php?p=81399355&postcount=1574
1.7.0 https://forum.xda-developers.com/showpost.php?p=81684441&postcount=1675
1.9.1 https://forum.xda-developers.com/showpost.php?p=82120413&postcount=1737
1.9.7 https://forum.xda-developers.com/showpost.php?p=82743109&postcount=2002
2.0.0 https://forum.xda-developers.com/showpost.php?p=83555997&postcount=2163
Android 11/R
1.1.0_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-84786595
1.1.1_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-84793145
1.1.3_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-84812661
1.1.4_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-84853537
1.1.6_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-84900619
1.3.9_R https://forum.xda-developers.com/t/...r-op7-pro-aka-guacamole.3933916/post-85510637
Donations:
Donations are not mandatory but very welcome!
If you want to support development or just buy me a coffee/tea to get development going: http://paypal.me/freak07
Credits:
@osm0sis for all his work, including the ak2 installer!
@tbalden for being the best HTC wingman!
@LeeDroid for his awesome roms!
@Captain_Throwback for all the mentoring and guidance!
@Eliminater74 for bringing me into the game and the Inspiration
@nathanchance for his upstream guidance and assistance
@RenderBroken for helping me out
@flar2 for all his work
@joshuous for all the help he provided to me in the past!
@arter97 for giving me advice
@kdrag0n for giving me advice
@topjohnwu for magisk!
@osm0sis for anykernel!
Contributors
Freak07
Source Code: https://github.com/freak07/Kirisakura_OP7Pro_A11
Kernel Special Features:
Version Information
Status: Stable
Created 2019-05-26
Last Updated 2020-09-26
Question: Is root preserved when flashing this kernel?
Answer: My kernel.zip keeps a device rooted by magisk rooted.
Question: How do I return back to stock kernel?
Answer: Flash boot.img as well as dtbo.img extracted from the full firmware zip.
Question: My WiFi is not working after flashing the kernel. I can´t toggle it on.
Answer: That means something happened to your device, that is causing some stuff to not get loaded properly when booting. I ran into the same issue once. Read through the thread to find the cause.
I wrote a guide in the linked thread, that explains step by step, how to return to a working condition without the need to wipe the phone completely.
Click the following link to find the post: post is linked here
Question: How to report bugs properly?
Answer: Have a look at post #3 in this thread. The linked guide is a pretty good starting point.
Before reporting any bug make sure you´re not using any mods, magisk modules, scripts or other modifications that alter various functions like sound mods etc.
Try to describe the issue as detailed as possible! Give your exact setup, like rom, magisk version, kernel version.
Is the issue reproducible? Does it happen frequently?
Provide logs, otherwise debugging is a lot harder. If you can already reproduce the issue and provide logs it greatly limits the amount of time I have to spent until I figure out how to reproduce it.
If the device force reboots/randomly reboots (that means you see the bootloader unlocked screen!) provide a ramoops file.
Easiest way is immediately after booting up, with a root explorer navigate to sys/fs/pstore. Copy the contents to your internal storage, zip it up and send it to me.
If the issue happens while the device is running provide a dmesg plus a logcat that you take while/shortly after the issue happens. This will log what´s running in the current session. Try to be as detailed as possible what´s happening when the issue appears. It will also help me in reading the log!
To easily get a logcat in case of a crash take a look at this post:
https://forum.xda-developers.com/showpost.php?p=79462002&postcount=1566
Big thanks to @jcmm11 for it
Here´s a tasker task to automatically copy /sys/fs/pstore on each boot to internal storage. Be advised these files get also created on correct reboots.
https://forum.xda-developers.com/showpost.php?p=79549126&postcount=1670
thanks @jsauder2 for this little trick
Useful Resources
How to report bugs:
It is incredibly useful if bug reports are done in a proper way. That saves everyones time and will ultimately lead to a faster bugfix (hopefully).
The following guide from @nathanchance is a very good guideline on how to properly report a bug!
https://github.com/nathanchance/Android-Tools/blob/master/Guides/Proper_Bug_Reporting.txt
How to convert your OP7 Pro to use f2fs on /data:
Do this only if you know what you´re doing. This guide works even on stock rom with stock kernel.
OP7 Pros Kernel as well as the fstab support f2fs by default.
If you´re using Kirisakura-Kernel starting with version 1.5.0 you will use the latest upstreamed f2fs implementation. Otherwise you´re running that´s a bit outdated and also a bit slower.
Google did put a lot of work in f2fs and that benefits here greatly too.
1. Backup your data and transfer it to an external storage device, because we will now erase everything on /data
2. Boot to TWRP
3. Go to Wipe - Advanced Wipe - Select "data" - Change file system - f2fs - confirm <- This will erase all userdata including your internal storage (pictures, videos, music etc)
4. Boot up and set up your device freshly.
5. Enjoy f2fs on your OP7 Pro
Androbench Results:
Stock EXT4 taken from XDA OP7 Pro Review:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
F2FS on Kirisakura 1.5.0
Well, I wasn't planning on unlocking the bootloader in this phone.... Going to now that you're here! Thanks for your hard work
Dude,
So pumped to have you on the OP7Pro! This is shaping up to be a really well supported device!
Sent from my OnePlus7Pro using XDA Labs
So hey everyone
want to lose a few more words here. I spent quite a bit of time getting this up as quickly as possible. I never had an OP device until now. So I needed to get familiar with it and get the hang of it.
I spent quite some hours and most of my free time since thursday, in the hope of getting this up before the weekend ends. Some people I spent less time with, were not quite as happy about this decision, but so be it.
I had quite a bit of experience with the CAF merge from the Pixel 3 XL, that made things a bit more easier and smooth. Upstreaming to latest linux-stable was quite a pain, because there are several commits, which cause the device to boot straight into Qualcomm Crash Dump mode.
In the end I got to 4.14.122
It´s still early here on this forums. So far now use adb sideload to install the kernel. The magisk module needs to be flashed otherwise some things, like accessing battery settings isn´t working, because of selinux-denials. If you can live without it, I´m pretty sure you can run this kernel also unrooted. But for the things I mentioned magisk is required, because you need to flash the companion module.
Once TWRP data decryption works, we can flash the zip simply in TWRP. Once EXKM and FKM are updated, we should be able to flash the zip via the apps too
For now it´s this way
I have a few more plans for this kernel, like wireguard, adding maybe some (not to much) features to it, maybe use f2fs and bringing it to latest state. I´m pretty sure I find more stuff as well.
The kernel is way more snappy than the stock kernel for me. It uses some of the EAS improvements from my Pixel 3/XL kernel, which can be utilized on this newer kernel base as well.
I confirmed it with a few little tests/benchmarks and for me the difference is night and day.
I´m running the device always full resolution and 90fps
If somebody can confirm, this it would be really great
If you encounter bugs, please take a look at post #2 and #3
there is a bit more in the kernel than the pure OP. I´ll update it the next few days
I wish everybody a nice weekend.
Great to see you here on this device!
Welcome to the world of OnePlus! This is my second device from Oneplus and finding it an awesome device. Sad to see HTC go down the tubes.
great to see you here freak!
Great news. Just flashed all working well so far
Great to see you here freak & we all appreciate you giving up your time. I'm staying stock until Stable Twrp is released, but as soon as it is I'll be using your kernel.....
@Freak07,
Never thought there would be a day that we would both be on the same device again.. ( I technically haven't gotten the device yet.. waiting till next month),
But glad you are here man. Your work is awesome... Now I got someone to cherry pick from JK man.............
BTW< stop by Slack every once in a while man.
Looks promising, I'll flash it! Good job!
hey bud message me on telegram guess we meet again lol im working on my stuff now glad to see you here @Freak07 and eleminator
Wow it's so nice to see you here! Never thought I'd see the day haha
Freak07 said:
I have a few more plans for this kernel, like wireguard, adding maybe some (not to much) features to it, bringing f2fs to latest state and I´m pretty sure I find more stuff as well.
Click to expand...
Click to collapse
Hey buddy,
I would love to see WireGuard support as I use it all the time. I much prefer the kernel implementation as it doesn't consume any battery compared to the userspace version which does.
In terms of F2FS are you also going to update in line with how Arter97 does things and also implement his Rapid GC commit and subsequent changes?
https://github.com/arter97/android_...mmit/34a4ea7309f551150628603f7ef71abc25e6b68e
Regards,
Ravi
Sent from my OnePlus7Pro using XDA Labs
Just flashed the kernel and companion module from within ex kernel manager 5.03 without issue. No pc or twrp needed
DC Dimming function in Utility/Oneplus Lab is not working...
Works fine here.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Team PrimeOS is pleased to present you, PrimeOS 2.x.x based on android 11 For Laptop/PCs.www.primeos.inPrimeOS is an Android-x86 based OS that provides a desktop experience on any x86 based device providing user top-of-the-line features like multi-window, taskbar, and deca-pro key mapper for gamers.Warning: PrimeOS 2.x.x is a free-to-use software in its alpha version and is constantly under development. We are not responsible for any kind of damage, data loss, or anything else that happens to you or your device due to PrimeOS. Please feel free to report bugs and other suggestions, we will consider them if they seem important for many users.Feature HighlightsDesktop Experience
Multiple features to give a desktop experience like start menu, taskbar, etc.
Multi-window support with maximize, minimize, close, resize, etc.
Close to AOSP experience with only necessary desktop features.
Taskbar with the ability to pin apps, show notifications, and system icons.
Android Gaming
Decapro key mapping tool to play games with keyboard and mouse (Press F10).
Pre mapped some popular games like PUBG, Freefire, Subway surf, etc.
PrimeOS Gaming Centre is available to browse recommended games.
Others
Opengapps included, no need to install them manually.
OTA support is available in settings -> about the device
Using Linux Kernel 5.4.x and Mesa 21.1.x for 64 bit variant
Spoiler: CLICK TO SHOW
USB stick / Flash Drive guide:
For this method, you need the Etcher / Rufus, PrimeOS iso file. We recommend you use a decent-speed USB drive (8GB or larger).
For flashing PrimeOS to the USB drive, plug in your USB drive and launch Etcher / Rufus. Now select the PrimeOS iso file, create the bootable USB.
Note: Be careful with the steps below and backup your data if you're not sure about what you are doing.
For installing PrimeOS on your HDD/SSD/SDcard, first, create a new partition for PrimeOS ( suggested minimum size is 16GB ).
Turn off the secure boot of your device and then boot up the PrimeOS USB by pressing Esc or F12, depending on your bios menu key, and selecting the PrimeOS USB to boot from.
Select the ‘Install PrimeOS option from the GRUB menu.
The installer will load, and you will have an option to choose which partition you created earlier. Choose it, and select Ext4 for formatting the drive.
When it asks if you want to install Grub, select YES.
When finished, the installer will then ask if you want to run PrimeOS, you can just reboot here, and make sure you remove the USB drive.
Do you already have PrimeOS and want to update manually? Read post #2851Known Bugs:
Hardware specific bugs like the trackpad, sound, wifi may come on few devices
Please share bugs or suggestions if you have any, we will try to fix them
PrimeOS 2.x.x would not have been possible without the awesome contributions of LineageOS, Android Generic Project and Supreme Gamers, please thank them before us.
Other information:Base android version - ANDROID 11.0
Download PrimeOS!! Please do not mirror without permission. !!Consider donating to us to keep this awesome project up and running.https://ko-fi.com/primeos
View attachment 5494493
Get Support
Reserved.
Reserved.
Core i 6400
ASRock motherboard
And i got black screan after install and bot it
Its appear after prime os logo boot
Thank you so much to all those working on this project. I was able to install the January release on two machines in dual boot mode with Windows 11:
(1) Lenovo Yoga2 Pro - this went without any glitch whatsoever, runs very well. All things seem to work well. Touchpad accuracy seems low. Dual boot works just fine, touch screen works great, my PC behaves very much like a 13" Android Tablet. Kudos to the development team.
(2) Lenovo Think Centre Tiny M715q - AMD Ryzen 5 PRO 2400GE, 12GB RAM, Intel 2TB NVMe M.2 SSD, WD 500GB SSD.
I ran into installation issues with this machine. I wanted install on a partition in the Intel NVMe drive and after I get through all the way to the end of the installation it would fail to create files on the filesystem and get a Kernel Panic Error and the system will reboot. I tried PrimeOS and BlissOS with the same result. I assumed that this might be caused by the NVMe drive and decided to put back the WD 500GB drive in the machine and ran the installation off of USB, installed PrimeOS on that SSD successfully (well, sort of).
Now challenges I am facing : Dual boot works only sometimes. I always get the grub2 boot screen. However if I booted to PrimeOS the previous time, I do not see Windows 11 as an option to boot. If I booted to Windows 11 (which I do by going into Bios Boot Options and selecting it from there, which is pain), then on the next boot grub2 shows me Windows 11 as an option. Can someone help me understand what I am doing and help troubleshoot the issue. Is there a way to edit grub2 entries fix this issue so that I get Windows boot option in grub2 all the time?
It works fine at times but apps keep crashing and also there is no video playback. Video plays but the screen is black. I observed this via Live Boot. I tried the Old Prime OS and video worked fine on the live boot without any issues save the GUI. Has anyone noticed any issues with the Prime OS? or is there any place I could find working solutions for Prime OS 2.0.1 (Beta)?
Thanks!
And are there any known issues with running it via LIVE Boot?
Any way to root?
jamescable said:
Any way to root?
Click to expand...
Click to collapse
Hi friend, I have some good news for you. Look at my mod build, there I added root through Magisk. And updated Kernel to version 5.15 (and also made a couple of small edits). If you're interested, here's the download link - > https://aopc.dev/t/prime-os-mod-by-joccers77.1377/
Prime OS Mainline 0.6.1 (Android 7)
1. Kernel updated to 5.15 (works better)
2. Fixed disk mounting error (oh... finally)
3. Root-access out of the box (Magisk)
4. Added ViperFX (sound mod + DDS)
5. Updated MESA (up to version 21)
6. System optimization (works faster)
7. Replaced native and sound libraries
Prime OS x64 2.1.0 (Android 11)
1. Kernel updated to 5.15 (works better)
2. Replaced native and sound libraries
3. Fixed disk mounting error (oh... finally)
4. Root-access out of the box (Magisk)
5. Added ViperFX (sound mod + DDS)
6. Updated MESA (up to version 21)
mod builds (for old hardware pc)
A11 Kernel 4.19.113 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 20.11
A7 Kernel 5.4.112 + Mesa 20.11
A7 Kernel 4.9.194 + Mesa 18.3.6
Will there be questions? - Write ME
To download, click on the name Builds.
Checked on PC
CPU : N3450 (6W)
RAM : 2+2Gb
iGPU: Intel HD 600
kamazok said:
Prime OS Mainline 0.6.1 (Android 7)
1. Kernel updated to 5.15 (works better)
2. Fixed disk mounting error (oh... finally)
3. Root-access out of the box (Magisk)
4. Added ViperFX (sound mod)
5. Updated MESA (up to version 21)
6. System optimization (works faster)
7. Replaced native and sound libraries
Prime OS x64 2.1.0 (Android 11)
1. Kernel updated to 5.15 (works better)
2. Replaced native and sound libraries
3. Fixed disk mounting error (oh... finally)
4. Root-access out of the box (Magisk)
5. Added ViperFX (sound mod)
6. Updated MESA (up to version 21)
mod builds (for old hardware pc)
A11 Kernel 4.19.113 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 20.11
A7 Kernel 5.4.112 + Mesa 20.11
A7 Kernel 4.9.194 + Mesa 18.3.6
Will there be questions? - Write ME
To download, click on the name Builds.
Checked on PC
CPU : N3450 (6W)
RAM : 2+2Gb
iGPU: Intel HD 600
Click to expand...
Click to collapse
hello Kamazok and thank you for this incredible effort to manage so many mods!
I have 1 question for you: I need to change the UiMode for 1 APP from "normal" (I think it is default) to "television" as this app has bad colors while playing streaming in every Android version higher than Nougat.
I know how to fix this behaviour in Android Boxes whose "TVsettings.apk" has a specific option to select TV among many UImodes. This app is SkyGo
thank you
Hello everybody,
Thanks to @TeamPrimeOS for your great work, which brings a nice Android Desktop to my Chromebook and @kamazok who fixes a shutdown-camera glich and adds root out of the box.
But I have a problem: I have no sound.
Using a Acer CB314-1H-C7SJ which is Geminilake and sound DA7219 (I think).
I found a post to use sof-firmware, but this is for Linux and I don't know how to port this to Android.
I tried official 2.1.2 and 2.1.3 as weil as the unofficial 2.1.0 from @kamazok all without luck.
Can someone help?
Best regards
my chrome keep crashing, any fix?
kamazok said:
Prime OS Mainline 0.6.1 (Android 7)
1. Kernel updated to 5.15 (works better)
2. Fixed disk mounting error (oh... finally)
3. Root-access out of the box (Magisk)
4. Added ViperFX (sound mod + DDS)
5. Updated MESA (up to version 21)
6. System optimization (works faster)
7. Replaced native and sound libraries
Prime OS x64 2.1.0 (Android 11)
1. Kernel updated to 5.15 (works better)
2. Replaced native and sound libraries
3. Fixed disk mounting error (oh... finally)
4. Root-access out of the box (Magisk)
5. Added ViperFX (sound mod + DDS)
6. Updated MESA (up to version 21)
mod builds (for old hardware pc)
A11 Kernel 4.19.113 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 21.1
A7 Kernel 5.10.32 + Mesa 20.11
A7 Kernel 5.4.112 + Mesa 20.11
A7 Kernel 4.9.194 + Mesa 18.3.6
Will there be questions? - Write ME
To download, click on the name Builds.
Checked on PC
CPU : N3450 (6W)
RAM : 2+2Gb
iGPU: Intel HD 600
Click to expand...
Click to collapse
i tried almost every browser, and it just keep crahsing. any fix? thank you for your wonderful works on PrimeOS.
also I want to try other version of prime OS. do you have any guide to completely uninstall PrimeOS?
I just delete and format the boot sector (back to NTFS)
via disk management ( press "win+r" then diskmgmt.msc )
Hello. I am using a Lenovo Flex 11. The OS works fairly well on it, but I was wondering if there was a way to enable the keyboard disconnect function on this 2-1 laptop? If I fold the laptop it will not disconnect the keyboard and thus the touchscreen keyboard does not come up. I can get around this by enabling the touchscreen keyboard in the physical keyboard settings, but my physical keyboard is still active if the laptop is folded.
I know a bit of Debian based linux, not sure what fork this is. Any advice would be appreciated!
traversone said:
hello Kamazok and thank you for this incredible effort to manage so many mods!
I have 1 question for you: I need to change the UiMode for 1 APP from "normal" (I think it is default) to "television" as this app has bad colors while playing streaming in every Android version higher than Nougat.
I know how to fix this behaviour in Android Boxes whose "TVsettings.apk" has a specific option to select TV among many UImodes. This app is SkyGo
thank you
Click to expand...
Click to collapse
any feedback on this topic?
wifi & Bluetooth not working in dell venus 8 pro.......
Is there a way to change the main storage amount of 3 GB in the image file? I'm not that tech saavy, however I have followed instructions. I'm using PrimeOS on a Fujitsu T901 (dual core 64bit) Running 64 bit PrimeOS with a very large partitioned drive, but main storage is way too small! (- aka the storage cache is too small even at 3GB) I'm only running noteshelf note taking for seminars and have run into issues with this limit. Thanks in advance for any links or advice. Willing to figure out root access If I can and mess with the image file as long as instructions are clear. I've backed up all my notes just in case anyway. It was a struggle to get it installed. It is not dual boot it is android primeos on its own and I only use linux as the other operating system. I might have access to a windows device if needed
As opposed to other options for an Android Laptop, at least it installs to begin with! A lot of bugs. I might, in fact, have to reinstall it atm. The UI keeps crashing. Everything is a learning process. I was on Fyde OS before trying Prime. So like Fyde I thought I could login to the play store and download my paid apps. So on Fyde I did a bulk download and it went fine. But on Prime, my UI has now crashed. Again, a learning process. TBH, I'm just glad it works. And how well it worked before I messed it up. For me, if its the amount of apps I downloaded at once lol. I'll just reinstall it and do an app at a time. I do like the settings directory. It has a feel of LOS settings directory. I was using the Plasma Live Wallpaper....And IT Was Dope on my Laptop. To install directly on your laptops hard drive. You would just navigate to advanced options when it first boots up. Then look for Auto Installation and click yes to everything for an easy install. I just wondered if it came rooted with SU? Anyways, I tried Bliss before this and it would not install at all. I even tried Android 86, but that's version 9. All in all, I know it's in development and I look forward to its final release. Having tried other similar platforms with no avail. This will definitely be my choice for Android Laptop Software! Maybe make a release with Magisk already installed lol (wishful thinking). Anyways, I like it. The way it reads all your devices really fast is great. Unlike Fyde, it shows much more control over files. You don't have to go in each viewer/player like Fyde and pick the directory manually. On Prime it reads files automatically. Which is important when you want to enjoy your favorite music player etc. OK I'm done lol have a blessed day!
My issue has been that auto install did not work. I had to boot by usb drive into mx linux and set up partitions and then use the regular manual install. Apparently the fujitsu t901 has some install issues with primeos. Had to make sure there was a ntfs partition and the rest fat32