Related
Back in the days when I used to flash my "mytouch" every other I never seemed to have the problems I get now. there was no such app as "rom manager" and yet when you partitioned, wiped data and dalvik then flashed the only glitched i would ever get seemed to end up in the change log for the next update, meaning everybody had this. So my question is why now with the incredible when i wipe data and dalvik then flash a new rom why do I get things like gmail not sending attachments, message app problems and all sorts of random annoyance that requires master reset or wipe and reflash, back in the "mytouch" days I only got these kind of errors when i did not wipe. am I missing something? I love and appreciate the community and developers and though as i read this back it sounds like a rant its not, i just don't understand if im missing something? the process seems so streamlined with "rom manager" compared to pulling sd cards im curious why i don't get similar results.
Which Rom are you using? I haven't had those issues yet.
Using Skyraider 3 vanilla
Sent from my ADR6300 using XDA App
Some of us are stuck with a flawless leaked froyo but worth a dead GPS.Finally got mines to work.Here's the steps.
1: with clockworkmod flash this stock zip.
http://www.sdx-downloads.com/devs/noobnl/stock.epic.DI18.rom.update.zip
2: boot up, then reflash froyo. Gps got a look in 6 seconds.
What was your before/after testing methodology?
AndrewZorn said:
What was your before/after testing methodology?
Click to expand...
Click to collapse
Flashed to 4.2 from 4.1 in which I had a stock epic rom but just rooted. 4.1 had dead gps, so I dumped 4.2 to see I'd the fix was there. Nope. Rewiped data and clear all cache on the 4.2. Did that 3 times and still dead gps. Reformatted and clear cached and dumped 4.1. Did that 3 times, and still dead gps. Many have commented to flash back to stock and reflash 4.2 afterwards. Did that with clockworkmod and gps took about 4 to 5 seconds with gps lock.
Sent from my SPH-D700 using XDA App
Thank you! Trying this now.
Edit: Reporting in
I wiped everything, installed the DI18 update, installed froyo, and no go on the gps.
I wiped everything, installed DI18, booted and wasn't getting a get a lock (at least not quickly). So I rebooted DI18, and this time got a good lock. Then I shut down, flashed 2.2, and it works!
If anyone has trouble, make sure to boot into DI18. I did twice just to make sure I had a lock and good assistance data since the 2.2 zip doesn't wipe everything. I'm going to go back and flash my /data back now and check once again. As long as GPS still works after that, I'm set.
Thanks, SINNN.
Tried this method and was still not able to get a GPS lock. Wiped everything x3 between flashes. Still no lock with Sprint Nav or Google Nav.
This won't do ****. Read up on the bug that causes the problem and you will understand.
Sent from my SPH-D700 using XDA App
Ok. If this fails like some have said.Do these steps and its guaranteed to work.
1: with clockwork data format, clear cache and clear danluk cache, then flash dl18 stock that I linked inn the 1st post.
2:boot into stock 2.1
3:Get google maps to lock on gps.
4:Shut down. Boot into clockworkmod. Format data, Clear cache,clear danvik cache. Then fo back to the first menu on clockworkmod and flash the froyo 4.2 zip file. Once flashed.Just for extra luck, stay on clockwork and do the data format, clear cache and finally clear the danlik cache.
5: Finally boot 4.2. Go to the market and get "gps status & gps toolbox" combo app thats free.
6: Turn your gps on and launch the gps status app and under settings go to clear gps cache and redownload new data.
7: launch NAV or google maps. You WILL get a lock almost under 4 seconds.
Just did these steps on my gf Epic wich had the same gps problem after rooting and flashing the first leak froyo and them flashing the 4.2 froyo.
Now she has GPS.
Bit long but guarrantee to work.Don't blame me for 500$ paper weight! Do on your own risk. I did.
Sent from my SPH-D700 using XDA App
It worked! Last time I didn't do step 3...
Gmaps, GNav and Sprint Nav all worked. The real test is will it still work a few days from now after I've used it a few times... That cache bug is liable to show its ugly face.
Thanks for your help!
insanity213 said:
It worked! Last time I didn't do step 3...
Gmaps, GNav and Sprint Nav all worked. The real test is will it still work a few days from now after I've used it a few times... That cache bug is liable to show its ugly face.
Thanks for your help!
Click to expand...
Click to collapse
yup. I'm curious to see what will happen myself. But at least we know what to do I'd we need gps to work asap.
Sent from my SPH-D700 using XDA App
insanity213 said:
It worked! Last time I didn't do step 3...
Gmaps, GNav and Sprint Nav all worked. The real test is will it still work a few days from now after I've used it a few times... That cache bug is liable to show its ugly face.
Thanks for your help!
Click to expand...
Click to collapse
Booting into DI18 and acquiring a lock seems to be the necessary part of this. I've been flashing things all day and as long as I boot into DI18 and get a GPS lock in GPS Status, I can flash 2.2 directly over it without wiping anything before hand. Then boot into 2.2 and gps should work. Going back and flashing /data will bring back all your apps and settings and gps should continue to work as it did on mine.
This "Fix" only works for about a day or so, then it goes back to nothing / takes forever to acquire a lock.
Just curious, I do this on mine and it seems to work.
1) Reboot the phone
2) go to Settings --> About Phone --> System Updates --> Update Profile AND PRL
3) try again
It just doesn't make sense how it can work so good sometimes, then just stop working.
SINNN said:
Ok. If this fails like some have said.Do these steps and its guaranteed to work.
1: with clockwork data format, clear cache and clear danluk cache, then flash dl18 stock that I linked inn the 1st post.
2:boot into stock 2.1
3:Get google maps to lock on gps.
4:Shut down. Boot into clockworkmod. Format data, Clear cache,clear danvik cache. Then fo back to the first menu on clockworkmod and flash the froyo 4.2 zip file. Once flashed.Just for extra luck, stay on clockwork and do the data format, clear cache and finally clear the danlik cache.
5: Finally boot 4.2. Go to the market and get "gps status & gps toolbox" combo app thats free.
6: Turn your gps on and launch the gps status app and under settings go to clear gps cache and redownload new data.
7: launch NAV or google maps. You WILL get a lock almost under 4 seconds.
Just did these steps on my gf Epic wich had the same gps problem after rooting and flashing the first leak froyo and them flashing the 4.2 froyo.
Now she has GPS.
Bit long but guarrantee to work.Don't blame me for 500$ paper weight! Do on your own risk. I did.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
youre an idiot if you think any of those steps have anything to do with fixing the gps
Agree does not make sense if you look at it in tech... Way.
Sent from my SPH-D700 using Tapatalk
The only known method that gives me 5 meters is have sprint navigation running then goto google maps(this only works under clear skys not in the city with buildings)
Sent from my SPH-D700 using Tapatalk
nobloat said:
youre an idiot if you think any of those steps have anything to do with fixing the gps
Click to expand...
Click to collapse
Instead of calling people names, why don't you enlighten us as to why this doesn't fix gps. And while you're at it, tell me why I get gps in 2.2 when I do it this way and no gps in 2.2 when I flash differently or try other fixes.
insanity213 said:
It worked! Last time I didn't do step 3...
Gmaps, GNav and Sprint Nav all worked. The real test is will it still work a few days from now after I've used it a few times... That cache bug is liable to show its ugly face.
Thanks for your help!
Click to expand...
Click to collapse
If it does you could try
##GPSCLRX#
and use your MSL code (getprop from terminal and search for it) to reset the GPS which might clear the cache since the old "cold start" GPS menu code is not working.
DiGi760 said:
Instead of calling people names, why don't you enlighten us as to why this doesn't fix gps. And while you're at it, tell me why I get gps in 2.2 when I do it this way and no gps in 2.2 when I flash differently or try other fixes.
Click to expand...
Click to collapse
Ignore him. Obviously he is unable to communicate at any level of worth while commentary.
I downloaded the GPS status & toolbox and have gone into the setting but cannot find where to reset the gps cache and download new data. Is the app "GPS Status & Toolbox" or "GSP Status & GPS Toolbox"? I could only find the first one. Please help.
insanity213 said:
It worked! Last time I didn't do step 3...
Gmaps, GNav and Sprint Nav all worked. The real test is will it still work a few days from now after I've used it a few times... That cache bug is liable to show its ugly face.
Thanks for your help!
Click to expand...
Click to collapse
Cache bug is still present on what we have so far.
Most of this info may be extraneous, but I'll throw it in here just in case.
A few days ago, I decided to root my Evo 4G from the stock, 2.2 OS (HTC Sense?) using the Unrevoked website (using a PC running XP). It worked fine and got me rooted. Trouble began to arise when I attempted to install new ROMs such as CM-6 and Salvage. I decided to fork out a few bucks and pay for the ROM Manager Pro app, thinking that it would save me considerable hassle. After downloading the most recent CyanogenMod 7.0.0-RC2 through the app, I selected the "Install Gapps as well" option but did NOT check "Wipe Data and Cache" before letting the app do its work of installing and flashing and whatever for me. Upon completion of the installation, my phone then automatically rebooted normally, but became stuck on the boot image of the android on the skateboard with the spinning arrow. I let that sit for about 6 hours (I went to bed) thinking it was just first-time setup before I battery-pulled and booted into recovery, restored my original settings, and started over. This time I did everything the same except remembered to check "Wipe Data and Cache," as an online tutorial told me I ought to when switching from stock to another ROM, and it installed and booted correctly. I ran CM-7 for a day before deciding to try out a different ROM, downloading and installing it through the same interface, ROM Manager Pro. Everything went well until it got stuck, again, at the boot image. After about 30 min I battery-pulled and tried to restore back to CM-7, only to be greeted by another endless boot image. I was able to restore back to my original backup, but am now back to square one. What the heck am I doing wrong?
EDIT: That original backup I mentioned was made immediately after rooting the phone in preparation to install CM-7.
Sorry my technical knowledge is grossly lacking, I just got into this game. Patience and any help is GREATLY appreciated.
When switching from one rom to another, it is always important to remember to wipe data and cache. There are a few rare cases that it is not necessary to do this, but I really recommend that if you are just starting out, wipe them both for good measure until you learn enough that you can tell when you can get away with not wiping. Also, I know that one common problem that people experience with Rom Manager is that Unrevoked contains the Amon_RA recovery image, and Rom Manager is designed to with with the Clockwordmod recovery. In Rom Manager, you should be able to see which one you are currently using, and you should also be able to use Rom Manager to download and flash the latest Clockworkmod recovery. I too use Rom Manager as a convenient way of making sure that my rom is up to date, and to download roms, but I recommend that when you want to change roms, you do it by booting into recovery mode, and performing the wipe and install manually, as I have found that this method will help prevent errors like boot loops. I hope this helps!
P.S. Feel free to PM me if you ever need any help.
Sent from my DESTROYED Evo using XDA Premium app
So, for example, if I wanted to restore back to my CM-7 backup, would I want to boot into recovery and just restore to the backup or re-flash the ROM, then boot into recovery and try to restore it? I'm still getting the endless boot image.
Oh, and I am running clockworkmod, as per the instructions for ROM Manager.
Thanks for the quick reply!
Move CM7-RC2.zip and the gapps.zip (or whatever its name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip(s) [CM7, Gapps] from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
totalanonymity said:
Move CM7-RC2.zip (or whatever it's name; ex: filename.zip) to the root of your SD card by plugging it into your computer via USB and mounting it as a drive. Go ahead and exit all that.
Turn off your phone.
Hold volume down + power.
Go to Recovery.
Wipe the following: data/factory reset, cache, (in Advanced, accessed from same menu) wipe dalvik.
Go back.
Install .zip from SD.
Choose your .zip from your card, flash, and presto!
I'm not too experienced with ROM Manager as I do not use it whatsoever, but I know the above stated method should work perfectly.
Furthermore,
I'm not sure if a format_all.zip should be used here with CM7. If someone who knows would like to chime in about this, that'd be great.
Click to expand...
Click to collapse
This is the way I would flash any roms that you want from here on out.
I have used CM7 and have not had to use the format.zip from calk, so I don't think it is absolutely necessary, but it probably wouldn't hurt.
Sent from my DESTROYED Evo using XDA Premium app
I recommend flashing the format all zip whenever switching ROMs. It completely formats the various partitions and leaves a blank slate for the new ROM to be installed. I also recommend using ROM Manager to flash Amon_Ra recovery and do everything manually instead of using ROM Manager. People seem to have a lot less problems with Amon, and I have never had any issues flashing ROMs or kernels or anything with it.
You won't be able to restore a Clockwork backup with it but it never hurts to just flash a new ROM and restore your Titanium backups, assuming that you made them.
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
RossGoldenstein said:
Wow, thanks all for the fast replies!
Ok, I now have Destroyer installed and working (finally!), but I am experiencing the apparently common black-on-black text box problem. I downloaded the .zip to be flashed to fix this, but am not sure how to proceed. Do I just do the exact same thing as flashing a new ROM entirely or is there something special I need to do to let the phone know that it is an update?
Click to expand...
Click to collapse
Not sure with ROM Manager but you can flash that from recovery the same way you flash a ROM. I'm sure there is an option in ROM Manager to flash it, I just couldn't tell you where. Do not wipe anything before flashing that though. Only wipe when flashing ROMs and kernels.
Go back into Recovery and flash that .zip the exact same way you flashed the ROM. Minus the data wipe.
Others: Does he wipe cache/dalvik as well? I've seen some posts say to do that when flashing mods that are flashable .zip and some don't. I've done both ways and seen no negative consequences (as of yet).
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Wiping the cache and dalvik most likely isn't necessary but it can never hurt.
RossGoldenstein said:
Yeah, that last post was dumb, I clicked "Submit" before I tried anything on my own. Flashing it the exact same way minus data wipe worked perfectly, though the prediction boxes for input in the market app (when you hit "search" and start typing, the things that drop down to give suggestions) still appear to be black on black. Bleh.
Also, the Dalvic wipe before installing was a good idea; I don't know for sure if it made a difference but a good habit to get into.
EDIT: By the way, this has got to be the least grammatical/spelling errors in a forum thread I've ever seen. I think I may like this site...
Click to expand...
Click to collapse
I'm really new to this stuff myself (rooted for the first time ~2 days ago) and so I'm unsure how to further fix the blacked out predictions in the Market. Perhaps you could try contacting those within the thread of the ROM you downloaded, specifically citing that you installed the initial blacked out fix so that they don't redirect you back to the fix you've already applied, testing your patience and furthering your wait for perfection.
Aye, this site has got to be full of some of the most fluent English-speaking persons I've found on the internet.
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Anthonyl123 said:
Sorry if im a total noob at posting but spare me, when I have a chance ill change the specifics and have it in the appropriate forum but at the moment let me describe the issue at hand. Im currently using hyperdrive on my sprint galaxy s3 and at least more than 8 times a day I open a simple app or attempt to multitask. The phone freezes and I have to keep rebooting and rebooting until it finally works. Has anyone other than me had this issue?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Switch ROMs.
Maybe your phone just doesn't play nice with the Hyperdrive ROM. Try out a new one, or do a clean install of it and see if that fixes it!
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Mr._Happy said:
Switch ROMs?
Well, I suppose it's a fix.
The thing is, what if you want Hyperdrive to work?
I have been getting random reboots, which led to boot looping. I have done a clean re-install, but mysteriously lost the multi-view launcher.
Any ideas? Besides switching ROMS...
Click to expand...
Click to collapse
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
topherk said:
The difficult thing when trying to troubleshoot Roms like Hyperdrive is that unless you document exactly what option you chose (which kernel, mod, theme, etc) in the Aroma installer, it'll be difficult to replicate your specific situation. Do you happen to know which settings you chose (maybe walk us through page-by-page in Aroma). Than we'd be able to help troubleshoot what's going on in your phone.
That being said, I'll walk you through some generic fixes for reboots/bootloops. You can try each one in order, and if #1 doesn't work, try #2, so on and so forth. They may work, but no guarantee.
Clear Cache & Dalvik Cache: This probably won't help, but there's a long shot that it would.
Fix permissions in TWRP or CWM: If it's a system app that somehow got installed incorrectly, this will help fix that issue.
Reinstall the Rom with a "so fresh and so clean clean" wipe: Wipe Cache, Dalvik Cache, /data, and /system. Make sure your rom zip file is in an accessible location, because wiping system erases your system (you won't be able to boot).
Reinstall the Rom without any mods: If you really want to take the time to flash the Rom multiple times, I'd say flash the Rom without any major mods. If nothing is broken, you can reinstall it again (after a so-fresh-and-so-clean-clean wipe) with another mod installed. It might takes hours, but if there's something inherently broken in the ROM, you'd be able to find the culprit if you do it this way.
Do not restore apps/data from TiBu: A lot of people have had issues because they've restored system apps/data through Titanium backup (TiBu). I still use TiBu for a lot of my backup needs, but I never restore system apps with it.
That's all I really got in terms of fixing the problem. I hope you can get your phone working the way you like.
Click to expand...
Click to collapse
Ive done options 1 and 2 but here is what I have installed on my phone
When I ran the aroma installer I chose the option to run a full installation with the devs choice of mods and stuff etc. So I have the tw launcher installed along with the multiwindow mod and pretty much everything else.
Sent from my SPH-L710 using xda app-developers app
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