[KERNEL] Modified O Boot Image Kernel for O as Daily Driver - Nexus 5X General

After installing the O Preview, with no source code available for the kernel, I was wondering how I could run O as my daily driver with my apps like Sony Music, ES File Explorer (Root) etc, when Chainfire came with SR4 Beta.
Also required in my daily driver is my own custom kernel. Here is a kernel with boot.img from O along with ramdisk and module tweaks:
RACER_O
Kernel version name will show that of O stock boot image, but rest assured that some modifications have been done. Open the kernel zip to explore what is in.
Tweaks that are part of the kernel zip:
ramdisk: init.racer.rc, Bullhead power script, Ghost peper Interactive Gov Profile
default.prop: persist.bt.enableAptXHD=true, ro.opa.eligible.device=true added
Modules packaged for O: (I am testing these modules)
LED
SURROUND LOUDER
APTX - need libaptx.so and libaptxHD.so and may be one or two other files from AOSP BT Stack. As of now O-DP1 doesn't have those. Since the System UI shows the options, one can expect this feature to be activated in future O updates.
Apps packaged for O:
Pixel Launcher
Sony Ericsson Music

Reserved -1
Reserved for later

Reserved -2
Reserved for later

Here is a kernel with boot.img from O along with ramdisk and module tweaks:
RACER_O_20170324
Kernel version name will show that of O stock boot image, but rest assured that some modifications have been done. Open the kernel zip to explore what is in.

Is there any way to port this over to the Nexus 6P? Having aptX sounds fantastic (no pun intended), and the ramdisk tweaks could help with the sluggish performance in O.

So this is stock or does it have performance enhancements ? Its not overclocked is it ?

mikeprius said:
So this is stock or does it have performance enhancements ? Its not overclocked is it ?
Click to expand...
Click to collapse
No. Everything that goes into zImage of the kernel is stock. External modules and tunables are all that can be played with now.
Previous builds posted here have too much battery drain during active as well as idle, though they are still not show stoppers.
Here is a more stockish build with stock interactive gov and stock thermal conf tuning to see is there is any improvement on the battery front. Thermal appears to be work in progress. I have not seen any exposed parameter tunables such as /sys/module/msm_thermal/parameters/temp_threshold
RACER_O_20170325_Stock_I&T

Thanks for the info. I've been having a rough time with DP1. Can't root and having issues booting. Will try next release

Can't download. No mirrors found.

mikeprius said:
Thanks for the info. I've been having a rough time with DP1. Can't root and having issues booting. Will try next release
Click to expand...
Click to collapse
That's strange. I hope you are using latest Jolla recovery and Chainfire's Su...SR4. Root works like a charm for me. A pixel launcher and navbar animation are available, even before Charles comes up with his full mod, that is already in the making I think. Overall I have no reason to get back to nougat.

rachanta said:
That's strange. I hope you are using latest Jolla recovery and Chainfire's Su...SR4. Root works like a charm for me. A pixel launcher and navbar animation are available, even before Charles comes up with his full mod, that is already in the making I think. Overall I have no reason to get back to nougat.
Click to expand...
Click to collapse
Flash the preview O and used SuperSU SR4. I used standard TWRP, I believe 3.0.1. Didn't have any issues when loading TWRP and Preview O work. Just when I tried flashing SR4 via TWRP the thing went into bootloop and would not boot. The only way to force boot the ROM was to flash the stock preview kernel back. Not sure what happened, but could not get root to work flashing the ZIP

mikeprius said:
Flash the preview O and used SuperSU SR4. I used standard TWRP, I believe 3.0.1. Didn't have any issues when loading TWRP and Preview O work. Just when I tried flashing SR4 via TWRP the thing went into bootloop and would not boot. The only way to force boot the ROM was to flash the stock preview kernel back. Not sure what happened, but could not get root to work flashing the ZIP
Click to expand...
Click to collapse
Phone will boot normally after two reboots.

Mods and tweaks described are already in your kernel ?
Inviato dal mio KFGIWI utilizzando Tapatalk

amag3308 said:
Mods and tweaks described are already in your kernel ?
Inviato dal mio KFGIWI utilizzando Tapatalk
Click to expand...
Click to collapse
Yes

rachanta said:
Yes
Click to expand...
Click to collapse
I found a test folder with 24th march versions and main folder with 25th kernel versions. Which one should I install? What is RACER_O_20170325_GP.zip?

amag3308 said:
I found a test folder with 24th march versions and main folder with 25th kernel versions. Which one should I install? What is RACER_O_20170325_GP.zip?
Click to expand...
Click to collapse
It has Ghost Pepper interactive governor profile and stock thermal. The other option has stock interactive governor and stock thermal. The test builds are with different thermal-engine-8992.conf options. If you extract the zip you can play around with init.racer.rc and other files to pack different flavours and create your own kernel zip.

rachanta said:
That's strange. I hope you are using latest Jolla recovery and Chainfire's Su...SR4. Root works like a charm for me. A pixel launcher and navbar animation are available, even before Charles comes up with his full mod, that is already in the making I think. Overall I have no reason to get back to nougat.
Click to expand...
Click to collapse
were is the navbar animation for android O

Did anyone test if aptx is working?
Flashed racer 25th march version but did not work. I tried with flac and also spotify (of course my bt headset are capable) but logcat shows nothing
Inviato dal mio KFGIWI utilizzando Tapatalk

rachanta said:
After installing the O Preview, with no source code available for the kernel, I was wondering how I could run O as my daily driver with my apps like Sony Music, ES File Explorer (Root) etc, when Chainfire came with SR4 Beta.
Also required in my daily driver is my own custom kernel. Here is a kernel with boot.img from O along with ramdisk and module tweaks:
RACER_O
Kernel version name will show that of O stock boot image, but rest assured that some modifications have been done. Open the kernel zip to explore what is in.
Mods & Tweaks:
ramdisk: init.racer.rc, Ghost peper Interactive Gov Profile
default.prop: persist.bt.enableAptXHD=true, ro.opa.eligible.device=true added
msm_thermal: thermal-engine-8992.conf stock in use in the kernel for now
Installed, but dont seem to be doing anything: lights.bullhead.so, mixer_paths.xml
Help required: How to make O work with f2fs data and cache, usual fstab.bullhead mod has no effect
Apps packaged for O:
Pixel Launcher
Sony Ericsson Music
Click to expand...
Click to collapse
The lights.bullhead.so file is for the RED LED when on low battery. The mixer_paths.xml contains the DualMonoV2 LOUD "surround sound".

Simonthow1 said:
were is the navbar animation for android O
Click to expand...
Click to collapse
I am searching for it. Navbar animation in pixel o has some major advances. You can edit it to add 2 more buttons. We have to wait till somebody ports it.

Related

[ROM][WIP][AOSP][4.4.4_r2.0.1] Google Edition for SGS4A (int'l) 1.0.0

What?
A work in progress build of AOSP, using CM11 kernel sources and device files, modified to play ball with AOSP
some stuff copied from CM, to make build happen (bionic, assorted libs and stuff in external and system, etc...)
build makefiles modified, using CM files where possible
some small code modifications
for I9295 international only
stuff is broken, for how long i do not know. Limited time and real life... meh
DISCLAIMER: You take responsibility of your phone and what you flash into it, not me. You are warned!
How?
grab the file: https://drive.google.com/folderview?id=0BzJzDM42pkRvcUVyZDRVSERzdlk&usp=sharing
if coming from another rom: factory reset + format /system + format caches as well
upgrading previous version shouldn't need factory reset or system format
flash in CWM (yes, CWM or similar needed)
flash gapps
report bugs if new one found
help with development if possible
Credits
Google for Android (and Google search, boy this wouldn't have happened without it )
CyanogenMod for stuff i'm using to make this happen
SlimRom guys
LeJay for jactivelte kernel sources and other stuff
Chainfire for root and SuperSU app
chenxiaolong for DualBoot
Donators and testers
ES File Explorer creators https://play.google.com/store/apps/details?id=com.estrongs.android.pop&hl=en
DualBoot
I provide dualboot version of this ROM, mainly because i run the test versions in dualboot mode (second rom). If you aren't' familiar with the concept, have a look here: http://forum.xda-developers.com/showthread.php?t=2447534.
Basically it allows one to have two (or more) roms installed simultaneously, switching between them using the application provided on the above thread.
Notes:
When using dualboot roms, DO NOT USE CWM wipe, format functionality. Backup works, but for what i know, it backs up the secondary rom too, not 100% sure how well this works...
For dualboot secondary rom, you need dualboot gapps
Flashing main rom destroys secondary rom, flashing secondary rom doesn't harm main rom
For more info, read the above thread
Changes v1.0.0 and 1.0.0-opt
new KK blobs taken in use (same that CM11 has been running since last fall) (NOTE: KT kernel from last spring won't work with this)
contains some of the latest fixes to CM11, like Network search fix and Camera fixes
repo sync, not much changed
probably the last Android 4.4 release
Changes v0.9.10 and 0.9.10-opt
fix phone speaker
AOSP repo sync, nothing major has changed
Changes v0.9.9 and 0.9.9-opt
triple framebuffers, reduces screen refresh stutters
f2fs in kernel enabled. Not supported bu updater yet, though
updater_script updates, more compatible with TWRP
SuperSU 2.37
Changes v0.9.8 and 0.9.8-opt
camera: fixed exposure setting
added proper network operator name list
Changes v0.9.7 and 0.9.7-opt
camera fixes: front camera should work now
exfat is now writable
external sdcard write restrictions relaxed
selinux rules updated from CM11
updater_script: properly set permissions and selinux metadata (may need CWM update)
kernel: Firmware files from TW KK kernel
kernel: Exfat 1.2.6 from TW KK kernel
kernel: Added f2fs
blobs: Wifi, NFC and Bluetooth from NE5
Changes v0.9.6 and 0.9.6-opt
incremental camera fixes, toggling flash and HDR shouldn't freeze the camera, at least so much. There's still bugs, but easy does it...
kernel: Newer bcmdhd drivers from TW KK 4.4.2 kernel
kernel: Wcd9xxx stuff from TW KK 4.4.2 kernel
kernel: Cypress touchkey, leds and max77693 stuff from tw kk kern
optimized build: changed to Google's GCC ver 4.8, no more broken playstore icons
Changes v0.9.5 and 0.9.5-opt
kernel: Msm qdsp6v2 updates from TW kk 4.4.2 kernel
framework: some minor bluetooth and gps code merges from CM
Changes v0.9.4-opt
First build with JustArchi's optimizations (Linaro 4.8)
Also added DualBootPatcher 8.0.0
Changes v0.9.3
updater-script fixes to support some CWM recoveries
Changes v0.9.1
added bash, ebtables, ntfs-3g, vim
updated sqlite and zlib
fixed wifi ap
Changes v0.9
wifi & gps settings from msm8960 (from cm jflte)
stepdetector and -count sensor permission xmls (from cm jflte)
init network tuning (from cm jflte)
charger update (from cm jflte)
wifi settings moved out (from cm msm8960)
gps setting moved out (from cm msm8960)
charger change for kk bootloaders (from cm msm8960)
kernel: using new unified jf kernel http://review.cyanogenmod.org/#/c/67429/
kernel: enabled CONFIG_DISPLAY_DISABLE_TEST_KEY
kernel: enabled CONFIG_CFG80211_REG_NOT_UPDATED
kernel: enabled CONFIG_SENSORS_HALL
QC time services: fixed time resetting to wrong value when rebooting
Changes v0.8
update scripts fixed
md5sums added
zips cleaned
Preferred network-setting now has only Lte, 3G and 2G. Default is 3G, change it if needed. This is work in progress
Qualcom init script updates from CM jflte (sdcard read/write speedup etc.)
Google backup working
Changes v0.7
Updated SuperSU to 2.0.1
Updated su install scripts to match SuperSU CWM scripts (hopefully...)
Added ES FIle Explorer
Added DualBootPatcher ver 7.0.0 app
Changes v0.6
4.4.4_r2 (doesn't seem any changes so far...)
Nfc seems to be on now
Some overlays updated, check the commits here: https://github.com/spegelius/android_device_samsung_jactivelte/tree/aosp-4.4
? can't remember...
Changes v0.5
GPS working
sdcards working
mobile data H and H+ icons working
some code updates from CM (bionic) and overlays updated
Changes v0.4
Initial release, fresh from oven. Might be bit burned on the sides...
Bugs
Camera: toggling HDR might crash camera (rare)
Apparently flaky Bluetooth
Fixed bugs
exFAT
Camera: exposure setting crash
Camera: toggling front camera crashes camera app
Camera: toggling flash might crash camera
Sdcard problems, mounting fails (even internal). This causes a lot of other problems...
Camera: can't save pics as no sdcard...
GPS: doesn't seem to work
NFC crashes silently on the background (logcat)
Google cloud backup
Date resets to 1970 or so in reboot, might cause problems when in flight mode or bad connection
WiFi tethering turns on but the ap network cannot be seen
Mobile network operator names aren't shown, only id's
Source code
https://github.com/spegelius
Manifest and how to use:
Code:
mkdir aosp-src
cd aosp-src
repo init -u git://github.com/spegelius/manifests.git -b aosp-4.4
repo sync
source build/envsetup.sh
make otapackage
*needs some scripts fro there on, not yet in github, resulting zip cannot be flashed in CWM!*
Oh happy day. Will test ASAP. I really really want this to work as a daily driver.
Ver 0.5 uploading. Fixes:
- GPS works
- sdcards work
- mobile network icon shows H and H+
- Google cloud backup option unknown, doesn't work for me, but i haven't done clean install for latest
Ver 0.6 uploading. Fixes:
- 4.4.4_r2 (doesn't seem any changes so far...)
- Nfc seems to be on now
- Some overlays updated, check the commits here: https://github.com/spegelius/android_device_samsung_jactivelte/tree/aosp-4.4
- ? can't remember...
Seems quite solid so far. Hmm maybe have a look at L preview, eh?
I just try 0.6 dualboot ZIP and so far everything worked AS it should but in the aosp Rom im not able to install an apk. Die i Miss a major Detail in the dualboot threaf?
Gesendet von meinem GT-I9295 mit Tapatalk
olarf said:
I just try 0.6 dualboot ZIP and so far everything worked AS it should but in the aosp Rom im not able to install an apk. Die i Miss a major Detail in the dualboot threaf?
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Do you mean installink from apk file? For me it works fine, after you allow Unknow sources in security. I'm on dualboot also.
I expected this after the github commits
spegelius said:
Do you mean installink from apk file? For me it works fine, after you allow Unknow sources in security. I'm on dualboot also.
Click to expand...
Click to collapse
I allow unknown sources but can't install any apk. Therefore it is very uncomfortable to switch ROMs. Beside this I think a file browser could be good as basic part in the aosp build. Switching via cwm works fine so in general everything runs good expect from installing apks. Can it be a result from don't installing gaps on second ROM?
Gesendet von meinem GT-I9295 mit Tapatalk
olarf said:
I allow unknown sources but can't install any apk. Therefore it is very uncomfortable to switch ROMs. Beside this I think a file browser could be good as basic part in the aosp build. Switching via cwm works fine so in general everything runs good expect from installing apks. Can it be a result from don't installing gaps on second ROM?
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Well i'm trying to keep this as close as possible to stock AOSP, so only addition so far is the SuperSU. But a file browser of some kind would be good. Just don't know how it is with integrating an app from play store to ROM on legal side...
I actually don't know if installing an apk should be possible without gapps... could be, as there aren't any google play framework.
spegelius said:
Well i'm trying to keep this as close as possible to stock AOSP, so only addition so far is the SuperSU. But a file browser of some kind would be good. Just don't know how it is with integrating an app from play store to ROM on legal side...
I actually don't know if installing an apk should be possible without gapps... could be, as there aren't any google play framework.
Click to expand...
Click to collapse
you can include any app from from the play store as long as its free and you provide credits , i dont think there is a relation between sideloading apps and google framework , but could be google messing with its tail
spegelius said:
Well i'm trying to keep this as close as possible to stock AOSP, so only addition so far is the SuperSU. But a file browser of some kind would be good. Just don't know how it is with integrating an app from play store to ROM on legal side...
I actually don't know if installing an apk should be possible without gapps... could be, as there aren't any google play framework.
Click to expand...
Click to collapse
This is excellent! I finally was able to get time to install after your 4.3.1 AOSP. Please keep it clean AOSP. Nice to finally have a 4.4.4 rom that boots and will deep sleep. My last attempt was very frustrating, as updates broke things and I could not get any help with it. I'll throw another donation your way soon.
Yeah, vamilla AOSP is my aim with this one. If there's some modifications, i'll propably release a different version of the rom altogether, that way there's possibility to choose.
I think i'll include the Dualboot patcher app at least on the dualboot variants. That way it's easier to switch back to main rom. And maybe some free file manager app. I've been using ES File Manager myself.
Not being able to install apk is strange, it could be that there's some framework tidbit missing from vanilla AOSP and installing gapps installs it also. I'll need to test this some time. Also, i forgot to mention that the 0.6 has updated bionic from CM which caused recompile of most of the code and lot's of FC's before doing a clean installation.
Hello, how can i get\enable root for this rom?
6783 said:
Hello, how can i get\enable root for this rom?
Click to expand...
Click to collapse
Yes, SuperSU is included and working
spegelius said:
I actually don't know if installing an apk should be possible without gapps... could be, as there aren't any google play framework.
Click to expand...
Click to collapse
I run a pacrom (4.1.2 I think) for a while without gapps and installing APS was no problem. However this don't mean that it can be the reason in your clean aosp build as PAC is a full flavoured mix To embedded switcher app and file browser is a great idea anyway, make things more easy for dualboot user.
Gesendet von meinem GT-I9295 mit Tapatalk
Ver 0.7 up:
Updated SuperSU to 2.0.1
Updated su install scripts to match SuperSU CWM scripts (hopefully...)
Added ES FIle Explorer
Added DualBootPatcher ver 7.0.0 app
I try to install the dualboot Version but it fails!? Cwm told me that the ZIP file is not OK after beeing nearly ready. When i want to reboot then, cwm tell me that su is damaged and offer me to fix it. Then PAC boots Ingo Logo, stuck there and after switching it off and in it bootloops. So i flash PAC again and it was fine. Can there be something in the build or is my file maybe corrupt?
Gesendet von meinem GT-I9295 mit Tapatalk
olarf said:
I try to install the dualboot Version but it fails!? Cwm told me that the ZIP file is not OK after beeing nearly ready. When i want to reboot then, cwm tell me that su is damaged and offer me to fix it. Then PAC boots Ingo Logo, stuck there and after switching it off and in it bootloops. So i flash PAC again and it was fine. Can there be something in the build or is my file maybe corrupt?
Gesendet von meinem GT-I9295 mit Tapatalk
Click to expand...
Click to collapse
Strange, i flashed the 0.7 dualboot fine. Previous versions gave some errors because i was tweaking the updater-script to set proper permissions for su and other stuff + selinux context. You wouldn't happen to remember waht the error was? I'll have to check the zip that it has proper updater-script...
Edit: scripts are fine. I have a hunch that these lines are causing the problems:
Code:
run_program("/system/bin/toolbox", "chcon", "u:object_r:system_file:s0", "/system/bin/.ext/.su");
I remember seeing something similar when i was using newer CWM and tried to make a CWM script using older updater-scripts, some commands parameters were changed. Currently i'm on 6.0.4.7, you are propably running newer?
I'll remove those lines for now, su has been working ok without them in the past. Let's see how it goes...
I use 6.0.4.7 aswell. However, I will download it again after dinner, try again and if the error appear again, I will report it 100% exact. Thanks for taking a look into it!
Gesendet von meinem GT-I9295 mit Tapatalk

[ROM] [T805] [BOCC] [LOLLIPOP] ||| Basic Rom L ||| Rooted - Zipaligned - De-Knoxed

​
I just wanted to start making custom roms for my Galaxy Tab S 10.5 LTE, since there is virtually no material for this particular device (Only the WiFi version is out in the USA) I guess I'm starting the trend
Features:
Based on the last LOLLIPOP 5.0.2 BOCC rom
Rooted
Busybox Added
ZipAligned
Knox Removed
**WARNING**
This file may cause explosions on your device, flash ONLY if you know what you're doing and you're able to recover from a brick
**WARNING**​
Flash with TWPR Recovery
Download: HERE
Older downloads:
v1.1
UPDATE 1.2
V2
V3
V4
Changelog:
V1
Initial Release
V1.1
Uploaded to mega while waiting for Androidfilehost to add our device
Build.prop tweaks
Removed some outdated apks
v1.2
Custom Kernel
✔ Based on official Samsung source: SM-T805_KK_Opensource (Released Today!)
✔ ramdisk source: T805XXU1ANFB
✔ BFQ Default Scheduler
✔ Frandom
✔ Other Optimizations
V2
Based on the newest NG2 Firmware (Super Fast!)
Stock NG2 Kernel since the availbe sources are from NF8, but NG2 it's way faster
Root, busybox, etc.. all as previous releases, and updated to the latest releases
V3
Based on the newest NJ5 Firmware (Super Fast!)
Stock NJ5 Kernel
Root, busybox, etc.. all as previous releases, and updated to the latest releases
V4
Based on the newest OA1 Firmware Finally
Stock AO1 Kernel
init.d support
Root, busybox, etc.. all as previous releases, and updated to the latest releases
L
Based on the newest BOCC Firmware with the long awaited Lollipop release
Stock BOCC Kernel
Root, busybox, etc.. all as previous releases, and updated to the latest releases
Credits:
UpInTheAir for inspiring me to work on the T805Kernel
Dees_Troy for bringing TWRP
Source:
https://github.com/619619/T805-Basicrom-Kernel
It should work on T800 too, it does not include modem, but I haven't tested it on that particular device
Does it come debloated?
619619 said:
It should work on T800 too, it does not include modem, but I haven't tested it on that particular device
Click to expand...
Click to collapse
Ill try it later and report back. Btw, can you make kernels? I'd love a t800 kernel that allows for synapse to work, I REALLY want to adjust the screen tint.
Hisma said:
Does it come debloated?
Click to expand...
Click to collapse
It could, but I wanted to maintain all the features of the device
If I have time to upload a debloated version, I will
Inviato dal mio SM-N9005 utilizzando Tapatalk
toyanucci said:
Ill try it later and report back. Btw, can you make kernels? I'd love a t800 kernel that allows for synapse to work, I REALLY want to adjust the screen tint.
Click to expand...
Click to collapse
I already built the kernel from source, but I've never looked for implementing Synapse
I'll take a look and report back
Inviato dal mio SM-N9005 utilizzando Tapatalk
Should it work with the t800?
toyanucci said:
Should it work with the t800?
Click to expand...
Click to collapse
Tried it and yes seems to work. Installs ok. Boots ok. Shows tethering option, shows t-805 and other 805 stuff
619619 said:
I already built the kernel from source, but I've never looked for implementing Synapse
I'll take a look and report back
Inviato dal mio SM-N9005 utilizzando Tapatalk
Click to expand...
Click to collapse
I meant, should your kernel work on the t800 as well?
619619 said:
I just wanted to start making custom roms for my Galaxy Tab S 10.5 LTE, since there is virtually no material for this particular device (Only the WiFi version is out in the USA) I guess I'm starting the trend
Features:
Based on the last NFB rom
Rooted
Busybox Added
ZipAligned
Knox Removed
Init.d Support
**WARNING**
This file may cause explosions on your device, flash ONLY if you know what you're doing and you're able to recover from a brick
**WARNING**​
Flash with TWPR Recovery
Download: v1
Click to expand...
Click to collapse
Thnks very very much........ I was waiting for this Unfortunally I have a T705 device........ can you pls do something ab that??
Yhnks very much again
Just a question regarding knox removed, do you do something more than SuperSU do when it disable knox ?
Thank you
Edit : a debloated version would be great
Orphee said:
Just a question regarding knox removed, do you do something more than SuperSU do when it disable knox ?
Thank you
Edit : a debloated version would be great
Click to expand...
Click to collapse
Supersu disables Knox ,in this rom it doesn't exist in the first place; but the final result I guess it's the same
Hisma said:
Does it come debloated?
Click to expand...
Click to collapse
You can do that yourself if you're rooted. Use the apps found on the playstore called System App Remover. The advantages of this app is that it comments on what is safe to remove and what isn't. The free version did such a good job on my Nexus devices that I bought the pro version just to support the developer.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
It can remove user apps also but that is less to your needs.
The best part is that it automatically backups what it deletes into a trash directory. This means if you accidentally remove something you shouldn't you can use the app to reinstall it. I used this feature on more than one occasion when an app would no long work (e.g. Gmail need a cloud print module).
Sent from my Nexus 10 using XDA Premium HD app
3DSammy said:
You can do that yourself if you're rooted. Use the apps found on the playstore called System App Remover. The advantages of this app is that it comments on what is safe to remove and what isn't. The free version did such a good job on my Nexus devices that I bought the pro version just to support the developer.
https://play.google.com/store/apps/details?id=com.jumobile.manager.systemapp
It can remove user apps also but that is less to your needs.
Sent from my Nexus 10 using XDA Premium HD app
Click to expand...
Click to collapse
That is good to know. Yes, I am rooted and have TWRP recovery.
I want to know what apps are safe to remove, and what aren't. With a tool that can tell me, that would be perfect. I don't have a samsung phone, so I have no use for sidesync, for instance.
Hisma said:
That is good to know. Yes, I am rooted and have TWRP recovery.
I want to know what apps are safe to remove, and what aren't. With a tool that can tell me, that would be perfect. I don't have a samsung phone, so I have no use for sidesync, for instance.
Click to expand...
Click to collapse
I forgot to mention another very important app feature, please see the additional last lines in my updated post.
Sent from my Nexus 10 using XDA Premium HD app
Dingchow said:
Tried it and yes seems to work. Installs ok. Boots ok. Shows tethering option, shows t-805 and other 805 stuff
Click to expand...
Click to collapse
Would anyone have an alternative link to the ROM file? The link in the tread seems to not be functioning
ewells38 said:
Would anyone have an alternative link to the ROM file? The link in the tread seems to not be functioning
Click to expand...
Click to collapse
I'm uploading to a new host, waiting for Androidfilehost to add teh Galaxy Tab S so I can upload there :angel:
New upload, v1.1
https://mega.co.nz/#!eVgiSJZR!8IOwGRjUp9CalZk5qCGwjB41hfoE0eNhN5wq7jYRtfM
Are you planning to make a ROM also for 8.4 users ? It looks amazing!

[ROM][OP3][UNOFFICIAL] CyanogenMod 13 - odexed

Just another CyanogenMod rom – but odexed
This build of CM 13 for the OnePlus 3 is made with the sources of CyanogenMod
Special Features are:
Odexed
Navigation Bar always enabled like on Nexus devices
Home button enabled as well
Faster GPS fix
Changelog
Check on https://www.cmxlog.com/13/oneplus3/ for the latest changes
Installation instructions:
Download the latest build
https://www.androidfilehost.com/?w=files&flid=86101
Download Gapps
Take a nandroid backup
Recommended - Full wipe and factory reset
Flash ROM using latest Recovery
Flash Gapps
Reboot.
Enjoy!
* Note:
Don’t reboot in between flashing rom and Gapps
SuperSu is supported as well but is not needed
All credits belong to
CyanogenMod team
@Grarak, @dianlujitao ​
XDAevDB Information
CyanogenMod OnePlus 3, ROM for the OnePlus 3, Odexed
Sources
https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Firmware Required: Unlocked bootloader, custom recovery
Version Information
Status: Nightly
Created 2016-07-28
Last Updated 2016-07-28
First of all, I’m not a developer and cannot really fix things. My work depends on the real CyanogenMod developers. I run builds on my build host because I like to have Android being Odexed like all stock roms are.
If we’re talking about the odex files, here are its advantages when compared to the deodex files.
• In case of odex files, apps start a lot faster since the preloading information is separately available to load directly to the Dalvik virtual machine. Where as in deodexed files, the boot times are significantly longer as the DVM has to decompile APKs at boot time to get the necessary information.
• The odexed APKs occupy less space when compared to the deodexed APKs, so they occupy less room in the system folder.
These builds will not be on a daily schedule but a few times a week. If you like my work please press thanks on the button beneath.
Latest build of today
cm-13.0-20160730-UNOFFICIAL-oneplus3.zip
From now on the files can be downloaded on Androidfilehost
https://www.androidfilehost.com/?w=files&flid=86101
Have fun
is it still possible to disable navbar? thanks
nadejo said:
is it still possible to disable navbar? thanks
Click to expand...
Click to collapse
That is possible, but you have to do that in the build.prop and the synaptics.kl files if necessary.
Thanks @Planet X good work!
Todays nightly is up on Androidfilehost.
https://www.androidfilehost.com/?fid=24591000424950852
There has been a lot of changes like DASH charging has been added and also the camera should work better now. You will find all the changes here https://www.cmxlog.com/13/oneplus3/
Let's find it out?
Thats what I have found so far:
DASH working !
DASH is working perfectly except for those of us who would like that "DASH charging" text and blue notification light.
- Gallery crash couple seconds after viewing recently taken image. Crashes hard triggering automatic reboot of the device.
- Cannot transfer files from/to PC through USB
Fix is:
Edit build.prop and remove ro.sdcardfs.enabled=true
Everything will work as usual.
New Build is up!
cm-13.0-20160730-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24659325368664127
This includes the fix for File transfer to PC and tweaks for the camera.
Have fun
Which camera tweaks?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Steve has unmerged changes on Gerrit. I have merged that.
New Build is up!
cm-13.0-20160730-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24659351692116054
It has the same date. I have deleted the earlier build.
There has been a lot of changes to the camera in the meanwhile today. My first experience is that even Snap is a good camera now. The flash works finally as it should and also noise seems to be reduced. After all, I 'm finally convinced that cm13 is capable of taking pictures in house and can be used for daily shots on my upcoming vacation too.
Enjoy the new build. Have fun
New Build is up!
cm-13.0-20160731-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24659325368664296
Again with changes to the camera. Enjoy the new build
P.S: I was to early to submit. The upload took longer than expected.
Planet X said:
New Build is up!
cm-13.0-20160731-UNOFFICIAL-oneplus3.zip
Again with changes to the camera. Enjoy the new build
Click to expand...
Click to collapse
Hi Mister, link is missing for the other people
New Build is up!
cm-13.0-20160801-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24659325368664383
Again camera fixes and outdoor overlay fixes.
Have fun
New Build is up!
cm-13.0-20160802-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24659325368664512
With all the changes up to 18:00 CEST.
Have fun
I'm a bit concerned about the added feature blur on the lockscreen. Personally I like it more the way we had it before. What do you think about it? Should I remove it in my builds?
Planet X said:
I'm a bit concerned about the added feature blur on the lockscreen. Personally I like it more the way we had it before. What do you think about it? Should I remove it in my builds?
Click to expand...
Click to collapse
Personally, I like that feature
Sent from my ONEPLUS A3000 using Tapatalk
g_Four said:
Personally, I like that feature
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Than I leave it as it is for now.
New build is up again.
cm-13.0-20160803-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24665539028713513
This time with a lot of fixes and changes. Mainly the Them engine has been updated and we are updated to Android 6.0.1 Release 61 (MOB30Z).
It's a clean build again.
Have fun
Planet X said:
Than I leave it as it is for now.
New build is up again.
cm-13.0-20160803-UNOFFICIAL-oneplus3.zip
https://www.androidfilehost.com/?fid=24665539028713513
This time with a lot of fixes and changes. Mainly the Them engine has been updated and we are updated to Android 6.0.1 Release 61 (MOB30Z).
It's a clean build again.
Have fun
Click to expand...
Click to collapse
Thanks for update..
How about bug in gallery?
Sent from my ONEPLUS A3000 using Tapatalk
g_Four said:
Thanks for update..
How about bug in gallery?
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
As I use from time to time MTP for filetransfer between PC and Phone I have decided to disable sdcardfs in the sources until everything is fixed.
So we don't have that bug. You could still enable it in build.prop file if you like that.

LineageOS First Build!

The first builds of Lineage are out for the shamu finally!
download.lineageos.org
How do I get rid of the ugly watermark across my screen?
The link to the nightly version doesn't work
Link to nightly worked fine for me. Haven't flashed yet, but it downloaded, albeit slowly.
https://download.lineageos.org/shamu
How to remove this cm to lineage migration build background ?
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
You're supposed to flash nightly over experimental. Just read the instructions...
Dopamin3 said:
People who have the watermark did you flash the nighly or experimental?
From my understanding the experimental build is only used for migration from CM and will have that watermark no matter what, the nightly build should have no water mark. I believe they posted this info on their site.
Click to expand...
Click to collapse
can confirm - no watermark at nightly building!
Strange how everytime I try to download the nightly it fails. No matter what browser I use
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
coremania said:
You mean permissive, but you can use stock kernel enforced, a bit tricky, you need to root with supersu, latest beta sr3 runs fine. Superuser from los page doesn't recognize viper4a for root at all. I flashed latest arise and supersu, reboot, viper4a still not recognized for root, uninstall viper4a driver, supersu recognize viper4a now, confirm it. Reboot to recovery and reflash latest arise. Now it's working.
If you want Dolby too you have to use blackbird kernel and stay permissive.
Click to expand...
Click to collapse
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works without any trouble ...
MartinN6 said:
Thanks for advice!!
And yes of course - sorry - I mean "permissive"
I flashed "Viper4Android_Cleaner_v1_3_Android_7x.zip" and than "ViPER4Android_2.5.0.5_guitardedhero.zip"
... and it works witout any trouble ...
Click to expand...
Click to collapse
Good, if it works that easy, but there was something about the cleaner, don't remember right now exactly, but it breaks something. May it was dolby.
Edit: using the cleaner always kills cast connection, that's why I didn't use it anymore
MartinN6 said:
first run with lineage - every thing works fine!
Does anyone know, how I can get SElinux "enforcing"? - other kernel? whichone? - need it for using Viper4Android
Click to expand...
Click to collapse
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Is there an updater built in or do we flash all updates? Reading in other threads that ppl get a update notification when a new build is available. I'm on experimental cuz the nightly link didn't work when I tried last night
Dopamin3 said:
Kernel Adiutor Mod should let you toggle that (requires root) under the Misc Controls tab. I would imagine the ad-filled subpar original Kernel Adiutor from the Play Store would too but I wouldn't recommend using that.
Click to expand...
Click to collapse
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
MartinN6 said:
Thanks!
I got it and it (Kernel Adiutor mod) works great!
Now AdAway works again (need SElinux permissiv) - that's very good!
Click to expand...
Click to collapse
How did you get those SOFT keys from. Pixel
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
sorry I don´t understand what you mean with "SOFT keys" ?
Edit: Aah now I know!
Yes, it's from the mod - link next post! ->
hashtag_harsh said:
How did you get those SOFT keys from. Pixel
Click to expand...
Click to collapse
https://forum.xda-developers.com/nexus-6/themes-apps/cool-pixel-mod-android-7-1-1-t3532951
Here you go
---------- Post added at 19:57 ---------- Previous post was at 19:54 ----------
LeroViten said:
Guys, whats your baseband or radio? My proximity sensor isn't working properly on LineageOS...
Click to expand...
Click to collapse
Latest
https://forum.xda-developers.com/ne...-nexus-6-recovery-flashable-fastboot-t3066052

[GUIDE][6/27/17] Magisk V13 + Rom + Passing SafetyNet + Working Modules for Pixel

I am creating this guide for Magisk v13 and working modules. Please let me know if there are additional ROMs that this guide works with, but I am trying to keep the steps as simple as possible.
Magisk Installation Instructions:
Download Latest PureNexus / PA ROM and follow those instructions
Boot into the ROM and go through the initial set up, at this point verify that SafetyNet is passing. If it is not you may need to factory reset and re-install your ROM.
Reboot into TWRP
Flash the attached modified Magisk-v13-Pixel (from Goodwin_c)
Flash the attached verified boot signer (from Chainfire)
Reboot the System
Uninstall the version of Magisk Manager that shows up in the drawer
Install the attached version of MagiskManager_v13_new5.apk (from Goodwin_c)
Open Magisk Manager (you may need to wait a bit, I had to clear it from my recents a few times before it launched and asked for file system permissions)
Go to the app settings and tick on Magisk Hide
Re-run SafetyNet and verify it's passing
Working Modules
I will create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
Modules I have modified to work with Pixel:
Emoji One - systemlessly replaces emojie font with Emoji One.
Tethering Enabler - enables tethering on phones where it is disabled by the manufacturer/provider.
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
mac796 said:
Is v13 working for you. I tried it when he first released it. Very glitchy. Went back to 12. A few of us did. That and we couldn't restore a backup with TB.
Click to expand...
Click to collapse
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
uodii said:
These still looks like the ones @goodwin_c created. If that's the case, then yes, it's very glitchy and you are better off sticking to v12. It is a good starting point though and hopefully he can get an updated v13 working soon!
Click to expand...
Click to collapse
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
mac796 said:
I was just curious why a guide was made with V13 this might scare people off wanting to run magisk on a pixel V12 is way more stable
Click to expand...
Click to collapse
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
That's cool maybe I'll give it another shot.
chadgauth said:
I haven't had any issues yet, but I've only been using it for a few days. I have the Arise module installed and have been using Dolby Atmos while maintaining a clean SafetyNet
Click to expand...
Click to collapse
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
uodii said:
What rom are you using? The issue I came across that Goodwin confirmed was that root seemed to work, but apps like Titanium Backup didnt work properly. Are you running any apps that require root? And do they seem to perform correctly?
It also looks like he released a v13_new5.apk on his AFH account. Are you still using new1? Just curious if the new5 version might fix any previous issues.
Click to expand...
Click to collapse
Yeah, I haven't tried Titanium backup, I'm using Solid Explorer and Greenify with root and they seem to work alright. I am still using new1, I will update to new5 and play with Titanium to see if I can get it to backup and reinstall an app
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
I'm very interessted about how to modify modules to work with Pixel device !
chadgauth said:
I may create a video guide on how to modify modules to work with the Pixel phones until Magisk is fully updated to support Pixel.
I'll attach some working modules that I have modified.
Click to expand...
Click to collapse
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Only custom rom? Anyone tried on stock image?
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
maflin18 said:
The zip failed to flash for me. Couldn't unpack boot image.
Pixel running PN 7.1.1, twrp RC1.
Click to expand...
Click to collapse
Try TWRP RC2
TENN3R said:
Only custom rom? Anyone tried on stock image?
Click to expand...
Click to collapse
The stock image should most likely work, if it works for you or someone else in this thread let me know and I'll update the OP.
y2kbugleung said:
Excuse me, may I know is there a thread by Goodwin_c publishing the modified Magisk?
I just want to keep updated to his modification.
I have been using his modified Magisk v12, but finding it from RR thread.
There is no way to know if it is updated or not.
Click to expand...
Click to collapse
I'll update the post date in brackets when I make updates here. Goodwin_c does not have his own thread, so I've just been monitoring his android file host account. The original poster has not updated or maintained his guide from the RR thread, so I created a new one to be as up-to-date as possible and include modules as I modify them.
foski said:
The only one I need is Tethering Enabler! Emoji One would be nice to have as well...
Click to expand...
Click to collapse
I've included both of those. I basically have been using beyond compare to compare the arise module that works with pixel to other modules and re-zipping them and testing with my device.
I see. Thanks.
Btw do you know the difference between v1 and v5 apk?
It seems MagiskHide is gone on v5?
I have tried Magisk-V13 on Pixel-XL with stock ROM.
I haven't tried it with stock kernel, since SafetyNet won't pass (as far as I understand).
Tested with Elemental-X + MagiskManager-v1, SafetyNet does not pass. App always says "cannot use Play service"
Tested with Kirisakura-Rebase-1.36 + MagiskManager-v1, SafetyNet passes.
MagiskManager-v5 does not come with MagiskHide, so I assume it cannot handle SafetyNet.
Both MagiskManager v1 and v5 loads very slowly.
Before the UI could be used normally (it means Magisk is loaded?), ROOT cannot be obtained.
So those boot-up root-required action would probably fail.

Categories

Resources