yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] cjmcsw87:
That's what I'm talking about ! Thank you I appreciate it. I do have one more question though ..sorry. I would want to pick a theme marked with the "star" for cm 10.1, correct? Thanks again for the help.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] mapatton82:
Yes that's correct.

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] cjmcsw87:
Good stuff. I won't be new forever :D

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] BrUhNiGGs:
When dirty flashing from nightly to nightly, do you have to reflash tweaks such as Acid Audio mod, custom kernel, cross breeder, tk mod, etc?
[Verizon Samsung Galaxy S III] pocii29:
I know you have to re flash kernels. But modems stay the same. Not sure about the others...

I'm also an apex user. And you can backup your desktop on the free one. To find themes. Just use cm10 themes on the playstore
[Verizon Samsung Galaxy S III] cjmcsw87:
Since I flashed I've been getting SMS messages coming in saying vzwnmn 1 from 6250.. Anyone have any idea what this is ??

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] johnsgone:
I had that or at least something extremely similar ( cant remember the exact #'s) happen yesterday when I had been pissing around on big reds website and clicking on the new "backup assistant" bs they are running. They hit my phone with the SMS, I panic moved with a quick battery pull, kicked my power strip off and lit up quick. No problems though. Took off the tin foil hat & no more msgs so you ought to be fine. Of course I wear a tin foil hat, may not be the best one to listen too.
[Verizon Samsung Galaxy S III] airmaxx23:
Where can I find the Halo build, I can't seen to locate it. Thank you.
[Verizon Samsung Galaxy S III] lazarus0000:
It is supposedly the bogus Back Up Assistant BS but I've cruised Verizon's site as well as spoken with a rep and I am not signed up for any of their useless crap. I get the same text @ least once a day and it seems to happen every time I reboot as well as occasional random ones as well. Sort of a pain but only because I have to see who's texted me & see its the same garbage.

No one that I'm aware of has a fix. I've been told, over & over, to disable the back up assistant and I do not have that enabled.
[Verizon Samsung Galaxy S III] OMG_VTEC:
are the nightlies compiled with 3.4? i really want to try this halo crap but my phone doesnt like 3.4.

and if they are, is there any carbon development continuing with the 3.0 chain
[Verizon Samsung Galaxy S III] Rev. Voodoo:
The Carbon community on Google+ has it, probably a post from about a week ago?

https://plus.google.com/103315278250477995368/posts/8GgNg4PUxEM <-- edit: here it is

---------- Post added at 01:07 PM ---------- Previous post was at 01:06 PM ----------

They've all been 3.4 for some time now.... Unfortunately I can't recall the last nightly to run 3.0 - probably about a month ago? I don't beliee there is any way to tell from the naming of the nightlies.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Last nightly with a 3.0 kernel was back in March... Or the 1.6.1 stable build also runs 3.0.

From here on out the developers are building on the 3.4 base kernel...its come a long way since it's first nightly and runs very very well for me. Give 5/29 nightly a try (doesn't include halo tho). Running smooth as silk after a clean install for me.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
5/29 was the last one to install easily for me. I'm on 5/30 now, but I had to clean flash and screw with it a lot. ANything after that has just sent my phone into a boot loop - including the most recent 6/2. I'm not gonna play with the halo builds until they mature a bit.

But yeah, the 5/29 and 5/30 builds are great for me as well!
[Verizon Samsung Galaxy S III] imtoomuch:
Has anybody been having problems with Bluetooth? I started using this ROM as my daily driver mainly because it was stable and the Bluetooth worked flawlessly (March 26 build). On the recent nightly builds (currently using 05/27/2013) the phone has a hard time connecting to my car. It doesn't connect the first time and sometimes not at all. When it does connect I can't use voice dialing in my car.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Had this issue today as well on 5/29 nightly. No issue on 1.7 stable but after a few pair - delete pair cycles with my car I don't seem to be having any trouble. After a successful drive home using Bluetooth calling and music I have wiped cache and dalvik and foxed permissions, returned to my car and it connected as normal without any issue (phone & music). Try that...see if it helps you as it did me.
[Verizon Samsung Galaxy S III] imtoomuch:
Thanks. What do you mean by fix permissions? Just the standard Bluetooth password/permission?
[Verizon Samsung Galaxy S III] WettbackMartyr:
I mean when you go into recovery mode and perform the clear cache/ dalvik operation there is also an option to fix all apps permissions under advanced menu I believe.
[Verizon Samsung Galaxy S III] imtoomuch:
Thanks. I'll check it out.

The 6/1 nightly immediately gave me an android process crash as soon as I rebooted. When you click "OK" it just shows the same process crash window over and over again. The 6/3 nightly install failed. I'm not having any luck. The weird thing is that GOOManager said I didn't have an update even though I was on 5/27 all of the builds up to 6/3 are available.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Can't comment on nightlies after 5/29 as the Google drive changelog hasn't been updated since then so that's as far as I've flashed. Others here have made some iffy commentary on 5/30- current nightlies so I've stayed away so far.

Goo manager update notifications have ceased for me as well.
[Verizon Samsung Galaxy S III] cjmcsw87:
Seems my call log is broke. I just flashed over the weekend and hadn't made any calls until today. I'm on 1.7 w/ included kernel. I restored my call log w/ TiBu... Any ideas?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] rossida:
6/4 nightly constant process stopped after boot.
[Verizon Samsung Galaxy S III] slick_rick:
I updated all d2 trees an hour ago or so. Should run fine for tonights nightly.
[Verizon Samsung Galaxy S III] rossida:
are u saying that u reuploaded 6/4 or for 6/5 will it be working fine? and thanks for the feedback :D
[Verizon Samsung Galaxy S III] wareynolds:
Hopefully he means 6/5 build as the 6/4 is crashing for me.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
Oh, nice!! As always, I assumed I was screwing something up! Thanks for the update!
[Verizon Samsung Galaxy S III] draexo:
Right now I see two 6/4 builds, a 0240 & 0517.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] airmaxx23:
How do you access the Halo settings?
[Verizon Samsung Galaxy S III] WettbackMartyr:
I'm sure I can help you but you didn't describe the problem you're having with the call log...I understand you restored XML data of the call log with TiBu but what are you experiencing when using the call log that makes you think it's broken?
[Verizon Samsung Galaxy S III] cjmcsw87:
Sorry. None of my calls are going to my call log. Only ones there are the restored ones.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] imtoomuch:
+1! Holo settings?
[Verizon Samsung Galaxy S III] mapatton82:
There are only 2 settings right now in Settings|Carbon|Interface under the section Halo. There is also the blacklist options in Settings|Apps for each option there is a checkbox to Blacklist that application in Halo.
[Verizon Samsung Galaxy S III] airmaxx23:
Thanks, I gave up on it for now. Anytime I got a text message systemui would stop working and Halo would not pop up at all. That, and there are a few apps that still show up in Halo even when they are blacklisted. I know the blacklist resets after a reboot but the apps still got notifications in Halo even when blacklisted.
[Verizon Samsung Galaxy S III] mapatton82:
The Halo builds are still considered alpha. I've noticed that if I close Halo, reboot, and open Halo I don't get any System UI FC's.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Why don't you go ahead and just clear the call log and clear data on "phone" and "phone/ messaging storage" and then see what happens. You already have the backup saved anyways so it can't hurt. What I believe happened is for the same reason a clean flash was recommended a while ago when they added custom notifications to contacts, its just manifesting itself in a different way but some data from your backed up call log is corrupting the new call log.
[Verizon Samsung Galaxy S III] airmaxx23:
Thanks, I'll keep that in mind. I'll be trying the next Halo build as soon as it's available, I was hoping this build would be a bit more stable for me.
[Verizon Samsung Galaxy S III] imtoomuch:
I'm on the 20130604-0517 nightly build and the swipe doesn't work on the keyboard. I can type just fine, but swiping doesn't work.
[Verizon Samsung Galaxy S III] krazie1:
6/04 build has issues with Shadowgun Deadzone, I open it and it always just exits to the homescreen. I cant even get a game started before it goes to the homescreen.
[Verizon Samsung Galaxy S III] cjmcsw87:
That worked..should I give restoring the call log backup another shot?

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] WettbackMartyr:
I wouldn't. Obviously there was a data discrepancy between ROM versions. I'd leave it as is if it works.
[Verizon Samsung Galaxy S III] cjmcsw87:
OK. Issues like this are fairly common when changing from 4.1 to 4.2 or visa versa I take it.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Wi1son:
YSK - There is a Halo companion app in the Play Store called Halo))). It let's you pin apps to Halo, even if they have no notification.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Well there Ya go buddy! Now I get it. I didn't know you were upgrading from 4.1 to 4.2! Yea there can definitely be issues like that.

Now that you're on 4.2 I'd stay with it!

Makes things easier. :thumbup:
[Verizon Samsung Galaxy S III] cjmcsw87:
Yeah I like the smoothness of 4.2 a lot better, my signal was better on 4.1 but it's just where I live in between these hills. I haven't seen my free ram drop below 900ish and as high as 1256 so that's niiice.

I did like the goodness reborn ROM it was pretty nice. Best tw ROM imho as soon as they get a couple of bugs taken care of.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] shilohdrummer:
The Bluetooth on this rom has ALL it's audio coming out of the headset. EVEN ALL phone calls+All ALARMS+ALL notification sounds. This is problematic since I don't always have the headset on my ears. I even forgot to turn my bluetooth off so I couldn't hear my morning alarm since the sound was coming out of my bluetooth headset. Was late for work.

Liquidrom seems to have the exact same bluetooth driver as this one, but the necessary notification audio does come out of the phone and headset at the same time. Maybe copy the drivers from there?
[Verizon Samsung Galaxy S III] OMG_VTEC:
Is there an option to change the led color? I don't remember if it was on the earlier version of carbon or on liquid.

If not, can it possibly be added later?
[Verizon Samsung Galaxy S III] shilohdrummer:
You can change it by going to display setting> pulse light notification> you can even add custom notification light colors for specific apps by pressing the +

Now if only someone can solve my Bluetooth problem
[Verizon Samsung Galaxy S III] imtoomuch:
The switched to the AOKP keyboard that doesn't support swipe?

And Bluetooth doesn't work?

I don't get it...
[Verizon Samsung Galaxy S III] WettbackMartyr:
Huh???? All works fine for me! :thumbup:
[Verizon Samsung Galaxy S III] krazie1:
Still have issues with Shadowgun Deadzone on the new nightly. It closes immediately after I try to sign in, can you guys fix this weird bug?
[Verizon Samsung Galaxy S III] Rev. Voodoo:
Yeah my bluetooth has been really flaky for about the past week. Since myaybe around 5/29 nightly (not sure exactly).

I just cannot get anything to reconnect. I have a bluetooth watch, and my bluetooth headphones. If I get out of range for the watch I have to restart the phone to get them talking again. As for the headphones, once I shut them off it's over. Every morning now I have to unpair them. Then When I try to shut off bluetooth it just gets stuck at the turning off bluetooth screen. I then have to reboot my phone to get bluetooth to show as off. Then I can repair and reconnect my headphones. Bluetooth works fine when connected, I just have to go through a lot of song and dance every day.
[Verizon Samsung Galaxy S III] HypostaticOnion:
What? AOKP keyboard swipes fine. I'm on AOKP.
[Verizon Samsung Galaxy S III] draexo:
Hey, was there a certain nightly after which we WERE REQUIRED to wipe user data?? I'm getting nothing but force closes on 6/5 & 6/4

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] Wi1son:
A clean wipe was recommended for 5/22

SCH-I535 on CarbonRom & KT747
[Verizon Samsung Galaxy S III] draexo:
So 5/22 and anything after?

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] mapatton82:
On 5/22 they added a feature to allow custom ringtones and notification for different contacts, thats why a clean install was needed. Since then you should be ok to dirty flash each nightly. I know they did have a few builds (6/3 and 6/4) that people where getting a lot of FC's. I don't know about the latest nightly since I am running the Halo build.
[Verizon Samsung Galaxy S III] Rev. Voodoo:
Yeah, for about a week in there... like maybe 5/31-6/4 or so things were messed up.

They had to do something involving the RIL to fix the ROM, I'm on the 6/5 nightly with no problems.

I know when I was using a restore after flashing a jacked up ROM, I would forget to factory wipe first and it wouldn't work... had to make sure to factory wipe then restore. I did that to get back to my 5/30 backup, and was able to dirty to 6/5
[Verizon Samsung Galaxy S III] imtoomuch:
The swipe doesn't work for me. I wiped cache and davlik and re-flashed multiple times and I still have the same issue. I had to install the Google keyboard from Play to get swipe back.
[Verizon Samsung Galaxy S III] shilohdrummer:
You might have to wipe and format data to get rid of the previous version of keyboard. I personally don't use that AOSP swype. It's not as accurate as the original Swype. There's a 1 month free trial on Google Play Store. Not really thinking about what to do after my 1 month trial ends, I'm just enjoying the fast typing at the moment.
[Verizon Samsung Galaxy S III] imtoomuch:
I don't like the "official" Swype. I prefer TouchPal and it's free.

I will eventually wipe, format, etc. Thanks.
[Verizon Samsung Galaxy S III] rigman:
Vibrate mode very weak

I searched the posts for "vibration problems", and found in Feb. where someone said the vibration was real intense. But I've had the opposite problem since switching from the stock ROM to this ROM a few days ago. I can barely feel the phone vibrate at all. Is that a function of the ROM? Or the kernel? Or what? I'm running nightly 20130604-0517.
[Verizon Samsung Galaxy S III] BattsNotIncld:
Settings>Advanced>Haptic>Vibrator Intensity
[Verizon Samsung Galaxy S III] tprophit:
On 1.7. Using GOSMS pro, as I have since before Carbon. Usually, after a reboot, get 'unfortunately messaging has stopped working ', I.e., the stock app. Occasionally, would be difficult to send s photo. Today, it's freaking impossible. No changes have been made. Suggestions appreciated. Thank you.

Edit : on wifi is the problem, 4g working.
[Verizon Samsung Galaxy S III] glman1:
Try a newer nightly. 1.7 is 3/4 of a month old, and there have been a ton of improvements in the latest nightlies. Download the 6/06 one and flash it.
[Verizon Samsung Galaxy S III] tprophit:
Thanks but it doesn't explain why mms not working....

Is a clean flash required because of the notification changes in an earlier release?

Thank you.
[Verizon Samsung Galaxy S III] draexo:
Ditched Swype.

Formatted user. Running stock Carbon 6/6 nightly.
[Verizon Samsung Galaxy S III] cjmcsw87:
Should my voice to text be working on this ROM ? The button is on my keyboard but pressing it does nothing. On 1.7 w lk 6.2 I think.. Pretty sure didn't work w/ stock kernel either

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] PeterGunz:
Installed the Halo version and phone gets stalled at the splash screen. Wiped and tried to restore a backup and still freezes. Wiped and installed a different rom, still freezes at the splash screen.

I am assuming I will have to Odin back, but just wanted to give a heads up that there might be an issue with the current Halo download that's up. Anybody know a place to download a stock image that doesn't take several hours?
[Verizon Samsung Galaxy S III] draexo:
I always used it

---------- Post added at 10:57 PM ---------- Previous post was at 10:57 PM ----------

I just went from 1.7 to 6/6 nightly.

What have I gained? I can't find change log.
[Verizon Samsung Galaxy S III] glman1:
https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/mobilebasic?pli=1

Basically, Pie improvements, framework changes, lots of small fixes, Dalvik improvements, LED improvements, the ability to assign contacts notifications, Ribbon improvements, and a fix for the phone FC.
[Verizon Samsung Galaxy S III] cjmcsw87:
So anyone know how to fix it?

Edit: my voice to text, that is.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] krazie1:
6/7 Nightly will have the Games Fixed in it, really looking forward to it. Thanks CarbonTeam
[Verizon Samsung Galaxy S III] winner00:
New halo build if you guys want it: https://docs.google.com/file/d/0B56PlNCXH0HrUy1ORjBHNE1LaEk/edit?usp=sharing

This is the latest halo code so it should be more stable also has the latest carbon code. So games are fixed in it.
[Verizon Samsung Galaxy S III] rossida:
Thanks so much!! i love the halo feature! ive been with carbon since the liquid split and love everything u have done to this rom! Thanks so much for everything!!!
[Verizon Samsung Galaxy S III] krazie1:
Thanks a lot winner00, definitely deserve some Thanks (hint to the community)
[Verizon Samsung Galaxy S III] cjmcsw87:
Actually I was wrong the mic button is not on the keyboard. When I go into input setting I can't get the " mic on main keyboard" or "mic on symbols keyboard" toggle to stick. As soon as I press the back button and go back into setup input there is a blank underneath 'voice input key" instead of specifying which keyboard its on (main, or symbols).

I just wiped cache/dalvik then fix permissions with no luck. Then I tried downloading the new Google keyboard app and no dice, same result. Makes me think I somehow missed the voice to text software.. I do remember having the button on the keyboard after flashing carbon but It never worked. I'm thinking the mic button went M.I.A. when I flashed LK.

Any help would be appreciated.

Sent from my SCH-I535

---------- Post added at 01:39 AM ---------- Previous post was at 01:36 AM ----------

Build 1.7 LeanKernel 6.2

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] cobija:
Thanks for the new halo build, everything seems to work great. However, one feature I really used on 6/5 was the clock actions (carbon>statusbar>clock and date>Clock " " actions). Seems to be broken in this build.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Have you checked to make sure there is not an update waiting in the play store for your version of Google Search? That'll effect it. Other than that try clearing data on Google Search & Android keyboard and reboot.
[Verizon Samsung Galaxy S III] tpayne2345:
clean flashed the new Halo build and every time I receive a text the SystemUI stops

anyone else getting this?
[Verizon Samsung Galaxy S III] Wi1son:
I'm getting a lot of systemui crashes too. Dirty flashed the new halo build over the last one. I also can't close Halo.

SCH-I535 on CarbonRom & KT747
[Verizon Samsung Galaxy S III] cjmcsw87:
OK for some reason my Google search was disabled. I'm thinking I might have done that in the initial setup. Enabled that and cleared data on it and keyboard. Still isn't working the mic button is back but it FC instantly and also sets my default input to voice typing.

Sent from my SCH-I535

---------- Post added at 01:28 PM ---------- Previous post was at 01:16 PM ----------

fixed it. There was an update so thanks for that. Cache dalvik and permissions. Money.

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] pocii29:
So I have figured out my force close issues. I am trying to run a titanium backup thats from a pre 5/23 build. for the 6/6 halo build

What can I exactly can I restore that wont conflict with the new notifications build? Just apps+data? can I run any system settings restore?
[Verizon Samsung Galaxy S III] mapatton82:
I would stick with only user apps+data, leave the system apps alone they will cause issues.
[Verizon Samsung Galaxy S III] rfranken:
new halo build running ok so far. (clean flashed)

Torch crashes every time you run it. (whether from the app itself or a shortcut in your pull down menu tiles)

halo really doesn't work all that well.

I just turn it off after playing with it for a bit.
[Verizon Samsung Galaxy S III] gts012:
Dirty Flashed new halo build over a clean flash of the last one. Had a SystemUI crash on first reboot, but left Halo open before flashing in recovery. I closed Halo, rebooted the phone and no SystemUI crashes. Halo working great.

Only janky thing I've found is I cannot hit Install when trying to sideload apps with Halo open. Need to get rid of Halo before being allowed to hit the install button. Cancel works fine....sort of odd.
[Verizon Samsung Galaxy S III] jlokos:
I had the same issues on sideloading apps. I continue to have SystemUI crash intermittently. Halo working great.
[Verizon Samsung Galaxy S III] cobija:
I think all halo builds need their own clean flash. When I dirty flash the prior 5/30 alpha halo build I was getting system UI crashes and other problems. Clean flashed 6/7 with no issues beside the one I stated before.
[Verizon Samsung Galaxy S III] pocii29:
Aside from having to redo my system settings... This halo build is badass!
[Verizon Samsung Galaxy S III] Masterfisto:
Running the las test halo build. I've had zero force closes so far. This build rocks!
[Verizon Samsung Galaxy S III] pocii29:
Every time I use halo to open text messaging while in a non system app. It seems to close the app to homescreen and then launch the in-window. Anyone have any ideas
[Verizon Samsung Galaxy S III] draexo:
Battery won't charge past 88% since I flashed 6/6 build.

Clean install.

Stock kernel.

Battery draining fast too.

Update. Phone now at 82%. Sensors report 100.6 degrees. Not even using it. Normally high 70s in this situation.
[Verizon Samsung Galaxy S III] boman06210:
I've just (clean) flashed 6/7 from 1.7 - smooth sailing.
[Verizon Samsung Galaxy S III] krazie1:
Loving the Carbon HALO build from last night, its awesome thanks again.
[Verizon Samsung Galaxy S III] draexo:
Flashed kt747 for giggles. Temperature down to 92. Phone still Will not charge.
[Verizon Samsung Galaxy S III] cregor:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Thanks. I have tried uninstalling/clearing data-cache. Several times no luck always wants to play on speaker.
[Verizon Samsung Galaxy S III] rebretz000:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Loving the ROM. Great battery life. Only minor issues. Notification turned off on hotmail but phone vibrates when mail comes in.
[Verizon Samsung Galaxy S III] Dcox28:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Anyone notice that the phone only rings once when getting a call? My phone rings once then just vibrates. Minor annoyance but great rom
[Verizon Samsung Galaxy S III] cpttsubasa:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

Thank you for replying. Weirdly, it didn't work in my case
[Verizon Samsung Galaxy S III] Neverender326:
Re: [ROM][AOSP][LINARO] CarbonRom JB 4.2.1 [d2vzw] » Feb 6

This rom plays so nice with Ktoons kernel. I'm in heaven. Left on overnight (data off)... 2% drain.