Database Info

[ROM] Mokee 5.1.1 STABLE (Daily Driver)

First Thing First : I'm not the developer of this ROM. Just Sharing "MY" experience
It's been a long time Mokee builds are available for Mi 4i. I've been using it since 2nd last build (more than 10 days) and currently on latest built i.e. 25th Jan 2016. And I can say that it's Stable.
What's Working :
Everything, except volume rocker keys on earphone.
Highlights:
DT2W
D2TS
Ambient Display
Not even a single FCs or Reboot since installation (more than 10 days now)
CoC is working fine
FB is working fine
More than 24 hours backup (With normal use, NO intensive gaming and ~4 hours SOT)
Installation Instruction (Which I followed, You can go with normal way):
1. Flash MIUI ROM 5.6.11 (I tried to install on 7.1.1, it keep on rebooting. Tried everything, but no luck)
2. Flash TWRP as permanent Recovery
3. Root using SuperSU
4. Wipe everything (but ROM & Gapps Folders)
5. Flash ROM
6. Reboot to System (No need to set-up anything, just do next next)
7. Go to Recovery, Flash Gapps
8. Reboot to system (Again no need to set-up anything, just do next next)
9. Factory Reset (From settings, NOT from recovery)
10. Set-up now
11. Enjoy and All the Best
I know it's painful the way I set-up ROM, but yes I'm not facing any problem at all (Fingers-crossed ). We three colleagues are using it. So it's tested now (you can say)
I've only one phone and I'm using it as a daily driver.
Downloads:
ROM
Gapps : pico version

Enjoy the New ROM guys

this rom is still stuck in LP. was hoping for MM already

ajaxcbcb said:
this rom is still stuck in LP. was hoping for MM already
Click to expand...
Click to collapse
You are very much correct my friend, but again it's a very good alternative for :
1. Those who don't wanna be on MIUI.
2. Struggling to find a CM daily driver.
//TM

good to know. I couldn't take the constant reboot from Remix ROM. Just installed Mokee yesterday. So far so good. Keep my fingers crossed.

getting very high wakelock on *alarms* on any mokee rom

Yeah this is the most stable custom rom for mi4i ...
- official
- update OTA almost every week ..

Can anyone verify if fast dormancy is present in the rom? either through wakelocks or logcat(it should say fast dormancy service or otherwise)

Is ambient display working on this rom?

Hey I am not able to do it. I tried it several times, but every time it says that ERROR IN UPDATER BINARY ZIP.......I am not able to flash it. Help me.

Rajat Naik said:
Is ambient display working on this rom?
Click to expand...
Click to collapse
Yes, Check OP.

xposed support?

lineoxkun said:
xposed support?
Click to expand...
Click to collapse
works, no problem!

imagine92 said:
works, no problem!
Click to expand...
Click to collapse
Nice! Definitely will try this ROM tonight! Thanks OP for sharing [emoji1]
Sent from my MI 4i using Tapatalk

What's your SOT on MIUI 7 with similar type of use?

not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.

sik619 said:
not happening please help. i tried flashing mokee 5.1 on my mi4i but there are some errors occuring everytime i try to do it. help on this.
Click to expand...
Click to collapse
Use twrp 2.8.7
http://forum.xda-developers.com/showthread.php?t=3204594

Is it smooth as any other moto g mobile lolipop version...becoz i always get a feel that miui is laggy..i never install a custom rom before

hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me

sik619 said:
hey i flashed mokee and the gapps as well...but now its rebooting repeatedly. there comes this screen with welcome and the language but cant click next option..i dont know why. help me
Click to expand...
Click to collapse
I suggest you to use miui 6.6.10.0 glob stable before flash mokee rom

UNOFFICIAL Lineage 14.1 for AT&T HTC One XL - evita

LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!​
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03

Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1

wow..this device is still alive
hats off
It was my first android ...

paras33 said:
wow..this device is still alive
hats off
It was my first android ...
Click to expand...
Click to collapse
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.

great news!
@mdmower - I was following your GitHub notes over the past while, always hoping there would be something which we could use!
Thanks to all involved - I still have and use my evita, but often with an alternate SIM for travel. It is still a very nice phone. I put new batteries in both my evita, and my wife's, and they keep going. But security... That's where LineageOS, and this build, will be crucial.
I need my evita as a daily-driver for the next couple of weeks, so I'll eagerly read the results from others for now. But I have three other devices using unofficial LineageOS builds, and I'm very happy with them.
Thank-you, everyone!

Dnorris55 said:
It was my first Android also.
Been waiting for a modern ROM for it...
I think I got it loaded, but can't get thru the setup, due to popups...
com.android.phone has stopped...
google play services has stopped....
"that" has stopped...
"whatever" has stopped.....
Edit: I reinstalled the ROM today, and was able to setup properly. Only quirk so far is a red outline that flashes around the screen occasionally.
Click to expand...
Click to collapse
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen

wlewin said:
how exactly did you reinstall? I just did a series of wipes and reinstall and am still getting force closes like mad. cant properly get the device running/through the setup screen
Click to expand...
Click to collapse
I'm not sure just what worked, because I tried so many things. I even tried flashing the evita-x twrp, but it didn't work, so I reflashed the twrp in the op. At one point, I thought I was really screwed, because the data partition showed a size of 0. Then I re-did the format data (step 6), and was able to install the ROM and get thru the setup.
You might try reflashing the twrp, and repeat step 6.
Also, I installed the ROM by itself, booted and setup.
Then flashed gapps and rebooted.
Then flashed SuperSU.
Sent from my SM-T800 using Tapatalk

h8rift said:
Please be sure to thoroughly read the instructions to do the partition swapping. This should be nearly identical to jrior001's thread for CyanogenMod 12.1
Click to expand...
Click to collapse
Great development on the One XL. Thanks guys for the great work. I managed to install the rom. It however seem unstable and apps taking long to open. Also the red box on the edge of the screen. Will try wipe and reflash and see if there will be an improvement

WOW! Nougat on a Five Year-Old Phone!
Thank you so much. You guys are amazing. I can't believe I'm running Android 7.1 on a five year-old phone. Everything works and is running pretty smooth (except for occasional red border flash).
As things turned out, my good old HTC One X has become my primary phone for the time being. And here I am running Nougat. I guess it says a lot about this phone's build quality that it has lasted so long. My deep appreciation to all the XDA developers and their amazing ROMs, apps and troubleshooting tips that have kept this phone, amazingly, at the forefront of Android development all these years.

Well, I couldn't wait. And the summary: I am thrilled
Here are some notes and observations, while installing lineage-14.1-20170226-UNOFFICIAL-evita.zip:
from within TWRP-3.0.N2-1, device always performs a full system-reboot when selecting "Reboot to Recovery". You have to reboot to fastboot (press-and-hold Vol-Down and Power), then enter recovery from the fastboot menu. Later, from within Lineage OS, you *CAN* reboot to Recovery.
cannot flash this ROM and nanoGapps queued together: insufficient memory. Flash this ROM first, then use TWRP file-manager to delete the ROM .zip. Now, there will be sufficient space to flash nanoGapps.
there are plenty of red-border-flashes during setup, and during regular operation It seems like just about every user-input-event, and maybe even every install-decision-point will produce this. It's actually slower than a "flash" - more like a red-border-blink I doesn't hurt anything, and I suspect this will be ironed-out later.
this ROM doesn't include 'su' (SuperUser). For this installation, I opted to use Lineage's 'addonsu-arm-signed.zip'
My roaming SIM won't work where I am now, but I have input my voip details into the provided dialer, and voip/SIP calls work as they should. I added Yahoo as a CM_WeatherProvider, and now cLock looks and works as expected.
a huge THANKS guys, for bringing this ROM to this point - @h8rift, @mdmower, @jrior001 !

Wow, guys this is great!
Thanks for the hard work.
What can we expect from this? Will it be patched to fix bugs or is this a "one build"?
Also, question for the devs: can one realistically hope to use Nougat on evita as a daily driver or is this device simply too old? I'm on CM12.1 and it's not that smooth. Would switching to Nougat better or worsen the experience?
For current testers: what features are currently working (camera, GPS, etc.)?
Again, hat's off!

Device Encryption busted
Device Encryption does not work.
(to be honest, this seems hit-or-miss with other LineageOS 14.1 ROMs; maybe even more "miss" than "hit" :-O . My Nexus 5 will encypt fine; my Nexus 7 (2012) won't).

Camera Works
I've attached an image OF YOUR QUESTION @Luxoboy to show that the camera works. The (exif??) data that I can see in the LineageOS Gallery app shows reasonable information too.
It doesn't seem to crash, nor have weird colors, for still-photos.
HTH,

WiFi stumbles a bit
OK... During setup, the first inkling of a rough-spot for WiFi showed up (for me): finding and displaying WiFi SSIDs took *forever*... Maybe I even skipped past that, and went back to set up WiFi access after the setup was finished and Lineage OS was fully running.
In actual hand's-on usage, I've found that the WiFi connection is both a bit weaker (fewer bars, doesn't reach as far) and lower-throughput than other devices. Both the 5GHz and 2.4GHz bands work; max throughput on 5GHz was 135Mb/s for me, right next to my 802.11n router (running DD-WRT). It's OK though.
Also during use, I sometimes noticed the WiFi icon, and the Settings -> WiFi progress indicating a drop + renew of the WiFi. Right now, my evita is at home while I'm at work - the phone is charging/sleeping but my Voice-Over-IP SIP provider site shows that the evita isn't registered... I suspect that WiFi isn't working, when it was during breakfast when I was playing with it...
The WiFi is certainly usable, but it does stumble a bit here-and-there, it appears.
Does anyone else experience the same, or something different with WiFi?

Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!

wildboarhog0 said:
Nice! thanks guys! The red flashing border and a little lag is
the only thing I see so far... This is awesome!
Click to expand...
Click to collapse
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1

worked like a charm! Thanks!

No More Red Flashing!
kuF3AR said:
You need to root device(install addonsu-arm-signed.zip from attachment) and then add 2 lines to the end of file /system/build.prop with any root file explorer and reboot it.
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
Click to expand...
Click to collapse
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.

shannester said:
Thanks, this fixed the red border flashing, and also has made the phone seem to run more smoothly. I already flashed the latest (2017) version of SuperSU when I flashed the ROM. I notice your attachment has a different version of SuperSU. Is there a difference between the version in your attachment vs. the latest one on the chainfire website. Thanks for your advice.
Click to expand...
Click to collapse
I found this file on the lineageos web site as approach to root their ROMs.

h8rift said:
LineageOS 14.1 is a free, community built distribution of Android 7.X (Nougat) which greatly extends the capabilities of your phone.
This is an unofficial build of LineageOS 14.1 for the AT&T HTC One XL.
To hear about the latest updates and changes to LineageOS as a whole, please follow +LineageOS on Google+!​
Installation Instructions (These are all required)
S-Off your device (Do this before RUU'ing and it will not wipe your /sdcard).
Update to 3.18 RUU or later.
BACK UP YOUR DATA TO A PC/OTG DRIVE. THIS WILL WIPE EVERYTHING
Flash a custom TWRP recovery that supports the EvitaX scheme and prepare your partitions. (Download from the downloads tab).
Boot to Recovery -> Wipe menu -> Advanced Wipe. Change /system to "FAT" format.
Reboot back into Recovery
Wipe Menu -> choose Format Data -> back to Wipe Menu -> manually wipe /system, /cache, /dalvik
Reboot back into Recovery.
Download the unofficial build from the downloads tab.
Locate 7.X ARM Nano Gapps via a quick Google search.
Install the build and GApps
Huge thanks:
mdmower and jrior001 for doing all the hard work.
XDA:DevDB Information
Lineage 14.1, ROM for the AT&T HTC One X
Contributors
h8rift, mdmower, jrior001
ROM OS Version: 7.x Nougat
ROM Firmware Required: 3.18
Version Information
Status: Testing
Created 2017-03-03
Last Updated 2017-03-03
Click to expand...
Click to collapse
One x or One XL? Can it work on both?
(My Device's SKU - 65383)

[ROM][7.1.2][Ovation][EMMC][UNOFFICIAL] LineageOS 14.1

You can find download under the "Downloads" tab on the top left of this thread / post.
Or you can find it at, https://forum.xda-developers.com/devdb/project/?id=22974#downloads
XDA:DevDB Information
[ROM][7.1.2][Ovation][EMMC][UNOFFICIAL] LineageOS 14.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
secretwolf98, LineageOS
Source Code: https://github.com/airend/android/tree/cm-14
ROM OS Version: 7.x Nougat
ROM Firmware Required: TWRP 3.1.1-0 and up
Based On: LineageOS
Version Information
Status: Stable
Current Stable Version: LineageOS 14.1
Stable Release Date: 2017-12-16
Created 2017-10-24
Last Updated 2017-10-24

Thanks again, i'm using it now and seems to work properly.

Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk

Nemesis1278 said:
Thanks again, i'm using it now and seems to work properly.
Click to expand...
Click to collapse
Your welcome

Tight Git said:
Downloaded and installed perfectly. Running fine - will update later.
Good job thanks
Sent from my BN NookHD+ using Tapatalk
Click to expand...
Click to collapse
Your welcome

Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!

BSAB said:
Hah, awesome, just dug the Nook up from a drawer and was wondering what to do with it, glad to see I can flash a proper updated OS!
Thanks for all your effort!
Click to expand...
Click to collapse
Your welcome.

Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.

sur4k said:
Really great work, thanks secretwolf98! Gave new life to my old Nook HD+, especially with some of my favorite apps starting to no longer support older Android versions. A few issues/questions:
How do I get root? I tried installing the official LineageOS addonsu-14.1-arm.zip as well as amaces' addonsu-14.1-arm-new.zip and they both fail in TWRP with
Code:
ApplyParsedPerms: lsetfilecon of /system/addon.d/51-addonsu.sh to u:object_r:system_file:s0 failed: Operation not supported on transport endpoint
Maybe related to the previous if it's an issue with the TWRP I have, but I couldn't find a TWRP 3.1.1-0 zip for Ovation so I just replaced the img in amaces TWRP 3.0.1-0 zip. Is there an actual 3.1.1-0 zip that this ROM requires?
When I select Power Off, my Nook reboots instead and I have to hold down the power button to get it to really shut off. Not a big deal since I rarely power off, but a strange bug.
Click to expand...
Click to collapse
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.

Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?

Nolfer said:
Hey I downloaded the twrp 3.1.1-0 from the official twrp site but it seems bugged, in that it doesn't read internal nor external storage. Where can I download a good version? Should I use a different version?
Click to expand...
Click to collapse
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.

secretwolf98 said:
Thanks, and your welcome. Install this version, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/239817874034
then install this, https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/file/185013076312
Make sure to install G-Apps before ROOT. I recommend, ARM | 7.1 | Pico, from, http://opengapps.org/
Then I recommend going into system and enabling ROOT. Then play around in the system for about 5 minutes. Do a reboot back into the system. Download, https://play.google.com/store/apps/details?id=com.joeykrim.rootcheck&hl=en
and make sure ROOT is working correctly. If it's working... Reboot into TWRP then wipe the 2 caches in advanced. Install my latest version, https://forum.xda-developers.com/devdb/project/dl/?id=27077
Then wipe the 2 caches again (said above), then reboot into system.... See if you have ROOT in "ROOT Checker". If you have any questions, don't be afraid to ask.
Click to expand...
Click to collapse
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?

sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
Yes, the latest one.

secretwolf98 said:
Use the latest ClockWorkMod here, https://forum.xda-developers.com/showthread.php?t=2062613
and install the ROM from there. I had this same problem with my first Nook HD.... I thought it was 100% Hard Bricked... But it is soft bricked. Nook's can get into soft bricks only. So I bought a new nook, and it runs better. The first Nook has been dropped so many times... After just using is for 30 seconds it felt like a oven. It was on stock... Until April-30-2016, after school I went to spend the night at my friend's house and then I used his computer to ROOT it. Bad idea only getting 30 minutes of sleep that night... Because I wanted to finish to install CM 10 on the Nook. Then a day or 2 later I installed CM 11. I was so tired on my birthday the next day. So I would say on May-9-2016 it did the same thing in the recovery like yours. I did own the Nook for like 5 years with stock.
Click to expand...
Click to collapse
I solved the problem adb flashing twrp 3.1.0-0 wich worked flawlessly.
I now have another problem. I cannot change the default cfq scheduler for internal storage. Every time I change it the tablet frezes and I have to manually reboot
---------- Post added at 01:35 PM ---------- Previous post was at 01:34 PM ----------
sur4k said:
I tried installing the linked ROM, then gapps, then the linked addonsu and still get the same error. I'm convinced my version of TWRP is the problem. Can I use CWM instead?
Click to expand...
Click to collapse
try flashing 3.1.0-0 TWRP
then go to developer options, disable root and then reenable for apps and adb. Reboot. Let me know

Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app

edsib1 said:
Just like to say thanks for all the work on this rom. My 4 year old Nook HD+ now does everything i need from a tablet
Sent from my SM-G935F using XDA-Developers Legacy app
Click to expand...
Click to collapse
Your welcome

so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!

zspeciman said:
so far so good, updated both my hd and my hd+, both running smooth. Great job secretwolf98 !!!
Click to expand...
Click to collapse
Thanks and your welcome

will not reboot, stuck at loading screen

xecutionkrk said:
will not reboot, stuck at loading screen
Click to expand...
Click to collapse
clean install, wipe everything, except where you have the ROM at.

[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...