yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] wernst:
Hey Guys,

Though I was originally flashing ROMs with the OG Droid back when it came out, for the past 2.5 years of Razr MAXX (Verizon) ownership I'm been running Rooted-stock until this weekend.

After reading hundreds of posts in this thread, this weekend I installed the latest SafeStrap, installed CM11 Milestone 5 (from 04/05) and GAPPS-KK, along with many apps and configured them, and other than wireless connectivity issues, it was working very well. The Orange Bars and LTE almost never coming up prompted me to Dirty Flash to the 4/20 nightly, based on comments of how things after 4/16 are looking pretty good.

"Dirty Flash" was a new term to me, so I want to double-check I did it right:

1. Reboot to Safestrap. Ensure Slot 1 is still active. Backup current Slot 1 contents just in case.

2. Wipe Cache and Dalvik.

3. Install the 04/20 nightly zip.

4. Install the GAPPS zip.

5. Wipe Cache and Dalvik again.

6. Reboot. Let things settle.

7. Reboot again.

Any problem with this? And Dirty Flashing is fine for updating Nightlies that aren't too far apart, right?

4/20 seems good, and it seemed it was able to hang on to LTE a bit better, but Orange Bars were still a problem.

I followed these steps (found in previous posts and links - apologies in advance for not crediting those who found/wrote theses tips/instructions) to dramatically improve LTE acquisition and my Orange Bars issue seems to be nearly gone (we shall see...):

A: Set the Preferred Network Type to: CDMA+LTE/EVDO

B: Force a reload of apns-conf.xml to ensure the new nightly's APN info is loaded:

1) Enable airplane mode; 2) Restart phone; 3) Settings > Mobile networks should now show "Access point names" as a menu you can enter; 4) In Access point names menu, choose "Reset to default" from the drop menu; 5) Disable airplane mode

C: Set the correct APN setting with these steps:

Settings > Mobile Networks > CDMA Subscription: Set it to RUIM/SIM

then while you are connected to a wifi network

Settings > Mobile Networks > Access Point Names: Select LTE Verizon Internet

Then back out of everything and reboot normally ASAP before doing anything else with the phone.

So, thanks for the tips, and please, let me know if I'm Dirty Flashing the right way.

Thanks,

Warr
[Motorola Droid RAZR] Ohmster:
LOL! Man, you are sooooooooo far from "dirty flashing" you might as well be "Mr. Clean". :laugh:

The Official Install Guide is right on page 1 and is maintained, current, and up to date. Use those instructions and if you have problems, THEN you can address the specific issue that you have, not anticipate problems you do not have.

You went way above and beyond what one normally has to do to install a good build of cm11. A "Clean Install" would be to wipe the rom slot in cm11. Either by wiping all the partitions or deleting the slot and recreating it or wiping all the partitions. Deleting and recreating the slot is a nice way because you can bump up the size of your data or other partitions if you run a lot of apps. Then flash cm11 and pa-gapps. Wipe dalvik and cache again and reboot. Follow the setup wizard and your are done, install what you like. That is a "clean install".

"Dirty Flashing" is a term used when someone updates what they currently have without wiping everything first. So, if you go to Settings, About Phone, CyanogenMod Updates, and touch a new build to download and then install it, that would run scripts to put you in recovery, "hands off", wipe your cache and dalvik, and install the new rom over the old. This is an OTA or "Over The Air" update, some call it a dirty flash. I do not like that term for OTA because OTA was meant to be used to update your phone easily and it does work quite well.

A real "dirty flash" is for you to enter Safe Strap and flash the new build without wiping anything and rebooting. cm11 is pretty good now and can stand on it's own legs. All the things you did for APN should not be necessary but make sure your mobile network is set to CDMA+LTE/EVDO. If you are having network problems, THEN you can take the additional steps. Orange bars come and go. Even if cm11 were perfect, you would still have occasional orange bars because you are trying to maintain a 24/7 connection to Google servers. Networks always choke here and there so occasional orange bars is normal, but it should not be "all the time".

The M5 build is not a stellar build of cm11. I would suggest you pick something up to 04/21 because the recent builds have been very good. As of 04/22, a LOT of changes will be put into the new build and it might get sticky for a while if it comes with bugs. 04/22 could be good, it could be buggy. I know that anything a week prior to it are good builds. Dump M5 and try 04/21. Yes, you can do it from Settings, about phone, cm updates. Touch once to download, again at the door icon to install, hands off. If that gives you problems, then redo it clean by wiping the slot, recreating it, and flashing cm11 and pa-gapps. Good luck. :good:
[Motorola Droid RAZR] wernst:
Thanks. I did indeed follow the steps on Post 1 for installing M5 clean initially, and I then used it for the weekend until last night, when the near-constant Orange Bars and near-never LTE was too much to bear,

So to be clear here, I did the full-on-wipe and clean install of M5, and then last night did the "Dirty Flash" procedure I outlined to update to 4/20 while maintaining the apps and settings I had installed last night. I would like to confirm that these steps are OK for doing a Nightly update to a working ROM.

Then this morning, still having LTE lock-on problems and still some Orange Bars, I did the the Steps A, B, and C, which significantly improved things.

Thanks,

Warr
[Motorola Droid RAZR] Ohmster:
Yeah, you pretty much got it right. Gold Star Student! (There are no gold star smilies or I would give you one.) ;)

Yes, the OTA update is a very quick, easy way to install new updates. It does contain all the necessary prep and wipe scripts to install your update and wipe the necessary partitions clean, then reboot to system. It is amazing to watch as this is a totally "hands off" procedure. This does not always work if things in cm11 change so drastically as to require you to install clean. This does not happen often and you will know if "it didn't work right" so you can then install clean. If changing to new versions, i.e.: cm10 to cm11, the you must install clean!

You did good by ditching M5, that thing was outdated 5 days after it was released. The nightlies are where all the action is, the new improvements, bug fixes, and features added. But there are good ones and some bad ones. We all report when we install a new build (Some of us do.), how we installed it (OTA or Clean), how it went, and any problems encountered or noticed in the new build. A follow up post of how is it holding up and what new problems do you have (Always name the build by the release date such as 04/20) now. This is a "Gold Mine" of information for those that want to update but cannot risk losing their phone for a while, trying to fix bugs or reinstalling or restoring a backup. You too can use this gold mine system to find out which nightlies to go for and which to avoid.

Since you still had problems after updating, the ABC steps you did were the correct procedure to follow and implement. As a matter of fact, you did such a good job of making a really nice list, I myself will copy it and save to text file for future issues I may encounter. I like to make and save my own help files, usually by using the Adobe pdf file plugin to save a page or post as a handy pdf help file or guide. Thanks for the handy how-to guide. :laugh:

If you found the post useful or helpful in any significant way, please be nice and tap the Thanks button under my name on the post(s) you found helpful. Same thing goes for anyone that really helps you or that you find to be particularly helpful. That is the "official XDA method of thanking someone".

You are doing extremely well for a beginner, if that is what you are. Keep up the good work! :good:
[Motorola Droid RAZR] wernst:
Thanks for the confirmation that I'm doing things right. Not totally new at this, but new since SafeStrap was invented.

I'll post another question in another post.

-Warr

---------- Post added at 03:28 PM ---------- Previous post was at 03:18 PM ----------
[Motorola Droid RAZR] deboyz1014:
Ok so I'm coming from Slimkat 3.2 over stock slot. Wiped system/data/cache/dalvik, install nightlies 4/21, install gapps, reboot and everything is working fine except 2 items. I even tried this on 3/30 and 4/20 just to see if it make any difference and it does not.

1. Tethering, I can set it up and my other devices sees it, it just wont connect. I set it to no security, WPA, WPA-PSK2. It sees it but just wont even attempt to connect

2. the button function in setting, this is a known issue throughout all the ROMS I've tried but might as well report since its always there but does not work. Changing search button to anything other than search, it wont do anything. I would like to change it to recent or menu (I can change menu to recent and it work just fine) but no go.

Only reason I'm still on slimkat 3.2 is that I hate the slimrecent, its laggy as heck.
[Motorola Droid RAZR] wernst:
CM11 IMAP and SMTP connectivity problems?

So I've noticed that NONE of the email apps I use under CM11 that use IMAP and SMTP for connectivity work. I've tried several (Aquamail, SolMal, K9), and they all claim they can't talk to the servers.

CloudMagic and Gmail works, but they use their own protocols. My iPad's IMAP/SMTP apps work fine, and my JB ROM using the same applications work fine with IMAP too - all are pointing to the same servers, and they're run by Google. It just seems like CM11 is blocking the ports that IMAP and SMTP uses or something.

Anyone here experiencing the same problem?

-Warr
[Motorola Droid RAZR] Ohmster:
Has anyone installed "the monster" yet? (04/22)

This one update has 20 changes in it, so it might be really, really good, not so good, a few bugs, or really bad. I don't know so to anyone who installed it, is it good? Did you install it OTA or clean? Anything broken or not working? Anything new or good that you noticed? Any report at all would be greatly appreciated. When I go for it, I will post the install details and follow up in a day or two to let you know if it is fit for daily use or not.

This is important information so anyone reporting it would really be helping out a lot. Thanks guys! :cool:

UPDATE:

I just did the update from 04/21 to 04/22 OTA, went very smooth. No issues at all, cam works good. Took another person's advice to clear cam data in app settings to be sure of no more wonky camera, still or video. So far, so good. I am impressed!
[Motorola Droid RAZR] ef141:
OTA'ed about 8 hours ago, from 4/16 So far:

Battery is about the same as 4/16 YMMV

NO FC's

LTE synced right up

Dialer works

Can receive incoming calls

Camera works in video and still mode

Have not seen the dreaded "no APN....." errors

MMS works in stock SMS and Hangouts

Seems pretty smooth with minimal lag

I have seen the orange bar loss of connection to Google, the usual toggling of airplane mode clears it

Seeing a few Couldn't/failed to load memtrack module errors in catlog

I'll keeping playing with it as I have time!

emil
[Motorola Droid RAZR] jmsmeltzer2000:
Running 4/22 and getting FC on the camera. Everything else running pretty smooth.
[Motorola Droid RAZR] Ohmster:
Thank you. The video camera has always been a little wonky. Not sure why, seems to be with pausing and resuming. Such a tiny unpause dot that if you do not hit it, dead center, video stops dead and does not save a real video file, only a useless temp file that you have to delete. I have not had problems with still camera, but am still on 04/21. Still cam works fine, Emil says cam works but did not go into details. Could be an anomaly in your OS or a genuine bug. Not sure yet.

Since installing Battery Doctor, my Cool Tools Xposed module display goes out, not sure if BD is stopping it. But have a good backup and between both you and Emil's reports, it is sounding a LOT better than I thought. Thanks guys, will try OTA and report. :silly:
[Motorola Droid RAZR] josuearisty:
I have some otg cables here and nothing.

I wish we get it as soon as possible, Im really ansious to do something. :D

Enviado desde mi MB865 mediante Tapatalk
[Motorola Droid RAZR] jeff_roey:
Try clearing data on the camera under settings - apps. I get camera FCs after nearly every nightly install. Clearing data immediately resolves the issue.
[Motorola Droid RAZR] Ohmster:
THAT is good to know. I get wonky cam action a lot lately. I didn't even think to clear existing data. Good tip, thanks man. :good:
[Motorola Droid RAZR] Ohmster:
Uh, could somebody bring me up to date here? What is OTG? :confused:
[Motorola Droid RAZR] Omegadrive:
I'm getting lots of UI crashes since CM implemented the new theme system, 90% of them happen when I pull down the notification bar after using the phone for a while. I tried build 03/30 as suggested earlier but hat one has the sound crash bug. Mind this is on a semi-dirty install, been updating nightlies since 02/10 but never installed the snapshot, but today I installed the 04/22 release hoping it fixes the crashes but they still there, just this time I manually went to SS 3.72 and wiped system, cache and davlik, then proceeded to install latest build and pa-micro-gapps 04/21. After the most recent crash I opened Syslog and captured all logs (since I have no idea what I'm looking for), here is the zip:

https://www.dropbox.com/s/cj62clx985765bw/2014-04-23_02.51.zip

Many thanks for any help, this is driving me crazy as is the ONLY issue left for me on this rom.
[Motorola Droid RAZR] josuearisty:
USB OTG!

Enviado desde mi XT912 mediante Tapatalk
[Motorola Droid RAZR] jmsmeltzer2000:
Cleared data. Still get FC every time I try to open it. :confused:
[Motorola Droid RAZR] vanwho:
I had an issue a few weeks ago similar to that. Every ROM I installed, the camera would force close. No matter what I did, it still happened on any ROM, any Slot. I think it was an issue with my Recovery. I updated to the latest SafeStrap 3.72, which forced me to uninstall the recovery on the stock slot with the SafeStrap app. I then installed 3.72, then opened it and installed the Recovery. Once I did that, no more issues with the camera FC. You may not even need to upgrade, just boot to stock, open Safestrap, uninstall, then reinstall the recovery. It can't hurt to try that. I assume that once you do this process, you will want to wipe and flash the ROM again. Hope this helps. Let me know how it goes.
[Motorola Droid RAZR] GTiceman:
I am on the monster Ohmster and it seems to be okay so far. I have been on Wifi though. Camera works fine for me, I did clear data.
[Motorola Droid RAZR] jmsmeltzer2000:
Upgraded my safestrap, reflashed ROM and cleared camera data. Still FC's:mad:
[Motorola Droid RAZR] Mr-Glass:
http://xdaforums.com/showpost.php?p=49965266&postcount=2404

http://xdaforums.com/showpost.php?p=49966507&postcount=2411

:) nice feature.... I use it on the N7 all the time...

Edit** Your Tab 2 should have OTG out of the box
[Motorola Droid RAZR] krestian:
I seem to remember there was a hardware issue regarding OTG support. Actually, the RaZR *does* support OTG, but the caveat is it does not provide any (as in zip, zero, nothing, nada) power on the USB connection. Thus, anything you plug in there, you have to power with an external something (charger, battery pack, pocket Mr. Fusion, whatever) also attached to the cable, or a powered USB hub... completely defeating practicality and the purpose of "On The Go".

FYI, OTG-USB means "On The Go USB" and it means the device can act as a USB host (or "server", as opposed to its regular role as a peripheral). Thus, you can connect to the device pretty much every USB device you could hook to your PC, such as thumb drives, HDDs, and even a mouse or keyboard or game controller, and get it to recognize.

Pretty handy thing to have, especially for those pen drives or external card readers. Especially now that so many devices are beginning to lack micro SD slots.
[Motorola Droid RAZR] vanwho:
If you want a ROM with the On-The-Go camera feature for walking and using the phone, LiquidSmooth has that feature. Maybe Carbon, or Pac-man. But I doubt that CM11 has the same one people are thinking.
[Motorola Droid RAZR] morr22066:
Yeah, PAC ROM has the on the go camera feature so the camera displays in the background while you are in other apps.
[Motorola Droid RAZR] Omegadrive:
Had 4 crashes more since last night, not good, anyone had the time to check the logs attached? Thanks
[Motorola Droid RAZR] Ohmster:
Thanks Mr. Glass, that clears things up quite a bit. I often wondered how neat it would be if we could just plug in USB items to the phone, would it work with just a micro to standard USB adapter. A flash drive would be nice, keyboard and mouse? Maybe to create a phone book or something. I cannot imagine all that cumbersome stuff just to use the phone unless you have a big project or something. Great heads up! :good:
[Motorola Droid RAZR] Mr-Glass:
I use this cable.. I am a sucker for Motorola Cables.. it is short and the quality is top notch.

http://www.amazon.com/dp/B004UAG6WC...UTF8&colid=83O6Y03W7YUE&coliid=I16NOQYQ5TCYFO

Flash drive would be the only thing I would use it for on the Razr - movies plugged into the usb otg - hdmi out to tv - and bluetooth keyboard and mouse... full control from across the room... I have a Motorola bluetooth kb/mouse just for that... ;)
[Motorola Droid RAZR] Ohmster:
Only a dev can help with the logs, they are very technical and hard for anyone but a coder to understand. I had really good success with 03/30 because I previously went clean, installed ONLY cm11 and pa-gapps, and kept it clean. Made a good backup because the system was very stable. I only updated cm11, nothing else, always OTA w/out patches, tweaks, or anything. The only dev we have in this thread is Stargo and he has 5 minutes here, 5 minutes there, to help with major problems, usually affecting several phones. He cannot stop development to help one individual work out issues with one particular phone. But he tries even that, when he can. The guy is amazing.

I cannot tell for sure but it sounds like you have old data corrupting the system. Meaning you might have to do one, super clean install, do the setup, let Google put back your stuff or if you use Titanium Backup,

do not restore any data!

Get a good, solid, working phone first and back it up in Safe Strap. A "Super Clean" install means delete rom slot 1, recreate it, flash ONLY cm11 and pa-gapps, wipe dalvik and cache, reboot and finish the process.

Do whatever network tweaks you must and once solid, save that in a backup! After that you should be able to update OTA from the settings menu like I do. I am saying this because I had exactly the same problems you are describing. Everything and anything would just crash or FC at will. I sort of knew I had to "bite the bullet" and go clean, just did not want to. But remembering what all was in my current setup, patches for camera, patches for WiFi, custom kernels, ...there is like "no way" updates will work on top of that house of cards. cm11 does not need anything but gapps. I have not even used JBX because I do not want to pollute a good working system.

This is

Standard Advice

, not a miracle cure for you. It is what I would do. You know if you installed any system altering things like patches, kernels, or altering any system files. Yes, people do it from time to time, but once done, it cannot be undone. Thus, you have a solid backup to revert to in case a new thing does not work out. XT912 phones all work pretty good now on cm11. A few minor bugs here and there, orange bars sometimes, but I have been pretty lucky since starting with a sterile clean install. :fingers-crossed:
[Motorola Droid RAZR] Omegadrive:
Hmm, I was afraid of that, just wanted to confirm since every time I do a clean install on my phone it takes me over 3 hours to restore everything as it was before and I barely have time to deal with that anymore cause of work and personal commitments. Was trying to find out if it was something simple I could wipe or an app I needed to uninstall to fix the issue. Oh well, thanks.
[Motorola Droid RAZR] Ohmster:
Yeah, me too. It seems to be pretty good. Nothing bad to report yet.

---------- Post added at 04:29 PM ---------- Previous post was at 04:17 PM ----------

Yes it sucks, but you have to be positive about it. Bite the bullet, get it done, and insure it works, works well, and you have the bugs worked out. Back that up to Ext SDCard and keep that one. Copy to PC or Dropbox or something. If you get one, really good one, you won't have to go through this anymore. Setup everything perfect, get it the way you want, back up again. If you have good, solid backups, you won't have to do this again. :fingers-crossed:

Remember, there are things to help. Google is good about restoring your contacts, and if you were/are smart and purchased and use Titanium Backup (Buy the Pro version, it cost about six bucks!), you can restore everything in one swoop, just do not restore data. Once solid and working right, backup, then if you must, restore data for the few apps that really need it.

If you don't have Titanium Backup, it is not too late to install and use it. Buy it if you got the six bucks. Make a backup of all your apps so you can safely restore them,

without data

, because you are coming from a corrupt system!

Okay, hope you got some direction now. Good luck.

If this really helps you now or later, be nice and tap my Thanks button. :angel:
[Motorola Droid RAZR] Ohmster:
On 04/22 and seem to always have problems with Google voice typing. I use it a lot to answer text messages. At first boot, it works fine. Hour or two later, round dot comes up, never beeps and turns red to talk. Only a reboot will clear it. Issue seemed to start when installed Battery Doctor, not sure if it is the app or the update. Removed Battery Doctor and rebooted, working now. Will know more when a few hours pass. Else must revert. "Something" is putting it to sleep and I cannot find the "app" to clear data or see what it is doing. Where the heck is Google voice typing, other than Language and Input?

Gray screen comes up, round dot never turns red or beeps to accept voice input.

Anyone else have Google voice typing not working when you need it? :confused:

UPDATE:

Dammit! Not even an hour gone by since removing Battery Doctor and rebooting. Voice typing worked and is out again. Grrrrrrrr! :mad:

UPDATE 2:

Found my SVOX UK Victoria voice not installed. Tried to test it after reinstalling from play store. No sound, not even key press tick. But while testing the SVOX voice, saw the Bluetooth icon in a system message, I had it turned on but not my headset. Shut off Bluetooth and button tick sound returned as well as Voice Typing. Strange, Bluetooth being active and not connected should not affect this voice typing and keypress sound, but it does. I think I found a bug.
[Motorola Droid RAZR] Noe!:
Is there a nightly worth upgrading from 4/15? Thanks.
[Motorola Droid RAZR] Ohmster:
Yes, any of them. I went up to 04/21 and all was well. Was nervous about 04/22 because it contains over 20 changes. Asked others if any problems, they all said no. I installed it OTA after backing up, and it is good. So far all builds in the past week are good. :laugh:

* Only "bug" I found in 04/22 is that if you have Bluetooth turned on and not even connected, within an hour of booting, voice typing stops working and key press tick sound stops. It keeps getting routed to or stopped by Bluetooth. So, I turn off Bluetooth when not using it and all is well. If you want to avoid any possible problems, go as far as 04/21, but even after that, no really major problems, Noe.