CyanogenMod is a free, community built distribution of Android which greatly extends the capabilities of your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* CyanogenMod members or anyone else on this website is
* not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the
* alarm app failed. Please do some research if you have
* any concerns about features included in the products
* you find here before flashing it! YOU are choosing to
* make these modifications, and if you point the finger
* at us for messing up your device, we will laugh at you.
* Your warranty will be void if you tamper with any part
* of your device / software.
*/
This is a nightly build of CM for the LG G3 on Sprint (ls990).
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review.
If you want to help out follow the building guide and then submit a patch to our Gerrit instance.
Installation Instructions:
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery *TWRP* for "ls990”.
1. Download this ROM and 6.0 GApps (recommended Open GApps here). You are going to need to use the Marshmallow ones, this is 6.0)
2. Put both on Internal Storage
3. Reboot into recovery
4. BACKUP CURRENT ROM
5. Factory Reset/Wipe if not already on CM13
6. Flash CM13 (no need to wipe System)
7. Flash GApps 6.0
8. Reboot
9. wait... wait... wait...
10. Profit
To get root/SU, enable Developer Options and change "Root Access" options.
Nightly builds *http://get.cm/?device=ls990.*
Working:
Almost everything
Known issues:
Bluetooth for some users
NFC – not working at the moment
??? - list any others and I will try to get them working as I have time
@invisiblek does most of the work for this device series, much more credit goes to him than me, I just focus on the ls990.
CyanogenMod Blog
CyanogenMod Wiki
CyanogenMod Community
CyanogenMod Forums
CyanogenMod Google+
CM Download Page for ls990
Been on this for a month, and it's without a doubt more stable than anything else I've tried on MM. Some things don't work, like NFC, but they don't work on any current rom. It never shuts down randomly like others I've tried and keep up with. Nice job. I'll take stability over glitchy features every time.
Got No SIM Card detected on this build, trust its because of baseband version.
Has anyone got CM13 and CM12 baseband dumps?
Any solution to No SIM Card?
Been trying official build since they came out, cannot get LTE. Only 3G. I am on ringplus if it helps.. I am on newest lollipop baseband from zvc. Tried editing apn.config xml, airplane mode, changing network modes. All I get is 3G. I did find by flashing an apn fix for ringplus I get lte but for carrier it says Digital roaming instead of aprint.. Is it my device or is it the rom?
Lte works fine on stock lg roms. Everytime i flash TOT back to stock i have to do an rtn reset to get lte back though it gets stuck on 3g. Did clean flash btw every nightly wiping internal,system, data dalvik and cache
Disillusioned said:
Got No SIM Card detected on this build, trust its because of baseband version.
Has anyone got CM13 and CM12 baseband dumps?
Any solution to No SIM Card?
Click to expand...
Click to collapse
Try to do a full wipe and flash again. I haven't had any problems with it detecting my SIM. Worst case flash to stock ensure everything works and then flash back to CM.
allanlgz said:
Been trying official build since they came out, cannot get LTE. Only 3G. I am on ringplus if it helps.. I am on newest lollipop baseband from zvc. Tried editing apn.config xml, airplane mode, changing network modes. All I get is 3G. I did find by flashing an apn fix for ringplus I get lte but for carrier it says Digital roaming instead of aprint.. Is it my device or is it the rom?
Lte works fine on stock lg roms. Everytime i flash TOT back to stock i have to do an rtn reset to get lte back though it gets stuck on 3g. Did clean flash btw every nightly wiping internal,system, data dalvik and cache
Click to expand...
Click to collapse
In general mine stays on Domestic Roaming but that depends on how you are connected to the network. Every once in a while mine will show Sprint. Also you don't need to wipe prior to flashing nightlies unless you are experiencing issues.
Been flashing the nightlies since day one of release, and this by far the most stable, fast, overall amazing MM rom I've seen. Smooth as silk even with the stock kernel
flashed last nightly, almost all apps force close, rom is unusable, flashed twice. And no GSM signal
jesus.sea said:
flashed last nightly, almost all apps force close, rom is unusable, flashed twice. And no GSM signal
Click to expand...
Click to collapse
are you sure you have a LS990?
syndre said:
are you sure you have a LS990?
Click to expand...
Click to collapse
Yep!, it was my bad, i was coming from fulmics and had adaptive storage enabled, that was causing the force closes, i guess a problem with teh encryption, just set to forget the storage and everything was OK with the apps.
For the signal issue i had to flash the GSM patch and worked again.
i'm on LS990 using GSM Network on Mexico
Really enjoying the ROM. Thanks for this.
One question... I'm on sprint ls990 and my data speeds have dropped. Considerably. Is there a fix for this, or something I didn't do on my end when flashing? Thanks.
Great ROM! No issues with nightly updates at all. Best ROM I have used on this phone..clean flashed with bumpd TWRP...looking forward to new updates..Thanks!!
Are there any running issue for those using this ROM on the current build besides whats posted? I'm getting horrible dropped calls on RR.
Anyone figure out how to get SuperSU updated?
l_4Fhit_l said:
Are there any running issue for those using this ROM on the current build besides whats posted? I'm getting horrible dropped calls on RR.
Click to expand...
Click to collapse
You might try updating your PRL and see if that helps at all.
gsm sim not working any fix?
Kasual52e said:
You might try updating your PRL and see if that helps at all.
Click to expand...
Click to collapse
I think that might have worked! Thanks man
Anyone else getting a force close with their Clock app when their alarm goes off? My alarm still works, but I'm worried it'll close itself and make me late for work.
Ok, fixed the clock issue by freezing the Clock app and redownloading it from the Play Store.
I've noticed I can't make any in-app purchases with this ROM. I wiped my cache/davlik and flashed a newer version of GApps which didn't work, I then installed a newer apk of Google Play Services and that caused a force close issue, I wiped everything, reflashed the new version of GApps and now I'm back to square one. Not sure what I can do from this points, any ideas?
Edit:Figured it out! Lucky Patcher was messing my store connection up somehow. Froze it via Titanium Backup, cleared the data/cache from the Play Store app, and now everything is working.
Anybody have the issue of their display being too dim?
On lowest brightness, display is barely visible even in complete darkness. Highest brightness is fine for indoor but outdoor its too dim
Yes, adaptive brightness is off. I am on LS990, latest 3/19 nightly. Did not have this problem on stock, brightness was fine both at lowest and highest.
allanlgz said:
Anybody have the issue of their display being too dim?
On lowest brightness, display is barely visible even in complete darkness. Highest brightness is fine for indoor but outdoor its too dim
Yes, adaptive brightness is off. I am on LS990, latest 3/19 nightly. Did not have this problem on stock, brightness was fine both at lowest and highest.
Click to expand...
Click to collapse
Setting > Display & lights > Brightness level is set to what you want
Setting > Display & lights > Adaptive brightness is disabled
Setting > Display & lights > LiveDisplay > Display mode is set to Off
One of those three should do it for you.
Related
★ ☆[ROM][4.4][UNOFFICIAL] CyanogenMod 11 | Alpha.02 | tiKtaK [12-06-13]☆ ★
Unofficial
Cyanogenmod 11
HTC Fireball
I don't usually develop for devices I don't have.
But I saw you guys had no KitKat love over here yet, so I thought I'd give it a shot for you.
Please realize this is completely untested, as I do not have this device.
I have a Thunderbolt, a DNA, and an HTC One.
So just be aware of that and be kind to me, lol.
I hope it boots and is somewhat usable!
I look forward to hearing the results.
It is built using the latest CM sources.
***EDIT: It boots and has working 4G/LTE, wifi, and GPS!
KitKat -- Android 4.4 -- CM11
DISCLAIMER:
Your warranty is now void.
I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Please do some research if you have any concerns about features included in this ROM before flashing it!
YOU are choosing to make these modifications, and CANNOT BLAME ME or anyone else for causing harm to your device.
Click to expand...
Click to collapse
CyanogenMod (pronounced sigh-AN-oh-jen-mod), is a customized, aftermarket firmware distribution for several Android devices.
Based on the Android Open Source Project, CyanogenMod is designed to increase performance and reliability over Android-based ROMs released by vendors and carriers such as Google, T-Mobile, HTC, etc.
CyanogenMod also offers a variety of features & enhancements that are not currently found in these versions of Android.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While this build is heavily optimized, it is also capable of pushing your phone much harder.
CyanogenMod and it’s team hold no responsibility to any damage caused to your phone, loss of earnings as a result of damaging your phone or anything else that is connected to the development of this rom.
For a list of devices officially supported by CyanogenMod, check out the official devices page.
Such is the craze for CyanogenMod, that devices that aren’t officially supported, still manage to receive ports of the ROM courtesy of enthusiasts and developers.
CyanogenMod offers the most barebone Android experience coupled with some very powerful tweaks.
This whole package by now is not wholly developed by CyanogenMod developers alone, but is a collaborative effort between them and independent developers around the world.
DOWNLOAD:
cm-11-20131206-UNOFFICIAL-fireball
4.4 Gapps
You will likely need an updated recovery.
Assuming that is the case, I will provide the one that compiled with my build.
ClockWorkMod KK compatible recovery image
Old Versions:
cm-11-20131202-UNOFFICIAL-fireball
Source: CM Github
Thanks for trying my build....
Just in case....
I tried to install using TWRP 2.6.3.0. It seemed to mostly work until...
Code:
Creating Symlinks...
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
Error flashing zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
After this, the device just bootloops.
I'm going to try again using the recovery.img referenced in the first post.
EDIT: After flasing the CWM recovery from the first, I was able to install. My phone is booting up....
And success! It booted. I made a phone call. I have 4G/LTE. WOW! I'll test some more tonight and report any issues I discover.
EDIT2: The first boot after installing gapps-kk crashed and rebooted the phone. The second boot hung at the "Android is upgrading..." screen with the message "Optimizing app 1 of 21". During this, I checked the CPU usage and found that /system/bin/mpdecision was using 100% of the CPU. After a few minutes I pulled the battery and restarted the phone. This time, with it unplugged (it was connected via USB to my laptop in all previous tests). It completed booting and finished the Android upgrade.
I was able to setup my Google account and download apps over 4G/LTE.
Google Keyboard, Google Search, and Google + were all out-of-date and got updated.
I briefly tested the GPS using "GPS Test" from CHARTCROSS LIMITED. The GPS worked and I got a lock quickly.
I tested WiFi on both 2.4, and 5 GHz both worked reliably for the brief period I tested.
The only thing I find lacking (and it's lacking in ALL non-stock-based ROMs) is the ability for an app to read the secure element of the SIM. This is a requirement for the ISIS contactless payment system - which I use A LOT. So, even though I'd really love to be on KK, I'll be reverting back soon.
-xdadevelopers-user
xdadevelopers-user said:
I tried to install using TWRP 2.6.3.0. It seemed to mostly work until...
Code:
Creating Symlinks...
ApplyParsedPerms: removexattr of /system/addon.d/50-cm.sh to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
E:Error executing updater binary in zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
Error flashing zip '/sdcard/cm-11-20131202-UNOFFICIAL-fireball.zip'
After this, the device just bootloops.
I'm going to try again using the recovery.img referenced in the first post.
EDIT: After flasing the CWM recovery from the first, I was able to install. My phone is booting up....
And success! It booted. I made a phone call. I have 4G/LTE. WOW! I'll test some more tonight and report any issues I discover.
-xdadevelopers-user
Click to expand...
Click to collapse
Thank you for testing and reporting back! :good:
Can confirm it boots and runs very well after updating recovery. Great job!
Please for HTC Thunderbolt Sir Santod:victory:
wow - great news!
This works very well considering. I haven't experienced any major drawbacks yet. WiFi, GPS, LTE, Bluetooth all work great and I have no problems sending or receiving texts or pictures, the only thing I have really noticed is that the native browser force closed on me. I downloaded chrome and all is good. I did redo the RUU because of a borked radio but that was from the last time I installed 10.2.
Sent from my Incredible 4G LTE using xda app-developers app
I had the same issue with installing, worked flawless when using the specified CWM.
Camera, 4g, calls, wifi, gps everything worked.
1 main issue I ran into is multiple FC when using messaging or hangouts to text
I have not had any fc 's for messages and I don't use hangouts. I forgot to mention the camera works well and it's even oc'd to 1.5 GHz, which works well. This is the best alpha build I've ever ran. I did have to use the CWM recovery provided also, forgot to mention that.
Sent from my Incredible 4G LTE using xda app-developers app
By far the BEST alpha ever..... I did have to use the recovery specified
No fc so far and ran it for the better part of yesterday and overnight ... Will report back on battery life tonight
One question , how do you add home screens
When you go to the widgets page and touch and hold the one you want then you can add it to the left or the right of the home screen and it will add a page for you.
I have noticed that the ear piece volume is pretty low during phone calls, I know this was/is an issue with other CM builds, I don't know of a fix for this. Does anyone else?
About to flash soon reboot back how to works for me! Thanks for you efforts Dev!! Awesome that you are building us cm11 and don't even have the device!
Sent from my LG-G2 using Tapatalk
What are the recommended install steps? I am rooted and S-off. Thanks for your hard work! Currently running Viper.
Sent from my ADR6410LVW using Tapatalk
Flashed CWM, then the zips, wiped davlik
1st boot: restarted during CM splash screen
2nd boot: got to "Optimizing app" but was going extremely slow (this has been happening alot lately with other builds)
3rd boot: seems good
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
j3grizz said:
What are the recommended install steps? I am rooted and S-off. Thanks for your hard work! Currently running Viper.
Sent from my ADR6410LVW using Tapatalk
Click to expand...
Click to collapse
Flash the stock recovery: adb fastboot flash recovery nameoffile.img
Do a factory reset/wipe data in Recovery
Flash the rom and flash Gapps
reboot
enricong said:
Flashed CWM, then the zips, wiped davlik
1st boot: restarted during CM splash screen
2nd boot: got to "Optimizing app" but was going extremely slow (this has been happening alot lately with other builds)
3rd boot: seems good
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
Click to expand...
Click to collapse
There is no need to wipe dalvik after flashing the rom, that creates issues.
As the dalvik hasn't even built yet and now its gonna try and optimize on first boot.
Let me know if you guys want more builds/updates/nightlies?/weeklies?....
Or is there not very many folks left on the device that are interested?
Glad the initial build is working out well.
Great Thx!
---------- Post added at 09:24 PM ---------- Previous post was at 09:10 PM ----------
I would be willing to try weeklies. This looks like it could be a great rom. I will post after I flash it. Thanks again.
OK just finished running for the day and with moderate usage
Dozen or so phone calls....
40+ text/chats
15min of navigation
And various web searches
Took it off the charger at 5:30am
8% at 7:30 pm
About the same or just a touch better than what I had with cm 10 or stock
enricong said:
I wish there were a way I could restore a TWRP backup using CWM so I could jump back to 10.2 quickly if needed
EDIT: Oh I guess I could have just down a backup in CWM before flashing CM11. Oh well
Click to expand...
Click to collapse
Assuming you didn't delete the TWRP backup you could always just reflash TWRP and then restore like normal.
Sent from my XT1060 using xda app-developers app
Q&A for [ROM] **crDroid Lollipop 5.0.1** [vs985][12-3-14]
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] **crDroid Lollipop 5.0.1** [vs985][12-3-14]. 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!
Need for Wipe
oadam11 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
crDroid Custom Features:
Dialer Lookup;
Profiles form CyanogenMod;
Call blacklist support;
Protected apps (using trebuchet launcher);
Filter spam notifications;
Clear all button in recent panel;
Privacy guard from CyanogenMod;
Quick settings pull down with one finger in right corner;
Data activity indicators;
Increasing ring tone;
Advanced reboot menu;
Option to hide adb notification;
Screen shot quick delete with confirmation;
Long press back to kill with configurable timeout;
Less frequent notifications sound;
Advanced keyboard features (auto rotation with timeout, disable full screen, selector notification, show enter key, volume key cursor control);
Always Have a full functional Backup. Just in case!
DOWNLOAD
please do not mirror !
pa gapps
screenshots
First time installing crDroid to your vs985, or coming from another ROM:
- Make sure you're running a proper working Recovery (CWM or TWRP)
- Copy GApps and crDroid zip to your internal SDCard
- Boot into Recovery
- Flash crDroid zip
- Flash GApps zip
- DO A DATA WIPE / FACTORY RESET
- Reboot
- Don't restore Apps using Titanium Backup!
Don't expect any support if you:
- are not running stock crDroid-kernel
- have installed any mods such Xposed!
- have modified system files
Thanks to:
Cristiano Matos the developer of this beautiful rom
CM Team
Slim Roms Team
ParanoidAndroid Team
temasek
Omniteam
androidfilesharing for his awesome contribution
invisiblek
manups4e
sooti
And Many More...
if you want to donate please donate to Cristiano Matos who has made this rom PAYPAL
this rom is unofficial so not supported by Cristiano Matos , please don't bother him with questions
kernel source
http://crdroid.org/
crDroid G+ community
https://github.com/crdroidandroid
Click to expand...
Click to collapse
Does flashing this need a wipe if im coming from CM 12 unofficial Lollipop ROM?
New CM Theme App
Pbaird1979 said:
From what I understand, cm team is not beginning themes until 12 is more stable. I may be wrong about this but it's what I understand.
Click to expand...
Click to collapse
The CM Team just announced a new Theme App for anyone running a CM-based ROM that will allow for full customization. From the sounds of it,
it should be out any day and I expect it will work on CM12.
Brandodando said:
Does flashing this need a wipe if im coming from CM 12 unofficial Lollipop ROM?
Click to expand...
Click to collapse
Yea. Clean flash is necessary
I tried to install SuperSU and it sent me into a boot loop, same thing happened to me with the Vanir Comotio build as well, any ideas?
I am getting the "Unfortunately, DSP Manager has stopped" every time I open Play Music and when I skip tracks. Anyone know how to fix this? Also is Wifi Tether working? If not any workarounds?
Does anyone know how to fix the 505 error in play store when trying to DL an app
PA gapps - modular version?
Is the modular version the one to download for this rom? The rest of the versions seem to not have DL links
Bug report:
While playing music and using navigation in the car (using bluetooth), voice directions break in and lower the music volume as it should. Upon returning to music, the volume does not return to its previous level, rather it gets louder, overdriving the phone output and causing distortion. Pressing volume down on the phone once returns volume to normal levels.
Same scenario when SMS notification is received while playing music.
I'm working on a band-aid fix using Tasker, but it would sure be nice to have this fixed more permanently. This is a fantastic ROM, and other than this has been 100% trouble-free. Great work!
Currently running crDroid 12/19 build
This is not a question, but because I'm new, my post came here. I've been lurking around these boards since the HTC rezound, and I must say that the crDroid 12/30 build for the G3 is the fastest and most stable ROM Ive ever used. Great work! I signed in just to say that.
This isn't a question, just a quick note that the 12/30 build is running great so far. The only thing I could even think to add is the option to modify the DPI within your crdroid menu in settings. Other than that, Great Job!
Huge Battery Drain
Folks,
I like the overall look, features, etc. of the Rom so thank you for that. However, it took my battery from 100% to 11% overnight. I'm on the 1/2 version, did the usual wipe/factory reset, wipe cache/dalvik, etc. and then installed the Rom and Gapps.
Any suggestions before I flash back to CM11?
I'd greatly appreciate it.
pressmoon said:
Folks,
I like the overall look, features, etc. of the Rom so thank you for that. However, it took my battery from 100% to 11% overnight. I'm on the 1/2 version, did the usual wipe/factory reset, wipe cache/dalvik, etc. and then installed the Rom and Gapps.
Any suggestions before I flash back to CM11?
I'd greatly appreciate it.
Click to expand...
Click to collapse
Have you checked your battery stats to see if any app or process in particular is the culprit?
Keyboard Chooser Crash
On the newest Jan19 build I can't switch to alternate keyboards. They install but under settings/language&input when I press choose keyboard under current keyboard it crashes. I installed clean with the Jan16 PA Gapps. I just want to know if anyone else has had similar problems.
Not sure if anyone else is having this problem and I did not read it anywhere. But it could be just me but when I'm in a phone call and another call comes in I can transfer over but both people can't hear me and I can't hear them. What do you guys think. In on 1-20 build
flac support?
does this most recent update not support .flac files natively?
Loss of root
I've been using this rom since the very first release with no problem, yesterday I tried to update to the latest build but I wasn't able to reboot into the recovery using the terminal emulator. Then I did a root check and it seems I'm no longer rooted. I attempted to use stump to reroot my phone but it's giving me an unsupported device error. What can I do to install the latest build?
WiFi?
WiFi passwords are not being saved every time I turn the WiFi off the passwords get deleted.
crDroid Lollipop 5.0.1 ROM crashing my LG G3
Using TWRP 2.8.4.0 I ROMed my LG G3 (vs985) with crDroid Lollipop 5.0.1 01/19/2015 build) yesterday and everything worked great. This is the second time ROMing this phone for me - previous running ROM was Cyanogenmod cm-12 which I didn't really care for. My initial impressions was that this is a great ROM.
Not so sure about that now. Before going to bed last night turned off phone; got up this AM, turned on phone and everything turned to s**t. Greeted with a KP right at boot up. Rebooted and appeared to boot ok with my normal home screen appearing but then several seconds later either of two windows started popping up - "Unfortunately, Google Play Store has stopped." or "Unfortunately Google Play Services has stopped." Every time time I do an OK button press on the displayed window either that one or the other window immediately pops up. I can't do any actions to get out of this mess.
So my question is what can I do to get back to normal operation and put my VZW ROM backup back on the phone? Also, is there a bug in the crDroid ROM (at least in this build)?
Thanks.
bmwmcrider said:
Using TWRP 2.8.4.0 I ROMed my LG G3 (vs985) with crDroid Lollipop 5.0.1 01/19/2015 build) yesterday and everything worked great. This is the second time ROMing this phone for me - previous running ROM was Cyanogenmod cm-12 which I didn't really care for. My initial impressions was that this is a great ROM.
Not so sure about that now. Before going to bed last night turned off phone; got up this AM, turned on phone and everything turned to s**t. Greeted with a KP right at boot up. Rebooted and appeared to boot ok with my normal home screen appearing but then several seconds later either of two windows started popping up - "Unfortunately, Google Play Store has stopped." or "Unfortunately Google Play Services has stopped." Every time time I do an OK button press on the displayed window either that one or the other window immediately pops up. I can't do any actions to get out of this mess.
So my question is what can I do to get back to normal operation and put my VZW ROM backup back on the phone? Also, is there a bug in the crDroid ROM (at least in this build)?
Thanks.
Click to expand...
Click to collapse
Edit: managed to reboot into recovery mode and restore from my backup VZW ROM. But my original issue still stands: Why did everything go wonky? Also, the previous poster noted that Stump Root complained about non-compatible phone. Before doing my recovery I managed to launch Stump Root and got the same response. Stump Root doesn't like crDroid?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github Repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
CyanogenMod 13 Changelogs
Instructions
First time flashing CyanogenMod 13 your device, or coming from another ROM?
Official long version:
Installing CyanogenMod from recovery
Short version:
1. Download the zip(s) from the download section below.
2. Install a compatible Recovery
3. Perform a NANDroid backup of your current ROM (Optional)
4. Perform a Factory reset (wipe data & cache partitions of your device)
5. Flash your CyanogenMod zip file
6. Optional: Install Google Apps
Downloads
Official CM13 Nightlies
TWRP Recovery
Official Open GApps (Choose the nano version or smaller. The other versions won't fit.)
Open GApps XDA-Thread
Note: Some GApps are very basic & will give you only Google app & Google Play Store. The rest of the apps can be downloaded directly from the Play Store as per your need after signing in to the Google. If calender syncing is not working so there is an additional script for that, just flash it & voila it will start working.
Bugreports
On nightlies, you don't have to report bugs here, if you wish to, you can do that here.
Thanks!
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy.
PS: I have not built this rom, I don't even know if I can post this here, it's mostly a copypaste from another CM thread. If you want me to edit/remove this just tell me.
Current nightly status
I'll use this post for the current nightly build status, wether it has major issues or not. I'll try to keep this updated based on the communities replies, no guarantees though.
Current 20160219 build status: GOOD
20160129 nightly causes bootloops and was removed from get.cm. The build from 20160127 is fine, so use that instead.
Thanks for opening this thread!
Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".
Might need to get the AOK from mods about this thread, but hopefully will be ok, makes sense to get cm13 one by now.
Hi, thx for this thread. I love Cyanogenmod from version 6 and I was very happy, that came CM13 MM, but with a few last builds I have trouble with lags. After reboot is several hours everything OK, but after that I have several seconds lags when I want run some application (or wake from recent apps).
The same trouble was in last builds CM12.1. Let me know, if exist some solution? Now I must left CM13 (to Chroma and lags are gone), but I want come back, but without lags...
Do you have some of you the same trouble?
Odesláno z mého Nexus 4 pomocí Tapatalk
sigulda1 said:
Thanks for opening this thread!
Just a little note. From my experience it is quite important to wipe system as well, if you plan flashing a new ROM. Of course this depends on the previous ROM. Most of the times it might not be necessary, but for me it is "best practice".
Click to expand...
Click to collapse
Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.
Nilsb7 said:
Manually wiping the system partition actually seems to cause some issues.
Click to expand...
Click to collapse
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Nilsb7 said:
Had to research it because I wasn't sure about this part either (I copy pasted it from the old thread..) but apparantly a Factory reset is the way to go as CM installs wipe the system partition anyways. Manually wiping the system partition actually seems to cause some issues. The official instructions don't mention wiping system either. Thanks for the feedback though.
Click to expand...
Click to collapse
bringonblink said:
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.
bringonblink said:
Huh? Never heard that before, any sources?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
xWolf13 said:
Manually wiping the system partition causes no problems at all. It simply wipes the ROM, and when flashing a new build, will replace it. Unless you are using CyanDelta, wiping the System should not cause any problems. I, for one has not gone through any problems while wiping my system partition.
Click to expand...
Click to collapse
Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .
Nilsb7 said:
Had some problems with this myself when trying to update from CM12 to CM13, I tried to only wipe /system though, because I was trying to get rid of a buggy/unkown gapps installation, and this caused error messages to pop up when trying to flash the CM13 version in TWRP. Can't find any sources for this besides this one though, this was the only one I found when searching before so I assumed it was right.
Guess I was wrong? .
Click to expand...
Click to collapse
Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems
bringonblink said:
Oh if you're flashing different android versions without doing a full wipe, yeah you're gonna get problems
Click to expand...
Click to collapse
Dirty flashing was approved/recommended officially see here.
Back on topic, anyone tried the 20160201 nightly yet?
Nilsb7 said:
Dirty flashing was approved/recommended officially see here.
Back on topic, anyone tried the 20160201 nightly yet?
Click to expand...
Click to collapse
I'm using it, no problems so far
Edit
Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.
Can anyone else check if they have this?
Sent from my Nexus 4 using Tapatalk
bringonblink said:
I'm using it, no problems so far
Edit
Seem to be getting a huge "sns_async_ev and sns_periodic wakelock" wakelock. Actually not letting the device sleep at all. Looks to be related to the hardware sensors.
Can anyone else check if they have this?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.
Nilsb7 said:
I'm on 20160201 and I don't have that issue. Here's a screenshot of my battery stats, the long wake periods are caused by my audiobook player.
Click to expand...
Click to collapse
Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.
You can see from the pic it stays awake, but no battery drop off :s
Sent from my Nexus 4 using Tapatalk
bringonblink said:
Something strange is going on, just did an hour test, where the phone did not go into deep sleep at all (from the wake lock, however drain seemed good at -1%an hour.
You can see from the pic it stays awake, but no battery drop off :s
View attachment 3631357
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Have you tried rebooting it at least once after flashing the nightly?
I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.
What I have tryed,
-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP
Still not working
You can find some screenshots attached....
izuels said:
I´m having problems enabling the WIFI after 4 days using the CM13.... it is very strange.
What I have tryed,
-Fly mode on - off
-Flashing the Radio
-Wiping cache with TWRP
Still not working
You can find some screenshots attached....
Click to expand...
Click to collapse
Try the latest nightly, this might be related.
Nilsb7 said:
Try the latest nightly, this might be related.
Click to expand...
Click to collapse
That was.... now after installing the last Nightly it works :/
I found also that the APP which is giving problems is https://play.google.com/store/apps/details?id=com.ryanamaral.wifi.passwords
im on the 20160202 nightly and everything seems fine except for the user profiles, it looks like they dont do much, i set a profile that toggles from 3g to 2g when connected to wifi but nothing happens. what else... the weather isn't displayed in the status bar and in the clock widget... multiple APN for the same carrier that sometimes disables the whole network until setting up the correct APN... but other than that its flawless. i rather stick to cm13 nightly than going LL or custom MM.
Sent from my Nexus 4 using Tapatalk
I installed nightly 2016-02-06. Everything looks fine since 24hours.
But CM has chosen the wrong APN : Wap.vodafone.de instead of web.vodafone.de
lineage 15.1 oreo builds are now available. See new thread here:
https://forum.xda-developers.com/ne...rom-lineageos-15-1-nexus-5x-bullhead-t3724575
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
LineageOS is a free, community built, aftermarket firmware distribution of android, which is designed to increase performance and reliability over stock android for your device.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Wiki.
Important Info
Current lineage 14.1 bullhead nightlies are based on the N2G48C (August 2017) monthly update from google. So you should be using the vendor, radio and bootloader img from that update. They can be extracted from the factory image on google's site here. Or you can use the ones linked below that I already extracted:
Note: The radio and bootloader img is the same as what was in the previous monthly google update, so if you already have it you don't need to flash it.
* vendor-n2g48c.img
* radio-bullhead-m8994f-2.6.37.2.21.img
* bootloader-bullhead-bhz11m.img
The vendor img is flashable with twrp or fastboot. For the radio and bootloader img, use fastboot.
More information and installation instructions can be found on the LineageOS wiki here.
Download Links
LineageOS: https://download.lineageos.org/bullhead
Google apps: Beans GApps (recommend mini)
SU addon zip: Addon Install zip / Addon Removal zip NOTE: LineageOS does not come with root, so this is now provided for those that want it. The install zip is a one time flash, like gapps. Meaning, it persists when updating to a new LineageOS nightly. REF: https://download.lineageos.org/extras
Changelog
https://download.lineageos.org/bullhead/changes/
Stats
https://stats.lineageos.org/
Credits
Many thanks to the LineageOS team and all the contributors out there in the community :good:
Contributors
dcd1182, razorloves
Source Code:
Device tree: https://www.github.com/LineageOS/android_device_lge_bullhead/tree/cm-14.1
Kernel tree: https://www.github.com/LineageOS/android_kernel_lge_bullhead/tree/cm-14.1
ROM OS Version: 7.1.2 Nougat
ROM Kernel: Linux 3.10.73
Status: Nightly
Issues with CM 14.1
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
maof_ke said:
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
Click to expand...
Click to collapse
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
Otherwise pretty stable.
I've flashed it, it had some problems booting, but now its working. Here's my guideline:
1-If you do not want to get the VENDOR message at first boot, start flashing last NRD91N factory image
2-Flash TWRP from fastboot, and do a "Fastboot erase cache" and "Fastboot erase userdata"
3-Reboot into TWRP, and do a DATA Format
4-Reboot into TWRP and do a Full Wipe
5-Flash CM14.1 and OpenGapps (i used nano)
6-Reboot. Give it about 5 min, mine got stuck at CM logo. If after 5 min it does not boot, keep power button pressed for a few seconds till it reboots. It should boot properly now.
7-If after booting, entering SIM Pin code DO NOT ENABLE WIFI OR DATA. It will cause a loop on the wizard. Let both be disabled till the end of the config.
8-Reboot and you should have CM14.1 official working.
Here's proof:
Sorry for my english. :angel:
UPDATE:
Ok, i've been doing some more testing with both official 7.0 and dev preview 7.1 and here are my results:
1-If you want, you can use 7.1 dev preview as base, using the same tutorial above. The only difference will be that after every reboot, right before PIN Code, it will tell you the VENDOR.img message. Nothing to worry about.
2-I don't know if it is a placebo effect or not, but I get better performance on the CM14.1 if I use 7.1 as base. I think it is more fluent.
3-Using 7.1 as base definetively changes something, there's a little "glitch" or graphical difference with 7.0. Here's proof:
As you can see, Menu item switch looks different from 7.0.
4-In my experience, I've decided to disable the stock Web Browser and install any other, because the one that comes with the build gives FCs some times, and I think it has some memory leak or something, that makes the OS lag. After disabling it, everything works fine.
Hope this helps to anyone.
Cheers
@razorloves
Thanks for you're contribution to N5x!
I've never used but want to try this out since i'm hearing a lot about it....what I want and need to know is what features comes with this ROM? something tells me i'm really going to like it.
Gallery app freezes and then the phone resets...and ElementalX has dark camera bug
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
outlawman007 said:
Gallery app freezes and then the phone resets...
Click to expand...
Click to collapse
yep, just heard about that couple hours ago.
already submitted fix, just testing it now.
http://review.cyanogenmod.org/#/q/topic:sdcardfs-fix
EDIT: Thanks to @DeHuMaNiZeD for testing my changes. The fix is now merged and will be in the next nightly.
My impressions so far are exactly as mentioned above by others with the added addition that battery icons dont work when you switch landscape and circle. Hidden and text work. Other than that the rom is pretty stable.
Carach_CZ said:
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
Click to expand...
Click to collapse
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
After first flash, coming encrypting screen, is this normal ?
airtower said:
Do not enable wifi or cellular data during setup, and it will not attempt the device setup part that you can't get past.
Click to expand...
Click to collapse
Couldn´t sign in
You don´t have a network connection.
After pressing next i can either turn on mobile data or connect to wifi.
So.. sorry your advice really didnt helped at all. :crying:
PS: even got "CM stopped working". I even downloaded NRD91N factory image, used its bootloader, radio and vendor. With no luck. Im DEcrypted btw. How the hell you managed to make it work?
PPS: Should i use CM Recovery instead of TWRP? "Sigh" this is frustrating..
Carach_CZ said:
Couldn´t sign in
You don´t have a network connection.
After pressing next i can either turn on mobile data or connect to wifi.
So.. sorry your advice really didnt helped at all. :crying:
PS: even got "CM stopped working". I even downloaded NRD91N factory image, used its bootloader, radio and vendor. With no luck. Im DEcrypted btw. How the hell you managed to make it work?
PPS: Should i use CM Recovery instead of TWRP? "Sigh" this is frustrating..
Click to expand...
Click to collapse
I came from tupac4u's debloated Nought rom, but flashed an unofficial CM14.1 build before this official one. During that process I was prompted to encrypt. I used TWRP 3.0.2-2 throughout. I get warnings during boot, but I clear them with no ill effects.
Not sure what else to tell you. As far as the setup goes, there's instructions a few posts up on how to delete the wizard all together. I didn't need to do this however. Initially I was stuck on the copy from device screen (there's no forward or submit button), but was able to go back, long press and forget the previously saved wifi, uncheck mobile data, and proceed forward skipping the device sync part. When I first opened play store, I was asked for my google credentials and two-factor code.
airtower said:
I came from tupac4u's debloated Nought rom, but flashed an unofficial CM14.1 build before this official one. During that process I was prompted to encrypt. I used TWRP 3.0.2-2 throughout. I get warnings during boot, but I clear them with no ill effects.
Not sure what else to tell you. As far as the setup goes, there's instructions a few posts up on how to delete the wizard all together. I didn't need to do this however. Initially I was stuck on the copy from device screen (there's no forward or submit button), but was able to go back, long press and forget the previously saved wifi, uncheck mobile data, and proceed forward skipping the device sync part. When I first opened play store, I was asked for my google credentials and two-factor code.
Click to expand...
Click to collapse
7-If after booting, entering SIM Pin code and WIFI, it gets stuck at "looking for another terminal" or similar, reboot to TWRP and go: MOUNT-->TICK SYSTEM. Then got to ADVANCED-->FILE MANAGER-->SYSTEM/PRIV-APP/CYANOGENSETUPWIZARD and press option button-->DELETE.
This helped A LOT. I got rid of bugged (i know, first nightly) CM settings wizard and got into AOSP settings wizard which was flawless. Im using the CM 14.1 now! Finally!
Thanks!
maof_ke said:
Hello, today I tried to flash CM 14.1 but I had some issues like warning that my phone is corrupted or something and I have to contact manufacturer. I wasn't able to setup the device. I'm wondering if this can be flashed over purenexus 7.0 ROM with NBD90Z vendor image...or should I flash some newer vendor image ? Thanks for help community
Click to expand...
Click to collapse
What I did to fix this is I did I clean install with no gapps so that you don't have to do Google setup at first boot. booted fine, then I rebooted into twrp and flashed gapps. When I booted back up I just went to settings and added my Google account. I am using mini open gapps
After the registering problems, does the ROM is stable for daily use? I really want to try it, but it is my main phone...
Carach_CZ said:
Im unable to complete the initial settings.
After connecting to wifi or data, im prompted to copy data from another device with some error messages and i cant proceed, im always taken back to previous settings screens.
When i try to turn off the wifi and data, the phone tell me that "unable to connect" and im taken back to "choose how to connect" screen. So... any suggestions? I even tried "factory reset" but with no luck.
Im using the newest bootloader from 7.1.1 DP, is this a possible source of the issues? Thanks!
Click to expand...
Click to collapse
someone posted how to get around the setup solution just a couple of post upwards, I was having that problem to, but followed his instructions and cm14 works fine now
@razorloves. the cm bug report keeps force closing.
Anyone else having problems with clock app? I can't open it at all, tried installing through aroma gapps and through app store, aside from that everything seems stable. Even my fingerprint unlock works again which makes me really happy, it stopped working during marshmallow and even after 7.0 it wouldn't work but somehow it's back and fully functional.
Not booting with F2FS data and cache partitions. Booting fine with jolla kernel. As I see stock kernel that included in ROM also supports F2FS, but I don't know why it's not booting.
LineageOS is a free, community built distribution of Android which greatly extends the capabilities of your phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Code:
#include <std_disclaimer.h>
All information and files — both in source and compiled form —
are provided on an as is basis. No guarantees or warranties are
given or implied. The user assumes all risks of any damages that
may occur, including but not limited to loss of data, damages
to hardware, or loss of business profits. Please use at your
own risk. Note that unless explicitly allowed by the warranty
covering your device, it should be assumed that any warranty
accompanying your device will be voided if you tamper with
either the system software or the hardware.
This is a weekly build (Wednesdays) of LineageOS 14.1 for the Sprint variant of the LG G3 (ls990).
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
If you want to help out follow the building guide and then submit a patch to our Gerrit instance.
Installation Instructions are available on the wiki but the basics are below.
*NOTE*: You must be Bump'd for this to work. This requires flashing via custom recovery *TWRP* for "ls990”.
1. Download the ROM and Open GApps (recommended Open GApps here). You are going to need to use the arm 7.1)
2. Put both on Internal Storage
3. Reboot into recovery
4. BACKUP CURRENT ROM
5. Factory Reset/Wipe if not already on LineageOS 14.1
6. Flash the ROM ***(if installing GApps flash it prior to rebooting or you will have to Factory Reset and start over)
7. Flash GApps 7.1
8. Reboot
9. wait... wait... wait...
10. Profit
To get root/SU, flash the arm su package available in the "Extras" download section or here.
Weekly builds
Working:
Almost everything
Known issues:
None at this time. List any others and I will try to get them working as I have time
@invisiblek deserves most of the credit for this project
LineageOS Blog
LineageOS Wiki
LineageOS Community
LineageOS Status
LineageOS Google+
Best rom ever for this device i came from resurrection remix .. pixel .. fulmics ... crdroid .. this one is better than all of them.
In camera app there is no 4k recrding option but you can use other camera apps and get this option. thermal and performance is just fine but not like stock 6.0 based roms but better than RR rom. Tnx a lot for keeping cyanogenmod alive
this rom have some problems with gapps some of them not install complietly and some of them don't work ...
Beautiful ROM! S'much appreciated.
Settings, More, Cellular Network, Carrier Settings produces the error:com.android.phone has stopped
Open app again. There is a reload/refresh circular button to click on the second line before "Open app again".
Having issues locating where/how to update PRL due to horrid DATA reception which is nothing new to this location.
Freedompop is the carrier.
LS990 running (latest) LineageOS version 14.1-20170611-NIGHTLY-ls990
Since Cell/DATA was not beautiful before the ROM Flash and horrid after, I flashed Modem VFC and although possibly imaginary, the connection is more stable but also still poorly and "apparently" not as good as before.
avibp said:
Beautiful ROM! S'much appreciated.
Settings, More, Cellular Network, Carrier Settings produces the error:com.android.phone has stopped
Open app again.
There is a reload/refresh circular button to click on the second line before "Open app again".
Having issues locating where/how to update PRL due to horrid DATA reception which is nothing new to this location.
Freedompop is the carrier.
LS990 running (latest) LineageOS version 14.1-20170611-NIGHTLY-ls990
Since Cell/DATA was not beautiful before the ROM Flash and horrid after, I flashed Modem VFC and although possibly imaginary, the connection is more stable but also still poorly and "apparently" not as good as before.
Click to expand...
Click to collapse
You need to flash stick to update prl properly but there are other options if you search for them. Carrier settings has always been an issue I'll look at giving that option again.
Flash "stock" STOCK - I was wandering around searching for a "stick" to flash. LOL Thank you very much for the reply. As a side note to this posting however the other options to refresh or update the PRL do not work as in ##72786# or *#*#72786#*#*. The later does seem to want to work but where it should normally prompt for the MSL, instead just goes to a blank screen with a dialer.
Now for the real issue: I'd like to keep as many of my applications on my ext SD card as I can. I can't move any of my applications to the ext SD card. There is an option in developer options that theoretically allows you to move all applications to the SD card, however, when this option is selected, there is still no effect.
This was an issue with marshmallow as well as CyanogenMod 13 I believe but was address appropriately in CyanogenMod 14. Again - I believe, but please don't quote me.
Thanks again for the release
hi ! thx for this rom !
my problem with this rom and others like the RR rom on my LS990 ,my phone stuck in the boot screen ,i wait for an hour but it still stuck :/ :/ :/
plzzz someone helps mee :/
ayouarti said:
hi ! thx for this rom !
my problem with this rom and others like the RR rom on my LS990 ,my phone stuck in the boot screen ,i wait for an hour but it still stuck :/ :/ :/
plzzz someone helps mee :/
Click to expand...
Click to collapse
Make sure you have the latest twrp wipe and install. If you are installing gapps make sure to install prior to reboot.
Last two builds...
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
bgabel said:
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
Click to expand...
Click to collapse
Try with a custom kernel
Sent from my LG-ls990 using XDA Labs
bgabel said:
Has anyone had any success booting the last two weekly builds? The 8/30 and 9/6 builds both go into a bootloop for me... the Lineage startup logo never appears... tried many things including erasing and clean installing and I get the same. Going back to 8/23, all is good again...
Click to expand...
Click to collapse
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
[/COLOR]
Kasual52e said:
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
Click to expand...
Click to collapse
Thanks for your reply! This ROM has been a godsend for an older phone that I am not ready to give up yet... Thanks for your work on this!!
Kasual52e said:
I think it was an issue with one of the CVEs that were merged but I haven't had a chance to figure out the exact issue yet. I'll get the build pulled.
Click to expand...
Click to collapse
I really appreciate the work done on this ROM! What I ended up doing is using a working boot NANDROID and restored that after installing the update. It worked fine for me but looking forward to future offerings with a working kernel.
I think it is this commit https://review.lineageos.org/#/c/189075/ which is causing the problem. I created the revert and I'm going to let some others test before merging. I don't expect it to be an issue and we can probably get it in before this weeks round of builds.
The latest download is available -> https://download.lineageos.org/ls990. Let me know if there are any issues with it.
Kasual52e said:
The latest download is available -> https://download.lineageos.org/ls990. Let me know if there are any issues with it.
Click to expand...
Click to collapse
I installed the latest update without any problem. The system booted up just fine. Tried Magisk this time for root and it also is working fine, passed safe net.
Secure Boot Error
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
ExitusLSU said:
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
Click to expand...
Click to collapse
I can't answer your question about the error message (have never seen that) but you can install Supersu without any problem. I used it on all nightlies until this one, tried Magisk this time and it also works fine.
ExitusLSU said:
I'm having some small issues with my most recent installation of Lineage OS nightly on my G3 (LS990).
I did the following:
I installed TWRP.
I advanced wiped the cache, system, and data partitions.
I flashed the LineageOS zip (lineage-14.1-20170913-nightly-ls990-signed.zip).
I wiped the dalvik cache.
I flashed the LineageOS su add on zip (addonsu-14.1-arm-signed.zip).
I flashed the GApps zip (open_gapps-arm-7.1-pico_20170914.zip).
I rebooted.
Everything seems to be going ok, but everytime I reboot, I see a "secure boot error, error 1003" at the top of my screen. Is there a way to get rid of that message? Also, is there a way to install SuperSU onto the device, or is the su add-on the root for the device? I enabled apps to have root in the developer options screen. The hash sign in the status bar at the top really bothers me for some reason. Is that something built into LineageOS or is that part of the su add-on? Is there a way to hide that?
Thanks for the help.
Click to expand...
Click to collapse
The only way to get rid of that error it's to install an older factory firmware (I think around zvb) and flash from there or go with stock. It isn't an issue but it lets you know that you aren't running a stock image. You should get it booting into TWRP and Lineage but not if you go to fastboot.
SuperSU and magisk both work fine if you don't like the stock implementation
len207 said:
I can't answer your question about the error message (have never seen that) but you can install Supersu without any problem. I used it on all nightlies until this one, tried Magisk this time and it also works fine.
Click to expand...
Click to collapse
Have you run into any issues with the cellular data connection only showing as connecting to 3g? At my house, I get 4g lte, but now LineageOS only ever shows me connected to 3g.
Thanks.