Unofficial Resurrection Remix v7.0.2 PIE unified for Oneplus3/3T
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
About:
This ROM is just an update to Official RR-v7.0.2 Pie. It integrates latest security patches, bugfixes and features from LineageOS and Google.
Oneplus3 RR development was stopped, so I decided to build own ROM that incorporates latest updates just to be safe.
This ROM is functionally equal to the original RR, no bloatware added, no applications replaced.
I don't want to switch to Android 10 yet, because of BETA version of GAPPS, missing face unlock and early stage of development in general.
I want to stay with Android 9 for next few months, until Android 10 gets stabilized.
Next updates will be posted monthly (to provide latest security updates) or if any serious bug is found.
I expect that I'll be maintaining this build for at least next 3-6 months. I want to see where Android 10 development goes.
This ROM was made for my own usage, but I wanted to share my work results with you if somebody is interested.
All credits goes to official authors of RR, LineageOS and FraEgg, Mady51. I picked their changes to make this ROM complete and up to date.
Features:
Functionally equal with RR-7.0.2 Pie
Based on latest AOSP, LineageOS
Updated kernel (OmniPie)
Various bug/stability fixes
ChangeLog:
https://github.com/obeny/platform_manifest/blob/pie/ChangeLog
Prerequisites:
https://forum.xda-developers.com/oneplus-3/how-to/op3-flashable-firmware-modem-zips-t3816066
https://sourceforge.net/projects/op...en_gapps-arm64-9.0-nano-20200117.zip/download
https://dl.twrp.me/oneplus3/twrp-3.3.1-1-oneplus3.img.html
Installation:
WARNING:
You have to perform clean install when switching from any other ROM, including Official RR.
If you want to preserve face unlock feature, DO NOT install opengapps newer than 20200117
First time installation:
Unlock your bootloader
Install latest Oxygen OS firmware
Flash recovery zip (TWRP)
Reboot into TWRP Recovery
Wipe all data
Flash latest ROM
Flash Open GApps
Optional: Flash Magisk
Reboot and enjoy
OTA App update installation (auto):
Go to Settings > Advanced > Updater
Press reload button (right corner)
Select download on the new build list
After download select update/flash new build
Reboot and enjoy
Download:
RR-P-v7.0.2-20200416
RR-P-v7.0.2-20200416 md5sum
Staging versions:
Older versions:
RR-P-v7.0.2-20200315
RR-P-v7.0.2-20200209
RR-P-v7.0.2-20200119
Special thanks to Teams:
This build is just a integration of great work done by:
LineageOS team: https://www.lineageos.org
RR Team: https://www.resurrectionremix.com
TheMuppets: (https://github.com/TheMuppets)
Mady51: (https://github.com/mady51/OmniPie)
FraEgg: (https://github.com/FraEgg)
and all the supporters.
Contributors
obeny
Source Code: https://github.com/obeny
Kernel Code: https://github.com/obeny/OmniPie
Local Manifests: https://github.com/obeny/rr_op3_local_manifests
ROM OS Version: 9.x Pie
ROM Kernel: Linux 3.18
ROM Firmware Required: 9.0.5
Based On: RR, LineageOS, Resurrection Remix, AOSP, LuisROM
Version Information:
Status: Stable
Created: 2019 Dec 26
Last Updated: 2020 April 6
Hello. I just installed your "unofficial" update. All is working great. Thank you so much for doing this! Dziekujemy!
I'm glad to hear that! You're welcome I'm happy that this build could be useful for others.
Going to try this. been running the june Official RR update, but having sound problems (different issues on 2 phones). Update modem/firmware, wipe, and install this, will see if it helps!
Please, let me know about the results. Maybe we can debug the problem somehow. I have no problems on my phone, everything works as expected. Have you got any hw changes? Was your mobile serviced?
What about Luis version, I mean why are you building an other RR Pie, just curious.
Well, thing is simple. I prepared this build for myself, it was shared if somebody looks for something similar. I wanted to be independent from anybody. I cannot foresee if there will be new version and when maintenance will be stopped.
Thanks to Luis, some of the repos are taken from his github (e.g. android_frameworks_base).
My build is almost vanilla RR without any customizations, reworks - only updates and bugfixes, nothing else. Some of updates are missing in Luis ROM, so I integrated them.
I'm planning to merge some missing features from Los, that are not yet integrated in both Luis and mine builds.
Moreover I wanted to get some practice with android before starting work on porting RR to android ten, if there will be no official support. I'm not planning to change the device soon, so I want to have guaranteed support
I was on OOS 9.0.6, wiped all and formatted data, rebooted recovery (on latest official TWRP recovery), now when I try to flash this ROM, it end up with E1001: Failed to update system image. Tried flashing latest firmware again, still same.
Format everything, system, data, cache. Most probably you forgot to format system partition.
obeny said:
Format everything, system, data, cache. Most probably you forgot to format system partition.
Click to expand...
Click to collapse
Thanks Oneny, I tried it twice with wiping everything and formatting data, but same error, now tried flashing Havoc 3.0 and it worked just fine, no idea what's wrong with it.
I've switched back from HavocOS 3.0 to RR Pie. I had few problems:
- Google Pay do not work (even if Magisk says that basic integrity and cts profile are ok)
- Face Unlock is unavailable (maybe related to the beta version of Gapps)
- Phone stops ringing after 0.1s, only vibrates (couldn't find the reason)
- Terrible battery drain
I gave up after 3 re-flash attempts and moved back to RR which works like a charm.
@obeney thanks for this build. Works great so far.
One question: does the LTE quick setting do anything? In other ROMs it would turn off LTE network mode.
obeny said:
Please, let me know about the results. Maybe we can debug the problem somehow. I have no problems on my phone, everything works as expected. Have you got any hw changes? Was your mobile serviced?
Click to expand...
Click to collapse
The problems were on the official RR rom. After switching to yours, my bluetooth problem went away (phone forced "dual channel" mode, causing garbled audio or no audio with some speakers/headsets, had to select stereo in developer options after each connect), but I'm still not getting notifications playing. sometimes the first 1/2 second of the sound is played, then cut off. The rest of the time, silence. I'm using the stock notification sound, so it's not something I've added on that front. I'm not expecting any serious instability, I had no problem doing 700+ hours uptime on official RR.
I plan to bring another phone to this rom this weekend. It has the same notification cutoff problem, no bluetooth issue, and some audio problems (can't hear calls from main earpiece speaker). I'll follow up if that clears up, but I'm thinking that's probably a HW problem. No servicing here, both phones were new in box 3T.
ROM is good stuff, thank you for putting it together!
Edit: It seems that the Notifications are playing now mostly, and get cut off more often when the phone has been in sleep for a while.
obeny said:
I've switched back from HavocOS 3.0 to RR Pie. I had few problems:
- Google Pay do not work (even if Magisk says that basic integrity and cts profile are ok)
- Face Unlock is unavailable (maybe related to the beta version of Gapps)
- Phone stops ringing after 0.1s, only vibrates (couldn't find the reason)
- Terrible battery drain
I gave up after 3 re-flash attempts and moved back to RR which works like a charm.
Click to expand...
Click to collapse
I'm on Luis build for now, it flashed fine on same recovery, your build is not working for me for some reason ?
mrfrantastic said:
@obeney thanks for this build. Works great so far.
One question: does the LTE quick setting do anything? In other ROMs it would turn off LTE network mode.
Click to expand...
Click to collapse
Just checked that and it seems it is always on, no matter whether it was triggered or not. I never used this option and didn't know that it even exists
Was this LTE switch working on Official RR pie?
Should I take a look into it to fix that?
obeny said:
Just checked that and it seems it is always on, no matter whether it was triggered or not. I never used this option and didn't know that it even exists
Was this LTE switch working on Official RR pie?
Should I take a look into it to fix that?
Click to expand...
Click to collapse
I just tried Luis' build before and it didn't work there either. I guess it is not that important so you don't have to put in the work just for me.
If enough people also request it you could maybe think about it . But I will survive without it
airtel volte works?anybody plz confirm volte is imp for me this is the only thing stopping me from using custome roms.
Does the VoWifi feature, work by default on this ROM ?
I want to use Jio VoWifi (India) on my OnePlus 3.
obeny said:
I've switched back from HavocOS 3.0 to RR Pie. I had few problems:
- Google Pay do not work (even if Magisk says that basic integrity and cts profile are ok)
- Face Unlock is unavailable (maybe related to the beta version of Gapps)
- Phone stops ringing after 0.1s, only vibrates (couldn't find the reason)
- Terrible battery drain
I gave up after 3 re-flash attempts and moved back to RR which works like a charm.
Click to expand...
Click to collapse
Did you reflash the FW before downgrading to Pie?
Try it and see if it´s different In the HAVOC 3.0 installation notes, it was specified the FW´s reinstallation before reflashing Pie ROM
BTW It was announced that encryption is fixed in the last HAVOC 3.1 build! (I didn´t test it )
Code:
HAVOC OS 3.1
Device Changelog:
• Fixed SafetyNet
• Fixed Encryption
• Updated blobs to 9.0.6
Bump.
Updated build:
http://obeny.net/RR-oneplus3/rr-pie/RR-P-v7.0.2-20200118-oneplus3-Unofficial.zip
Merged latest LineageOS and google changes.
Updated kernel.
Security level is now 2020 January.
Update available through the Updater under: Settings->System->Advanced->Updater
Related
As was my plan all along, kltevzw official support for AOSP roms is picking up. Please see this thread for official downloads and support:
http://forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
My builds will cease.
-- Begin copy-pasta template from my CM13.0 build thread... please let me know if I miss updating something --
Note: I don't run this ROM personally, I really just built it. It shouldn't, but it may eat your cat.
Code:
*** Disclamer
-- You install these at your own risk! You are responsible for anything that happens from flashing these files to YOUR phone! If your
phone melts into a pile of goo, catches on fire etc. IT IS NOT MY RESPONSIBILTY BUT YOURS!
FAQ:
Q: Can I use this?
A: Do you have a developer aboot? If so then yes, but I won't help you install a developer aboot. I only ever had a Developer phone, so I only know the process as well as reading the thread. See this thread for info/help: HERE
Q: When/how often are these built?
A: Less often than my CM13.0 build, but at least every week. Unlike my CM13.0 build, I don't use this ROM so I won't be doing a "does it boot" check before uploading. Please tell the entire thread if one day's build doesn't work properly.
Q: Can I get help with something?
A: I have a full-time job and travel a lot. I'll try to jump in and answer some questions, but there is a lot of info out there for you to learn on your own. Aside from you having a vzw-variant, most of the details are standard KLTE. Please see the normal Resurrection Remix KLTE thread for standard ROM help.
Click to expand...
Click to collapse
Recovery:
The standard KLTE TWRP 3.1.0-0 should mostly work, but MTP doesn't work for any klte* variant using it.
I prefer KToonsez's 2.8.6-based Recovery. It's older, but MTP works.
There are Unofficial 3.*.0-* recoveries available by @jcadduono. I find that these don't support decryption properly, which I find to be mandatory.
Like many other devices, the .zip files can be flashed in a recovery. The .tar.md5 files can be flashed in ODIN. The .img files can be flashed using Flashify, a TWRP recovery. You can even get an .img file from a .zip or .tar.md5 if you just open it up.
If you use adopted storage then things get odd. The latest recovery by @jcadduono MAY support adopted storage if you don't encrypt userdata (I personally know that TWRP handles adopted storage for jflte and d2), but I do use encryption so I don't use that recovery. It may be that you only see /data/media/0 -- if so, I find that using Flashify for each nightly is the most straightforward way to update, but you could always manually copy to /data/media/0 before rebooting to recovery. This is a standard Marshmallow and TWRP thing.
Click to expand...
Click to collapse
Modem/Firmware:
Most of the LP modem/firmwares should work, but I use the one PB1 here. This modem matches with the proprietary vendor files that are part of the build. Flash it in ODIN. Please note that some have reported that you cannot flash these after the aboot unlock; If you cannot flash the PB1 modem/non-hlos it shouldn't cause any big problems.
https://www.androidfilehost.com/?fid=24459283995308895
Click to expand...
Click to collapse
GApps:
Resurrection Remix recommends SlimGapps or OpenGapps. See their thread for discussion of pros/cons and what those users tend to use. If you use OpenGapps, make sure to use an 6.0 version for ARM architecture.
OpenGapps
SlimGapps
Click to expand...
Click to collapse
Downloads (the thing you were looking for):
I'll build at least once per week, at least until the RR team picks up the torch. Once the build is complete, I upload it to my AFH account.
ResurrectionRemix-M v5.6.X KLTEVZW weekly-ish
Click to expand...
Click to collapse
Does/Doesn't Work:
Everyone that gives it a shot needs to let the thread know. See the Unified Resurrection Remix thread for discussion of what generally does/doesn't work with the ROM.
forum.xda-developers.com/galaxy-s5/unified-development/rom-ressurrection-remix-mm-t3275340
Click to expand...
Click to collapse
Thanks:
Everyone on the Resurrection Remix and CM teams. This is 99% of their stuff with just a couple tweaks to make it build, (hopefully) boot, and run for KLTEVZW. See Post 2 for those changes.
Click to expand...
Click to collapse
Android Version: 6.0.1_r22 (prior to 20160406 build)
Android Version: 6.0.1_r24 (20160406-present build)
I forgot something. I know I did. I'll try to update this post sometime.
More things...
Source
In order of importance:
Resurrection Remix github: https://github.com/ResurrectionRemix
Cyanogenmod github: https://github.com/cyanogenmod
My github: https://github.com/haggertk
Click to expand...
Click to collapse
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
tbclandot said:
Wow man you work hard want me to flash this and give you results/impressions? I was just resetting up your CM13 on my S5 and voila RR XD you the man!
Click to expand...
Click to collapse
Someone needs to be the guinea pig. I know how much a pain it can be setting a ROM up from a clean install, but if CM feels just a bit too vanilla then I'd say jump into the pool.
Alright going to download and flash it now and I will report back to you thanks for your hard work!
---------- Post added at 01:06 AM ---------- Previous post was at 12:35 AM ----------
Hagg flashed the rom and everything seems to be working so far I can make calls and receive texts I prefer RR to CM13 for the features! Just wish there was a way to get my Gear S to connect to non Touchwiz roms but oh well I'll just use it as a regular watch or maybe get an AW watch lol
Running CM13, what's different?
Hmmm extra features to be honest I like CM13 but it's so boring and as a guy that actually likes Touchwiz RR is nice because of the added customization!
So I've for RR installed. Few things I noticed right away: Built in ad-away, nice! Uses super-su. I personally have no issue with the built in root, but whatever. Other than that, it's very close to CM13 in terms of speed and look/feel.
Edit: One weird glitch I've run into on both this and CM13 is that the camera app gives and error "gallery has stopped working" when launched from the icon. If i used the double power button though, then the icon starts working. Any ideas?
Edit2 : It seems to be the default camera icon that is on the home screen in both ROMS. I noticed the graphic is slightly different from the dock as it is in the app window. Deleted bad icon and replaced with app windows one and it works fine. Probably an easy fix!
No glitches, no forced closes. Everything works, and works smooth. Very nice. My new daily driver.
Unlocked and loaded RR with OpenGApps..
No issues...running great!!
Thanks!!
Will try later, thanks haggertk for your work...
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
drewcu said:
Just turned my S5 into DEV last night but do not want the Bluetooth and wifi bugs of CM13 so...
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
4) Does Xposed work?
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
Thanks!
Drew
Click to expand...
Click to collapse
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
tbclandot said:
drewcu I'll try to answer your questions as I'm running this rom flawlessly!
1. Haven't noticed any bugs
2. This is 6.0.1 Android M with a March 1 security patch
3. Fingerprint reader works better than stock Touchwiz lol
4. Xposed works I'm running v23
5. Probably need the PB1 modem not sure on that actually
6. not sure
7. Roms are limited right now because the retail VZW bootloader was just unlocked be patient I'm sure many devs are working on roms
Click to expand...
Click to collapse
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
drewcu said:
Guessing the "6. not sure" was in response to the Front Speaker question and not the Upgrade question, so how difficult is it to reinstall all apps using Titanium Backup or something similar? Or is there a way to upgrade without having to reinstall apps?
Front speaker doesn't work out of the box in RR, right? (where a patch isn't necessary)
Thanks for all your feedback!
Drew
Click to expand...
Click to collapse
No idea on the speaker as I don't mess with it usually use headphones and I don't really use T backup but I don't see why you should have problems but you'll probably want to clean wipe when installing
drewcu
1) Are there major bugs present in RR like those in CM13 (Bluetooth, wifi)?
Not that i notice
2) To be clear, is RR Marshmallow 6.0.1 as well (might be helpful to state the Android version explicitly somewhere for us newbies to custom ROMs)? I know CM13 is mentioned in different places and 6.0 is mentioned in the GApps section, but I don't see the Android version like on the RR Changelog (ResurrectionRemix - v5.6.5 - 20160313 #Marshmallow 6.0.1_r22).
6.01
3) Are there S5 functions that won't work with RR like the fingerprint reader or is it pretty flawless?
Work great
4) Does Xposed work?
Yes
5) If I am coming from KK stock 4.4.4 NK1, do I need to do something special with the Modem as discussed in the OP such as somehow flashing the PB1 Modem?
I advice to flash PB1 firmware no botloader
6) I am betting I have to wipe my S5 clean before flashing this ROM, but is it reasonably painless to restore all my apps and settings with Titanium Backup?
Yes, system, data, cache and dalvik, but dont restore system apps nor system settings
7) Is there a patch for RR to make the front speaker work when playing music similar to a patch I found on KK that does? Love that functionality and don't want to lose it.
Dont know
8) Are there other Marshmallow S5 Dev ROMS besides CM13 and RR or are these the best options right now?
At this time not yet
Every time I attempt to download, it fails after 55kb.....
amaury48 said:
Every time I attempt to download, it fails after 55kb.....
Click to expand...
Click to collapse
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
haggertk said:
Maybe one of the mirrors is messed up -- have you tried forcing the download mirror to other locations?
Click to expand...
Click to collapse
Finally got it by switching browsers.....
Would one of you on RR be so kind as to send me the mixer_paths.xml (if that's what it's still called in MM) in your System > Etc folder (assuming folder structure is the same in MM also)? I would like to compare it to the surround sound modded file I installed in KK as per the following link: http://www.naldotech.com/enable-stereo-surround-sound-speakers-galaxy-s5. I am probably not technically capable of making the same thing possible in MM with the S5 front speaker, but it's entirely possible the same modded file I have will work in MM and it's possible a comparison will reveal only a few lines of code to modify that I could do.
Thanks in advance!
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
NOUGAT 7.1
DOWNLOAD WEEKLY
CURRENT ISSUES ON OFFICIAL:
1. Encryption is broken
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm8952/tree/android-7.1
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][N][7.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-06
Last Updated 2017-06-11
reserved
New WEEKLY build released. This build contains rootless theme support through substratum (downloadable from the playstore)
The issues posted in op are still present?
yes they are, those issues mainly relate to sonyxperiadev project, which is the base of the bring-up of Xperia X Compact on omni.
The issues need to be resolved there, then they will also be resolved for omni
oshmoun said:
XC/KUGO/F5321 OmniROM BUILDS
NOUGAT 7.1
DOWNLOAD WEEKLY
CURRENT ISSUES ON OFFICIAL:
1. Incall speaker volume is not controllable
2. Slight incall echo on receiving side
3. Double tap to wake doesn't work
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-7.1
BUGS REPORT
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
CHANGELOG:
https://changelog.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
[/CENTER]
XDA:DevDB Information
[ROM][XC][N][7.1][WEEKLY]OmniROM, ROM for the Sony Xperia X Compact
Contributors
oshmoun
Source Code: https://github.com/omnirom
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Version Information
Status: Stable
Created 2017-03-06
Last Updated 2017-03-06
Click to expand...
Click to collapse
screenshot Please
eymentuna said:
screenshot Please
Click to expand...
Click to collapse
Ok i will add some screenshots when possible, but please don't quote the first post next time
Flashed your rom yesterday. I got the same problem as with the aosp rom, my x compact frequently loses mobile network connection. Today I had no connection for several hours. Had to reboot 4 times to gain network connection. Though I don't know if the restarts fixed it. Plus I often only have hspa or 3g connection, this is strange. This doesn't happen on 7.0 or earlier ROMs.
Micka84 said:
Flashed your rom yesterday. I got the same problem as with the aosp rom, my x compact frequently loses mobile network connection. Today I had no connection for several hours. Had to reboot 4 times to gain network connection. Though I don't know if the restarts fixed it. Plus I often only have hspa or 3g connection, this is strange. This doesn't happen on 7.0 or earlier ROMs.
Click to expand...
Click to collapse
Maybe you have your APN settings setup incorrectly?
Other than that, this rom does not replace the modem partition so that should be the same as on stock. Not sure where your issue would come from if not from APN
Thank you I will take a look at the apn settings (didn't ever change anything there though)
flashed your ROM but i find that the two big cores frequently turned off which is causing lags
it might be something wrong with the interactive governor I guess
jeremy.wang said:
flashed your ROM but i find that the two big cores frequently turned off which is causing lags
it might be something wrong with the interactive governor I guess
Click to expand...
Click to collapse
That doesn't seem wrong. The big cores will only go online if they're needed. They stay offline most of the time. That still shouldn't cause stuttering though.
Just checked here and big cores go online on high cpu loads as expected.
Is F2FS supported? I didn't see it listed anywhere and the changelog link in the op just loads the Omni homepage.
TadMSTR said:
Is F2FS supported? I didn't see it listed anywhere and the changelog link in the op just loads the Omni homepage.
Click to expand...
Click to collapse
F2fs is not supported, because fstab is explicitly requiring ext4 partitions.
oshmoun said:
F2fs is not supported, because fstab is explicitly requiring ext4 partitions.
Click to expand...
Click to collapse
Is F2FS something you could add without too much difficulty? I use it with some Nexus 7 2012 and Asus TF201 tablets and it appears to make a difference. Not sure how noticeable it would be on the XC though. I completely understand if adding F2FS support is not something you want to focus your time on.
Thanks for your work on this rom. I get my XC in the mail tomorrow and I'll be loading Omni pretty soon after.
TadMSTR said:
Is F2FS something you could add without too much difficulty? I use it with some Nexus 7 2012 and Asus TF201 tablets and it appears to make a difference. Not sure how noticeable it would be on the XC though. I completely understand if adding F2FS support is not something you want to focus your time on.
Thanks for your work on this rom. I get my XC in the mail tomorrow and I'll be loading Omni pretty soon after.
Click to expand...
Click to collapse
Honestly i haven't checked if it's feasible or not. Main issue is that this is my daily driver so i can't experiment with it to such levels.
I'd suggest you setup your device on omni, then maybe i can upload a custom build with f2fs support for you to build. Assuming f2fs is possible on XC of course, which is something I'll check soon
Got Omni loaded and was trying out encryption. It kept boot looping. On one of the loops I briefly saw the Omni logo. All the other times just the Sony boot screen, the LED would light blue/purple then turn red as the phone restarted. I know setting up encryption will cause several reboots but this didn't seem to be working correctly. Does Omni on the XC support encryption currently?
TadMSTR said:
Got Omni loaded and was trying out encryption. It kept boot looping. On one of the loops I briefly saw the Omni logo. All the other times just the Sony boot screen, the LED would light blue/purple then turn red as the phone restarted. I know setting up encryption will cause several reboots but this didn't seem to be working correctly. Does Omni on the XC support encryption currently?
Click to expand...
Click to collapse
Hmmm, haven't tested encryption.
Can you try booting to twrp to see if that at least works? That way we know the issue does not lie in the kernel
oshmoun said:
Hmmm, haven't tested encryption.
Can you try booting to twrp to see if that at least works? That way we know the issue does not lie in the kernel
Click to expand...
Click to collapse
Yea twrp works. Had to go into recovery to restore my backup. It appears the encryption process did start as the first restore had the boot loops. It was only after I formatted the data partition that the restore worked and I could boot back into Omni without issue. I do have Magisk installed for systemless root so not sure if that is part of the problem. The next time I try I'll remove Magisk first.
Update: Did some searching and it looks like Magisk might be the cause. Some people have reported that encrypting the device before putting Magisk on works.
Update 2: Did a clean install of Omni after formatting all partitions. Still getting the boot loops so Magisk wasn't the cause. Some boots only have the Sony logo. Other timers the Omni logo does appear but then it restarts.
TadMSTR said:
Yea twrp works. Had to go into recovery to restore my backup. It appears the encryption process did start as the first restore had the boot loops. It was only after I formatted the data partition that the restore worked and I could boot back into Omni without issue. I do have Magisk installed for systemless root so not sure if that is part of the problem. The next time I try I'll remove Magisk first.
Update: Did some searching and it looks like Magisk might be the cause. Some people have reported that encrypting the device before putting Magisk on works.
Update 2: Did a clean install of Omni after formatting all partitions. Still getting the boot loops so Magisk wasn't the cause. Some boots only have the Sony logo. Other timers the Omni logo does appear but then it restarts.
Click to expand...
Click to collapse
Please do the following:
1. Boot up device after trying to encrypt
2. After device crashes at start and reboots, directly boot up twrp with volume buttons
3. Using adb, get all files under/sys/fs/pstore and upload
I hope they was understandable, and thanks for investing time in this
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...
Originally, this was thread was centered on the LineageOS 17 GSI by AndyYan, however, CodeF86 has so very generously made a working GSI for the Moto G6 which you can try out now!
Unlike AndyYan's generic GSI, for this you do NOT need to flash johnaltg1's LineageOS 16 image (if you do, this GSI will NOT boot). It is recommended you use stock Pie firmware. Oreo firmware has not been tested and may result in bugs.
Download here—Compiled Feb 22nd, w/ working LTE!
See CodyF86's thread post
Some notes:
Unlike the generic GSI, calling works.
Also unlike the GSI, the colors don't invert randomly.
Magisk DOES NOT work at the moment, neither phhuson's nor regular Magisk. Flashing it will cause a bootloop.
Bluetooth audio has been reported to not work
As with many Android 10 GSIs/ROMs, Chrome freezes or crashes because GApps packages currently are missing the new Trichrome WebView implementation which replaces Chrome as the default WebView. This being worked on (see OpenGApps wiki and issue #773 on their GitHub.) For now, use another browser (like LineageOS's default browser) if you install GApps. —As soon as Trichrome is added onto the ARM package just as it has for ARM64, Chrome should be stable.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient! If you see any bugs, report them here.
Extremely huge shoutout to CodyF86 for this GSI!
The developer of this ROM has moved on to another phone and the community now has a full fledged 64-bit ROM which has much better support for things.
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. Things may break randomly, whoops, so please be patient!
Click to expand...
Click to collapse
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
everything works for me
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
so you can make phone calls without WIFI conection?
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
yesssss
xda4joe said:
Just to reiterate, you are stipulating that this pre-release build doesn't permit me to make an outgoing phone call (nor possibly receive any) unless connected to a WiFi network? Please pardon my not-so-subtle-sarcasm ... but, why would anyone release this with a bug (or limitation) which inhibits the core functionality of the device? I could see a million other issues being permissible but not being able to make normal phone calls (or possibly even receive them) doesn't warrant any kind of release for testing. That being said, I'd be happy to help if possible and eagerly await a usable version of Android 10 to put on my Moto G6 which I only got a month ago (happily unlocked at a great price on Amazon). However, it is (currently) my main phone for making calls.
Click to expand...
Click to collapse
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
taiyofurukawa said:
everything works for me
Click to expand...
Click to collapse
xavcasgar said:
so you can make phone calls without WIFI conection?
Click to expand...
Click to collapse
taiyofurukawa said:
yesssss
Click to expand...
Click to collapse
How? What is your modem version/phone model?
Can't Boot
AgentICS said:
The LineageOS 17 GSI works great on the Moto G6. There are some caveats however for anyone willing to try it:
You MUST first flash the LineageOS 16.0 ROM first or else you will bootloop.
Use this Magisk from phhuson's official GitHub
Your screen may change colors and look weird, when this happens, go to Settings > Display > LiveDisplay> Color mode and change it to the value under the value selected on the menu and then back to the original one and that should fix it
If you flash GApps before first boot, follow AndyYan's suggestions as the Setup Wizard is broken for some reason on most GApps packages.
Calling while not on WiFi is broken for now.
Bluetooth is horribly broken for now, it causes the app playing audio to lag and crash so please stay away from it.
Chrome is wonky at the moment. It'll work and then all of a sudden cause the whole OS to lag and crash or become unresponsive. This is possibly an upstream GApps issue.
For now, that's all I can think of. However, if you notice any other bugs or caveats, let me know so I can add it to the list.
This is a GSI based on phhuson's prereleased GSI work and also based on the prereleased LineageOS 17. This is a pre-release so please be careful and don't use this as a daily driver. Things may break randomly, whoops, so please be patient!
I am documenting everything on here. Stay tuned to that page for more info and further updates. Addiotionally, I have filed a bug report regarding calling, please add on to that GitHub issue and bump it so it can get resolved.
Click to expand...
Click to collapse
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
SomeAndrodGuyWithInternet said:
Ok, so I installed and flashed Lineage 16 first. Then I flashed Lineage 17 GSI in system img, but then when I did that I go into twrp and it said an os was not installed and wouldn't boot. But if I just flash Lineage 16 it would boot. Am I doing something wrong?
Click to expand...
Click to collapse
First off, are you unzipping the file? The standalone uncompressed file is unflashable. It needs to be decompressed from it's .gz (or whatever it was compressed to) form. If you have, have you tried using fastboot flash system <lineage file name> from a PC?
AgentICS said:
It is pre-release so not all the bugs are ironed out, I should have added that this should not be used on your daily driver. But yes, it's dumb to use a phone that can't make calls without WiFi. Just as a note, you can make and receive calls however if you're not using WiFi, the caller can't hear you. I have filed a bug upstream with phhusson as this affects every GSI built using his work (Pixel Experience, Lineage and AOSP which I've tested). I hope this gets fixed soon so stay tuned to that GitHub issue
Click to expand...
Click to collapse
Just wanted to jump in here and say I'm seeing same bug on xt1925-6 with callers not able to hear me on any 10 gsi's and speakerphone does not work at all. Phh aosp 10 build 209 with stock pie 55-37-7-2 boot vendor boots fine, other gsi's will only boot using the Ali lineage full ROM boot- vendor but call audio is broken as well. Thanks for submitting the bug report, hopefully it will get fixed in future builds.
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
CodyF86 said:
Hello friends,
It's been a while since i've posted on XDA. I was the person who originally rooted the g6 play. I managed to build a GSI image of 17.1 with the latest code as of today if anyone is interested I can upload it to gdrive or something, didn't feel like making a new thread.
It boots, mobile calls work, dark mode works (which is amazing), it all seems to work.
Getting it to compile was just short of a miracle...lol.
Only bad thing is I cannot get it to boot with any version of magisk even the version specifically for phh / Android 10, but with just the stock kernel with the ,verify removed it boots fine.
Click to expand...
Click to collapse
That's amazing! Could you upload it please so I can test it?
Thank you!
AgentICS said:
That's amazing! Could you upload it please so I can test it?
Thank you!
Click to expand...
Click to collapse
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
CodyF86 said:
GSI-Lineage-17.1-2-16-2020-system.img
It seems it only connects at 3g although it lists a different apn server on lineage, I may be able to fix that, and I couldnt get the sd card to format as anything but adaptive storage, but everything works more or less. going to recompile in a week its still pretty early in development stage of lineage.
Click to expand...
Click to collapse
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
AgentICS said:
Huge thanks for this GSI!!! I've been using it and it works flawlessly, I have also observed that only 3G works for now but regardless of that, everything works fine.
Again, I can't reiterate enough how thankful I am with you for this GSI!
Click to expand...
Click to collapse
May have a fix for LTE compiling it now, using the stock apn file with the adjusted mcc mnc numbers.
If I could get root I could get it for sure, but I can't get it to boot with a magisk flashed kernel, even the android 10 special version of magisk.
I got LTE but now mobile network stays disconnected although there is an LTE connection. It's an apn issue will work on it. if I get it working will make a thread...not sure why magisk won't work with my builds / kernel though yet.
https://github.com/codyf86
I've noticed that restarting always restarts to the bootloader. I don't know if it's just me but that's weird
Could you provide a link to the kernel source used in the rom?
Uclydde said:
Could you provide a link to the kernel source used in the rom?
Click to expand...
Click to collapse
It's on his GitHub
The kernel is actually just the stock kernel from the latest firmware with the ',verity' flag hexedited out to disable encryption. (You also need to change the fstab that is in all the guides ever made including my original one), but I'm working on building the kernel and making it work...but I got LTE to woooooork with some changes to the stock apn file lineage provides ! lol.
Only thing now is that it thinks my external sd card is corrupted and wont format right unless i set it to adaptive storage, so make a backup of your external sd card for now. Going to try using TWRP to format it with a couple different file systems.
Here she is boys.
Lineage-17.1-02.22.20-treble-arm-system
Still working on getting it to boost with magisk not sure why it won't when it was fine in Pie.
Still playing with the apn file the apn its using says sprint ehrpd but not sure what makes it pick which apns to show on the screen, but the apn is set to x.boost.ispsn which makes LTE work. I'll clean it up soon.
(All of this is assuming you're on Boost / Sprint)