Android Q hidden settings enablerCreated by @kingbri
Disclaimer: I am not responsible if you flash this and make your phone into a brick, blow it up, create nuclear war, etc. You are flashing this at your own risk (However, it's very likely this won't happen)
This is a simple magisk module that adds a script to your /system/bin directory
What it does: Shows android Q hidden settings for well-known features (example: Dark mode)
Current features:
Android Q dark theme (system-wide and app-forced)
Navigation bar tweaks (Removed back button and new Q quick switching mechanism)
How to use:
ADB
Enter an adb shell
enter the command "qmod"
Follow the instructions
On-phone
open terminal emulator
su
enter the command "qmod"
follow the instructions
You can also use this without root!Just grab the script by running this command:
curl https://raw.githubusercontent.com/bdashore3/q_tweaks/q_master/system/bin/qmod > /sdcard/qmod
and follow the steps
Steps:
Push the file to /sdcard
Enter an adb shell
cd to sdcard
chmod 0777 qmod
type "sh qmod"
follow the script
Downloads: https://github.com/bdashore3/q_tweaks/tree/releases
If you want to ask questions, here's the contact group for my work: t.me/KingDevel
Credits: MishaalRahman (for getting all his journal posts), paphonb (for the debug_pixel launcher), and anyone else who figured out these tweaks/were behind-the-scenes for this stuff.
Please put any hidden android Q features that you find in here (With the code or it won't be accepted) or open an issue on github along with the code necessary to enable that feature.
mine again
Thanks, this is mine
I am confused, is this a Magisk module to Enable hidden features that already exist in Android Q or a module to add Android Q features to Pie?
firesword14 said:
I am confused, is this a Magisk module to Enable hidden features that already exist in Android Q or a module to add Android Q features to Pie?
Click to expand...
Click to collapse
This mod just turns my tutorials into scripts:
Source 1: https://www.xda-developers.com/android-q-navigation-gesture-controls/
Source 2: https://www.xda-developers.com/android-q-toggle-dark-theme/
Good on ya @kingbri does the trick ?.
MishaalRahman said:
This mod just turns my tutorials into scripts:
Source 1: https://www.xda-developers.com/android-q-navigation-gesture-controls/
Source 2: https://www.xda-developers.com/android-q-toggle-dark-theme/
Click to expand...
Click to collapse
** into A script **
Update! (v1.1)
Changelog (In github q_master branch under "Add v1.1 commit"):
-Fix dark theming command
-Add Lockscreen clock styles, Desktop mode, and chat bubbles as options
-Change option input to numerical format
-Make things easier to read
The downloads are located here: https://github.com/bdashore3/q_tweaks/tree/releases
To contact me on Telegram, I am located here: t.me/KingDevel
Update! (v1.3)
Changelog (In github releases branch under "Add v1.3 commit"):
-Add iphone-style gestures
-Fix some missing stuff
-Add more documentation
-Add keycheck and a few options in installer
(Circumvents system not mounting)
For iphone-style gestures: No other nav bar tweaks are allowed!
You need the back button. All documentation on how to enable
is in the script, nav-bar tweaks, option 3.
The downloads are located here: https://github.com/bdashore3/q_tweaks/tree/releases
To contact me on Telegram, I am located here: t.me/KingDevel
Additionally, if anyone sees a new news post before I do about android Q hidden features (there are new ones popping up everywhere), follow the 2nd post in the O.P. If @MishaalRahman can post an article about this, that will be great rather than making seperate magisk modules for everything
Deleted. Duplicate post
Update! (v1.4)
Changelog (In github q_master branch under "Add v1.3 commit"):
-Improve iphone-like gestures documentation
-Update github documentation to use a curl command
(Non-root)The new curl command is in the OP, just run it in a terminal
Please follow the non-root instructions in the OP
To contact me on Telegram, I am located here: t.me/KingDevel
kingbri said:
Update! (v1.4)
Changelog (In github q_master branch under "Add v1.3 commit"):
-Improve iphone-like gestures documentation
-Update github documentation to use a curl command
(Non-root)The new curl command is in the OP, just run it in a terminal
Please follow the non-root instructions in the OP
To contact me on Telegram, I am located here: t.me/KingDevel
Click to expand...
Click to collapse
Will this work on latest Beta 2 patch?
Zehlek said:
Will this work on latest Beta 2 patch?
Click to expand...
Click to collapse
For me it causes issues especially with pixel launcher
With Q beta 2 update, nope. Changes to launcher so dev options limited. Now I did find that using this link instructions I could get file permissions to revert back to Pie. the "sandbox memory, files protection" is turned off. File managers and app can then access just like before. Now I started with a complete wipe, Q beta 2 factory image, adb enabled, run script,. As warned resets phone, I then added my apps, data, pics through device to device transfer.
https://developer.android.com/preview/privacy/scoped-storage#test-behavior-change
adb shell sm set-isolated-storage off
adb shell getprop sys.isolated_storage_snapshot
should return with flag = false
Your mileage may vary, data may be lost..... bla, bla, bla. Lawnchair v2 alpha works great too!
Related
Short Order Kitchen
By
KF2M
*** Please read the README.txt in the ZIP for changelog, and other useful information***
*** !!!!!!You MUST edit all remove_ files before using!!!!!***
*** !!!!!!You MUST edit all remove_ files before using!!!!!***
*** !!!!!!You MUST edit all remove_ files before using!!!!!***
This is a very simple kitchen for doing some quick mods to a ROM.
How many times you have a favorite ROM that you add some tweaks to it before flashing?
Then have to do it again when a new release comes out. Not fun.
This partially automates that task. It is written as a batch file. Yes, good old MS-DOS batch. Very simple, and in Windows 7 quite powerful. Everything is easily laid out, and menu-driven. The batch file is documented, and module so you can tailor it to your needs. It is portable with some changes to support your specific ROM, but in general supports most HTC Evo 4G LTE ICS ROM's.
This will not cook you ROM's like dsixdas' kitchen. This is much more simpler.
Have a basic understanding of MS-DOS batch if you want to mod this.
Must have a basic understanding of the Android file structure.
Have 7-Zip CLI, and GUI installed as well as included in your PATH.
This was developed using MeanROM so it is geared to that ROM
To use the ADB shell you MUST have the Android SDK installed, and adb pathed.
Support will be very limited. But I will be updating it from time to time with features/fixes.
This project is Open Source feel free to mod as you like. I have included some icons, media, and apps to get you started.
To install, and run
1. Extract preserving full paths.
2. Open a command prompt, and change to the extracted folder
3. Edit the removelist if you want to remove stuff from your ROM.
4. Add your favorite files to their respective folders for inclusion
5. Copy your ROM to the kitchen folder.
5. Type in at the prompt run.bat .
6. Have fun!
As always use at your own risk.
Current Release
------------------------
Release - v0.932 - Minor fixes
Download here
Release - v0.93 - Fixes, more options
Download HERE!
Release - v0.92 - More fixes, and some new options (FastBuild, and ADB shell)
Download here
Release - v0.90 - Lots for fixes, and changes. Please read the README file!!!
Download here
Release - v0.82 (I removed as much as I dare, included Holo Launcher. YMMV)
Download Here
Release - v0.80.1
Download here
Initial Release: v0.789
Download Here
Thanks to dsixda, mendozinas, mikeyxda, Haus, and all the other numerous outstanding XDA Dev's.
Usage
---------
To run.
Open a Command Prompt
Nagivate to the directory you put the kitchen
At the prompt type in: run THENAMEOFYOURROMHERE.zip
At the prompt type in the name you want to use for your new ROM
Once your work image is created you will be at the menu
Files to edit
-----------------
There are 4 files you can edit for removing stuff from your new ROM. They are:
remove_data
remove_resource
remove_system
remove_system_nosense
You can use either Notepad, or Wordpad to edit these files. Each line is starts with a #. If you want to remove that file delete the #, and the space after it. Every time you do a junk removal then that file is deleted.
You can also edit the run.bat file as well. You can add more menu's, more processes. Everything can be used as a template that you can use to expand the kitchen. I coded this batch file to be a modular, and as simple as possible. How you mod it is up to you. You are only limited by your imagination.
Changelog here
Changelog v0.932
________________
- More bug fixes
- Changed handling of uncompressed SystemUI.apk files that are near the size limit
Changelog v0.93
________________
- Supports all non-ODIN, Blobed ROM's
- Lots of bug fixes
- Code cleanup
- When initially run it will check for the remove_ files, and if they don't exist creates them
- Added an menu for common ADB commands (you MUST have ADB in your path statement)
Changelog v0.92
________________
- Added ADB Shell (you must have the Android SDK installed, and pathed to use)
- Changed the Sense removal option to a total nuke of Sense, widgets, and downloadable apps
- fixed bugs
- added more bugs
- corrected errors in spelling
- removed some debugging code
- you can now run from a desktop shortcut instead of opening a Command Prompt window
- added a FastBuild option (adds the signal icons, performs a nuke, builds then exits)
Changelog v0.90
________________
- Cleaned up the remove sense script (You can edit the remove_sense file for customizing your Sense removal)
- Squashed some bugs
- introduced new bugs
- Made Sense removal a separate menu item
- fixed a bug in the file renaming code
- The ROM folder is for the ROM('s) to be modded.
- The Output folder is where your finished ROM will be located.
Changelog v0.82
________________
- Added Sense Removal to the Junk Menu
Changelog v0.80.1
_______________
- Added a clean all function to the Junk menu
Changelog v0.79
________________
- Added JUNK_MENU
Can select what files to remove from:
data/app
system/app
system/customize/resource
Use the remove_% files to select which files to remove from your ROM.
- Minor fixes
Changelog v0.789
________________
Initial Release - Better have a can of RAID handy!
This sounds nice cant wait to try it
Sent from the depths of hell
will try it out, Thanks ,,,,,,
Version 0.80.1 is now available for download.
Sent from my EVO using Tapatalk 2
Sounds good, Thank You!
Sent from my EVO using Tapatalk 2
Thanks much for this.
Sent from my EVO using xda premium
scottspa74 said:
Thanks much for this.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No problem. I have a new version coming out shortly. Less bugs, more fixes. Before you run this batch file make sure all check the configurable files.
I can tell you this, the remove Sense on this next release will decimate Sense, and everything else. It is going to be a bare ROM app, and widget wise. Just working out a few quirks, and fixes.Between family, and work I don't get to spend too much time working on this. If anyone has fixes, or mods that they like to see included in future releases please post up the code, and specs.
New version up... Enjoy!
Release v0.93 is up...
Have fun cooking!
DELETED
Installation Instructions
Comming from a Pre "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file. (You WILL get an assert error!)
Read the warning on the screen.
Flash the ROM again!
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Comming from "Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839" ROM or later
Do a back up!
Do factory reset/ wipe (incl. /system)
In recovery: flash ROM zip file.
Ignore the warning on the screen.
If you have and international device flash the INT Kernel from the OP.
Flash Gapps
Reboot.
Change Log:
NOTE: All future changelogs will be attached below!
Slim-venturi-4.4.2.beta.1.7-UNOFFICIAL-20131221-1839 --> Slim-venturi-4.4.2.beta.1.9-UNOFFICIAL-20131223-1727 changes:
SlimRoms/frameworks_base:
2013-12-22: systemUI: fix notification dissapearing during recreation and possible <@Lars Greiss>
Code:
app crashes due that binded notifications are not there anymore
as well small cleanup
Change-Id: Ieed143088a55693fc56e6526e6b349d72b7b25cc
2013-12-22: Merge "fb: use SlimActions for torch tile and send as qualified user" into kk4.4 <@Gerrit Code Review>
2013-12-22: Merge "fb: lock statusbar recreation and release after ticker is done" into kk4.4 <@Gerrit Code Review>
2013-12-22: fb: use SlimActions for torch tile and send as qualified user <@Lars Greiss>
Code:
the broadcast and do not collape the panel bar
as well send with qualified user the IME switcher broadcast.
Change-Id: Ibad8b4f908e6d701999712f58b9996cd7a805fc4
2013-12-21: fb: lock statusbar recreation and release after ticker is done <@Lars Greiss>
Code:
In rare cases it happens that the ticker call just happened and a recreation
was called which results in a crah due of the missing binder.
To avoid it lock the recreation when a ticker call is in progress
and release it after it is done and notify the recreation to go ahead
Change-Id: Iedbf858bdb2ac2ad97563e344a571b384e17cfc7
2013-12-21: trds:[framework] dark images adjustments <@kroz>
Code:
Change-Id: Ie038c4a1aa535708c23f099fb5e836407e3d1603
SlimRoms/packages_apps_Camera2:
2013-12-22: TrueView Returns! <@Gerrit Code Review>
Code:
This adds the ability to view the complete sensor frame image
rather than the cropped preview used by AOSP to fill the entire
surface.
Change-Id: I79b14a165c66fa4f8b8e43598bd6a80e4de1c08b
2013-12-22: Fix Smart Capture label display <@Lars Greiss>
Code:
Change-Id: Ia3cceda0bf7fec21f2d019f07d416bfe8ebf211d
2013-12-22: Fixes Mako continues focus problem <@Lars Greiss>
Code:
rebase
Change-Id: I25187998003d357ec5ed3b10329fb39941f47bea
Signed-off-by: Josue Rivera <[email protected]>
2013-12-22: camera: Add ZSL support for Samsung/Qualcomm cameras <@Lars Greiss>
Code:
* Preview management for Samsung/Qualcomm cameras
Patchset 3: merge conflicts fixed
build errors fixed
PatchSet 4: codestyle corrections
Change-Id: Ib36bd21c9a76b45bced3eee2f25acc35b5d82b30
SlimRoms/packages_apps_InCallUI:
2013-12-21: Merge "TRDS: Dark InCallUI" into kk4.4 <@Gerrit Code Review>
2013-12-19: TRDS: Dark InCallUI <@kroz>
Code:
PS2:
- moved into right folder
PS3:
- redirect colors of original layout xml
Change-Id: I5bcfeb692bc4653e240df7c47216826452ee7d47
SlimRoms/packages_apps_Settings:
2013-12-22: Merge "First translation of Settings for KitKat" into kk4.4 <@Gerrit Code Review>
2013-12-18: First translation of Settings for KitKat <@gwindlord>
Code:
"Go To Sleep" paraphrased
Removed whitespace
Change-Id: I666cb60da3a0751ba1d4f351c2a46b1b159d9dd3
SlimRoms/packages_apps_Torch:
2013-12-22: Torch: add better error handling and added fallback mechanism <@Lars Greiss>
Code:
The handling of the Torch if an exception occured was very bad and
it was easy to break:
- notify the user with toast if the camera interface is not pressent
- catch the case that sys led controlled devices have wrong permissions
(eg third party kernel) and torch will completly crash.
Checking now if sys init is present.......if not successful
try to switch back to the camera interface.
- send broadcast change only if the state really switched
- when error occured turn off the service and the notification
- cleanup
- send broadcast with qualified users
Change-Id: Iabeb3b5f1c17d784a06c154f9a33e8d3d5214b7d
2013-12-21: make torch to a real system app <@Lars Greiss>
Code:
give it the correct permissions to allow to write
to sys interface with less permissions needed to
keep security alive
Thanks Alex for the hint to the hidden API
and gmillz for the idea
Change-Id: I44f70bdf3ecfb57ccac85eebe61e57a163bdf501
SlimRoms/vendor_slim:
2013-12-22: push to 1.9 <@Lars Greiss>
Code:
Change-Id: I4c4aab6fbd8440cda3649b1d77351aa0563dd15c
2013-12-22: push to 1.8 for weekly <@Lars Greiss>
Code:
waiting for feedback on last patches then we start jenkins
Change-Id: I1b8f5dcb6f8620506dfc4399b75c56802a3bd8e1
Older logs:
2013-12-22: clean up: movefiles.sh is no longer needed... <@Meticulus>
2013-12-22: overlay: SlimCenter overlay for ota. <@Meticulus>
Code:
-I've found that with just a few small adjustments you can redirect
SlimCenter to another url to check for updates.
2013-12-22: overlay: BOARD_USE_LEGACY_TOUCHSCREEN device tree flag. <@Meticulus>
Code:
-Everytime I repo sync my framework base commit to fix the touch screen
gets wiped out. In order to preserve it, I'm putting it in the overlay.
2013-12-20: ota: testing <@Meticulus>
2013-12-20: LVMv2: phase out the use of mmcblk0p14 as extra space. <@Meticulus>
Code:
-With the implementation of LVMv2, we don't need to use mmcblk0p14
(/vendor, /system/vendor) as extra space.
-mmcblk0p14 is now in the logical volume group "lvpool" along with
mmcblk0p13 and mmcblk0p16.
2013-12-20: ota: change device name from venturi to YP-G70 <@Meticulus>
2013-12-20: ota: removed beginning and ending spaces.. <@Meticulus>
2013-12-20: ota: ota update manifest. <@Meticulus>
Code:
-Initial commit of the ota manifest.
2013-12-19: slim.mk: build type switch. <@Meticulus>
Code:
-Switch from common full tablet to common full hybrid...
2013-12-19: init.venturi.rc: fix a small typo.. <@Meticulus>
2013-12-19: LVMv2: add lvm services to init.venturi.rc. <@Meticulus>
Code:
-This was left out of my initial commit here:
https://github.com/Meticulus/slim_device_samsung_venturi/commit/7ccd47c874f9a00c0397c8e8f17f3faaf72e256b
-This is absolutly neccessary for LVM...
2013-12-19: twrp: Correct screen resolution. <@Meticulus>
2013-12-18: LVMv2: initial implementation system(600M) <@Meticulus>
Code:
-Logical Volume Management
-The YP-G70 only has a 290m /system partition and this is not enough
to accomodate KitKat + full gapps. So, I'm implementing LVM so that
we can get dynamic volume resizing without having to change the under-
lying partitions.
-Partitions in Logical Group (Aprox 2.1G)
-- /dev/block/mmcblk0p13 (normally /system)
-- /dev/block/mmcblk0p16 (normally /data
-Logical volumes
-- /dev/lvpool/system (600M)
-- /dev/lvpool/data (100% remaining, aprox 1.5G)
-Installation Notes
--On the first flash, if the system logical volume is not present or
is less than 600M there is an assert error. This is so that if anyone
needs to backup information contained in /data, they can. In order to
proceed with the installation, the zip must be flashed a 2nd time.
--During the 2nd flash partitions in the logical group are wiped and
the logical volumes are created and formated then the /etc/fstab and
/etc/recovery.fstab are switched so that, when we hand everything off
to the normal rom installer, the new logical volumes are mounted.
-Reverting to a PRE-LVM ROM
--In the YP-G70 the "recovery", be it CWM or TWRP and in the kernel's
recovery-ramdisk. So in order to get a different recovery you just
flash a different kernel. So to get back to a PRE-LVM ROM, you just:
1. Reboot to recovery like normal.
2. Flash your PRE-LVM ROM like normal.
-- Note: All we really care about at this point is that the kernel
(boot.img) gets flashed. Ignore any other errors!
3. After the flash, Power off.
4. Hold volume up and power on, till you get to recovery.
5. Full wipe, including /system
6. Flash ROM + Gapps like normal
-Future Considerations
--LVMv2 allows us to quickly change the size of the system partition
as Android grows in size without having to manually repartition.
Manually repartitioning might cause unforseen problems with legacy
software.
-Meticulus
2013-12-17: recovery init: adb without /system <@Meticulus>
Code:
This allows "adb shell" to function when /system partition is not mounted
or for any reason /system/bin/sh is unavailable.
When /system IS mounted then adb uses mksh is used via /system/bin/sh
When /system IS NOT mounted then adb uses busybox via /sbin/sh
2013-12-14: Removed torch from build. <@Meticulus>
Code:
Torch isn't working at the moment anyways. May readd later!
2013-12-14: twrp: defined custom power key and fixed screen timeout problem. <@Meticulus>
2013-12-14: Initial commit <@Meticulus>
Super mine again!
BAH!! y u release while i'm at work....
Gonna test when i get home....
Flashy flashy, its like Christmas but better! no wrapping paper to clean up or relatives to dispose of.
Somehow I knew I would come on today to find KitKat available. Trying it now, will update later.
EDIT: No options for hardware buttons?
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I didn't really solve it, per say. I put in a cheap hack to change the permission of the directory: in the init.venturi.rc. I'll got some clean up to do, but I'll be pushing my device tree tomorrow and submitting some changes to yours so we can get CM11.
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
i'm having problems getting super user access, anyone else got this?
Lorddemonrage said:
i'm having problems getting super user access, anyone else got this?
Click to expand...
Click to collapse
My SU access is ok.
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
mr_ggcstop said:
Hello! Thanks for your work! I tested this rom, it's pretty nice. The only bug (except known) is that TWRP is not working on INTL kernel.
Click to expand...
Click to collapse
TWRP is a "known issue", if you read the OP. (workin' on it)
Lorddemonrage said:
had sometime to mess with it. my sd card is not showing up, lost super user access. other than that almost everything works fine.
elaborating, i can see sd card in file manager, but connecting to windows does not show sd card accessible, just the galaxy players internal memory
Click to expand...
Click to collapse
I am aware of the "2 cards in mass storage issue", but for the su problem, haven't had any issues .... developer-options-> root (or something like that)
joemhewitt said:
Does it need a wipe if coming from 4.3
Sent from my zx spectrum
Click to expand...
Click to collapse
yes including system:good:
iurnait said:
Very nice. How did u solve the dalvik cache issue?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
aznflawless said:
Will you be making a stock cm11 ROM in the upcoming weeks?
I would love to play with this ROM for the time being ^_^
Click to expand...
Click to collapse
No I am not. I can't maintain 2 Roms... I submitted patches to get CM11 working but someone else is going to have to build it...
@iurnait ???
Sent from my M470BSA using Tapatalk
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
bassbrick15 said:
When will the TWRP fix be released? My US player now, after the flash using Clockworkmod, will not be recognized in odin when in download mode. I love kitkat but i want to go back to my cm10.2 build. And the only way to do that as i know is to go to gingerbread and upgrade from there. but because of this issue i am stuck with TWRP and no os on my USA galaxy player 5.0. Please advise!!!!
Click to expand...
Click to collapse
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Been Waiting For This For Awhile Noe. Thanks Guys, I Guess With Patience Good Things Come. Hopefully The Same Can Be Said About The Rear Camera.
Sent from my YP-G70 using xda app-developers app
Meticulus said:
Do not ask for ETA's!
READ THE OP BEFORE FLASHING!!! THE OP CLEARLY STATES NOT TO FLASH UNLESS YOU KNOW WHAT YOU ARE DOING BECAUSE TWRP IS NOT WORKING!
Click to expand...
Click to collapse
Hi Meticulus!
First, let me thank you for all your time and energy spent in making this mod for an old device! I love my Player 5, but it is show it's age. I'm hoping your SlimKat 4.4.1 will breathe new life into it. (A shame Samsung stopped developing this line).
I have a Galaxy Player 5 running a rootedGingerbread 2.3.5 with CWM v5.0.2.7 (no TWRP)
Do you recommend any special preparation before applying SlimKat 4.4.1?
Since I'm using CWM, will I be able to restore back to Gingerbread using a current backup (just in case)?
As you might have guessed, I am not a frequent "mod"-er so I've fallen behind a bit.
Thank you for taking your time to help me and so many others!
AlmostVanillaAOSP Marshmallow 6.0.1_81 [MOI10E] ROM for the Nexus 5
Description
An "almost vanilla" AOSP-based Marshmallow ROM for the Nexus 5.
Disclaimer
I am not responsible for anything that happens to your device. By downloading and flashing or installing these zips, you automatically agree that I won't be held liable for anything that happens to your phone.
Background
AlmostVanillaAOSP is an AOSP-based ROM directly using Google's source code with a few functional modifications; these modifications are fully-sourced and easily-installed prior to building the ROM. Included modifications are designed to fix bugs, enhance security, and improve "in the field" function.
Many users prefer a "vanilla" version of AOSP, without added factory bloat and proprietary software; a basic version of AOSP is a great building block to create a custom-featured ROM, or it can be left as-is by users desiring to live outside Google's realm.
Users shouldn't see any visual or functional difference between this ROM and a vanilla AOSP build; all changes are "under the hood". Please note that there has been no attempt to remove functionality or user choice with this ROM.
If you're looking for a 100% pure AOSP ROM, please install BreckZeBoulay's UntouchedAOSP ROM IN THIS THREAD
Included Modifications
Enabled the Doze option: Google's Doze option (built-into the AOSP code base), is a set of rules that puts an idle phone to sleep, reducing battery drain. For Doze to work, you have to have Google Play Services (GApps) installed. If you don't have Play Services installed, nothing happens and the phone still works fine. For more details on Doze, read HERE.
Option to add Google's current WebView: The WebView included with AOSP Marshmallow is locked-in at version 52, and the only way it will get updated is by installing a later ROM. With the stock AOSP code, users have no option to upgrade to a newer version; trying to upgrade results in browser crashes and instability. This "fix" allows installing the "Android System WebView" from the Play Store (currently at version 58); the Play Store version is kept current by Google. If you choose not to install the Play Store WebView version, the included version works fine, although at an increased security risk due to not having updates. DO NOT REMOVE THE INCLUDED WEBVIEW VERSION! Keep the original version that's located in /system/app, if you install another version; it's not "bloat". The Play Store Android System WebView can be found HERE.
Addition of Sony's suggested (and disapproved) Power Menu reboot option: Sony made attempts to add a reboot option to the Power Menu in the AOSP code; their efforts were rejected. However, Sony generously posted the code changes needed to enable this option, and they are included in this ROM. An interesting read on Sony's attempts can be found HERE. For details on implementing this feature post-install, please read the "Implementing Reboot" section below.
Removal of broken AOSP applications (Browser, Calendar, Email, and Exchange): AOSP Browser, AOSP Calendar, and AOSP Email (and by extension, AOSP Exchange) are hopelessly broken. I refuse to put broken applications in a ROM, even for "completeness". The good news is that Lightning Browser, Etar Calendar, and K9 Mail are open source and even better than the originals. Look in the "Suggested Open Source Applications" section below for links to these apps.
Removal of LiveWallpapers: The LiveWallpaper bloat has been removed from the ROM. The LiveWallpaperPicker app remains, so the functionality is still there. They're something that few people (if any) actually use.
Updated Launcher Icons to Material theme: The Material Dialer Icon is usually the first item folks ask for in AOSP ROMs. The Calendar, Dialer, and Gallery launcher icons were borrowed from the Cyanogenmod Github. The QuickSearchBox and Music launcher icons were modified from the icon set provided by Rammist on this WEBSITE. No other changes were made to the apps other than their launcher icons.
Added Option to Utilize UnifiedNlp Location: UnifiedNlp is a FLOSS (Free/Libre and Open Source Software) Wi-Fi- and cell-tower-based geolocation tool for Android by MaR-V-iN. His XDA thread can be found HERE. All that's been done is the addition of a single entry (org.microg.nlp) during build to the list of the ROM's network location services. Users who don't add the UnifiedNlp app will see no change or function with the ROM. For details on implementing UnifiedNlp with this ROM, please review Post #2 in this thread.
Sources and Source Patches
Source tree:
Code:
https://android.googlesource.com/platform/manifest -b android-6.0.1_r81
Nexus 5 (GSM/LTE) binaries for Android 6.0.1 (M4B30Z):
Code:
https://developers.google.com/android/drivers
Source Patches Used for ROM Build:
Bloat
Broken
Dialer-Gallery2-Calendar-Search-Music - Launcher Icons
Doze
Reboot Icons <- Required for the Reboot patch
Reboot
WebView
UnifiedNlp
Patch Installation Prior to Building ROM:
Put patch(es) in the AOSP build folder. This is how the patches and icon images were installed:
Code:
patch -p0 < M4B30X_Reboot.patch
patch -p0 < M4B30X_WebView.patch
patch -p0 < M4B30X_Doze.patch
patch -p0 < M4B30X_Bloat.patch
patch -p0 < MOB31T_Broken.patch
patch -p0 < MOB31T_UnifiedNlp.patch
unzip M4B30X_Reboot_Icons.zip
unzip M4B30X_Dialer-Gallery2-Calendar-Search-Music_Icons.zip
find . \( -name \*.orig -o -name \*.rej \) -delete
NOTE on ".rej" and ".orig" generated files:
Patches that succeed but have ***ANY*** issue generate additional ".orig" files in the same folders as the original files.
Patches that fail generate a ".rej" extension file in the same folder as the original file. A failed patch must be investigated before proceeding further.
For example:
Code:
frameworks/base/core/res/res/values/config.xml
frameworks/base/core/res/res/values/symbols.xml
Both of the above files are modified by two or more patch files. An initial patch will work fine, but subsequent patches are noted with notices like "Hunk #1 succeeded at 306 (offset 1 line)". The patch applied fine, but the patch command is notifying you that when it went to apply the patch, the lines weren't where they were originally expected to be (shifted down XX number of lines). As long as the patch didn't fail with output like "Hunk #1 FAILED at 58.", you're good. However, even though the patch was successful, it still generates a "config.xml.orig" or a "symbols.xml.orig" file when there is a conflict.
Now the problem: those ".xml.rej" and ".xml.orig" files, despite having incorrect endings and not being actual ".xml" files, are treated during build as valid .xml files. Since the config.xml.orig and config.xml file are in the same folder and almost identical, the build will fail as it's seeing the duplication. AOSP appears to parse all files in certain folders, regardless of extension.
The following command will eliminate those ".orig" and ".rej" files, should they appear:
Code:
find . \( -name \*.orig -o -name \*.rej \) -delete
To revert installed patches, with the patches in the AOSP build folder:
Execute the following commands:
Code:
patch -p0 -R < M4B30X_WebView.patch
patch -p0 -R < M4B30X_Reboot.patch
patch -p0 -R < M4B30X_Doze.patch
patch -p0 -R < M4B30X_Bloat.patch
patch -p0 -R < MOB31T_Broken.patch
patch -p0 -R < MOB31T_UnifiedNlp.patch
find . \( -name \*.orig -o -name \*.rej \) -delete
NOTE: any icon images you've unzipped can't be reverted.
Known Bugs
None yet.
GPL
The kernel included with this ROM was pulled directly from the AOSP source tree. No modifications have been made to any of the kernel sources or the kernel itself.
For the source tree for the AOSP-supplied kernel, please check HERE.
The GPL v2 license can be found HERE.
AlmostVanillaAOSP ROM Download
LATEST: AndroidFileHost | Mediafire
AlmostVanillaAOSP[6.0.1_r81-MOI10E]Hammerhead-20171004.zip
SHA256: 7fcdb2dd0e349b1b99eefc55f9e49b0fd07c9e2ad1054848840019a88434c2b5
OLDER RELEASES can be found here: AndroidFileHost
AOSP Changelogs - Does not include AlmostVanilla changes.
Generated using the following bash script:
Code:
#!/bin/bash
#
#
#
repo forall -c '
if git rev-parse android-6.0.1_r79 >/dev/null 2>&1
then
git log --oneline --no-merges android-6.0.1_r79..android-6.0.1_r80
else
git log --oneline --no-merges android-6.0.1_r80
fi
' | cat
android-6.0.1_r79 to r80
Add-on Downloads - In TWRP-flashable format.
Radio/Modem Download, Version M4B30X_M8974A-2.0.50.2.30: AndroidFileHost | Mediafire
- The current modem-radio for the N5 is M8974A-2.0.50.2.30, from the M4B30X ROM.
Video Green Line Fix, Version 6.0.1_r77-M4B30Z: AndroidFileHost | Mediafire
- Fixes the green line along the edge of video frames.
- Pulled from the latest factory N5 ROM, M4B30Z_6.0.1_r77.
Qualcomm Time Service Fix, Version 6.0.1: AndroidFileHost | Mediafire | Older Versions
- Fixes the date and time resetting on successive boots.
UnifiedNlp(GAPPS), Version 1.6.8: AndroidFileHost | Mediafire
- A flashable version of UnifiedNlp(GAPPS) that installs to /system. Only for AlmostVanillaAOSP[6.0.1_r79-MOB31T]Hammerhead-20170418.zip or later versions WITH built-in UnifiedNlp support.
- For details on implementing UnifiedNlp with this ROM, please review Post #2 in this thread.
N5 Boot Animations: This THREAD has an assortment of N5 flashable and tested bootanimations.
Debloating Tools: Look at this thread THREAD for debloating scripts to eliminate unwanted or redundant applications.
Wallpapers
AOSP doesn't include any wallpapers for the Launcher/Home Screen. To help beautify your N5, I've included some links to stock Android and Nitrogen OS wallpaper in Post #3.
Installation
PLEASE ASK QUESTIONS IF YOU HAVE THEM!
General ROM & GApps Install Procedure:
--------
PREPARATION:
1. Flash current factory ROM via PC (to get current modem radio)
2. Install TWRP via adb
3. Create empty GApps text files as per directions HERE
4. Copy ROM, empty text files, and install items to phone from PC
FLASH & INSTALL:
1. Boot to TWRP
2. Reboot to recovery (TWRP) from within TWRP
3. Wipe everything but internal storage
4. Flash the ROM
5. Flash a bootanimation, TimeService, Green line fix
6. Reboot to System
7. Configure Time, WiFi, APN, Reboot Menu
8. Reboot to TWRP
9. Flash GApps (Delta GApps MM PROCEDURE
10. Reboot to System
11. Set permissions for GApps (Contacts, Play Store, Google Play Services)
12. Reboot back to System
13. Setup Google Account
14. Install Play Store Apps
15. Install APKs manually
16. Reboot to TWRP
17. Run debloat script.
18. Reboot to TWRP
19. Flash UnifiedNlp app
20. Install SuperUser (PHH's is fine)
21. Reboot to System.
22. Done
#6, rebooting to System BEFORE flashing GApps, is VERY important.
GOOD LUCK!
Screen Shots
{
"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"
}
FAQ
Q: How can I verify the running WebView version of my ROM?
A: Use HTML5test WebView from HERE.
Q: Does Doze work in this build?
A: Yes. You'll need GApps installed for it to work properly. You do not have to enable anything; it is active by default.
Q: How can I check and see if Doze is enabled on this ROM?
A: Download and install the APK from this THREAD.
Q: My date and time keeps resetting on successive boots?
A: Solution is to install the Qualcomm TimeService app (a proprietary application) - the 6.0.1 version is available HERE
Q: Can I use this ROM with Android Pay?
A: No. Only approved factory ROMs from Google can use Android Pay. If you want Android Pay on the Nexus 5, install a Marshmallow factory image.
Q: Where can I get the Marshmallow bootanimation? I'm only seeing the AOSP default framework bootanimation.
A: Try Post #1 in this Boot Animation Collection.
Q: Where can I find your build tree?
A: There is no build tree for this ROM, other than the full source code as provided by Google. Any modifications to this source code are noted under "Patches".
Q: Can you add new features to this ROM?
A: The goals of this ROM are a stock AOSP feel and security. "Features" other than bug-fixes and security enhancements aren't a priority and probably won't be added.
Q: Which GApps are recommended?
A: Deltadroid's GApps are highly recommended using this installation PROCEDURE
Q: How do I install GApps?
A: A general procedure to install ROM with GApps:
Don't flash the ROM together with GApps in the same ZIP queue because this will cause the Installation Wizard to run on first boot. Due to Google Play permissions errors the Wizard will keep crashing and you won't be able to bypass this. Solution:
1. Boot to TWRP
2. Reboot to recovery (TWRP) from within TWRP
3. Wipe everything but storage
4. Flash the ROM
5. Flash a bootanimation, TimeService, Green line fix
6. Reboot to System
7. Configure Time, WiFi, APN, Reboot Menu
8. Reboot to TWRP
9. Flash GApps
10. Reboot to System (Yes, you'll probably get Play Services "FC" messages until you perform #11, below)
11. Immediately toggle application permissions to "ON" under "Settings -> Apps -> ... -> System show" for:
Code:
- Google Contacts Sync
- Google Play Services
- Google Play Store
12. Reboot back to System
13. Setup Google Account via "Settings -> Accounts -> Add account -> Google"
14. Install Play Store Apps
15. Install APKs manually
16. Reboot to TWRP
17. Run debloat script.
18. Reboot to TWRP
19. Install SuperUser (PHH's is fine)
20. Reboot to System.
21. Done
Q: My Google Play Store / Google Play Services / Apps keep crashing?
A: This is a permissions issue. Please read the "Which GApps are recommended?" answer above.
You can try System Settings > Apps (top right menu button) > Show System,
and set the following to resolve most crashes:
Google Contacts Sync > Contacts permission
Google Play Services > All permissions
Google Play Store > All permissions
Q: Can you patch the ROM to deal directly with the GApps permissions issue?
A: No. It's a security policies issue, and there's no desire to override those policies.
Q: Where is the System Tuner UI?
A: Enable Developer Options (under "About Phone", tap "Build Number" seven times), then long-press the settings icon in the notification shade/bar.
Q: How do I get root?
A: PHH's SuperUser is highly recommended. Install the SuperUser APK (F-Droid or Play Store), then flash the superuser.zip from HERE. It works flawlessly, and it's open source.
Q: Can I use this ROM with MultiROM?
A: UntouchedAOSP users were successful with MultiROM. AlmostVanillaAOSP should work equally-well.
Q: AOSP Calendar (and Etar Calendar) won't sync with my on-line Google calendar. How can I make syncing work?
A: Flash the Google Calendar Sync addon for 6.0.0+ add-on from this THREAD, located under "Additional Kitkat, Lollipop, Marshmallow, and Nougat gapps addons". Ensure that permissions are granted in Settings -> Apps for "Google Calendar Sync". You'll need to enable "Show system" under the ". . ." in the upper right of the Apps window,
Q: I get a green line on one side of the frames when recording video. How can I fix this?
A: Go to the "Add-on Downloads" section in this post and get the "Video Green Line Fix" download.
Q: I'm having issues with Location and certain apps (Chronus, f.lux, Google Fit, etc.). How can I fix this?
A: This isn't a ROM issue; it's an AOSP issue. Review POST #2 in this AlmostVanillaAOSP thread for a solution using UnifiedNlp. For a long, detailed answer, look at Mar-v-in's initial response in this GITHUB POST. Hopefully the following will be a short-enough summary:
Google started with an open Location API that was used for AOSP and Google's factory ROMs.
Google created a new Play Services Location API that isn't included is AOSP code and it's only included in factory ROMs.
Google recommends that developers use the newer, closed API version.
Despite the fact that there are few differences between the old and new API, some developers are migrating solely to the new, stranding AOSP users.
Possible solutions for those AOSP users not having access to the new Location API:
Use the solution in POST #2 of this thread.
Forget about custom ROMs, only install factory ROMs (yeah, right!).
Only use and support apps that use the open Location API (all of the applications listed in post #1 of this thread -- requiring Location -- under "Suggested Open Source Applications" support the older Open Location API).
Ask developers if they're willing to modify their applications to fall-back to the open API if the Google one isn't available, or just use the open API.
For other AOSP ROMs, use the procedure as outlined by @alessio89g in this POST
Q: How about a Nougat ROM?
A: Until things stablize on the development front, no. There are driver issues for Nougat on the N5 that have yet to be resolved. It was hoped that there'd be a very vanilla Nougat N5 build, with very detailed modifications of the source tree; documented changes seem to be all over the place, with developers more focused on "features" than straightforward builds. There is a "CleanAOSP" Nougat ROM, but I don't know much about it.
Implementing Reboot
Activate Developer Options: Go to "Settings -> About phone", scroll-down to "Build number", and tap it seven (7) times (first image).
Activate System UI Tuner: Swipe the top of the screen twice, until you get the below image. Long-press the gear icon. When you let go, a wrench icon appears (second image).
Go to "Settings -> System UI Tuner", toggle "Show restart in global actions menu":
Go to "Settings -> Developer options", scroll down and verify "Restart shortcut" is toggled:
NOTE:
"Developer options -> Restart shortcut" and
"System UI Tuner -> Show restart in global actions menu"
are tied together; toggling one automatically toggles the other.
Either method will activate the Reboot menu.
Suggested Open Source Applications
AdAway (requires root) - XDA
Add to Calendar - F-Droid
Amaze File Manager (root capable) - F-Droid | Play Store
AnySoft Keyboard - F-Droid | Play Store
Barcode Scanner - F-Droid | Play Store
Battery Widget - F-Droid | Play Store
Calendar Widget - F-Droid | Play Store
Etar Calendar- F-Droid | Play Store
Flym News Reader - F-Droid | Play Store
Forecastie (uses Open Location API) - F-Droid | Play Store
K9 Mail - F-Droid | Play Store
Lightning Browser - F-Droid | Play Store
Mathdroid - F-Droid | Play Store
MuPDF - F-Droid | Play Store
No-Frills CPU Control (requires root) - F-Droid | Play Store
Open Camera - F-Droid | Play Store
QK SMS - F-Droid | Play Store
QuickDic - F-Droid | Play Store
Simple Gallery - F-Droid | Play Store
SMS Backup+ - F-Droid | Play Store
Solitare CG - F-Droid | Play Store
Turbo Editor - F-Droid | Play Store
Vanilla Music - F-Droid | Play Store
VLC (ARMv7) - FTP | FTP-testing | Play Store
Thanks:
@BreckZeBoulay - for inspiration, guidance, keeping up the good fight, and teaching me how to build a ROM
@Deltadroid - for an awesome GApps package, and listening to users
@MattDN93 - for listening to users and being a cheerleader
@Scott - for his incredible walkthrough in this THREAD
Using UnifiedNlp(GAPPS) with AlmostVanillaAOSP:
What is UnifiedNlp(GAPPS)?
The UnifiedNlp(GAPPS) tool (application) works WITH an installed version of Google's GApps to enhance Location capabilities on AOSP ROMs; the XDA thread for this tool can be found HERE.
Why do we need UnifiedNlp(GAPPS)?
Developer MaR-V-iN provides a detailed response in his initial reply to this GITHUB POST. The short version is:
Google started with an open Location API that was used for AOSP and Google's factory ROMs.
Google created a new Play Services Location API that isn't included in AOSP code and it's only included in factory ROMs.
Google recommends that developers use the newer, closed API version.
Despite the fact that there are few differences between the old and new APIs, some developers are migrating solely to the new API, stranding AOSP users.
Simply put, a growing list of applications (Chronus, f.lux, Google Fit, etc.) refuse to work with the older Open Location API; UnifiedNlp(GAPPS) adds functionality to get these unusable apps working on AOSP ROMs.
How does AlmostVanillaAOSP support UnifiedNlp(GAPPS)?
AlmostVanillaAOSP now includes a build patch (found in Post #1, under "Sources and Source Patches") that adds "org.microg.nlp" to the Location Services providers. It's a simple two-line addition (including one line for a comment). AlmostVanillaAOSP DOES NOT install the UnifiedNlp app; that's up to the user to decide if it's needed or wanted. A user opting to NOT install the UnifiedNlp app will see no performance or functional changes.
Notes
There is a UnifiedNlp(noGApps) version available. It's designed to work with the MicroG Services (an open substitute for Google Play Services). The directions in this post DO NOT apply to the "noGAPPS" version of this application.
Xposed: AlmostVanillaAOSP versions 20170418 and later have support for UnifiedNlp "compiled-in". There should be no need to install the UnifiedNlp Xposed module to get the app/tool to run.
The UnifiedNlp(GAPPS) tool must reside in /system, not in /data; the flashable zip will make installation much easier.
When installed properly, the UnifiedNlp(GAPPS) tool WILL NOT display under the Launcher Apps Menu; you'll find the tool listed under Settings -> Location.
Setup
1. Install AlmostVanillaAOSP[6.0.1_r79-MOB31T]-20170418, or a later ROM revision.
- Follow the suggested install process listed under "Installation" in Post #1.
2. Flash the the UnifiedNlp(GAPPS) app/tool.
- Found in Post #1, under "Add-on Downloads"
- This flashable version of UnifiedNlp is designed to work WITH GApps
3. Install your choice of UnifiedNlp "backend" APKs.
- See the "Backends" list below.
- Should be "side-loaded" via ABD or installed via file manager.
- You can install as many backends as you desire, but you should only have one active.
- The Apple, Mozilla, and OpenBMap backends are "interesting" for our purposes WITH GApps, and should be prioritized.
4. Go to System Settings --> Location:
- Ensure "Mode" is set to either "High accuracy" or "Battery saving", NOT "Device only".
- Ensure that "UnifiedNlp Settings" is listed under "Location services"
5. In System Settings --> Location --> Location services --> UnifiedNlp Settings:
- Enter "Configure location backends", add and configure desired backends.
- Return to "UnifiedNlp Settings".
- Enter "Self-Check", ensuring that all boxes are checked.
Backends
Again, the Apple, Mozilla, and OpenBMap location backends are probably best for easiest compatibility WITH GApps.
Location Backends:
Apple UnifiedNlp Backend - UnifiedNlp location provider (Apple WiFi) - F-Droid
UnifiedNlp backend that uses Apple's service to resolve wifi locations
MozillaNlpBackend - UnifiedNlp location provider (Mozilla) - F-Droid
UnifiedNlp backend that uses Mozilla Location Services to resolve locations (AKA IchnaeaNlpBackend).
OpenBmapNlpBackend - UnifiedNlp location provider (Openbmap) - F-Droid
UnifiedNlp (no GAPPS) backend that uses OpenBmap.
Address Lookup Backends:
NominatimNlpBackend - UnifiedNlp geocoding provider (MapQuest Nominatim) - F-Droid
UnifiedNlp (no GAPPS) backend that uses MapQuest's Nominatim service (based on OpenStreetMap) for geocoding.
Database Location Backends:
LocalGsmNlpBackend - UnifiedNlp location provider (local GSM database) - F-Droid
UnifiedNlp (no GAPPS) backend that uses local GSM data to resolve user location. Create a database using data from OpenCellId and/or Mozilla Location Services CSV files.
LocalWifiNlpBackend - UnifiedNlp location provider (local WiFi database) - F-Droid
UnifiedNlp (no GAPPS) backend that uses locally acquired WiFi AP data to resolve user location. Consists of two parts sharing a common database. One part passively monitors the GPS. If the GPS has acquired and has a good position accuracy, then the WiFi APs detected by the phone are stored.
Wallpapers
AOSP doesn't include any wallpapers for the Launcher/Home Screen. Here are some links to beautify your N5; all of these images will automatically scale properly on the N5:
Stock Ice Cream Sandwich - Individual files | Full ZIP - 960x853 images
wallpaper_architecture | wallpaper_bubblegum | wallpaper_canyon | wallpaper_chroma
wallpaper_escape | wallpaper_fiber | wallpaper_fidelity | wallpaper_flora
wallpaper_kepler | wallpaper_leaf | wallpaper_noir | wallpaper_outofthebox
Stock Jellybean - Individual files | Full ZIP - 1440x1280 images
wallpaper_01 | wallpaper_02 | wallpaper_03 | wallpaper_04
wallpaper_05 | wallpaper_08 | wallpaper_09 | wallpaper_10
wallpaper_11 | wallpaper_12
Stock Kitkat - Adjusted - Individual files | Full ZIP - Scaled to 1920 pixels high
default_wallpaper | wallpaper_15
wallpaper_16 | wallpaper_17 | wallpaper_19 | wallpaper_20
wallpaper_22 | wallpaper_50 | wallpaper_51
Stock Lollipop - Adjusted - Individual files | Full ZIP - Scaled to 1920 pixels high
wp_arc_001 | wp_arc_003 | wp_arc_004 | wp_geo_1243
wp_geo_1557 | wp_geo_2102 | wp_geo_2167
wp_geo_2170 | wp_geo_2278 | wp_paper_001
Stock Marshmallow - Adjusted - Individual files | Full ZIP - Scaled to 1920 pixels high
wallpaper-kleiner-google-blue | wallpaper-kleiner-google-red | wp_001
wp_002 | wp_003 | wp_004 | wp_005
wp_006 | wp_007 | wp_008
wp_009
Stock Nougat - Adjusted - Individual files | Full ZIP - Scaled to 1920 pixels high
wallpaper-001 | wallpaper-002 | wallpaper-003 | wallpaper-004
wallpaper-005
Stock Oreo - Adjusted - Individual files - Scaled to 1920 pixels high. Only one image at this time.
Nitrogen OS - Individual files | Full ZIP - 2160x1920 images downloaded from HERE - Simply stunning
nos_01 | nos_02 | nos_03 | nos_04
nos_05 | nos_06 | nos_07 | nos_08
nos_09 | nos_10 | nos_11 | nos_12
nos_13 | nos_14 | nos_15 | nos_16
nos_17 | nos_18 | nos_19 | nos_20
nos_21 | nos_22 | nos_23 | nos_24
Post #4 reserved.
Post #5 for me
Glad to see you sharing your job !
All options you propose, I do them after installation of Untouched with flashing zips and exposed. I think this rom could be my daily rom for now.
Bye bye Untouched, hello Almost ! :laugh:
And I make a suggestion !
Build a AOSP kernel with k-exec patch for MultiRom users !
May be it's a little off topic but it could be included in the Almost zip no ?!
BreckZeBoulay said:
Post #5 for me
Glad to see you sharing your job !
All options you propose, I do them after installation of Untouched with flashing zips and exposed. I think this rom could be my daily rom for now.
Bye bye Untouched, hello Almost ! :laugh:
And I make a suggestion !
Build a AOSP kernel with k-exec patch for MultiRom users !
May be it's a little off topic but it could be included in the Almost zip no ?!
Click to expand...
Click to collapse
Please keep Untouched; it needs to exist
I'm guessing that should such a kernel already exist, you've have installed it by now. For humor, I'll take a look if you can show me the patch.
What am I missing, under-the-hood-wise, from this ROM? I'm mostly concerned about security and fixing broken things.
Are there items missing from the FAQ?
@androcraze thanks for this great ROM but pls add screenshots.
Barbiox Dogg said:
@androcraze thanks for this great ROM but pls add screenshots.
Click to expand...
Click to collapse
It's Vanilla AOSP!
OK, I'll see what I can do. A screenshot of what? Apps? Desktop? What items do you think will visually give more info about this ROM?
Will this be moving up to 7.0 build soon?
cell2011 said:
Will this be moving up to 7.0 build soon?
Click to expand...
Click to collapse
Soon? No. Please read the FAQ.
EDIT: I'm hoping that I can start something with 7.0 soon, but despite building and patching things, I'm not a "coder". At this point, I'm not seeing a detailed, basic list of things required get get AOSP Nougat going on the N5. Viewing git repos (for those developers that actually bother to post changes) is a cluttered mess, without much explanation about why a commit was included.
Great job..
BreckZeBoulay said:
And I make a suggestion !
Build a AOSP kernel with k-exec patch for MultiRom users !
May be it's a little off topic but it could be included in the Almost zip no ?!
Click to expand...
Click to collapse
I see the MultiROM patch and what it's for.... Do other developers make a kernel that works with Untouched and AlmostVanilla ROMs that supports MultiROM?
Right now, building a kernel looks do-able (I used to do it under Linux, and instructions for the N5 look straightforward). I wouldn't mind adding patches to change the scheduler from cfq to deadline, and drop the CPU minimum speed; it would get rid of an app that I have to install every time to do just that.
What's the advantage of including MultiROM support with this ROM vice flashing another kernel (other than the extra flashing step)?
androcraze said:
I see the MultiROM patch and what it's for....
Do other developers make a kernel that works with Untouched and AlmostVanilla ROMs that supports MultiROM?
What's the advantage of including MultiROM support with this ROM vice flashing another kernel (other than the extra flashing step)?
Click to expand...
Click to collapse
Just for information :
http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
EX, Blue spark, Franco and may be others...
Just to have a stock AOSP kernel up to date.
At this time, I use EX because I need a kernel with k-exec patch and up to date.
But a stock kernel (with patch) is enough.
Anyway, it's not a priority at all.
---------- Post added at 08:32 AM ---------- Previous post was at 08:31 AM ----------
androcraze said:
OK, I'll see what I can do. A screenshot of what? Apps? Desktop? What items do you think will visually give more info about this ROM?
Click to expand...
Click to collapse
Take the screenshots of Untouched
And your paint shoped screenshots for System tuner are uglyyyyyy
BreckZeBoulay said:
Just for information :
http://forum.xda-developers.com/google-nexus-5/orig-development/mod-multirom-v24-t2571011
EX, Blue spark, Franco and may be others...
Just to have a stock AOSP kernel up to date.
At this time, I use EX because I need a kernel with k-exec patch and up to date.
But a stock kernel (with patch) is enough.
Anyway, it's not a priority at all.
---------- Post added at 08:32 AM ---------- Previous post was at 08:31 AM ----------
Take the screenshots of Untouched
And your paint shoped screenshots for System tuner are uglyyyyyy
Click to expand...
Click to collapse
I'll take a look at the MultiROM patch. If it won't affect users in any way (other than the ability to use MultiROM), then it might be worthwhile.
I like my paint-shopped images; they convey the exact message that I wanted them to I was actually more worried about the file size and image dimensions than artistry. I'll have to make newer ones when I get a chance.
I'll get some better screen shots.
androcraze said:
I'll get some better screen shots.
Click to expand...
Click to collapse
Because you are my friend of AOSP :
https://drive.google.com/file/d/0B02Btet3um2pd0tleDgyWjZ4T00/view?usp=sharing
(if you are interested )
Tell me when I can remove it.
BreckZeBoulay said:
Because you are my friend of AOSP :
https://drive.google.com/file/d/0B02Btet3um2pd0tleDgyWjZ4T00/view?usp=sharing
(if you are interested )
Tell me when I can remove it.
Click to expand...
Click to collapse
Got 'em!
Yeah, they look a LITTLE better.... Not that home-made, I-was-busy-so-I-had-my-kid-make-them feel, but I'll struggle with them.
Thanks
pls add screenshots.
tiixman said:
pls add screenshots.
Click to expand...
Click to collapse
Will do this evening. @BreckZeBoulay was kind enough to help with creating them. I just need some time back at my desktop to play.
Today's Material Icon Day!
Yes, I have some screenshots included.
Added a new build with Material icons for Dialer, Calendar, QuickSearchBox, Music, and Gallery.
What do you think?
Man, you should've mentioned your ROM restores the stock system recovery...
░▒▄█▀▄░ █▀▄ █▀▀▄ █▀▀ █▄░█ ▄▀▄ █░░ ▀ █▄░█ █▀▀░░▒▐█▀▀▄ ▄▀▄ █▄░▄█
▒▐█▄▄▐█ █░█ █▐█▀ █▀▀ █░▀█ █▀█ █░▄ █ █░▀█ █▀▀░░▒▐█▒▐█ █░█ █░█░█
▒▐█░▒▐█ ▀▀░ ▀░▀▀ ▀▀▀ ▀░░▀ ▀░▀ ▀▀▀ ▀ ▀░░▀ ▀▀▀░░▒▐█▀▄▄ ░▀░ ▀░░░▀
Key Features
Based on @foobar66 GoogleWiz ROM
NX Kernel
Samsung SoundAlive Dolby Atmos
Shell Script Advanced Features (SSAF) *See post #2
Updates will come in small service packs instead of a complete ROM update unless necessary
Samsung Gear might work out of the box
Removed some tweaks that I deemed useless.
Removed a few Google apps (Drive, Map, YouTube, etc) from the ROM, you can install them from Play Store instead
Emergency Launcher, UltraPowerSavingMode, SmartCapture, SmartSwitch, LiveWallpaper
Removed GoogleWiz's customizing script
Installation
Backup is always recommended
You should be able to dirty flash from stock/GoogleWiz ROM
You might not be able to boot, which is why 1. is important
Install any patch or cumulative update zip.
Adrenaline Experience
Some apps that I personally use and recommend:
SolidExplorer
SwiftBlack
Fluid Navigation Gestures
Download
*Feel free to mirror, however, monetizing the download link in any way is strictly prohibited.
Google Drive
Patches & Cumulative Update
Bootloader
Source
GITHUB: Shell Script Advanced Features
Credit
@foobar66
@SoLdieR9312
@Noxxxious
@xpirt
amirzaidi for Pixel Launcher
Shell Script Advanced Features
Everything that can be done in shell script shall be done in shell script.
You will need to install a terminal emulator from PlayStore to use this function.
Current functions:
Remap Bixby Key
Change Device Name
Max Volume Warning Toggle
Enable Stereo Speaker
Navigation Bar Toggle
Immersive Mode
Set DNS
Powercfg by yc9559 @ CoolApk [EXY8895]
Host File Based Adblock
Service Disabler
Set big Cluster Max Freq
Set LITTLE Cluster Max Freq
Script OTA Self Update
Reboot Device
Reboot into Recovery
To use, type the following in a terminal emulator
Code:
su
cfg
Code
Issues
TODO/Progress
Wiki
Credits
Changelog
v1.0 - The Late Santa [26 Dec 2018]
Initial Release.
v2.0 - WorstJet [13 Jan 2019]
Reverted Samsung Camera to stock
Samsung Gallery is back to the party
Added quite a lot of files that are related to VOLTE/VOWIFI (credit), you will need to flash CSC installer to install your CSC files
NX Kernel R19
Magisk v18.0
Almost up-to-date SSAF
Flashable Update Zip
[Patch] - Smaller fix, you need to install all patches according to the number, you do not need to reboot in between patches. (Flash 1.0 first, then 2.0, 3.0 ...)
[Cumulative Update] - Bigger update containing all the previous small patches.
WorstJet
-Nothing available as of now
Previous Version(s)
The Late Santa
[Patch 1.0] 26122018
Enabled navigation bar
Added Project WIPE by yc9559 @ CoolApk, default setting is set to [Balance]
Changed config to cfg for easier access
[Patch 2.0] 27122018
Added GearManagerStub.apk
Added Launcher from amirzaidi
[Patch 3.0] 27122018.2
Updated custom menu to include adblock and service disabler
[Patch 4.0] 30122018
Fixed permissions
Minor update to SSAF
Service disabler in SSAF will now run in complete silence
Enabled UHQ tile in csc
[Patch 5.0] 31122018
SSAF now able to set DNS properly
SSAF now able to change big cluster max freq
[Patch 6.0] 03012019
SSAF now able to grab dependencies from GitHub if any is missing
SSAF now able to change LITTLE cluster max freq
Minor fixes to powercfg
[Patch 7.0] 05012019
SSAF now able to enable stereo speaker
Thanks! Haven't been able to download the ROM you're basing yours as it always hangs for me with megaupload, will try yours as I have better luck with gdrive. Slds.
well stuck on android is starting
Android is starting and no navbar,even going for settings and reenable it
pbls said:
Android is starting and no navbar,even going for settings and reenable it
Click to expand...
Click to collapse
I left the navigation bar disabled in build.prop accidentally
Edit the last line in build.prop:
Code:
qemu.hw.mainkeys=1
to
Code:
qemu.hw.mainkeys=0
and reboot.
or use the custom menu to re-enable it then reboot
or edit the build.prop and reflash ROM
EDIT:
or flash the attached flashable patch zip
how do i install the rom?
well the navbar is back and still stuck at android is starting
ps: this rom doesnt have a launcher thats why i keep stuck at android is running
Is Volte vorking? Foos original rom hasn't.
Good job ! I will test the rom i i will give u a feedback !
You will planning to add some more mods ?
Thanks.
the ROM doesn't have a launcher,you must go to the Google play to install one
pbls said:
the ROM doesn't have a launcher,you must go to the Google play to install one
Click to expand...
Click to collapse
Ah.. now I know why it doesn't boot.
navaskp said:
Is Volte vorking? Foos original rom hasn't.
Click to expand...
Click to collapse
It isn't working either
xtmzone said:
Good job ! I will test the rom i i will give u a feedback !
You will planning to add some more mods ?
Thanks.
Click to expand...
Click to collapse
I'd refrain from adding 'mod' myself that requires to be redone every security update as it wastes time.
Feature will be added to the custom menu instead as that is portable, work across updates and even devices.
Everything that's doable in shell script shall be done in shell script.
ImbaWind said:
AdrenalineROM Custom Menu
You will need to install a terminal emulator from PlayStore to use this function.
Current functions:
Remap Bixby Key
Change Device Name
Max Volume Warning Toggle
Navigation Bar Toggle
Immersive Mode
Set DNS
Powercfg by yc9559 @ CoolApk [EXY8895]
Host File Based Adblock
Service Disabler
Reboot Device
Reboot into Recovery
To use, type the following in a terminal emulator
Code:
su
cfg
Click to expand...
Click to collapse
I always get the result "permission denied"
Su rights granted to terminal emulator. Used the commands su "enter" cfg "enter". What am I doing wrong?
xxxPLETTIxxx said:
I always get the result "permission denied"
Su rights granted to terminal emulator. Used the commands su "enter" cfg "enter". What am I doing wrong?
Click to expand...
Click to collapse
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
keyboard is not working for me
ImbaWind said:
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
Click to expand...
Click to collapse
Sure. Hope you can help.
ImbaWind said:
Sounds like you are doing everything right, but I'm not sure why.
Can you attach a screenshot?
Click to expand...
Click to collapse
Same here,but loving the ROM nonetheless and I've installed so many
xxxPLETTIxxx said:
Sure. Hope you can help.
Click to expand...
Click to collapse
pbls said:
Same here,but loving the ROM nonetheless and I've installed so many
Click to expand...
Click to collapse
Code:
su
mount -o rw,remount /system
chmod 777 /system/bin/cfg
cfg
This should help
Hi, there!
Now that we can use Project Croissant to get ChromeOS running or non-Chromebook devices, what is missing is a better kernel for improved compatibility.
Thanks to the threads by @nabil2000 I was able to successfully build a chromeos-4.14 kernel that boots on my test device (Lenovo MIIX320-10ICR - Z8350 processor) using a CONFIG from FydeOS 5.31 with most hardware enabled (WiFi, Bluetooth, sound), but it has the same issue as latest ATB builds: it freezes after a while. This doesn't happen with latest FydeOS or CloudReady builds (CloudReady bought FlintOS so I guess they are using some of their code now), so my guess if that their kernels have some patches that aren't included in the Chromium git. FydeOS is open-sourced only for RaspberryPi and TinkerBoard, there are no sources available for the PC or VMWare versions (PC version is not open source as many say, so be aware).
I already have some ideas to make the trackpad as well as the battery meter and brightness work, but it is not useful if the kernel isn't as stable as FydeOS (virtually no freezes or crashes once booted). I have already checked, and the issue is not the intel_idle.max_cstate issue that plagued most BayTrail/CherryTrail devices in the past (using value 1 doesn't change anything).
So any ideas how to get FydeOS kernel source? Patches to make the current chromeos-4.14 kernel stable?
UPDATE: As @nabil2000 reported, it seems that FydeOS is not willing to release their kernel source. But it is possible to get kernel config from v5.31 using configs.ko module, which is missing in the next version (v6.0). Using FydeOS v5.31 as base it is possible to build a very stable kernel for CherryTrail devices.
Thanks
Installation v71/v72 - kernel 4.14
FydeOS has the best support for the MIIX320-10ICR, with some caveats:
It will boot to a black screen, but you just need to wait until it finishes loading the hit Ctrl+Alt+Fn+F2, the screen will blink and then hit Ctrl+Alt+Fn+F1 to go back to ChromeOS (for some reason, the developer shell is blank in 5.31 but it seems to work fine on 6.0). Use Ctrl+Shift+Fn+F3 to rotate the screen manually;
WiFi works out of the box, Bluetooth is detected but audio does not work (Chromium misses a library for audio over Bluetooth);
Sound works too, but you need to install some UCM files (more about this later);
Camera does not work, and the trackpad works very well, with gestures, but does NOT click (tap to click work with a custom conf file, see below - the trackpad actually sends two events when clicking the physical button, as some Windows devices do, and this doesn't work with cmt driver).
First I tried to build the ChromeOS file using the chromium.img from FydeOS v5.31. It booted fine and I was amazed to see the ChromeOS logo and Google enrollment, but PlayStore setup didn't finish (low space?) and there was no way to install it to another driver: many GPT errors and the installer failed...
Then I tried to do everything on place:
Booted to FydeOS on USB drive;
As I could not get to the dev shell in v5.31, I had to login then use crosh and shell, then installed it on a second external disk (120GB SATA on USB, /dev/sdb):
PS: your device may be a different one, check the correct device name using "lsblk" or "fdisk -l" and be aware that this installation erases the whole disk!
Code:
sudo chromeos-install --dst /dev/sdb
After installing, I have used option 2A from GitHub page (very detailed, thanks!) with the script, soraka (or pyro) and caroline recoveries (both versions 11151.113 = v71) on another disk:
PS: FydOS v5.31 kernel does not have support to VTPM_PROXY, while v6.0 does, it means you cannot use swtpm.jar with FydeOS v5.31 and chromefy. For nocturne or Android Pie ARC, you must use FydeOS v6.0, otherwise ARC won't work.
Code:
sudo bash ./chromefy.sh /dev/sdb recovery.bin caroline.bin
Answered YES to use the local installation, YES to resize partitions and NO in the end to keep SELinux as enforced (it may work fine if you keep it to enforced with nocturne recovery tho when using FydeOS v6.0);
Rebooted using the final installation, logged in and everything seemed fine, but then Play Store would not show installed apps even after a reboot, so I tried a powerwash and it seems it fixed the issue, now it seems to be working fine.
Original post: https://forum.xda-developers.com/showpost.php?p=78891386&postcount=729
Post installation fixes v71/v72 - kernel 4.14
1. Sound
You need to install UCM files using linuxium-install-UCM-files.sh script after remounting rootfs as RW.
Code:
sudo remount -o rw,remount /
sudo bash ./linuxium-install-UCM-files.sh
2. Headphone jack
You must send this quirk to the rt5645 module when loading it, so while rootfs is still RW, as root add a file named "miix320.conf" to /etc/modprobe.d with this line:
Code:
options snd_soc_rt5645 quirk=0x1030
PS: if you have used the correct UCM files then the audio should change between speakers and headphones, but not mic. To enable internal mic:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev DMic
and to enable mic from headset:
Code:
sudo alsaucm -c chtrt5645 set _verb HiFi set _enadev HSMic
3. Tap to click with trackpad
While rootfs is still RW, as root add a file named "50-mixx320.conf" to /etc/gestures:
Code:
Section "InputClass"
Identifier "MIIX320 conf"
MatchUSBID "048d:*"
MatchIsTouchpad "on"
MatchDevicePath "/dev/input/event*"
Option "Tap Minimum Pressure" "1"
EndSection
PS: for this to work, make sure "tap-to-click" is enabled in trackpad section of system Settings. If you have another device, use "dmesg | grep input:" with "lsusb" to find your device USB id instead of "048d:*".
Still needing fixes:
- chrome://flags is blank for some reason, so any special flags should be added manually to "chrome_dev.conf" instead;
- Trackpad physical button click;
- Brightness control;
- Battery meter;
- Rotation;
- Automatic change between tablet/desktop modes;
- Cameras (hardly they will work as they rely on ATOMISP, which was abandoned and does not work even on newest kernels).
Original post: https://forum.xda-developers.com/showpost.php?p=78978577&postcount=757
reserved
Good news! With chromeos-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
lfom said:
Good news! With chrome-4.19 it is possible to fix most problems:
- trackpad button click;
- battery meter;
- accelerometer sensor module is loaded, it needs to be tested;
- possibly brightness can be fixed too.
Using FydeOS v5.31 kernel config as base I could get a very stable build, but it broke loading ARC somehow, and I have no idea why. Maybe it's a permissions/signatures issue? I will try to run chromefy again, with the new kernel already in place to see if it works.
Click to expand...
Click to collapse
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
nabil2000 said:
Nice to see you do some kernel work.
Care to share link to Chromium OS Kernel 4.19 source code, I would like to get a crack at using menuconfig to add drivers..
Click to expand...
Click to collapse
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-dev in order to successfully build it.
lfom said:
Sure. I should post a full guide as soon as I get ARC working without issues, the new kernel is awesome.
I have used the same base procedure as you did:
https://github.com/dnschneid/crouton/wiki/Build-chrome-os-kernel-and-kernel-modules
I then cloned (duplicated) the kernel source (chromeos-4.14) so I could then checkout the newer version while keeping the old one:
Code:
$ cd ~/kernel_new
$ git reset --hard origin/chromeos-4.19
PS: I am building on Xenial (not chroot), so I had to install libssl-devel in order to successfully build it.
Click to expand...
Click to collapse
I am a lazy billy - thanks - I like copy & paste, & think as little as I can afford
Could you help me patching it on my GPD pocket?
it uses cherry tail
https://forum.xda-developers.com/ha...gpd-pocket-t3928828/post79496417#post79496417
thank you