Related
Q&A for [ROM][5.1.1] Candy 5 - Skyrocket
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.1.1] Candy 5 - Skyrocket. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Anaya Boom said:
hello
I changed my i727 to 5 candy lollipop , everything works except that appeals nobody hears me and I hear nothing
Here are the notes from phone
baseband i727ucmc1
Version 3.0.101 CyanogenMod - g0c7bddd
uMTS network
state service
current service
Homelessness: Homelessness without
state of the mobile network : offline
thank you for your answer
i have installed rom from sd card after wipe data and partitions
___________________________________________________________
new:
that's it, after two reboot it works; but I'm waiting still the problem will return, I install once "kitkat bluelighting 4.4.4" and "Slim-skyrocket - 4.4.4.build.6 - OFFICIAL-5252" "
everything worked very well
Thank you
Click to expand...
Click to collapse
This is a problem with most 5.1 roms. Mostly after using another audio app like hangouts phone,whatsapp phone,music players and video players. Driver is not released back too phone.Reboot is needed . On a good note, Paranoid Android 5.1.1 has just come out with an update and an audio patch that fixed mine. Hope this helps.
I don't get any signal
My phone after updating it to candy 5(5.1 Lollipop) I can't get any signal?
Please Help!
New to this
This is the best rom I have installed ever since fixing my bricked Skyrocket a couple weeks ago.
Latest Version 5/15:
After installing the latest update the data drops far less frequently... however it is still a good five times every twenty minutes or when I send two or more text messages. I tried rebooting, messing with wifi/airplane mode, removing excess APN's, and using Signal Boosters which are junk. Folders seem to be a bit different and overall rom is a bit more laggy compared to previous version. My recents menu did not work, holding the home button with no response, fixed by turning on OmniSwitch.
Installing SlipLP fixed the data, so I am confident you will figure it out for Candy! If only I digged the look of SlimLP.
Will report back next update, still learning how to Logcat... I will post if I figure it out tonight.
I am not getting any charging or heat issues like the poster above. I did not change to noop prior to writing this.
Found a PERMANENT signal fix!
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
requiredhq said:
Apparently this has something to do with the radio being flashed and 5.x.
Here is how you fix it, I have not had one drop in signal since my previous post!
(For AT&T, T-Mobile, possibly others)
1. Download the [UCMC1] I717 AT&T Radio
http://d-h.st/PKI
- official thread: http://forum.xda-developers.com/showthread.php?t=2228292
2. Either Clean flash or Recover from a backup of Candy 5.x
3. Install the AT&T Radio
Signal drop is fixed, select your APN and enjoy!
I suggest this for those who are using AT&T Servers, T-Mobile, or etc. If not visit here and find your carrier radio... http://forum.xda-developers.com/showthread.php?t=1785999
I hope this helps everybody! :good::fingers-crossed:
I am not a professional, I have been flashing custom for a couple years here and there! This is working on my device, I now have ZERO signal drops and perfect signal, please allow OP to further test.
Click to expand...
Click to collapse
Thanks, yes the UCMC1 radio or newer is needed for this. It is one of the last versions available for the Skyrocket. My Slim threads have this but I didn't see that mentioned here, so I have updated the OP.
Cheers!
Preinstalled App
Does this ROM has Apollo music player installed?
Hunter661 said:
Does this ROM has Apollo music player installed?
Click to expand...
Click to collapse
It has CM's Eleven music player. You can install whatever you want, Google Music, XenoAmp, etc.
GAPPS
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Candy 5 v2.5.3 onto skyrocket I727 as well as I727R)
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Twisterboy669 said:
Everything is working on my Skyrocket SGH-I727R but when I want to install gapps from my recovery it says it successful but I can't find google play when I installed the zip. Do I need to use a different GAPPS file?
Click to expand...
Click to collapse
Michel177 said:
tried to update from v2.5.1 .Got Google play bug .
Then did a full wipe and installed on both units with slim Gapps .No more chance .same error .When back to prvious version from restore .
Should we be able to update from the previous 5.1.1 buid v2.5.1 ?
Thanks
Click to expand...
Click to collapse
Make sure you are using an up-to-date version of GApps. Recommended is Slim's Zero GApps (~60MB), a link to which you can find in the OP.
Google Cards
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Minor Question
How would you update the 2.53 version to this one?
Twisterboy669 said:
The google now widget I can't find under the widgets tab is their anyway to retrieve it?
Click to expand...
Click to collapse
When you flash the ROM, either the GApps package you flash needs Google Now (might be Google Search, not sure), or you need to install it from the Play Store separately. Voice input on the AOSP/Google keyboards may be missing as well until you do.
I partitioned my Skyrocket to have a 6GB Data partition so the tiny GApps is fine and I can install pretty much all I want for apps. It's quite nice.
Twisterboy669 said:
How would you update the 2.53 version to this one?
Click to expand...
Click to collapse
Wipe Dalvik and Cache in recovery
Make a nandroid backup
Flash the ROM
Flash either Slim Zero GApps or a very small base GApps package
Reboot
Have fun!
Flashing Potential Issue
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Twisterboy669 said:
I am currently Flashing the ROM using TWRP and everything seems good it's just that its stock on "Patching system unconditionally" It's been on that step for about ten minutes. I did the Cache and Dalvick Cache wipes. So I Don't know what I did wrong.
Click to expand...
Click to collapse
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
NoSpamDan said:
Then it sounds like there were core changes which may require a full wipe (/data or a factory reset).
I normally clean flash to test, so unless I've made a change that I know requires a full wipe, or coming from another version (5.0 vs. 5.1, etc.) I would suggest to try dirty first and see. If you get stuck, as you have, then I'd go clean.
Sorry for any inconvenience...
Click to expand...
Click to collapse
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Twisterboy669 said:
When I down graded bak to 2.5.3 It flashed perfectly. So do I just wait for the next update or is their a solution because none of the methods you mentioned to me are working. I backed up my data and did a full factory reset.
Click to expand...
Click to collapse
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
NoSpamDan said:
Have you wiped /system in the process?
Have you formatted your device with ODIN using a PIT file, or have you used any virtual partitioning?
Post your recovery log. You can export it from TWRP.
Click to expand...
Click to collapse
Nvm, Sorry I forgot about the dirty flashing and it worked. Thank you
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)
This is a list of Nougat ROMs for this device and it's clones.
The list will be in the following format:
ROM : Version : Device : Tested/Untested
LineageOS : 14.1 : MMXC5 / E481 : Untested
Resurrection Remix : 5.8.4 : MMXC5 / E481 : Tested
crDROID : v3.5 : MMXC5 / E481 : Tested
AOSGPX : 7.1.2 : MMXC5 / E481 : Untested
There are also ROMs for the Elephone P8000, however the first time I tried one I got into a bootloop. It could just have been that I didn't wipe my caches, or it could have been a fault in the ROM; nonetheless I haven't tried any others from that device.
I couldn't find any for other devices, let me know if you see others.
Here is the factory firmware, as according to this post (Direct Download).
Also, the stock recovery: Original Post | Direct Download.
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
elbastardo1 said:
Im currently running crDroid and I couldn't be happier. Runs far better than the original firmware and the useless marshmallow update.
Click to expand...
Click to collapse
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
BereiBlue said:
Have you encountered any bugs with crDroid? Did screen on time and standby increase by any good margin because doze and other os optimizations? With stock I get 7hrs SOT with LTE half the day. 5hrs if Skype calls and such.
Click to expand...
Click to collapse
Only bug so far is the kill app button not working (long press the back button) and sometimes after reboot sim cards not being detected. Usually it corrects itself after a few minutes. If not, I'll just re-flash the fix
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
elbastardo1 said:
Only bug so far is the kill app button... and sometimes after reboot sim cards not being detected...
Battery gets drained pretty fast compared to lollipop, but then again I used lollipop with xposed, greenify and amplify.
Click to expand...
Click to collapse
Happy to hear only minor bugs. I'm waiting on black Friday SD card to ship and then I'll be able to test too.
On lollipop all I needed to use was power nap to kill unwanted wake locks. I'll definitely try to get it to work because batter life is important to me. Only reason I'm upgrading is because of older exploits that stock didn't get updates for. Other than that stock with xposed is extremely stable for me.(30-60 days between reboots)
Do you know if crDroid is using stock lollipop kernel or is it a ported kernel? That would effect battery life greatly I suppose.
review of roms
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me a part of this rom was made by another group of people that were not given credit.. Default browser loads the homepage of the other group. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
BereiBlue said:
Review time. Installed and tested these roms by wiping dalvik cache, system, data, cache and internal storage. Flashed ROM then gapps then "front camera flash" patch lastly flashed sim patch. Afterwards I wiped cache and dalvik cache again before rebooting. Once I had access to settings I disabled display live/night mode/blue filter for all ROMs.
All the roms tested used about 1GB of ram (and stock ROM being around <600MB.).
Resurrection Remix : 5.8.4 : Looks to me this was made by some Russians. Default browser loads RU homepage. The system FM radio app was asking for root permission(denied it). Also it had email services running before I added any accounts can't remember this being the norm. Other than that this ROM ran the best in terms of speed and ui. Uninstalled because of security concerns.
LineageOS : 14.1 : This ROM has about the same speed as resurrection which is good but the ui stuttered/not smooth. Uninstalled because ported by same user as resurrection.
crDROID : v3.5 : This one ran the worse. It was slow and stuttered throughout the ui. Missed some customizations that Resurrection had so not sure why any one would want to use this instead.
AOSGPX : Didn't bother installing because last I heard they copied and pasted code from crDRoid.
At the end of the day I reverted back to stock because of security concerns. As well as having more ram available for apps. If I had more than one phone phone I would wireshark/test connections of the ROMs to confirm but I do not have. Hopfully this helps someone.
Click to expand...
Click to collapse
Just wondering with the ROM testing, did you disable the LiveDisplay nonsense? It drops my FPS to about 10, and is enabled by default.
Sorry, didn't read your whole post. I didn't find UI stuttering unless I enabled weird kernel stuff, or had L Speed installed.
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
tinpanalley said:
Does anyone happen to know if any of these ROMs fix the problem that the official MM caused which was that all camera apps created a very dark image and took extremely dark photos?
Click to expand...
Click to collapse
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
elbastardo1 said:
Im using crDroid and yes, it fixes it. That is one of the main reasons why I decided to keep it and got rid of Marshmallow.
Click to expand...
Click to collapse
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
tinpanalley said:
Hmm... sounds good. Any issues with that ROM? Slow downs, wonky USB port, minijack works ok, etc?
Click to expand...
Click to collapse
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
elbastardo1 said:
sucktastic battery life (not like the original firmware was good to begin with) no compass (gmaps will point north regardless of your orientation) as soon as you install the google app (okay google!) the device will run a bit slower.
Click to expand...
Click to collapse
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
tinpanalley said:
Oh, ok... well in that case, that doesn't exactly help things. I'm gonna go back to Lollipop rooted to take out the bloatware. Can you recommend a way of doing that that is known to work well?
Click to expand...
Click to collapse
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
elbastardo1 said:
SP flash tool, scatter file and the original firmware (not a flashable zip). It's all in the original BLOX thread, buried somewhere there. Flash TWRP recovery using adb fastboot and flash super su with twrp recovery for root access.
Click to expand...
Click to collapse
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
tinpanalley said:
Wow, thorough, thanks. Don't know what half those things are but I'll look them up. I guess there's no way to go straight back to Lollipop without flashing a stock ROM. I mean, by rooting it now maybe and then downgrading or something?
Click to expand...
Click to collapse
You could flash a lollipop twrp backup, if anyone uploaded one or if you made one before. But if you don't have it, only way is by sp flash tool and original firmware (which is not a recovery flashable zip).
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Teblakuda4o4 said:
Been using the Crdroid rom for a few weeks now. Havn't had any lag or extreme battery issues. Im interested in trying the resurrection remix rom since it was tested to be the fastest, tho them security issues are kinda holding me back. One thing im lookin for is front camera flash and back aswell. on Crdroid u cannot toggle it in the camera app, tho the flash works.
Click to expand...
Click to collapse
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
tinpanalley said:
What are these security issues people are mentioning? Isn't a ROM a ROM? I don't get it.
Also, if crDroid works fine, you could just try any other camera app. There are several that are quite good. I wish there were videos of crDroid.
Click to expand...
Click to collapse
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Teblakuda4o4 said:
I mean with what's going on with Kaspersky being investigated for allowing certain trogens to work undetected and Kaspersky is own by Russians and since when does fm radio need root access.
Just a bit sketchy you know... But it could be just over-thinking it.
Click to expand...
Click to collapse
I'd just not use the radio. [emoji4]
tinpanalley said:
I'd just not use the radio. [emoji4]
Click to expand...
Click to collapse
But the thing is you don't know what else has been tampered with.
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...