yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] lucky13:
Under WiFi and network settings-more > mobile networks > check that CDMA subscription is ruim/sim. Mine, for some reason, will change to NV for some reason and knock out my data. Also check the other two in there, and mobile data, make sure its enabled.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] fcardona86:
Anyone have any issues with text messages being wiped? I've been noticing that all of my text messages are randomly being deleted.
[Verizon Samsung Galaxy S III] lucky13:
Check under MMS settings>delete old messages, that's unchecked?

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] fcardona86:
Ah the notorious user error. Thanks, that was probably it.
[Verizon Samsung Galaxy S III] lucky13:
No problem. I only know half of what I do because at some point in time I did the exact same thing.
[Verizon Samsung Galaxy S III] Kipland007:
Flashed this yesterday and am very impressed with how smooth and functional the stable release is. Really awesome work. Probably the most stable ROM I've used on my s3 thus far.
[Verizon Samsung Galaxy S III] madjokeer:
What else have u used?
[Verizon Samsung Galaxy S III] ckelly33:
I've been on carbon for a while and currently on 4/8 with lean kernel (I was having tons of video artifact on kt).

When I go to settings> about phone> status, at the very bottom is "up time" and it is at almost 6 hours. What is that referring to? I've had my phone off the charger for 8.

The only reason I looked was because my phone is getting pretty hot lately.

Thanks
[Verizon Samsung Galaxy S III] david_hume:
The up time is when the ROM was completely activated and on in general. Sounds like you barely flashed the ROM. Just wait for the ROM to settle and the hot feeling will go away. Mine's been up for almost 200 hours.

It'll reset if you reboot the phone (or if the phone decides to reboot).

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] PeakyBoo:
That's how long its been since you rebooted the phone. Go ahead and reboot and see it go back too 0 ..or close to it.Lol its 0+the time it took to reboot:good

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] ckelly33:
Thanks for the explanation...I knew that at one time. In my agitation over the warmth of my phone I....don't know what I was thinking:o

Now, I do have one real issue. Running 4/8 and having large amounts of video glitching from time to time that affects the entire screen - unless the keyboard is opened. When the keyboard is opened, it only affects the area of the screen not using the keyboard. I've tried LK (current) and KT kernel.

From my recollection, it seems to happen primarily on the lockscreen and when using the stock texting app.

Any one know of a fix?
[Verizon Samsung Galaxy S III] draexo:
Disable hardware overlays. It's an option in the developer section. That will fix it. Have to re-apply at boot.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] ckelly33:
Thanks I will try that next. I just fixed permissions and have had some temporary relief of the issue I'm gonna see how long it lasts
[Verizon Samsung Galaxy S III] slick_rick:
Added a feature u guys might like :) pull down Statusbar even when its hidden (credit to CodefireX)
[Verizon Samsung Galaxy S III] mapatton82:
Just a heads up, the latest nightly (4/19) will not boot with the latest Lean Kernel. Boots fine with the stock kernel. I haven't tried any other kernels.
[Verizon Samsung Galaxy S III] buggerritt:
What is the stock kernel version?

Hopping from ROM to ROM in my Verizon Galaxy S3
[Verizon Samsung Galaxy S III] sgs22012:
Also if its not kt747, its it compatible with kt747, took a brief break to try out synergy and I'm back but was turned on to KT 747 hoping it plays well like the stock kernel on carbon
[Verizon Samsung Galaxy S III] Ronde90:
Doesn't boot with BMS kernel either
[Verizon Samsung Galaxy S III] squito:
I tried KT 4/11 3.4 and it will not boot :(
[Verizon Samsung Galaxy S III] mapatton82:
Here is the screenshot, its still 3.4

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] biyobe:
how does the backup tool work?? is there an setting/function to use it or when dirty flashing it just doesn't overwrite the areas that we'd normally have to reflash gapps?
[Verizon Samsung Galaxy S III] system6:
Any way to disable this? The Bar keeps showing up in full screen games and apps and cutting them off.
[Verizon Samsung Galaxy S III] slick_rick:
Not at the moment. Maybe we can add something to configure it eventually.
[Verizon Samsung Galaxy S III] khaoskosmos:
It would be nice to adjust the timeout also.

---------- Post added at 03:11 PM ---------- Previous post was at 03:07 PM ----------

Horrible screen flicker when SwiftKey pops up on 4/20. Unbearable. Disabling HW overlays fixes it but that's not a solution.

4/19 rebooted my phone twice during a call. Haven't had any calls on 4/20 yet.

---------- Post added at 03:22 PM ---------- Previous post was at 03:11 PM ----------

Just got a random reboot on 4/20 while using GooManager to download updated TWRP. The countdown only got to 9 seconds lol.

Also the screen flicker stops in SwiftKey while I am swiping to input text. Disabling HW overlays didn't stick after the reboot either.
[Verizon Samsung Galaxy S III] ckelly33:
I may be speaking too soon but I didn't disable hw overlays to fix the flicker, I fixed permissions and it hasn't been back in a while.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Can anyone confirm if these functions work on Nightlies? They were show stoppers for me in 1.5 and 1.6

-Open Google voice mail direct from dialer's call history tab (caused dialer to close in 1.6 and 1.6.1)

-fitness apps like Garmin Connect or Strava (frequent gps signal drops and grossly over calculated distances in 1.0 thru 1.5)

Thanks
[Verizon Samsung Galaxy S III] david_hume:
Reason why the other kernels don't boot with the latest nightly is because CM blocked all kernels with their latest nightly. Since Carbon's nightlies is based off the latest CM nightlies (which blocked all kernel support that isn't using CM's proprietary code), no kernels will work until the devs use CM's coding.

sent from my Hard Carbon S3
[Verizon Samsung Galaxy S III] khaoskosmos:
The voice mail from dialer crashes as soon as it tries to play. We do have an ascii carbon logo in the install script now though lol.

---------- Post added at 04:55 PM ---------- Previous post was at 04:50 PM ----------

I always fix permissions after flashing, but did it again after installing the latest TWRP. Flicker is still there.
[Verizon Samsung Galaxy S III] draexo:
I fix permissions as well. It didn't make a difference for me. Some days the flicker is worse than others, but it always goes away when I disable HW overlays.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] tprophit:
Is it confirmed that all nightlys after 4/19 require the updated CM coded kernel? I think KT a an updated one in the verizon kernel thread...

Thanks.

Sent from my Carbonized S3 via Taptalk[/QUOTE]
[Verizon Samsung Galaxy S III] khaoskosmos:
All the nightlies using the 3.4 kernel make my phone a worthless piece of ****.

From flickering, screen glitches to random reboots... It has become pointless to flash nightlies unless you wish to see what new issues have been introduced. (or want a pocket warmer as my phone will also randomly get hot)

I definitely advise against crack flashing unless you are a glutton for punishment. :) Also, it seems to not make any difference which kernel I use, from stock to any of the custom ones.
[Verizon Samsung Galaxy S III] tpayne2345:
posts like this don't help anyone until you at least share specifics like what nightlies+kernel you're flashing

only advice I have for you right now is get a new phone
[Verizon Samsung Galaxy S III] khaoskosmos:
I stated 4/19 and 4/20 with stock and custom kernels already. I understand that nightlies are experimental and if course will have issues. I was just letting others know that this rom isn't one to flash each nightly unless you like working through issues. It's mostly anything using the 3.4 kernel.
[Verizon Samsung Galaxy S III] jamesino:
I'm using Caron 4/8 + Kt 4/11 for week now, not a single reboot or freeze or any significant problems.

Previously, I have tried all variations of Carbon and LS roms with all combinations of suitable BMS, LK, and KT kernels and not a single has been stable for more than 4 days except for this current combination I'm using. Try it out.
[Verizon Samsung Galaxy S III] draexo:
Don't think you can run nightlies as your daily driver. You will have problems eventually. I'm still happily running 1.61. I will admit the latest lean kernel seems to be draining battery faster. I usually come home from work with 80%. Now coming home with 60%. Minimum use while at work. I might go back to stock Carbon kernel and see how it compares.

Just don't run a nightly when you need to rely on your phone. It doesn't matter which Rom you run - CM , AKOP, CARBON, - nightlies are inherently unstable over the long haul and you are taking a chance.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] tpayne2345:
Just read the comments here and you can figure out which are the best nightlies.. With the 4/8 build + KT kernel I had 0 problems for over a week, and right now I'm on 4/17 build + KT April 11 kernel and have no problems once again

no reboots, no overheating, no flickering, and no screen backscrolling.. this will be my daily driver until the next official release
[Verizon Samsung Galaxy S III] Setco:
I am running the the 04/20 Carbon nightly with the KT747 04/19 kernel. Did a clean flash and have been running all day without problems. I will post any problems that come up until my next nightly installed.
[Verizon Samsung Galaxy S III] mapatton82:
Nightlies are not meant to be stable releases, one night may be great and the next not so much. Personally I have ran every nightly (at least the ones that booted) and I have not had any issues.

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] draexo:
Can someone provide a link to the governor's and schedulers? I know there is one out there, but I can not find it.

I'm looking for the fastest combination and the combination that is most conservative, as well as something that is middle of the road.

Thanks

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] mapatton82:
Depends on the kernel, butnif you are running KT kernel there is a Team Kernalizer thread in the general section that is worth checking out!!

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] draexo:
I'm talking stock Carbon kernel. I found the thread link in lean kernel forum as well, thanks

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] draexo:
Is there a problem with GPS and workout apps? I just walked a mile and it's telling me I went 7 miles.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] sgs22012:
Gps working to w/in 50ft consistently on my s3 so may be app specific or an app break
[Verizon Samsung Galaxy S III] draexo:
App break? What's that??

It was working fine on touch wiz. I thought it was fixed on CM now.

Sent from my Carbonized S3 via Taptalk

---------- Post added at 05:20 PM ---------- Previous post was at 04:50 PM ----------

I've tried several apps and GPS is off on all of them.

Edit. When I say off, I mean it tracks location but reports miles and miles of travel when there clearly isn't miles and miles of travel. You can stand in one place and watch it slowly show movement.

GPS works in my navigation apps no problem.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] jamesino:
I don't know, I've had SODs and freezes and reboots on both the 1.6 and 1.6.1 stables, but have not had a single problem on the 4/8 nightly for over a week now.
[Verizon Samsung Galaxy S III] sgs22012:
Check settings>location and gps and confirm gps is enabled
[Verizon Samsung Galaxy S III] draexo:
I just checked and it is. Just seems to be the two workout apps. I've used them before no problem. It's could make me go back to a touch wiz Rom...... Sad!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] sgs22012:
For those apps clear cache and data and force stop....restart and see if that helpa if not uninstall and reinstall /maybe it didnt like two different roms or had a cross bleed of info /settings
[Verizon Samsung Galaxy S III] BrUhNiGGs:
I have been at 1.6.1 for a longgg while now. The one thing irritating me is random sods I get from time to time and those freezes when talking on the phone which keeps me from navigating any of the toggle buttons such as even hanging up! I can't wait until 3.4 goes stable as 3.0 isn't completely but it is better...
[Verizon Samsung Galaxy S III] draexo:
No luck

Sent from my Carbonized S3 via Taptalk

---------- Post added at 08:04 PM ---------- Previous post was at 08:00 PM ----------

GPS itself seems to work as the apps seem to show and track my movement around the one mile oval, but report it as nearly seven miles.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] sgs22012:
If you dont mind.....do you have a tw nandroid to restore if so enter samsung service mode and rebuild gps db and recheck. (To enter dial *#197328640# and press send on your dialer ---must be a tw rom....then hit option 3 wait 30 sec and reboot and restore current rom if apps are still acting funny its the apps and you should try to capture a catlog and send to apps dev....
[Verizon Samsung Galaxy S III] draexo:
I deleted my touchwiz nandroid as I wasn't planning on going back too touchwiz.

I know it was working on February 24 of this year. I can't recall if I was running Carbon then or not. I jumped on the carbon bandwagon once 4.2 came out. When was that?

Edit: I have two nandroid on my internal card. One is 2/21/13. The other is 1/24/13. One of these might be touchwiz.

It's safe to nandroid from ASOP to touchwiz and back??

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] sgs22012:
Yes just nandroid your current rom and wipe system /cache /data/dalvik before restoring the tw or before reverting back to current rom
[Verizon Samsung Galaxy S III] 1heffer:
Don't know of a fix but, for me, the sod's only come after a battery swap/reboot. Call freezing only on call waiting.
[Verizon Samsung Galaxy S III] draexo:
Seems to be any app that tracks miles or distance can not keep accurate tally. Five to seven times the actual distance.

Am I the only one with this problem?

I'm 1.60 with stock kernel. I'm willing to try a nightly if you suggest one

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] bamaredwingsfan:
I'm on the April 18th nightly with stock kernel and it's running good for me

Sent from my rOot3d Samsung Galaxy S3
[Verizon Samsung Galaxy S III] Rev. Voodoo:
Yeah, I'm good on the 4/20 as well. Prior to the 1.6/1.6.1 releases I had the same issue mentioned with fitness apps and bad tracking. At some point on the nightlies after the 1.6 release the problem went away for me.
[Verizon Samsung Galaxy S III] Kjennings15:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

I feel like I'm back on super stable liquid 4.1.2. Feels like home.
[Verizon Samsung Galaxy S III] masri1987:
running kt kernel with carbon --

screen time 1h 38 minutes

voice calls - 2h 18m

not sure if all this is good avg or what ---

plus GPS was on for the majority and in use, even though i had it turned off (which was weird)
[Verizon Samsung Galaxy S III] tprophit:
Let the kernel settle a week, it should get better.

There are also a bunch of governor/OC/UV/Tweak recommendations on the KT page. I was running Liquid 4.2.1 with KT kernal, and on a weekend, which is lighter usage than the work week, ran phone down to 3% in 47 hours 10 minutes...

Today, less than 24 hours after flashing the updated KT kernel, had 39% battery after 9+ hours of heavy use.
[Verizon Samsung Galaxy S III] annoyingduck:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

I'm still registering the Google services as using the 2nd most of the battery, which did not happen on Baked, not sure about liquid. Though it does not appear to be effecting battery life in general. Day to day battery life is better than Baked 7, and liquid 4.2.

I'm also convincing a friend with a vzw note 2 to root/rom. This rom will be my selling point! Is there anything incredibly different between our GS3 and the note 2 variations of this rom?
[Verizon Samsung Galaxy S III] bobby janow:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

You are.
[Verizon Samsung Galaxy S III] jmill75:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Agreed, this thing is very stable. On every CM rom I've ever tried I loose days when going to gym, nothing but a reboot would Get it back. This picks 4g back up as soon as I leave. Huge win!
[Verizon Samsung Galaxy S III] masri1987:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Two questions

My phone just switched from rium sim to nv by itself in the middle of a phone call, any ideas?

And is in call volume low for anyone?
[Verizon Samsung Galaxy S III] stlcity:
Guys, have a couple of questions for you: Sorry if this has been covered before:

1. When I place custom apps on the notification bar, (like phone/dolphin browser of example) all I get is a white outline of the icon. With the prior Liquid ROM, the custom icons were visible on the notification bar.

2. Titanium backup cannot seem to find my backups everytime I wipe and install ROMs.. Says no backups when I did back them up ?

3. How do I get rid of the Nav bar once I enable it.

Otherwise the ROM is great. It is running fine. Battery life is good. Thanks to the Devs for all the work.
[Verizon Samsung Galaxy S III] xdapadogx:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Like I said, it's decent. Could be louder but it works for me
[Verizon Samsung Galaxy S III] masri1987:
yeah could be louder too for me, i quickly flashed to masta's latest cm10 morningly\afternoonly and tested audio, was the way i like it, but restored back to carbon for now...
[Verizon Samsung Galaxy S III] cregor:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Did you go into the preferences and change the backup location to where you originally made your backups?

I always have mine backup to extSD, and default in internal sd. So when reinstalled it does not see your backups till you change it.
[Verizon Samsung Galaxy S III] xdapadogx:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

You can use the audio gain for the ear piece in advanced settings if you really want that extra
[Verizon Samsung Galaxy S III] PsiPhiDan:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

You better tighten those days up bro. :p
[Verizon Samsung Galaxy S III] niv3d:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Those of you running KT kernel. Which governor and schedule are you running for battery life mainly?
[Verizon Samsung Galaxy S III] cali4nia831:
Anybody know how to enable headset controls? Is it even possible on this rom? So far thats probably the only thing missing from this amazing rom. Call volume could be a little louder too.
[Verizon Samsung Galaxy S III] bobloblaw1:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Pretty sure good battery settings are on the last page or two of the kt kernel thread....
[Verizon Samsung Galaxy S III] jakereeves31:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Yeah, I'm running those and I've gotten this so far after the first day.
[Verizon Samsung Galaxy S III] annoyingduck:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

1: not sure

2: any variation in the way a rom identifies a storage point will cause titanium to not locate your backups. The easiest way to fix this is to go into preferences in titanium/backup storage location/choose to detect/titanium will then automatically find your backup then choose use this location after it finds it.

3: just un click enable nav bar in settings. You may need to reboot
[Verizon Samsung Galaxy S III] Real_JESRadio:
CarbonROM review!

Here is my recent video review of this very fast ROM! Great job guys! http://youtu.be/DCRrQ6Ku9Ik
[Verizon Samsung Galaxy S III] tprophit:
Interesting. I checked my baseband, and I still have i535vrblk3. Is that a function of using KT Kernel?
[Verizon Samsung Galaxy S III] draexo:
Guess I'll try a nightly. Suggestions?

Guess I couldd download them all and just try....

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] fcardona86:
Haven't experienced anything crazy on 4/21. One freeze today but other than that smooth.
[Verizon Samsung Galaxy S III] jlokos:
4/22 build with LK 5.5 exp working smooth as silk; No Fc's and no screen flicker.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Never had Carbon work with fitness apps ever. Ride 7 miles and log 40 miles is the typical result I got in Carbon Version 1.0 to 1.5. That's was the deal breaker (along with Google Voice mail in Dialer force close) that was why I left for SOA Rom where fitness apps work fine on all builds.

Ping me when it's fixed because I'd love to come back to carbon when fitness apps work.
[Verizon Samsung Galaxy S III] rhcp1253:
My battery life sucks, android system using almost 20 percent
[Verizon Samsung Galaxy S III] draexo:
Horrible flickering in stock message app with stock kernel and 4/22 nightly. Disabling hardware overlays fixes this.

Not sure if the GPS issue is fixed.I will know tomorrow.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] moparfreak426:
This may or may not be a stupid question.... How does this stand apart from say slim ROM? Or the now banned from xDA jellybam?

Sent from my SPH-D710 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S III] mapatton82:
This rom is smooth, fast, and has tons of customizations. Make a backup and give it a try, you won't be disappointed!!
[Verizon Samsung Galaxy S III] Rev. Voodoo:
It's been fixed for me on every nightly since the 1.6/1.6.1 release. Just used it last night. I was using cardio trainer and have recently switched over to runkeeper. Both have been fine for nearly a month now. And I'm one of the folks who experienced the same problems you did. I did a wipe and flash at 1.6 and have dirty flashed since.
[Verizon Samsung Galaxy S III] draexo:
Jellybam got banned??!! That was the first Rom I used once I rooted my S3. Then I went I on a mad flashing week and I've been on Carbon ever since!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] 760hacker:
anyone flash the latest 4/22 nightly?
[Verizon Samsung Galaxy S III] mapatton82:
Yeah, works great!! The new lockscreen settings resets the lockscreen targets though.
[Verizon Samsung Galaxy S III] jlokos:
It is working great for me with newest LK 5.5exp.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Thanks. I'm back on Carbon now. Will give the fitness apps a try when I have a chance.

It's nice to be back. Lots of cool features. +1000 for the Settings>Language and Input>Disable Fullscreen Keyboard and the Settings>CarbonRom>Interface>Use Alt Defualt App Picker

4/22-004407 nightly, lk 5.5 (interactivex, row, 384-1836mhz, undervolted 75mv across the board down to 875)

Manually installed Xposed Framework and App Settings for my dual pane Gmail, Email, and Tapatalk HD

So far so good. Stable and no issues.

Only nit is that the Google Voice messages in Dialer still force closes the dialer.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
I hope they work for you ... I don't wanna be giving bad intel!! :D But yeah, been good on my end for a while now. Your other issue, Google voice messages in dialer..... I'm not 100% on understanding the issue you have to know if I have it on my end as well ....