yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
Oh what a nice Kitty! My kitty Sonia might like to meet your kitty.

Uh, your phone is NOT sleeping, AT ALL. And this is bad, for battery life. It is not uncommon for Android OS to consume most battery power. But when the screen goes off, the phone CPU drops to 300 MHz and then night night. No huge battery loss there. Why is it not going to sleep. Oh I hate when people ask that! :p

Just kidding. There are A LOT of things that can keep the phone awake. Xposed modules, power settings, app settings, we could spend all day trying to figure it out. To prove or disprove your sleep cycle, there is a really neat Xposed Module for that. (Ohmster just

loves

Xposed Modules!) Install your Xposed Framework using the app for it in the app drawer if you have not already done so. Go visit the downloads in Xsposed and pick this one, Android Tuner Free. Do not get overwhelmed by all the features. There are 5 pages of them. The two items you want are on page five at the bottom, just swipe to the left until the little dots show you on the last page, all the way to the right. You have a Battery information popup and a CPU information popup. Look at battery, see if it shows you anything. Then look at the CPU popup. Screenshot attached.

You get all sorts of things you can do with the CPU, What they are doing, how they are set, what governor to use if you want. Interactive is a pretty good balance of battery and performance. You can set min and max speeds, leave them alone at 300 and 1200. Look at the bottom, see Uptime, how long phone is running and to the right, Sleep, how many hours. In my screenshot you see phone up for a day and 8 hours, but sleeping for 13 Hours and 9 minutes. This does not tell us what is stopping the sleep but before going down that road, at least see if that is the issue.

There are other really good modules too. I will tell them if you want but for now, go check if the phone is sleeping at all or very little, okay?
[Motorola Droid RAZR] Ohmster:
Ah! Yeah man, those over 100% numbers were driving me crazy too. Thank you for this important news, Jake.

Michael did all this himself. We have been talking about the Bluetooth noise. Nothing yet, but if confirmed in ALL 4.4 roms, Google might get involved and that could only be good news. They have the power to deal with Motorola about source code and binaries that do not work anymore. Also asked him about "apps write to SDCard Ext. Found something interesting on it, tried it myself, difficult for me, so he will investigate and incorporate if found to be affecting all of our phones.

Jake, you da man! :good:

---------- Post added at 11:08 PM ---------- Previous post was at 11:05 PM ----------

Just checking tapout talk for zero66. I just had orange bars a minute ago but they went away. They don't stay usually very long for me. Seems to work fine. I am on 04/12 though, have not tried 13 yet. (unlucky number.)

---------- Post added at 11:11 PM ---------- Previous post was at 11:08 PM ----------

NO! Do not wipe it. Android OS is the operating system, like Windows. You cannot delete it. I just sent you a reply how to check if phone is sleeping with xposed module. Please read, check, and report back. Thanks. :good:
[Motorola Droid RAZR] Noe!:
Hey Ohmster, did the SDCard App Fix I sent you work? I was wondering about that just now.
[Motorola Droid RAZR] Ohmster:
Huh, what app fix, Noe? How did you send it? Make friend Req, I will give email.
[Motorola Droid RAZR] my2cents:
After nearly 2 days on 4/13, got error about missing APN. Dang it... Also, WIFI still wont turn off no matter what I do, it shows that it is consuming battery. And, again, LTE lock takes some time. It will go into 3G first (after a couple of minutes of no data connection, then about 5 minutes later it will find LTE. It seems like the latest nightlies are messing with the radio somehow??
[Motorola Droid RAZR] welder73:
Look under Wifi/Advanced settings/Scanning always available,if it's checked,uncheck it.

Sent from my Razr XT910
[Motorola Droid RAZR] marlowe310:
Quick question, is it possible to delete the stock slot and then recreate it? That way you could make as clean a flash on stock as it would be if you deleted a ROM slot and created a new one through safestrap?
[Motorola Droid RAZR] icarome:
I don't think you can delete the stock slot, but for a clean install you can advanced wipe your system, data and cache... But whenever you do it make sure you installed a system that is compatible with stock slot, otherwise you're going to stuck on bootlogo and not even safestrap will load, so you'll have to flash the phone with RSD (I've already did this mess). So before you start dealing with stock slot make sure you have enough battery to flash it in a emergency case. Hope it helped... :p
[Motorola Droid RAZR] Mr-Glass:
Hashcode has the new Safestrap out on Goo.im - getting ready to check it out...

Spyder : http://goo.im/devs/Hashcode/spyder/safestrap/Safestrap-Spyder-3.72.apk

UMTS_Spyder http://goo.im/devs/Hashcode/umts_spyder/safestrap/Safestrap-UMTS_Spyder-3.72.apk
[Motorola Droid RAZR] Ohmster:
Hey,

Emil told you to wipe dalvik, cache, and android secure. You replied that it worked. So what happens, it does not work anymore?

What about what welder told you, that work?

Look under Wifi/Advanced settings/Scanning always available,if it's checked,uncheck it.

I tell ya 2¢. I was happy as a clam on 03/30 and would not touch 04/09 and up, bug ridden. I knew it would happen, too many very big changes in a rom, not enough builds to find and fix them. I went for 04/12 and now problems. Orange bars all the time, play store does not want to download or barely trickles. Other times play store says "Waiting for network". Video camera crashes, this is getting to be too much headache. I might just revert to 03/30 again but will back this up. I just got a 64Gb SD Card.

04/09 was when all the trouble started, too much new code, OMAP4 and everyone was so excited about it. Not me, not right away. THAT much difference in code means lots of bugs to field test, work on, release nightlies, rinse and repeat until you get it right. Can't say I am surprised.
[Motorola Droid RAZR] chinkster:
[MENTION=4245858]Ohmster[/MENTION] where can i find 3/30 nightly at?
[Motorola Droid RAZR] Super_Luddite:
I too would like to know where to get a copy of this
[Motorola Droid RAZR] stargo:
What happens if you set Mobile networks -> CDMA subscription to "RUIM/SIM"? This might fix it (and is actually the correct setting...).

If this works, I'll try to change the default.

Regards,

Michael
[Motorola Droid RAZR] ktimque:
Hey guys are there any serious issues left with this?

I want to clean up the OP and I'm assuming most bugs have been ironed out?
[Motorola Droid RAZR] Ohmster:
Well, I see it is not on the download page. I have 03/30 on my phone and would be glad to up it to my web space for you. But the issues began on 04/09 when all the new OMAP4 stuff was added. Anything before that should be alright. On the download page is 04/05. That is pre-OMAP4. Give that a try on The Download Page. If need be, I still have the rom and will up it for you. 03/30 isn't "magic" or anything, it just works fine. 04/05 should too and it is on the download server right now. Grab it!

If you really want 03/30, I am pulling it off my phone and upload for you. Just give me a little bit. Done.

MD5: 9DEF332B275A7E82DB287B228994F6E5

cm-11-20140330-NIGHTLY-spyder.zip

Alright. Since I pulled this off my phone, this is what I installed, I checked the MD5 to be sure what I copied to PC for upload is

exactly the same

. This is to insure that you do not get a file that is corrupted in transport. Now you can, if you want, check your MD5 sum when you download this file to be sure you got a good copy. MD5 checkers are free all over the internet. Just pick one and check against my posted MD5 to be sure your copy is good.

But really, anything prior to 04/09 should be fine, and give Stargo a chance, do what he says and report the results, please.

Important Guys:

Stargo just gave you some advice today at 7:52 AM. His fix may work, more important he is the lead developer. Someone like *that* does not just "pop in for chit chat* often. He has a fix for you to try and REPORT BACK that it worked or did not work, that may fix not only your phones, but everyone else's too.

Dam, they are pulling stuff off the download page in record time. I tried to quickly grab 04/05 before it was gone and I am too late. Gone. Only thing left is M5. I have 03/30. Does anyone have 04/05? 07 is when problems were introduced, Micheal just posted so. Meaning 04/05 and below are good, 04/07 and up are bug ridden. I would like a copy of 04/05 if anyone has it, just checked my phone, not downloaded. :(
[Motorola Droid RAZR] Dwillian:
I would be happy with the 4/7 nightly too. It seemed to work very well for me, but it is gone from the download server too.

IMHO CM is removing the nightlies from the server way too quickly. We barely have time to check out a few of the nightlies before they are gone.

I'm OK with bugs in the nightlies, but we need more options for reverting back to more stable versions. Clearly the M snapshots aren't any more stable than the nightlies (although CM says they should be), so that's not much of an option either.

CM does accept bug reports on M snapshots, but I'm unwilling to spend much time on M snapshots that are just as unstable as the nightlies (and in fact some nightlies, like 3/30 and 4/7, are better than the allegedly more stable M snapshots).

And now I hear that KitKat 4.4.3 is just around the corner. If past history is any indicator CM will drop 4.4.2 pretty quickly once 4.4.3 is available. And so the cycle repeats.

Sorry for the rant, but at this point I find the situation to be very frustrating. I know the developers are doing a lot of good work and are providing CM for free, so I'm not complaining (really I'm not). I do feel that the situation with removing nightlies too quickly and releasing M snapshots that are less stable than nightlies has room for improvement though.

---------- Post added at 06:32 AM ---------- Previous post was at 06:23 AM ----------

The most recent discussions seem to revolve around issues with the most recent M5 snapshot and recent nightlies (i.e. released during 4/2014). Based on these discussions it appears that bugs do still remain.
[Motorola Droid RAZR] morr22066:
No 4-15-14 nightly?

There was no 4-15-14 nightly? I checked the nightly download page and it looks like only about half of the devices listed have gotten a 4-15-14 nightly. Maybe they are just uploading a little slower than usual?

---------- Post added at 05:57 AM ---------- Previous post was at 05:38 AM ----------

Hi Ohmster,

I have applied the settings fix that you referred to. I turned off my WiFi, went to mobile networks and changed my subscription from NV to RUIM/SIM and then rebooted. It did not revert to the prior setting but still took a while to connect (maybe not as long) but it is connected to LTE and I do not see any orange bars. I did also notice that (prior to switching) my preferred network type is not global, it is now CDMA+LTE/EVDO, I could swear that it was previously set to global, not sure when it changed.

It's been about 45 minutes and I have not seen any orange bars and I have been able to send / receive MMS messages with WiFi turned off. Turned WiFi back on about 10 minutes ago and bars did drop from 2-3 down to 1-2, but no orange bars yet and I was able to send and receive MMS messages.

The setting change may have worked.
[Motorola Droid RAZR] Ohmster:
YES, there are issues. NO, do not give it a clean bill of health.

It was really good in late March, early April. As of 04/09, a whole slew of new, recently made available, OMAP4 (Droid Phones, in plain English.) improvements were made. Many people were excited about it, downloaded, and installed. I know better. "New, previously unavailable updates" means, again in plain English, is a major system change, have not field tested it, and there will be bugs. You report them and we work them out in future builds. As of 04/12, things have gotten better, but not quite. Annoying bugs like losing the APN, orange bars to Google servers, loss of WiFi and signal, video camera crashes, and a whole bunch more. This is "normal" in a build process, sometimes you get a good one, and there will be times you get bad builds. Once a big or many big changes go into a build, it could take weeks or a month to sort out.

I avoid bad builds by reading the install reports and bug reports in this thread. I am now on 04/12 which was said to be better, "fixed", but it is still fraught with problems. Contemplating on reverting to my 03/30 backup. Or any build prior to 04/09.

So if you are talking about updating the page 1 Install Guide, cm11 as of mid April is NOT ready for prime time. Sorry.

:(

---------- Post added at 10:31 AM ---------- Previous post was at 10:27 AM ----------

Oh that is such good news, thank you for the diligent report. These reports and mutual cooperation is what makes this thread so active and helpful. I will pass on your report to Stargo. Global NEVER works for our phones. You will be lucky to get 3G if anything at all. The correct settings for mobile network is CDMA+LTE/EVDO. They always have been, this issue was cleared up 2 months ago but the recent changes in cm11 as of 04/09 broke a lot of stuff.

Good job, you get Thanks! :good:

---------- Post added at 10:43 AM ---------- Previous post was at 10:31 AM ----------

Dwillian is very much right about this. I just had two people asking for my copy of 03/30 and of course, I obliged. But anything prior to 04/09 is good. 04/07 is still there and it is a good one too. I think the OP here wants to update the current status of the cm11 build tree. I say it took a nose dive on 04/09 and has not recovered. Prior to that, all is fine like Dwillian said.

It is true, reporting on M5 is stupid. By the time we make a report, the build is already outdated and we are moving on to better builds. CM11 needs to stop that ridiculous policy of freezing a mediocre build and taking reports on it ONLY. Invite the devs here to see for themselves. I am constantly asking for diligent reporting for new build installs, how it was done, how it went, and any problems reported. Then, the follow-ups come, days later when this is broke, and that does not work, and my APN is gone, etc., so on, and so forth.

I am with Dwillian on this.

If CyanogenMod wants to know what is really going on, they need to get their butts in here and start reading

.

Good job, Dwillian! :good:
[Motorola Droid RAZR] stargo:
It got built, so it should eventually show up.

Ok, let's hope that this easy fix solves it. If not, I have reverted a commit which I suspect could be responsible for the problem and uploaded a test-build to: http://131.188.40.106/cm-11.0/test/

Please try this if you continue experiencing LTE-problems.

The omap-changes are not causing the recent problems. I assume the problems got introduced in the 20140407-nightly with a fix for RUIM/NV selection or a fix for Sprint. The first one is easy to test and fix, the second one not so (that's what the test-build is for).

People using the UMTS-version of the phone are not affected by these problems.

About the orange bars: They seem to be caused by server-problems on Google's side and are connected to a device/user-pair. I have seen them with other devices, too...

Regards,

Michael
[Motorola Droid RAZR] my2cents:
That was it. Thanks.

---------- Post added at 08:06 AM ---------- Previous post was at 08:01 AM ----------

Yeah, I know how to fix it. I just dont think it should happen in the first place.
[Motorola Droid RAZR] Ohmster:
Thank you Michael. I asked some of those requesting an earlier build to please try your fix and

report it

. Fortunately, we got at least one positive report.

Personally, do not like cm11 after 04/09, a lot of problems and workarounds since then. Orange bars, video camera no longer reliable, FC crash and cannot pause it, play store downloads stop, "waiting for network", signal drops from time to time. I will probably revert to 03/30 (Only because I have a clean, working, good Safe Strap backup of it.) and maybe up to 04/05 or 07. But I will wait, give it some time, in the event you need a cooperative bug tester. That I never mind for the dev team.

Appreciate you making an appearance, it was getting a little hectic in here and sometimes the "voice from above" does a lot to calm things down and reassure the people here that they are not being ignored. My, my, what a job you got, dev team leader and CM Ambassador. Hah, is the pay good, can I get that job? ;)

I am just kidding, thanks for stopping by Micheal. :victory:
[Motorola Droid RAZR] kburt8:
My wife had this problem on her Droid 4 a while back and changing to RUIM/SIM fixed it.
[Motorola Droid RAZR] krestian:
Few bugs - report

Just for the record, since this is the forum to report bugs, I'm running 04-07 (UMTS) and still have the occasional phone app crash, where it won't recover by any means and just gives an unresponsive black screen with the subsequent self-reboot.

Another one I've spotted during the last few days is Wi-fi not turning on (I have Llama set up to turn Wi-fi on when I'm approaching home). It gets stuck somewhere in the middle and won't start or allow you to stop and restart it. Settings menu show "starting Wi-fi". Airplane does not fix it, the only way I've found is to reboot.

Both of these, the phone was not under a whole lot of uptime. Phone crash was probably two or three hours after boot, and Wi-fi was more like 10 or 12 hours into it.

On the other hand, I've been having some pretty stellar battery life with this release, which should also be mentioned / praised / appreciated :p. About 30 hours tops between charges, on the regular XT910, normal to light use.
[Motorola Droid RAZR] Ohmster:
You are right. No it shouldn't. We had *that* bug whipped 2 months ago. Michael (Stargo, lead developer for all Droid/Bionic phones.) took the responsibility to admit that the bugs got back in as of 04/07. I knew 09 would be bug ridden, but I did not realize it went back to 07. He is working hard now to "right that wrong", made a special build to help those afflicted immediately, and will get it out of new builds.

Communication w/each other helps. I ask for limited detailed install reports, to be followed up with a "what did you find broken" follow-up within the next couple of days and people are now starting to listen and report. I avoid these bad builds by looking for and paying attention to these reports, even going so far as to ask for more details when they are not given. Because we are "NIGHTLY" users, we are the guinea pigs and test everything new that is released. When big changes are incorporated, it takes days or weeks of reports and rebuilds to get it right again. This "report mining" of the thread is not a hard skill to learn. I haven't been burned by bad builds that I cannot get out of because I keep a good, working, recent build as a Safe Strap backup on my Ext SDCard. You can too. Drag the backup to Dropbox in ES File Manager and you will not lose your backup in case you screw up the phone/card. Backups for Safe Strap are under /TWRP/BACKUPS on internal or external, wherever you put them in Safe Strap. Do this for any "good, dependable" build you find so you can easily revert.

I think you are a teacher, right? Mr Glass and I pledged to help you. Talk to us and we will help you. By the way, I gave a mini-how-to for copying your SD Card or cloning it to a new or larger card. Glass posted the free tools and they are GREAT. The report is here:

How To: Copy SD Card data from one card to another

Download these tools man. I am not sure why you are messing up your Ext SDCard but this tool can help, per the guide, HDD Raw Copy Tool. Pop your card into the home or laptop PC, copy card to image file, put back in phone. Now you can restore that card ANYTIME by using that same, free tool to write the image to the tool. Effort needed is near zero, total time it takes is maybe 15 minutes. Never lose photos or videos again, my friend.

Okay, don't want to "write another book", just letting you know, you have friends here, 2¢. Go teach those kids, man. :good:

---------- Post added at 12:04 PM ---------- Previous post was at 11:54 AM ----------

Can someone please tell me what is "UMTS" and the difference between UMTS and UMTS-spyder? I know we have spyder build phones, but what is this UMTS stuff all about?

Mr. Glass, I want to update my Safe Strap. But as I recall, this must be installed from your stock rom and should not be installed in the cm11 build we have running. I remember this because I had it already in place, did the update from cm11, and "lost it" after reboot and had to go reinstall the apk under my stock rom. So I will revert to stock and do the install. Hey good looking out buddy. These are things we "have to know". :victory:
[Motorola Droid RAZR] Mr-Glass:
UMTS is XT910 (UMTS is the network used based on GSM) - regular Spyder is XT912 - I just saved the regular SS for spyder to my dropbox and installed in CM11 - once installed I opened the SS app and Installed the new version, rebooted to recovery to check that it updated and all was Ok.. I think the older safestrap upgrade from 3.11 to 3.5xx or 3.6xx had to be done on stock slot - this did not seem necessary now..
[Motorola Droid RAZR] Ohmster:
I am not too sure about XT910 phones, but you should know that since 04/07, the nightly build have bugs in them and are still being sorted out. If you are using such a build and need a stable phone, revert to a build prior to 04/07, such as 04/05 or even 03/30. I notice that they are all disappearing from the cm server and was asked today by two people to give them my copy of 03/30. I took the time to upload it to Comcast, gave the link and MD5 checksum so you know you got a good download. If you want it, here is the file.

MD5: 9DEF332B275A7E82DB287B228994F6E5

cm-11-20140330-NIGHTLY-spyder.zip

Again, I do not know about 910 phones, but this is a good, stable build. Good luck. :good:

---------- Post added at 12:16 PM ---------- Previous post was at 12:13 PM ----------

Oh cool! Thanks Mr. Glass. You didn't have to uninstall it first, did you? I think it just overwrites and an uninstall is not necessary, correct me if I am wrong please. I am downloading it now.
[Motorola Droid RAZR] Mr-Glass:
I did not uninstall - just installed over top - the install should show to that effect..(the install inside SS app)
[Motorola Droid RAZR] Ohmster:
No, Noe! (no no, that's funny. Hyuk hyuk hyuk!) :laugh:

Come on man, make with the fix. What did you do, go out of town or something?
[Motorola Droid RAZR] krestian:
Hey thanks for that. I, too, have some older versions back home, I just noticed I'm keeping them in my disk for longer than CM in theirs :D. I don't have them all however, but when I get back there tonight I'll put together a Google Drive shared folder for the benefit of the community. Will post my list tonight JIC anyone else can use something there.
[Motorola Droid RAZR] Noe!:
No, no I'm here. A while back in this thread you were talking about the Music2SD module for Xposed. You said that after a reboot the songs did not save to the external SD card, and I had suggested you use this link and also to downgrade to version 1.7.1 of Music2SD. With the release of KitKat, Google made changes on how apps can write to the external SD card, which practically made it useless. With the app that I linked above, it restored the ability for apps to write to the SD card (which Music2SD does). I suggested that to see if it would work for you.