[ROM][7.1.1] SlimRoms N [tbltetmo/tbltecan] - T-Mobile Note Edge Android Development

[ROM][7.1.1] SlimRoms N [tbltetmo/tbltecan] - T-Mobile Note Edge Android Development

{
"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"
}
To God be the glory, my Slim7 Nougat project finally works on the Note Edge!
This is a very slimmed down version of Android Nougat, almost a "vanilla" experience with a few tasteful perks! By design, this ROM comes without root for those who wish to have a "pure" version without the entanglements that come with root, but it can also be easily rooted by using chainfire's SuperSU (see below for instructions and downloads). In it's default form, it is perfect for those banking apps, workplaces, and games that require you to have a phone without root. No need for tricks or hacks, all while having the latest and greatest Android on your Samsung Galaxy Note Edge.
If you do decide to use root, then you will be pleasently surprised to know that Substratum and layering works with this ROM. While not perfect, for the most part it functions well in my initial testing. However, if you find problems arise after installing a theme, please remove the theme to make sure it is not a substratum related issue.
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
This SlimRoms Nougat ROM was built for the TBLTETMO/TBLTECAN using modified LineageOS TBLTEXX trees. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK. The updater script would need to be edited. Chime in if it worked on your device.
A huge thanks to the SlimRoms Project team!
Disclaimer: SlimRoms is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make SlimRoms, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
Click to expand...
Click to collapse
A huge thanks to the SlimRoms team!
Another huge thanks goes to mickey387 for pioneering Nougat on the Note Edge!
Downloads:
Rom Download link:
http://www.mediafire.com/file/varcd...-7.1.1.build.0.7-UNOFFICIAL-20170223-0838.zip
SuperSU download: (There may be other versions, 2.79 is the only version I personally tested.)
http://www.supersu.com/download
Gapps link:
http://opengapps.org/
-Which I personally only tested Nano. Be sure to choose "Arm" and "7.1".
If you want the AKLU kernel - Better performance and battery life:
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
Be sure to only choose the SLIM 7 version.
This Rom has been stable for me, however, Nougat is new, so be prepared for some little hic-ups here and there. Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
!!!FIRST BOOT TAKES LONGER THAN 5 EARTH MINUTES TO COMPLETE!!!
!!!IF YOU FLASH SUPERSU, IT WILL REBOOT SEVERAL TIMES DURING INSTALL, THAT IS OKAY!!!
Installation instructions ( TO BE NON-ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and if desired, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
--> OPTIONAL - After first boot, then go back to recovery and install the AKLU kernel.
Installation instructions ( TO BE ROOTED ) :
-YOU MUST BE ON THE 6.0.1 MODEM and BOOTLOADER!
-Download ROM, and SuperSU, AKLU kernel, and gapps, and put them on your phone's external storage.
-Reboot into recovery mode - TWRP (I personally installed this using 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps -- Optional.
-Let the system boot up.
-Go back to TWRP.
-Install AKLU kernel. - Optional
-Reboot to system.
-Go back to TWRP.
-Install SuperSU.
-Let the system boot up. Note that it may reboot a couple times during the boot animation, that is okay.
-Enjoy!
Code:
What works:
So far everything that I have tried works, such as
- Camera for video and pictures (use orange camera app, not traditional blue camera app.)
- Phone calls/receiving
- Data 2g/3g/LTE
- Bluetooth
- WiFi
- PTP/MTP
- GPS
- WiFi hotspot
- Multi-Window
- Fingerprint sensor* See notes.
etc....
What doesn't:
- Notification LED only shows RED and YELLOW. To show YELLOW, choose CYAN as the notification color, and it will show up YELLOW. All other color choices appear RED.
- The automatic time zone function forgets where you are alot. Use the manual time zone instead.
- Choosing to reboot the phone sometimes takes a loooong time. It may be better to Power off and then start the phone, which is faster for some reason.
- Built in blue camera app sometimes gets "stuck" or freezes or crashes, I tested several other camera apps, and all worked fine, including the orange camera app and opencamera from the fdroid repository.
- There is no "edge" feature at this time.
- Let me know in the forums if you find other issues.
Main Features:
- Merged with android-7.1.1_r13
- SlimDim, now with 100% more dimming
- SlimAction, Splits screen action (long press app in slim recent)
- SlimRecents, an alternative recents
- Notification log (long press statusbar header)
- Kill app from notification (long pres app notification)
- Substratum support (if rooted)
- OmniSwitcher built in so the kill function works with or without root.
- Advanced reboot (found under security settings).
SlimRoms XDA Forum: http://forum.xda-developers.com/slimroms
Source Code: http://github.com/SlimRoms/
Official websites: http://www.slimroms.net/ or http://slimroms.org/
ROM OS Version: 7.1.1 Nougat
ROM Kernel: Linux 3.10.40
Based On: AOSP and LineageOS.
My device trees: https://github.com/alaskalinuxuser/
Created 2017-02-23
Last Updated 2017-02-23
Change log:
Code:
20170223
-Fixed home button screen wake.
-Fixed WiFi hotspot.
-Added texting app.
-Added OmniSwitcher as optional switcher/tasker (makes a good "edge bar" since you can pin apps).
-Initial release!

Notes about the rom:
Notes about the rom:
Fingerprint sensor:
I have successfuly used the fingerprint sensor, but it is a bit sketchy. To make it work:
- Go to register your fingerprint under security settings.
- I registered all 5 of my fingertips all at once, by clicking add another, and only 2 of them "stuck" when I clicked done. I redid it registering one finger over and over again several times, and it eventually registered and stuck.
- If after clicking done, the fingerprint settings says x-number of fingerprints registered, then those fingerprints are working. Once registered, then you can use it in apps, and for the lockscreen, which did work about 1/2 of the time for me.
- If the lockscreen does not show the "fingerprint" icon, reboot to make it appear.
Open Source apps:
There are quite a few really good open source apps included in this build, such as:
Browser app
Amaze file manager app
SatStat GPS app
Camera app (orange one)
All of these great apps and more can be found at https://f-droid.org/repository/browse/. You can also download other great apps there like music players, games, and everything else you might need. The Fdroid app allows you to maintain up to date version control and simple downloading and installation of these apps and is a lightweight alternative to the Google Play Store. that is certainly worth taking a look.

Running smooth as butter. Thanks man!

JeremySS said:
Running smooth as butter. Thanks man!
Click to expand...
Click to collapse
Thanks for the kind words! I also use Slim as my dd on the note edge. Simply elegant. Thanks to the slim team.
I do find the led color for notifications to be an interesting problem.
When setting notifications: If I choose red, it shows up greenish. If I choose yellow, it shows up red. If I choose cyan, it shows up yellow.
But the first flash is always red.
I'll have to work on that.

Does it work with tbltexx
It says it is not compatible with tbltexx.
Thanks
Tunc

eresen said:
It says it is not compatible with tbltexx.
Thanks
Tunc
Click to expand...
Click to collapse
Correct, this is the tbltetmo version. You need this version, which is compatible with your phone:
https://forum.xda-developers.com/note-edge/development/rom-slimroms-n-t3562516

Im having a problem with ir. Sure remote control worked before i changed rom to this one and now it doesnt. Any ideas?
Other than that its top work fella.

any reason why certain applications force close? Like skype for example. Starts, loads for a brief second and force closes

Hi,
I flashed this rom on N915W8 through TWRP. All went well but no sim card was detected. I am very new to this stuff and this is my first post. I really like the rom so would like to know should I do to make it right.
Thanks.

blue_waturz said:
Hi,
I flashed this rom on N915W8 through TWRP. All went well but no sim card was detected. I am very new to this stuff and this is my first post. I really like the rom so would like to know should I do to make it right.
Thanks.
Click to expand...
Click to collapse
Sorry, I no longer have my note edge. However, you could try flashing these data zips: https://forum.xda-developers.com/showthread.php?t=3546110
Hope that helps!
Sent from my LG-H811 using XDA-Developers Legacy app

AlaskaLinuxUser said:
Sorry, I no longer have my note edge. However, you could try flashing these data zips: https://forum.xda-developers.com/showthread.php?t=3546110
Hope that helps!
Sent from my LG-H811 using XDA-Developers Legacy app
Click to expand...
Click to collapse
I reverted back to stock rogers rom to save time and phone. I will need to try again.

Can't install it ..keeps saying E: unknown
Sent from my SM-N930F using XDA-Developers Legacy app

kachhh said:
Can't install it ..keeps saying E: unknown
Sent from my SM-N930F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Are you installing this on a 930F? This is for a N915 T.
Sent from my LG-H811 using XDA-Developers Legacy app

No sorry I figured out...I'm on 915T is just my browser was downloading it incomplete.. I just changed the browser and is working
Sent from my SM-N915T using XDA-Developers Legacy app

I flashed the rom but when I connect to beats earphones the mic doesn't work..... Is there a fix for this issue? Besides that it looks good so far, thanks

Related

[DISCONTINUED][AOSP][6.0.1] Fire Nexus ROM - [SUBSTRATUM] [M4B30X] [22 Oct 2016]

{
"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"
}
Fire Nexus ROM
Introduction
This ROM is based off AOSP marshmallow. I have merged changes from CAF and Cyanogenmod to enable this boot on our HDX devices.
Features
- AOSP with optimisations from CAF
- Open GAPPS nano is built-in
- Clear all recents
- Advanced Power Menu
- Substratum Theming Support
- Init.d Support
- SuperSU is built-in
Prerequisites for Installation
- Unlocked bootloader is a must
- TWRP 3.0.2-0 installed
- This does NOT work with Safestrap
Downloads
*** Please do NOT create any mirrors ***
- Fire Nexus ROM for APOLLO
- Fire Nexus ROM for THOR
Issue List
- Sideloading of some apps may be necessary
- Bluetooth
- LTE
- WiFi may need to be manually toggled after wakeup
Kernel Source Code
- https://github.com/CyanogenMod/android_kernel_amazon_hdx-common
Credits
- AOSP
- CodeAurora Forum
- Cyanogenmod
- Substratum Team
XDA:DevDB Information
mm-fire-nexus-rom, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-10-22
Last Updated 2019-10-02

Release Notes / Change log
22 October 2016
- Initial Release
- Xposed needs testingConfirmed as working

Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).

schr01 said:
Thank you for this new rom. I have testet it with the open camera app, but it showes me a picture whith a rotation error (180 degrees).
Click to expand...
Click to collapse
Yes, rotation is a problem. If I remember rightly it is the same issue as with other custom ROMS. Try locking the screen rotation in the correct aspect then running open camera again. The app should then appear correctly.

Thank you for your tip. It works.

Woohoo!
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.

Davey126 said:
Initial findings after a quick 15 min test:
- clean flashed (Thor) with Xposed 23; booted fine (wiped system/data/cache/dalvik)
- installed a handful of essential apps from Play Store - no compatibility issues
- installed GravityBox 6.1.6 and tested a few tweaks that tend to be problematic on some devices/roms - no issues
- big test: installed my preferred messaging app which hates everything including no-SIM devices - worked perfectly!!
Good to hear Xposed is working and your problematic messaging app
Very excited on first take! Sadly, rom hangs w/dirty flash or if CM 12.1 data partition restored after initial boot. Will need to fall back temporarily until I have time to perform a manual migration of existing app portfolio. No ding against the rom; dirty flashes are always a crap shoot and I have been bringing this one forward since Jelly Bean (yikes!). I have an old Fire Nexus KitKat build I may try too. Hate rebuilding from scratch.
I would expect CM 12.1 data restore to not work. The framework in this ROM is very different from CM 12.1.
You might also run into problems dirty flashing from the KitKat build of the ROM.
Clean flash would be recommended in both cases when coming from an older or different ROM.
The only (minor) suggestion is to include recovery and soft boot options to the Advanced Power Menu. No big deal as I can easily get this from Xposed; just seems a natural as it was noted in the feature set (not normally part of AOSP). Love having GAaps Nano and SuperSU built in; avoids many initial flash headaches and simplifies upgrades.
Kids sometimes use my tablet so having the reboot to recovery options etc can be a problem.
Really nice work, @ggow. Clean and simple.
Edit: I did need to enable 'all rotations' in GravityBox as expected on this device. Likely could achieve the same result via Nova or other third party tweak. Native setting was largely ignored.
Click to expand...
Click to collapse
Thanks for the detailed feedback :good:

Thank you for nexus rom.
Thank you for nexus rom.
It works almost good for me, but google contacts cannot synchronize gmail account.
In nexus5 (6.0.1), it can be synchronized by contacts->settings->accounts->google.
In thor, contacts->settings->accounts->(not shown google).

Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?

rootnooby said:
Will the install work with twrp 2.8.7 or is 3.0.2 a requirement?
Click to expand...
Click to collapse
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)

ADB Backup/Restore
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?

I had no installations problemes with TWRP 3.02.

Davey126 said:
May have found a bug: adb backup and restore commands are ignored. Command is accepted (Win 10 x64 host) but no response from device. Other adb commands appear to work fine. Tinkered with the various USB modes but behavior is always the same. Also tried setting/clearing device debug password. With no password there is a 3-4 sec delay before returning to command prompt; with a password exit is nearly instantaneous. Did some searching online but not a lot of good info on the net. Works on CM 12.1 build (Thor).
Anyone else experiencing this?
Click to expand...
Click to collapse
Will take a look, before the next release.

ggow said:
Will take a look, before the next release.
Click to expand...
Click to collapse
Thanks. Two reasons for wanting this:
- transfer apps and all associated data between devices
- create targeted backups or nandroid clone on devices with limited internal storage
Titanium used to be the go-to choice but it hasn't been updated in nearly two years (struggles on Android 6+) and also utilises adb functions for transport.

FYI - I was able to get this rom to dirty boot a CM 13 build but that's as far as it went. Processor pegged on lock screen judging from heat and sluggish response (5+ sec per key press). Obviously a clean flash is highly recommended by dev but was looking for a path to bring my existing CM 12.1 build (apps and data) forward. Probably hang out on Lollipop for awhile as it meets my needs with no meaningful loss of functionality vs Marshmallow with Greenify, Nova and a few Xposed modules thrown in.
Might give Nexus 6 another whirl once adb backup/restore is working (see previous posts for background). I do miss AOSP ...
Also sad CyanogenMod can't get their act together and fix the ridiculous bug that throws up a fur ball when SIM access is requested on CM 13 if there ain't no SIM card installed (hello...tablets!!). Regression was introduced in a nightly build last March and never resolved.

Camera isn't working on apollo

@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.

chipsugar said:
@ggow Nice to see the work you're doing for the hdx. I'm just curious - before I decide to upgrade to this- are there any plans to get Bluetooth stable on this ROM or is it going to have the same issues as on other ROMs. Thanks.
Click to expand...
Click to collapse
I have been looking into Bluetooth as I need this working too. But with these new versions of android running with old binaries, it becomes really difficult to get everything working as it should.

Davey126 said:
FWIW - install worked fine on 3.0.0.x (3.0.2 has permission issues)
Click to expand...
Click to collapse
Installed with 2.8.7, Apollo, with no issue!

My Apollo was on 4.5.5.1, then installed with Safestrap v4, and then Fire Nexus KK ROM. After waiting weeks for the 1-Click bootloader unlock tool, I finally decided to go for the step-by-step unlock procedure and managed to have my Apollo unlocked yesterday afternoon.
I clean flashed your TWRP 3.0.2.0 and this Fire Nexus MM ROM immediately after unlock and am really pleased with the new ROM and the newly found freedom. The ROM works quite well so far except for 1) camera (tried Snap Camera and Camera MX), 2) Google Contacts cannot sync with Gmail account.
As I came over from SafeStrap v4, is there any old files and folders need to be tidy up?

[ROM][7.1.2] AOKP Nougat with built in side bar! [tbltetmo][tbltecan]

{
"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"
}
To God be the glory, my AOKP NOUGAT project finally works!
My fellow T-Mobile-ians, you have been left out of AOSP development long enough! By God's grace I was able to use mickey387's great tbltexx work, and completely adapt it to our tbltetmo after extracting all of the needed firmware from our 6.0.1 stock roms! No data zips are required here! It is all built in!
This is not a dirty unicorn. This is the original unicorn, the AOKP. Now made out of Nougat! That's right, all of the AOKP stuff you love, plus LineageOS, plus a built in side bar, and more! All wrapped up into one! With tons of settings from status bar tweaks to button remaps, it's all here and ready to rumble!
Click to expand...
Click to collapse
**** This is an UNOFFICIAL ROM. Install at your own risk! ****
You must be on a 6.0.1 Bootloader with a 6.0.1 modem! I suggest if you are unsure, flash stock 6.0.1, then install this ROM!
Downloads :
THE AKLU KERNEL CAN BE DOWNLOADED HERE (OPTIONAL - BUT DOES FIX WIFI HOT SPOT ISSUE) :
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
Download:
http://www.mediafire.com/file/4ebke9zgq6i76wo/aokp_tbltetmo_nougat_unofficial_2017-05-01_1117.zip
OLD DOWNLOAD:
https://www.mediafire.com/download/cpa96oxnyavaot8
Gapps link:
http://opengapps.org/
-Which I personally tested Arm 7.0 Nano.
No data fix zip is required for T-Mobile phones! This ROM is actually built for the T-Mobile variants (tbltetmo, tbltecan)!
Be sure to follow these installation steps very carefully, as they may be different then what you are used to.
Installation instructions:
-Put your phone on the 6.0.1 Bootloader and Modem
-Download ROM and gapps, and put them on your phone or external storage.
-Reboot into recovery mode - TWRP (I personally installed this using Mickey's 3.0.0-0).
-Backup what you had. (Just to be safe.)
-Wipe. (I personally wipe everything prior to flashing new roms, but at least do the basic wipe.)
-Install Rom.
-Install Gapps. - Optional
-Reboot to system and enjoy!
I do not recommend installing superSU on this ROM! SU permission is already built in, and superSU has been causing problems with the rom. Please read the thread for further details.
What works :
Code:
+ Phone calls/receiving
+ Data 2g/3g/LTE
+ Bluetooth
+ WiFi
+ MTP
+ GPS/Glonass
+ S PEN
+ Split screen
+ The WiFi hotspot does work with the AKLU kernel!
etc....
What doesn't :
Code:
- The edge panel is not implemented at this time. The screen wraps around the edge. But there is an app bar feature under ROM CONTROLS!
- The capacitive buttons work, but do not illuminate.
- The WiFi hotspot does not work with the stock kernel, it does work with the AKLU kernel!
- Fingerprint sensor is really flaky. I got it to work once, but only once. Most times it will not register.
- I have not found any big errors, fault crashes, or problems yet. Please let me know if you find an issue!
This AOKP N ROM was built for the tbltetmo, the T-Mobile Samsung Galaxy Note Edge. I have not tried this on any other device, but you are welcome to try it AT YOUR OWN RISK. You will need to edit the META-INF updater script to accomplish this.
Code:
Disclaimer: AOKP is not responsible for any damages to your device.
All of my work is completely available for any who wish to use or modify it. I didn't make AOKP, the device trees, or vendor blobs. I simply used and edited existing material. A huge thanks should go to those who actually created this stuff.
AOKP XDA Forum: http://forum.xda-developers.com/aokp
Source Code: https://github.com/AOKP
Official website: http://aokp.co/
Device trees: https://github.com/alaskalinuxuser/
ROM OS Version: 7.1.2 Marshmallow
ROM Kernel: Linux 3.10.40
Based On: LineageOS and PA, and AOSP.
Created 2017-02-16
Last Updated 2017-05-02
Change log:
Code:
20170501
+ Edited camera settings to help with third party apps that use the camera.
20170428
+ Fixed recent button.
20170427
+ Synced with AOKP source!
--> Security update to April 5th, 2017
--> New battery icon options.
--> New powermenu torch option.
--> Long press hotspot tile to go to hotspot settings.
+ Added kexec hardboot to both default and AKLU kernels to allow this to work with multirom.
+ Borrowed from mickey to fix the notification led lights for proper color display.
20170316
+ Synced with AOKP source!
--> Security update to March 5th, 2017
--> Numerous AOKP fixes for the ROM itself. See the change-log under Rom control.
+ Added in possible VOIP fix for voip app problems.
20170301
+ Synced with AOKP source!
--> Merged with Android 7.1.1_r21
--> Added PIE controls
--> Security patches updated to Feb 5, 2017
--> Now FULLY supports OMS/SUBSTRATUM
+ Screenshot issue fixed
+ SDcard read from File Manager fixed
20170217:
-Fixed WiFi hot spot issue with AKLU kernel, but must be downloaded from the kernel thread.
20170216:
-First build release.
-Built with AOKP 7.1.1 source
-Added Kernel Adiutor and Omni-Switcher

Thanks!
A huge thanks to the Android Open Kang Project team!
@OldDroid
 @Mickey387
@deadman96385
And all of these great testers (some for other devices, not all helped me test this rom, but helped me test the Note Edge in general, as well as provided valuable feedback!) :
@Aaren11
@xNNism
@beany23
@swecon
@1freedude
@lostinlife33
@faizan'
@gavin10
@brainwasher01
@hosny1964
@xcube1

Features and Screenshots!
Features and Screenshots!
- Advanced Reboot
- Omni-Switcher
- Kernel Adiutor
+ Rom Control:
+ App Launchers
- App Circle Bar
- App Side Bar
- Gesture Anywhere
+ General
- cLock settings
- Recents settings
- Wakelock Blocker
+ Hardware Keys
- Backlight control
- Power button options
- Launch vibration control
- Home button controls
- Recents button controls
- Long press options, double tap options
- Kill app back button option
- Volume buttons wake
- Volume button playback controls
- Keyboard cursor controls
- Volume button reorientation
- IME features
+ Lockscreen
- Media Cover art
- Display music visualizer
- Show weather
- Blur background
- Fingerprint auth vibration
- Double tap to sleep (DT2S)
- Disable quick settings
- Show lockscreen clock and date
- Lockscreen notification count
+ Notification Drawer
- Brightness slider
- Brightness icon
- Rows in portrait and landscape modes
- Columns
- Tile Animations
- Advanced data tile
- Smart pulldown
- Quick pulldown
+ Power Menu
- Animation choices
- Screenshots
- Screenrecord
- Airplane mode
- Sound Panel
+ Sound
- Various sound settings
- Volumn step control
+ Status Bar tweaks
- Network traffic
- Clock style
- Double tap to sleep (DT2S)
- Superuser indicator
- Icon controls
- AOKP logo
+ User interface
- Toast controls
- AOKP animations
- Transparency controls
AND MORE!!!

Notes.
A place for rom notes....
Background image:
https://qlfiles.net/2017/01/07/upload-fractal-images/
The background images that I used in this ROM came from the Quiet Learner. You should check out his mathematical artwork, including 3D mandelbox images!
If the screen looks red-ish, check the settings->display->live display options, you may want to turn them off, it is a low light sensitive display option.
T-Mobile users with device model = unknown:
If you are using a N915T (like myself), the fix is very easy!
-Open /system/build.prop in any text editor
-Anywhere in the file, add this line:
Code:
ro.build.model=SM-N915T
Save and exit, then reboot your phone. You can check "about phone" under settings, you should see yourself as SM-N915T, and apps like XDA should report you as Samsung Galaxy Note Edge.
Apps:
Swiftkey Keyboard - This keyboard can be set so the keyboard does not wrap around the screen.
https://play.google.com/store/apps/details?id=com.touchtype.swiftkey
Spen Command - This app cost a few dollars, but enables the Spen to be somewhat smart again, rather than just a pointer stick.
http://www.emandt.net/Android/SPenCommand/Website/
If you find something else that will help other users, please let me know by posting in the thread!

Hey everyone!
The AKLU kernel is online for the AOKP 7.1.1 Nougat rom! It fixes the WiFi hot spot issue!
https://forum.xda-developers.com/no...droid-development/kernel-aklu-kernel-t3558419
20170217
- Fix WiFi hot spot error for Nougat.
- Overclocked the GPU from 600MHz to 633MHz
- Overclocked the CPU from 2649MHz to 2688MHz
- Added governors: Bioshock, Lionheart, Nightmare, Darkness
- Removed input boost, use cpu boost instead
- Added I/O schedulers: FIOPS, ZEN

Would this work in a ATT version if I replace the modem.bin component? Any possibility of damage to try it?

spoiledsport said:
Would this work in a ATT version if I replace the modem.bin component? Any possibility of damage to try it?
Click to expand...
Click to collapse
Spoiledsport,
That is a great question.
Most AT&T phones have a locked boot loader, do they not? If you have an unlocked boot loader than it is possible to try, and no damage should arise. But if you have a locked boot loader it will fail to flash.
If you get it to flash, I do not know if it will work or not.
This ROM is flashed through TWRP, there is no modem.bin file in it, it doesn't over write the modem file.
Hope that helps!

Thank you for this. Will flash it and the kernel shortly.

Awsome rom. Using since last night absolutely great. Just fingerprint having issue other than that great work...

JeremySS said:
Thank you for this. Will flash it and the kernel shortly.
Click to expand...
Click to collapse
Syed husaain said:
Awsome rom. Using since last night absolutely great. Just fingerprint having issue other than that great work...
Click to expand...
Click to collapse
Thank you for the kind words!

?Hey something is wrong with this ROM for some reason SU Binary is not stable and I can't change SELINUX to PERMISSIVE. So I it won't allow me to change it is there a fix for this I try updating Super SU Binary on Recovery and still doesn't work please fix and am runny 6.0.1 Boot and Modem N915T how cant I fix this for some reason it says not root detected please fix

miguelr4720 said:
?Hey something is wrong with this ROM for some reason SU Binary is not stable and I can't change SELINUX to PERMISSIVE. So I it won't allow me to change it is there a fix for this I try updating Super SU Binary on Recovery and still doesn't work please fix and am runny 6.0.1 Boot and Modem N915T how cant I fix this for some reason it says not root detected please fix
Click to expand...
Click to collapse
Miguelr4720,
You should not install super su on this rom. It has a built in root and controller.
Hope that helps.

Loaded up and so far is running smooth with the exception of some weirdness around the back and recent apps hw buttons. They seem to be acting properly but are not lighting up. I went into ROM control and tried to adjust. Interestingly when I have the screen open for adjusting time on they do light up, but then go black again after closing the adjustment box. There is also no vibration when hitting those 2 buttons. Im not getting anything useful in the logs that I can see. I tried reflashing but no change in behavior. Any suggestions? Am I the only one seeing this?
I'll post this in the International thread too in case it is effecting other models.

By the way, this rom supports substratum in legacy mode.
I tested the inversion ui theme successfully.

ROM: aokp_tbltetmo_nougat_unofficial_2017-02-16_1258.zip
Yea I Dont Know What is Causing this problem the SU Binary is not Install Propertly on You Rom
And I Also Install Your Kernel and The Issue With SU Binary not Detected still Persist And I Still Cant Fix It And You Told Me Not Install SR3-SuperSU-v2.79-SR3-20170114223742.zip So I Have not and the problem still Occurred.
still cant change SELinuxModeChanger to PERMISSIVE.
1. Viper4Android FX Driver Wont Install??
2. Cant View Files on The SD Card On File Manager?
3 .SELinuxModeChanger Wont Work Says Root Not Detected?
Please Test This Problem on Your Side and Leet Me Know if there a New Fix For This.
Or Instruction On How to Install This Rom Correctly on N915T I Have Try all the Method on your Page And Still SU Not Install Property. other Thing Like Grant And Denied is the only thing that works on SuperSU
There Has To Be A Fix For This i dont Understand SuperSU WORKS Grant and Denied
and other things are saying that root is not detected really i dont understand.
I Never Had Seen a Problem Like This Before on the Last Rom 6.0.1 aokp room i never had this issue your Check the Rom Image to see if SU Binary are fully install Correctly on the new rom aokp_tbltetmo_nougat_unofficial_2017.
i try everything i try Re-flashing the Phone On Odin Using The 6.0.1 N915T Image and Re-Root and erase system data factory reset and i am still having the issue with some tools Root Not Installed?

miguelr4720 said:
ROM: aokp_tbltetmo_nougat_unofficial_2017-02-16_1258.zip
Yea I Dont Know What is Causing this problem the SU Binary is not Install Propertly on You Rom
And I Also Install Your Kernel and The Issue With SU Binary not Detected still Persist And I Still Cant Fix It And You Told Me Not Install SR3-SuperSU-v2.79-SR3-20170114223742.zip So I Have not and the problem still Occurred.
still cant change SELinuxModeChanger to PERMISSIVE.
1. Viper4Android FX Driver Wont Install??
2. Cant View Files on The SD Card On File Manager?
3 .SELinuxModeChanger Wont Work Says Root Not Detected?
Please Test This Problem on Your Side and Leet Me Know if there a New Fix For This.
Or Instruction On How to Install This Rom Correctly on N915T I Have Try all the Method on your Page And Still SU Not Install Property. other Thing Like Grant And Denied is the only thing that works on SuperSU
There Has To Be A Fix For This i dont Understand SuperSU WORKS Grant and Denied
and other things are saying that root is not detected really i dont understand.
I Never Had Seen a Problem Like This Before on the Last Rom 6.0.1 aokp room i never had this issue your Check the Rom Image to see if SU Binary are fully install Correctly on the new rom aokp_tbltetmo_nougat_unofficial_2017.
i try everything i try Re-flashing the Phone On Odin Using The 6.0.1 N915T Image and Re-Root and erase system data factory reset and i am still having the issue with some tools Root Not Installed?
Click to expand...
Click to collapse
Miguelr4720,
You should not install SuperSU, because the rom already has root permutation built in.
1. I do not support v4a, but you are welcome to mess with it.
https://forum.xda-developers.com/showthread.php?t=2191223&page=2497
According to the official v4a thread, others cannot get it to work on nougat with SuperSU. PLEASE DIRECT ALL V4A QUESTIONS TO THE OFFICIAL V4A THREAD.
2. Thanks for pointing that out. I see that the built in file manager does not let you look at the SD card. I use the amaze file manager, you can use another manager, until I can fix it.
3. I do not understand the problem. The kernel I made is already selinux permissive. Do you want to set it to enforce instead?

Thank You for Understanding and for finding the fix for it
Thank you for leeting me know and hope you fix soon.? your rom Mr Aka i hope you fix soon the room is really nice I love it and I give you good credits leet me know when its ready and more Stable to be use. your room looks nice and greet on 7.1.1 and i really like it and I love it... SO I WIIL Remain On The OEM stock software rooted I have the backup files from my Original Rom and su bunary are not install on my System i have mine Permit running. Everything works good on mine SuperSU app work and opens. So mine is working OK please leet me know when its ready i love the rom. Am also a fan Dirty Unicorn i love the unlock custom rom running on the latest software 7.0.1 I love the room
Everything works good on mine so I wait and am also running x posed on my System and it works and
Main thing X-posed Dev its working on 7.1.1 framework and he expected to lunch the tool in May Or June
And x posed it's not available 7.1.1 sad hope they fix thanks for doing a greet job and I give you good credits for this new akop custom rom I love it leet me know when the room Becomes a little Better We can be a good Team
X-posed frame-work. .
Viper Works too
DOLBY WORKS.
Thank you for leeting me know when its ready leet me know when is coming. When it becomes more stable to use I can wait for 7.1.1 version to work and become avaliable. With the fix and Also I See its running on beta now so I guess it will take you sever all hours and time. leet me know when is its fix
And have a more stablet rom beta Thank You
T-Mobile N915T Root New York City thank you. Good Credits Good Work

Follow up... After an indeterminate time the back button stops working all together and requires a reboot.

There Are Bugs On The Betta I Dont Recommend to use
JeremySS;71120910]Follow up... After an indeterminate time the back button stops working all together and requires a reboot.
Miguel Rodriguez
Yea there are several bugs on this room and he expecting a fix soon please be patient have you FOUND ANY Fixes For The Room i see you a High Senior???

JeremySS said:
Follow up... After an indeterminate time the back button stops working all together and requires a reboot.
Click to expand...
Click to collapse
Great feedback. I haven't noticed that problem myself, but I reboot frequently. Can you do me a huge favor? When the back button stops working, can you immediately try it 5 times, then pull a log cat and send it to me? Thanks, then I can see the problem.

[ROM][SiriuZ V3.0][GT] EMUI 8.0 P20 Lite by Catuva21

{
"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"
}
V 3.0 - EMUI 8.0DONOT COPY MY WORK, Ask for Permissions
Code:
- I am not responsible for the damage of your cell phone if you do not correctly perform the steps
- loser warranty
- if you are not sure better not to touch and leave this page
COMPATIBLE WITH
with all versions, P20 lite, remember to know your original compilation if at any time you want to return to stock for example ANE-LX3C25 with this data you can return to stock.
This version is based on the official modification of EMUI, activating functions that are in the high-end versions, adding some modifications for their better performance.
REQUIREMENTS:
- EMUI 8.0.0
- Activate the OEM unlocking, which is in adjustment / developer options and leave it so forever to avoid conflict.
- unlock the bootloader.
- install the recovery that I will leave, automated from windows-linux
Guard the rom in an external memory.
Turn off the cell phone press the plus and power buttons until you have the TWRP window
Press WIPE
Press FORMAT DATA
Write the word "yes" without quotes and accept, just do the work
Press BACK to go back several times to the main window.
Press WIPE, then ADVANCE WIPE
Verify that the partition DATA this in the f2fs extension
Mark: Dalvik, cache, data, internal storage, system
IMPORTANT !: do not mark "micro sdcard".
Once you have marked, slide the "swipe to wipe" arrow to clear it.
Go back to the main sale, press INSTALL
Press SELECT STORAGE
Switch to Micro SDCard to find the rom.
Look for the MORFUZ rom and flash
At the end of the installation press "wipe davilk-cache", wait for it to finish.
Reboot system.
Congratulations now will start the rom MORFUZ
It seems that Huawei modified the modem partition in the September-October patch and the MORFUZ kernel does not work incoming and outgoing calls.
-IMPORTANTonly install this module from the root Magisk options if incoming and outgoing calls do not work.
https://mega.nz/#!F7oXzSRZ!8uuSCIx4UTbuWkTEYoFmTXTCwvIr6Reuc1vyq6OIhw0
Rom Siriuz
https://mega.nz/#!tYBjTQhC!yPbPXkazpQUy7bzLdm33rEapihBB8iVmSGlGxy1RweI
TWRP Mod by catuva21 - VERSION 2
unzip, the file is automatic
https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
TELEGRAM GROUP
https://t.me/joinchat/ERAhfQ8kyF6_iH5nMun5dg
Contributors:
CATUVA21
Credits:
- Openkirin Recovery TWRP
- Alexxx1
- Chisetdel31260
ROM OS Version: ANE-L
ROM Kernel: Stock
ROM Firmware Required: EMUI 8.0.0
Version Information:
Status: Stable
Created on: 2018-06-30
Last Updated on: 2018-09-10

DESCRIPTION ROM SIRIUZDETAILS OF THE ROM
SIRIUZ 3.0
- Base firmware P20 lite (security patch for September).
- Custom kernel MorfuZ now works wifi and bluetooth.
- Huawei ID integrated and running.
- New bootanimation.
- New bootlogo.
- Percentage activated from start, for other models.
- Activated the font change in themes.
- New topics.
- 7 themes to change the font customization.
- Yorreciones de camara.
- Youtube advance updated.
- Adaway ad blocker.
- VolTe Activated.
- Magisk 17.1
SIRIUZ 2.6
- P20 lite base firmware (August security patch).
- MorfuzKernel 2.1 selinux Permissive.
- Turbo GPU.
- Added support init.d.
- Added busybox.
- Huawei ID back.
- Boot profile for the Darknnes-Blu_Active kernel within init.d improves performance.
- Change of the MTweaks auditor kernel application.
- Added Lent AR fun camera function.
- Magisk 16.7.
- Increase bitrate of photos and video, improve quality.
- Application of return mail.
- Youtube Mod Updated.
- New Gboard keyboard.
SIRIUZ 2.4
-Base firmware P20 lite(security patch jun).
-Activated Dual Speaker.
-Added DolbyAtmos in Music.
-New Boot logo.
-Added custom watermark for the P20 lite.
-Now without patches.
-Installation mode AROMA-INSTALLER.
-Music: stock or crack.
-Camera: stock, Mate10Pro or P20Pro.
-Root: Magisk or Supersu.
-Navbar, Use the fingerprint sensor as a navigation bar.
-Solid explorer, Kernel Auditor, Quick Reboot.
-MxPlayer.
-Sony Music.
-Eliminated the data space.
-Deodexed (improves optimization).
-Improvements in the quality of photos, video and sound..
-It eliminated unnecessary google applications.
-Added Call Recorder.
-Added Youtube Mod (function in the background).
-Activated multi-user X5.
-Keyboard change, google.
-Reduction of size of icons.
-Activated glove mode.
-Mtu 1500.
-Explored files improved.
-Added main screen design 5x5,5x6,6x5.
-Added more applications of social networks of Twin cloning.
. * facebook, faceboot lite
. * messenger, messenger lite
. * whatsapp, whatsapp mod
. * instagram
. * snapchat
. * telegram
. * twitter
. * mega
. * creativefrends
. * microsoft office

r2

when i go to security options settings app crashes
cant setup fingerprint id
oh now it works after playing with the instalation settings

I got an error during installation and start bootlooping, latter with more time I'll try again.
Thanks to share your work with us.

Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post

same problem with me

brandox0 said:
Error finishing the installation:
set_perm: some changes failed
Other problems:
-Does not detect micro sd
-You can not configure a screen lock method (settings close when you try to enter that section)
-Developer options can not be activated (the settings are closed when you press compile)
Those problems are what happened to me, I followed the installation instructions exactly as it says in the post
Click to expand...
Click to collapse
The rom is working or not?

thanks for the rom!
followed the install instructions except i didn't install the TWRP321_OREO_P20LITE.rar because i previously installed it following these instructions.
chose to install the custom kernel and SuperSU. not sure right now what else. i will write it down when i try the next build.
i encountered the following issues:
-error finishing the installation: set_perm: some changes failed during flashing (could this be because i didn't install your modded TWRP?)
-unable to set the lockscreen options
-unable to set up fingerprintid
-settings crashes when attempting to enable dev options
-sd card isn't detected within the fw
once i saw the sdcard isn't detected, i tried to recover from my latest backup but TWRP wasn't able because /system was only mounted as read-only (could this be as well because i didn't install your modded TWRP?).
ended up having to reflash stock from erecovery, rerooting and reinstalling TWRP in order to restore from my last backup (maybe i did something wrong?).
after reading the features list, i personally would use it as my main rom. i'd love to see it with viper4android included and with an all dark theme though but that's just me.
thanks for your work! looking forward to more!

luigi997 said:
The rom is working or not?
Click to expand...
Click to collapse
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.

brandox0 said:
Well, if you eliminate the fact that the fingerprint reader or any other screen lock method does not work, you can not use the micro sd and the developer options are not available. So yes, the rom works.
You can try to urge it, maybe you're lucky and do not have mistakes.
Click to expand...
Click to collapse
If i try to uninstall an app, the system reboot.
I've installed the modded kernel

Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^

[email protected] said:
Anyone with no issues? Can be used as a daily driver?
Please report back testers ^_^
Click to expand...
Click to collapse
Nope, so far I haven't seen anyone reporting positively. No fingerprintid and no security features makes the rom pretty much unusable as far as I've tested and seen on the thread. I'm awaiting to see how this develops..

Success
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.

riorabel12 said:
This rom is working prefectly.. i have keep on trying to re install the rom.I always follow the exact instruction, and i have found out. You will have a set_perm: some changes failed. IF you mark check the navbar, and status bar while in aroma installer.. I have able to use everything. Ill try to make a screenshot of it.
Click to expand...
Click to collapse
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!

madalone said:
Awesome! I'll try again!
Did you flash the recovery included in the post?
What do you mean with "If you mark check the navbar, and status bar while in aroma installer"?
Thanks for the feedback!
Click to expand...
Click to collapse
YES. I HAVE FLASH THE RECOVERY. AND WHEN YOU FIRST DO THAT... AND YOU SHOULD PUT THE ROM INTO YOUR SD CARD..
YES, IF YOU MARK CHECK THE NAVBAR ANF STATSBAR. WHILE CHOOSING YOUR DESIRED APPS. YOU WILL SEE THAT IN THE VERY LAST PAGE OF THE AROMA INSTALLER. WHERE YOU HAVE THE OPTIONS. NAVBAR STATSBAR, SOLID EXPLORER, KERNEL AUDIATOR, AND the QUICK REBOOT. SO JUST MARK CHECK THE SOLID EXPLORER,KERNELAUDITOR,AND QUICK REBOOT..
SO TRY IT NOW. AND GIVE ME SOME FEEDBACK IF IT WORKS IN YOU. ALSO KINDLY TRY TO DO A SCREENSHOT. I DONT HAVE OTHER PHONE TO TAKE A SHOT ON IT. KUDOS THANKS

ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
brandox0 said:
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?
Click to expand...
Click to collapse
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
edit2: as i am stubborn, i reflashed the rom with the custom kernel and Magisk. root is on and the phone seems to run smoothly.

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting). is that the kernel failing to install?
after a cache wipe, i rebooted the phone. the phone boots as expected.
Click to expand...
Click to collapse
I also want to try again, but I'm still not sure.
So far, how is the rom working? Is there a fault signal mentioned above?

madalone said:
ok so i flashed the provided recovery and the rom following the instructions with the following options in aroma installer:
Kernel: Morfu2kernel
Root: SuperSU
Camera: P20 Pro
Music: Stock
Kernel Auditor
Quick Reboot
the installation went through except bootimage patcher failed at decompressing ramdisk (failure, aborting).
edit1: after a cache wipe, i rebooted the phone. the phone boots but no root.
tried to flash SuperSU through TWRP but failed.
wiped data/cache/dalvik/system & reflashed rom with Stock kernel & Magisk no bootimage patcher errors. after a cache wipe, rebooted & phone has root :victory:
so far i'm still getting all my apps installed. i'll letcha know how i get on with it.
Click to expand...
Click to collapse
I worked perfectly, the only problem is that mobile became very slow.

rapza4 said:
I worked perfectly, the only problem is that mobile became very slow.
Click to expand...
Click to collapse
i had that plus overheating but after what i did in edit2 it was gone and the phone runs smoothly.
on another note: is it possible to make this rom have init.d support somehow? it'd be cool for stuff like Liveboot..

[10][OFFICIAL] CarbonROM | cr-8.0 [z3c]

My feedback about CR8.0 (weekly build 20200513-0206) with gapps pico, magisk 20.4 and ~75 user apps.
Using TWRP 3.3.1-z3c-20191212-sar from here
Xposed (RiRu 20.2 from magisk repo, EdXposed-YAHFA-v0.4.6.2.4529 from here) works without problems (1st screenshot).
I'm not using internal data encryption because of compatibility problems between ROMs/versions, tired to restore backups each time I flash new ROM.
About 700MB of RAM free just after boot, with stock launcher.
Battery drain fast, but my battery is very old, no complain.
Pros:
+ reliably fast
+ everything works including GPS, BT, calls/data, hotspot and all my apps
+ no problems with audio routing and mic sensitivity
+ camera is ok but I use OpenCamera anyway
Cons/bugs:
- still no 5ghz wifi in Russia (I use my magisk-patch to fix this, may also help with other regions, try if you meet this bug)
- ongoing call can be hanged accidentally by double-tap in any place of turned off display (e.g. by cheek) if tap-to-wake feature is active (here is my workaround using Automate tool, works like a charm). I'm not sure if this bug belongs only to my phone or to any z3c, but it was like forever on any AOSP-based ROM, starting with Android 7.
- broken size for "Aeroplane mode" button/icon in power menu (see 2nd screenshot)
- ringtone sound become a bit quieter after half a second from start of incoming call
- overall loudspeakers volume is not loud enough
Features I'd like to have in this ROM:
1) choose clock position in statusbar (only at left in CR8.0)
2) brightness control by sliding in statusbar without opening it
3) mess up digits on the PIN unlock screen [Carbone Fibers > Buttons > Scramble PIN]
4) unlock instantly when entering last digit without confirmation
5) long press power button to turn on/off torch while display turned off [Carbone Fibers > Buttons > Toggle torch]
6) restrict/disable power menu while phone locked
7) disable notification panel while phone locked
8) set minimal time between notifications on per app basis
9) wake by volume rocker buttons
10) increasing ringing volume
11) debugging over network (settings in devs options, absent in CR)
Most of this stuff available in LOS and AEX roms, but also all (except: 7,10,11, with bugs: 6) can be achieved in CR by using GravityBox xposed module.
Thank you @Myself5 for continue work with our lovely z3c.

Thank you very much for supporting our cute device
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?

Found a BUG: can't set PIN/pattern to lock screen, getting bootloop after try to set it and reboot.
I use z3c as my daily driver, so I need screen lock, can't use this ROM until fixed. Hope I'm not only one who faces this bug.
BigBrother84 said:
Did anyone tried edxposed with xprivacylua, Viper4android, Netflix. Do they work?
Click to expand...
Click to collapse
Not sure about these apps, but at least GravityBox[Q] and App Locale 2 I can NOT get working on this ROM with EdXposed v0.4.6.0_beta(4471) (YAHFA). As well as on latest february build of LOS 17.1 (but worked fine on january build). May be I should try some newer versions of EdXposed (like ones from "canary" repo or something), but I need screenlock bug fixed first to use this ROM and more of free time. Btw, everything works perfect on LOS16.

Hooin Kyoma said:
Wiped all except micro sd. Stuck at "Setup wizard keeps stopping", system unusable. With and without gapps.
Ok I just clean-reinstalled ROM and made first boot WITHOUT SIM CARD INSERTED and it's boot fine. Btw my SIM card PIN-locked (if it's important) and it never caused any problems in LOS17.
Also I reserve this post for my review.
Thank you @Myself5 for continue work with our lovely z3c.
Click to expand...
Click to collapse
The Setup Wizard is still work in progress, and we just discovered nobody tested it with a SIM so far. We'll take care of it, thanks.
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?

Myself5 said:
As for your screen lock issue in the other message: are you encrypted by any chance? Also I assume that's not happening on the lineage17.1 builds you mentioned?
Click to expand...
Click to collapse
Tried with and without encryption. With and without Gapps. With and without SIM card. Always same result. Everytrhing fine until you set screen lock PIN either from Setup Wizard or from Security settings. First of, unlock method stays "Swipe" after set PIN. And if you reboot, system's boot to desktop and auto-soft-reboot (without sony logo) after few seconds. And yes, this not happening on LOS17.1

Installation immediately fails for me.
Code:
Patching system image unconditionally...
E1001: Failed to update system image.
[COLOR="Red"]Updater process ended with ERROR: 7
Error installing zip file '/sdcard/CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200208-1428.zip'[/COLOR]
Updating partition details...
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
Failed to mount '/appslog' (Invalid argument)[/COLOR]
...done
[COLOR="red"]mount -o bind '/data/media/0' '/sdcard' process ended with signal: 6
E:Error creating fstab[/COLOR]
Tried to update from your previous CR7 build (CARBON-CR-7.0-OPAL-UNOFFICIAL-z3c-20190819-2110), using TWRP 3.2.1 from here. Nothing actually got written, so previous installation is fine.

yxagasasgas said:
using TWRP 3.2.1
Click to expand...
Click to collapse
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.

Hooin Kyoma said:
Try 3.3.1 from here, it support Android 10 with "system as root". And I'd recommend wipe all except internal storage and perform clean install.
Click to expand...
Click to collapse
Doesn't work for me, just blackscreens and reboots. Tried installing it both via TWRP app and fastboot (although strangely enough, even though adb worked, fastboot didn't in Windows, had to boot to Linux), no dice, so went back to my previous TWRP for now.
Would be nice to know what's up with that, but I haven't fiddled with any of this in a long time. Ever since CarbonROM appeared, my Z3C pretty much "just worked" and I never had to do much of any fiddling.

New build uploaded just now has the SetupWizard fixed. The lockscreen bug is getting looked into right now.

Uploaded a new build. Contains some additional lockscreen clocks but more importantly, the PIN issue is fixed.
Code:
f8d3b9c5519b91baba7a917d99b7f09e CARBON-CR-8.0-PAX-UNOFFICIAL-z3c-20200225-1530.zip

Myself5 said:
PIN issue is fixed
Click to expand...
Click to collapse
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.

Hooin Kyoma said:
I can confirm this. Also Google' Setup Wizard passed fine with SIM. Thank you!
What is bother me - the Carbon Fibers menu - as I recall, it usually have much more settings than I can see in this build (see screenshots). This is only to me or some global restriction?
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
the camera was not working for me as well, but after some restarts it fixed itself. i dont know how that happened (even tried the xperia camera port from magisc) but i cannot confirm weather that did the trick..

Hooin Kyoma said:
Also camera app not working, this is odd. Though I didn't try it on fresh system (before google's backup restore). Someone please check.
Click to expand...
Click to collapse
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.

okij said:
You could try if the camera starts working after deleting the folder /data/credmgr with a root file explorer and then rebooting. By doing this, the credmgr folder with the credmanager files are rebuilt by the system, which can help fixing camera issues.
Click to expand...
Click to collapse
Thanks for the tip mate. But it didn't help in this case.
Btw, today I installed (again) latest LOS17, tuned it, rebooted many times, played with microG/magisk/xposed modules - camera worked fine all the time.
Next (steps to reproduce): wiped cache, dalvik, data and system, installed only CR-8.0 (20200225), rebooted to system, skip anything, camera WORKS! Did nothing, just rebooted again, and got "Can't connect to the camera"! I think this is a BUG and hope I'm not the only one who faces it.
I still have a question about Carbon Fibers menu, why it lack items/options? I can't even reposition statusbar clock to right without using "third-party" apps like GravityBox xposed module.
Also, kind of "feature request": time to time I use adb from PC (we all do i think), and I hate to connect cable to micro-USB port, cuz it's weak and can break soon if use freqently. I use magnetic port/cable for charging and "ADB over network" toggle in Developer Options for ADB operations. One of the reasons why I prefer LOS is because of this "must have" thing, they even have tile in QS for toggle it quickly! Can it be added to CR?

the "cant connect to the camera" returned unexpectedly..

Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?

Thank you for your hard work!
Does encryption work properly?
What works
Viper4android works
Sony Device Dummy works with official Sony apps
Spotify works

Myself5 said:
Hum this new OP looks interesting.
And what is this Twitter Post?
And did someone say May Security Patches?
Click to expand...
Click to collapse
Great, this looks interesting indeed!
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1 (because everything is working well and rock stable on this older version and thankfully you still release monthly security patches for it.)
Have you done some thorough testing of cr-8.0 on the Z3/Z3c devices before making it now official and is everything working (e.g. full camera support and proper in-call audio, which had problems on shinano devices on Android 9 and 10 before)?
If so, I might give it a try this weekend.
Thank you and keep up the great work! :good:

okij said:
Today cr-8.0 also was offered as an OTA update on my Z3c which so far I still have on cr-6.1
Click to expand...
Click to collapse
I tried dirty-flash on my cr-6.1, but without success - I can't boot my phone because it stuck in boot animation.

[ROM][11][flox][OFFICIAL] crDroid 7.31Google Nexus 7 2013 repartitioned

{
"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"
}
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/11.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Kernel: https://github.com/mantinan/android_kernel_google_msm
Device: https://github.com/LineageOS/android_device_asus_flox
Download:
ROM
Known issues:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid Community Telegram
crDroid Updates Channel
Donate to help our team pay server costs

bestiatester said:
Code:
*** Disclaimer
I am not responsible for any damage you made to your device
You have been warned
crDroid is designed to increase performance and reliability over stock Android for your device also attempting to bringing many of the best features existent today
Features:
https://github.com/crdroidandroid/crdroid_features/blob/10.0/README.mkdn
Flashing Instructions:
Flox is how LineageOS has chosen to name the repartitioned version of flo, which means that if you haven't repartitioned your Nexus 7 2013 you must repartition it before even trying to flash this. Please read LineageOS instructions here before trying anything.
Pre-installation:
Recovery (TWRP Lineage Recovery)
ROM (Download from here)
gapps arm (MindTheGapps OpenGapps)
Sources:
ROM: https://github.com/crdroidandroid
Download:
ROM
Known issues:
Battery is shown as charging at 0 mA.
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Visit official website @ crDroid.net
crDroid <device> Telegram
crDroid Community Telegram
Donate to help our team pay server costs
Click to expand...
Click to collapse
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!

Mr.Conkel said:
OH MY GAWD I'M IN LOVE everything working great here. This rom is surprisingly smooth with MicroG installed. Long live the Nexus 7!
Click to expand...
Click to collapse
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!

GeekyTanuj said:
Can you share the steps you used to get microG to work? I am having a hard time getting them to work on LOS 18.1 and This ROM as well!
Click to expand...
Click to collapse
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!

Mr.Conkel said:
Well the steps can be different on Los 18.1 because Signature spoofing is not built in to Los but it is on Crdroid which makes it was less of a pain because you don't need Xposed for things to work correctly.
So starting with Crdroid go about your normal setup and install Magisk per normal. Afterwards you're going to need to select a package from this link normally minimalAP or the Standard package should be just fine. These packages have everything you need to get MicroG working with the Google Play store the only difference between minimal is Aurora Services and the location backends which a tablet doesn't necessarily need but it depends on what you use it for.
After flashing this through recovery follow these steps..
Initial Setup:
- Complete the setup wizard actions as you prefer
- Open the app drawer and long-press on Play Store to choose the App Info button
- Go to Permissions, then Additional permissions and change Spoof package signature to Allow, go back to home screen afterward
- Run the microG Settings app — The rest of these instructions are taken almost directly from https://gitlab.com/Nanolx/NanoDroid/-/blob/master/doc/microGsetup.md
- Choose Self-Check at the top of the list, and start tapping on the second item, System grants signature spoofing permission which should prompt a permission request
- Everything should now be checked on the Self-Check screen, go back to main microG Settings screen
- Choose Google device registration and enable the Register device switch, then go back
- Choose Cloud Messaging and enable the Receive push notifications switch, then go back
- SafetyNet doesn't actually work or pass right now, but you can try enabling it in the same manner as above
- Choose Location modules and enable at least one "Network-based Geolocation module" and one "Address lookup module". I usually only turn on Deja Vu Location Service from the top list; it seems to work well enough for driving directions here, and of course choose Nominatim from the lower list because it's the only one there
- This is important: Reboot now before you add a Google account or do anything else to the Play Store app
- After rebooting, go back into microG Settings app and make sure that all of the Self-Check items are still checked, and then make sure that Google Device Registration, Cloud Messaging, and SafetyNet are still enabled — if they were not, enable them.
- Now get app info for Play Store, clear cache (yes, again), then launch the app
- Add your Google account, and verify that it will show your app library — Purchased apps won't show as paid-for yet, this will take approximately 24 hours until Google decides it likes your new Android ID
- Open Settings app, then Accounts then choose your Google account, then chose Personal info & privacy, and make sure Allow apps to find accounts is enabled
- That should be everything!
Then after a few hours (a day or so) you should have complete access to you paid apps and you're good to go. Let me know if you need anything else!
Click to expand...
Click to collapse
Thanks for this guide! Really helped me get things going smoothly! Love this ROM.

Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you

jojo33680 said:
Hi,
I need dt2w but i can't activate it, does thé kernel support it?
Can you Hello me please?
Thanks you
Click to expand...
Click to collapse
you need to use the Exkernel to enable dt2w. Here's the latest one: Link.

I am running an old 7.0 Resurrection ROM on my N7.
TWRP is installed & bootloader unlocked so I suspect I would just need to repartition & install?
No clue why ADBgives me these errors in powershell.
fastboot : The term 'fastboot' is not recognized as the name of a cmdlet, function, script file, or operable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ fastboot
+ ~~~~~~~~
+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException

For those who have partition with a different method like me that is NOT flox so they can flash other ROMs, replace this in the ROM zip. All I did was remove assert get prop that checks to make sure your tablet is the right one for the ROM. It won't flash if you're not using flox repartition so I changed it to allow it to flash. I have 1.6gb of system space and am able to flash this ROM, opengapps pico, magisk and custom kernel with no issues running a non flox repartition.
updater-script
drive.google.com

Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.

bestiatester said:
Hi!
In the known issues I descrived:
When scanning the face unlock the camera shows left side of video Ok but right side darkened, cameras seem to work ok on other apps.
Can anybody please confirm that this is happening also for you?
And if you know why it is failing or even better, how to fix it... that would be great
Thanks in advance.
Click to expand...
Click to collapse
I confirm I have the same problem

Hello all,
I follow the guides and the installation went smoothly, thanks for the really good job you've done.
I'm new in the crDroid world so sorry if the question seems stupid: As the power button of the Nexus 7 is not easy to access, how can I activate the double tap to wakeup ?
Some years ago the tablet was installed with aicp, and the DT2W was working. So I'm a little bit disappointed if it is not working now.
Thanks.

Davidtre07 said:
DT2W
Click to expand...
Click to collapse
This material will help you: 01 ... 02 ... 03 ... 04

lyushiK said:
This material will help you: 01 ... 02 ... 03 ... 04
Click to expand...
Click to collapse
With Anykernel installed works like a charm !
Thanks.

Davidtre07 said:
With Anykernel installed works like a charm !
Thanks.
Click to expand...
Click to collapse
If you have a patch or pointer to the code that makes it work... just let me know and I'll try to add it.

I'm testing a patch for the charge current to be shown ok, seems to work, if all the tests are ok I'll ship it in with the next release.

No I don't have any patch to propose, I just followed the links provided by @lyushiK.
As far I understood, to work you have to recompile a kernel with DT2W hability and you have to activate it with the right flag in the kernel.
From my side what I've done:
Installed Magisk (patched boot.img)
Installed this kernel: https://androidfilehost.com/?fid=7161016148664820402
And to finish added to magisk this module: https://github.com/ipdev99/mModule_dt2w
Reboot and it works !

In Magisk I see the module is looking in /sys/ for "doubletap*" or "dt2w*" or "wake_gesture".
If it found one of the files then activate it (echo 1 in the file)
But still, you have to have the right kernel !

Thanks very much, this Rom is so smooth and running great. The only thing I've noticed is that the icon size and text is very small when using the tablet in landscape mode but fine in portrait mode. Any changes I make to the icon size from the settings apply in portrait but when switched to landscape stay as really small, is there any setting I have missed to enlarge them?

Thank you for the great work!
Just for feedback: I can confirm the camera issue, too, though it doesn't bother me.
Another small thing I noticed: during the initial setup my device was called Pixel 6 Pro (first I thought, I chose the wrong image) but in the settings it says correctly "Nexus 7".

Database Info

welcome