yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
Oh you did get the output file! And you get to learn some ADB too. I just thought you didn't want to learn all that to get a system log. Your tutorial author admits to liking the CatLog app on Android because it is easier and makes the nice colors to show what is power, what is audio, what is sytem, etc. Thanks for the feedback. Good job, man! :good:

...my ADB experience *did* generate the logcat.txt files, but I used "Search Everything" to find them as I had not idea of where to look. :o
[Motorola Droid RAZR] Dwillian:
I bit the bullet and went the ADB route because the force close on my phone made it very tedious and nearly impossible to do anything on the phone. I still had to fight through the FCs while getting the mass storage mode and android debugging enabled, but that wasn't too bad. Thanks for the help.
[Motorola Droid RAZR] Ohmster:
Oh! I forgot, you were tapping the FC message every second while trying to use the phone. Ooooh, that totally sucks, man. You HAD to use ADB over USB to get that log. Nice. I was reading up and you can get status and communicate with the phone even while booting with ADB.

You are welcome. I just want you to play with everyone else and enjoy the rom instead of hating it so much. :o

You will get good at shutting down stuff you do not need and allowing what you do need. Then, you will know what is running, when, and why. Once you "get good at this" maintenance stuff, you will be able to enjoy it a LOT more and do almost anything you want. I am NOT an expert yet, but I am good at learning what "I need to get good at" and then working towards that goal. And for me, the rewards are paying off already. People like DumbleCore and sherri are so good at this stuff that they just do it, "matter of fact" w/out having to think of what to do. I hope to get good at this like them one day. You will too. Goodnight Dwillian. :highfive:
[Motorola Droid RAZR] Ohmster:
Build Report 11/28 Spyder FINAL

NIGHTLY BUILD REPORT 11/28 OFFICIAL SPYDER XT912 Verizon US

Updated to 11/28 NIGHTLY Official Build from UNOFFICIAL patch Build11/24. Not using Stargo's patched UNOFFICIAL Build.

ROM: cm-11-20141128-NIGHTLY-spyder.zip

Gapps: pa_gapps-modular-mini-4.4.4-20141121-signed.zip, already on system

Method: Installed 11/28 OTA from Settings Menu over UNOFFICIAL Stargo patched rom 11/24.

Run Time: 2 days

Initial Install: Smooth, perfectly normal install, no issues at all

Tested: Contacts, Dialer, Bluetooth Audio, Streaming Audio, Maps, GPS, File Manger, WiFi, Camera

Results: Very good, smooth action and good performance. No FC's or major issues. Dialer did lag a bit w/black interface & white spinning arrow but only lasted a few seconds and was a one time incident.

Individuals with unstable devices might have issues with this rom as indicated by the one time lag incident.

Comments: Good rom for me. Perfectly usable for day to day phone. I plan to stay with this rom until something noteworthy comes out. The only available update available at this time on Changelog is NIGHTLY Build 11/30 and there is only one minor change for "headless mode", which I assume to be operation via USB cable with ADB or some other method of working the phone indirectly. Overall a good daily driver.

Outcome: Positive - Good :good:
[Motorola Droid RAZR] azurikai:
Some time ago I forgot to respond to you as a thanks. I got the CyanogenMod ROM running with the XT912 (using SPYDER).
[Motorola Droid RAZR] Dwillian:
I'm a little confused. Did you mean cm-11-20141128-NIGHTLY-spyder.zip, or cm-11-20141129-NIGHTLY-spyder.zip?

I would like to try and reproduce your install as closely as I can to see if I can avoid the com.android.phone force close problem.
[Motorola Droid RAZR] Ohmster:
Sorry. I got messed up with copy and paste on the URL and file name. I installed the official NIGHTLY Build 11/28 over the 11/24 UNOFFICIAL patched Build. Wow, I see how you can be confused. Had 11/24 installed, updated OTA to 11/28, still on 11/28 because it is, "pretty good". And I have been busy building a medical office workstation so I did not have the time to play with later builds. 11/30 had nothing impressive to offer in the Changelog.

The UNOFFICIAL patched 11/24 build did not crash on me. I was just testing it as a user rom. I then wanted to update and took the best available at the time, the 11/28 Nightly. Hope that clears things up. :fingers-crossed:

Post #6924 corrected, links fixed. Thank you Dwillian. :o
[Motorola Droid RAZR] parser:
So guys, it is a farewell for me. I bought a Huawei Ascend G7 which blows my mind with its battery performence :) I got what i actually wanted. I am sending my razr to me mum. She has a lumia which makes her pretty angry most of the time so she wants to try android. I wish you all the best and keep this monster alive!!

peace out!
[Motorola Droid RAZR] Ohmster:
Oh gosh, sorry to see you go, Parser. But not unhappy that you have something you really like and are upgrading your phone. We are all your friends here so stop in once and a while to say "Hey" if you want and *do* let us know about the new phone, what make/model you got, how you like it, and of course, the most IMPORTANT THING,

please tell us if you have it rooted or not and if you installed a custom rom like CM11 on it.

(CM12 is not officially released as anything near stable so please do not install CM12 as your day to day rom!)

By the way to everyone else,

I am installing the new CM11 12/02 NIGHTLY Build to see how it works.

I am quite satisfied with CM11 11/28 as it has served me well. I will backup this installation and install the new 12/02 nightly and report on it's performance. Goodnight Everyone and good luck to you, Parser with the new phone! :)

Update:

I did update from NIGHTLY Build 11/28 to NIGHTLY Build 12/02 spyder through Settings, About Phone, CyanogenMod Updates. pa-gapps on system already. Install went well. App Count during bootup to rebuild Dalvik Cache as accurate as to the number of apps on the system. Initial install went very well, everything seems to work. Nothing strange, out of the ordinary, or sluggish about this install as of yet. Will update you all with a Final Report in 1 or 2 days.
[Motorola Droid RAZR] Dwillian:
I am happy that you can successfully install the latest nightlies (but envious nonetheless ;). I'm still stuck on the 11/07 nightly. Every nightly after 11/07 that I've tried causes the com.android.phone force close problem. I haven't tried the 12/02 nightly yet but I don't expect any better results. I guess I'm stuck and will need to be patient until the issue can be further investigated and resolved; probably until mid-December when [MENTION=3457922]stargo[/MENTION] returns, or January when CM12 releases are likely to become more stable. Sigh.

It is very perplexing to me why some people have the force close problem while some (most?) do not. It makes me think that there is something fundamentally different about my particular phone versus other XT912s. Flawed firmware perhaps? My wife has the identical phone and it has always performed better than mine (even when we were both on stock verizon). The performance difference is really what prompted me to investigate custom ROMs in the first place. Oh well.
[Motorola Droid RAZR] Ohmster:
You know, that is pretty darned frustrating. I am hesitant to put you through an entire series of tests and procedures, only to find out that it didn't help at all. I already ran that route with [MENTION=2774395]my2cents[/MENTION] who was constantly plagues with APN issues from very early on. We checked everything for him. We tried clean installs, patches, altered system files, imported system files from other builds. Nothing worded and now Frank has upgraded to the new Droid Turbo and cannot root the device anymore. It is not "terrible" w/out root, he is the same as any end user now. But he badly misses the ad patchers, ad removers, and Pandora Fix that came from Xposed modules. I would greatly miss the free WiFi Hotspot as Verizon charges $20/Mo for this feature, whether you use it or not.

Things to be grateful for:

You do have a good build of 11/07 that does everything you want it to do.

You have a rooted phone and can install root apps and do what you want with it.

You do have a custom rom and it is FAR better than the stock bloat that comes with the phone.

And you still have hope.

Be thankful for that my friend. :)

Couple of things you can check. Do you have the manufacturer /pds folder in the root of internal storage anymore? See attached screenshot for that. Are there any missing or blank fields in yoru /Settings/About Phone/Status screen? I am not currently running WiFi or Bluetooth so I do have some "unknown" fields in this screen.

Wi-Fi MAC Address

Bluetooth Address

And for some strange reason: Serial Number

Other than that, my About Phone/Status screen is fully populated. How does your screen look? I "stitched together" a long screenshot of my About Phone/Status screen in the attached screenshot #2. The applied distortion is only to protect personal information, however the pixelated numbers are indeed real. You may need to download or "pinch out" the image to see it all. Does this pretty much match what you see, Dwillian?

I do not want to advise anything yet, just give you something to be grateful for (So what if 11/07 "get's old"? It does everything you want and will serve you just fine for now until something better can be done.). And to give you a few things to check that might give us some clues to just what the actual problem is.

OMG, I have to go back and finish cooking dinner! Check your phone for these items and get back to me if you can buddy. :good:
[Motorola Droid RAZR] Dwillian:
OK, I did some checking. I had to do this from my good install of 11/07 nightly. Here is what I found:

/pds does exist

Under Settings, About Phone, Status I noticed the following differences:

Mobile network state says "Disconnected"

My Phone number says "Unknown"

MIN says "Unknown"

PRL Version says "Unknown"

Wi-Fi MAC address had values listed

Bluetooth address had values listed

Seems odd that my mobile network is disconnected. I checked and even though I am on my local WiFi network the mobile network icon shows 4 white bars and says Verizon Wireless. I tried disconnecting from my local WiFi and then checked phone status again. Now Mobile network state shows "Connected" and My phone number has my phone number listed. I turned WiFi back on and waited for the bars to turn white. Now Mobile network state shows "Disconnected", but My phone number still shows my phone number.
[Motorola Droid RAZR] Dwillian:
Actually I did do a full factory reset using the procedure you suggest a couple days ago. It didn't solve the problem. There must be something else going on with my phone.

Thanks for the suggestion though.
[Motorola Droid RAZR] Ohmster:
Mmmmm. Wow, now I really don't know what to say. The basics, I guess. Go to Verizon and get a new SIM card. They are free. Boot to stock rom and while you are there, ask them why you do not have a MIN and PRL. That stuff comes from them, so ask them. (Make sure they are still missing in stock rom first.) Swap out your external sd-card, it might help. Other than that, I just don't know right now my friend. But will keep it in mind. :)
[Motorola Droid RAZR] Ohmster:
Build Report 12/02 Spyder Final

NIGHTLY BUILD REPORT 12/02 OFFICIAL SPYDER XT912 Verizon US

Updated to 12/02 NIGHTLY Official Build from NIGHTLY Build11/28.

ROM: cm-11-20141202-NIGHTLY-spyder.zip

Gapps: pa_gapps-modular-mini-4.4.4-20141121-signed.zip, already on system

Method: Installed 12/02 OTA from Settings Menu over NIGHTLY Build11/28

Run Time: 2 days

Initial Install: Smooth, perfectly normal install, no issues apparent at the time.

Tested: Contacts, Dialer, Bluetooth Audio, File Manger, WiFi, Camera

Results: Good, smooth action and good performance. No FC's or major issues. Mom called and instead of sliding screen, I pressed power by mistake and blacked the screen. Pressing power again lit the hard buttons but not the screen. I could hear mom on phone but screen would not light, seemed like proximity monitor was lagging or some black screen issue again and I missed the call. This was a one time incident because I updated to 12/04 before I got any more calls.

Individuals with unstable devices might have issues with this rom as indicated by the incoming call black screen incident.

Comments: It seemed like a good rom at first. Nothing failed outright but I did not get the impression this was any better or even equal to the previous rom. I did not bother to back it up. Worse, I did do an OTA update to 12/04 and saw the boot-up App Count dead wrong, indicating 100 apps on system, I have 201. Anytime I get a bad App Count when rebooting after an update, the rom always fails. I bailed, restored my 11/28 backup, and am back to 11/28 again. I just do not like "the feel" of the current rom set. They don't install or run smoothly like in better times. Seems there is always some hidden burr in the system and I am staying at 11/28 for now. Newer, more powerful phones might run better on the latest build of roms right now. For me, they have to be "really good" and then I am quite satisfied. ;)

Outcome: Negative - Bad for me - others might have more luck with it. :rolleyes:
[Motorola Droid RAZR] farangcm:
XT910 CM11 12/04 Report

CM11 12/04 Build Report: XT910 (umts_spyder/gapps-kk-minimal-20143924/CM11 12-03-->12/04/Testing Period: 1 hour/CM Updater

At startup, Google initialized 34 apps (I have just over 100). Shortly after install, the phone vibrated-- I had a call, but it didn't play my Rachmaninoff ringtone. After the call I went into settings to check the ringtone and volume. The ringtone was set right, but I couldn't open "Volumes." Then Setting FC'ed. Since I hadn't any problems with 12/03, I restored my backup.

Allen
[Motorola Droid RAZR] fujcru:
CM 11 12/04 Report

Interesting thing to note with the report of a bad update is that the file that propagated to the various servers might be bad. Downloading the cm-11-20141204-NIGHTLY-spyder.zip file from both get.cm/?device=spyder and http://www.cmxlog.com/11/spyder/ result in a broken file. The files were the same and they did not match the checksum. They also were not valid zip files. So it seems like the problems with the 12/04 build may simply be because there was a problem with the file that made it to the servers. So it may be best to just hold off on this build. It probably won't be fixed since it seems like they pump these out fairly regularly and are already working on the next builds. Best guess is that this was just a glitch. I think this is the first build where I've seen this discrepancy between the file and the checksum. Hopefully the future builds won't have this problem.
[Motorola Droid RAZR] clclcl:
Flashed CM11 NIGHTLY 1127 for XT910 (umts_spyder) with stock PA-GApps

Update method is flash via Safestrap 3.75

Everything works fine, battery life is really good... EXCEPT clock keep on closing, thus I can't set up alarm... This was almost fatal for me as two days ago I set alarm via Google Now and went to bed straight away without rechecking... Almost late for my final test the next day. :eek:

Will try flashing OTA update.
[Motorola Droid RAZR] qkdxorjs1002:
deleted
[Motorola Droid RAZR] clclcl:
Just updated to CM11 NIGHTLY 1203 via OTA (XT910 umts_spyder) I'm in PA GApps Stock

Almost everything doesnt work... Clock, Homescreen, Google Play Service... My phone is just blank, only lockscreen, notification bar and settings works.... :silly:

I suspect that's because I'm running out of free space in /system (damn stock GApps) but since the GApps are alrady there, maybe the ROM became corrupted/ only partially flashed....

Will flash 1204 manually via Safestrap...
[Motorola Droid RAZR] Dwillian:
[MENTION=4245858]Ohmster[/MENTION] [MENTION=3457922]stargo[/MENTION]

Looks like the missing phone number, MIN, and PRL is something related to CM. I booted back into stock Verizon and those values are populated. When I reboot back into my "good" CM 11/07 nightly the values are shown as "unknown". I wonder if this is the source of the com.android.phone FC I experience with newer nightlies?

Update1: Out of curiosity I did a clean install of CM 11/07 nightly and micro PA GApps into a newly created ROM slot 2. After going through the initial setup I checked phone status and My phone number, MIN, and PRL version are populated now. I guess my "good" 11/07 nightly backup is not so "good". Guess i will finish setting up the clean install of 11/07, make a "better" backup, and then see if I can OTA update to one of the newer nightlies and avoid the com.android.phone process FC. Fingers crossed.

Update2: [MENTION=4245858]Ohmster[/MENTION] [MENTION=3457922]stargo[/MENTION] I think the source of the missing My phone number, MIN, and PRL is a SafeStrap issue. I did finish setting up my "better" CM 11/07 install in ROM slot 2. I then made a backup of the "better" installation. Then I recreated my ROM slot 1 and restored the backup. I immediately checked Phone Status and My phone number, MIN, and PRL all now say "unknown". I tried this using both SafeStrap 3.73 and SafeStrap 3.75. I think this could be bad news since you cannot assume that a SafeStrap restore has actually completely restored the ROM to its original state. I'm now going to try doing an OTA update of the latest nightly (12/05) over ROM slot 2 (my "better" 11/07 install that does have values shown for My phone number, MIN, and PRL version) and see if the com.android.phone FC reappears, or not.

Update3: So, I booted into my "better" 11/07 install on ROM slot 2. In preparation for the OTA update I first checked phone status and somehow now My phone number, MIN, and PRL version all say "unknown". This is very strange to me since all these values were populated last night before I put the phone on the charger and then went to bed. I am assuming this is not normal, but I don't know if I should be concerned or just ignore the problem. It also is not at all obvious why or how these values are being removed. Could be CM, could be SafeStrap, could be Verizon, could be ????

Update4: So, I tried rebooting with WiFi turned off and lo and behold My phone number, MIN, and PRL version are populated again. Apparently those values can get lost while on WiFi, but are repopulated if you reboot while on mobile network. Rebooting while on WiFi does not fix the problem. I'm not sure if this is at all important or not though.

Update4: No joy :( The OTA update to 12/05 nightly results in com.android.phone FC. I tried getting a logcat, but the FC is so bad I can't get usb debugging enabled. I'm going back to my "better" install of CM 11/07 nightly, rebooting with WiFi off to reset My phone number, MIN, and PRL version. And then sit tight until some progress can be made on this issue.
[Motorola Droid RAZR] clclcl:
Flashed 1204 for XT910 1780mah (umts_spyder) with Stock 2.0 PA GApps

Using Safestrap 3.75

Flashing is quick and didnt encounter any problem, didnt wipe /data nor cache and all is well.

But the clock problem persists! I dont know why...

So went to Terminal Emulator and ;

$ su
# logcat
# cd /data/data/com.android.deskclock/databases
# mv alarms.db alarms.db.bak

and it's fixed now.

Another minor problem, when screen is locked, battery status wont update when charging (I'm using number instead of icon though) at some point I had a look when it was locked and it indicated 79%, unlocked immediately.... 100%?
[Motorola Droid RAZR] Dwillian:
Please see my updates to my prior post (http://xdaforums.com/showpost.php?p=57254266&postcount=6942)
[Motorola Droid RAZR] Ohmster:
Wow, that is quite a bit of work you did [MENTION=5362796]Dwillian[/MENTION] and an awful lot of new stuff to learn. I do hope that you are keeping screenshots and notes of what you discover, or at the very least, copy your last Post #6942 as text and paste into a dated text file as NOTES. Update and refer to these notes in the future so that you need not recreate these examples to find out this information. Good detective work, bra! Even great detectives do not solve every case or at least not quickly and easily. ;)

I restored my 11/28 backup last night, still running well so I am leaving it alone for now. I tend to forget that you leave your WiFi on almost all the time. I have unlimited data and never use enough to consider throttling so I only use WiFi to transfer files to/from the phone. This saves a LOT of battery power and I think this is how most users run their devices.

I checked MIN and PRL with WiFi on and off. The fields are populated with numbers in each case. I have an "unknown" serial number at the bottom of Phone Status in call cases, but it does not seem to affect anything, just an observation. Is your serial number present? Not that it seems to matter, I just want to understand these fields and their significance a little better.

So a clean install of CM11 11/07 gave you back your PRL and MIN. After being on charge overnight, these fields are now empty or unknown, correct? If so, that gives us something to Google about. Rebooting w/out WiFi turned on repopulated your MIN and PRL fields, yes?

And OTA to 12/05 restored the FC issues again, yes? Maybe you have an issue with the new roms "being a little rough around the edges" as I suspect. Can you get your good 11/07 build restored and update to a "not much newer" NIGHTLY Build to see if this update does indeed go well so we can narrow it down to the latest set of updates, Dwillian? Let me see if I have any builds that are just a bit newer than 11/07.

Oh, I have 11/09 on the phone, I am now transferring it over WiFi w/ES File Explorer to my PC and dropbox for you. (I can copy directly to dropbox as well in ES File Explorer, this is a great root file manager!) This is taking too long, copying directly to dropbox now w/out WiFi. Grab this rom, put it on your phone in /sdcard/cmupdater/cm-11-20141109-NIGHTLY-spyder.zip and then update OTA from /Settings/About Phone/CyanogenMod Updates/cm-11-20141109-NIGHTLY-spyder. If this update does not cause FC issues, then we can narrow down the issue to late release versions of CM11.

...if you want to try OTA that is. Otherwise, you can also update "Dwillian Dump" w/pa-gapps. I would try the plain "copy rom to /sdcard/cmupdater/" and just OTA update first. If that does not work, then try the Dwillian Dump. :confused:

Okay, want to try that? Download cm-11-20141109-NIGHTLY-spyder Here.

See how that works. We are really just gathering information here but if we get results, all the better! :D
[Motorola Droid RAZR] Ohmster:
Hey I like that report and the nifty deskclock fix. Instead of deleting the alarms.db file, you renamed it with a .bak extension to disable it, thus keeping it available in the event the removal failed. And you gave the steps to help others do this if they need to. Nice work! I can't tell you about the lockscreen battery icon, I use a colored icon with % text inside with Xposed Modules. GravityBox KK v3.2.5 for the color and I haven't noticed the battery icon in disagreement with the desktop as they are the same icon. Are you using a custom icon or something? Why would the battery icons differ from lock to unlock?
[Motorola Droid RAZR] Dwillian:
I recreated my ROM slot 2, installed 11/07 nightly and PA GApps (micro version), wiped cache and dalvik cache, and rebooted. I went through initial setup and let Google restore all my apps and settings.

Everything seems to be working fine. My serial number does show as unknown. My phone number, MIN, and PRL version are populated. I then copied the 11/09 nightly that you provided into /sdcard/cmupdater and then did an OTA update. So far the update seems to be working fine with no FC of any processes.

I suppose I should start working forward through the nightlies until the FC problem reappears. All the more recent nightlies are listed on the download server, but the older nightlies no longer seem to be available for download. Do you have any that are just a little newer than 11/09?