Q&A for [ROM][L900] Cyanogenmod 12.0 [12/14/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][L900] Cyanogenmod 12.0 [12/14/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!
keyboard ?
works Good to what i see but there's no keyboard . Any fix for that ?
Working great no issues with phone, gps or camera. Great job and I look forward to the updates. Seems great so far.
Thanks
I just installed the new build I am only wondering how do I turn off my mobile data. This ROM is amazing and everything works except for data turning off and front camera
Battery Life
When i flashed this rom onto my device, i noticed a significant drop in battery life. Has anyone else noticed this and is there a fix for this?
thnx
Thank you sooooooooooo much man ,,, its sooooooo cooool ROM
working Perfectly on my sprint Note 2 SPH-L900
camera works fine ,,, everything is cool ,,, downloading now gapps
So I'm relatively new to the forums, I mostly just read, learn and try to stay out of way. Just flashed latest nightly last night. So far very smooth and stable. I did some poking a prodding this morning to answer some questions I had coming from CM11 which I was also new to.
Nice to see Sprint carrier billing back in this version. I know I saw it posted that NFC was not working but everything but Tap & Pay seems to work fine for me. Beam and Tags all function okay.
On top of Netflix not working yet, Play Movies 3.6.16 FCs on launch and after reverting to 3.4.23 it waits until you press play to FC.
I did have the keyboard issue that has been mentioned but was prepared with SwiftKey apk on my sdcard just in case. After finishing setup ALL keyboards seem to function just fine.
BT and GPS both working great.
All in all very usable and I'm going to give it a go as a daily for as long as possible though I may have to revert back to CM11 just for the Netflix/Play Movies since we only stream in my household. We'll see.
Not sure if this thread was the best place to share (I can't seem to comment on the main thread) but if there's a more appropriate place to provide feedback that someone wants to point me at, happy to do it.
Nice work everyone who's contributing. Thanks for your efforts keeping my Note 2 relevant.?
GPS
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
k3v0 said:
How did you get the GPS working? I tried flashing the GPS fix linked in the thread and a clean install with the latest nightly. I drive around and never obtain a GPS lock.
Click to expand...
Click to collapse
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
So I've been following the change log for this Rom, and I can't understand much.
I'm still on the 1/5/15 non nightly version and it's pretty much functional as a daily driver. What I'm wondering is are there any major differences for the newer nightlies?
Perhaps in addition to being a Q&A on these nightlies, everyone can post which version they're on, how it is (what's broken/what's been fixed), and what's new if anything.....
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
The Commish said:
Newb question: This is the first time I've started on a ROM at such an early stage of its development. Typically how fast does CM development progress once a new version is started? Idle curiosity mostly.
Click to expand...
Click to collapse
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
t4d73 said:
That would be nightly.
Sent from my SM-N910P using XDA Free mobile app
Click to expand...
Click to collapse
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
The Commish said:
Haha, thanks. ? I understand the nightly releases. What I meant was I guess is how long after a new version is started does it normally take to get to the first milestone or even snapshot release for instance? Like I said, I'm just curious about the process.
Click to expand...
Click to collapse
Lol. Yeah I wouldn't get your hopes up too high for that. It might happen but I guess we'll see. I don't think any device has gotten a milestone just yet anyway.
Sent from my SM-N910P using XDA Free mobile app
Keeps restarting on cm12 boot screen
Hey guys,
I have a situation I've never come across and wanted to see if someone might be able to point me in the right direction. I have two Samsung Note 2(l900) and running on cm12 as of this morning. I installed the new nightly on both devices the same exact way by opening clockwork recovery and installing zip. One device was successful and is working just fine, the other seemed to flash fine until it had finished loading the apps and going into boot. The device would restart on the note 2 logo screen and then proceed to the cm12 boot screen and then restart after a few seconds. I went back into recovery which took longer than usual, and proceeded to clear partition, wipe dalvik cache, and install older nightlies. I had the same result no matter what nightly I went with.
I decided to set the device back to stock rom and root again. I it worked just fine, so I went through the process about 4 times installing different nightlies but had the same restarting results. It was then I noticed that getting in clockwork recovery manually lagged about 30 seconds. I took the advice of someone on the Google plus forum and switched the recovery from clockwork to twrp. Tried again with the same restarting results and with the manual recovery lagging about 30 seconds to get into.
It seems to work just fine if I flash to stock touchwiz but recovery seems to have issues.
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
The Commish said:
I followed the sequence in this comment on the main thread and it just worked.
http://forum.xda-developers.com/showthread.php?p=58403610
Credit: @kylemccracken
"Edit: Make sure all important data and backups are stored to your external SD card before formatting. I used Philz 6.48.4 and CWM 6.0.5.0 when following this procedure.
[IMPORTANT]
After wiping clean to install a new rom, factory resetting, and wiping cache and dalvik cache, in philz recovery, go to your storage and mounts settings and format every option you can EXCEPT sdcard1. Reboot your recovery then proceed with the steps below.
Make sure you have your ROM, Gapps, SuperSU, and GPS fix zips on your external sdcard1. Flash in the order below.
1. Flash your ROM zip.
2. Perform a factory reset then wipe both cache options. This step is very important when facing problems after flashing.
3. Flash your Gapps zip. Wipe both cache.
4. Flash your SuperSU zip. Wipe both cache.
5. Flash GPSfix zip. Wipe both cache.
6. Reboot.
This process will give you the cleanest possible install with the highest chance of success. When I start having problems with flashing, I format everything (except sdcard1) then follow those steps. It's the same procedure I took when flashing the CM12 nightly and all is running well."
Click to expand...
Click to collapse
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
KAZETARO said:
I've tried several methods and combinations of wiping at every possible opportunity before pressing reboot and i'm still having
issue. All the the apps are listed in the app drawer displaying the file name instead of the app name. Also all of the apps display the same icon (default android) and the not installed toast appears when attempting to launch any of them. Is anyone else having this issue
attempted flashing
cm-12-20150203-NIGHTLY-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://download.cyanogenmod.org/?device=l900&type=stable
cm-10.1.3-l900.zip with md5: ba795d6a4261654648b0eb5cec019021 downloaded from http://wiki.cyanogenmod.org/w/Gapps
has anyone had success with either of these
currently running Android 5.0 Lollipop ROM for Galaxy Note 2! [CM12] downloaded from http://galaxynote2root.com
attempted with both gapps-lp-20141109-signed.zip and LollipopMicroGapps-121914-HighOnAndroid.zip both downloaded from http://galaxynote2root.com
I would prefer to use the aforementioned build because the build I'm running is not compatible with the nightlies
thanks for any responses in advanced.
Click to expand...
Click to collapse
Sorry, I'm probably not the most knowledgeable. If it wasn't for these forums I wouldn't know how to do any of it. I haven't had any issues flashing, but I followed the steps I quoted from the get go and do that every time. Currently I'm back on the last KitKat nightly because Netflix/Play Movies is still not working on CM12. Have you tried any of the CM11 builds? Im currently using:
http://download.cyanogenmod.org/get/jenkins/98444/cm-11-20150118-NIGHTLY-l900.zip
and I use the 20140606 GApps package found here:
http://wiki.cyanogenmod.org/w/Google_Apps#Downloads
The Commish said:
Anyone getting Netflix or Play Movies to work yet on the latest versions? It's the only thing that made me have to revert back to CM11. I tried looking over the change log but honestly I don't know what half that stuff means.?
Click to expand...
Click to collapse
Odd that Netflix and Play Movies don't work. Plex, Amazon Instant Video, MX Movie Player, and Chromecast all work.
Sent from my SPH-L900 using Tapatalk
Deleted
Related
I have installed the rom of cfx_ace-4.2-BR11 & cfx_ace-4.2-SR1 and install all my apps, change my wallpaper and stuff, butt when I reboot my phone it resets to first installation (lose my wallpaper, my apps, and settings). Can someone help me with this? I really like this ROM.
I use a HTC Desire HD.
Did you a Fullwipe before flashing the ROM?
L3moon said:
Did you a Fullwipe before flashing the ROM?
Click to expand...
Click to collapse
Yes I did full wipe, dalvek & cache
Download again. Flash rom. Reboot. Wait a few minutes. Do your settings, reboot, flash gapps, reboot.
Technically, it doesn't really matter in what order you do it (I believe it so), some people swear by x or y method. In short, you should be able to flash the rom and gapps without needing to reboot in between and without loosing anything. It's odd that you are. After flashing both of those then download your apps, that is, if you use gapps.
Sent from a dream.
Tworan said:
Yes I did full wipe, dalvek & cache
Click to expand...
Click to collapse
Dalvik and cache is not a full wipe. A full wipe is system, data, and cache.
Yes i know, tried it still doesnt work. Installed another rom that One Works fine, going to try and reinstal the rom this weekend.
Sent from my HTC Desire HD using xda app-developers app
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
yauchildchew said:
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
Click to expand...
Click to collapse
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
@gregkneitas said:
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
Click to expand...
Click to collapse
Flash gapps. Linked in cfX OP.
I do have the gapps file downloaded. I just dont know how to get it on my phone and working. I used a ROM manager app for the ROM file.
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
bananagranola said:
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
Click to expand...
Click to collapse
Like I said, I didnt flash the ROM, I used a ROM manager app.I dont know how to get to the recovery screen. Could someone please help me out with a step by step. Keep in mind vol down + power doesnt put my phone into recovery
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
bananagranola said:
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
Click to expand...
Click to collapse
Figured it out, thanks!
Next question is I downloaded Gmail App, and it wont sync with my account. I login, and everything but it just sits at the screen saying "Waiting for sync, your email will appear shortly" I've waited well over 10mins and no sync. Ideas?
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
bananagranola said:
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
Click to expand...
Click to collapse
It appears I didnt. You solved the problem! Thanks a bunch. Sorry for all the questions.
Ok last question, will adobe flash player work with this ROM? If so how can I get it. I search the market and the app isnt there. And its not on my phone either
4.2 in general doesn't support flash. You could try searching for the apk and sideloading it. Make sure you enable installation from unknown sources in Settings - Security.
sashank said:
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
So, when fixing one thing, the process could probably break some working features.
Hey everyone,
Whenever I decide to step away from stock and try a new custom ROM (latest being cm11), my phone won't go a day(well, more like 5 hours) without rebooting and hanging at the boot animation. I'm not sure if its the number of apps i install (like 30 including gapps), or something I'm missing, but its not limited to just one rom. I've tried miui, dirty unicorns, revolt, paranoidandroid, all great ROMS, but they don't LAST!
I'm really sorry if I seem like I'm repeating an already-asked question, but I've researched this problem and tried suggestions such as going back to stock and retrying, using Darkside scripts to wipe, wiping cache and dalvik cache and rebooting, wiping android.secure or moving apps away from sd card, etc. Nothing works. So for now I'm back on stock and not enjoying it I just wanted to know if theres anyone that might have any idea how to fix this?
Thanks!
EDIT: To sum up the thread so far, now instead of wiping completely everytime this occurs, i just need to do a battery pull to fix it. However, its really annoying to do 3-4 times a day. Another thing I might note is that my device is refurbished(mentioned below). I did more research and found some fix perms script reccommended by Real_Pariah, which was supposed to fix the issue. It didn't. Also same problem does happen with stock, I've just never stuck with it long enough to find out. At UltimaniumX's suggestion, I did a logcat, which is attached on the last post. Thanks UltimaniumX for your help so far!
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
UltimaniumX said:
So the way I understand it, you've flashed different custom ROMs and they work fine, but after an unspecified amount of time they decide to reboot and hang?
What is the exact process you're using to flash the custom ROMs? As well, each ROM has a specific method to get it working on your phone.
What recovery are you using and what version is it?
What radio are you using?
Click to expand...
Click to collapse
Yep, that's correct. As for exact process, usually I just full wipe everything but sd, then flash.
For my kitkat roms(paranoidandroid, cyanogenmod 11, beanstalk), i flashed used cwm recovery 6.0.4.3. For jelly bean i used either twrp 2.4.4.0 or cwm 5.x(this was in earlier attempts as that was the recovery a guide on galaxys2root instructed me to flash to root stock in the first place). All used radio UVMC6.
Even on stock it happened, but I was able to fix by wiping cache and dalvik plus removing external sd.
When I first rooted, my major issue was getting the rom to get past the animation screen while hanging, and that still occurs, though lately I've been having some success using rom manager from stock to get to cm11(without ext sd). However that does reboot eventually. The first time I was able to fix it by wiping system, android.secure, cache, and dalvik and then reflashing, but it just happened again and that method doesn't seem to be working...
It's interesting that it's happening to all different ROMS that you install. There's a possibility that it's hardware related and not software related. Though I may not be the best to offer advice (since I've only been here for about a year), I recently installed Beanstalk after going through several troubleshooting steps that I finally resolved.
I know that my friend and I both have an SG2. We installed Jedi Knight 6 (which is an older ROM now) but one of the most important steps that he missed, was that he didn't leave his phone idle for 10 minutes after booting it up for the first time. I recall he had issues with apps not working, force-closing, and irregular reboots on his phone. This may or may not been an issue for you, but for awareness sake I leave it here.
If you want you can give Beanstalk another try since I have some experience trying to get it to work. Beanstalk requires you to use a very specific recovery, and I used TWRP 2.6.1.0 straight from the author's post. I wouldn't suggest using a higher version just because KitKat is new.
- I used INFAMOUS wipe cache to clear everything, and then I did a full wipe (including preload) using TWRP.
- Install Beanstalk 4.4 and the 4.4 GAPPS
- Boot and let sit for 10 minutes.
Once you know for sure that it's been 10 minutes, run the "Android Terminal Emulator" and do a logcat. Here's how to do it:
- Type su
- Type logcat -d -f /sdcard/logcat.log , it will save a .log file where your sdcard is.
- At this point, I guess you would have to leave it running until your phone decides to reboot. Then take that file from your SD and examine it on your computer.
http://wiki.cyanogenmod.org/w/Doc:_debugging_with_logcat
See if that helps. Fixing Permissions may also help reset some of your system settings. If it does the reboot loop, try rebooting into recovery, Fix Permissions, and reboot it again.
Alright I'll try Beanstalk, nothing to lose except my cookie clicker progress
Funny same thing happened in stock but was fixed in stock recovery with simple data wipe. I remember about hearing someone downgrading to ics because of "jelly bean bugs", so if beanstalk doesn't work out I'll try that!
(Couldn't straight reply/quote cause I can't post links yet)
EDIT: can't find beanstalk thread, at least cant find one mention twrp, so i wasnt sure if i was on the right one
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
avbluestar14 said:
Alright Beanstalk up and running, waited 10 minutes, and ran logcat command, however, it went back to prompt after running, so I'm not sure if its running in the background or if it dumped the current log and stopped. I kept terminal running just in case.
Quick side question, do you know if beanstalk disables long press home for recent apps? When I try long-press home it brings up the bottom menu instead.
Also, thanks for your help
Click to expand...
Click to collapse
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
avbluestar14 said:
So Beanstalk was running all fine and dandy as usual when a random reboot occured. However this time it actually got past the bootanimation. But, it asked me to set the default launcher again and terminal wasn't working(no text on screen). So I rebooted and whaddya know, stuck at bootanimation. Tried fixing perms, didn't work.
I tried wiping cache and dalvik, and reinstalling(which after restarting twrp asked if i wanted root and i said no, maybe thats significant?), nope, now no bootanimation. :'(
I forgot to mention that it is refurbished, so maybe that's of significance? Honestly though, now I'm at a loss of ideas.
Click to expand...
Click to collapse
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
UltimaniumX said:
If you followed the logcat instructions, the file logcat.log is now saved in your sdcard. The Terminal Emulator would not show anything other than that the logcat has been created. Now all you need to do is go to your SD card and grab that file "logcat.log", it will contain a lot of information regarding the state that your phone is in. It's good that you kept the terminal emulator running otherwise the file would not populate with anything. If you can, attach the logcat so we can see it.
Beanstalk long-press home button should show recent apps like normal. I can't remember if the default launcher shows it, since I use Nova Launcher and can confirm that long-press still brings up recent apps.
Right, it seems like if this is occurring on all your ROMs, that may indicate something hardware-related. Again, it's difficult to diagnose. What happens when you go back to the stock rom? Is it T-Mobile's version and it works fine?
This may seem like a stupid question, but you have rooted your phone right?
Click to expand...
Click to collapse
yeah, stock works fine. about the logcat..I had restarted to try and fix that home button issue like an hour after starting the logcat, which means i inadvertently stopped terminal. whoops. so, i will try beanstalk again, making sure to keep terminal running i guess. sorry about that! might as well see whats in the current logfile for now. also, yes phone is rooted.
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
UltimaniumX said:
I think we're out of options at this point. My last and only recommendation that I can think of is to just install TWRP 2.6.1.0 (and it HAS to be this), and do a full wipe of the phone.
That means:
- factory reset,
- wipe data
- wipe SYSTEM
- wipe cache
- wipe dalvik
- reinstall the same UVLC3 radio (you're on Tmobile I think right?)
- install Beanstalk, install the 4.4 GAPPS (make sure it's the 4.4 apps)
- reboot the phone from recovery.
- let sit for 10minutes
- run logcat to your sdcard,
- observe and post the logcat if the system reboots itself.
Click to expand...
Click to collapse
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
avbluestar14 said:
right, isn't UVMC6 the latest? i already have beanstalk running after full wipe, if it don't work, im going to repartition with one of old gb roms and pit file and go from there. no reboot on beanstalk yet, logcat is running though. Googling it, a lot of gs2 have problem with this sort of thing it seems.
Click to expand...
Click to collapse
well beanstalk restarted on friday, can't find anything significant in logcat except for sometimes a long list of apps with perm issues,,,even stock has this reboot problem, but a battery pull+cache wipe fixes it(i hope). After googling, many have this problem with jb... maybe ill try an ics rom or something
hmm, back on cyanogenmod 11, and when it stuck at boot, a battery pull did the trick...running logcat overnight.
Well, here's the logcat, perused through, not sure if the errors I'm seeing are normal or not...honestly I wouldn't know what's contributing to the random reboot, and I'm not reporting it to cyanogenmod because I'm not sure if its a fault of their rom, my phone, or me lol
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
UltimaniumX said:
I took a look at the logcat, and there doesn't seem to be anything that would show a fatal error of some sort. Unfortunately there isn't a guide on how to read logcats, so I'm going off of the little experience that I know. Did the logcat run up until the phone reboot?
Again this may seem like a stupid question, but you are sure that you're using an SGH-989 samsung galaxy s2 and not the I-1900 right?
Click to expand...
Click to collapse
Yep, logat was running up to reboot. It is a SGH-t989, ordered straight rom tmobile site refurbished. I still think its weird how a simple battery pull fixes it though, is it corrupted memory? or partitions? or some hardware on the device?
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
UltimaniumX said:
Sorry man, looks like there really isn't any other suggestions that I have.
There is another user who seems to be having the same issue as you.
http://forum.xda-developers.com/showthread.php?t=2573854
It looks like he was able to resolve it by slowly flashing ROMS starting from 4.1.2. You will have to ask him exactly how he did it, but his story of ROM issues seems exactly the same as yours.
Click to expand...
Click to collapse
Ah I saw that thread, new plan of action:
1. Hard reset, go to stock, try it for a day, see if it randomly reboots.
2. If it does, get a replacement after Christmas since 90-day warranty. If it doesn't, try AOSP 4.1.2.
3. If AOSP 4.1.2 doesn't reboot, go from there.
Well, I'll make sure to update after I get through. Thanks again!
Well, RMA'ed and now everything's working fine, running latest beanstalk, so i guess some partitioning or hardware issue? Oh well, thanks for your help!
Q&A for [ROM][UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11]
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
my desire hd cant boot when i swich to ART mode
Mustaavalkosta said:
General:
These are UNOFFICIAL CM11.0 Kitkat Nightlies / Releases brought to you by AceEnablementProject and TeamCodefire as a continuum to CM10 and 10.1 nightlies. Builds are generated automatically each night. Process starts around 00:30 PDT. If it fails, then there will be no build until the reason for failure is taken care of which can take time. Latest 12 nightlies will be kept on the server. If you want a longer history of them, you are free to archive them yourself.
Thanks and credits:
Andromadus
CodeAuroraForum
CyanogenMod
BananaGranola
Epic Beard Men
eXistZ
Flemmard
Flinny
goo.im
Juansheng
paulb_nl
randomblame
synergye
TeamCodefire (for build server and hosting, priceless)
All the rest that have helped to construct these builds and develop software for ace directly or indirectly in the past.
Githubs:
CyanogenMod
AceEnablementProject
Changelogs:
CM Gerrit
CM Google+
Github (see above)
Installation instructions:
Download Nightlies / Releases [BasketBuild mirror]
Download gapps from here. Pico/Nano/Micro recommended, Mini/Full/Stock doesn't fit in our system partition after the ROM has been installed.
Put the files on SD card.
Reboot to recovery.
Do factory reset (ie. format /data, /cache, /sd-ext and /sdcard/.android_secure)
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Flash gapps zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
Reboot and enjoy.
Update instructions:
Download Nightlies / Releases [BasketBuild mirror]
Put the file on SD card.
Reboot to recovery.
Flash cm-11-YYYYMMDD-UNOFFICIAL-ace.zip
Remember to reflash boot.img via fastboot if you are HTCDev unlocked.
No need to flash gapps as CM backuptool script should take care of them. (Results may vary depending on which gapps package you are using.)
Reboot and enjoy.
InspireMod
http://downloads.codefi.re/mustaavalkosta/inspiremod
Kernel
Source: github
Compiler: stock AOSP gcc-4.7
Branch: cm-11.0
Kernel Version: 3.0.101
defconfig: spade_defconfig
Contact:
My Google+
My twitter
#codefireX @ freenode
Donations:
For hosting: codefi.re (use the donation button at the bottom of the page)
I don't really need your money right now but if you insist on donating to me I suggest you donate that money to EFF instead here: https://supporters.eff.org/donate
Q&A:
Q: I tried to flash the ROM and got this:
Code:
Installing update...
set_metadata_recursive: some changes failed
E:Error in /sdcard/..path od ROM.zip
(Status 7)
Installation aborted.
A: Update your recovery to one that is compatible with new recovery functions. See the list below.
4EXT Recovery Touch v1.0.0.6 RC 3 or newer
CWM 6.0.4.8 Advanced Edition / PhilZ Touch 6.29.8 or newer
TWRP 2.7.1.0 ACE or newer
Q: I've used HTC Dev unlock and flashed the rom but it won't boot. What should I do?
A: You need to extract boot.img from the zip and flash it via fastboot. If you don't have fastboot executable anymore from flashing recovery, install Android SDK platform tools (Linux users should find it from distro's package management) and then reboot to bootloader, open command prompt and navigate to the location you extracted your boot.img and type:
Code:
fastboot flash boot boot.img
You need to repeat this everytime you flash new version of this rom to ensure everything will work fluently as long as you have just basic HTC Dev unlock.
Q: Where are my developer and performance options?
A: http://goo.gl/jpS8r
Q: Feature X doesn't work, let's make 1000 posts about it to annoy everyone.
A: Please, dont. Use search and then use search again and only then report your problem with necessary logs. [Logcat guide, thanks to MusikMonk for the link]
Q: I hate you for not fixing this issue X!!!
A: I love you too.
Q: How I can build CM11.0 myself?
A: Setup a basic Android build environment.
Code:
mkdir cm11
cd cm11/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
mkdir -p .repo/local_manifests
wget https://github.com/AceEnablementProject/android/raw/cm-11.0/local_manifest.xml -O .repo/local_manifests/cm_ace.xml
repo sync
cd vendor/cm/
./get-prebuilts
cd ../../
. build/envsetup.sh
lunch cm_ace-userdebug
mka bacon
Once the build finishes you'll find your goods from out/target/product/ace/ directory.
Q: Something about something something something.
A: Ask the guy/gal next to you.
XDA:DevDB Information
[UNOFFICIAL] CyanogenMod 11 Nightlies / Releases [M11], ROM for the HTC Desire HD
Contributors
Mustaavalkosta, paulb_nl
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: M11
Beta Release Date: 2014-10-08
Created 2014-04-11
Last Updated 2014-10-09
Click to expand...
Click to collapse
some saids it`s because the partition of cache is too small
CM11 latest release freezes after first reboot
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Question about bugfixes
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
And i think it is more like off topic but how i can unlock the phone that i do not need to flash boot.img it is at the moment only HTC-Unlocked.
And very much thanks for this ROM it is great!
Thanks in advance for your answers
ag1707
Cannot dirty flash Nightlies
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Solved
Nanashi_anon said:
Hi
Since sometime around M11 release, I can not dirty flash nightlies on nightlies. The phone stuck at booting with the message "Android is upgrading / Finishing boot".
I'm using TWRP 2.7.1.0 for recovery.
1. Install Rom
2. Wipe Cache/Dalvik (I've tried without wipe too)
3. Reboot System
Am I missing something here?
I'm using non-English locale. Could it be the reason?
Best Regards,
Click to expand...
Click to collapse
Just figured it out that PA_GAPPS requires flash every update for recent ROMs.
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
XZelin said:
some saids it`s because the partition of cache is too small
Click to expand...
Click to collapse
Possibly. There are some posts about this from paulb_nl on the main thread but I didn't find them right now. They are there though.
sky141 said:
GD to all. I am trying to install CM11 latest release, first time starts ok, but after reboot it doesn't start, freezes with black screen before bootanimation. Tried to flash boot.img via ADB & also tried to install CM 10.1 SR3, nothing helped, same situation. Waiting for your replies. Thx in advance.
Click to expand...
Click to collapse
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
_Bon_Bon said:
Hey!
Would it be possible to you to add gpu overclock to that kernel?
Thx
Click to expand...
Click to collapse
Is there working GPU OC for ace? I thought it was hardware locked thus can't be overclocked via software.
ag1707 said:
Hi,
at the moment i have M10 installed but i want to ask if there is a fix in M11 included which fixes sudden restarts.
My DHD restarts over night or when i want to something (it doesnt depends on what i am doing).
And another Problem sometimes the screen wont turn on when pressing the power button only the menu keys lighten up.
Click to expand...
Click to collapse
I haven't heard any complaints about frequent reboots. I know that there are those but it's been said to happen like once a week or so. M11 may change something if your issues come from corrupted devlog partition but if it's something else, then M11 won't do anything for your reboot issue.
Nihim said:
Hi and thx for your rom!
I flashed the cm-11-20141008-UNOFFICIAL-M11-ace from releases, using twrp 2.7.1.0 for the recovery on a HTC Desire HD.
I am experiencing some lag when opening the screen or starting apps / widgets. It can take be almost instant up to 3-5 sec for the app to launch and be accessible (camera, gallery, weather, settings, mail anything really).
Also once in a while parts of the text in the screen get deformed (example here), any action by me (moving my finger around) or by the OS (some notification) fixes it.
As far as I can tell I followed your instructions properly. Is there anything I could try?
Click to expand...
Click to collapse
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Mustaavalkosta said:
It's a bit slow but I suppose that's understandable considering we are talking about 4 year old device. People have reported it gets slower the more apps you install. I'm not sure why.
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Nihim said:
Yea that is very much true, this might sound bad but would is there some other version you would recommend (even if it's a previous android release) which would be snappier? (your ROM so far is absolutely fine outside of that lag which as you stated is probably because DHDs hardware can't handle it).
As for that graphics glitch can't think of something, any apps were installed from play store (not restored by titanium for example) it happens on different ones but a lot more often on k-9 email client (from which the screenshot is).
If there is something that you would like me to try, feel free to tell me, though any action on the screen restores it to its normal way.
Click to expand...
Click to collapse
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly. I haven't been using other ROMs that much during the time I've kept my own stuff going here so I can't really recommend anything else. A fellow user may be a bit less biased to recommend other options.
I'll see if I can catch that graphical glitch with K-9 myself. Thanks for reporting it!
Mustaavalkosta said:
I'm seeing that kind corruption on the screen graphics for the first time. Any chance of figuring out how to reproduce it and write step-by-step what to do so I could maybe replicate the issue on my end?
Click to expand...
Click to collapse
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
paulb_nl said:
I get that black boxes glitch with the standard Email app all the time. They usually go away in less than a second. I also checked for those when I was testing the 4.4 adreno drivers and it was still not fixed.
Click to expand...
Click to collapse
Oh ok. If it has been mentioned in the development thread, I've just probably forgotten about it.
Mustaavalkosta said:
I don't mind people looking for better solution for their needs. You may want to try my CM10.1 builds which were noticeably faster if I recall correctly.
Click to expand...
Click to collapse
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Nihim said:
Thanks! What would be the proper way to backup the whole "phone" so I can switch back and forth between roms? Atm I 'm only backing up apps & data with titanium.
Click to expand...
Click to collapse
Doing a backup in recovery should be sufficient to backup everything except sdcard.
Mustaavalkosta said:
Are you using the latest recoveries mentioned in the first post's Q&A section in the development thread? If your issue is what I think it is, full wipe with the previously mentioned recoveries should fix it.
Click to expand...
Click to collapse
Thx 4 yours above. I'm using latest 4ext recovery touch + full wipe, of course. Will try to do something with partition.
Update from M11 to Nightly
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Christian1987 said:
It is possible to flash the newest nightly over the M11 release?
Or I need a full wipe.
Click to expand...
Click to collapse
Well, generally it's recommended to wipe if you switch from one to another but it may work in this case without wiping. Make a nandroid backup and try it.
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
prufessor_oak said:
My battery dies really fast. Do you guys have a recommendation in terms of which battery to get? Link it here. Thanks.
Click to expand...
Click to collapse
You can get original Desire HD battery on ebay cheaply, no point looking at other batteries which cost almost the same. Just look for one in your region.
Install Wakelock Detector from the Play store and find out what is causing your battery drain. Depending on phone use it should be able to last all day, 2 days if just left on standby all the time. Screen on all the time will be around 3-4 hours.
[Q&A] [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
Q&A for [ROM][4.4.4/KTU84P][OMNIROM][LINARO/OPTIMIZED] FML: Fork My Life (10/08/2014)
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. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
kbfirebreather said:
Anyone having problems with torch on the beta build? Not turning on LED for me, and keeps force closing.
Click to expand...
Click to collapse
I'm having issues with it as well. Sometimes it sits there thinking it works, other times it waits a few seconds and then crashes. It worked for a day...not sure what I did past that to break it.
Is there anyway to overclock the latest update? I know I can't install a new kernel with this ROM.
Also, any option for Volume Rocker unlock? I'm new to this ROM, coming from CM. I kinda rely on that option, since my power button is kinda on the fritz.
Fml 4.4.4 beta
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
vicious01 said:
I love this rom but my after clean flashing it the gallery and the camera will not show
Pictures. Is there anything I can do to fix it so I can get camera and gallery to work?
Click to expand...
Click to collapse
Which gapps package are you using? I'm using the modular mini. Try another clean flash (sorry) and use a different package than you are now.
aaa
nothing
I've tried a lot of KitKat ROMs, but each one with a lot of issues. So I came back to the 4.3, it surprised me for his stability (1 year with bugged ROM make you feel that your phone sucks more than it actually does [no, it doesn't, I love it!]) and I decided to don't try your FML. Now I can't wait for Lollipop, and even if I haven't tried your ROM, I trust in it and I think it will be the best choice. Good work and thanks!
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
Samsung Galaxy Nexus FML Lollipop
Hello. I hope this is the right place to post this. I have less than 10 posts so I have to post here...
I've tried to install your FML rom (the lollipop beta) on my Samsung Galaxy Nexus, but I seem to be having the same issue that coleburns is having. Namely, I flashed the rom from recovery, but when I reboot the phone, it shows the Google splash screen and then keep rebooting over and over again.
I understand that the first boot is supposed to take some time, but I've left it for over an hour and it still won't boot into the OS. Is there a step I'm missing?
I'm using the custom version of TWRP that you linked to in the first post. I also formatted all the partitions to ext4. Before flashing the rom, I performed the factory reset from recovery and also cleared the /system folder.
I've managed to load on the KitKat version of your ROM just fine...I can't work out what I'm doing wrong!
Anyway, if you need some logs or something to help debug the issue, let me know. Or, if I'm doing something wrong, could you please let me know? I'm very keen to try Lollipop!
Thanks.
Could some1 possibly upload a video of this good work ? Got a maguro and I'm very curious
thx in advance!
lollipop build 2
Haven't seen anybody ask... In your changelog for lollipop you said the rom takes a VERY LENGTHY FLASH TIME. Are we looking at 5 minutes or more?
edit: VERY LONG... over 5 minutes for me
This is the best rom ever!
When you said, "These builds are very early! They aren't daily-driver-stable, but they are progressing extremely fast." I was expecting junk, then I tried it. I was a big fan of your kit kat rom as well but once I tried this android l rom I fell in love. I have used this all day and it is extremly stable. The only bug I have to report that isnt even a need is the app drawer is the app drawer animation is very laggy. I tried enableing 2d gpu acceleration just in case that had something to do with it but it still didnt help. Any suggestions would be great. Oh and yes I have tried closing other apps, multitasking is no issue with this rom, the memory management is great. I thank you so much for such a great rom, keep up the amazing work.
Installing TWRP Problem
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Mondos said:
So I am currently on CWM and am trying to switch over to TWRP. I'm have a slight problem. When I install TWRP (via twrp manager app), I am also using the recommended custom twrp from the first post. It installs successfully, then I go into reboot options and reboot into recovery...and it's still CWM. I've tried it multiple times. I am rooted, I do have busybox installed, I can't figure out what the problem is. IM STUCK WITH CWM, HALP!
Click to expand...
Click to collapse
Download the file in the OP for FML (twrp 2.7.1). Flash with Flashify. Reboot to recovery.
Don't worry too much about it not working. It's fully working for me but it's pretty slow when you actually need to use it. If you get it going it will pick up the pace, but it's far from usable, being in an app for longer than a minute and touching the home screen button will freeze it up for 10 seconds before it takes you to an empty screen that takes another few seconds to load all the apps and widgets back in. I'd wait for a newer release.
Feedback
Hello i have tried the older version and it was great but i really need my camera so i went back to 4.4 but i appreciate you so much thanks !
Please fix the camera asap and i will definitely install this rom ! and i tried to install the new version but it said Error Binary something in TWRP recovery what can i do thanks!
Q
Is the camera fixed yet?
Notification Light
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
TheIbanez97 said:
Is there a way to disable the notification light while the phone is plugged in via USB? It's a little annoying to be on while I'm sleeping. It's not a huge issue though.
Click to expand...
Click to collapse
I don't think so.
I found that the miscellaneous section of the battery stats was taking up most of the battery usage. I don't have any apps installed other than the stock standard.
I have a Samsung S3 L710 on Virgin Mobile.
I've been running a Kitkat ROM; Conquest Singularity; for a very long time and wanted a change. I wanted to try out a ROM running Lollipop.
This is were my issues have started.
I updated to the latest TeamWin recovery and so far have clean flashed 3 different ROMS.
1 ROM the PAC ROM did not stay on the phone long at all because it was having trouble staying connected to my wifi. Wasn't on long enough to see if it has the same problem as the other ROMs listed below.
The other 2 ROMs I've tried, Liquid Smooth and currently on the phone OctOS. Both these ROMs will I think randomly reboot. (I'll get to "randomly" part in a bit.)
One thing I've done that I know is not recommended, is using TiB to replace data on a new flash. My question here is, if you have information in some apps that can not be saved in anyway way, how would one do this without using TiB?
Now onto the random reboots. I know most happened when I was playing Ingress on both ROMs. Ingress uses a lot of resources and being on for a while gets the phone pretty warm. Not sure if it's overheating the phone causing it to be unstable or what.
I have not adjusted any kernel CPU settings on any ROM that I've installed. Everything is left stock. Not sure if the developer has the settings overclocked from an install and maybe this is making the phone unstable.
Basically I'm frustrated to why I seem to be the only person getting reboots, and I know that from what is written no one will have any ideas why. I'm just venting. Now that I've been playing with LP ROMs the past few days, I'd like to keep one on the phone working properly.
Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out
lvpre said:
Lollipop roms are still buggy since they aren't made for our device. Have you tried the cm official or aicp roms? You will never have the stability as touchwiz on this phone. They have made a ton of improvement of them though.
With titanium backup, you shouldn't backup and restore app/data to system apps. That's when things get strange. Most non-system apps should be fine.
You could always take a logcat if the reboot has in the exact same spot. That would help the devs out
Click to expand...
Click to collapse
Well that might explain it.
Haven't tried CM yet because most the ROM's required TWRP recovery and CM takes a different one.
I tried flashing AICP, but the Gapps didn't flash. Said wrong ROM or something. I only had the one Gapps on my internal storage so I flashed the OctOS instead. Just downloaded the Gapps listed on the AICP page. May try flashing that one now. Just so sick of reinstalling all my apps..... :silly:
As for TiB. I'm good then. I never do any system apps. I must have misunderstood about that. Been a long time since I've flashed anything.
Here's how I flashed aicp on my phone, using the modified TWRP that's made specially for Virgin/boost d2spr made by Lrs121. 1. Flash the latest aicp nightly. 2. Flash latest banks gapps: http://fitsnugly.euroskank.com/?rom=banks&device=gapps. 3. Flash APN fix: http://androidforums.com/threads/vi...rgin-mobile-apn-fix-wip-cm-aosp-4-4-x.840298/ 4. Boot into ROM, and reboot into recovery as soon as it boots up. 5. Reflash the ROM and gapps (but don't wipe anything this time).
That should get you up and running, with LTE and the APNs configured properly.
Thanks all for the help.
Been running the 7/3 build for a few days now without any problems. May flash the 7/7 ver 10 build very soon.
Powered_By_Linux
I tried the APN fix on a Kitkat ROM some time ago and did not help. Found 8SMS messenger with the added line fix and was able to get my MMS messages then. May try the APN fix in the order that you suggested and see if I can go back to the Handscent messenger. I like that app better the 8SMS but was not able to get MMS messages.
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.
elgecko said:
One last question for anyone willing to answer. Any easy way to update the PRL?
Didn't see anything when snooping around the system menus.
Found this link for easy PRL updates; http://forum.xda-developers.com/showthread.php?p=25470797#post25470797 on ASOP Roms, but not sure if AICP is a ASOP ROM as it doesn't seem to work. I can get the script widgets on my homescreen, but nothing happens when I click on them, other then some kind of error message.
Click to expand...
Click to collapse
Make a backup of AICP. Then you'll have to flash back to a TouchWiz ROM, update PRL, then flash the AICP backup you made. Your updated PRL will stick.
You can also use a PRL from the PRL thread.
http://forum.xda-developers.com/showthread.php?p=35576100
Flash a ROM like Wicked X or Tribute (you don't need your MSL). Download the PRL you want from the many listed in the thread, extract from zip, rename the PRL "TEST.prl" (without quotes), place on your internal SD, open your dialer and press ##DATA# to enter the hidden menu, tap View, scroll down to PRL Write, tap, and select. Your phone will reboot and you'll have yourself the PRL of your choosing.
Some people have good results from using these PRLs while others do not. Personally, I'm on Boost and have been running Sprint PRLs for years lol.
Hope this helps :thumbup:
EDIT......
NOTE- REMEMBER TO FACTORY RESET, WIPE CACHE, DALVIK CACHE, AND WIPE YOUR INTERNAL SD BEFORE RESTORING YOUR AICP BACKUP AFTER EITHER DOING A PRL UPDATE OR FLASHING THE ONE OF YOUR CHOOSING.
Sent from my SPH-L710 using Xparent Purple Tapatalk 2