yashsingh1/xdaforums huggingface dataset:
[Motorola Droid RAZR] Omegadrive:
[MENTION=3457922]stargo[/MENTION]

No luck, disabled Swiftkey from my input devices and 6 hours later I got the crash again, but this time it was weird, let me give you the details:

I was browsing my Facebook feed when scrolling suddenly stopped, I figured the UI crashed again, it happened, but when I look at my status bar the bluetooth icon is gone (my headset was still connected but I disabled the media audio on it like 20 minutes ago to use the built in speaker), then I see the bluetooth icon come back after 20 seconds and it looks like the screen freeze is about to end and UI is going to reset, but then the BT icons dissappear again, 5 seconds later the phone does a soft reset and when it comes back all I get is a loop of this error:

View attachment 2716906

which doesn't let me load the whole device (it also reset my wallpaper) and I had to press all 3 keys to force reset my phone. When it came back I captured the logs. I have no clue if the logs are kept between restarts or after those fatal crashes, but here they are just in case they can help you find the issue. Oh and btw, I saw a post in the liquid smooth thread that someone was having the exact same issue with their rom on stock kernel (which I assume is based on CM source)

https://www.dropbox.com/s/37lwgfwbmrgsk23/2014-04-29_23.00.zip

Sorry for all the trouble :(
[Motorola Droid RAZR] my2cents:
Hi Stargo,

No, everything works "normal" now with the CM 4/26 through 4/28. Your commit a few builds ago fixed it. LTE connects just fine and quickly. What the APN swap that Jake outlines does is take the APNs from CM and removes them. Then we put the stock 4.1.2 JB APNs in their place. It actually does reduce the orange bars. However, I still get them - just not as much. Others claim it completely stops the oranges bars.
[Motorola Droid RAZR] chinkster:
i did jakes APN orange bars fix...if i flash another nightly, will i have to do it over again?
[Motorola Droid RAZR] Noe!:
Does anyone else having overheating issues? I can't let an app run for me than an hour at night without my phone to start churning out lava. Only a reboot seems to fix it. I'm not sure if it's related to JBX or CM or my phone. If someone else has this issue, I would love some feedback on it. Thanks.

Edit: using jbx 4/16
[Motorola Droid RAZR] Mr-Glass:
I had the same issue using JBX 4/16 and also had freezes due to the heat - I just dirty flashed CM again writing over JBX and have not had any overheating issues.. My hardware has never played well with JBX - others seem to have luck.. I have tried with clean slot - clean RSD'd phone and always go back to stock CM kernel.. YMMV
[Motorola Droid RAZR] Noe!:
Hmm. I figured it was JBX. I'll revert to the default CM kernel later on. Thanks.
[Motorola Droid RAZR] Ohmster:
I believe that one of the APN complaints were for MMS or something. I don't get it either with the APN mega checklist. This is not a "crap rom". Install it, boot it up, and phone connects. It is made that way. Now XT910 phones BFE might have other issues. with foreign carriers. " La Mierda de Brasil" may not be the best carrier and they have problems. So far as I know, XT912 phones "just work" in the US.

Orange bars will always happen, just not so much. Maintaining a 24/7 server connection is pretty hard to do. Network congestion alone will cause orange bars sometimes.

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

On 04/28 and my phone seems to come out of the case a lot warmer than it used to. No JBX, just stock cm11 and 04/28.

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

I have no idea of what they are doing. The phone should connect "out of the box".

Of course not. The issue may be a Google issue. They are not exactly sitting on their hands over there with the severs. Network congestion, new server configs, could all cause orange bars.

I am doing every update now, just hoping that my screen will light again when in call. I hardly ever use the phone next to my head, either Bluetooth or speaker.

But how does the phone "know" when to light back up if not using proximity sensor?

Well if you found something, God bless you man. Maybe I will get that fix after all. Thanks.

Sure! :o

Ah! You have put in the To Do list on the changelog. Good man, Micheal, good man. ;)
[Motorola Droid RAZR] ldeveraux:
I am/was having the same problem. It does go away when you remove JBX, but the CM11 kernel has more drops than I can handle. Using a week old CM11 build, so if something's changed in the meantime, let me know. Let us know if you experience similar drops with CM11 kernel!
[Motorola Droid RAZR] Ohmster:
Help Michael our Developer please!

[MENTION=3457922]stargo[/MENTION] (Michael) just stopped in to answer and ask a few questions. One question he does not understand and I don't understand either, is why are people adjusting, tweaking, or changing the APN on their phones?

APN= Access Point Name

Cellular data for the phone.

These roms are supposed to work, right out of the box and get the APN right, first time. Here is a screenshot of my APN, it is exactly right for my phone and carrier. Everything works and I didn't adjust anything.

I remember some of you guys saying things like "Cannot find specified APN" or something of the sort. What were you doing when you got that message? I remember a couple of months ago we did have to adjust our mobile networks to CDMA+LTE/EVDO and take it off "Global", but that is for phone connectivity. The APN is for cellular data. And a stock install of cm11 and pa-gapps gets it right.

Michael cannot fix something he does now know to be broken and I cannot for the life of me can see why you would want to change the APN, unless you are using an XT910 on foreign soil with a foreign carrier.

Would you folks with the APN issue mind making a post and putting at the top:
[MENTION=3457922]stargo[/MENTION] APN Issue

So that he can find your posts and read what the issue is. I think this is more of a misunderstanding or misconfiguration rather than a bug, but Michael would be in a better position to tell you. He DID ask so he can help you, let's make this easy on the guy, mark your posts on the issue so he can find them, and see what the issue is all about.

Thank you. I have tried to help with this myself but never had the issue and don't know why you are doing it. So this would make things a LOT easier on everybody. ;)
[Motorola Droid RAZR] chinkster:
i think Jakes APN fix really does work because I am at work right now and I haven't gotten the orange bars yet all day (knock on wood) after I did the fix. If I didn't do it, I would have been had to toggle airplane mode a couple of times just to get connected to the google servers
[Motorola Droid RAZR] vanwho:
[MENTION=3457922]stargo[/MENTION] I am testing out the Stock APN restore as well. I will report back with any details once I can run it with the stock APN's for a day or so to get some valid data. I don't want to say one way or another as far as results until I have it set up like this for a little more time.

I also have another question. It does not matter what KitKat ROM I try, none of them will wake the display on an incoming call until about the 3rd or 4th ring? I can't even answer the phone if I try, because the screen will not wake. I know some people have mentioned this issue in the past, just wondering if there is any hope of this being fixed? Thanks.
[Motorola Droid RAZR] stargo:
Ok, I can't see why it should work, but maybe Verizon's network is completely broken ;)

The phone actually enters deep sleep when you are making a call using handsfree-mode or using a bt-headset. This is all handled autonomously by the additional chips (modem, ti wpan(bt) and moto cpcap (everything and more)) while the main ARM is sleeping. You actually need to wake the phone up using the power-button while you are in a call.

After the other side has hung up, the modem wakes the main-processor up again and the display turns on.

Ok, please report back.

Hmm, in my test the phone starts to vibrate and then the display lights up after approx. 1s. It actually takes about 2.5s from the time the modem wakes up the ARM processor until the display is turned on (for me).

Regards,

Michael
[Motorola Droid RAZR] vanwho:
Hmm, in my test the phone starts to vibrate and then the display lights up after approx. 1s. It actually takes about 2.5s from the time the modem wakes up the ARM processor until the display is turned on (for me).

Regards,

Michael[/QUOTE]

Mine will start to vibrate for about that amount of time 1-2 seconds, then it will start to ring. It will ring 3-4 times before the screen will actually wake up.
[Motorola Droid RAZR] Ohmster:
Yeah, Vanwho is absolutely right about that. You get a call and don't even know who it is or can answer it, takes a few rings to get the screen lit. I did not know it was in all KK roms, though. Vanwho has been using other roms like Liquied so he would know. Man, Google made the Kit Kat very good, very tight, very good memory management. But some of it is just plain dumb like apps being able to write to Ext SDCard (Unless it was being abused.) and now cannot see phone screen for several rings or hang up when the call is over.
[Motorola Droid RAZR] Ohmster:
[MENTION=3457922]stargo[/MENTION] Alright, being a technician, I am good at testing and verification. I got a timer. Let my phone go black screen, and called myself from home phone. At first ring buttons lit immediately and screen lit within one second. I answered the call. Blah, blah, blah. It took 1 minute and 12 seconds for the screen to black out without speaker, Bluetooth, or next to my face (Laying on desk.). I picked up phone, tapped power, buttons lit immediately, screen lit within one second. Able to end call. Took a log, grepped word "call".

Repeating test with speaker as not to complicate with Bluetooth. Same Results!

Did not bother to collect a log as results were the same. Go figure. When I want this to happen, it doesn't. Everything you said happens with your phone, Happens with mine now, Michael. Except I do not use vibrate when ring. Might be a good idea in case phone in pocket in a loud place.

Current Build Date: 04/28

I don't know if this helps but I just did the test, upped the log, and it just proves what you said should happen. :confused:
[Motorola Droid RAZR] wernst:
You know, I hate to be the only voice saying this, but at the risk of being unpopular for a moment, this is not a universal truth.

I can reboot to Stock Rooted Jelly Bean and in Southern California, and literally NEVER get the JB equivalent of "Orange Bars." Then 5 minutes later I can reboot to a CM nightly, and even after the APN swap from JB, get Orange Bars. In the same house. In the same room. On the same couch. With 4 bars of LTE signal.

So please, let's not pretend the problem rests solely (or even mostly) with Google's servers or network congestion. The evidence is very strong that something is not right in CM11 in this regard.

Now then. I'm not saying I'm angry or irritated about the Orange Bar problem: this is the nature of a nightly or beta software. Also, I understand that I'm doing this by my own free will - I'm not being forced into this. Also, I know if there is a vital need for constant connectivity to Google's servers, I can reboot into JB and get it. And finally, I know this must be as frustrating as hell to the Devs, and I want them to know how grateful I am for the hard work they are performing - for free! - to make this happen on an old XT912. You have skills I don't have and time and conviction to burn, and you're my heroes.

I'm not taking issue about the Orange Bars here - I'm taking issue with thinking it isn't a problem that can be solved.

Ultimately, the first part of solving a problem is admitting that there is one. So let's do that. There is a problem with CM11 not keeping a sync with Google servers. The problem is not with network traffic or Google Services in general.

The problem won't get solved if we pretend that Orange Bars are normal and inevitable. They aren't. You need look no further than JB to see that Orange bars neither normal or inevitable with this hardware on this network.

So count me among the grateful users hoping for eventual improvement with the CM11 Orange Bar problem, and among the grateful forum members who is appreciative of the support and communication between users and users, and users and devs.

Thanks,

Warr
[Motorola Droid RAZR] drewski_1:
i thought it's been established that the Orange Bar problem is across devices / ROMs and is a Google KitKat codebase issue, that hopefully will be fixed / improved with 4.4.3?
[Motorola Droid RAZR] Noe!:
Yup, it even says it in the 4.4.3 change log, apparently.

The unofficial Android 4.4.3 changelog follows below:
[Motorola Droid RAZR] Ohmster:
I didn't mean to say "It's Google's Fault". I would expect to see orange bars "occasionally", fleetingly", but not constant or almost always.Yeah, there is something in cm11 that has not matured enough to maintain a strong Google server connection. Reminds me of that cracker commercial where the tech asks a wheel of cheddar a question and he gives a wisecrack answer. The tech puts a heavy check in the "Not Mature" box. It will probably be the same thing as they are building the Kit Kat rom from the ground up. It takes a long while. I get orange bars for extended periods too. But with so many serious issues to tackle, it may be a while for that to happen. There is "something wrong" in some way, with every part of this rom, and the pieces get fixed, one by one, as time goes by. Sometimes to fix something and get it right, it backtracks several other items that need to be modified to meet the new rom specs. I *hate* when that happens, but it does. The first couple of weeks in April were a fine example of it.

You are right Warr, the rom has issues. Funny because when my orange bars clear, suddenly I got 31 updates on the way. :p

---------- Post added at 07:29 PM ---------- Previous post was at 07:21 PM ----------

Gosh, Noe! I thought you were just a cute little kitty cat. :laugh:

As you can see, Sonia Kitty prefers her cupcakes "raw". :silly:

​

Changelog looks good. Thanks for the heads up!
[Motorola Droid RAZR] chinkster:
[MENTION=3457922]stargo[/MENTION] after a full day of testing, i only noticed the orange bars ONCE but that was probably because I went into a heavily cemented area at work. But it also automatically reconnected to the google servers and the bars turned white again whereas before the fix usually I would have to toggle airplane mode to get it back to white or else it would stay orange forever.
[Motorola Droid RAZR] jeff_roey:
Merging APNs and Battery Life Still Suckin'

I've just merged APNs using Jake's method and I'll watch it over the next day or two to see if there's any notable difference. I rely A LOT on Gmail and Maps, Drive, and SMS Backup Pro - all of which were made somewhat unbearable by the frequency of orangeouts so it shouldn't take me long to note an improvement.

I want to take the conversation back to battery drain for a moment. I'm currently running 04.27 with stock kernel on an XT912 Maxx and since coming over to this ROM at the beginning of March battery life's been in the crapper like most others are reporting. I noticed today that while on the stock ROM, fully charged and plugged in, I switch over to the 04.27 ROM and once booted - still fully charged and plugged in - my battery meter reported on 75 percent charged. Got me thinking that perhaps some of the drain isn't just wakelocks - which according to WLD there sure is a lot more - but also how the ROM is seeing or calibrating the battery.

According to WLD, my big wakelock offenders were Hangouts, Google Now, Google+, and cLock, but even after freezing them, battery life is still in the dump.

If orangeouts subside thanks to Jake and others, then battery life is the only remaining characteristic that's keeping me from making this my daily ROM. Is anyone having any better luck getting to the bottom of the battery drain?
[Motorola Droid RAZR] chinkster:
Does anyone know if I flash another nightly, would I have to do Jakes APN fix again?
[Motorola Droid RAZR] Ohmster:
By reading Jake's post, I think you would as he seems to be merging it into the rom itself as a system app. What troubles stargo and myself is why you would have to do this. The APN should be already worked into the cm11 rom and mine always get it right.

Before you go doing all that stuff, would you mind just looking at your APN in Settings and see if it is set correctly, if not, change it and see if it improves? Screenshot of my APN is attached, cm11 got it right, and I never had a problem with it. That is, if you do not mind, of course. Thanks,
[Motorola Droid RAZR] chinkster:
i checked the APN settings and it is bubbled in on the same one as you have pictured. But I already did Jakes APN fix so that could be why.
[Motorola Droid RAZR] sonomazr2:
Did anybody check if the settings in VZWINTERNET are the same. If you tap it you can look at the setting for each one.
[Motorola Droid RAZR] CoreyWillWhat:
I've been gone a couple of days, but I'll chime in with this APN thing everyone is talking about. I was doing the testing for [MENTION=3457922]stargo[/MENTION] with our phones and the new APN's he implemented back with the 4/22 Nightly. Prior to his updated APN, the issue was connecting to LTE. His updated APN fixed that issue. Around the same time, the Google server (Orange Bars) issue was drastically reduced. I don't believe this had to do with his change in APN's but a mere coincidence that the Google Server issues are being worked on at the same time.

Jake's APN's: I tried Jake's stock APN's, which are in fact a combination of stock APN's AND cm11 APN's, says it right in his post. I saw no benefit to adding the stock APN's after a day or two and so reverted back to only the updated CM11 APN's which I am running now.

Orange Bars and my observations: I'm running the CM11 APN's that come prepackaged in the nightlies. I live in Philadelphia but travel all over Pennsylvania, New Jersey, and Delaware for work, every day I'm in a new place. I have not seen the Orange Bars in quite some time, except one day when I was in the middle of nowhere PA, although still with full LTE coverage. What it seems to me is that Google is making some changes on the server side of things at the same time they are working to release 4.4.3.

Thoughts: The issue may be locality. Larger cities like Philadelphia may have had changes made to fix the issue from Google's side of things. Google likes to roll things out rather than do everything at once, so this approach would make sense to me, although it is just my opinion and may not be how it works at all.

What I know: I'm running cm11 APN's included in the nightlies, have the best service I've had with the phone since KitKat was given to us by the cyanogenmod team, and never see the orange bars while in Philadelphia or the greater Philadelphia area.
[Motorola Droid RAZR] KurtSagar:
Gummy ?

Hello,

What is this Gummy Edition ?

Never heard of it.
[Motorola Droid RAZR] tydiamond11:
Yeah?
[Motorola Droid RAZR] Mr-Glass:
It is another Rom project that Dhacker is a Dev for... running great btw on my XT912
[Motorola Droid RAZR] vazersecurity:
Is "Gummy" KitKat or JellyBean? Would you recommend "Gummy"?
[Motorola Droid RAZR] Eighthourblink:
Is there a link for the Gummy Custom Rom? Tired the quick search with no luck
[Motorola Droid RAZR] Mr-Glass:
Gummy is KitKat.. I recommend it - everything seems to work fine (I havent tested everything).. The gummy Rom I installed was in Dhackers omap4 folder.. http://androidhosting.org/Devs/Dhacker29/omap4/
[Motorola Droid RAZR] vazersecurity:
Okay, thanks for the info. Yeah, I saw it. I got curious haha and I'm gonna try it. :)
[Motorola Droid RAZR] kenosis:
Always failed to download Gummy UMTS. Is the link broken?
[Motorola Droid RAZR] Mr-Glass:
umts version seems fine from here..
[Motorola Droid RAZR] 1droidmod:
http://androidhosting.org/Devs/Dhacker29/omap4/

Gummy!! It is up top on list..

XT912 RaZR SpYdEr CDMA

hit ThAnKs if I was helpful!!!
[Motorola Droid RAZR] Bashok:
I honestly hate the Gummy boot animation...wished it was the CM one or something different but hey, its his work, his effort, his time, I have no right to complain. I an edit the boot animation myself anyway if I really wanted to.
[Motorola Droid RAZR] Gus194:
Has anyone installed Gummy on their Stock Slot on Safestrap?
[Motorola Droid RAZR] iZak17:
Hi, have you found any solution to the signal problem?

I know you are on a XT912, I'm on a XT910, but maybe there is a common solution for this issue.
[Motorola Droid RAZR] ivan11235:
What rom verion?

There were many solutions how to fix it in CM11 at this thread.
[Motorola Droid RAZR] kenosis:
Gummy stucks at boot animation. :(

I installed on system 2 by using BMM
[Motorola Droid RAZR] ivan11235:
I am OK on XT910. I used System #3 with SlimGapps.

Did you use System#2 previously? custom roms loaded normally?
[Motorola Droid RAZR] vazersecurity:
Pros/Cons: GUMMY

Gummy has some pros and cons in my prospective. It is mostly based on preference, though.

==

PROS:

More Customization (compared to CM11 Alpha 20131126)

Laucher feels more stock-ish (compared to CM11 Alpha 20131126)

Different feel (I understand that this can be a pro or a con to some people)

Boot animation (user opinion)

Searching for some more...

====

CONS:

DSP Manager is not present on this ROM, can get from Play Store via CyanogenMod App Installer (CM App Installer), but doesn't switch properly in settings.

Lags a lot. (on my device anyway, yours could be different)

Lacks some CM features I wish this ROM had.

Feels different. (Could be a pro to others, to me it is a bad thing even though it is in the pros list as well.)

Contradicting settings. (Same setting is in multiple (or just two) places and not changing together.) (ex. Lockscreen widgets)

Boot Animation (user opinion) (my opinion)

Confusing QuickSettings customization.

Apollo FC everytime I select a song. Is it working for anyone else?

Searching for more... (if any)
[Motorola Droid RAZR] dtrail1:
SELinux state is not available? Well, this isn't a pro except if it was completely removed. The code itself doesn't look dangerous, but maybe the compiled program could cause a buffer overflow or something which helps to open a backdoor to our devices.. I don't trust someone like the NSA when they start to contribute into Linux code...

Gesendet von meinem XT910 mit Tapatalk 4
[Motorola Droid RAZR] ivan11235:
Available. I can see "Only warning".
[Motorola Droid RAZR] meilbox:
also new gummy for UMTS by dhacker

http://androidhosting.org/Devs/Dhacker29/omap4/Gummy-2.0-12-01-13-UNOFFICIAL-umts.zip
[Motorola Droid RAZR] vanwho:
[MENTION=3457922]stargo[/MENTION]. I have been running Stock APNs for a little over a day now. I believe what coreywallen is talking about may be true in regards to the APNs and Orange Bars. I am in a rural area that I usually have orange bars most of the time. Restoring the stock APNs has helped me with the connection. I have not had a single orange bar in a day and a half now. This is at my house where I consistently had the orange bars before. I also believe that once you get away from the metro areas, these issues get worse, and the stock APNs must have more options to get a better signal in the rural areas. I am not sure how many APNs for Verizon are on CM11, but stock restored 142. That is a lot in my mind. I agree that maybe Google is working on things as well, but the APN restore definitely helped my service issues right now. Of course, only more time will tell if it is truly fixed though.