yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Ohmster:
Thank you Mr. Chen. That is awesome that you can help. Many thanks, my friend! :good:
[Motorola Droid RAZR] chinkster:
ok i found a backup of 4/5 nightly that i made so i will revert to that then upgrade to 4/19. hope i dont have any problems. thanks ohmster
[Motorola Droid RAZR] Ohmster:
Now THAT, sounds like a PLAN, chinkster. This is an awesome way out, by reverting to your backup of early April, you will get a solid, working phone. Then, you can just flash this file. Since it is an update, I don't know if you have to wipe anything. Wipe dalvik and cache for good measure before & after the flash. You *Could* wipe system while in recovery, as well as dalvik and cache, BEFORE you flash the 04/19 file. Then reboot.

This is a standard OTA update though and should contain the necessary wipe scripts as any OTA update would. Flash OR wipe, flash, reboot should work fine. Then install the wrapper if you need Bluetooth AS (artificial speech) and if necessary, orange bar fix and APN as well, if you need them.

...never mind orange bar fix, I get it now. ;)

I think you are on track and know what to do now, chinkster. W/out theme engine, we have the same cm11 we had before that runs well. May need orange bar fix if there is one and APN, ONLY if you need it, and you are experienced with these familiar issues. Not like these persistent lock ups, black screens, UI crashes, etc., in the current builds.

Good luck to you! :highfive:
[Motorola Droid RAZR] ChungHung.Chen:
These two files are for people who still using version before 05/06.

It can be flashed in recovery(SafeStrap) so you could patch when you flash system.

It should work in May build, but I don't know if it works in April build.

Could someone test it and report? Thanks.

P.S. According CM changelog, this should be patch version 12.
[Motorola Droid RAZR] Ohmster:
Hey Chinkster,

You get a stable phone up yet? Emil has a whole crap load of April builds to donate for those that want a phone that works all day. I don't want to put all these up if you don't need them. I would like to know if your idea of reverting to the early backup and updating to 04/19 worked. You get a good working phone, all your stuff there? Any APN issues or stuff like that?

I am going to sit on 04/19 for a while until this darned theme engine either get's it's stuff together or gets canned.

If you need/want a different April build, let us know, may be more available to choose from. April 19th is alright. Orange bars but they don't hurt anything, I still have Google. I use rainbox icons from Xposed Ex-Themer. The colors are nice but there is a check box to allow them to show change state colors.

If you are happy an no one else wants some April builds to pick from, we will leave it be for now. But if others want/need some early builds, speak up y'all and I will get some more. Good Morning.
[Motorola Droid RAZR] leperkuan:
I ran 05/07 for a couple days and the only down side was a crackle during video recordings audio and a beep every 10secs during phone call. I just updated to 05/10 and I haven't recorded video but phone call beep stopped. :)
[Motorola Droid RAZR] chinkster:
hey ohmster, yeah i reverted to an old backup from like april 5th or something then dirty flashed 4/19 over it and did Jakes orange bar/apn fix as well. one problem i had today was that my phone wouldn't pick up LTE even tho i know i was in an LTE area. it was stuck on 3G and when i go into settings>mobile network settings>APN's nothing was bubbled. usually the LTE - Verizon Internet is bubbled but when it was stuck on 3G and i went into the settings to double check, nothing was bubbled. Don't really know what caused it but that is what happened. i am going to stay on this 4/19 build for a while until things get worked out.

EDIT: btw, thanks Emil for the april builds.
[Motorola Droid RAZR] Ohmster:
Yeah, I get that too sometimes. Signal bars drop to near zero, only 3G available, but driving around in a car shows this does not last, the bars pickup and signal is restored fine. I can still make calls when this happens but I doubt I could watch HDTV live video when normally, I can. For the most part, 04/19 is a good build for me, just not 100% consistent with signal strength. Well if Emil comes up with any more builds from April, possibly late April, I will put them up. Just be sure to backup what you have that works, just in case.

Take care.
[Motorola Droid RAZR] Ohmster:
April builds available as temporary work around while cm11 is in a state of flux

Hey Guys,

I had offered up a few April builds as "Rescue Builds" to rely on and use while the current build set is in such a state of flux with problems caused by the theme engine. To consolidate all of these files in one post (This PSA is taking up WAY too much board space.), they are all listed together in this one post.

I do have access to a few more if there is a demand for them. As far as I am concerned, ONE individual constitutes a demand for the files. And without further ado, here they are!

Add to that my own contributions of 04/27, 04/28, and Mr. Chen's top shelf flash-able audio wrapper zip files, and you are pretty much covered to install something more stable that you can use in the interim while waiting for cm11 to stabilize.

APN fix for those who find it necessary:

Remember, these April builds have problems too.

Mostly orange bars, signal dropping, or APN issues. For me this is minor, never had an APN issue, the orange bars do not mean much, all Google services still work, and signal dropping seems to be while you drive or go to different locations, they always restore. But they do not lock up, force close, or "get stuck". It would probably be in your best interest to grab a few and tuck them away on your hard drive, just in case. Since this is a temporary measure, please let me know if it works for you and if these files are still in demand or if you find them not important so I can stop. Hope this helps somebody, goodnight folks. :cool:

If you find this post helpful in any way, please give thanks to Emil [MENTION=5685307]ef141[/MENTION], Mr. Chen [MENTION=52527825]ChungHung.Chen [/MENTION], and [MENTION=4245858]Ohmster[/MENTION] (myself), if you feel it is warranted. Thank you!

Last and Most Important Thing:

Anyone with experience installing, using, testing

ANY May builds of cm11

are encouraged to report on the build,

please

. Install OTA or clean, Immediate Problems with install, AND ESPECIALLY any issues noticed after a day or more of running the rom.

Let's make this work. Let's "Do This". Thanks everybody for your help, diligent reporting, and especially for your help assisting other members. Good Night. :victory:
[Motorola Droid RAZR] suhaspatwa:
I installed this on my KDDI Japan phone, and gives me this error when called to someone

unfortunately, the process com.android.incallui has stopped

Plz tell me what should i do? I tried flashing this rom many times. do I have to any radio flash?

regards

Suhas
[Motorola Droid RAZR] GTiceman:
I am on 5/08 and am quite happy. I still get orange bars but it seems like the phone reconnects automatically more often on its own. I can't speak to batter life as my batter is destroyed but I can make it a whole day, which is amazing for me.
[Motorola Droid RAZR] Dwillian:
Looks like there is a fix for the system UI crash in the 5/12 nightly. I've just flashed it and will report back later once I've tried it for a few hours. It does seem more responsive then earlier builds that had a lot of lag on my device.
[Motorola Droid RAZR] Omegadrive:
Sweet, downloading now, installed 05/11 last night and everything was fine until I woke up this morning, had an incallui crash every time I made or received a call, reinstalled a couple of times and issue persisted so had to revert to 05/09 and now all is fine (except the UI crashes). Will report later. ?
[Motorola Droid RAZR] stargo:
Seems this fixes another SystemUI crash, but not the OOM-problem.

This is currently handled in https://jira.cyanogenmod.org/browse/CYAN-4047 and it seems it's a bit more involved than just the "view"-change I linked to earlier.

Regards,

MIchael
[Motorola Droid RAZR] Omegadrive:
Just found out that on 05/12 build, was I the middle of a game then a client came by so I turned off the screen, heard a notification, turned on screen, swipe down from lock screen to see the notification, boom, UI crash and this time took almost a minute to recover. ?
[Motorola Droid RAZR] Ohmster:
Hey Guys,

I cannot thank you enough for taking the bleeding edge and most important, reporting on it. I too am itching to get back on the edge, just cannot chance it for lack of a dependable phone. I can and will update for testing if necessary, and revert if need be.

Special Recognition and Thanks:
[MENTION=719744]GTiceman[/MENTION]
[MENTION=5362796]Dwillian[/MENTION]
[MENTION=4867965]Omegadrive[/MENTION]
[MENTION=3457922]stargo[/MENTION]

For testing the new builds, reporting on them, and providing followup reports. And of course Micheal, for following the chatter and giving updates. You guys rock! :victory:

Thank you. Thank you very much. :good:
[Motorola Droid RAZR] chinkster:
Ohmster, do you know if the 4/28 build has the signal drop problem?
[Motorola Droid RAZR] Ohmster:
I believe they all do. Mine have been slight though. In some areas, it drops pretty low, but does not last that long and I can still make calls. Drive around and it clears right up. It is doing that now on 04/19. None of these April builds ever stopped the phone from working, but signal should never really drop here unless inside of a cement building or something.
[Motorola Droid RAZR] Dwillian:
Been running 5/12 nightly all day today (about 10 hours). It seems a bit better than previous May nightlies, but I have had a couple UI crashes (current app freezes, screen goes black, and device becomes unresponsive. After 2-3 minutes the device revives and goes to lock screen, after unlock it takes a minute or so before all app icons and widgets are redrawn on home screen).

I've also had some issues with orange bars as I drove around town. Hoping the UI crash problem can be fixed soon.

Sent from my Droid RAZR Maxx (XT912).

Please click thanks if my post is useful to you.
[Motorola Droid RAZR] Ohmster:
I will give you Thanks in a heartbeat. Fortunately for the group, we have several members who are sitting on the bleeding edge, sticking it out, reporting the installs, and most important, reporting the followup on how the build performs, weak spots, bugs, and deal breakers. I posted in a previous post but will repeat it for those that missed it.

Special Thanks and Recognition

[MENTION=719744]GTiceman[/MENTION]

[MENTION=5362796]Dwillian[/MENTION]

[MENTION=4867965]Omegadrive[/MENTION]

[MENTION=3457922]stargo[/MENTION]

For reasons stated above. Installing a new build and keeping it to yourself may be nice for the individual, but does nothing for the group at large. We need, look for, and depend on reports like these to know when we can update and not lose jobs, appointments, important calls, etc.

From what I can deduce, we are getting better with the new nightlies, but the main culprit is illusive. Per Micheal (Stargo), our developer:

Seems this fixes another SystemUI crash, but not the OOM-problem.

This is currently handled in https://jira.cyanogenmod.org/browse/CYAN-4047 and it seems it's a bit more involved than just the "view"-change I linked to earlier.

Regards,

MIchael

Now I for the life of me do not know what the "OOM-problem" is, but whatever it is, a man would consider this a testicle breaker. Last I knew, the new theme engine started causing elusive problems that mimic earlier problems, thus making troubleshooting very, very difficult and frustrating. I would love to see the bug report on this, if anyone has the link, by all means, show me. ...uh, never mind, Micheal provided the link I needed to see.

For those that want to know, the OOM killer is a Linux process to kill applications when memory is dangerously low. The link provides an excellent article describing it. And since Android is a scaled down version of Linux, the issues are often the same. I often wondered how Kit Kat was able to return such speed back to an older device, now I know. They stepped up the OOM Killer, quite a bit. And if you look back on your phones, there is an awful LOT to be killed as the apps that refuse to close are non-essential applications. I could not believe when "Let's Golf 3", a fantastically graphic game, had NO exit button. This thing eats memory like a homeless man scarfs down free hors d'oeuvres at an open house banquet. And, ...it has to run all the time, why? Advertisements, what else!t Facebook, guilty, and almost ¾ of all apps do this. Thank God for Kit Kat. Now the problem is, how to tame Kit Kat. Ha, that is pretty funny. :laugh: But Micheal is a very dedicated developer. That man will not sleep until this is fixed, and it may take quite a while. I *do* have faith.

I will do my part by keeping the community alive with known working earlier builds and advice, but I sure am chomping at the bit for something new, "that works". Thanks Dwillian, :good:
[Motorola Droid RAZR] GTiceman:
Thanks Ohmster

I have not had any crashing on 5/12 like the others have stated. I have had orange bars off and on.

I will say that I had two weird issues. One was no internet connection while on wifi when my internet was fine, items wouldn't load. Resolved itself in 5 min from the time I noticed it. Also I had wifi toggle itself off last night when I was updating things on my goPro but once I toggled back on it seemed fine.

Throughout the day I will make some calls, check email if the orange devil allows it, and text. I leave BT on all day, along with wifi, neither is connected except when I am in my car(BT) or at home(wifi).

I might jump to 5/13 later today
[Motorola Droid RAZR] Ohmster:
Awesome report, GTiceman. Thank you. Let us know how it goes.
[Motorola Droid RAZR] chinkster:
Hmm getting sporadic APN not specified popups even tho I've done Jakes APN fix and *228 to program the phone. Had to go into settings>mobile settings>APN and toggle the vzw lte internet in order to get the popup to go away

EDIT: well even toggling the APN vzw lte internet from one to the other didn't help. i had to do jakes apn fix AGAIN in order to get the popup to go away.
[Motorola Droid RAZR] Ohmster:
Oh man, brings back memories, doesn't it? Yes, my phone is set to LTE-Verizon Internet, later in the day after a reboot, it changed to something else, I had to set it back. Yes, April is filled with signal issues, but at least I have a phone that works. We have some good people testing and reporting on the new builds, so, hopefully it won't be for long.
[Motorola Droid RAZR] Bobcus Leper:
Any idea why the phone is killing my battery? I'm not activated BTW.

I'm on the 05-13 nightly.
[Motorola Droid RAZR] leperkuan:
You need to reset the battery stats.

Is the phone hot?

Let the phone goto zero and shut down, plug into wall charger and do not power up, allow to charge to 100%

This cycle should be done frequently.

---------- Post added at 03:05 PM ---------- Previous post was at 03:02 PM ----------

Im currently on 05-10 and things seem great, was actually about to update to 05-13

my only issue is, i can receive group messages but people dont get the ones i send...

i feel an RC is in our grasp.
[Motorola Droid RAZR] Bobcus Leper:
Thanks! I thought that I might have to calibrate my battery. I've been flashing a lot.:D:p

---------- Post added at 10:17 AM ---------- Previous post was at 10:16 AM ----------

And yes, my battery gets to 120°.
[Motorola Droid RAZR] GTiceman:
5/13 showed no noticeable improvements for me so on to 5/14
[Motorola Droid RAZR] JakeDHS07:
Updated to 5/14 strange glitch not sure what to do about. Using Poweramp and on the now playing screen (the one showing the album art for the current playing song) the controls and text at the bottom keep jumping size from their normal size to small. Its driving my eyes crazy. Can anyone else reproduce or have a way to get it to stop?

DROID RAZR MAXX CM 11 JBX KERNEL

---------- Post added at 11:51 AM ---------- Previous post was at 11:40 AM ----------

*Update* After some tinkering discovered if you tick the Disable HW Overlays option in Developer Options it stays at correct size and doesn't jump. This of course forces GPU to do the screen composition so the issue must lie somewhere else. Though this is a easy work around at least for now. Unticking the option does bring it back as well.

DROID RAZR MAXX CM 11 JBX KERNEL
[Motorola Droid RAZR] ef141:
Man that could drive you crazy!
[Motorola Droid RAZR] Ohmster:
Jake, have you monitored the CPU load with Poweramp Pro when using it? I had issues with it trying to verify SoundGirl's flutter issue. Only happend when CPU load would really top out over 80% and give a stutter sound. I chalked it up to old software on a new platform, but have not gotten any recent releases of poweramp to play with. Yours okay? CPU load not too high?
[Motorola Droid RAZR] JakeDHS07:
No issues CPU being too high. But I am also using JBX and Trickster to regulate CPU

DROID RAZR MAXX CM 11 JBX KERNEL
[Motorola Droid RAZR] Ohmster:
Ahhh, thanks for the tip. I really miss that JBX kernel. As soon as I find a current build stable enough, I think it is time to reinstall it. Great information, thanks.

Note:

Well, you are not reporting any UI crashes, lockups, or black screens and that is what scares me the most. I think I will try the most recent build. Backing up stable 04/19 now, only complain orange bars and signal drops.
[Motorola Droid RAZR] JakeDHS07:
Nope UI has been fine all day

DROID RAZR MAXX CM 11 JBX KERNEL
[Motorola Droid RAZR] Ohmster:
Backed up April build, stable with orange bars and fading signal issues, minor.

Used OTA update to 05/14 nightly. Update was normal, everything appears to work quite well on the phone. CM11 and existing pa-gapps only. My issue with May builds has always been black screen lockup when receiving calls. Made a call to myself, screen lit on it's own, call proceeded normally, ended call, back to home screen. No apparent issues.

Now I will run and use this for a day or two and report back. It seems that when hours accumulate, the right conditions occur, problems will manifest themselves. I will use the phone normally, play some games, push the memory a little bit, and report how stable the build is. It does look like Micheal and the dev team are making progress, and THAT is very, very welcome news. Stay tuned for more information... :)

[MENTION=3457922]stargo[/MENTION] Thank you so much for your dedication and persistence. I had to duck the early May builds, they were simply too unstable with lockups for me to use on a daily basis. I rely on tester reports and Jake just gave a positive review on 05/14 and wanted to follow suit. Now Jake does use a custom kernel and he has the experience to tweak his phone quite well. I will do mine as an ordinary user and see what happens.

Micheal, if you have a moment, could you tell us briefly what current issues remain as to know what to expect and how and if to report it. Theme engine, OOM Killer, UI issues? Thank you for your devotion and stellar performance in coding. This only comes with diligence and man, do you ever have it. :good:

NOTE:

For Chinkster and others on the April builds to have a reliable phone, I do have a 64GB SDCard from Amazon ($40) and can afford the space for backups. I will test the current build 05/14 and report if it is safe to move on. If you can afford it, the large external SD Card is probably the best investment you can make for your phone, best thing is you can take it with you if you upgrade phones. The 16Gb card I had vanished pretty quickly and fighting for space was always an issue.
[Motorola Droid RAZR] Omegadrive:
I updated to 05/14 like 2 hours ago and first thing I did was force the UI crash with the method I mentioned several posts ago, it crashed, so still not fixed. ?

Btw, found this post browsing the forums for answers on the system UI crash, maybe a workaround until official fix is released?

http://xdaforums.com/showthread.php?p=52636929

Btw, have no idea what the guy is talking about, maybe [MENTION=3457922]stargo[/MENTION] can figure it out or the post is talking about a different issue?
[Motorola Droid RAZR] Dwillian:
I've been running 5/14 all day without any force close or orange bars. It also seems fairly responsive.

I tried finding your post on how to cause a force close, but I didn't find it. If you post a link to the post I will see if I can reproduce the force close.

Sent from my Droid RAZR Maxx (XT912).

Please click thanks if my post is useful to you.
[Motorola Droid RAZR] Omegadrive:
Here is the post:

http://xdaforums.com/showthread.php?p=52446319
[Motorola Droid RAZR] eregev:
I eagerly wait to see how you're phone is doing in a little while. Like you said, love being an "average Joe" tester (though I should start reporting my issues to the rest of the forum :eek:) but the past couple of weeks were just too unreliable for a daily driver. Despite my 16gb memory card limit, I'll make a backup of my 4/19 build before moving forward (I'm actually thinking ahead this time ;) ). I hope to hop on 5/14 and continue on the nightly track when reports on extended use start coming back.

Thank you all for testing and squashing bugs!
[Motorola Droid RAZR] GTiceman:
I am on 5/14 and I have rarely seen orange bars. Seems more stable for me than some of the recent nightlies. I have not tried to force crash the UI.
[Motorola Droid RAZR] Dwillian:
I installed Honor Bound, played game for 7-8 minutes, exited the game, closed all recent applications, swiped down on notification bar. I did not experience a FC. Did I follow the procedure correctly?

Been on CM 5/14 nightly for 24 hours now. Everything seems to be working fine for me so far.
[Motorola Droid RAZR] Bobcus Leper:
Has anyone tested the 5-15 nightly? I'm completely happy on the 5-14.:p
[Motorola Droid RAZR] jeff_roey:
I'm also pretty happy with 5/14 . . . all except battery life which has been in the crapper on every CM11 nightly I've installed. I'm burning an average about 5% per hour on my Maxx and can't seem to get it to slow down no matter what I try. Stock JB, same conditions, same locations/signal strength, same app config, I'll see between 1-2% per hour of burn. My current setup is the following:

- 5/14 Nightly with stock kernel.

- cLock frozen using TIBU

- Google Search, Google+, Hangouts all converted to user apps using TIBU and hibernated with Greenify

- Nearly all other GCM apps including Maps and Skype hibernated.

I'm not smart enough to fully understand BBS but in a 9 hour period disconnected from charge, the device is awake 5H, deep sleep 3H 50M), RILJ is my biggest partial wakelock offender (1H 12M) and powermanagerservice.wakelocks is my biggest kernel wakelock offender.

I'd like to hear from soe of you with good battery life what you've done in your setups that you think has made a big difference: freeze any apps? Change governors? using JBX and if so, what settings changes did you make? What are you hibernating?

Other than better life, these ROMS perform a ton better than stock JB for me. If I can get past the battery burn rate, this one is worth staying on for a while. A little help please?
[Motorola Droid RAZR] Omegadrive:
I keep having the OOM /crash issue, even after long calls if I swipe down the status bar it crashes all apps and call. This is on a dirty install from OTA but last fresh install was last week with M6.

Also, I have no idea how many apps you have installed and running in background, my free memory hovers at near 250 normally, after exiting the game I get to around 120 free, that's when usually the crash happens.