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.
Related
Hey guys,
So here is a straight from source build of Android L, 5.0. I have not done anything beside build it from source and flash it. I have not done extensive testing on it.
So anyways, here is the link:
http://d-h.st/zi0
I have not included gapps or anything else. They will be coming soon. This build is primarily to play around with. I would not consider this a daily driver.
Issues:
Probably a ton, seeing as I have only checked if it boots.
I am not responsible for any issues this may cause or anything else that may happen to your tablet as a result of this.
I also have a ton of schoolwork and other things that keep popping up, so my support may be iffy. Please bear with me or go back to 4.4.4.
Here is a screenshot for proof:
https://www.dropbox.com/s/lnmhdapeemskggi/1743495_10153594576754572_4551962379003400239_n.jpg?dl=0
Future Plans for this Rom:
GApps are not yet possible on Lollipop as far as I can work out, due to the fact that baksmali and smali do not appear to play nicely with ART odex files. I will be rebuild the rom to be odexed and then including a gapps package.
XDA:DevDB Information
[Android 5.0] Straight from source ROM, ROM for the Nexus 7
Contributors
MidnightNinja
Version Information
Status: Testing
Created 2014-11-05
Last Updated 2014-11-04
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
cchant said:
Tried to adb side load and am getting No OS error. Will restore and try again on device
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm..let me know if you still have issues, because I was able to sideload on my device
Awesome!!
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Niekhout02 said:
When first booted you need to erase it because it is encrypted. But after that it works (for now) like a charm. Wifi working, sound working.
The only problem so far is that after I installed the Play Store it didn't want to open but the Amazon app store works fine.
Click to expand...
Click to collapse
I am missing alot of the google stuff, which is probably why none of that works
That will come shortly, I just need to redo a lot of my vendor files and such to get gapps to be built in.
It worked even though it said no OS
first boot takes awhile but it works!
Confirmed it works.
Sideloading gapps for cyanogenmod 11 and hoping they auto update does not work. Worth a shot though. Time to reflash.
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Working great! I think performance is even better than kitkat
Wi-Fi also working (maybe bluetooth, nfc and gps too)
StardustGeass said:
Woah, thanks a lot
Btw, how do I sideload gapps? (especially play store)
Since I think it won't be just installing apk, isn't it?
Click to expand...
Click to collapse
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
tatazeuz said:
Flashing GApps is the solution. Sadly, there isn't a package for Lollipop GApps yet.
Click to expand...
Click to collapse
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
MidnightNinja said:
I am currently working on the gapps, right now i have fixed my own build process and am getting a nexus 9 dump to try and fix it up.
Click to expand...
Click to collapse
Yay!
Works great, now waiting for gapps
thanks
Gapps mostly work fine if you edit updater.script
I've only had issue with the keyboard crashing so I'd suggest removing it from the gapps package before flashing.
Woah
I can't wait for the final version, this one, using 4.4.4 binaries, is crazy smooth. Google outdid theirselves on the optimization department.
Awesome work, think im gonna givebthis a try atbwork tomorrow.
What does work and what doesn't
basuraunak said:
What does work and what doesn't
Click to expand...
Click to collapse
So far, everything seems to be working. Have to check camera yet though.
I cant seem to get much else to go with it, but I will share my findings.
I can get TWRP to install,but then I get a bootloop.
If you use the Nexus Root Toolkit v 1.9.3 and "Root" with custom recovery checked. It freezes after trying to temporarily boot the modified boot image.
Hard reset the tablet and boot normally. The toolkit should reboot your tablet back into the bootloader and into TWRP, but this is only good for one boot.
If you mount /system and run a fix permissions, then it stays installed, but never gets past the boot screen.
It boots far enough to get into ADB.
Not sure what to try next though...
I was thinking if we could get a flashable zip without the stock recovery, then we may be able to keep TWRP, but I am not familiarwith building the flashable zips.
Wait, So how do you flash the google play services after you lose TWRP?! I don't understand..
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)
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.
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
beta 2 uploaded
dt2w works, bluetooth audio works, camcorder works.
wifi still partially broke and is a wip. after that its on to lineage os 15 for the h631
wifi works now and the end? of lineage 14.1 dev is here. everything seems to work now
release 1 is posted in the op.
Awesome work! I've finally got me a full featured daily driver
I still got my OG Stylo lying around somewhere. Guess I'll give this ROM a try...
After attempting to reboot after installing, I got a "Kernel Crash!" error. Now my Wi-Fi won't work after restoring a Nandroid backup. Good thing the OG Stylo isn't my primary phone, anymore.
EDIT: I just realized Bluetooth is busted, too.
EDIT 2: After reading from sources outside of XDA, the firmware should have definitely been on v20k before flashing this. Oh well. I might check into attempting to fix the issues, one day.
But ever since I moved on to the OnePlus 5, I only use the OG Stylo as an alarm clock. As long as that still functions, at least it won't end up in the dumpster.
Gave this ROM a go. VERY pleased! WiFi had a hiccup but now working. I can connect to Bluetooth but can not hear audio. Any others come across this? I'm on the metro version of the Stylo.
Thanks in advance.
Z
Sent from my LG-H631 using Tapatalk
I have a MS631 (MetroPCS).
S/W : MS63120p
Is it possible to install and any plan to post Official Release (14.1 or 15 later)?
Thanks..
This is cool... hoping to get a Google-less minimal fernsprecher going, but this time (compared to your other 14.1 build) I can't see any providers-- just 'error while searching for networks.' Now I'm guessing the reason is the same in both cases-- I started from wrong official ROM. Can anyone point to a 63120k kdz? All the old links I found yet are dead
ed: Tried to prove to myself that a kdz was even useful. I have a few wrong kdz sitting around still-- 10j, 20b, 20l. LG Flash Tool wouldn't actually change anything, ever, no matter what. ("Consult your system administrator". Well, he's me... baka.) And LGUP looked like it was doing great the first time, right up until it gave me back a shiny brick (QHSUSB__BULK), so ...maybe later?
:: phasepalm ::
ed-2: found https://lg-firmwares.com/lg-ms631-firmwares/ so now all I have to do is get QFIL to do anything.
I love this OS. I removed the Nexus launcher and installed the new pixel 2 launcher in its place though. Every now and again I have to disconnect and reconnect Bluetooth. But that's not really a problem for me. WiFi sometimes drops but reconnect. I can't wait for the new lineage OS.
Any update?
pnaralove said:
Any update?
Click to expand...
Click to collapse
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Revenant Ghost said:
Nope, because the OP's phone was destroyed.
On another note: I was also able to get my OG Stylo up and running again with LG Bridge yesterday, with the latest official update (Marshmallow). I might try this ROM again, one day.
Click to expand...
Click to collapse
Thank you for the reponse
Please let me know how it is after you try this ROM.
won't boot all the way through, logcat without complete boo
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
Hello, everything seems to be fine but it won't boot all the way through. Also I am still a noob and am wondering how to get a logcat without being able to get all the way into the operating system? Any help would be appreciated
whoshotjr2006 said:
Release 1 is posted.
READ THIS BEFORE PROCEEDING: I took all the latest updates and was sitting on v20k before I flashed the zip I compiled. I dont know if you have to be, but dont be surprised if things dont work if you arent where I am with your phone.
******************************Start of dev stuff************************************************************
kernel sources based off of LG K10 devs msm8916 caf kernel sources (since its basically the same device) here:
https://github.com/touchpro/android_kernel_lge_msm8916
all the device and vendor trees are based off of teamregular's/LG K10 devs work:
h631: https://github.com/touchpro/android_device_lge_h631
msm8916-common: https://github.com/touchpro/android_device_lge_msm8916-common-lineageos14
vendor: https://github.com/touchpro/android_vendor_lge-lineageos14.1
*********************End of dev stuff*********************************************************************
Feel free to create other custom roms based on the trees above!
I would recommend using my TWRP 3.2.0-0 here to flash it: https://androidforums.com/threads/update-twrp-3-2-0-built-from-source-12-8-17.1103219/
what works:
everything as far as I can tell
The rom zip:
https://androidfilehost.com/?fid=746010030569947653
gapps: http://opengapps.org/ (choose your package to fit your needs. just choose arm and 7.1)
THIS DOESNT COME STOCK WITH SU!
Download it here: https://download.lineageos.org/extras
(choose the option for su (arm) and 14.1)
If you wish to report a bug:
Please give a detailed report of what the bug is, things that could possibly cause it (xposed, magisk, etc) and a logcat that was running while the bug occurred. This means you may have to do things to make the bug occur.
adb logcat > log.txt
And finally, ENJOY!
Click to expand...
Click to collapse
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
gameplayerdo2 said:
hi, me again.. I finally got my phone back to totally stock from the LG Bridge. How do I get the v20 K that you were sitting on to try and get lineage on my phone now at this point. Thanks in advance
Click to expand...
Click to collapse
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
derpendicular said:
Like I said, I finally found https://lg-firmwares.com/lg-ms631-firmwares/ and v20k is on there but no promises unless you can find the known good MD5 hash somewhere. I couldn't just try it because again, this ms631 is bricked in 9008-mode.
Click to expand...
Click to collapse
Hey there I got it. What I did was I hooked up to LG Bridge and let LG do the repair from the upgrade repair button and it got my phone back to square one which was fine. From there i unlocked the bootloader and booted from TWRP 2.8.7.1 image file and then once inside TWRP I installed version TWRP 3.2.0-0 recovery from the zip file. At that point I then was able to do an advanced wipe and wipe out the system and then do the lineage install from there. Once that worked I wiped it out and installed CyanogenMod just to see if it will go on as well and it did. So I went back and wipe that out and put the lineage OS back on there with the opengapps and it's running flawlessly! I also installed magisk to root it and everything is running fine. The only thing I miss from the LG part of the software was the knock on knock off feature. And I downloaded a tap on tap off app for that but you can't use any other locks with it. but I'm good, and thanks! Because I hated that stock operating system with all the bloatware even though MetroPCS didn't have as much garbage as the T-Mobile or other versions but still now I can control Play Store and everything else. I in fact use APK pure to get most of my apps if I can find the software there.
Hey I got my LG g Stylo and might use it again with lineage on it. I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
elwhiteboy01 said:
I need to understand you're flashing a nougat custom rom over a mm stock room and it works? Also, I have 20o and in reading I see 20k is the requirement? Hope to hear feedback, thanks in advance. And can anybody tell me how they got twrp 3.0.2 on the stylo? I can't seem to do it with an unlocked bootloader via adb.
Click to expand...
Click to collapse
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
derpendicular said:
Your best bet is (very likely) to back up stuff and wipe it all out. I use SMS Backup Restore, manually export contacts, copy the files to SD, etc. Then to answer your other question-- root using apk from Kingroot.net which works but it loses root every time you reboot. So before you do, you can use Flashify to flash TWRP onto recovery, also run TitaniumBackup once and put everything on SD card. Then with TWRP running you could install SuperSU zip onto the stock rom and it actually sticks, but you would (make yet another backup and) wipe the phone before starting fresh with Lineage and then restoring your stuff piecewise. That was last year, though, might have forgotten something. Like it's hard to remember but I *think* you can skip the Kingroot & Flashify routine altogether, just reboot to fastboot and on the computer 'fastboot boot twrp-x.x.x.x.img' to boot it once-- even though it won't flash it directly. Then 'adb push twrp-x.x.x.x.img /sdcard' and then inside TWRP, flash it using [Install Image] under [Install] instead of the usual zip file. HTH
Click to expand...
Click to collapse
The phone is bricked now. I did a fastboot boot twrp and installed magisk zip. Then installed flashify and flashed twrp image. Then formatted data and installed the lineage os and it didn't go through. I was in a hurry so I didn't backup the stock ROM. And so I pulled the battery and put it in download mode and flashed kdz. And when it finished the screen went black and shows no signs of life no matter what I do.
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?