AOSP 7.1.* Z5 Premium - Xperia Z5 Premium Android Development

Present you with a 7.1 .1 Nougat AOSP!
Tested on E6853, released a build for Dual E6883 "NOT TESTED" try at your own risk
Install trough ADB as usual by flashing boot.img system img and userdata.img
(detailed how to in post no.2)
Note:
If you are updating from previous release, flash only system.img if you wanna keep your userdata (you will only loose gapps)
This is pure AOSP.
have tried most of it and everything has been working fine.
Improvments from 7.0:
Camera is working (Not inverted anymore)
Fingerprint is working
Auto brightness works as intended
Known bugs:
AC 5GHz wifi might not work for all.
Fingerprint might bug out for some people.
Download Here
GApps
(Use arm64 7.1)
Updated 2017-04-14
AOSP 7.1.1 rev 38
Cheers
XDA:DevDB Information
AOSP 7.1.*, ROM for the Sony Xperia Z5 Premium
Contributors
Elfmirth
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Stable
Current Stable Version: _r7
Stable Release Date: 2016-12-18
Created 2016-12-14
Last Updated 2017-04-17

Reserved
How to:
In the ADB folder press shift key and right klick with your mouse, choose "Open Command prompt here"
Power off your phone, once it's off, press and hold volume key up, and plugg it in to your PC, now the indicator on the phone sould turn blue, that shows that the phone is in Fastboot mode.
(Check in your device manager that the sony fastboot drivers are installed)
when all that is done, in the command promt type:
Code:
fastboot flash boot "drag and drop the boot.img file"
when that is done type:
Code:
fastboot flash system "drag and drop the system.img file"
after that:
Code:
fastboot flash recovery "drag and drop the recovery.img file"
when all is done type:
Code:
fastboot reboot
and your phone will reboot, it might take longer than usual.
If you wanna install gapps and root READ!! and follow this to boot up TWRP.
When phone is booted up, turn it off again enter fastboot mode then:
1.
Code:
fastboot [U]boot[/U] TWRP.img
2. On your phone press volume up until you see that you're booting in to TWRP

Thanks a lot! I've been meaning to try building this myself. Thanks for giving me hope again for the Z5P!

e6833
thank you.
is it working for z5p Dual?

faraheed said:
thank you.
is it working for z5p Dual?
Click to expand...
Click to collapse
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend ?

e6833
Elfmirth said:
No so far I have only done a build for E6853, since I have One of those, but ill see if I can give Dual a try this weekend
Click to expand...
Click to collapse
thank you my friend, can i try it on my e6833?

faraheed said:
thank you my friend, can i try it on my e6833?
Click to expand...
Click to collapse
Ofc you can try, but to be safe wait until I have made a proper build for it ?

e6683能用吗,或者说e6653

I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.

Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!

WannaB101 said:
Tested and played with it for a couple hours. (E6853)
Everything seemed to work flawlessly minus performance being a little on the slow side in comparison to stock Sony Roms.
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
(also, i couldnt find the asop.zip you referenced in the OP so i directly flashed all the .imgs directly)
Once we get the performance close to stock, and Camera up to par (its A LOT better, but still lacking features) this will definitely become a daily driver for me!
Lets hope Sony keeps pushing quality uploads to their aosp program!
Click to expand...
Click to collapse
The speed will improve over time, the first 2-3 hours and 2-3 reboots mine was a bit laggy to, but after installing pixel launcher and playing around for a few hours there is no lag at all and it's just as fast as my HTC 10 (if not faster)
FC on SU I havent had, but then again only used it for 3-4 apps but worked fine with those.
The asop.zip was a typo on my end, have removed it now (was a little to tired)
exvargos said:
I've noticed a bug, Wifi AC (5GHz band) doesn’t work with this ROM. i flashed the 3 imgs (Boot, system, userdata) with fastboot, then used the boot.to.TWRP to boot into TWRP and flashed GApps and SuperSU through that.
Click to expand...
Click to collapse
"Edit" I tried a couple of times now and the only issue I had was cus of bad reception. But then again I dont have AC router only N 5GHz

WannaB101 said:
I didn't notice any issues with the 5ghz as it connected just fine and gave me 351mbps down and 26mbps up.
Im not sure if its 7.1 or an issue with the ROM but i couldn't get SU/Busybox to properly open. It kept FC even after clearing my caches.
Click to expand...
Click to collapse
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.

It's a lot better than the current 6.0.1 ROM I was previously using. RAM usage was cut down by half, battery life is pretty phenomenal and everything is butter smooth. I had some camera issues in the past where the z5p could never focus on anything.
All fixed with AOSP 7.1, making it my daily driver

Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?

KbaB.BroS said:
Great ROM, but I have some issues with fingerprint. I added them during the initial setup and now they don't work after I rebooted once, so I tried to remove and add new fingerprints but the system freezes when I try to delete them. anybody else with same issues?
Click to expand...
Click to collapse
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
exvargos said:
How did you flash? I tried again, fastboot flashing all 3 images then flashing gapps through the provided twrp, but still no 5G wifi.
Click to expand...
Click to collapse
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)

Elfmirth said:
Hmm, haven't had that issue, but I never added fingerprint during setup, only added it after setup.
Hmm that is wierd.
Im building a new rom atm, updated to 7.1_rev7 (from rev6) so hopefully it will fix some issues. Will be uploaded tonight if all goes well, and will upload for e6883 as well.
How is battery life for everyone? I had some massive drain on 7.0 but have had almost 3 days on one charge here (mostly standby)
Click to expand...
Click to collapse
Battery life is much better than Sony stock ROM and everything based on it, easily lasts me one day which is what I need. Light usage keeps the phone alive for more than two days.

@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.

KbaB.BroS said:
@Elfmirth from which stock FW version did you come from? from my experience fingerprint and other issues happens when I try flashing ROMX over a different FW than it was based of so the 5G WiFi and fingerprint might be a cause of this.
Click to expand...
Click to collapse
The first FW I started out flashing from was 32.1.A.1.163. Then I flashed AOSP 7.0 and after that AOSP 7.1

OP Updated with rev7 for both e6853 & e6883
enjoy

Hi Elfmirth,
Thanks for your work.
Hope you keep support for the dual sim devices too. Thanks
Best Regards,
Ashray
Elfmirth said:
OP Updated with rev7 for both e6853 & e6883
enjoy
Click to expand...
Click to collapse

Related

[ROM][6.0][ALPHA/WIP][UNOFFICIAL] CM 13.0 and TWRP for Sony Xperia X Compact (kugo)

Now with LineageOS 14.1 Nougat
builds
sources (github) PATCHES STRONGLY ENCOURAGED
local_manifests for building
current branch is cm-14.1 (LineageOS 14.1 with Linux 3.10.x)
Instructions:
Unlock bootloader
Flash TWRP from kugo/twrp/recovery.img or from https://forum.xda-developers.com/x-compact/development/recovery-twrp-t3522249
Do not use AndroPlus's, it does not handle /system writing very well (in my experience)
Do not use my recovery build for stock, it does not handle /data encryption
Flash zip in recovery
SELinux: Permissive (I haven't updated the sepolicy in a while, enforcing makes the camera panic which causes bootloop. I may fix this later.)
Lineage 14.1
WORKING:
WiFi
Data/Cellular (you may want to jot down APN settings from stock before flashing)
Fingerprint reader (a bit unreliable, will fail sometimes)
FMRadio
Camera
NOT WORKING:
AudioFX (the built in equalizer thing; just disable it from the apps menu)
SELinux (sepolicy needs update)
Bluetooth (system seems to crash when turning it off)
Whatever isn't working in AOSP/Omnirom (e.g. in-call volume control)
UNTESTED:
NFC (it turns on, but I have no NFC devices)
Keep in mind that I am not really a developer but will do what I can to help with issues
Special thanks to the Sony-Kitakami team for serving as a base to port changes from suzuran/kitakami to kugo/loire
Additional thanks to humberos for porting omnirom to kugo and serving as a base to port to kugo
...and thanks to Sony for allowing us to unlock our bootloaders and for porting AOSP to their phones (unlike some other manufacturers)
Recent Changes:
Rebased device trees off of omnirom trees, updated everything
I'll go first and say thank you for developing for this device.
Hope that this encourages other devs to build their ROMs too.
Great job! :good:
Nice
as soon as audio playback is fixed i will flash and try to post logcats !
A little love for the XC
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
ardylemon said:
Keep up with the good work! Now that TA backup is also possible, it's just a matter of fixes until this is good to go!
Click to expand...
Click to collapse
Not to mention greater adoption of ROM flashing now that we have a way to get back to stock.
thanks for the update!
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Micka84 said:
Looking forward to testing cm14.1. Has anyone already flashed it and can give some feedback and impressions?
Click to expand...
Click to collapse
I would go with cm-13.0 honestly unless bluetooth is that important (which is next on the to-do list for cm-13).
CM-14.1 is pretty incomplete upstream, so it's missing some features (like theming).
It's also still running the marshmallow kernel, so things like vulkan probably won't work either, and
I don't plan on releasing a build with the nougat kernel until we at least get prebuilts for it.
howdid said:
as soon as audio playback is fixed i will flash and try to post logcats !
Click to expand...
Click to collapse
Audio playback should be "fixed" now, for both 13 and 14.1
How is camera quality and battery life?
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
ammarr said:
Looking for a little bit of clarification. After unlocking the bootloader, what is the process for installing TWRP? Does it require a modified boot.img to boot recovery as outlined in AndroPlus's thread? Thanks.
Click to expand...
Click to collapse
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
tlxxxsracer said:
How is camera quality and battery life?
Click to expand...
Click to collapse
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
EliWallace said:
I don't think I ever needed to flash a modified boot.img, so just flash recovery in fastboot, power off the phone, and then boot into it with volup+power
If for some reason that doesn't work, you can flash AndroPlus's boot.img and try again
I can't really comment on the camera (it seems fine to me, but that isn't my area of expertise), but the battery is admittedly not where I want it to be after disabling audio offloading and rolling back the kernel for bluetooth.
Kind of waiting for CM-14.1 to be more ready to fix both of those
Click to expand...
Click to collapse
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
ammarr said:
Thanks for the reply and for bringing CM to the XC.
Comparatively how much worse is the battery life compared to stock? Obviously depends on usage but are you still able to make it through the day?
Click to expand...
Click to collapse
It was enough to get through a day, but I would end up with 30-50% instead of 60-75% (I have mail checking constantly, so that was a big drain)
Thats in comparison to a CM build with a newer kernel and audio offloading not disabled,
I haven't used stock at all so I don't know how the battery life is on it
Why not use an existing msm8956 tree for kenzo and hydrogen and make Sony additions to a car kernel source and boot cm. It will bring much lesser issues.
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
NL_henk said:
Rom looks good!
But I only have 2 problems:
1) I have a changing mac adress. Every time I reboot my device, I get another mac adress. It always starts with 00:90:4c but the remaining part changes.
I found some solutions on google, but nevertheless they didn't work... Maybe because the solution is not for X compact or CM 13/14.1....
2) The phone doesn't charge when I connect it to the wall socket. Just for half a second the led turned yellow, but after that it stops charging. The cable and battery are fine (I went to stock and it charges immediately).
Hopefully does anybody have a solution or idea how I could fix these problems!
Click to expand...
Click to collapse
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
NL_henk said:
I think it has something to do with the kernel. Could someone let me know which kernel-version is used?
Click to expand...
Click to collapse
I also noticed that the mobile does not charge however at the laptop over USB load it
Ps. i use not Costum Kernel

Android Nougat ROMs List for the BLU Life One X 2016

This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.

[ROM][XC][O][8.1][WEEKLY]OmniROM

XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (Optional) Flash a gapps package
4. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. No USB tethering
2. Wifi sometimes fails to turn on
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-8.1
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][O][8.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
Source Code: https://github.com/omnirom
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2018-01-14
Last Updated 2018-11-03
Awesome!! Thank you very much, I'll be trying this out immediately!
oshmoun said:
XC/KUGO/F5321 OmniROM BUILDS
OREO 8.1
Click to expand...
Click to collapse
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
 @oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
levone1 said:
So far so good. Using Magisk root, and Xposed beta, and micro g, and all working well. WiFi did disconnect once so far. Hopefully a fix coming... Thanks
@oshmoun - can you add option to switch nav buttons, or enable nav bar tuner? I can't get my apktool working on O, and no Gravitybox for O yet either...
Click to expand...
Click to collapse
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
I can register new fingerprints, but i cant use them to unlock my phone or to login on apps.
I installed TWRP https://forum.xda-developers.com/x-compact/development/recovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
OmniROM work greatly on my device, I'm using since 14 Jan without any problem! Really Thanks!
coderex96 said:
I installed TWRP https://forum.xda-developers.com/x-...ecovery-twrp-3-1-1-xperia-x-compact-t3640914, the OEM image and I'm testing OmniROM now, thanks for your work, where can I report bugs?
Click to expand...
Click to collapse
Here only. With logs if possible.
farfetch said:
Try this: https://play.google.com/store/apps/details?id=xyz.paphonb.systemuituner
Click to expand...
Click to collapse
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
levone1 said:
Oh yeah, I actually have that in my downloads already. Forgot about it... Thanks
---------- Post added at 12:54 PM ---------- Previous post was at 12:51 PM ----------
Lost mobile data today. At first boot, working fine, then installed AfWall and changed dns, and still working fine yesterday. Then this morning, no mobile data. Signal shows bars, but no 4g/lte, etc, and won't connect. Tried disabling and uninstalling tweaks and many reboots, but no change.
Update - now it's in and out...
Click to expand...
Click to collapse
seems to be caused by installing afwall? could you please try without it?
oshmoun said:
seems to be caused by installing afwall? could you please try without it?
Click to expand...
Click to collapse
I am testing now. I haven't checked it enough to saying it's a rom issue; just wondering if anyone else has had it. It worked find with AfWall yesterday, but now in and out. I remember the same issue with AfWall on certain CM 12 roms...
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
OpenDelta
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
edit: forgot to mention I of course also had to update gapps to an 8.1 supporting version. I downloaded an unofficial pico opengapps from here
drstefankrank said:
oh man, thanks for making these ROMs, but the updater of 7.1 recommended this update and I just pressed install. Recovering from a brick now…
I'll come back to it later, when I have time for all the prerequisites.
Click to expand...
Click to collapse
cds0 said:
Nice work. OpenDelta advertised this update which I naturally installed without checking the requirements here. No requirements were stated before the update. Bricked my phone in a place where I couldn't do much about it. Just ask to please be more considerate since I more or less trust the update tool.
Click to expand...
Click to collapse
harryharryharry said:
FYI: I dirty flashed from 7.1.2 via opendelta too. Once I flashed the oem partition using fastboot, the device booted again (only a handful of apps force closed and needed their data cleared to function properly again). Not the best choice to make this update available for installation with opendelta, no...
Click to expand...
Click to collapse
Good to know flashing the odm image helps when updating from 7.1
About opendelta, i don't have much control over it to filter out the 8.1 build. It's all done automatically.
Besides, it did do its job well. It notified about the new version.
The requirement to flash a seperate ODM image is similar to how it's needed to flash a vendor image, and not just system and boot images, on Google devices. Guess that's new for Sony devices, hence this confusion.
@oshmoun - how about kcal support? Here's my tests with kppd - https://forum.xda-developers.com/showpost.php?p=75200267&postcount=64 (and forward)
@oshmoun: Yeah I was kind of surprised to see 8.1 was available through opendelta, and I didn't think it would work. So I backed up everything before upgrading. Which is probably what people should do before upgrading anyway
Flashing the oem partition was a relatively easy fix, so it's all good.
Thanks again for your great work! It's much appreciated as the number of custom roms for kugo is really slim pickings.
Latest stock ftf compatible is 34.3.A.0.252, right?
EDIT: It seems so. Flashed it and this build works great with it, so far.
I've performed a clean install after full wipe and also don't have mobile data working. Wi-Fi works, though.
Strange issue I have is the lack of sound over bluetooth ONLY in calls. Playing music/video works otherwise. It's quite baffling. This was working as expected on 7.1.

[ROM][XC][P][9.0][WEEKLY]OmniROM

XC/KUGO/F5321 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device crashes and reboots (mostly happens on demanding tasks)
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XC][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun, humberos
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-06-16
Last Updated 2019-06-16
so are the micro lags fixed or still happening? there were slow downs and microlags on on games like clash royale etc... not as smooth as stock
This is excellent news! For those of us coming from 8.1 should we dirty flash (along with dsp-label-fixer) or is full data wipe required?
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Bluestar01 said:
Tried already but not booting completely.
I came from Omni 9 homemade.
Installed this one and restartet and waited about 20 minutes, but only the omni sign visible with wobbly feelers.
Then restored backup.
Need to do complete clean install?
Click to expand...
Click to collapse
yes
official builds are signed and hence not really compatible with homemade
oshmoun said:
yes
official builds are signed and hence not really compatible with homemade
Click to expand...
Click to collapse
thank you, clean flash and is working
Great work! thanks for taking time to upgrade this ROM to Pie.
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
EDIT: GPS works
EDIT 2: GPS has a mind of its own and will not work except for the time when it does, currently investigating (probably something wrong with my phone)
ardylemon said:
Is GPS working? I have just installed the ROM with binaries v9 and GPS detects satellites, but cannot lock onto any. (I previously had harry's ROM with the same problem as well, I guess it's poor implementation from the AOSP end)
Click to expand...
Click to collapse
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
droncheg said:
Just tried in GPSTest - locking works. Omnirom 9 official, v9 OEM. Clear field would be best test area =)
Click to expand...
Click to collapse
Thank you, I also got it to work after waiting a while, enabling mobile data as well as derping around with A-GPS settings in the process appears to have worked (not sure which, though). For future reference, my phone locked in after detecting at least 8 satellites with ~20% signal.
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
I've not this problem, for me all is working well and smooth (the only problem is quickswitch magisk module not working).
badbatlinux said:
All seems work (camera, fingerprint...) but an important things don't work. The phone conversation don't work (micro and audio), I can't received and emit sound. BUT the contact can received the sound of phone numbering ?!?!!
I specify that the sound and the microphone works perfectly.
So it's unusable.
I return to => Omnirom 8.1
Click to expand...
Click to collapse
The Unofficial version of OmniROM by HarryHarryHarry had a similar issue, the fix was to first flash the latest stock ftf image (ends with .118), flash twrp and do a clean install of the rom. I would think this fix is going to work for this version too.
I'm currently running the Omnirom 8.1, and I just got a pushed message from OpenDelta on the phone itself:
Update ready to download
omni-9-20190616-kugo-WEEKLY
Click to expand...
Click to collapse
Can I update to Omnirom 9 from the phone itself by running that? Or must I download the rom on my computer and install it the normal way?
Great I will try this very soon!
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
In regards to the device crashing/rebooting issue. Does underclocking help at all?
lapucelle2 said:
8.1 omni -> this rom -> micphone issue
so,
i will try back to stock rom, and flash this rom. thanks
Click to expand...
Click to collapse
Did that work? I've got the same issue
After updating to the latest weekly today, some apps got uninstalled again. I dad this behaviour also with the test builds before.
can't find stock rom yet i gave up upgrade to 9.0
Mietjelan said:
Did that work? I've got the same issue
Click to expand...
Click to collapse
can't find stock rom yet i gave up upgrade to 9.0
lapucelle2 said:
can't find stock rom yet i gave up upgrade to 9.0
Click to expand...
Click to collapse
I can't find how to install it either, all that flashtool crap isn't working...

Lineage 17.1 is available now

So this morning I went to check on lineage OS news oh, and I found out that they released today for all pixels. I am running it with no issues although I would recommend to download the micro gapps package cuz if you do the Nano or anything below it will give you issues with your phone reading SIM card. Aside from that I had successfully running the rom with magisk installed.
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Which versions of gapps did you try? Only nano/micro? I was thinking of selecting pico. Also, can you update via their in house ROM updater app while rooted?
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
i42o said:
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
bradical711 said:
Thank you for the detailed response!! I greatly appreciate all the info and I'm sure others will as well!:highfive: I will probably try it when the ROM becomes more stable. Currently on DU myself and I don't mind waiting until the project improves further. Would you mind letting us know in the thread how your first update goes while rooted? Thank you again for trying the legendary ROM and letting us know it was released!
Sent from my Pixel 4 XL using XDA Labs
Click to expand...
Click to collapse
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
i42o said:
Yeah, so after I installed it and set it up, I then adb sideloaded magisk canary on its stock kernel, it went thru like knife thru butter.
I then rebooted into android, finalized the magisk set up, rebooted and voila... I was rooted.... I then tried Kiri Kernel, since it has the necessary things for TWRP, flashed it within ex kernel and then tried to boot TWRP in bootloader only to get stuck on TWRP splash screen...
I was honestly trying to have lineage working with a working TWRP but unfortunately it did not work as such. So I gave up on the TWRP and I've been running the ROM with magic and modules installed with no hiccups The boot time is amazing battery life is really really good...
Viper worked first try... This has has to be one of three good roms out there with little to no issues.
DU
PIXEL DUST ( CAF )
LINEAGE
Click to expand...
Click to collapse
Is 90hz working??
ahoslc said:
Is 90hz working??
Click to expand...
Click to collapse
Read just one or two more posts above the one you quoted to find your answer.
bradical711 said:
Read just one or two more posts above the one you quoted to find your answer.
Click to expand...
Click to collapse
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
i42o said:
Will there still wait to check to see if the updater works but it looks like everything is fully functional within it and right now, take a look at the picture that I'm going to attach to this that is her updater and it looks like it is completely 100% functional but I cannot be sure because there is no updates to test it with.
As far as the gapps go, don't use anything smaller than micro. There is something pixel 4 needs in telephony to work that is in micro+ but not in nano or pico ... If you flash rom without gapps , your phone will work to make calls, if you flash any gapps before micro, you will get a " insert SIM, emergency calls only " message.
After you flash rom, MAKE SURE TO REBOOT AND THEN FLASH GAPPS,! otherwise if you try to do it in the same session that you flashed ramen you will get a message telling you that you have insufficient storage to flash and it will fail to flash gapps!
A few things that I wish and I hope they do fix would be the 90 hertz implementation switch as of now there is no switch for it and the screen flickers at low brightness.
Soli gestures would be great, I know DU has them working so it's a matter of time before lineage does as well.... Same goes with the squeeze for assistant,.... It is also not working ..
Not working :
Soli gestures
Squeeze
Smooth display
this is the first release so I did expect it to not be fully fully functional but I know that within time it will be one of the best roms out there
Click to expand...
Click to collapse
90hz works, 70% plus brightness on coral gives 90hz, below is 60hz. flame has some different tunings percentage wise, but same concept.
RefreshRate will work as soon as we have an official R image I can steal a single APK from.
We won't be implementing Squeeze or Soli most likely - it's RE, and given scrutiy over large projects and reverse engineered code, we likely won't see it unless it's reimplemented OSS (DU reverse-engineered it, but didn't clean room re-implement).
ahoslc said:
Smooth display is auto switching between 60hz and 90hz that's why I asked if just 90hz was working
Click to expand...
Click to collapse
It works.
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Madjax2020 said:
ok well i went back to stock aug firmware and then flashed the img file, then sideloaded the rom, rebooted right into recovery and flashed gapps ... stuck on the lineage boot animation .. do i need to let it boot up then reboot into recovery and flash gapps?
tried again, flashed the image then rebooted to start menu, rebooted to recovery and flash mini gapps and rebooted ... still stuck on the boot logo
what am i missing?
somehow i got it to boot and had a trebucket error, installed a different launcher - FIXED.
can not finish setup, keep getting data transfer crash
anyone get TWRP to load? im using fsociety kernel and it worked on another ROM
Click to expand...
Click to collapse
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
i42o said:
You're going to have to skip that by disabling the app when it force closes . It should let you proceed from there on. TWRP won't work and idk why... Trebuchet launcher will FC as well but since Google home launcher is installed via gapps it should be a fail safe. As far as kernel, I am running kirisakura and it has the necessary things to work with TWRP but I won't. Trust me I tried.... Make sure to root with magisk canary .
To fix cts mismatch in magisk download termux
SU
props
And select option 2 forced basic key attestation
Select y for yes and proceed... Reboot and you should pass safety net checks...
Hit thanks if I helped .. one love
Click to expand...
Click to collapse
thank you sir for the reply. However i could not get it to be stable. The initial setup failed no matter what i tried. The error of data tansfer tool would fail. I want to run this as it seemed very smooth, however i think i need to wait for another update or something. i followed the OP to the t and nothing seemed to work properly for me.
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
I'll try again thanks for the info
Seems the wiki says you can sideload gapps right after sideloading the OS, the OP said doing that causes issues lol. But he'll I'll try it anyway
npjohnson said:
I use this daily, and am entirely unsure what you're doing here.
Are you using the wiki guide? If not, follow that to the tee, use nano opengapps preferably, and everything works like a charm.
Click to expand...
Click to collapse
Got this running great, with gapps. Was wondering if you're getting the issue I am with google assistant. It seems to freeze up and not be usable.
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Madjax2020 said:
followed the wiki directions and used full gapps not nano ( missed that 1 bit of info ) im STILL getting data tansfer tool keps stopping when trying to finish the setup going to try a reboot and see what happens. it shows just a sec then saying looing for updates then installing updates and crashes ... then back t connect to wifi . does this have to do with the gapps?
SO ODD ... reflashed and used nano. asked to connecto to mobile data, nothing as showing up, hit skip, tried wifi and nada .... hit skip then same damn error for setup .... insane. maybe ill just cancel the setup and do everything manually
retied all steps and got the no space error when doing gapps, switched to slot b and tried again and it worked ... waiting to see the data tansfer error ... i dont think my phone wants to play nice lately, or ever.
went back to stock firmware, loaded the 9/6 lineageos and have NO mobile data with nano gapps loaded. doing the update currently and will update shortly what happens
i can officially state i am up and running with so far NO issues, i have mobile data, wifi sent texts and made a call. now going to root and swiftbackup restore all my apps and blah blah
Click to expand...
Click to collapse
You do remember I said micro right? I specifically explained that by using nano you would have no cell phone connectivity and upon transfer tool just put no transfer
XMayhem2099 said:
Anyone tried the new 13th nightly? Hopefully they fixed the screen flicker.
Click to expand...
Click to collapse
Yes it is still there but much less now
Face unlock working?

Categories

Resources