{
"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"
}
Evolution X 7.5 for Pixel 6a [bluejay]
Code:
/*
* Your warranty is void. Or valId, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/
Pixel 6a (bluejay) is now official supported device. →New thread
Spoiler: Changelogs
20230122
- Fixed up Adaptive Charging errors
- SELinux enforcing now
20230121
- Updated to Evolution X 7.5 Menudo
- January 2023 security patch
- Fixed up camera & fingerprint.
- SafetyNet now pass
20221226
- Updated to Evolution X 7.4 Kaldereta
- December security patch
- Evolution X replaced Pixel Launcher to own launcher, because battery drain too much
- Added Pallarel Space features
*This update needs clean flash, so please backup your data before flashing.
20221130
- Fixed Unlimited Google Photos storage
- Fixed SafetyNet
* Still working on fix Camera & Flashlight, please wait patient!
20221125
- Fixed neuralnetworks. Now you can update Android System Intelligence.
- Recent tasks screen Text Selection now works!
*Camera and Flashlight not working, we working to fix it.
20221119
- Fixed Google Camera crashing, but you cannot use normal shot (Night Sight is worked)
20221117b
- Enabled Adaptive Charging
- Removed broken Google Camera and Adaptive Connectivity in preinstalled apps
- Screen tappable Evolution X recovery
20221117
- November security patch
- Fixed Night Light
- Enabled Now Playing
- Enabled Text Selection on recent tasks screen
20221110
- Enabled RCS
- VoLTE are enabled by default
- Builds are moved to my sourceforge
20221107
- Added missing important proprietary blobs. fixed sim card bootloops.
* Now you're safe to insert SIM cards.
- Felica is now worked properly
20221103
- initial build
Spoiler: Screenshots
Features
Pure android UI and experience
Includes Google Pixel original features (Now Playing, Adaptive Sound, Adaptive Charging, Call Screening supported)
More customizing tools, "The Evolver" menus
System are not rooted, but you can be the superuser in adb shell.
Unlimited Google Photos storage, in original quality
Magic Eraser worked (To use, please turn off Unlimited Google Photos storage in Evolver menu)
Known Issues
you tell me
Download linksBoot and Recovery Images
OTA zips
(mirror: my GDrive)
How to flash?*This operation can make brick your device, so I recommend backup your data before flashing.
*Don't flash gapps, they're included!
First, make sure your device bootloader unlocked and if you're on another rom, I recommend revert back to stock rom before flashing.
Download it Boot and Recovery Images (boot.img, vendor_boot.img, installer.sh) and Latest OTA zip from my SourceForge, place it same directory.
Then simply run installer.sh to starts automatically flashing.
Also you can flash it manually following steps.
Power off, Hold the volume down button and turn on the power. your device will enterning bootloader mode.
Flash boot.img and vendor_boot.img via your terminal: "fastboot flash boot boot.img" and
"fastboot flash vendor_boot vendor_boot.img"
Use volume button, select "Recovery Mode" and press power button to confirm.
Then you will see Evolution X recovery. You can tap screen to select, or also use volume keys to move cursor and power keys confirm. *If you're already on my Evolution X, you can skip next steps.
If you're came from stock or another rom, you must wipe data. select "Factory reset" then "Format data/factory reset", and "Format data" to confirm. After data wipe complete, select left arrow icon to back to the main menu.
Select "Apply update" , then "Apply from ADB". your device will standby sideload mode.
Now, sideload the zip file via terminal: "adb sideload evolution_bluejay-ota-td1a.xxxxxx.xxx-XXXXXXXX-unofficial-unsigned.zip" (xx are some numbers)
After sideload success, you will see "Total xfer: 1.00x" in your terminal.
Back to the main menu, select "Reboot system now" and press power button to reboot.
Now you're taste Tiramisu. Enjoy! *If your device won't working properly, reboot to recovery then try sideload a previous build.
ROM Maintainer: nattolecats
ROM Source: https://github.com/Evolution-X
Device tree of bluejay: https://github.com/nattolecats/device_google_bluejay
Device tree of gs101: https://github.com/nattolecats/device_google_gs101
Vendor tree: https://gitlab.com/the-muppets/proprietary_vendor_google_bluejay/-/tree/lineage-20
Kernel Source: https://github.com/CalyxOS/device_google_bluejay-kernel
ROM OS Version: Android 13
To contact me: t.me/nattolecats
Thanks sir. I'm going ti flash it asap
angelmakumbe said:
Thanks sir. I'm going ti flash it asap
Click to expand...
Click to collapse
Thanks to use my rom. Enjoy Tramisu!
nattolecats said:
Thanks to use my rom. Enjoy Tramisu!
Click to expand...
Click to collapse
Good work. Only miss " now playing" and "magic eraser" even disabling unlimited storage and mencionated ROM bugs. Thanks and go on, please
angelmakumbe said:
Good work. Only miss " now playing" and "magic eraser" even disabling unlimited storage and mencionated ROM bugs. Thanks and go on, please
Click to expand...
Click to collapse
I see. Thanks for the feedback. I will maybe include it in the build sometime soon.
Update 20221107
- Added missing carrier settings. will don't appears "Adaptive Connect keep stopping" message but still have bootloop.
Any solutions for weird bootloops?
There's not caused by Carrier Settings.... hmm I'm stuck
I'm not recommended use sim cards there's still buggy
Update 20221107 (re-building)
- Added missing inportant proprietary blobs. fixed sim card bootloops.
* Now you're safe to insert SIM cards.
- Felica is now worked properly
FINALLY BOOTLOOP BUG IS FIXED!
you can insert sim cards then carrying device outside now.
We apologize for any inconvenience caused.
Enjoy Tiramisu!
Wait a minute about "Now Playing" and "Magic Eraser" features!
I'm looking for a way to enable them.
nattolecats said:
Update 20221107 (re-building)
- Added missing inportant proprietary blobs. fixed sim card bootloops.
* Now you're safe to insert SIM cards.
- Felica is now worked properly
FINALLY BOOTLOOP BUG IS FIXED!
you can insert sim cards then carrying device outside now.
We apologize for any inconvenience caused.
Enjoy Tiramisu!
Wait a minute about "Now Playing" and "Magic Eraser" features!
I'm looking for a
Click to expand...
Click to collapse
I don't understand how this ispossible, but fps seems to be better then stock. That's surprising.i'm gonna keep this rom for a couple days and reportback any issues if any pop up
Twilightsparklez said:
I don't understand how this ispossible, but fps seems to be better then stock. That's surprising.i'm gonna keep this rom for a couple days and reportback any issues if any pop up
Click to expand...
Click to collapse
That would be helpful. The current build seems to be the most stable. Enjoy.
First of all thanks
nattolecatsKeep your good work !
Ps * i would be interested to pay for the pixel camera app to work
Val.sexy09xx said:
First of all thanks
nattolecatsKeep your good work !
Ps * i would be interested to pay for the pixel camera app to work
Click to expand...
Click to collapse
Thank you very much. You can send me PayPal. My email is: [email protected]
Nice only issue I noticed is 5g won't auto connect from wifi to data like it goes to EDGE but switching to LTE Solves that. and Bluetooth disconnects sometimes
Santarosa 503 said:
Nice only issue I noticed is 5g won't auto connect from wifi to data like it goes to EDGE but switching to LTE Solves that. and Bluetooth disconnects sometimes
Click to expand...
Click to collapse
I wonder if tthe adaptive connectivity popup has anything to do with those bugs
Santarosa 503 said:
Nice only issue I noticed is 5g won't auto connect from wifi to data like it goes to EDGE but switching to LTE Solves that. and Bluetooth disconnects sometimes
Click to expand...
Click to collapse
I could not reproduce the same situation in my environment. I'il try to going fix in a future update, but at the moment I don't know how to fix it. That's takes many time.
Twilightsparklez said:
I wonder if tthe adaptive connectivity popup has anything to do with those bugs
Click to expand...
Click to collapse
Yes, I think so. I'm working to fix these bugs.
Update 20221110
- Enabled RCS
- VoLTE are enabled by default
- Builds are moved to my sourceforge
Bugs: Currently, AiAi (a Pixel-exclusive feature) doesn't seem to work at all. Suggestions in Pixel Launcher and Adaptive Sound in Settings exist but cannot be used. I tried to enable other settings such as Screen Attention and Now Playing, but I couldn't enable them. Please revert to stock rom to use these features. Also, I've been using Google Photos for a while on this rom, and the unlimited photo storage feature isn't working either, it seem to count against storage. (It's weird that's displayed in the photo app but not working.)
I'm sorry to this is my limit to development, it's stuck.
Please tell me any useful information.
Anyone had success using this ROM with Google Fi? I haven't been able to get it working
Flashed 11-10 and it's going well - google camera is jacked so I'm using Open Camera, everything else seems good so far.
Noice thank you so much for your efforts
No worries - going to run it through the paces over the next couple days and will report back.
Here is a link to some logs that ive collected when the camera wasnt fully working and also maybe some other info to solve the other bugs. https://drive.google.com/file/d/1YQqngBMNYewevRufWb7eIxqjUwErhQ77/view?usp=share_link
The main part that keeps on repeating is this which i believe that this module is missing.
Little background on this camera issue. This is the camera app that is available to download and was trying to use the ultra wide camera.
11-10 18:11:26.121 3890 8268 W HidlServiceManagement: Waited one second for [email protected]::IDevice/google-armnn
11-10 18:11:26.121 443 443 I hwservicemanager: Since [email protected]::IDevice/google-armnn is not registered, trying to start it as a lazy HAL.
11-10 18:11:26.123 3890 8268 I HidlServiceManagement: getService: Trying again for [email protected]::IDevice/google-armnn...
NOTE: for those who would like to help polish the rom up you can get the logs by doing: adb logcat > logs.txt while the issue is happing
I believe you need to add the following. Also there may be more things that it wants but you got to build that before you get the next set of info.
sm6150-common: hidl: Add android.hardware.neuralnetworks to fcm · PixelOS-Devices/[email protected]
* The following HALs in device manifest are not declared in FCM <= level 4: [email protected]::IDevice/qti-default [email protected]::IDevice/qti-dsp android...
github.com
Related
{
"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"
}
Unofficial OmniROM OREO for Z3C (aries)Brought to you by @nailykKnow someone with a Z3? Send them over to this threadClassic disclaimer:
Code:
/*
* 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 me for messing up your device, I will laugh at you.
*
*/
Features:
OTA Updates:
We've activated OTA updates, so you can be sure to get the latest updates for your device!
Unique, customizable features with OmniGears:
Control the brightness by swiping across status bar!
Set your own actions for hard- and software buttons!
Change the style of your device, thanks to substratum support! (dark theme already included)
Crop your screenshot right after you took one!
...and much more!
Switch your apps with OmniSwitch
Forget the recents drawer, you can switch your apps by swiping from the edge of the screen!
Customizable, with cool extra features!
And of course completely OPTIONAL! Switch it on the go without restarting your device!
...
Prerequisites:
Sony Z3 Compact (aries)
UNLOCKED Bootloader
Latest TWRP release
Install guide:
Still on stock fw?:
Make sure you're on 23.5.A.1.291, if not, download and flash it with Flashtool.
Flash the latest TWRP (3.1.xx) in fastboot (fastboot flash FOTAKernel twrp_***.img)
When you're done, follow the next points below this spoiler.
Enter recovery mode (HOLD VOL DOWN + POWER while device is off)
WIPE /system, /data, /cache, dalvik cache
SELECT the ROM zip and flash it
(Optional) Flash GApps: (http://opengapps.org/)
(Optional) Flash any other extras (root: look below the guide)
Reboot into system and wait for boot (it'll take some time, don't worry)
Root:
For root, we suggest that you use phhSuperUser, as it is fully open sourced and it works fine with OmniROM: phhSuperUser thread
Alternatives are Magisk (Click here) and SuperSU.
Downloads:
Latest build:
Read post #2 to check what bugs are currently on the latest build!
2018-06-16:
Direct: https://releases.nailyk.fr/omnirom/omni-8.1.0-20180616-z3c-nailyk.zip
Changelog at post#2
Previous builds:
2018-03-20:omni-8.1.0-20180320-z3c-nailyk.zip
2018-01-01:omni-8.1.0-20180101-z3c-nailyk.zip
2017-11-03: omni-8.0.0-20171103-z3c-nailyk.zip
2017-11-01: omni-8.0.0-20171101-z3c-nailyk.zip
2017-10-29: omni-8.0.0-20171029-z3c-nailyk.zip
TWRP:
https://releases.nailyk.fr/twrp/twrp_z3c_O_2018-06-16.img
Want to report bugs?
Give us logs using dmesg or logcat (clear logs first before reproducing the problem with "adb logcat -c")
Rebooting problems? Provide last_kmsg
Written explanations only with a way to reproduce the bug
XDA:DevDB Information
OmniROM, ROM for the Sony Xperia Z3 Compact
Contributors
devil188, nailyk, Dobsgw
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.x
Version Information
Status: Beta
Created 2017-10-29
Last Updated 2018-03-27
Changelog:
2018-06-16 release:
REQUIRES A FULL WIPE!
TWRP dirty fix for zip flashing.
Attempt to fix camera record (not working!)
Solve reboot to recovery
Periodicals updates
Switching to enforce mode (selinunx)
Click to expand...
Click to collapse
2018-03-20 release:
Partial Changelog
Lot of audio changes,
Video record fixed (some problems remain, like format, green bar, etc),
Some not-fully-tested power patches.
Click to expand...
Click to collapse
2018-01-01 release:
Lot of code cleaning,
some fixes about audio, & gps.
New issue about 4G connection: you need to connect to a wifi network before it became available (if you do not have nearly trusted wifi, turning on AP works too. )
Click to expand...
Click to collapse
2017-12-07 release:
Lot of change for camera (video record still broken)
Lot of sepolicy changes (next release will be enforcing so please report your denials logs)
Change for GPS. Should work but expect problems anyway.
SystemUI tuner should be working again.
Small change to make external sd mountable while using unix file-system. Still not able to write on it for now.
Click to expand...
Click to collapse
2017-11-03 release:
Multiple merges:
2017-10-31:
OTA updates
2017-11-03:
Fix video recording (26562)
Fix aries bootanim size (26515)
Click to expand...
Click to collapse
2017-11-01 release:
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
Click to expand...
Click to collapse
Currently known issues and their fixes:
ERROR 7 while flashing in TWRP
- Flash the correct TWRP or delete the getprop() in updater-script.
Video recording not working
- Now partially working, some bugs may occur!
Problems with MicroG
- https://forum.xda-developers.com/showpost.php?p=74341878&postcount=9
5GHz Wi-Fi networks not working
- There are reports that 5GHz Wi-Fi networks not getting detected, we can't reproduce this problem though. Currently looking into this.
Sources:
https://github.com/nailyk-fr/local_manifests/blob/android-8.0/x-roomservice.xml
https://github.com/omnirom
https://gerrit.omnirom.org/
How to report
How to post
Reports without logs or step to reproduce are useless (read contribute).
You are welcome to post your review: what is working, not working, etc... Check into know issues before.
You are welcome to report any typo, error, etc...
Try to keep thread clean as a dev reference. Thanks in advance.
How to report problems
To report problem, please provide logs.
It is always better to include reference to the Installed version. This guide is really detailed and explained everything about bug reports.
If you have any doubts, take the most logs. There is never enough logs
How to get logs
If your device is not booting at all, we need information about how you flash and all the handling you do, the display status, light status, and if available a dump of /proc/last_kmesg*
If you have a non working peripheral (non-working radio/wifi/etc...) please provide a full logcat and full dmesg, example:
Code:
adb reboot
adb wait-for-device
adb shell dmesg > dmesg.log
adb logcat -d > logcat.log
If you have a non working app please provide a partial logcat:
Code:
adb reboot
adb wait-for-device
adb logcat -c
<launch your app>
adb logcat -d > logcat.log
On this rom, there is a script who detect device at install time and provide the right functions for single or dual sim. If you have modem problems (like data not working or no signal) please also provide the /tmp/recovery.log.:
If you have ADB access to your device in twrp just use
Code:
adb pull /tmp/recovery.log .
after flashing omnirom.
If you do not have ADB access use the 'copy to SD' button in the advanced tab, then transfer it the way you like.
then upload your files to a service like pastebin.com / paste.omnirom.org
How to contribute
Code is like hieroglyphs for me:
No worries you can contribute anyway! Install the rom, do tests, read failure logs, look at internet for potential fix/similar users experience, is the biggest part of debugging. Then collect all of this and write your results here.
Code is like hieroglyphs for me and logs are worst:
No problem, collects logs the right way if you can, explain how you encounter the problem: detailed step to reproduce could be enough: explain exactly how you encounter the error/problem, it should produce each time someone repeat your steps. Then we will be able to fix it.
Based on stock sony kernel?
Amazing, I'm testing right now.
-It's quite fast (maybe a bit laggy in Settings app)
-Calls/SMS ok
-Wi-Fi working (both 2.4 and 5 GHz)
-Camera taking pictures, but not videos (as stated in post #2)
-Mobile data working (2G, 3G, LTE)
-Bluetooth working! I successfully connected to my JBL Go
-DoubleTapToWake not working
-Auto brightness not working here, good Night Mode
-Audio is quite loud, very good! (good inCall and loudspeaker volumes too)
-Screen rotation working
-64GB microSD correctly detected
-only around 5.5 GB occupied (without gApps)
-just 23 seconds to boot
-30 minutes of SOT drained about 7% of battery
I'm really tempted to keep this ROM, but I'll wait for it to get even more stable than now.
Oreo seems a way better than Nougat.
Thanks dev for this :good::good::good:
When video recording gets fixed I am installing this ROM,I already see good reviews so hoping it gets fixed soon.
Great job dev!
Awesome work guys, bluetooth works.
Hope we got Lineage or AOSP ROM soon.
Testing,so far so good.
So far so good... What I've noted:
- 'unknown sources' option in security settings is done away with. Now is a pop-up dialog included in pkg mgr.
- Settings layout is different. Main dashboard more condensed, with several options now in sub-settings.
- Signature spoofing ability included without patch, but Micro G still showing not active. Not sure what to do to activate it. SELinux already permissive; I don't see any option in settings...
- phh's Superuser working fine, (my preferred root).
Thanks
---------- Post added at 08:24 PM ---------- Previous post was at 07:55 PM ----------
Figured out the Micro G issue, (feel stupid because I already went through this with another ROM and forgot about it...) Just tap on the unchecked box in Micro G settings and allow permission in the pop-up box.
Now Micro G working fine...
Very Good!
Please add control with one hand as on LOS, my top of the sensor does not work.
Awesome work guys, thanks for all the hard work @devil188 @nailyk @Diewi @xkeita @rcstar6696
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
Awesome work guys, thanks for all the hard work @devil188 @nailyk @Diewi @xkeita @rcstar6696
Already approx 24h on. I am really pleased surprise, she isn't perfect but come on!! ,is Alfa release, and come so early after officially released!
Normally installed, on get gaps I have same treble, usually use aroma install, but don't past a way,finely successful with pico, magisk , and now I am a happy campers.
Tks a loot for this!
Stock camera working, no recording.(just flash)
I guess they cut button rearrangement out of system ui tuner in Oreo. Found this app that can restore it - https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner. I have a feeling it's easy to do with apktool also, but apktool not ready for O yet, so haven't been able to test, (https://forum.xda-developers.com/showpost.php?p=74347058&postcount=5108)...
Tried the rom. Many congrats for the good work and thank you.
I cannot get the 5ghz networks to show up.
Also double tap to wake does not work.
And, the camera, even if does not FC when taking video, it does not store it anywhere.
Finally I get an error message as soon as the phone boots up to android. "Cell broadcast has stopped".
I will be following closely this thread. Keep up the good work!!!
I flashed again this rom to check if "Nougat Sony Camera Port" could work on Oreo too (I cannot live without that camera).
The result is YES (obviously Video recording still broken and some camera mode like AR Fun are force closing) and Cyberian Camera 8.0 works too.
So proud of this phone, it does not want to give up :good:
madvinegar said:
Tried the rom. Many congrats for the good work and thank you.
I cannot get the 5ghz networks to show up.
Also double tap to wake does not work.
And, the camera, even if does not FC when taking video, it does not store it anywhere.
Finally I get an error message as soon as the phone boots up to android. "Cell broadcast has stopped".
I will be following closely this thread. Keep up the good work!!!
Click to expand...
Click to collapse
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
devil188 said:
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
Click to expand...
Click to collapse
Apologies for the noob question. How can I take a logcat?
devil188 said:
5GHz networks are showing up for me, double tap to wake works too. And that's what we meant with "video recording not working"
If possible, give us a logcat so we can take a look at that problem of yours.
Click to expand...
Click to collapse
5Ghz working for me too, but not DT2W.
I've seen a new build on androidfilehost (too late ), has it been fixed in that build?
2017-11-01 release
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
And a surprise coming.
Link will be added to OP in a few.
nailyk said:
Minor fixes:
Restore D2TW from 26502 & 26504
Attempt to fix AP with 26524
Enable Messaging app (26526) & FM app (26527)
And a surprise coming.
Link will be added to OP in a few.
Click to expand...
Click to collapse
You mean right now
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
{
"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?
{
"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"
}
This is an UNOFFICIAL build.of LineageOS 18.1 based on Android 11 for the OnePlus 7T Pro 5G Mclaren. Some LOS specific features haven't been re-imported yet so, just be aware. I did NOT create this ROM, it is an Open Source project by the community for the community and has many many contributors , some from this very thread!. thanks to all who have contributed to CyanogenMod/LineageOS over the years.
Supported device: OnePlus 7T Pro 5G McLaren (hotdogg)
Click to expand...
Click to collapse
Code:
[B]IMPORTANT[/B]
* Builds are done when they are done, and not a second sooner. Please no build begging.
* Do NOT be rude.
* If you don't get a reply from me in a timely manner about your bug, sorry i do this in my spare time
* Respect all users
* If I see a NOOB question and I don't feel like replying, I WONT.
Built from latest LineageOS/Android 11 source
Service
Text
Data
Call
VoLTE/WiFI Calling/IMS/5G]
Audio
WiFi
Google Now
Bluetooth
GPS
MMS
Video playback
Audio playback
Camera
Video recording
NFC
Standalone 5G
??? You tell me
Unlock Warning:
By unlocking a OnePlus phone, you can loose permanent functionality in fingerprint scanner and OTAs for Stock ROMS if improper steps are taken.
Please see 2rd post for backup instructions BEFORE flashing this or ANY custom ROMs
Join our Telegram Chat for added support
PAY ATTENTION!! DIFFERENT THEN MOST DEVICES! CURRENTLY TWRP DOESNT SUPPORT OUR DEVICE SO FASTBOOT MUST BE USED INSTEAD! GAPPS IS ALSO INCLUDED IN THE BUILD DUE TO SAME LACK OF TWRP!
(if you are comfortable with fastboot just run the following commands from fastbootd, if you are unsure of the procedure please read on IT IS DIFFERENT THEN TWRP!
Code:
(boot to bootloader)
fastboot reboot fastboot
fastboot -w
fastboot update lineage-18.0-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Boot to bootloader
from terminal/command prompt: fastboot reboot fastboot
(Don't forget the above step! This will bring us into fastbootd mode. Regular bootloader/fastboot doesn't have access to all needed partitions for flashing. You will see 'partition not found' errors)
Note: In order to access fastbootd mode, we must have stock recovery flashed until TWRP is fixed
if you are coming from a different rom wipe userdata by typing fastboot -w
now type fastboot update filename.zip where filename is the name of the downloaded zip. (e.g, lineage-18.0-20200723-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip)
Any and all users in this thread who contributed or will contribute to making this ROM as stable as possible
LineageOS Devs
@mjevange
@omariscal1019
@OC'D
Me
Not expected by any means but always brings a smile to my face when I see it, If anyone wants to Paypal me a couple bucks my way it would really help cuver all the coffee and smokes i go through debugging stuff haha
Thanks and happy flashing!
[*] See Post 3
[*] See Post 3
XDA:DevDB Information
LineageOS 18.0 | Android 11 for OnePlus 7T Pro McLaren (hotdogg), ROM for the OnePlus 7T Pro McLaren
Contributors
albinoman887
Source Code: http://github.com/Team-Hydra
ROM OS Version: Android 11
ROM Firmware Required: Must be on 10.0.39 Modem or higher for full support
Based On: LineageOS
Reserved
Unlock Warning:
- This matters only if you ever want to revert to OnePlus ROMs or a fully stock phone
- Choose a method below to get backups BEFORE unlocking to prevent this
- persist.img and reserve.img are most important, but get full dump/backup to be safe
- If you need help, join our Telegram Chat
Getting your phone into EDL mode
Code:
- While holding {Vol+} & {Vol-}, insert USB
- Your screen will remain blank, you will immediately be in EDL mode
- You will have 10 seconds to interact with EDL mode, or the phone will restart into Charging mode
- If an EDL mode interaction fails, you will need to first reboot into fastboot by holding {Vol+} & {Vol-} & {Power} for 10 seconds
MSM Readback (Windows Only)
Download Tool
Grab any MSM Tool version
Obtain Backup
- Launch tool
- Select Target 'TMO'
- Press F8 (password is 'oneplus')
- Select Partitions & Hit OK
(persist.img and reserve.img are very important, but can't hurt to have a copy of everything, use Ctrl-A to select all)
- Put phone in EDL mode (SEE NOTE)
- Enumerate device
- Click Readback & Wait
EDL Tool Backup (Linux Only)
Obtain the tool
Use GIT:
Code:
~$ git clone [email protected]:bkerler/edl.git
—or—
Download ZIP: https://github.com/bkerler/edl/archive/master.zip
Prep
Use the included README for required packages / setup
Pay attention to UDEV rules, python, and pip
Backup
In the edl folder:
- Create folder named dumps
- Put phone in EDL mode (SEE NOTE)
- Use edl.py:
Code:
~$ ./edl.py rl dumps/ --memory=ufs --genxml --skip=userdata
Mar 3
* Major Release, do a full wipe if you have problems. I actually STRONGLY recommend a full wipe anyways.
* For all intents and purposes this is a Stable release. I've done extensive testing and everything has worked as it should or above and beyond. Now on to the updates
* A lot of just under the hood optimization and cleanup. There some configuration options that weren't exactly optimized for our device, dalvik config is a good example.
* 5G support is on par with stock ROM, if not better.
* Auto brightness has been improved
* Some cosmetic issues have been addressed like status bar padding and FOD icon centering.
* Fixed a wakelock issue when using Always on Display
* Adjustable display refresh rate code has been improved.
* Updated vendor libs from hotdog Android R OB2 to allow full use of Android 11 Display HAL
* Added Stereo in call recording support
* Various audio fixups, including increasing volume steps from 7 to 15 and raising the max volume level to be on par with stock OOS
* Optimized Always on Display: fixed wakelock issue, lowed default AOD brightness, as well as enabled auto brightness when on AOD if enabled by user within settings
* Many upstream changes, fixes, and improvments.
** This will most likely be my final release as i have moved on to the Snapdragon variant of the Note 20 Ultra 5G. Thanks for the support guys and I hope you enjoy my work. Hopefully someone will pick up where I left off.
Dec 26
* Merry Christmas!
* Updated ROM base to lineage-18.1
* Notification pull-down menu now shows 3 rows of tiles as expected
* Added "Minimum Refresh Rate" settings option in Settings > Display instead of hard-coding to 90htz always. With this new option choosing 90htz will (obviously) make it always 90htz , and choosing 60htz is similar to the "Dynamic" option in stock OOS where it decides based on what app your using.
* (With version 18.1 most, if not all of the expected LineageOS features have been merged)
* Fixed "choppy" display frame rate that would happen from time to time
* Fingerprint recognition speed improvement.
* Fixed excessive battery drain when Always On Display is active
* Update dalvik configs (they were configured for an 8GB RAM devices, we have 12)
* UI: Enabled blur
* Fixed IMS from spamming system logs
* Fixed booting with SELinux Enforcing on "user" build types
* Enabled SELinux enforcing
Nov 20
* Fixed up all the small bugs from test build
* Standalone 5G (NR SA) support, requires being on 10.0.39 or newer modem. Also be aware the signal icon will show no bars when connected to NR SA, this is just a cosmetic bug.
* Updated audio configs to to match OOS 10.0.39
* Added audio volume policy , should fix the lower then normal volume when below 50%
* SELinux is currently set to "Permissive" until I work out all the sepolicy errors
Oct 14
* Initial internal test Release
[ROM]: lineage-18.1-20210303-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip
Gapps: TEMP INCLUDED WITH ROM IMG UNTIL ITS FLASHABLE VIA CUSTOM RECOVERY
[Download Archive]: All ROMs
https://github.com/LineageOS
https://github.com/Team-Hydra/android_device_oneplus_sm8150-common
https://github.com/Team-Hydra/android_device_oneplus_hotdogg
https://github.com/Team-Hydra/android_kernel_oneplus_sm8150
https://github.com/Team-Hydra/proprietary_vendor_oneplus
Thank you
90hz not showing in display or anywhere else?
Thanks man, just showed my appreciation via PayPal. Happy Thanksgiving! This build rocks. Passes safetynet with props module spoofing a Oneplus 8. Or you wouldn't be getting that stuffing! Stable as hell, everything working for me so far. Happy Holidays to all
when tryping fastboot reboot fastboot it says "fastboot: usage: unknown reboot target fastboot"
Is there any chance this would work on the Sprint OnePlus 7 Pro 5G? If not are there any roms that do currently work for Sprints model
Globel said:
when tryping fastboot reboot fastboot it says "fastboot: usage: unknown reboot target fastboot"
Click to expand...
Click to collapse
your using an outdated fastboot binary on your pc. download latest version
skyrmion said:
Thanks man, just showed my appreciation via PayPal. Happy Thanksgiving! This build rocks. Passes safetynet with props module spoofing a Oneplus 8. Or you wouldn't be getting that stuffing! Stable as hell, everything working for me so far. Happy Holidays to all
Click to expand...
Click to collapse
Thanks so much man that meant a lot to me
New build uploaded. I recommend everyone to update to it as it addresses the last few bugs i'm aware of and all the LOS specific features are fully merged
I got this installed and it's fantastic. For some reason my camera is capped at 12mp, even on other camera apps. Is there anything I can do about that?
333severs said:
I got this installed and it's fantastic. For some reason my camera is capped at 12mp, even on other camera apps. Is there anything I can do about that?
Click to expand...
Click to collapse
That's normal,even on OOS
First time installing a custom ROM but when I run "fastboot update lineage-18.1-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip" I get an error reading "Fastboot: error: failed to open zip file 'lineage-18.0-<builddate>-UNOFFICIAL-hotdogg+GAPPS_fastboot.zip': I/O error
EDIT: I got it working
I've installed the latest build (18.1, build 12/26), but I can't change notification, ringtone, or alarm through settings. Clicking on any of those restarts the settings app.
EDIT: I tried to do a workaround through tasker, but when I go to choose the sound I get the following popup:
Error: android.content.ActivityNotFoundException: No Activity found to handle intent { act=android.intent.action.RINGTONE_PICKER (has extras) }.
I wasn't able to find a working solution through google. I tried clearing the cache for settings and restarting, but it didn't fix anything. I also can't use the default launcher as it just continually crashes, but the pixel launcher works fine.
factorion said:
I've installed the latest build (18.1, build 12/26), but I can't change notification, ringtone, or alarm through settings. Clicking on any of those restarts the settings app.
EDIT: I tried to do a workaround through tasker, but when I go to choose the sound I get the following popup:
Error: android.content.ActivityNotFoundException: No Activity found to handle intent { act=android.intent.action.RINGTONE_PICKER (has extras) }.
I wasn't able to find a working solution through google. I tried clearing the cache for settings and restarting, but it didn't fix anything. I also can't use the default launcher as it just continually crashes, but the pixel launcher works fine.
Click to expand...
Click to collapse
hmmm. i'll take a look. tbh i restored stock like a week back to get updated libs and then my ISP was having all types of issues , one thing lead to another. blah blah blah.. i'm back now though
does this have pocket mode? or check proximity sensor before wakeup?N im happy your back
Also I dont seem to get the same signal as on aosip or oos not sure why switched it to global and im on the new sim
Great ROM so far! Just got one thing to add. Anyone seeing low WiFi signal? My house isn't big at all but when I'm in the kitchen, which is about 20 ft away form the router, it'll keep switching between data and wifi because it says the signal is poor. My gf's stock pixel is at full bars in the kitchen. Any thoughts? Also, I reflashed and still same issue.
I've been watching this therad ever since you released it, and it looks to keep getting better,, so kudos to you man! I have the T-Mobile variant on the Mint netowork, so I'm always afraid to try anything but I haven't done much research on if you can flash it to a T-Mobile device. Let me know, thanks!
Dopewaffles said:
I've been watching this therad ever since you released it, and it looks to keep getting better,, so kudos to you man! I have the T-Mobile variant on the Mint netowork, so I'm always afraid to try anything but I haven't done much research on if you can flash it to a T-Mobile device. Let me know, thanks!
Click to expand...
Click to collapse
I have the same phone, also went from t-mobile to mint. You have to get oneplus to unlock the bootloader, and then you can follow the flash instructions for the rom (Probably want to do the backup as well, although that wouldn't work for me). If you try it, hopefully you don't have the issues I had with notifications/ringtones.
Non-Official Lineage 20.0 for EMUI 9 Huawei (ANE, FIG, POT, VTR, STF)
{
"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"
}
LeaOS is a project which based on LineageOS 20.1 with Andy Yan's and TrebleDroid GSI patches. I have added my personnals patches for Huawei devices : Encryption, Signal Strengh, Speed Boot, Assisted GPS, NFC, CAST/Miracast, Media App fixes, Camera HDR, SafetyNet etc..)
Changelog :
LeaOS Maarch 2023 version
Move to Android r35 (SPL Maarch)
Add offline charging
Add spoof model to pass safetynet
LeaOS February 2023 version
First release
Pre-requisite :
You must have TWRP installed if you want install patch. and a phone with unlock bootloader
Installation (crypt or uncrypt)
Download the version that corresponds to your Huawei phone model here and extract img file. You can choose with ou without GoogleApps
Flash system image : fastboot flash system <drag system.img here>
Flash twrp image: fastboot flash recovery_ramdisk <drag twrp img here>
Boot into twrp: power + vol+ while NOT connected to pc
Resize system: Wipe > Advanced Wipe > System > Repair or Change File System > Resize File System > Swipe
Wipe cache, dalvik/art cache, internal storage
Wipe data
(option) Install DRM patch for EMUI 9.1 to support DRM : 8-Huawei-FixPreav-AB-v1.3-signed.zip
(option) Install single modem patch for multi-sim device : 11-Huawei-MonoSim-AB-v1.1-signed.zip
reboot to System and set up the phone with Lineage first start assistant.
Enjoy !!!
Source Code:
https://github.com/Iceows
ROM OS Version: Android 13
ROM Kernel: Linux Huawei 4.9.148 or Phenix 4.9.319
ROM Firmware Required: EMUI 9.1
Based On: Lineage 20.0 and TrebleDroid
Credits:
@Frax3r (Testing)
@PHH
@eremitein
@RakinTheGreat (GCam)
@TureX (Kernel)
And all the others who tested my patches and helped me improve this ROM
Support Group
Channel update
Screen
Thank you for releasing this ROM, gave my old P20 lite new life! Everything works as far as i can tell, only one minor annoying thing: When i unlock the phone via finger print a random widget gets highlighted on the home screen or if i am in a messaging app while unlocking it types the "="-sign into the input field
eiabea said:
Thank you for releasing this ROM, gave my old P20 lite new life! Everything works as far as i can tell, only one minor annoying thing: When i unlock the phone via finger print a random widget gets highlighted on the home screen or if i am in a messaging app while unlocking it types the "="-sign into the input field
Click to expand...
Click to collapse
Same here. What do you think the possible solution?
I started digging around in some logcat logs and found a bunch of errors/warnings related to not finding some apps due to the fact that i don't have gapps installed.
I also noticed, that the "=" sign only appears if i unlock the screen via the fingerprint reader, not when unlocking with my pin, @Chrisu_Kun can you confirm this behavior?
eiabea said:
I started digging around in some logcat logs and found a bunch of errors/warnings related to not finding some apps due to the fact that i don't have gapps installed.
I also noticed, that the "=" sign only appears if i unlock the screen via the fingerprint reader, not when unlocking with my pin, @Chrisu_Kun can you confirm this behavior?
Click to expand...
Click to collapse
It was a problem even back in android 10 era. I do not have a fix for it as I broke my fingerprint sensor. But I can give some insights into the issue. Here you can see wakeup function is using key number 118 which corresponds to KEYCODE_META_RIGHT. When used it unlocks the phone which means it does work and does execute. After that it writes "=" (KEYCODE_EQUALS) which is keycode 70. Totally unrelevant 2 seperate keycodes. This is strange because keycode 70 doesn't exist in /system/usr/keylayout/fingerprint.kl or /vendor/usr/keylayout/fingerprint.kl. My speculation is that keyboard apps, mainly gboard as it is bundled with aosp, translates KEYCODE_META_RIGHT into KEYCODE_EQUALS because it doesn't know what to do with that key. Keyboard apps does that regularly. For example if you want to press enter via keycodes you can use adb shell input keyevent 61 which is KEYCODE_TAB. How to be sure? Try multiple keyboard apps, gboard, swiftkey, samsung keyboard, simple keyboard, anysoftkeyboard, hacker keyboard even some lesser known keyboards. If one of them doesn't have this issue that means my speculation is correct and keyboard app translates KEYCODE_META_RIGHT. You might ask if this is the case why it doesn't happen in emui, i can't answer that honestly. As i said this is just a speculation.
edit: also could you try installing gapps? swipelibrary in gapps packages could be another factor
How do you install this? I thought Huawei disabled unlocking bootloaders. Is there another way, then?
uukelele said:
How do you install this? I thought Huawei disabled unlocking bootloaders. Is there another way, then?
Click to expand...
Click to collapse
Yes, take a look at PotatoNV (in the linux/macos crossplatfrom project some bootloaders are missing): I haven't tried using it yet, but I'm planning to.
I hope @AltairFR stay on top of the fixes on this custom rom, and thank you again for all the work you doing for us.
I havnt booted this on my p20 lite, what are known buggs, and when should we expect a patch.
Frax3r said:
It was a problem even back in android 10 era. I do not have a fix for it as I broke my fingerprint sensor. But I can give some insights into the issue. Here you can see wakeup function is using key number 118 which corresponds to KEYCODE_META_RIGHT. When used it unlocks the phone which means it does work and does execute. After that it writes "=" (KEYCODE_EQUALS) which is keycode 70. Totally unrelevant 2 seperate keycodes. This is strange because keycode 70 doesn't exist in /system/usr/keylayout/fingerprint.kl or /vendor/usr/keylayout/fingerprint.kl. My speculation is that keyboard apps, mainly gboard as it is bundled with aosp, translates KEYCODE_META_RIGHT into KEYCODE_EQUALS because it doesn't know what to do with that key. Keyboard apps does that regularly. For example if you want to press enter via keycodes you can use adb shell input keyevent 61 which is KEYCODE_TAB. How to be sure? Try multiple keyboard apps, gboard, swiftkey, samsung keyboard, simple keyboard, anysoftkeyboard, hacker keyboard even some lesser known keyboards. If one of them doesn't have this issue that means my speculation is correct and keyboard app translates KEYCODE_META_RIGHT. You might ask if this is the case why it doesn't happen in emui, i can't answer that honestly. As i said this is just a speculation.
edit: also could you try installing gapps? swipelibrary in gapps packages could be another factor
Click to expand...
Click to collapse
I may be misunderstood it but even I Install Nikgapps there is always an error/crashing when I open in my phone. Even so, how you will I remove KEYCODE_META_RIGHT?
eiabea said:
I started digging around in some logcat logs and found a bunch of errors/warnings related to not finding some apps due to the fact that i don't have gapps installed.
I also noticed, that the "=" sign only appears if i unlock the screen via the fingerprint reader, not when unlocking with my pin, @Chrisu_Kun can you confirm this behavior?
Click to expand...
Click to collapse
Even I unlocked it with my password. It still does the same thing
luc.sol said:
I hope @AltairFR stay on top of the fixes on this custom rom, and thank you again for all the work you doing for us.
I havnt booted this on my p20 lite, what are known buggs, and when should we expect a patch.
Click to expand...
Click to collapse
Well you expect a bugg such as this
eiabea said:
Thank you for releasing this ROM, gave my old P20 lite new life! Everything works as far as i can tell, only one minor annoying thing: When i unlock the phone via finger print a random widget gets highlighted on the home screen or if i am in a messaging app while unlocking it types the "="-sign into the input field
Click to expand...
Click to collapse
The problem has not yet been fix. As I'm using this custom rom, i clearly say it's true
USB tethering is not working on Phenix 4.9.319 but works on Linux Huawei 4.9.148.
Other things just works fine.
d0zzerr said:
USB tethering is not working on Phenix 4.9.319 but works on Linux Huawei 4.9.148.
Other things just works fine.
Click to expand...
Click to collapse
@TureX
AltairFR said:
@TureX
Click to expand...
Click to collapse
Hi!
Please share logs and i will take a look.
DadiBit said:
Yes, take a look at PotatoNV (in the linux/macos crossplatfrom project some bootloaders are missing): I haven't tried using it yet, but I'm planning to.
Click to expand...
Click to collapse
I've successfully unlocked the bootloader, installed twrp-3.7.0_9-0-anne.img and LeaOS-20.0-20230304-iceows-google-ane.img. First time doing it, but the guides had enough details for doing most of the stuff. I can share the .md file if anyone is a newbie like me.
eiabea said:
I started digging around in some logcat logs and found a bunch of errors/warnings related to not finding some apps due to the fact that i don't have gapps installed.
I also noticed, that the "=" sign only appears if i unlock the screen via the fingerprint reader, not when unlocking with my pin, @Chrisu_Kun can you confirm this behavior?
Click to expand...
Click to collapse
I have gapps installed (probably doesn't matter, but it's better to specify), and while testing with both the AOSP keyboard and Gboard, I couldn't reproduce the bug, neither with the normal pin unlock, nor with the fingerprint + neither with the screen properly locked nor by "unlocking" via fingerprint before the locking timeout fired.
On the other hand, I encountered another bug: although enabled in the settings, I couldn't show the notification panel by sliding on the fingerprint reader.
PS: thanks for the great ROM, if I can help in any way I'd be happy to
I've been using this ROM for a few days and I noticed a two bugs:
Audio and usb data not working. Neither in TWRP, nor in OS: might be a hardware problem, but it's strange, since I've used adb on Monday and my alarm rang Thursday 100%. It's really strange that I changed the USB port a week ago (same usb data issue) and it's back again... I'm going to do some testing
Data can't be backed up: twrp errors in createTarFork() when copying the nfc module data
As per OP emui 9.1 is required, am on vtr-l29(EMUI 9.0), so this rom ain't gonna work?
The system partition cannot be adjusted, an error occurred （error:4）
start infinite loop
The platform-tools version problem has been solved
very very very fantastic job!!!
i never see something like this (is mine first lineageOs)
the only thing not work is camera go app (ho care, the other app camera work perfect)
and a quik drain battery (maybe afwall+)
(installed the one with gapps)