yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Dwillian:
I just did a clean install of 6/17 nightly and PA mini-modular GApps. So far so good.

Previously I was having increasingly severe problems with spontaneous reboots (usually while navigating using Google Maps). I am hoping that a clean install will fix that problem. I will report back after I have a chance to try navigation for an extended period of time.
[Motorola Droid RAZR] Ohmster:
Yes, on it now. Very smooth, nice so far but too soon to tell if any hidden issues. I will say one thing, I have my lovely rainbow signal icons back in full 4G. 06/16 was an improvement of course, over 13, but orange city. Now this is a NICE change. Solid Google lock, great signal. First time since 06/13. I am not concerned that things will go bad but I will report if they do. Like I said, 06/13 had "way too many items" included, piled up since the compiler went down. Anytime there are 20+ items, we are in for a rough ride. Best to wait for the build to simmer down to something reasonable like 5-9 items instead.

What is bad about many items in the build? Each change has the ability to alter the entire phone. Theme Engines are particularly suspect because they touch the entire UI and FC will become your best buddy until the issues are rooted out. With so many "improvements" in one build, they have not been tested in the wild, and never in such a cluster. So, debugging is more difficult and prolonged. The days to follow, these hidden bugs will be rooted out. So 06/17 with a more reasonable item count of 13 items, adds more improvement to the cluster of 06/13. We have 4 Theme/UI items in the change log. We have black screen reintroduced with the Theme Engine. cmupdater is getting some attention and sure needs it. And more, less aggressive items.

Is 06/17 good? Yeah so far. A sweet OTA and here I am. I am so happy to see the orange go. Very stable now, not "chugging" like after 13. (Friday the 13th, BTW) Anything really goes bad I promise to let you know. But this, I can feel it, is *much* better! :D

* Will know more about signal tomorrow when I drive around. Signal has been dropping significantly when driving a mile North and that way I shall go tomorrow.
[Motorola Droid RAZR] my2cents:
Guys, my wife found a weird bug. If she goes to the camcorder and then touches the screen to focus (like you would for a still shot) then hit the record button it will FC. I dont ever bother with focus I guess, so I never noticed the problem. Any fix? On 6/14.
[Motorola Droid RAZR] d.casper.b:
Having black screen issues on 06/16.

Only every once in a while it happens when trying to wake phone up.. Ends in a reboot..

Doesn't seem like anything significant in new builds will address this though.
[Motorola Droid RAZR] jeff_roey:
I've been holding onto 5/17 and noticed the same problem just yesterday. Tried focusing to take a pic but had camcorder selected without realizing it. I wiped app data before realizing I had the wrong mode selected but it didn't help. Still there but like you, never really use it.
[Motorola Droid RAZR] Ohmster:
Hello Casper,

Yes, something is being done but you may not see it addressed immediately in the change log. The Theme Engine is a dangerous thing to create and then "unleash" on the build because it affects every UI there is on the device. It should be released in bits and pieces to catch the bugs and stomp them out.

Stargo revealed a couple days ago that he found what is "bringing it back" (black screen) and has to pass the info along because he does not work on the UI. I will give you a direct quote so you can rest assured it is being worked on and why.

I *hate* that black screen. First got clobbered by it because of "The USB Host choke point". Where all system data must flow through the USB host bridge, it is proprietary code and was very difficult and prolonged to fix. Once fixed, it was gone for months. When it came back, I was *sure* it was the same issue and you know Ohmster is very vocal about such things. I stand corrected, Stargo replied it is NOT the USB host but since problems reoccur and mimic previous issues, troubleshooting it can be very difficult. I forget what it was caused by that time. "Timer tick" okay he is over my head now but is not only aware of it but has a very good idea where the problem lies and will bring it to the attention of the them engine builder to debug out and assist, if necessary.

That black screen really bites, dude. You get a phone call, cannot unlock the screen fast enough to answer it, lose the call. OR, cannot hang up the phone because the hard buttons light, but not the screen. When it is severe, one has to hold the power button and volume down buttons until it forces a power off. Not good. :(

It's nice to know your issues are being addressed, isn't it? We are blessed in this thread and development branch with a very good, dedicated developer. Poor man is tired too. Grueling student scheduled, work, play, work again, dead tired. This explains why the cm11 Theme Feature does not fully "work" well like it did in cm10. It takes time to get stuff like that right because it's tentacles are far reaching. Hope this helps. :)
[Motorola Droid RAZR] azurikai:
I've got the Droid RAZR, installed CM11 06-16-2014, JBX, WiFiAP and the GAPPS.

Everything seems to be working 100% but I am not able to connect to the mobile network.

Any ideas?
[Motorola Droid RAZR] brkahughes:
Most strongly suggest that you only install cm and gapps to begin! WiFiAP is no longer needed, and JBX is optional. You may have a conflict with the WiFi fix, so you should wipe and install again only the base system, then after it's working, JBX if you want.

Sent from my continually born again RAZR MAXX!
[Motorola Droid RAZR] Ohmster:
Wow! I just mentioned that the video cam is still broken because I cannot pause then release pause because the release button is so tiny and the screen it touch sensitive to take a photo during record, I almost never hit that tiny dot and it causes the video to crash and leave no useable video file.

I never "touched the screen prior to record" for focusing though. I just tried it and got the focus rings, and unlike the still cam where focus lock turns the marks green, they go red on the video camera. Not sure this is "good" or the red marks could simply mean "video mode" instead of still mode. Once focus rings get red mark, I hit record and do not get an FC, video recording commences. BUT, NOW I CAN pause and un-pause the video camera with ease! OMG, and it still takes pictures during record! Oh here we go, once I close the camera and it is gone, I get an FC on the camera after it has been closed. But, I can use the video camera pause feature as well as take stills too if I touch the screen prior to recording.

Hmmm, that is interesting. If we all make observations, share them, they begin to add up. At some point, we can take it to developer and have it addressed. Great work boys, thank you! :good:

---------- Post added at 01:34 PM ---------- Previous post was at 01:20 PM ----------

Hughes you are *so* on the ball and ahead of me, I just saw this and was planning my reply when you beat me to it with exactly the right thing to say. :highfive:

Hughes is right, it is most likely your patch that is ruining the build for you. You have to go absolutely clean now. Delete the rom slot, recreate it, and bump up the user data space for yourself. Flash cm11 and pa-gapps ONLY, wipe dalvik and cache, reboot.

JBX is a custom kernel, it does work, and works quite well, but can become out of sync with our builds because they are nightlies. Every feature you can get in JBX is available in apps or Xposed modules but for one, overclocking by 100MHz and it must be reinstalled with every nightly flash. Leave it out for now, just do cm11 and pa-gapps like Hughes said and you will have a good, working build. 06/17 is very good, try that or if you want older and more stable, 06/07. Good luck and thanks to Mr. Hughes. :cowboy:
[Motorola Droid RAZR] Ohmster:
Follow up Build 07/17 report for Noe!

I posted a build install report for Noe! yesterday, stated that 06/07 was good, but I could not report on signal strength until I ride around a little bit in the day. I found no issues myself with 06/07 but driving a little as a mile in the last several builds would cause my signal strength to drop as much as to 0 as I drove. This phone in this area will never and has never dipped to 2 or less bars or even zero, unless in a heavy concrete and steel parking garage or other, similar concrete and steel structure. This build does it too, 06/17 will drop as low as zero while driving around in the open air, right in the middle of town where this should never occur. I corroborate these findings with the Settings Menu/About Phone/Status. In there you get a real time signal strength meter in dBm. At home, full bars = -76dBm, very strong.

Since we are dealing with negative numbers, a higher number means less signal. When dropped to 2 or 1 bar, had reading of -100dBm (1 bar) and at total zero bars, had reading of 0dBm, which is so strong it would blow the phone out of my hand, but in this case simply meant, no signal detected. But areas like this are in very sparse, isolated pockets, not in general. "The old phone" would never drop this low, anywhere in town. Good news is, move even slightly and the signal would pick right up again.

Summary:

06/17 is a good build. I get an FC if messing with the video camera sometimes, nothing else really. Signal Meter appears to be really sensitive to change, large, "range gaps" in coverage in what should be a relatively completely covered area, but the gaps are small in size. Screen shot of full bar signal, 4 bars and a reading of -79dBm attached. Good build. :)
[Motorola Droid RAZR] GTiceman:
6/17 seems solid for me ... had some weird issues with 6/16 where phone missed calls and I lost all audio for notifications
[Motorola Droid RAZR] Ohmster:
Build install and test reports are so essential to the smooth operation of this thread.

Thank you Iceman. Please edit to include your method of updating such as manual, OTA, clean, any add-ons such as JBX. You will learn to be a good tester and reporter and as I convince others to see the value in it, they too will reward you with Thanks.

Build Install & Test Results are very Important to this thread!

Build Install & Test Results are so important to Members who cannot afford to be without a phone for a day and must look for reliable build upon which to flash. Everyone please cooperate with this humble request for those that need it and you too will find yourselves leaning more and more on these reports. When posting a build install and test report, please include the following:

build date

Update method: OTA, manual with what else, or clean

Any aonomilies apparent during the process

How does the update feel in your hand within the first hour to you

List any features that are now not working or cause an FC

List any new features that you have found

Give a quick summary and your immediate opinion, "Yes, everything works great so far:

DO perform and submit a followup post when you find problems the next day. i.e.: mms out, no APN specified, etc.

Thanks everybody. Please help with the build reports. They are so important.

Discuss issues with each other in public so that if enough information exists that can be corroborated, it can be taken to developer for removal and publishing to the build tree. I have successfully been able to get issues fixed like the Bluetooth Artificial Speech bug as it was easy to corroborate and demonstrate to development.

Thank you for putting up with me and yes, I am aware that I talk too much. I am working on becoming more germane to the issue and brief. :cool:
[Motorola Droid RAZR] CoreyWillWhat:
Also be sure you are using the correct CM11 build.

XT912 = Spyder

XT910 = UMTS-Spyder

Sent from my Nexus 10
[Motorola Droid RAZR] otavioricciotti:
Hey guys.

I'm trying to install lastest CM11 nightly in stock partition, but I always get "Failed" status. Does anyone know how to install it correctly?

Thanks for the help :)
[Motorola Droid RAZR] dtrail1:
If you're talking about my build, there's a newer one with some fixed.

ART is known to cause FCs as this is an experimental feature at the moment, so no gapps will fix it.

You need another camera app to use external storage, like Moto X Cam.

Gesendet von meinem XT910 mit Tapatalk 4
[Motorola Droid RAZR] Nandeh:
[MENTION=4287139]dtrail1[/MENTION] the last build at http://hosting.crackflasher.com/?dir=Devs/DWiZ/Roms/XT910/CM11.0 shows 2013-12-02 and 11:17:41 as last modified, and by your answers in this thread, you uploaded it later, in the afternoon or evening... It's ok the build or there is any problem with the server time?

Thanks!!
[Motorola Droid RAZR] dtrail1:
It's the latest one from the evening. Server seems to show the first time I uploaded it.

BTW: CDMA build is up!
[Motorola Droid RAZR] BigCrisco39:
Link for CDMA?
[Motorola Droid RAZR] 1droidmod:
http://hosting.crackflasher.com/

Thanks dtrail1!! ;)

XT912 RaZR SpYdEr CDMA

hit ThAnKs if I was helpful!!!
[Motorola Droid RAZR] dtrail1:
http://dwiz.crackflasher.com
[Motorola Droid RAZR] 1droidmod:
[MENTION=4287139]dtrail1[/MENTION] Hey!! In dhacker29's first cm11 build screenshot would not work. Message "Couldn't sabe screenshot. Storage may be in use." Next build elimated screen tear and screenshot issue. After all set up rebooted blah blah screenshot is not functional (for me) on your latest cdma build.. Thought you should know.

XT912 RaZR SpYdEr CDMA

hit ThAnKs if I was helpful!!!
[Motorola Droid RAZR] dtrail1:
I cannot test CDMA builds... But on UMTS it works fine - except some minor grapchical glitches (sometimes). Thx for reporting. Aynone else on latest CDMA without working screenshots?
[Motorola Droid RAZR] Defragger51:
I did a clean install of the 11/26 build and the gapps., reset factory wipe and wipe data cache and dalvik cache before reboot , and everything is working great, setup Google acct. re-installed the apps all over wifi and after a reboot the wifi wont connect to the router ,keep saying ( authentication error ). I have erased the connection several times used wps and even entered it in manually still it will not go past authenticating. Anyone have any idea why or how to fix it?
[Motorola Droid RAZR] haztv:
Will there be no more power widgets in the kit kat roms or is it still too early? I miss having my music controls and reboot and other buttons that I could select and arrange on the top of my notification drawer did they do away with those? Also the notification shortcuts u could place apps in for quick access I NEED these lol
[Motorola Droid RAZR] dtrail1:
You tried my build from yesterday?
[Motorola Droid RAZR] kenosis:
[MENTION=4287139]dtrail1[/MENTION], Can I install your lastest CM11 on system 2? When I tried, it stops with Moto Logo with red LED on.
[Motorola Droid RAZR] dtrail1:
BMM? Idk, I use SS as this is getting further updates and fixes. Once I sweared on BMM - but its battery drops on each reboots and some other issues are annoying as long as development has been dropped for BMM. SS is running much better for me. I have CM11 installed on my stock system. No problems so far.
[Motorola Droid RAZR] kenosis:
ႊThanks for your reply. I will try to use SS 3.11 again to try your build. :)
[Motorola Droid RAZR] seandop:
I bounce back and forth between SS and BMM. BMM seems to do certain things better for me (although as [MENTION=4287139]dtrail1[/MENTION] pointed out, the battery drain bug is annoying) and I've never run into a ROM that would not behave properly on BMM. If you're going to use SS, use version 3.65, not 3.11.
[Motorola Droid RAZR] kenosis:
Ok. thank you. i will use 3.65.
[Motorola Droid RAZR] Defragger51:
Thanks after re reading every line of yesterdays post and this mornings post I finally found the link to yesterdays cm11 spyder build. downloaded it will try it when I get my buddy's phone back later today
[Motorola Droid RAZR] snives:
Failing to find the delete post button =D
[Motorola Droid RAZR] scottgti:
Anyone else running today's xt912 build? I'm boot looping. SS3.65, slot 1. I was running the gummy 4.4 build. I deleted slot and started fresh.
[Motorola Droid RAZR] archie1988:
I will try now on my xt910 slot1 via ss :fingers-crossed:

Do i have to install only gapps that in the download rom folder or i need to install 4.4 gaaps too?
[Motorola Droid RAZR] Noe!:
6/17 is working good so far. I had an issue trying to install Xposed at first, but a reboot fixed that. Loving the new theme engine as well ?

Sent from my XT912 using the XDA App.
[Motorola Droid RAZR] segordon:
Are you using safestrap or bmm?

If you are using safestrap 3.65 or 3.73 all you need to do to install cm11 on the stock side is click on wipe, then advanced wipe and select everything except for internal SD and external SD. After that install like any other ROM.

Tapped from my Razr Maxx from the dark side of CM11 4.4.3!
[Motorola Droid RAZR] azurikai:
So I did only the CM and GAPPS, still on the 6/16 version... No luck with the signal. I did a triple wipe and installed them one by one to make sure I did the right order.

I'm installing on Rom Slot 1. Should I change any of these variables?
[Motorola Droid RAZR] brkahughes:
Sooo, do you have an xt910 or xt912? What carrier are you on? Are you installing the spyder or umts-spyder build?

Sent from my continually born again RAZR MAXX!
[Motorola Droid RAZR] Dwillian:
Well...I'm still having spontaneous reboots when I navigate with Google Maps. My XT912 seems to get very warm, almost hot, so maybe it's rebooting because it's overheating. Also I have orange bars right after a reboot and it takes 5 minutes or longer before they turn white. So, a clean install of 6/17 nightly into a newly created rom slot 1 with PA mini-modular GApps is not working for me.

Is it just my phone or are others having similar problems with the latest builds?

I'm getting so frustrated that I'm about to go back to Verizon stock rom. It has lag issues, but at least I can navigate without reboots and it gets fast connect to google servers (i.e., blue bars).
[Motorola Droid RAZR] GTiceman:
In reply to [MENTION=4245858]Ohmster[/MENTION]

I almost always do an OTA flash immediately after downloading the update from the CM Updater

6/17

OTA through CMU

Safestrap Slot 1

I made it through almost an entire day with no Orange Bars, toggled when they appeared and haven't seen them again since

I can't comment on Battery, those who follow my posts know this

I had a weird slow/gmail crash when trying to reply from a notification, I AM NOT on 4.4.3 gapps yet so could be part of it

Slight lag when turning screen on

Slight lag when updating like 6 apps, not a surprise there

WiFi solid, BT solid

No FCs except the Gmail one mentioned
[Motorola Droid RAZR] CoreyWillWhat:
I have the same issues on my Nexus 10 that's running official 4.4.3. While running maps it can freeze up or reboot. Happens often...usually while running Spotify at the same time. Thought 4.4.3 was supposed to fix reboot issues. Hmm Seems like it's a maps issue on 4.4.3 and not so much the ROM....or just 4.4.3

Sent from my Nexus 10
[Motorola Droid RAZR] scottgti:
What would cause this? My battery is draining fast.
[Motorola Droid RAZR] leperkuan:
on the latest snapshot,

after a week i guess i cannot send picture messages, i have been using hangouts.

group messages started sending as singles and pics will not go through.

"Destination address is unknown"

No APN specified

otherwise the rom has been very stable with great battery life.

this install was a clean install.
[Motorola Droid RAZR] l33tlinuxh4x0r:
Is anyone using cmdelta? I am and it installed 6-18 build but I looked on cmxlog and did not see it and I didn't see it on cm.com either. Did this build exist did it get pulled for some reason? Or is cmdelta just messed up right now?
[Motorola Droid RAZR] crackerjack1957:
I think it got pulled, I started downloading but it never completed.

Tried about 5 more times with no success.

Could be cmdelta server issues.
[Motorola Droid RAZR] l33tlinuxh4x0r:
Thanks for the reply.

BTW 5-19 is up on cmxlog!
[Motorola Droid RAZR] Noe!:
Is Google Now enabled? That might be the reason why.

(Referring to post #4791)

Sent from my XT912 using the XDA App.
[Motorola Droid RAZR] scottgti:
It always is, but I've never had it use GPS that much (check 2nd pic).
[Motorola Droid RAZR] Ohmster:
[MENTION=719744]GTiceman[/MENTION] it seems like you are about "par for the course". That's kind of how nightlies work. Terrible, then "oh it's working", you comment on how "FAST" the phone works and it does, but *something* is always wrong with it, and it gets better. Bad builds come along with orange bars, signal loss, black screen, you name it and these bugs get worked out, and all along the way, it gets more improvements. But it works, ten steps over Jellybean, and we want it. Someday it will go stable and Release, like cm10. Which was *very* good, BTW. This is what nightlies are all about.

This Kit Kat stuff takes some getting used to, it is very fast. When I use stock JB rom, I tap phone, map, anything and just put the phone down because it will take minutes for whatever it is to show on the screen. So I like it and by carefully watching build install reports, I can pick good and safe updates and have a good experience.and you can too. That and always making a backup of a good, recent build to revert to in case you get a really bad one. Sounds like you are okay, Iceman. :D

---------- Post added at 06:46 PM ---------- Previous post was at 06:33 PM ----------

[MENTION=2878595]leperkuan[/MENTION] Snapshots stink. Get off the snapshot and flash a newer build. Snapshots are "old" builds, nothing special, so why read yesterday's papers? It has issues like any other rom of the same period. It is not like you are going to "fix it" or anything. We all go through this. APN, black screen, orange icons, battery, etc., it goes away in later builds as it is reported, addressed, and fixed. Picking a particular build like any nightly or snapshot and then sticking with it, fixing it up, and calling it home is not the right thing to do here. You have a clean install, great. Now tap Settings, About Phone, CyanogenMod Updates, change Update Types to all inc. nightlies. Pick something new, 06/17 is reported good, 18 is likely more of the same, cleaning up the 06/13 mess. Could be better yet.

Use Safe Strap to backup what builds you have that work well, so in the event the update is very bad, you can revert to your backup. Delete older backups to make room. leperkuan, shapshot 7 is old, time to move on. :good:
[Motorola Droid RAZR] leperkuan:
I'm on 06/19 now. The snapshot was 06/09 I don't seem to be having APN issues on a dirty flash but I'm not sure if the pic messages are going through
[Motorola Droid RAZR] my2cents:
6/19 has randomly rebooted on me twice now... Used CM updater to install over 6/17. No JBX.
[Motorola Droid RAZR] GTiceman:
Having issues with 6/17 now where it reverts GPS to device only no matter how many times I switch it to High Accuracy. Also had some issues with SMS not sending, but a reboot fixed it.

Waiting to move on again based on the recent posts. Maybe 6/20