yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] KlugN:
This thread is quiet...

After reading through carbon on XDA and a few other forums I decided to go with the 5/4 nightly over the 5/7 stable. No issues at all so far apart from 1 random reboot. I was updating an app in the market and the phone rebooted so I'm assuming it must have been a running app at the time...
[Samsung Galaxy Nexus] thefatalepic:
I have a lot of apps (217) so maybe this is why I get so many memory issues with Carbon. I have a decent amount (7GB) of free space, so I didn't think it would be an issue.

It seems that at least once every couple days I have the phone slow down so much it's unbearable. And at these times reboots or clearing cache do not help. Apps kill themselves in the background, audio skips horribly, apps lag or become unresponsive - it's a nightmare.
[Samsung Galaxy Nexus] jsgraphicart:
They HAVE been working on a lot of memory leak issues according to the changelog. But I havent experienced anything close to what you have though. Are you using the kernel that comes with it or another one?
[Samsung Galaxy Nexus] thefatalepic:
Every now and then I leave the stock kernel to see if that is my issue, but all the problems still arise. I normally flash AK kernel over stock, and when the phone is running fine I do feel the improvements. I uninstalled about 20 apps so hopefully that'll help some. I noticed my phone rebooted on its own once yesterday and again this morning. I'm not sure if it's related but I'm going to disable Smart Reflex for MPU voltages, this was the cause of my reboots on other ROMs.
[Samsung Galaxy Nexus] SomeGuyDude:
I'm not up to 217 but I do have a lot, and this has been the case on every ROM lately. I run IMO.im and it'll kill itself randomly and restart, Swype will take a genuine five seconds between when I hit a text box and when it actually appears (as in a real five-count), all sorts of horrific lag and stutter. It's becoming absurd and I literally cannot find a ROM/kernel combo to fix it.
[Samsung Galaxy Nexus] thefatalepic:
My stock keyboard does that. It really depends on where I'm trying to bring it up, stock browser takes about 2 seconds, Chrome takes about 5 seconds (if at all).

I was happy on PA until I started having random reboots and freezes. I found Liquid Smooth and it was a dream come true, until the team split up. I followed most of the team onto Carbon, and the first build was pretty solid. Now I've been getting this lag on any ROM I try. It's hard to spot because any new ROM I flash runs great for at least a week, then the memory problems kick in. I usually stay with AK kernel but I tried switching back to Lean Kernel since I've been having issues. The lag was considerably worse so I'm back on AK kernel.

I miss having a stable combo, I normally do a nandroid when I have a stable ROM/kernel combo before I continue with my crack flashing... I think it's been at least 3 months since my last nandroid. :(
[Samsung Galaxy Nexus] KlugN:
I am almost positive that your issue is a Swype dependant issue. I've dealt with that on EVERY ROM I've tried but apps like swift key, slide it, etc all run just fine.
[Samsung Galaxy Nexus] SomeGuyDude:
It's not just Swype though. It's everything. I'll hit the recents button and it'll take forever to show them. It takes five or six tries for Nova to recognize my swipe gestures. The list goes on and on.

I'm starting to think it's an issue with the most recent iteration of Jellybean.
[Samsung Galaxy Nexus] KlugN:
It could very well be. The updated Swype seems to load faster but definitely still takes more time than other keyboards. I have about 160 apps and everything has been running well for me. I use Nova as well. I have used lean kernel on my gnex for a while now and haven't had a single issue with it. Maybe give it a go and see if that fixes your issue?
[Samsung Galaxy Nexus] SomeGuyDude:
Giving LK a shot, reinstalling Carbon just to clear out the RAMdisk. We'll see how she flies.
[Samsung Galaxy Nexus] KlugN:
Let me know. I tried AK because everyone was so high on it but my phone hated it no matter what version I ran. I'm running version 6.5 of LK now and loving it. I even undervolted it for battery life and it's still the smoothest kernel I've used. Not to mention that I get 20 hours plus battery life with 4-5 hours of screen on time and data and Wi-Fi always connected. I also use interactivex governor.

Edit: If LK doesn't work for you for any reason try Tiny. I've used his with good results in the past as well.
[Samsung Galaxy Nexus] Txwolf1980:
Tiny is my go to kernel. I was actually going to suggest it, myself

As for the keyboard issues, occasionally SwiftKey will either refuse to load, or load, then immediately be kicked out of memory. So far, that is the only issue is had with the low ram.
[Samsung Galaxy Nexus] KlugN:
Interesting. When I get pissed off at Swype for taking too long I switch over to swiftkey because it hasn't given me any issues.

And yeah, Tiny's kernels are a great option!
[Samsung Galaxy Nexus] SomeGuyDude:
Back to Rubik. And now for some reason Mightytext stopped working. I swear this phone has turned into more trouble than it's worth.
[Samsung Galaxy Nexus] Txwolf1980:
Something I just noticed.

I've looking at the recents ram bar, and seeing the 22mb.

I decided to go ahead and run Tasker again, and noticed that the amount of free memory never dropped. So I went to the actual running apps section in settings. 215-212 free. I'm almost wondering if the recents ram bar is simply inaccurate. According to my bar, I've got twice as much ram being used for 'other' s's I do for cached processes.

I'm not negating the issues others are having. But, I'm beginning to think that it isn't necessarily related to the low ram issue.

Thoughts?
[Samsung Galaxy Nexus] thefatalepic:
I also notice about 7mb free in recents, then go into the running services to see 279mb free. I don't know if they are just reporting differently, because when I have about 7mb in recents is when I start having issues.

I have no idea.
[Samsung Galaxy Nexus] KlugN:
This has been widely discussed in many threads. For some reason, the ram bar in recents is not accurate. Most devs have recommended turning it off completely because it will just make you paranoid.
[Samsung Galaxy Nexus] thefatalepic:
You know, that's actually a good suggestion. Whatever it is, it sure doesn't help when my phone is misbehaving, all I do is look at the low memory and blame it. I'm better off flashing different kernels or adjusting settings than staring angrily at the low amount of memory.

EDIT: I wonder if this is also the cause of my Recents page lagging every now and then...
[Samsung Galaxy Nexus] KlugN:
Could be. Certainly wouldn't hurt to turn it off and test it to see what happens! I don't have any lag in my recents.

On another note, my play store just stopped working completely...anyone else's?
[Samsung Galaxy Nexus] Txwolf1980:
Stopped working as in won't load, shows no connection, shows file packages as invalid, what?

Occasionally I'll get an invalid file package error. But redownloading the affected apps update goes through fine
[Samsung Galaxy Nexus] KlugN:
Showed no connection after changing LCD density. Tried to switch it back to stock and still no luck. Facebook, Twitter, etc all worked fine.

I reflashed ROM and gapps and now everything is working as it should.
[Samsung Galaxy Nexus] thefatalepic:
I think my latest slowdowns have been due to overheating. My phone usually starts stuttering halfway into my drive home, and I never thought to check the temp. I don't know how the temp limit works but I have it set to 70 and CPU was jumping between 68 and 74 or so.

//XDAAPP//
[Samsung Galaxy Nexus] grandzu:
It used to be mine also but Tiny gets stuck in a reboot cycle at the Google screen and its been like that for a few months now.
[Samsung Galaxy Nexus] NeverSeparate:
Are you sure you don't have a bad download? I'm using tiny now with no issues like that.
[Samsung Galaxy Nexus] SomeGuyDude:
Slow as all hell after a few days AGAIN. Disabled Swype, but Google's stock keyboard for some effing reason doesn't trust me enough to let me trace swear words which gets aggravating as all hell. That's honestly a dealbreaker for me. :P
[Samsung Galaxy Nexus] Txwolf1980:
I've noticed the same thing. SwiftKey seems to have some moral filter, too.I think Swype is probably the only keyboard that doesn't differentiate.

Are you using beta, or the play store version?
[Samsung Galaxy Nexus] SomeGuyDude:
Play Store. Beta wasn't any different. SwiftKey will do it, you just might have to teach it the words first.

Sigh, still on a hunt for a ROM with at least some customizing that doesn't drag-ass hard after a day.
[Samsung Galaxy Nexus] zandroid:
If you are coming from AK Kernel you will need to dirty flash the ROM then flash Tiny. For example, if you are running 1.7 with AK, boot into recovery, do a backup, dirty flash 1.7 to get to the stock kernel, and finally flash Tiny. Has to do with the way AK handles ramdisk.
[Samsung Galaxy Nexus] grandzu:
Yeah, I saw in Tiny's thread he recommended the same. I just got the latest nightly so I'll see if that works.
[Samsung Galaxy Nexus] jcmm11:
Just add the words to the dictionary.
[Samsung Galaxy Nexus] SomeGuyDude:
That just prevents it from auto-correcting. It won't let you actually "swipe" those words.
[Samsung Galaxy Nexus] KlugN:
Give slim ROM a shot. I have been back and forth between the 2. I always end up back on Carbon though.
[Samsung Galaxy Nexus] Az Biker:
I'm surprised you've had a slowdown issue with carbon... If you haven't already, try Atom, Slim, and, Axiom. I've had nearly flawless results with all (including carbon)... If you still experience a slowdown with any of these, I'd say you need to look at your settings, flashing practices, or a rogue app that could be the cause... Just one guy's opinion :D Good luck hunting it down!

Axiom + AK SKL Series = Bacon, Skittles & Skulls!
[Samsung Galaxy Nexus] jsgraphicart:
Something weird happened yesterday. Out of nowhere, my phone rebooted and when it turned back on, I was greeted with the setup wizard. But not the full thing. It mainly just asked me to put in the owner name and click next through a few screens. It also seemed to remove my defaults I had such as launcher and gallery apps. Meaning I had to select them as my default again. I didnt lose anything. I'm guessing its just a memory thing.
[Samsung Galaxy Nexus] infectedorganism:
I've experienced the same. I can't say which nightlies it was on, but it has happened a few times.
[Samsung Galaxy Nexus] jsgraphicart:
Anyone else use Google Voice for Visual Voicemail? It worked at one point in time but recently, when trying to listen to a voicemail on the default phone app, it just closes the app and doesnt play the message. It doesnt force close with a dialog box or anything. Just closes. Anyone else have this issue. Its not a huge deal since I can still go into the Google Voice app to listen to my messages. But I thought I'd bring it up.
[Samsung Galaxy Nexus] thefatalepic:
This is interesting.. I always use the app to check my voicemail, or when I have a notification it takes me directly to the Google Voice app to check. I'm not sure what your saying :(

I have slow downs with most ROMs I've tried since 4.2.2 came out. I'm going to bite the bullet and do a clean flash for the latest nightly. I noticed I'm not the only one with these issues, but I also notice there are some with the same device that don't have any problems.
[Samsung Galaxy Nexus] christianpeso:
Been having this issues for a couple months on multiple ROMS. Trying to play the VM from within the phone app will just close.

In Voice settings, check the option to listen to VMs in the phone app and it should happen to everyone.
[Samsung Galaxy Nexus] roboots21:
Happens to me as well.
[Samsung Galaxy Nexus] jsgraphicart:
Like christianpeso said above me, in the Google Voice settings, there is an option that says Voicemail Display. Check that and you will see your visual voicemails in your phone app in the call log.
[Samsung Galaxy Nexus] thefatalepic:
Thank you, I did not know this existed. Now I'm just as frustrated because I've been wanting to see voicemail in the phone app for quite some time, I now learn it's possible, and it's broken. I can confirm the force close (without FC message) :(

EDIT: also the clean flash did help many of my problems. the phone doesn't seem to overheat as quickly and the audio from Power Amp has stuttered again, but this time I was able to see that the phone was desperately seeking a signal (still shouldn't have happened but it's a bit more understandable this time).
[Samsung Galaxy Nexus] jsgraphicart:
That was the main reason I got Google Voice was for the Visual Voicemail integration. It worked for a little while but eventually started doing that. I dont know if its ROM related or not.
[Samsung Galaxy Nexus] baggar11:
No issues here. Running Carbon 1.7 and lean kernel 6.5.
[Samsung Galaxy Nexus] infectedorganism:
Anyone else unable to connect when using the new adb toggle?
[Samsung Galaxy Nexus] christianpeso:
No issues as in your Google Voice VMs show up in your call log???
[Samsung Galaxy Nexus] baggar11:
Yeah. No FC's. Google voice is working fine for me. I can play vm's, etc.
[Samsung Galaxy Nexus] Txwolf1980:
Anyone know which base 'ribbons' was pulled from? Or is that a carbon original? Just curious, because I've been rom shopping, and don't see anything else with it
[Samsung Galaxy Nexus] Sailrace:
I have switched to Carbon from PA mainly because i was seeing some atrocious battery life. I'm hoping that Carbon is able to keep up a little better. But i am also having the Google Voice VM issue from the call log. I can play voicemail just fine from within GVoice, but trying to play from the call log causes an immediate close.

This is one thing that needs to get ironed out. I've also noticed that at most pixel densities other than stock and 241, the messaging app behaves badly with its header bar. Just something i noticed in playing around last night.
[Samsung Galaxy Nexus] jsgraphicart:
Not the Google Voice app itself. That works fine for me too. We are talking about the voicemails that show up in your phone app in your call log. Is that what you are talking about?

Also, apparently, I'm not the only one with the voicemail issues. So what is the best way to report the issue to the carbon team and see if this is a ROM issue? Maybe someone on Google+ can make a comment?
[Samsung Galaxy Nexus] baggar11:
Hmm, I guess I have never dialed GV to check voicemails. I usually keep my data off and have GV text me when there is a new voicemail. Then I just open the app and listen...
[Samsung Galaxy Nexus] jsgraphicart:
It doesnt seem everyone knows about this feature Google Voice has. lol. You dont dial GV. The Voicemail just shows up in your call log and you play it right from there. Its really perfectly integrated into the phone app and feels like it was meant to be there.
[Samsung Galaxy Nexus] jreyno10:
AOKP.
[Samsung Galaxy Nexus] slick_rick:
Yup, ribbons are the work of Steve Spear and AOKP.
[Samsung Galaxy Nexus] jsgraphicart:
So whats going on with the changelog? Its not really getting updated like it was before. Do we just look at the gerrit they have now? And if thats the case, are all the changes that have the date of may 16 on it included in the 5-16 nightly or are those in the process of getting added. I dont know how this stuff works really.
[Samsung Galaxy Nexus] thefatalepic:
Finally found a sweetspot, clean flash of 5-13 nightly paired with leankernel 6.5. No major issues or bugs I can see and have ran this combo for 3 days. Made a nandroid and now I feel safe crack flashing again.

EDIT: The Google Voice issue has been reported for Carbon ROM, go here and star it to show them it's a common issue:

https://code.google.com/p/carbon-rom/issues/detail?id=121&q=voice
[Samsung Galaxy Nexus] jcmm11:
Look at the merged tab. Not the open tab. You can assume that any merge date will show up in the nightly with merge date+1

So the 5/16 nightly includes all merges through 5/15

It's possible that some 5/16 merges would also make it in but that depends on exactly what time they were merged and what time the nightly was created.
[Samsung Galaxy Nexus] Wolfkmann:
Sorry, merged tab? I must be missing this. Where do you see this?

Thanks
[Samsung Galaxy Nexus] Skoogusmaximus:
I continue to have bluetooth issues with this rom, both nightlies and stable. I have to flash the btfixtest.zip every time. Is there a better solution for this?
[Samsung Galaxy Nexus] fcisco13:
Only problem i get is when i first connect then turn screen off it disconnects but after i connect again all is well, no breaking, no issues.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] grandzu:
Just noticed the bedtime calculator built into the nightlies alarm, telling you the optimal time to go go to bed. Kinda cool, gotta see how accurate it is.

---------- Post added at 12:17 AM ---------- Previous post was at 12:15 AM ----------

It's up for the 20th.
[Samsung Galaxy Nexus] jcmm11:
Gerrit is down so hopefully they'll be on top of the change log. We'll see.
[Samsung Galaxy Nexus] infectedorganism:
5/20 nightly: The reboot menu fix they merged seemed to have broken my reboot menu. Same experience for anyone else?
[Samsung Galaxy Nexus] slick_rick:
Tomorrows build will have it then. Its been fixed or you have your builds mixed up, either way.
[Samsung Galaxy Nexus] kmcrane:
I can't reboot. My first time using carbon, so I didn't say anything. I have been looking for an answer, I'll wait, and dirty flash the next build.
[Samsung Galaxy Nexus] vinal:
5/21 did fix reboot menu.
[Samsung Galaxy Nexus] thefatalepic:
Where'd you find this? I have 4 alarms for the morning (in 15 min increments) because it's that hard for me to get up, just curious as to what time it thinks I should go to sleep Lol..
[Samsung Galaxy Nexus] baggar11:
Looks to be a check box option under the alarm pull down.
[Samsung Galaxy Nexus] fcisco13:
Right n left ribbons not working on nightly 5/24 anyone else?? After setting up and saving after u click on app nothing happens.

WHATCHOO TALKING BOUT WILLIS?
[Samsung Galaxy Nexus] jcmm11:
Supposed to be fixed with 5/25 nightly
[Samsung Galaxy Nexus] NeverSeparate:
I am on the 522 nightly, the first with contact notification settings, and after setting several contacts, they don't appear to work. Ring tones work as normal. Just not notifications. Am I missing an option to enable this somewhere?

---------- Post added at 11:33 AM ---------- Previous post was at 11:21 AM ----------

Also just remembered, I did flash a different sms app, the sorcery apk from justen's thread. I wouldn't think that would matter since the settings for notifications are in the contacts app but I suppose there may be other factors.
[Samsung Galaxy Nexus] NeverSeparate:
Dirty flashed rom again to restore original sms app and it works. I like this feature being built in but I also like to be able to theme my messaging app? Has anyone tried other messaging apps that worked with this feature?
[Samsung Galaxy Nexus] cuzzinz:
Flashing nightly 0525 didn't work out so well. Acore and contacts stopped responding and were cashing. I had to clear data for contacts app and contacts storage. Dirty flashing from nightly 0518 to 0525. Anyone else have this issue?

Seems to be fine now but I'm concerned it will happen again after the next flash...or was I not suppose to jump from 18-25? Lol

Sent by click....click....click....click.....click.......telekinesis
[Samsung Galaxy Nexus] kmcrane:
Anyone ever had issues with play store? It has used 11gbs of data in 3 days! I cleared data and cache yesterday, but it started it's crazy data usage again.
[Samsung Galaxy Nexus] NeverSeparate:
The Changelog for the 5-22 said it may require a wipe. They added the contact specific notification tones to contacts. I'm sure any of them after would be the same. So if you dirty flash from then or later over anything older than that it may cause issues. I tried a dirty flash of the 22 over 1.7 but had issues, clean flash fixed it.
[Samsung Galaxy Nexus] enkrypt3d:
any time I Try to download from goo.im, I only get 10KB/s.... Just ran a speedtest on speedtest.net and I'm on a 50Mbps connection...... are there any other mirrors for these files??

http://rootzwiki.com/topic/40455-very-slow-downloading/

This might explain it........ any mirrors? Thx!

FYI I can mirror some of these files in the mean time as I have my own hosted server (not from my home connection) with a 100Mpbs uplink...... PM me)
[Samsung Galaxy Nexus] mfdemicco:
I tried dirty flashing two of the latest night lies, and had system crashes. MD5s checked out. I don't see anyone else complaining about this problem. Good thing I made a Nandroid.
[Samsung Galaxy Nexus] NeverSeparate:
See my post about 2 posts back.
[Samsung Galaxy Nexus] mfdemicco:
OK, yes, probably the same problem but I couldn't even get that far. But I'm not doing a full wipe to flash a nightly, so I'll wait for the next stable version and full wipe then, and just stay on the stable builds.
[Samsung Galaxy Nexus] jcmm11:
If you don't want to do a full wipe just set airplane mode and delete contacts and contacts storage data before flashing.
[Samsung Galaxy Nexus] cuzzinz:
Thanks!

Hopefully clearing the contact storage and resyncing contacts will solve this one for me.

Sent by click....click....click....click.....click.......telekinesis
[Samsung Galaxy Nexus] NeverSeparate:
Since flashing the Nightly my dialer doesn't seem to be remembering contacts I normally dial on first key press. For example, 5 should pull up Lee first after I dial lee a few times, but it doesn't appear to be saving that properly? I have had that issue with other roms but never on Carbon. It worked on 1.7. I clean flashed the 5-22 Nightly and it isn't now.
[Samsung Galaxy Nexus] kmcrane:
+1
[Samsung Galaxy Nexus] dj-bilbo:
i've had some random reboots on 1.7 stable, stock kernel lately after working fine for a while... sometimes while on chrome or gmaps... seems like i may have to try a nightly based on previous posts... Any rec's on stable nightly with stock kernel?

still luv this rom!

Sent from my tf201
[Samsung Galaxy Nexus] jsgraphicart:
I noticed the Carbon Team is working on the Halo feature for this ROM. I saw this in the changelog for the 29th:

"Nothing though there may be a Halo build for you device somewhere. Check G+ or forums. HALO NOT INCLUDED IN THE 5/29 NIGHTLY, but the links for the halo builds were released on 5/29. They are two separate things."

I think we would have heard if there was a Verizon version. I cant find any list of what devices got it or not. But I'm sure its safe to say that its coming.

EDIT: Found the links on their Facebook page. Toro is not one of them.
[Samsung Galaxy Nexus] cuzzinz:
i am on nightly 0525 and i am using AK kernel SKL256.

I have a wireless n (b/g compatible at home) with WPA2 auth enabled and I can connect fine at home.

At work I have 802.1x authentication (b/g/n corporate WiFi) and I am unable to connect to my wifi anymore. (I checked out radius server and it shows my authenticating but the phone just never connects to the wifi)

I have tried flashing the old wifi package that anakaria has and flashing a kernel from the last time my wifi worked and it is a NO GO.

I haven't done a clean flash yet but it just seem odd that it works at home and not at work.

Any thoughts or suggestions from anyone?
[Samsung Galaxy Nexus] cuzzinz:
NVM figured it out...lol.

Damn MAC ID changed on the phone for some reason. :-\

We use a MAC ID filter for all our devices at work...
[Samsung Galaxy Nexus] justen7723:
Carbon -Toro - halo build, from carbon Google+ page

https://docs.google.com/file/d/0B8Gx9o0pg-BcbTRnWEw1MWpFYm8/preview

http://xdaforums.com/showthread.php?t=2131538

[74 lock mods/18 glowdots/Nav keys/searchlights 5/25/13][25 sound mods 5/6/13]
[Samsung Galaxy Nexus] jsgraphicart:
Awesome. Going to try it out now.
[Samsung Galaxy Nexus] jsgraphicart:
Halo seems to be working good so far. :)