[ROM][Treble][9.0]AOSP 9 for Huawei Mate 10 Lite - Huawei Nova 2i (Mate 10 Lite / Honor 9i) ROMs, Ker

Hi,
{
"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"
}
Android Open Source Project 9.0 Pie for Huawei Mate 10 Lite
*** Beta Version ***
About
Code:
[CENTER]Android is an open source software stack created for a wide array of devices with different form factors. The primary purposes of Android are to create an open software platform available for carriers, OEMs, and developers to make their innovative ideas a reality and to introduce a successful, real-world product that improves the mobile experience for users.
[/CENTER]
Warning
Code:
[CENTER] * Your warranty is now void.
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.[/CENTER]
Working
Code:
[CENTER]* Boot
* Touchscreen
* Adb
* Audio
* Bluetooth
* Camera
* Internal/External storage
* Sensors
* Wifi
* RIL
* NFC
* Almost everything
[/CENTER]
Not Working
Code:
[CENTER]
* Hotspot Wifi
maybe there are some minor issues !
[/CENTER]
Note: At first boot maybe you will get a bootloop to bootanimation but after it your device will boot up.
Installation
Code:
[CENTER]* you must also have this recovery version installed : TWRP(make sure you got latest version installed!)
* go to TWRP and do format data and then a full wipe (system, data, cache, dalvik/art cache) !
* install AOSP rom
* flash gapps and root (optional)
* reboot to system
* Enjoy !!![/CENTER]
Download
Code:
[CENTER][URL="https://sourceforge.net/projects/askucciodevelopment/files/ROM/Aosp-Pie9.0/aosp-9-20180822-hi6250-askuccio.zip/download"]aosp-9-20180822-hi6250-askuccio.zip[/URL]
[URL="https://github.com/ianmacd/MagiskBuilds"]Magisk Builds for Huawei/Honor[/URL]
[URL="https://forum.xda-developers.com/android/development/gapps-unofficial-opengapps-builds-t3828141"]Unofficial OpenGapps[/URL]
[/CENTER]
NOTE: These gapps are unofficial and are in beta stage so you can maybe face a lot of crases. It is recommended to install it after first boot and once installed you need to unistall Setup wizard because it will crash a lot !
Credits
 @Askuccio_DROID
 @flex1911
 @phhusson
 @haky 86 @Dil3mm4
Kernel GPL policy: We are not violating kernel gps policy because we are making a treble based rom, so it is just a system image. Kernel is the default one provided by Huawei in Emui 8.x
I don' t have the device for testing, if you want faster releases please contribute for buying it. Thanks
DONATIONS
Regards !​
XDA:DevDB Information
Android Open Source Project, ROM for the Huawei Mate 10
Contributors
DarkJoker360
Source Code: [url]https://github.com/DarkJoker360[/URL]
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: Emui 8.x unlocked bootloader
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 9.0
Beta Release Date: 2018-08-26
Created 2018-08-26
Last Updated 2018-08-27

Reserved

So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices

SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
You could send screenshots of the rom? Please

@connnor kenway, Of course Here are some screenshots, as you wish. They're mostly done after I backed up stuff, so the wallpaper isn't the same and there are a lot of apps installed already At first, there are only apps that provide basic functionality of the phone such as clock, camera, gallery, file manager, music, calc, dialer, messages etc. but there's no browser, only WebView Shell. If you need any other screenshots, just tell me, I'll attach
What's the most exciting for me is that Digital Wellbeing Magisk module works here so it's great Fingerprint scanner works seamlessly as well, better than on stock EMUI ROM And it boots faster too! It's visible for the first sight, but I also tested it vs other Mate 10 Lite with stock EMUI without root, with locked bootloader etc. and the difference was really noticeable, not miliseconds, but seconds. Over 5 seconds less, I suppose.
Also, for me, official Magisk 16.7 works too, so I guess it's not necessary to use ianmacd builds?
I have two things to ask tho. Front camera has native 9.7 Mpix 18:9 option, but the rear one does not (only 2.1 Mpix and 0.9 Mpix are available I believe). Is there possibility to include one? Also, will there be any kernel with possibility to change SELinux to permissive?
From bugs, there are a few I have noticed, but they're rather minor. I'll leave a list here:
- Wi-Fi HotSpot is not working [known]
- USB options are greyed out [known, I guess]
- while transfering big files through USB OTG, USB stick disconnects and reconnects after a second
- sometimes white line between navigation bar and black-themes apps (such as YT Vanced)
- sometimes camera randomly doesn't work after reboot
- Viper4FX always needs to reinstall driver (idk if ROM's issue, but had everything running well on other phones)
- Magisk Manager crashes when checking SafetyNet status got fixed, probably issue of Magisk Manager rather than OS itself

SevenUp9 said:
@connnor kenway, Of course Here are some screenshots, as you wish. They're mostly done after I backed up stuff, so the wallpaper isn't the same and there are a lot of apps installed already At first, there are only apps that provide basic functionality of the phone such as clock, camera, gallery, file manager, music, calc, dialer, messages etc. but there's no browser, only WebView Shell. If you need any other screenshots, just tell me, I'll attach
What's the most exciting for me is that Digital Wellbeing Magisk module works here so it's great Fingerprint scanner works seamlessly as well, better than on stock EMUI ROM And it boots faster too! It's visible for the first sight, but I also tested it vs other Mate 10 Lite with stock EMUI without root, with locked bootloader etc. and the difference was really noticeable, not miliseconds, but seconds. Over 5 seconds less, I suppose.
Also, for me, official Magisk 16.7 works too, so I guess it's not necessary to use ianmacd builds?
I have one thing to ask tho. Front camera has native 9.7 Mpix 18:9 option, but rear does not (only 2.1 Mpix and 0.9 Mpix I believe). Is there possibility to include one?
From bugs, there are a few I have noticed, but they're rather minor. I'll leave a list here:
- Wi-Fi HotSpot is not working [known]
- USB options are greyed out [known, I guess]
- while transfering big files through USB OTG, USB stick disconnects and reconnects after a second
- sometimes white line between navigation bar and black-themes apps (such as YT Vanced)
- sometimes camera randomly doesn't work after reboot
- Viper4FX always needs to reinstall driver (idk if ROM's issue, but had everything running well on other phones)
- Magisk Manager crashes when checking SafetyNet status
Click to expand...
Click to collapse
Did you install it on a stock ROM? What recovery did you use?

Hi I just install This ROM, I've noticed that when I open setting text texture has low quality. Sometimes blurry.

connnor kenway said:
Did you install it on a stock ROM? What recovery did you use?
Click to expand...
Click to collapse
Yes, I installed it on stock EMUI 8.0.0.334. I used CATUVA21's TWRP.

Allan C. E said:
Hi I just install This ROM, I've noticed that when I open setting text texture has low quality. Sometimes blurry.
Click to expand...
Click to collapse
Didn't notice such bug... Or if you mean some weirdly satisfying "shadow" glitch in apps section then yes, but this gets fixed after all the apps' size gets calculated.
Also noticed that blur all over the ROM right now, with some exceptions such as homescreen, notification bar rolled down or typing. I checked "Disable HW overlays" in Developer options and it fixed the issue, everything is sharp right now. Cheers!

SevenUp9 said:
Didn't notice such bug... Or if you mean some weirdly satisfying "shadow" glitch in apps section then yes, but this gets fixed after all the apps' size gets calculated.
Also noticed that blur all over the ROM right now, with some exceptions such as homescreen, notification bar rolled down or typing. I checked "Disable HW overlays" in Developer options and it fixed the issue, everything is sharp right now. Cheers!
Click to expand...
Click to collapse
Disabling HW overlays fixed my issued. Thanks for info bro. Now I can fully enjoy android pie ?

SevenUp9 said:
Yes, I installed it on stock EMUI 8.0.0.334. I used CATUVA21's TWRP.
Click to expand...
Click to collapse
What modules do you have installed bro?

I've got a question to other users - could you please check SafetyNet status with Magisk Hide enabled and Core mode (to avoid module interference)? For me both basicIntegrity and CTSprofile are false, but idk if it's ROM or rather something with my previous EMUI install (had a few situations where I had corrupt installs that would not pass SafetyNet, I guess).
About modules... These are the modules I use, but keep in mind I don't know if GPU Turbo works and Unified Hosts Adblock downloads hosts, but does not block ads.

SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
Hi! How do you solve the problem with the setup, i check the gps but keep showing the message.
Thx for any help:laugh:

@EeN4, simply check all the permissions for Google Play Services and Pixel Setup in settings and reboot, it should do the trick and the setup should begin shortly.

SevenUp9 said:
@EeN4, simply check all the permissions for Google Play Services and Pixel Setup in settings and reboot, it should do the trick and the setup should begin shortly.
Click to expand...
Click to collapse
I tried the solution you gave me but it doesn't work , i'm gonna reflash the rom and see if that work.
wish me luck hehehe.
thx for the help.

SevenUp9 said:
So far so good! Camera works (quality is utter crap because of a lot of noise, but what should we expect from AOSP camera ), so Facebook, Messenger, Snapchat and all the other apps that need camera don't crash. Until Pixel Experience gets updated with the base of that AOSP, I'm probably going to use it as my daily driver, so I'll report any bugs if I see them persist. I'm going to reboot now and check if system storage is enough to install Gapps. Cheers!
Or... I can just install Lawnchair Launcher v2 for now and Pixel Icon pack
EDIT - checked system partition and it says that the size is 2015 MB and 708 MB is free. Much better than PE, but still needs some work... Stock EMUI has the size of 4431 MB while without system it's 4538 MB iirc. I doubt I can install full or stock Gapps which are the most interesting options for both ROMs as these ROMs are just bare without Gapps. Till memory issue gets fixed, I am forced to use Mini. Well... It keeps saying that the setup will begin shortly but it doesn't Fixed, simply had to check permissions for GPServices
Click to expand...
Click to collapse
camera just dont start at my device. i installed like instructions, what can i do?

@richmaster1o2, try to reboot your phone a few times and if it doesn't work, maybe reinstall the ROM. I experienced 3 times when camera simply would not work after rebooting and I had to reboot one more time. Maybe that's the case

Any update?

can i installed it at locked bootloader?
Sent from my RNE-L21 using Tapatalk

vip.bnda said:
can i installed it at locked bootloader?
Click to expand...
Click to collapse
No, you can't

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][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2018]

{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 7 (nougat), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What works:
Calls/SMS/Mobile data
Wifi
Bluetooth
GPS
Camera (Photo/Video/Flashlight)
Audio
Fingerprint sensor
DT2W
Keydisabler
Notification LED
Torchlight
Broken
You tell me
Source code:
device tree: https://github.com/HighwayStar/android_device_nubia_nx551j
device-common: https://github.com/HighwayStar/android_device_nubia_msm8953-common
kernel: https://github.com/HighwayStar/android_kernel_nubia_msm8953
vendor: https://github.com/HighwayStar/android_vendor_nubia
Clean code with kernel rebased on top of latest caf nougat msm8953 tag. Warning! this rom uses forceencrypt flag for /data partition, same as global stock rom. If you coming from Chinese ROM or other not encrypted /data ROM your first boot can take long. Do not reboot while encrypting, or you will lost all your data. It's recommend to make backup.
Download
2018-09-17
Fixed headset detection issue
Updated Lineage code
gdrive: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180917-UNOFFICIAL-nx551j.zip
Previous versions:
2018-08-22
Moved to common device tree with Nubia Z11 mini s nx549j
Removed unused camera libraries
Fixed Neocharge in offline-charging mode
Updated Lineage code
gdrive: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180822-UNOFFICIAL-nx551j.zip
2018-07-20
* Fixed Google camera crash in HDR+ mode in low-light conditions
* Fixed color "jumps", "blinks", "grayish color" in all HAL3 apps
* Looks like fully working HAL3 mode here
gdrive: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180720-UNOFFICIAL-nx551j.zip
2018-07-16
* Test build with opensource camera HAL. It enables HAL3 mode, but may also add some issues, please test if camera apps you are using is still working fine. Google camera mods working too, with HDR+ in Nexus 5X or Nexus 6P mode(tested with MGC_5.1.018.177624777-41364271.apk (BSG, 2018-07-12) version)
gdrive: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180716-UNOFFICIAL-nx551j.zip
2018-07-10
* Fixed phone crash when using dual sim.
* Set LTE mode on first run to allow to use mobile data for setup
* Added thermal daemon configs to control device temperature
gdrive:lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180710-UNOFFICIAL-nx551j.zip
2018-07-09
* Fixed Phone app crash on Enable/Disable Airplane mod
* Fixed torchligh
* Fixed notification LED. Now buttons backlight red leds blinking on notification
gdrive: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180709-UNOFFICIAL-nx551j.zip
2018-07-04
Fixed high CPU load and high CPU frequencies issue
Removed FM Radio app
Added LTE option to SIM network menu
Fixed call recording
Fixed displayed battery capacity
gdrive: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180704-UNOFFICIAL-nx551j.zip
2018-07-02
Initial build
gdrive: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
mailru: lineage-14.1-20180702-UNOFFICIAL-nx551j.zip
To install this you have to install TWRP first. I can recommend this version, built with same kernel as ROM. nx551-twrp-3.2.1.img
If you want to use google apps use ARM64 Android 7.1 opengapps package https://opengapps.org/.
If you need root use Lineage addonsu or Magisk
XDA:DevDB Information
[ROM][UNOFFICIAL][7.1.2][nx551j] LineageOS 14.1 for Nubia M2 [17/09/2218], ROM for all devices (see above for details)
Contributors
highwaystar_ru
Source Code: https://github.com/HighwayStar/android_kernel_nubia_msm8953
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: LineageOs
Version Information
Status: No Longer Updated
Created 2018-07-02
Last Updated 2018-09-17
Thanks for the work you've done. In the future, plan to go to the official assembly?
Big thanks.
LuigeUA said:
Thanks for the work you've done. In the future, plan to go to the official assembly?
Click to expand...
Click to collapse
Yes, code is done as clean as possible way to be able to go official. To go official it has to be rebased to oreo first. It should be not that hard now.
I can not adjust my fingerprint, go to my home screen when scanning
LuigeUA said:
I can not adjust my fingerprint, go to my home screen when scanning
Click to expand...
Click to collapse
Had this issue too. Have not found fix yet. Workaround is to setup one fingerprint on first boot, it not goes home here. Second fingerprint can be added anytime later, , there is no such issue with second and later fingeeprints.
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
Please install twrp from the first post. It should help.
Api
Hi , amazing work bringing nougat for us , thanks...
I'm testing for few hours and i tried many camera apps without lucky.. tried to enable camera2api for gcam and get force stopped in all cameras , could you help me ?
Another question is , will you bring future updates by OTA ?
Thanks a lot , wonderfull job.
estuardo4 said:
Hello,
Sorry for the noob question, but I cannot install the ROM because I receive an error while installing. Something like "this ROM cannot be installed because it is for device nx551j device and yours is NX551J"
How can I change this parameter?
Thank you for your help.
Click to expand...
Click to collapse
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.
rolandvb said:
it only works with the twrp that is for download on the linage rom downloadpage ,had the same issue.
i did flash the twrp that is advised and did work perfectly.
Click to expand...
Click to collapse
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.
Did test this android 7.1 OS this evening, and there are some bugs,the camera did not work on my phone and goty black screen,with other app camara did work
fingerprintscanner did not work properly and could not remove or add fingerprints ,also phone sometimes loses and has to search again for 4g network while using phone
and got symcard message while sym alreddy did work.
hope you can do something about these issues.
i can say the phone is a lot faster an snappyer compaired to all other roms i did test
it would be great if android 8 will come available with this OS, this will make this phone a up to date phone for a bargain!
I think the M2 will even be faster on android 8
afther testing and tryed to restore my older rom i just backed up my the phone it did not boot and ended with a bick
i did restart phone in twrp and did flash the twrp i did use before and everything was ok again.
So the`re seem to be TWRP ussues between different versions, i did use the original twrp that was relased by TWRP app
First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.
bumperiano said:
First, thanks for the good work. I have found a serious bug, there is no processor frequency control and it is always full. Then heat the phone and drain the battery.
Click to expand...
Click to collapse
Yes, something broken here, will check it out.
The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.
Woah great work! Will be running this as soon as that CPU util bug is squashed Just a thought, you've posted this in the general Android misc thread although we have our own dedicated sub-forum, any chance of moving it there? Might get better visibility? https://forum.xda-developers.com/t/zte-nubia-m2
estuardo4 said:
Is there other way to install? Yesterday I flashed the persistance.img posted by Mauronofrio without problems and now, for the life of me, I can't get my Win10 machine to recognize my device. I uninstalled, restarted with the option of not checking for signature files, installed, nothing. Uninstalled and installed old drivers and nothing. Uninstalled and installed the newest versions from Google and nothing. My win10 pc can't recognize my Nubia
And yes, I tried to make a working USB live image with FWUL but I don't have the technical knowledge to know whats going on and why I can't use it with my Nubia.
Click to expand...
Click to collapse
i confirm the issue that the phone is not recognized in windows 10 ,you can see the partitions but when opening there is nothing so see and empty while it is not and no files can be added.
this is a good start but at the moment this rom is not realy a usable rom, also very strange that it only can be flashed with the twrp provided. you get error 7 and also the message this rom is not suitable
for this phone and i am using the original TWRP provided bij TWRP itself. i don`t want to reflash my phone between different twrp versions to be able to restore my phone.
i had the official TWRP installed and did not work with this rom, so i think this must be corrected to and be compatable with the original released twrp , by twrp.
the twrp provided on the rom downloadpage also does load very slow and takes 3 times longer to load.
LuigeUA said:
The processor constantly operates at the maximum frequency. The battery capacity is 3000 mA/h and not 3630.
Click to expand...
Click to collapse
The battery capacity is 3630 and not 3000
mauronofrio said:
The battery capacity is 3630 and not 3000
Click to expand...
Click to collapse
I know, but Kernel Adiutor showing 3000 mah
LuigeUA said:
I know, but Kernel Adiutor showing 3000 mah
Click to expand...
Click to collapse
nubia ui stock also shows 3000. Do not worry about that.

[ROM][UNOFFICIAL]LineageOS-16.0[Evert][Moto G6 Plus]

{
"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"
}
LIneageOS is a free, community built, after-market firmware distribution of Android re-branded CyanogeMod, which is designed to increase performance and reliability over stock Android for your device.
Code:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
LineageOS is based on the Android Open Source Project and CyanogenMod with extra contributions from many people within the Android community. All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS please visit Gerrit Code Review.
Warning!!!
BackUp EFS partition before installing. .If you lose IMEI , use this backup to retrieve it in future.
Installation
Boot the newest TWRP .img
Flash copy-partitions-AB.zip from second post. (This will prevent device from getting bricked if you are coming from stock rom for the first time. It takes a backup of active slot to inactive slot)
In TWRP, click "Wipe", "Format Data", then type "yes" as prompted.
ADB sideload the newest build
Reboot to fastboot and do fastboot -w via terminal
Boot into "Recovery", this will boot you to either Lineage Recovery or TWRP depending on your choice to install TWRP or not. It is necessary to reboot between ROM flash and GApps/Addon flash due to verity/slot-swap logic.
(Optionally) Flash GApps - Only MindTheGApps arm64 are compatible, OpenGApps are not compatible with A/B yet: MindTheGApps.
(Optionally) Flash SU - you'll need to turn it on from in developer settings after first boot Lineage OS SU Addon. - Magisk works fine, though is not supported.
Reboot
Downloads
Warning
If you are coming from stock ROM and it's your first time flashing lineage, flash copy-partition zip (See second post) unless your device will brick and I'm not responsible
- LineageOS : Unoffical Builds
- TWRP : Get here
Bugs
You tell me
Reporting bugs
DO NOT report bugs if you're running a custom kernel
DO NOT report bugs if you've modifies system files
DO NOT report bugs if you've installed xposed and/or other mods
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Code:
adb logcat > logcat.txt
Code:
adb shell dmesg > dmesg.txt
If it is a random reboot, grab kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Code:
adb shell cat /sys/fs/pstore/console-ramoops
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. Please also do not report known issues or bugs reported in the lastest 5 pages of this thread. Any bug not reported in the bug report format below may be ignored.
Code:
Phone Informations
* LineageOS version
* Gapps version
What you did:
* Wipe data: y/n
* Upgrade from previous official cm build: y/n
* Restore with titanium backup: y/n
You're using (if yes write which one) :
* Task killer
* Phone cleaner / Battery enhancer apps
* Non-stock kernel
* Modified kernel settings
* Other mods
Bug info:
* Last version it worked on
* Repro steps
F.A.Q.
ROOT! ROOT! Give me root or i'll die!!! Where root is???
First of all DO NOT flash any SuperSu/SuperUser/SuperMan zip package to get root. Go to Settings>Developement Settings>Root access and select "Apps Only"
Why no nightly today?
Build failed. Check again tomorrow
When do I have to wipe data?
You must wipe data only when you're switching from another rom or migrating to Snapshot branch from Nightly and vice versa. You don't need to wipe data when you update in the same release channe (this applies to 13.0 -> 14.1 upgrades too)
Will you add <insert awesome feature here>?
I won't. If you write it, submit a commit to gerrit, where it will be reviewed.
The LineageOS team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Kernel Source : Here
XDA:DevDB Information
LineageOS, ROM for the Moto G6 Plus
Contributors
rahulsnair, erfanoabdi
Source Code: https://github.com/LineageOS
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: TWRP
Based On: LineageOS
Version Information
Status: Stable
Created 2018-10-22
Last Updated 2018-12-28
Copy Partition- Initial Setup
Flash the attachement via TWRP
Fantastic, can't wait to try this! :good: The copy-partition zip seems to be missing though? :crying:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Daniel47833 said:
Awesome! Thank you, can't wait to try it out.
Is the copy partitions zip the same as the one on the Lineage OS 15.1 thread?
Click to expand...
Click to collapse
Yes.
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Mara-X said:
"Pixel setup keeps stopping" after flashing Mindthegapps. Which version exactly, am I supposed to use?
Click to expand...
Click to collapse
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
RokCruz said:
When that app stop working select app info, force stop and clear app data.
And try again it'll work
And when you want to restore your stuff it'll show another error: "data transfer stop working" (I don't remember exact name) do the same force stop and clear data but this time allow all the permissions (storage, calls, etc)
Sent from my g(6) plus using XDA Labs
Click to expand...
Click to collapse
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
Try with opengapps nano package
Sent from my g(6) plus using XDA Labs
Mara-X said:
Hmm. Clear data is greyed out, can only clear cache and that doesn't help.
Click to expand...
Click to collapse
? The data transfer tool and Pixel set up both require notification access. Should solve the issue. ??
ksk35695 said:
The data transfer tool and Pixel set up both require notification access. Should solve the issue.
Click to expand...
Click to collapse
Hello, how can I give notification access to the pixel set up? I can't find the option
​
Daniel47833 said:
Hello, how can I give notification access to the pixel set up? I can't find the option
Click to expand...
Click to collapse
Goto Apps & notifications, scroll down to Special app access, There's the noticfication access around the middle of the list.
Always has worked for me in this senario. Good luck.
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
weazie said:
Nice work! Congratulations @rahulsnair + everybody on the team. Wow, did You receive the device on Monday this week?
So, I flashed and I'm writing the journey here and keep editing as I go:
- Is Emergency calling working, can you connect? You can test by calling there and saying that you wanted to test.
- Moto actions - Working!
- Is the camera quality the same-ish? I'd say yes.
- Can I install Moto Camera 2 (Stock)? Yes.
- Tethering (yes) / Hotspot (working) / Bluetooth calling (working) / Casting (working) / NFC (working).
- Since "Copy A -> B Partitions zip" makes a copy of the current ROM to another slot (correct?), how to restore from there? I know how to restore from twrp backup.
[STROKE] EDIT: At the moment I'm getting "Pixel Setup keeps stopping" Cleared cache. Did not help. I have no navbar. For some reason Gapps didn't flash correctly I think. Trying again from there.[/STROKE]
EDIT2: You have the wrong link in OP. It points to 8.x MindTheGapps
Here's the 9.x version:
https://androidfilehost.com/?w=file...0cea2c259bd6b42b84ebd97a7d581187be08d20207d94
The same error manifests in 9.0 MindTheGapps. I got a little further though. But it's possible to plough through. Just reboot if you get stuck like I did and you will get there.
* Still no navbar during setup. (This might possibly be remedied by enabling on-screen navbar before flashing gapps, maybe: "settings -> system -> buttons).
* When connecting to wifi at setup, it will connect, but nothing happens, no "next" button"
* Not able to skip restoring backup from Google account.
* Data Migration Tool shows that its pixel version. Give permissions by clicking "App Info", "Permissions", check all.
* I have a strong feeling I have flashed MindTheGapps for Pixel :silly::highfive::laugh:
Wohoo! Made it through the setup, and I have a NavBar! And a working ROM! Super! (Some time later) - It's an awesome smooth driver. Absolutely beautiful.
* TWRP is suddenly showing garbled folders in sdcard. There was a post about that... Lemme see -- Ok so the problem is force_encryption. For that I'd need help, how to change that?
* Computer does not see external sd anymore
* Integrated E-mail app couldn't log to Gmail
* Music player didn't see external SD - fixed by magisk module "ExSdcard Access Enabler".
* Audio Fx didn't change anything - there's a fix to try clearing the data and cache and see if it starts working - I installed Viper4Android FX through Magisk Manager, works.
Click to expand...
Click to collapse
I'm not going to test emergency services.
Moto actions do work-and this is why you don't see a navbar on setup. Fingerprint gestures, swipe right to left to go back,tap for home, left to right for recent, long press for assistant.
Copy partions- this should let you dual boot roms. So los15.1 on slot a and slot b can have Los16. The twrp reboot screen can allow you to choose your boot slot.
Gapps-you can use any gapps really just be sure to flash them if you flash a rom update. I like opengapps arm64 nano builds myself. Then install Google apps from play store.
Twrp- we have to wait for devs to deal with this. It will be fixed in time if it's not fixed with the new official twrp(I haven't tested it yet). It only applies to internal storage. SD card won't be scrambled.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Sent from my Moto G6 Plus using XDA Labs
Xplorer4x4 said:
Moto actions do work-and this is why you don't see a navbar on setup.
SD card-the mount point is wrong. I think it was /run/media/sdcard or something similar. Some apps can find the path and some can't.
Click to expand...
Click to collapse
Great, thanks for clarifying
My post above is written as I go through the setup, therefore a mess.
External SD resides at /mnt/media_rw/(sd_card_name).
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Just to clear up something the reason mavnar isn't shown is you need to use fingerprint gestures. Swipe left to right for recent, tap for home, swipe left to right to go back. Then you can activate navbar in settings after set up.
Sent from my Moto G6 Plus using XDA Labs
weazie said:
Easiest way to fix (most apps) to recognize it is to load ExSdCard Access Enabler module in Magisk Manager.
Click to expand...
Click to collapse
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Alpetrus said:
This method unfortunately doesn't work in Lightroom. "Use SD Card" in "Device Info & Storage" is still grayed out.
Click to expand...
Click to collapse
yes, it seems so. I asked this question in Adobe Support, but didn't get a satisfactory answer.
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
DocFallingApart said:
Is anyone else having a problem enabling the microphone in Gboard? It's not a big issue as I'm able to switch to Google Voice typing on the fly. I was just wondering if it's something I did, or if it is something with this ROM.
For reference I installed Nano Gapps, and Gboard from the store.
Click to expand...
Click to collapse
Have you enabled microphone permissions from settings - apps?

[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]

[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ & J6+ [j4primelte & j6primelte]
{
"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:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
NFC
Fingerprint on J6+
Sim slots
Flashlight
Mobicore keystore
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Download the latest build.
Reboot to recovery
Flash the latest build.
Optional: Flash GApps for Google Services and Magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+/J6+ [j4primelte & j6primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: 1.0
Stable Release Date: 2020-01-29
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-25
Last Updated 2020-01-29
Changelogs :
Stable version 1 - 29/01/2020 :
Now we are building vendor too. Goodbye OneUI vendor.
Happy news to J6+ users: my builds are now supporting j6primelte.
NFC is fixed on NFC variants.
Keystore is now fixed and got rid of aosp's software implementation. You don't need any hacks or tricks to make it work on GSIs.
SIM count detection added, single sim users won't have annoying second sim.
Previous build had dead flashlight sometimes. Fixed.
Removed Samsung's bloatwares.
RIL working delay after boot fixed.
And so much more that I did in past couple of months that I don't remember.
Public Beta 4 - 18/08/2019 :
MTP totally fixed.
Added FM Radio.
NFC should work now on FN users (Current device I have isn't NFC variant. I am not sure).
Public Beta 3 - 27/06/2019 :
Added USB and Bluetooth tethering.
Public Beta 2 - 26/06/2019 :
Lockscreen password fixed.
Audio on camcorder(video recording) fixed.
Autobrightness fixed.
Hotspot fixed.
MTP fixed.
Second SIM Slot fixed.
Public Beta 1 - 25/06/2019 :
First release.
Thanks to abhishek987 for thread template.
Screenshots on attachment.
Note(s) :
Send me logs if you've find any bug.
Reserved for just-in-case.
Please give me credits while building roms and sharing with my sources.
By hitting thanks button and following me on GitHub you can make me happy. Have fun!
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Andhika24kd said:
Wow just wanna say thanks for this. But based on this sentence by you: "If you're on oreo, flash OneUI latest."
Does it mean that we need to upgrade it to Samsung Android Pie first?
Click to expand...
Click to collapse
Yes.
New update released. Enjoy.
ataberkozen said:
New update released. Enjoy.
Click to expand...
Click to collapse
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
rudi021 said:
hi ataberkozen.i must say thank you for this rom.i flash it today and is boot and all work. i have few questions if i may. in your device tree is write that architeture is armv7-a-neon,but when i compile rom then is warning about a53 is armv8-a-neon(not error just warning).,thats ok,i add line for armv8-a-neon and now is ok. then no vendorsetup.sh in device tree.dont be mad is just observation from my side.btw thank you very much for device tree,vendor tree and kernel for this device.:good: btw for people who want flash this device do as: Must be on pie;when flash twrp go to format data,write yes,go to advance wipe and wipe dalvik,cache,system,data;then Flash RMM Bypass and forceencrypt disabler and then flash rom and magisk.reboot.as i hate gapps i dont flash it.once again thanks on rom and other stuff and your hard work.
Click to expand...
Click to collapse
Are you also building a ROM?
Geckyn said:
Are you also building a ROM?
Click to expand...
Click to collapse
yes.i build roms.i build also few gsi for j4+ just for test.but mostly for mtk devices.is my first samsung device.is my hobby. i have 55 years.
ataberkozen said:
Code:
/*
* I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed (like it did for me...).
* Please do some research if you have any concerns about features included in the products you find here before flashing it!
* YOU are choosing to make these modifications, and if you point the finger at me for messing up your device, I will laugh at you.
* Your warranty will be void if you tamper with any part of your device / software.
* Same statement for XDA.
*/
LineageOS is a free, community built, aftermarket firmware distribution of Android 8 (oreo), which is designed to increase performance and reliability over stock Android for your device.
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review.
What's working :
Boots
RIL (Calls, SMS, Data)
Wi-Fi
Bluetooth
Camera
Camcorder
Video Playback
Audio
Sensors
Flash
GPS
Known issues:
VoLTE
Selinux is permissive
Instructions :
If you're on oreo, flash OneUI latest.
Flash RMM Bypass and forceencrypt disabler from TWRP thread.
Download the latest build and GApps
Reboot to recovery
Flash the latest build and GApps
Optional: Flash magisk for root.
Reboot
Downloads :
All updates will be here.
Sources :
Device Tree
Vendor Blobs
Kernel Source
XDA:DevDB Information
[ROM][UNOFFICIAL][9.0] LineageOS 16.0 for Galaxy J4+ [j4primelte], ROM for the Samsung Galaxy J4+
Contributors
ataberkozen
Source Code: https://github.com/lineageos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.x
ROM Firmware Required: Pie, OneUI
Based On: LineageOS
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2019-06-26
Created 2019-06-26
Last Updated 2019-06-25
Click to expand...
Click to collapse
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Necrosis Virus said:
I tried to flash this on my SM-J415GN . It says on TWRP. "Size of image is larger than target device." How do i fix this? Thank you.
edit. I'm just dumb so uh nvm this. Lol
Click to expand...
Click to collapse
Some notes and bugs encountered by me on J415F:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Andhika24kd said:
1) No face unlock option even after flashing GApps. Workaround: use other screen lock method
2) SIM 2 will be named as 'CARD 2' instead of its real name on many occasions. Workaround: Change your SIM 2 name manually from Settings -> Network & internet -> SIM Cards -> SIM slot 2. This may happen because your SIM carrier is unrecognized by Android
3) Samsung Pay and Samsung Max are there. Workaround: Remove the APKs manually using File Manager that supports root feature. They are located inside ./odm/app
4) If Android cant 'sign in to network' on SIM 1. It will display an error referring to SIM 2's name. It will also use mobile data from SIM 2 instead (pic 1, pic 2). No workaround
5) Bluelight filter not working (won't change settings). Workaround: Use 3rd party app to filter it (such as CF.Lumen)
6) Saved screenshot shows a blank preview image (on notification list). No workaround
7) Removing system apps cause bootloop. Workaround: Just disable it or use ADB to uninstall it instead (current user only)
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
9) Download manager is buggy, taking long time or failed to download something (for example Magisk module), or download file with strange name (instead of its real name on Jelly browser). Workaround: Restart the device at least once or use other browser like Chrome or Firefox (Lite)
10) 'Files' app shows an error when renaming file (but it actually works). No workaround
11) Bluetooth keeps stoping when accessed/enabled by apps (example: Google Play Games). No workaround?
12) When setting navigation bar to compact mode (or other mode), the 'change rotation' button (if you don't use auto rotate) will appear behind/on top of/in the middle of other navigation buttons. Workaround: Use the default one or use 'Gesture' navigation bar instead. This may happen if you change your screen 'Display size' (aka DPI) from Settings -> Display
13) Changing navigation bar to lefty/righty may cause the navigation bar to disappear. Workaround: Reboot the device at least once or use the same workaround as above
14) Changing home screen wallpaper will also change lock screen wallpaper and using custom image as wallpaper will cause the default 'Wallpaper' app to crash. Workaround: Use other app to change wallpaper (such as Google Wallpaper app)
15) Lock screen message does not appear, although emergency message/info works fine. Workaround: Change it and save it again (for the second time), if the problem stays reboot the device at least once
16) Keyboard will not appear on some conditions (like when writing app review on Play Store) and cause heavy lag or screen blinking. Workaround: Press home button and kill the 'hanging' app. Install alternative keyboard (such as G-Board or Simple Keyboard)
17) Changing accent color (from Settings -> Display -> Style) will not change 'Trebuchet' launcher accent color. Workaround: Change it to other color and save it again. If the problem persist force stop the launcher or reboot the device
18) 'Trebuchet' launcher is using light theme even after I change the system style color to Dark/AMOLED. Workaround: Change your wallpaper to a darker one
19) Notifications are still on white color even after I change the system style color to Dark/AMOLED. Workaround: Use 3rd party theming app (such as Substratum) or Xposed module or whatever
20) Signal bar is empty on both SIMs but mobile data, SMS, and phone work fine. No workaround?
21) Some apps notifications (like Messaging app) will be delayed or not showing up at all if 'Do no disturb' mode is activated. Workaround: Check it manually, of course
22) Minor UI bugs here and there that doesn't affect anything (maybe also DPI related issue) (pic 1, pic 2, pic 3). No workaround?
Some of this may be features/limitations of AOSP and LineageOS, not actually bugs. Tested on beta 3 release, will always update this post once I found new bugs. Thanks for the ROM by the way. Cheers
Click to expand...
Click to collapse
1-) OpenGApps telegram group aware of this problem, wait for them.
2-) Prepaid doesn't show for me too, but others shows.
3-) I'll disable it later.
4-) Send logs from telegram.
5-) I forgot to add lineage livedisplay while creating tree. I'll add next update.
6-) SkiaGL problematic on sd425, 425 phones are using opengl. I had to choose between fixing lags and other ui problems or working screenshot. I choose first one.
7-) You said yourself, removing system apps causes bootloop.
I'll fix it later.
9-) IDK is it problem or not but i am pretty sure isn't bcz of me.
10-) Same 9.
11-) I didn't faced problem while sending mp3, but if u you can send logs i'll check.
12-) Not my problem.
13-) Not bcz of me.
14-) I didn't faced but it's app bug really not my problem.
15-) Not my problem 2.
16-) You said yourself install gboard.
17-) Accent colors is overlay based. Bug isn't from my side.
1 App feature missing or buggy. Idk java I cannot fix.
19-) It's not problem by me, even official devices same.
20-) I am aware of this problem. I need to find a way to change it to rssi.
21-) Isn't this point of DND ? I am busy don't send me any notifications ?
22-) Set ro.lcd.density to 280 with build.prop editor and report back.
Sorry I'm quiet busy nowadays (and I'm sure you are). I will upload the log (you mean logcat, right?) when I have time. Yeah, some of these bugs are actually features on AOSP/LineageOS, I'm just informing other users in case it's their first time switching from Samsung ROM to LineageOS or AOSP based ROM.
11) I didn't use the Bluetooth directly, Google Play Games used it to find a match with nearby player on the game "Bowmasters", will send logcat later.
16) Installing Gboard doesn't help, I already tried that 3-4 days ago.
19) Yes, I'm just informing the others in case they never tried LineageOS/AOSP before. However some unofficial LineageOS have that. Of course I'm not asking you to make/merge it, I don't care about themes.
22) Setting it to 280 doesn't help so far, but I think I need more time to see if it works or not.
Andhika24kd said:
8) MTP/PTP still not working, will show an error when copying files. Workaround: Use 3rd party file sharing apps like ShareIt or AirMore
Click to expand...
Click to collapse
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
breversa said:
This is a real show-stopper.
@ataberkozen :
When you hopefully fix this soon, will I be able to simply flash your new ROM version on top of the current one, or will I have to clean flash the phone first ?
Click to expand...
Click to collapse
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
ataberkozen said:
I fixed it yesterday, a new update expected today. Yes you can flash dirty.
Click to expand...
Click to collapse
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
breversa said:
Awesome work, @ataberkozen ! I can't wait !
---------- Post added at 13:20 ---------- Previous post was at 12:37 ----------
Now that's weird… I installed lineage-16.0-20190627-UNOFFICIAL-j4primelte while waiting for your new build, but MTP works without problem… I'm confused ! ^^
However, I can't connect to any hidden wifi. Seems to be an Android 9 issue though, as I encountered the same issue earlier today with another Android 9 ROM*: https://forum.xda-developers.com/showpost.php?p=79888858&postcount=10
Click to expand...
Click to collapse
MTP fails while copying from phone to pc.

[ROM][UNOFFICIAL][12] LineageOS 19 for Xperia X Compact [FINAL]

{
"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:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About LineageOS
LineageOS is a free, community built, aftermarket firmware distribution of Android 12, which is designed to increase performance and reliability over stock Android for your device.​​LineageOS is based on the Android Open Source Project, with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.​​All the source code for LineageOS is available in the LineageOS GitHub organization.​And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.​You can also view the changelog for a full list of changes & features.​​Official LineageOS website : http://lineageos.org​About LineageOS Legal : http://lineageos.org/legal​
Important Information
1. This ROM operates without ODM images, just follow the installation instructions.​2. This ROM does not intended to support Google Camera, but you can try some mods.​​Downloads Links
LineageOS 19:​Unofficial: https://sourceforge.net/projects/loire-development/files/lineageos-19.1/kugo​​Google Applications (optional):​MindTheGapps: https://androidfilehost.com/?w=files&flid=322935 (Android 12.1 -> arm64)​XDA post about GApps: https://xda-developers.com/download-google-apps-gapps​​Recommended Recovery (optional):​TWRP 3.x: https://forum.xda-developers.com/-/-t3793837​
Flashing and updating
Please install the latest version of TWRP to avoid further issues with recovery!​
LineageOS clean install:​
Download the latest build of LineageOS ROM
Full wipe and factory reset (recommended / backup to make sure not to loose data)
Flash the LineageOS ROM zip from the Recovery
Flash the GApps to have the Google Applications (optional)
Every additional zip you want to flash (optional)
Reboot
LineageOS update/upgrade:​
Download the latest build of LineageOS ROM
Wipe cache and dalvik cache
Flash the latest LineageOS ROM zip from the Recovery
Every additional zip you want to flash (optional)
Reboot
You can also update using the built-in Updater (requires at least TWRP 3.6.x or LineageOS Recovery)​
About the builds:
Kernel sources: https://github.com/Chippa-a/android_kernel_sony_msm8956​
Issues and reports
Report issues only if you are using the ROM kernel
If an additional mod is installed, make sure it's unrelated, and mention it
Make sure the issue wasn't discussed earlier in the threads
Grab a logcat right after the problem has occurred
(Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing)
If it is a random reboot, grab /sys/fs/pstore/console-ramoops and /sys/fs/pstore/dmesg-ramoops-0
(Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Also thanks to:
The LineageOS Team
The SODP Team
Everyone involved in working and testing
Contributors
Chippa_a
ROM OS Version: 12.x
ROM Kernel: Linux 4.9.x
Version Information
Status: Stable
FEATURES AND ISSUES
Boot: Ok
Bluetooth: Ok
WiFi: Ok
WiFi Hotspot: Ok
RIL - Phone - Data: Ok
GPS: Ok
Camera: Ok
Camcorder: Ok
Lights: Ok
MicroSD: Ok
Accelerometer: Ok
Compass: Ok
Gyroscope: Ok
QTI sensors: Ok
Touchscreen: Ok
FM Radio: N/A
Fingerprint: Ok
Vibrator: Ok
Microphone: Ok
Audio & music: Ok
Bluetooth audio: Ok
NFC: Unknown (HCE: Unknown)
Kernel: Ok
Graphics: Ok
3D Rendering: Ok
Clock: Ok
DRM: Unknown
Offline Charging: Ok
USB: Ok
USB Tethering: Ok
USB OTG: Ok
Encryption: Ok
SEPolicies: Enforcing
what the ...!?
i downloaded los18 just yesterday, installed it this morning and now i see los19 sneaked by
thank you so much chippa_a, i will try it out tomorrow
unbelievable what your doing to this oldschool device.
Gcam works perfectly on it. Thanks a lot for this device!!!
This works beautifully and is really smooth. Never thought I'd see another rom for the XC again.
Can confirm that GCam 8.x with HDR actually works! (No crashes, or stuttering) Unlike previous roms with the most recent kernel before this new one. I don't know what magic you pulled to make this happen but thank you!
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
decsimon said:
Thanks for this rom! It is very fast.... Only Chrome browser is laggy...
Click to expand...
Click to collapse
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
konstruktor said:
I haven't experienced this. For me normal browsing was pretty smooth.
Have you also flashed the kernel from the .zip?
I must say that for now everything seems to work fine for me (incl. Gapps).
Tested fingerprint reader, 4G, DRM with Tidal, smooth and responsive Maps / Android Auto, smooth Chrome. No sudden reboot for now.
Click to expand...
Click to collapse
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
decsimon said:
Ok, what steps for flash kernel i must to follow? Rom, gapps, kernel? Magisk is a problem or i can flash it? (i need it for apk bank)
Click to expand...
Click to collapse
You won't need to flash the kernel separately, it's included in the zip:
1. Boot to TWRP.
2. Install the Lineage zip file.
3. Reboot to recovery.
4. Optional: In TWRP, install/flash Magisk 24.1 and/or MindThe GApps.
That's it. No issues with Chrome lag either. I've tried a few browsers and they all work well.
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
how if i try nfc on ex japan S0-02 j ?
Little adventure said:
how if i try nfc on ex japan S0-02 j ?
Click to expand...
Click to collapse
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
betacrypt said:
I've tested a few GCams, I find these two work best so far:
Parrot043: MGC_7.6.008_Parrot043_V7.apk
Download MGC_7.6.008_Parrot043_V7.apk by Parrot043.
www.celsoazevedo.com
Parrot043: PMGC_7.2.014_Relesed_V1.apk
Download PMGC_7.2.014_Relesed_V1.apk by Parrot043.
www.celsoazevedo.com
In the Advanced Settings, make sure to change AI White Balance to "Pixel 3 XL" for best colour accuracy.
Note: For the front selfie cam to work, you'll need to disable HDR first.
Please post here if you find any other good ones!
Click to expand...
Click to collapse
First , thanks for this Rom I'm very happy to See Android 12 on my phone.
I have tried Encryption and it doesn't work for me. I have a bootloop.
Has anyone else tested it?
And on the Encrypt page , I had astrange bug : I wasn't able to access to the"Encrypt" button at the bottom of the page . I had to set the police size at the smallest size to see it.
Maciek602 said:
It works great! Very fast boot time. Everything is smooth, so far haven't noticed any bugs. Fingerprint unlock is faster than on stock and LOS 16.
Camera quality with the first GCam is also the best out of all custom ROMs I've tested. Great job! A new life for my old Xperia.
Click to expand...
Click to collapse
Agree, fingerprint detection and unlocking is incredibly fast, didn't think it could ever be improved this much.
betacrypt said:
Not sure what you're asking but NFC is located under:
Settings > Connected Devices > Connection Preferences > NFC
If it doesn't turn on, you might have to flash the last Sony stock firmware first then install this rom.
Someone with the JA model might be able to help.
Click to expand...
Click to collapse
thanks for the answer sir
I have ex japan status bootloader yes, now position in custom rom lineage 16.0 android pie, this rom very smooth in my old device , i try turn on nfc in this rom, nfc doesnt turn on , but nfc working fine in ex global
Maybe hardware nfc ex japan different with ex global , so that maybe build tree and config specific for ex japan , correct me if i wrong sir
my experience with gapps 12.1 12L
open gapps stock - not working (endless bootanimation)
open gapps pico - unusable (loop before setting up fingerprint)
flame gapps full - unusable (loop before setting up fingerprint)
flame gapps basic - unusable (loop before setting up fingerprint)
mindthegapps - working
nik gapps omni - working
nik gapps stock - working fine so far
I have this problem...my bank apk its OK with last magisk (and fingerprints setting and Hide zygisk), but gpay dont work when i insert my card code cvv, it say that is not possibile continue because possible root phone....i try to hide all with zygisk of magisk .....
OK i resolved with module safetynet....
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
decsimon said:
Toggles for me is too big, ....is possible return to standard lineageos toggles 16/17/18?
So when swipe down one time, i can see 6 toggles and not only 4....
Click to expand...
Click to collapse
That's Android 12. I wouldn't hold my breath that someone could port an older System UI over. You would have to get used to it I'm afraid.

Categories

Resources