yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] tprophit:
I'm on 4/30, and had to do the fix described earlier. GPS lock takes longer, 30-45 seconds. Once locked, it is accurate to within 12 feet.
[Verizon Samsung Galaxy S III] rossida:
stuck on splash screen of the newer 5/01 again. tried all kernels from KT and is a clean wipe

---------- Post added at 04:59 PM ---------- Previous post was at 04:19 PM ----------

wel **** im having problems. not sure if i bricked my phone or what but i cant restore to any of my backups using twrp 2.5 it fails after saying restoring data. after every clean wipe to install any of the roms i have saved with the gapps it gets stuck on splash scren saying samsung galaxy s3. can someone please help me!
[Verizon Samsung Galaxy S III] Setco:
Strange...I'm on carbon's 5/1 nightly with KT747's 4/30 kernel and GPS works here:confused:
[Verizon Samsung Galaxy S III] buffal0b1ll:
Carbon finally passes the off-road, out of cell coverage, and correct distance in fitness apps test. Garmin Connect app to be specific.

4/25 nightly with lk5.5

Yay!
[Verizon Samsung Galaxy S III] rfranken:
*fully prepared to get flamed for this...but here goes*

Could the carbon devs stop the nightlies and stop any future new features for awhile and focus on getting this rom STABLE?

The rom is awesome and has everything it needs already. These nightlies just fragment the crap out of its user base,this thread, and well...there are several things that need to be made more stable.

(be gentle)
[Verizon Samsung Galaxy S III] mapatton82:
You have a point but the users need to remember that the nightlies are "use at your own risk", some nightlies are great and some are not so great. Basically the nightlies allow the devs to throw experimental features and fixes for the user to try. If anyone is looking for a stable build they would be version 1.6 and 1.6.1.

Personally I like flashing the nightlies to see what new changes are included. If it doesn't meet my standards then I just nandroid back to the backup I created before flashing.

I hope you don't take this as a flame on you, because that is not my intent. Just adding my $.02!! :)
[Verizon Samsung Galaxy S III] PeakyBoo:
^+1

I agree. And for my 2¢…

I have been flashing Nght's from the start, NOT just with Crbn ROM either , and all I can add to this is the fact that I have never really had any issues with Carbon Roms nightlys that weren't fixed by either a reboot or a total clean flash. If you flash a Nightly and things don't jive, try a "CLEAN" install of that nightly. Sometimes a double System , Cache, Data wipe (after a factory wipe), and before flashing, (I know some people say that doesn't help and its redundant), but, what ever works for you is what I say. Remember, all phones are not alike, and what works for some does not always work for others. "A TRUE CLEAN Install/Flash" is the way to go if you are one of the ones having issues. Also a clean stock backup wouldn't hurt. So you can start from scratch. Happy Flashing Ya-All!:thumbup:

:good

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] jlokos:
+1; there is no requirement that you flash the nighlies; you can stay on the "Stable" builds. However, I must disagree with rfranken that "there are several things that need to be made more stable..." I just don't see those "things."
[Verizon Samsung Galaxy S III] draexo:
I run nightlies to try to get away from bugs in stable!

Sent from my Carbonized S3 via Taptalk

---------- Post added at 07:05 PM ---------- Previous post was at 07:00 PM ----------

Does 1.6 work with GPS on fitness apps???

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] PeakyBoo:
Huhhhhh?

What bugs Exactly are you talking about?

Also on which version? 1.6.0-3.4 or 1.6.1-3.0?

If you are having issues with any stable Crbn ROM might I suggest you Odin back to stock and start from scratch. You might have something else going on. JMO!

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] draexo:
I need a working GPS. I'd prefer no screen flicker, but I can live with it for now by disabling hardware overlays.

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] PeakyBoo:
OK. I can't speak for the latest nightly, (although I know some who can) but, if you are having those said issue ( I / them) can for sure say, it is NOT Carbon!

For 1;

GPS has never been an issue (other than a few fitness apps) Which has been FIXED for a few nightly's back and actually app related so code was adjusted to fix! NEXT!

#2

Screen flicker has been fixed for awhile now.....and

(YOU HAVE BEEN TOLD THAT) by me and countless others here!

Dude, sorry, but you are starting to get on my nerves! You CONSTANTLY come here and complain about stuff not working yet show now info on exactly which version or how you went (STEP-BY-STEP) about getting there, and, you have been told a countless amount of times (by me and others here) about how to fix the same issues..,Sorry everyone!!!

I am done with this and you.:banghead:

Peakyz ° S lll °
[Verizon Samsung Galaxy S III] Dragery:
Running 1.6.1 with stock kernel. Absolutely no screen flicker, ZERO force closes, restarts, and GPS has worked 100% of the time for me since flashing two weeks ago. Maybe it's a hardware issue, or other issue on your end, if you are continually experiencing the same problems after several flashes.
[Verizon Samsung Galaxy S III] mapatton82:
I agree!! Well said!

Sent from my Galaxy S3 with a Carbon footprint
[Verizon Samsung Galaxy S III] gzsmooth:
Could someone tell me which GAPPS I should be using?
[Verizon Samsung Galaxy S III] draexo:
*click unsubscribe*. Flash cyanogen. Or TouchWiz.

I won't bother you anymore. Good bye!

Sent from my Carbonized S3 via Taptalk
[Verizon Samsung Galaxy S III] prototype7:
https://sundergaming.com/downloads/gapps/4.2.2/gapps-jb-20130301-signed.zip
[Verizon Samsung Galaxy S III] pocii29:
Dude its true you whine a **** ton on this board. I think you forgot that these are Nightlies and Nightlies are supposed to have issues. If you don't like that... Go back to stable builds.
[Verizon Samsung Galaxy S III] cregor:
I have been on stable 1.6.1 since it came out and I absolutely love it. I have been getting the itch to flash again. I have never gone this long on the same build. Guess that says something about how great it is. What would you all say is the best nightly?
[Verizon Samsung Galaxy S III] Zaf9670:
I'm still on 4/8 and using LK 4.3 or 4.4 I think. My only issue is sometimes when I'm below 20% and do something intensive it will power down. I think that's just my extended battery.
[Verizon Samsung Galaxy S III] lucky13:
It was my understanding gapps was baked into the ROM now. I haven't flashed a gapps in awhile, even after a clean install, is that correct?

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Take a look at the change log and see what interests you https://docs.google.com/document/d/1Zcp6iVWVw_7iH-ErnKgkYy3r5QuqV8PHFoQMb8hoBwQ/mobilebasic?pli=1

BTW goo manager supposed to have change log link working for 5/3 Nightlies forward:)

Read back a few pages and see what recent nightlies sound like good DDs.

Personally I love 4/25 with lean kernel 5.5 (that's a 3.4 kernel Rom)

It includes the GPS fix for fitness apps and its the first day of paranoid hybrid settings (paranoid only available 4/25 to 4/27). Some folks complained of screen flicker, which I had too due to undervolting. Once I found (and posted a few screens back) the right voltage flicker disappeared. The only nits I have are Google voice/phone dialer voicemail integration bug and Google Now hotword detection causes random reboot on my phone when not disabled. Both those nits are not deal breaker for me.

The other nightlies that are more than a few pages back in the thread but stand out in my memory as being good choices are 4/8, 4/20, 4/22. Of these I only tried 4/22 which I ran on lean kernel 2.9 (that's a 3.0 kernel Rom)

---------- Post added at 11:42 PM ---------- Previous post was at 11:33 PM ----------

I believe that you don't need to flash gapps if you are dirty flashing. I also believe that if you factory reset or wipe system you need to flash gapps again, but I've never tried clean flashing carbon with out also flashing gapps.

In my experience reflashing gapps even if they are not needed takes less than a minute. Far less time than booting and finding no gapps and going back to recovery to install them would. I know of no negative effects of flashing gapps over gapps that may already be there.

Also, the file size of the ROM doesn't suggest to me that gapps are baked in.
[Verizon Samsung Galaxy S III] rfranken:
I always clean flash and things usually work really well.....for awhile. Then everything starts going wonky. I'd like to not have to clean flash every other week if possible to keep the Rom running smoothly.

You crack flashers don't see things degrade cuz you keep flashing so often.

And the stable builds aren't more stable than the nightlies from my experience.

Most annoying bug on my build are the screen jumps in most apps.
[Verizon Samsung Galaxy S III] slick_rick:
No please dont leave!

:p No but seriously, we dont need users who cant follow simple directions when posting about bugs or other issues.

And for the millionth time, its "CyanogenMod" not "Cyanogen" I see this everywhere and it drives me nuts. Carry on.
[Verizon Samsung Galaxy S III] mapatton82:
It appears that the persistence settings (to save LCD density and host file across flashes) was taken out of the latest build (5/3). Hopefully it makes its way back in again!!
[Verizon Samsung Galaxy S III] prototype7:
Don't flash cyanogen, he probably wouldn't appreciate it :p
[Verizon Samsung Galaxy S III] pocii29:
Flashed 5/3 last night. Having 2 issues of anyone was curious about moving to this. First the phone will randomly flash the screen black like it's thinking I'm in a call and holding up to my ear but then again quickly come back online. Second the Gps isn't locking for me.

And for anyone who was curious. I clean flashed and gapps was already baked in

---------- Post added at 05:56 PM ---------- Previous post was at 05:48 PM ----------

I just found why it's flicking on and off... It's every time my hand moves over the sensor at the top of the screen
[Verizon Samsung Galaxy S III] TheBurgh:
I clean flashed and have no problems. This was actually the first nightly in a few days that I could get the GPS to work. Great for me so far
[Verizon Samsung Galaxy S III] dg4prez:
i need to spend more time in this thread with my d2 brethren. i've been a lot busier managing this device, though.

since i've been away a while and can't really be bothered to read back a million pages... who wants to let me know what issues persist? i myself don't have gps issues, but i want to know about them.

flicker should be fixed, as well as stability. steve k keeps mucking about with the upstream d2 kernel so much that i forked it and am maintaining it manually, which means we have a flicker fix and stability fixes that aren't on their nightlies (though i suspect mastamoon's builds have them.)
[Verizon Samsung Galaxy S III] dg4prez:
i should probably mention that 1.7 is available...
[Verizon Samsung Galaxy S III] ckelly33:
FLicker and reboots have been my only issue. Not that big of a deal but if I can rid myself of them I will....where do the 'flicker-free' builds begin?
[Verizon Samsung Galaxy S III] dg4prez:
flicker was caused by an mdp parameter adjustment. it was fixed, and then somehow got back in there, which is when i forked the kernel. it's since been reverted for carbon builds.

this is the offending commit:

https://github.com/CarbonDev/androi...mmit/14d55c8fadd4710aecc142cb2790cc95c5ab59ad

there are a couple other reverts in there that i applied that have brought my reboots down to nearly nothing. 1 in the past few days. not sure if that's coincidence or not - it's still being worked on quite a bit.
[Verizon Samsung Galaxy S III] lucky13:
Voice mail from the call log crashing is a persistent issue. ;)

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] dg4prez:
it sure is. i think i'm gonna make that a priority.

who wants to get me a logcat? if you do, tell me if you're using google voice or not.
[Verizon Samsung Galaxy S III] pocii29:
Gps and screen stopped bugging out and all working now :)
[Verizon Samsung Galaxy S III] prototype7:
Read the thread, you noob :p

---------- Post added at 08:21 PM ---------- Previous post was at 08:19 PM ----------

Can't think of anything... is flicker fixed? Been using a build.prop hack to fix it myself that I mentioned to you before, haven't flashed the latest version.
[Verizon Samsung Galaxy S III] lucky13:
I'm using Google voice, and was not able to produce a log cat that showed anything. I'll keep trying and see what I can get, hopefully someone else can get one also.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] 760hacker:
So does 1.7 have flicker or was it reverted prior?
[Verizon Samsung Galaxy S III] dg4prez:
Been fixed for days.
[Verizon Samsung Galaxy S III] ckelly33:
does 1.7 have GAPPs goodness baked right in?

EDIT...NOPE
[Verizon Samsung Galaxy S III] Trumps:
503 has been running awesome for me, even dirty flashed.

Sent from your moms house using xda premium
[Verizon Samsung Galaxy S III] lucky13:
Why did the option to sort contacts by last name disappear? I have several hundred contracts for work and I know 90% by last name, makes it awful to scroll through.

Sent from my S3...like a BOSS.
[Verizon Samsung Galaxy S III] jeremytheindian:
Dirty flashed 1.7 over 1.6.1 and everything seems to be working fine.
[Verizon Samsung Galaxy S III] ckelly33:
I think I've found a bug in 1.7.

When using the camera, usually when you take a picture then swipe from righ to left, it brings up the "filmstrip view", starting with the picture that you just took. Swiping frgom R->L still brings up the filmstrip view mode...but there are not pics there anymore. It doesn't seem to be linked to the gallery

---------- Post added at 07:49 AM ---------- Previous post was at 07:47 AM ----------

Contacts -> Menu -> Settings -> click "Sort List by" -> choose 'last name'.
[Verizon Samsung Galaxy S III] rhcp1253:
No changelog in goo
[Verizon Samsung Galaxy S III] WhiteAssBrent:
Same here... But I am still getting glitch flickering in both Dolphin and Chrome web browsers when scrolling pages.

Sent from my Verizon SGS3 Carbon 1.7
[Verizon Samsung Galaxy S III] glman1:
GPS doesn't work on 1.7. It hasn't worked for me since 4/25, and I don't have a Nandroid. What should I do to get working GPS?
[Verizon Samsung Galaxy S III] dg4prez:
If your GPS doesn't work, one suggestion would be to flash to touchwiz, get a GPS lock, then shut it down and install Carbon.

GPS is a problem on all the AOSP roms for the d2 family. We continue to work on it.
[Verizon Samsung Galaxy S III] glman1:
Alright, thanks for the response.

---------- Post added at 02:23 PM ---------- Previous post was at 01:40 PM ----------

One more question. So I just wipe /system, flash a TW ROM, get a GPS lock, reboot into recovery, wipe /system again, and flash Carbon? Is it necessary that I factory reset or wipe data?
[Verizon Samsung Galaxy S III] bitemeoftn:
Just wondering, and it could be totally pointless, but I'm running the I535VRBMA2 modem for d2vzw and I've had no trouble with GPS besides it taking a minute to lock once in a while. Again it could be totally pointless but it might help.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
What date is the nightly that starts after the 1.7 release?
[Verizon Samsung Galaxy S III] ckelly33:
Bluetooth doesn't seem to work for me. Anyone else?
[Verizon Samsung Galaxy S III] system6:
Bluetooth working here. 1.7
[Verizon Samsung Galaxy S III] troyzero:
Another possibilty if you are having gps problems, as crazy as this sounds, someone (I wish I had their name to give them credit) found that the screws holding the back of the phone are slightly loose and tightening helped gps lock amazingly fast. I was unconvinced until I tried it on my phone when gps refused to work for me anymore. The stud that figured this out really does deserve credit.
[Verizon Samsung Galaxy S III] ckelly33:
The Bluetooth was user error. Thanks!

GPS is very jumpy though. First time on Carbon I've had any issue at all with GPS.

As far as the solution stated above (flashing tw):

1. Do I have to do stock TW or can I flash a TW based ROM like CleanROM?

2. What type of wiping do I do after that prior to flashing in order to keep lock?

3. Is this something I have to do every time I flash a ROM update or a kernel?

Thanks!
[Verizon Samsung Galaxy S III] mindflayyer:
I'm sure Steve Kondik doesn't want to see your privates :eek:
[Verizon Samsung Galaxy S III] dg4prez:
I'm not sure of the exact procedure as i've not done it. if i had to guess, it'd be a factory reset each time.

but i really have no clue. i suggest some googling.
[Verizon Samsung Galaxy S III] ckelly33:
Any idea how to get the R->L swipe from within camera to pull up the gallery from the SD card? It used to do it as late as 4/20 nightly. Nothing I see in settings to redirect/reassociate that action with gallery.
[Verizon Samsung Galaxy S III] WettbackMartyr:
Working for me on a series of really dirty flashes :what: maybe make sure all your gallery pics are backed up to external sdcard and try a clear data on gallery??? Or a clear cache, dalvik, and fix permissions??? Just some input. Sorry if it doesn't help.
[Verizon Samsung Galaxy S III] ckelly33:
Just tried all of that. Still doesn't work right when using external storage. Only works correctly when using the internal. If I take a pic with it set to internal, it works fine. If I switch it to external SD, it only shows the pics I took when I had it set to internal. To see the external pics, I have to back out and go to gallery.

If you dont mind, check your settings. Are you set on internal or SD card?
[Verizon Samsung Galaxy S III] WettbackMartyr:
I'm set to external sd card. So I know it's working, the question is what we have to do to get it working for you? Do me a favor and check your external sd card for a folder labeled DCIM and within that folder a folder labeled Camera. If your pictures on the external sd card reside within that Camera folder then my question is answered and I'll think of something else.

EDIT: Found the bug. Take a pic or try opening gallery first so its present in your recents. Then scroll to the right from the camera and see if they appear. Hadn't tried it till now but if gallery hasn't been opened for me then camera scroll will only show a blank image instead of my pics. Is this what you're experiencing?
[Verizon Samsung Galaxy S III] ckelly33:
I have DCIM/Camera on both internal and external SD.

Pictures inside them are filed appropriately. The ones I took while the camera was labeled as internal are within the internal/DCIM/Camera and the ones I took while the setting in the camera was set to external SD reside there.

Filmstrip from within the camera app only show the internal pics even when set to external.
[Verizon Samsung Galaxy S III] WettbackMartyr:
See my edit above.
[Verizon Samsung Galaxy S III] ckelly33:
Flipping back and forth, wiping, changing to grid view....something happened and it is working now. Now sure what caused the hiccup or fixed it. Hopefully it sticks through a reboot.

Thanks for the suggestions.
[Verizon Samsung Galaxy S III] jeremytheindian:
Anyone else getting random reboots on 1.7? Only issue I've run into. I dirty flashed from 1.6.1.
[Verizon Samsung Galaxy S III] BrUhNiGGs:
Flashing tw getting a GPS lock and flashing the latest carbon nightly (5/04) fixed my GPS :) locks within 5 seconds now.
[Verizon Samsung Galaxy S III] bitemeoftn:
I would suggest doing a clean flash since 1.6.1 was on the 3.0 kernel and 1.7 is on the 3.4 kernel. That should fix it.
[Verizon Samsung Galaxy S III] tprophit:
I'm thinking getting GPS lock before flashing should be part of the procedure now. I was running April 30, got GPS lock, nandroided, flashed 1.7, latest kt747, booted up, first GPS lock took 25-30 seconds. I'm outside now, just tried GPS with Navionics, accuracy to within 6 feet.
[Verizon Samsung Galaxy S III] buffal0b1ll:
Indeed. I never reboot to recovery without locking GPS first anymore.

---------- Post added at 08:55 PM ---------- Previous post was at 08:36 PM ----------

First impressions of 1.7 after dirty flashing from 4.25 nightly

-No problems flashing or booting or installing lean kernel

-GPS works fine (I never flash a Rom without getting a GPS lock on in the current Rom anymore)

-scrolling between homescreens feels a bit slower (am I crazy?)

-flickered when long pressing on keyboard straight away (disabling hw layers fixes that)

-I miss paranoid settings from 4/25-4/27 Nightlies (now I have to Run xposed again to get per app dpi- which is fine because xposed let's you tweak more than paranoid anyway)

-Google voice voicemail in dialer still crashes (I expected this based on previous posts)
[Verizon Samsung Galaxy S III] ckelly33:
Did you flash stock tw or did you do a tw based ROM such as CleanROM? And how did you wipe in between?

Thanks

---------- Post added at 08:26 PM ---------- Previous post was at 08:21 PM ----------

I did a super clean flash to 1.7 and I've had a minor camera issue (above), slow GPS (hopefully gonna fix that soon) and 1 random reboot.

No flicker. Phone does run warm and battery life (8 hours from 100% to empty) has been significantly poorer BUT I have been at a basketball tournament all day long with poor signal which probably was more of a culprit than 1.7.
[Verizon Samsung Galaxy S III] stlcity:
Group messaging

I have one problem with 1.7. Clean flash. Stock kernel.

When I try to send group messages, it shows up as seperate messages. And when people reply instead of all of the replies showing up in the group thread, they appear as seperate individual messages from the person. With 1.6.1 this would happen atleast once daily, going into recovery and wiping cache fixed it. Now on 1.7, that does not work.

I group message my friends a lot on a daily basis. Wondering if anyone has the same experience or does anyone know any fixes? Thanks in advance.
[Verizon Samsung Galaxy S III] jeremytheindian:
Small unimportant question. What happened to the option to select a"default" or "stock" icon on the lock screen slider. Anyone know where I can get the files to do it myself under the "custom"option.

Also after clean flashing from 1.6.1 to 1.7 and using Koontz current 3.4 kernel it's alp been super smooth sailing.