Related
Overview
Codename Lungo is a customized, aftermarket firmware distribution for several Android devices. Based on CyanogenMod, Codename Lungo is designed to increase battery life and size over Android-based ROMs released by vendors and carriers.
Features
Great Base
Lightweight & Fast
No Bloatware!
Longer Battery Life
Custom Launcher
Add-ons
Community Driven
And so much more...
Screenshots
Changelog
Credits and Acknowledgments
check the Codename Lungo website
Links & Other info
Kernel: Stock CyanogenMod
Documentation & F.A.Q
Add-ons
Facebook & Google+!
Codename Lungo is a Community driven ROM! So we now have a Facebook Group and a Google+ Page & Community
Here you can post mods, new ideas or just chat about the ROM!
Enjoy and JOIN! Facebook Page | Google+
Download ROM!
@ Codename Lungo Website
XDA:DevDB Information
Codename Lungo , ROM for the Moto G
Contributors
TimV_
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: CM11
Beta Release Date: 2014-11-17
Created 2014-03-08
Last Updated 2015-01-15
One more
going to test now :good:
---------- Post added at 05:55 PM ---------- Previous post was at 05:42 PM ----------
everything is smooth and fluid i only use 335mb ram without gapps and every thing else works
:good:
Installed twice. In the first step (choosing language) it says "unfortunately, setup wizard has stopped", the screen goes black and I can only shut down or reboot, no more .
Thanks for your work! Let see if people has this problem too :good:
Feyerabend said:
Installed twice. In the first step (choosing language) it says "unfortunately, setup wizard has stopped", the screen goes black and I can only shut down or reboot, no more .
Thanks for your work! Let see if people has this problem too :good:
Click to expand...
Click to collapse
installed gapps before or after fist boot?
In the first install after the rom, as always. In the second install I flashed the rom without gapps to see what happen, and same result :/
Flashed it. As said above, there's a setup wizard problem that after picking a language it crashes the setup continuously.
I also got the gapps from your site for 4.4 for the best minimal experience with great performance
flashing the google dialer makes com.android.phone continously crash and have no service
I tried flashing w/o gapps and the setup comes again which is really weird, again it crashed
I then tried flashing w/o gapps again but this time formatted system (most install scripts format systems but some people forget to do it) and the setup didn't show up that time and was butter smooth.
After booting up w/o gapps, i tried flashing your gapps again, and it did flash. No setup wizard, though. But Google Settings and Play Store worked fine.
Also, would be nice if you could include AOSP browser, but i'm not sure if it fits the roms purpose(lightweight)
SamsungAdmire said:
Flashed it. As said above, there's a setup wizard problem that after picking a language it crashes the setup continuously.
I also got the gapps from your site for 4.4 for the best minimal experience with great performance
flashing the google dialer makes com.android.phone continously crash and have no service
I tried flashing w/o gapps and the setup comes again which is really weird, again it crashed
I then tried flashing w/o gapps again but this time formatted system (most install scripts format systems but some people forget to do it) and the setup didn't show up that time and was butter smooth.
After booting up w/o gapps, i tried flashing your gapps again, and it did flash. No setup wizard, though. But Google Settings and Play Store worked fine.
Also, would be nice if you could include AOSP browser, but i'm not sure if it fits the roms purpose(lightweight)
Click to expand...
Click to collapse
made a error while building the rom should be fixed now....
please, even in this rom, like cm11 the flip shell doesn't work when close? (no screen off)....
TimV_ said:
made a error while building the rom should be fixed now....
Click to expand...
Click to collapse
great! im gonna try it again in a bit :good::highfive:
Going to try this ROM when I will have time for it, thank you for your work.:good:
The problem persist :/
Indigoreli said:
The problem persist :/
Click to expand...
Click to collapse
Yep, again . Thanks for your work!
Feyerabend said:
Yep, again . Thanks for your work!
Click to expand...
Click to collapse
Wierd going to make a test flash on my nexus tablet to so if the problem exists there!
EDIT:
Did a install test run on my nexus tablet and getting no error here when i install the rom + gapps
here are the steps I did
1. Download latest build for my device
2. downloaded the 4.4.2_20140306_gapps
3 Placed it all on the SD Card
3. rebooted device in Recovery mode
4. did a Data/Factort reset
5. did a format /system (its in the Mounts and Storage Menu)
Installed the Rom and Rebooted the Device
6. Rebooted in to recovery mode
7. Installed the gapps
8. Rebooted Device
9. Everything is working fine..
If you still get a error then it's device specific... Than it's something I must do research on please let me know
Since this is official, shouldn't it be in Original Development?
Sent from my Moto G using XDA Premium 4 mobile app
YoshiShaPow said:
Since this is official, shouldn't it be in Original Development?
Sent from my Moto G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
CM is not official or is it?
That a custom ROM is official because is compiled by some DEV on that Custom ROM team does not mean this ROM has the requirements to get Original Developement Title.
More things than being official are needed in fact to get Original Developement custom ROM status.
Works !
TimV_ said:
Wierd going to make a test flash on my nexus tablet to so if the problem exists there!
EDIT:
Did a install test run on my nexus tablet and getting no error here when i install the rom + gapps
here are the steps I did
1. Download latest build for my device
2. downloaded the 4.4.2_20140306_gapps
3 Placed it all on the SD Card
3. rebooted device in Recovery mode
4. did a Data/Factort reset
5. did a format /system (its in the Mounts and Storage Menu)
Installed the Rom and Rebooted the Device
6. Rebooted in to recovery mode
7. Installed the gapps
8. Rebooted Device
9. Everything is working fine..
If you still get a error then it's device specific... Than it's something I must do research on please let me know
Click to expand...
Click to collapse
Confirmed on Tesco UK XT1032 - followed above and working fine...
Cheers
what about xt1033 compatibility??
XT3033
what about xt1033 compatibility??:fingers-crossed::fingers-crossed::fingers-crossed:
My device: HTC ONE MAX (International) , Rooted , TWRP Installed, Hboot 2.49
My Problem/q : whenever i try to flash custom roms that have a cyanogenmod 11 base such as the CrDroid or the AOSB or any rom that has a cyanogenmod base everything works perfect except that when the signals show after like 20 seconds i get "Android.process.phone has stopped error" twice and when i press OK the signals are gone.
Now keep in mind i did a Clean Full wipe Installation.
Someone please take a minute or two and help me with this problem i will be really grateful. thanks alot.
OneLessRoot said:
My device: HTC ONE MAX (International) , Rooted , TWRP Installed, Hboot 2.49
My Problem/q : whenever i try to flash custom roms that have a cyanogenmod 11 base such as the CrDroid or the AOSB or any rom that has a cyanogenmod base everything works perfect except that when the signals show after like 20 seconds i get "Android.process.phone has stopped error" twice and when i press OK the signals are gone.
Now keep in mind i did a Clean Full wipe Installation.
Someone please take a minute or two and help me with this problem i will be really grateful. thanks alot.
Click to expand...
Click to collapse
Thats a bug. Send the bug report to the rom developer. Mine bug on cm11 for moto g was that if the notification bar was filled with details of upcoming alarms the system.ui would force close as soon as i unlock the phone and that happened repeatedly.
Sent from my XT1033 using XDA Free mobile app
OneLessRoot said:
My device: HTC ONE MAX (International) , Rooted , TWRP Installed, Hboot 2.49
My Problem/q : whenever i try to flash custom roms that have a cyanogenmod 11 base such as the CrDroid or the AOSB or any rom that has a cyanogenmod base everything works perfect except that when the signals show after like 20 seconds i get "Android.process.phone has stopped error" twice and when i press OK the signals are gone.
Now keep in mind i did a Clean Full wipe Installation.
Someone please take a minute or two and help me with this problem i will be really grateful. thanks alot.
Click to expand...
Click to collapse
are you using the recovery version specified on CM website?
http://wiki.cyanogenmod.org/w/Install_CM_for_t6
yeah im on the latest TWRP and everything is fine in the roms i flash except for that i get the message "android.process.phone" has unfortunately stopped and then there is no service. this repeats over and over. service comes for 20-40 seconds and then i get the message and then it goes away
With a team effort from myself and @tdunham I'm back again with a completely stock build of Android TW-Lollipop 5.1.1 (N920PVPU1AOGD) for the Sprint Samsung Galaxy Note 5.. I built this stock pre-rooted ROM using the official Samsung tar ball. The ROM will self root upon flash and it has init.d/busybox support (when custom kernels support it). Knox and Sprint Itson has been removed completely. It is completely stock with all of the original factory installed apps as well as a few added features. This build contains a fully deodexed framework and system apps.
Other than the removal of Knox and Sprint Itson, it is stock in almost every other way. This first build is stock and will stay that way. I may make a custom rom later on. This ROM is intended for people who want the stock rom in it's original form with the addition of root and removal of Knox & itson, as well as other members who need a good solid base for their rom projects. I give permission for other dev's to use this rom as your base and I highly recommend that you do so because it is bug-free and built from the official Samsung tar ball. However I do expect proper credit if you use this rom for any other project. If you discover any issues please send me a PM as I may not continuously monitor this thread. If you like my work please press that Thanks button, rate this thread, and consider a kind donation! Enjoy!
About ROM:
Android 5.1.1 N920PVPU1AOGD_N920PSPT1AOGD_SPR
Stock N920PVPU1AOGD kernel (root-permissive) by: @Manh_IT
All factory installed apps including the Sprint Setup Wizard, etc are included. Nothing was removed except...
Knox and Sprint Itson removed.
Hotspot mod enabled
Added camera shutter sound option in camera settings
Added call/message block in settings
Enabled call recording from the phone dialer
Private mode works out of the box
That's about it... for now. This should be as close to the original rom as possible.
Known issue:
tx_dbs_tx said:
I just wanted to let people know that Sprint "ID" is causing Carrier Setup Wizard to fc as well as ID itself. This is a known issue and it is caused by Sprint "ID". I have not been able to successfully deodex it. The apk doesn't like to be deodexed. Until ID has an update through Google Play or Sprint Zone I will not be able to update it in the rom. Once there's an update to ID please send me a PM and I will update the rom. Until then you will have to delete or freeze Sprint "ID" to stop the fc's. Sorry for this inconvenience. It is out of my control at this time.
Click to expand...
Click to collapse
If you are currently on the stock unrooted rom:
You ONLY need to flash the latest TWRP recovery ( for the N920P ) using odin on your pc. Nothing else. Then flash this rom afterwards. The ROM zip will pre-root your phone as well as flash the stock root-permissive OGD kernel by @Manh_IT
Flashing instructions: ***Before beginning the flash/setup process MAKE SURE your battery has at least 50% charge and/or connected to the charger!!!***
1. Backup anything you don't want to lose off your internal device storage to another location just to be safe.
2. Download the rom using your pc. (downloading with your phone has a much higher risk of file corruption. Not recommended with large files).
3. VERIFY the md5!!! Once the download has finished, compare the AFH md5 using a md5 tool on your pc. (Google "md5 checksum windows").
4. Put the downloaded rom onto your internal storage..
5. With phone powered off, reboot into recovery by pressing and holding volume up, power and the home button until you see the Samsung logo then release all buttons.
6. Once in recovery choose the wipe button and do a factory reset three times. Optional but recommended is to wipe "Data". This will wipe all of your user data such as google accounts so MAKE SURE you backed up first like I said in step #1 above! Next go to "advanced wipe" and select all of the partitions EXCEPT internal storage. Wiping Internal storage is optional but recommended in certain circumstances. The reason is to remove left-over data from previous version of Android and start with a clean slate.
7. Choose the "Install" option and select the rom "Sprint_Hybrid_N920PSPT1AOGD" from your internal storage. It will flash the rom and give a confirmation once completed.
8. Press "Reboot" then "reboot system". You should get no prompts or warnings about not having root.
9. Initial rom "optimization" may take several minutes while ART builds its cache and the phone will remain on the yellow Sprint Spark screen for about 8 to 10 minutes. Let the phone optimize for at least 10 minutes and the screen WILL eventually turn off or show the setup wizard once it finishes. If the screen turns off then simply turn it on and proceed to setup your phone.
10. Once finished with the setup wizard, wait a few moments and the phone will automatically install the Sprint apps. (I know... nobody likes that suff!) You must either "accept" or "disagree" with each and every google prompt for these apps or else the installs pause until you do so.. That's it! You're done!
flashing anything on your device is done at your own risk. There is no way myself or any other developer can guarantee that flashing this ROM or any other file will not brick your device or otherwise cause some other type of damage. This is just a standard warning. I am not responsible for anything that you do to your device.
Credits:[CENTER @tdunham for his initial kitchen updater script and his willingness to work together with me so we could tag team the initial dev'ing and testing phase. I must say it was a pleasure!
the same awesome group of testers which also are credited in T's OGD ROM thread found HERE. @Team DevDigitel @Chaz187 @fsunoles101 @JoeyDuran @GAPO @rlmiller @sml2004
Special thanks to: @Beastmode Brian for providing the updated google apk's i needed. Thanks a lot man!
If somebody was left out please let me know!
[/CENTER]
DOWNLOADSprint Stock N920PSPT1AOGD DeodexedEnjoy!!!.
XDA:DevDB Information
Sprint_Hybrid_N920PSPT1AOGD, ROM for the Sprint Samsung Galaxy Note5
Contributors
tx_dbs_tx, @tdunham @Team DevDigitel
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.10.x
ROM Firmware Required: N920PSPT1AOGD
Based On: N920PVPU1AOGD_N920PSPT1AOGD_N920PVPU1AOGD_HOME.tar
Version Information
Status: Stable
Stable Release Date: 2015-09-06
Created 2015-09-03
Last Updated 2015-09-09
Mods
N920PVPU1AOGD_Odexed-Deodexed_Hotspot_Mod
(can be flashed on odexed or deodexed OGD roms. the script will remove appropriate odex files automatically)
Reserved
Nice man congrats on the release..... Glad to see sprint getting some love! !!!!
You moved over to the 5, Sweet!!!!!?
Ok, now I really need root!
The mans in the house thanks bro
Sent from my SM-N920P using XDA Premium HD app
So glad to see develpment starting to move along. Thank you so much for this. Awesome job.
Sent from my SM-N920P using Tapatalk
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
pbedard said:
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
I just slammed my brake when I say this. I'll till this issue is resolved.
pbedard said:
Rom doesnt get passed the sprint boot screen waitied 15 minutes it just randomly rebooted
Sent from my SM-N920P using XDA Premium HD app
Click to expand...
Click to collapse
Did u download the ROM on ur phone? If so, u still have to verify the MD5. One thing about DBS ROMs is a completely clean slate is best. I would re-download the ROM on computer the verify and move to internal storage. U have a backup to go to JIC?
M2Iceman said:
You moved over to the 5, Sweet!!!!!?
Ok, now I really need root!
Click to expand...
Click to collapse
No I don't have the Note 5. I was invited to come help with the new stock base rom and thisis simply my own version with everything left in the rom and is hybrid odexed/deodexed.
Can somebody please download, verify md5 and test flash for me. I need to make sure there's not a problem with the rom. I need a comfirmation from a couple of people wether you successfully boot or not. Thank you.
tx_dbs_tx said:
No I don't have the Note 5. I was invited to come help with the new stock base rom and thisis simply my own version with everything left in the rom and is hybrid odexed/deodexed.
Can somebody please download, verify md5 and test flash for me. I need to make sure there's not a problem with the rom. I need a comfirmation from a couple of people wether you successfully boot or not. Thank you.
Click to expand...
Click to collapse
The md5 matched, but I'm also getting a failed boot at the spark screen. sits on it for a good 10 minutes, reboots, then does it again.
Do you care if i use this as a base? Gonna go through and pull bloat for the lazys and reup it.. credits due of course for your orginial work. Lmk
Thanks for the build. Gonna run in as soon as the dl finishes
So being that this is odex and deodexed and some system apps aren't deodexed, will xposed work with this rom?
tx_dbs_tx , Original poster is correct, flashed 3 times 3 dls, no go,, same result long wait on spark logo, random reboot and restarts again, wont fully boot as is
Team DevDigitel said:
Do you care if i use this as a base? Gonna go through and pull bloat for the lazys and reup it.. credits due of course for your orginial work. Lmk
Thanks for the build. Gonna run in as soon as the dl finishes
Click to expand...
Click to collapse
Hit me up on Hangouts if you can. [email protected]
If you have time you can help me test to find the problem. I can tell you exactly what to do to find the cause and you won't have to re-download the rom.
Sorry about this people. I don't have the Note 5 so I couldn't flash & test this build which is based off of our original test roms which are good to go. I made some changes, updated some framework files and re-uploaded this version and it's not booting. In the meantime I have to pull the download/link until i find and fix the problem. If anyone can help me test the rom, please contact me on google hangouts using my email address above. Thank you.
tx_dbs_tx said:
Hit me up on Hangouts if you can. [email protected]
If you have time you can help me test to find the problem. I can tell you exactly what to do to find the cause and you won't have to re-download the rom.
Sorry about this people. I don't have the Note 5 so I couldn't flash & test this build which is based off of our original test roms which are good to go. I made some changes, updated some framework files and re-uploaded this version and it's not booting. In the meantime I have to pull the download/link until i find and fix the problem. If anyone can help me test the rom, please contact me on google hangouts using my email address above. Thank you.
Click to expand...
Click to collapse
Any way to get that kernel? I think the Noble kernel is crashing my phone. Sprint Note 5
My is crashing. Every time i use hotspot
Jordan011 said:
Any way to get that kernel? I think the Noble kernel is crashing my phone. Sprint Note 5
Click to expand...
Click to collapse
A couple of people are currently working on the stock OGD root-permissive kernel. When they release it for testing or final build, i will include it in the rom. However I don't think the current kernel is the problem.
I sent an invite but I can't test until tomorrow I left my damn computer at work. But if you ever need some one to test something let me know, I'll gladly risk my device! Haha
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