yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] mastamoon:
Should roll back to before the 4.3 merge and test, not sure if it will be full functional though. I won't be back at work till Tuesday.
[Verizon Samsung Galaxy S III] Zacharybinx34:
The ribbon is good but for one thing... it should be able to fit 6 and not 5 and 1/2.... that's the only thing that I hate about it. What's the point of this?
[Verizon Samsung Galaxy S III] PerCompLLC:
It would also be nice if it were centered like power widgets... So if you only have a couple of items it wouldn't look all effed up. Just a nice to have though. :cyclops:
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Nexus 4 yes but not the Gnex
[Verizon Samsung Galaxy S III] airmaxx23:
Do we have to wipe data when going back to 10.1 or can it just be installed over 10.2?
[Verizon Samsung Galaxy S III] khymbote:
I know for me going 3g to 4gLTE didn't work. I would either have to try to cycle a few times and if that didn't work I would have to reboot to get data back. It could be the 4.3 RIL when this all started but data acts a little different phone to phone even when they are technically the same phone.

**edit I do know that the Nexus 4 group has been having data issues and Google is sending out an update here soon to fix it. From a post I had read they didn't think it affected anyone that wasn't a Nexus 4.**
[Verizon Samsung Galaxy S III] mcdevil58:
I sometimes get redraw and lag on the trebuchet launcher. Is this normal for that launcher. I usually use nova so I'm not sure.
[Verizon Samsung Galaxy S III] BrianAllred:
Bluetooth seems to turn off sometimes, and at other times it doesn't want to. On the latest right now. Going to flash 8/27 to see what happens.

Edit: or whichever build was the one before the Bluetooth cherry pick.
[Verizon Samsung Galaxy S III] :
Is it just me, or is the uninstall feature from the home screen on trebuchet no longer supported?

Also is there any way to keep the ringer and notifications on silent when plugging in a headset?
[Verizon Samsung Galaxy S III] khymbote:
I use the Aviate Launcher but I had an alpha invite for it. Other than that I have used Nova Launcher and loved that. There could be a lag from a possible memory leak that has been mentioned in here and I think they fixed it but not 100% sure. Chris and Masta could answer that.
[Verizon Samsung Galaxy S III] mastamoon:
These data issues are happening on official builds also?
[Verizon Samsung Galaxy S III] airmaxx23:
I keep losing data and getting stuck with LTE having 1 bar and no actual service when I should be kicking back to 3G. On my way to work I go through an area that has some LTE and some 3G, whenever I get a weak (1 bar) LTE signal I have no service when it should be switching back to 3G. I start in a 3G area then go to LTE, back to 3G, then LTE then 3G when I reach work.

I'm back on 10.1.3 for now but will be watching to see if/when the data issue gets fixed, I lost data and had to reboot 6 times yesterday.
[Verizon Samsung Galaxy S III] Chris123NT:
WTF, I flashed yesterday's build, got the nasty SystemUpdate wakelock everyone is talking about, flashed back to my previous build, won't go away. I might have to clean flash because of this, ughhhhh lol.
[Verizon Samsung Galaxy S III] mastamoon:
I haven't seen that bug either.
[Verizon Samsung Galaxy S III] Chris123NT:
Was wondering if maybe it was CM Account doing it.
[Verizon Samsung Galaxy S III] BrianAllred:
Yeah, between the wake lock and the persistent BT problems even after flashing the latest build, I'm probably clean flashing as well. My ZeroLemon battery went from carrying me around 3.25 days to 10% to only having 15% after 2 days. This on top of BT having mood swings about turning off.
[Verizon Samsung Galaxy S III] mastamoon:
There is some Google update commits on gerrit probably to squash this. Idk
[Verizon Samsung Galaxy S III] Chris123NT:
It's really starting to frustrate the hell out of me because it's seeming like there's no effort on the part of the device maintainers to fix the data issues etc... and now a new bug crops up because they must test **** with blinders on.

At least masta puts the effort into trying to clean up their mess lol.
[Verizon Samsung Galaxy S III] airmaxx23:
Is there a "higher up" who can maybe help get things rolling?
[Verizon Samsung Galaxy S III] guywmustang:
I tried wiping system and that didn't help... I really don't want to clean flash... It's such a pain.
[Verizon Samsung Galaxy S III] goldsmitht:
getting to the point where Chris and Masta are the only "Higher Ups" i'm trusting with my phone. Realize these are built off CM base, however, Masta tweaks them to the point they just plain WORK!

:highfive:

:victory:
[Verizon Samsung Galaxy S III] khymbote:
Yes. I believe I read it on android police website. http://www.androidpolice.com/2013/08/26/bug-watch-android-4-3-radio-bugs-causing-cell-connection-drops-on-some-nexus-4-handsets-fixes-in-sight/

---------- Post added at 01:34 PM ---------- Previous post was at 01:32 PM ----------

I'm hoping I don't see it either. **knocks on wood**
[Verizon Samsung Galaxy S III] locozildjiangodx:
I'm not sure if there is a fix yet, but I am still getting app crashes (DARN YOU CANDY CRUSH!!!) on 8/28 masta build
[Verizon Samsung Galaxy S III] dpaine88:
I'm on 8/23 and it's working pretty good for me, no data issues.
[Verizon Samsung Galaxy S III] khymbote:
Now I have the Google Services Bug.

**Edit I am on Chris's last build**
[Verizon Samsung Galaxy S III] johnwaco:
I shut off Google location services and rebooted and so far it has fixed my issue with Google services.
[Verizon Samsung Galaxy S III] khymbote:
as it doesn't take me long to back up and restore my phone I just did a full factory wipe and install of Chris's build. Hoping there was something in data that kept causing problems.

**Have to love it when your backup that you just created comes back as invalid and I cant restore. Now I have to download all my apps.**
[Verizon Samsung Galaxy S III] Chris123NT:
Did the clean flash fix it for you?

Here's the fix, I'll cook a build with this tonight, this bug is freakin killing me:

http://review.cyanogenmod.org/#/c/49329/
[Verizon Samsung Galaxy S III] khymbote:
I am still downloading and setting up my phone. I will reboot after that and watch what happens over the next hour or so. I will post asap if its still happening.
[Verizon Samsung Galaxy S III] zachf714:
http://review.cyanogenmod.org/#/c/49339/
[Verizon Samsung Galaxy S III] guywmustang:
This didn't work for me... :(
[Verizon Samsung Galaxy S III] Zacharybinx34:
Does anyone even have a clue why the battery life is so terrible on this?
[Verizon Samsung Galaxy S III] BrianAllred:
Last page or so suggests that it has to do with either CyanogenMod Account or Google Location Services.
[Verizon Samsung Galaxy S III] khymbote:
Trying to figure that out. There appear to be some services that are running even when you haven't started them. I did a factory wipe and fresh install. I'm trying figure out if its a data thing.
[Verizon Samsung Galaxy S III] don_xvi:
I thought I read on someone's Google+ that you can't just re-flash to go back, but didn't see it in the official CM postings. I'd definitely make a backup.
[Verizon Samsung Galaxy S III] iofthestorm:
Did invisiblek abandon us for the GS4? So we're left with noobnl as our maintainer?
[Verizon Samsung Galaxy S III] Chris123NT:
Invisiblek has been messing around with the droid dna as of late.
[Verizon Samsung Galaxy S III] khymbote:
This is after an hour of only listening to some music. This is my factory wipe and install of Chris's last build.
[Verizon Samsung Galaxy S III] zachf714:
OH SH*T POSSIBLE RIL FIX, will make a test build of carbon ( dont have cm source on my pc at the moment) asap
[Verizon Samsung Galaxy S III] shadrach47:
I had trouble trying to build with it cherry picked. Going to try it again and see if it will compile.
[Verizon Samsung Galaxy S III] BrianAllred:
Is RIL in the kernel? I just ask because I'm on BMS kernel and I don't think I've been having the data issues others have been having, and yes, I go through dead spots a few times a day. Granted, I usually have Wi-Fi, but anytime I've needed data, it's been there.
[Verizon Samsung Galaxy S III] zachf714:
didnt have any problems, carbon uses cm ril
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah just saw a couple of commits that look promising, building now
[Verizon Samsung Galaxy S III] zachf714:
nope ril is a lib like say webcore
[Verizon Samsung Galaxy S III] shadrach47:
Yea, seems to be okay now.
[Verizon Samsung Galaxy S III] zachf714:
built with these, about to flash ( yes carbon its what I have on my pc at the moment but they use cm opt telephony and ril )

cd ~/CarbonRom/frameworks/opt/telephony || exit 1

git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_opt_telephony refs/changes/42/49342/1 && git cherry-pick FETCH_HEAD

git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_opt_telephony refs/changes/73/48873/3 && git cherry-pick FETCH_HEAD

git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_opt_telephony refs/changes/46/49346/2 && git cherry-pick FETCH_HEAD

cd ~/CarbonRom/hardware/ril || exit 1

git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_ril refs/changes/58/46458/2 && git cherry-pick FETCH_HEAD

this breaks compile for the moment http://review.cyanogenmod.org/#/c/48875/
[Verizon Samsung Galaxy S III] Chris123NT:
Here's a build for today, repo sync around an hour ago from this posting using aeroevan's kernel which already has standalone power collapse enabled.

Cherry-Picks:

KeyguardViewMediator: Play lock screen sound sooner - http://review.cyanogenmod.org/#/c/46894/

Framework: Development setting to enable navbar (1 of 2) - http://review.cyanogenmod.org/#/c/46928/

Settings: Development setting to enable navbar (2 of 2) - http://review.cyanogenmod.org/#/c/46927/

PhoneProxy: Update IccCardProxy only when cdma voice tech changes. - http://review.cyanogenmod.org/#/c/49346/

Reverts:

audio-caf to get dock audio working again

That's pretty much it, purpose of this build is to see if the new telephony merges plus the cherry-pick fix the data hand-off issues.

Also test apps and see if that bug is still there

http://chris123nt.com/CM/cm-10.2-20130829-UNOFFICIAL-d2vzw.zip

Oh and that nasty wakelock from masta's build yesterday is fixed.
[Verizon Samsung Galaxy S III] khymbote:
From my rebuild and Chris's build from the other day I factory format and install and my batter is doing very well. No extra services running.
[Verizon Samsung Galaxy S III] TwistingSoul:
So, I'm on Masta's 8/28 build with stock kernel, and was playing CandyCrush a few minutes ago, when it crashed.

I installed Logcat Extreme about a week or so ago, and decided to take take a log of the game crash, which is below:

https://drive.google.com/uc?id=0B9ZgYFUQzv8KVkc5aTRKTVlzWkU&export=download

I don't even know if I did this right, as I had searched for the game name, and saved that information.

If you can't access the url above, I'll get on GDrive from a computer to change the sharing rights.

Is there anything in these logs that would show you why it crashed after only a few minutes?
[Verizon Samsung Galaxy S III] Wh1t3Rose:
Yea u need to change the share rights
[Verizon Samsung Galaxy S III] TwistingSoul:
I figured as much. Wish the sharing rights could be changed from the phone to be publicly visible. Ah well. Back in a 'mo.
[Verizon Samsung Galaxy S III] minnysota:
How's this been running? Interested to see how RIL is performing. Also - how is audio? Everything cool with BT?
[Verizon Samsung Galaxy S III] Reborn627:
In my experience everybody's setup is a little different and can play a part in the overall functionality of the ROM. The best thing for you would be to install the ROM and see how it works on your device. Masta and Chris have the most stable gs3 ROMs that I've experienced so you'll have that going for you. I know it may not be the answer your looking for but it's the best I can give. For me it runs great with very few problems. Others may have different experiences so installing it would be your best bet if you want to know how it runs.

Peace,

Ray
[Verizon Samsung Galaxy S III] TwistingSoul:
I stopped being a lazy git, fired up my computer, and have attached the file to this post in .txt format. :silly:
[Verizon Samsung Galaxy S III] minnysota:
Thanks for the reply. I was just wondering how Chris's build from tonight is running. I've been on Masta's 8/20 for a while and there's no huge problems. BT doesn't shut off at times, and there's the occasional hiccup, but no real complaints. I was just seeing if the recent RIL merges/picks had any positive effect. Thoughts out there?
[Verizon Samsung Galaxy S III] Reborn627:
So "Deep Sleep" should return with a clean install? Ugh, well, ya gotta do whatcha gotta do. Thanks for the info.

Peace,

Ray

---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------

Too early to tell on the RIL thing. Having a battery issue but it seems a clean install will correct that. That's my experience after installing at 11pm.

Ray
[Verizon Samsung Galaxy S III] PerCompLLC:
I guess if you are having deep sleep issues... I dirty flashed the latest unofficial from this thread (Chris123NT) and my device is deep sleeping fine. Using CPU Spy and Better Battery Stats to monitor.
[Verizon Samsung Galaxy S III] Chris123NT:
Wakelock is definitely fixed on my build, my RIL issue still seems to be present (handoff to LTE but no data connection after going through 1X area), but the commits don't seem to have made anything worse.
[Verizon Samsung Galaxy S III] sbenson1226:
Clean installs are always best practice but I dirty flashed Chris's build from Mastas 8/28 and it completely fixed my deep sleep issues. Try that first.
[Verizon Samsung Galaxy S III] khymbote:
Chris, I was at my gf last night and her place is in a 1x area and I had no data issue.
[Verizon Samsung Galaxy S III] Chris123NT:
So it switched back to LTE without issue when you went to an LTE area?
[Verizon Samsung Galaxy S III] khymbote:
Yes, Her house is a dead spot. I get 1x when I'm in there. About a mile down the road I get back on LTE. I had no issue getting on Chrome or FB to show me latest updates.
[Verizon Samsung Galaxy S III] Chris123NT:
Interesting, guess I'll have to try and isolate the issue even more.
[Verizon Samsung Galaxy S III] Reborn627:
Hmm, I dirty flashed Chris' from last night, over the 28th build, and I seem to have lost deep sleep. I'd blame it on the kernel that I use but I made sure I was on stock overnight. Not sure what the issue is. I'll factory wipe this morning and see what I come up with. On the positive side hand offs seemed to work fine this morning on my way to work. However, I'm not sure if I passed through a 1x area. I'll keep an eye on it today.

Peace,

Ray
[Verizon Samsung Galaxy S III] goldsmitht:
has anyone thought that maybe the difference everyone is having has to do with the hardware? I know (think?) there are different radios from those of us who bought the S3 when it first came out, and those who got it later. Samsung had some issues with their radios (even more so then than now) with the first batch, and if i am not mistaken, i was talking to a VZW rep and they said they would issue a new phone to me cuz of my reception issues. she said there were "differences", but not sure i always trust VZW

just a thought, but maybe something there

:confused:
[Verizon Samsung Galaxy S III] BrianAllred:
I got mine in November and haven't had any data issues. I don't know if that means anything.
[Verizon Samsung Galaxy S III] goldsmitht:
See... i got mine first batch, ordered one of the first ones when they came out. A lot of issues with radios that Samsung had to fix.

i have some issues with reception, and i have had the odd here and there data drops, but nothing really bad. Although when i was talking with VZW Tech, i actually had the phone call drop out 3 times! Nothing like putting the point across. Thats when they said they would replace, but i'm not certain i want to go through th hassle of stocking out mine clearing off the SDCARD and then re-rooting and unlocking a new one.

:confused:
[Verizon Samsung Galaxy S III] mcdevil58:
Yea i got my my first GSIII in november and i had horrible reception issues. I went back to the store and they Just gave me a new phone. Its had few problems since then.
[Verizon Samsung Galaxy S III] bluezr1:
Where do I find the superuser app? It keeps granting OS Monitor access after a reboot until I go into the app and toggle off and then on show CPU usage. I can't find it in the app drawer or in the play store.

This started happening with mast 8-28 build. And then after having poor battery life (from Goole services) I flashed Chris's latest build over the top (as some have said that they had good results) and the problem is still persistent.

Edit: I forgot to mention that the previous build that I was on prior to 8-28 was 8-07, and have been running them with the stock kernels and no other mods.
[Verizon Samsung Galaxy S III] goldsmitht:
system settings >SuperUser (all the way at the bottom above about phone)

:cyclops:
[Verizon Samsung Galaxy S III] bluezr1:
Now I really feel like a fool. Lol

Thanks bud
[Verizon Samsung Galaxy S III] bluezr1:
Would you have any idea why it keeps granting permission? The thing is that after putting in a fresh battery I'll always look at my CPU usage before doing anything, and now I'm forced to open OS monitor instead of usually waiting until my phone settles down. Do you think that it would be a good idea to try out a different superuser app (like SuperSu), considering the current one is baked into the rom?

This is just the beginning of a very long list.
[Verizon Samsung Galaxy S III] khymbote:
The first batch of phones was horrible for hardware. I am on my 5th phone for various hardware issues. First phone gps went out. 2nd data died, third data issue and they as in Verizon store dropped and phone went smash, 4th gps again and now my 5th.
[Verizon Samsung Galaxy S III] Wingdom:
Is there a way to add hotboot to the restart menu? Every other phone I've used has either had a 4 way reboot flashable option, or an option in the settings menu, but I cant find either for the S3. Am I missing something, or does it not exist?
[Verizon Samsung Galaxy S III] Hybridnoob:
It's in developer options and called advanced reboot. Tap build number 7 times to enable developer options.
[Verizon Samsung Galaxy S III] goldsmitht:
that one the smarter people are going to have to answer. I do know that mine grants every time i reboot, but that is the extent of what i know about that.

sorry
[Verizon Samsung Galaxy S III] Relentless D:
2 things...first are you on CM 10.2? That looks like a TW rom in the screens.

2nd (assuming you are on CM10.2) I've had issues on a few 4.3 roms (PAC, PA, CM10.2, Slim) where the super user app would grant permission but the app wouldn't actually have them. on GMD gesture control it would just spin on checking for root access while the logs for superuser were filling up with granted permissions for that app every few seconds. I found that the resolution was to install supersu off the play store. That seemed to fix it.

Strange problem because it was working fine for a long time.
[Verizon Samsung Galaxy S III] zachf714:
There is a TW theme chooser theme, I have it
[Verizon Samsung Galaxy S III] Wingdom:
Yeah, you get Reboot, Recovery, Download for reboot options. Is there a way to enable hotboot as well? Would be nice to not have to wait for the whole phone to restart when something goes wrong, or even if its just running a little slow.
[Verizon Samsung Galaxy S III] alershka:
I may be wrong but I thought the fast reboot caused issues in jellybean with the corruption scanning added in. It doesn't impact the fast boot but if you do a subsequent normal boot, it kicks off a scan and makes that reboot take much longer.
[Verizon Samsung Galaxy S III] guywmustang:
I went to cm 10.1.3 to try and get rid of the SystemUpdateService wakelock but it was still there.

After killing things I found that force stopping Google Services Framework stopped my wakelock issue.

For anyone else with the SystemUpdateService wakelock problem... Try killing gsf
[Verizon Samsung Galaxy S III] bluezr1:
I'm running a theme from the play store.

https://play.google.com/store/apps/details?id=com.thomassafca.theme.touchwiz

Thanks for the reply, I'll try out SuperSu. I didn't want to try it because I wasn't sure if it would mess anything up. Now that I know I'll give it a shot.

Thanks,

Edit: That did the trick. :)

Thanks a lot bud. And everyone else on the post, especially mast and Chris at making sure that all of the right pieces of code are put together creating an incredible rom.
[Verizon Samsung Galaxy S III] Wingdom:
That is entirely possible, but this is the first I have heard of it. I went looking for a 4 way reboot mod for other devices with 4.3, and didn't see it for anything else. I did however see it for 4.2, so if a problem like this exists, its only in 4.3 jellybean.
[Verizon Samsung Galaxy S III] devo1929:
sending text from mightytext

I just encountered a small issue that seems to be 10.2 related. I use an app called mightytext to be able to send text messages from my PC. One thing I've noticed is that I can't seem to use it to send text message over about 30-40 characters. At first, I thought it was a mightytext issue, but it appears to be a 10.2 issue (telephony specifically). I've recently reverted to the 7-31 build of masta's unofficial 10.1 and everything seems to work no problem now.

Attached are two logcats taken from 10.2. One is the failure and the other a successfully sent message. You can see the content of each message in each logcat.

This isn't really a huge issue at all as I don't use the app that often. I just wanted to point it out in case it causes any further issues down the road.
[Verizon Samsung Galaxy S III] mikejr83:
I can confirm the data issue reproduction as Chris described it.

Was in the doctor's office where I'll loose signal. When walking outside to my car I should be back in LTE. It showed a bar or two but I had no data. Toggling airplane mode got data back.

First time I've had this problem. Seems like my 3g to LTE handoffs are fine though.
[Verizon Samsung Galaxy S III] BrianAllred:
I've only noticed the issue on SMS over 160 characters. I reported the issue to MightyText, they asked if I was on a custom ROM, I said CM10.2, and they haven't responded, even with follow up emails. While I understand it can be a ROM issue, I don't appreciate my concern going ignored.
[Verizon Samsung Galaxy S III] kentedman:
Wow. I've been hitting my head against the wall trying to figure out why some of my mightytexts don't send. Never occurred to me its just the long ones. (that's what she said).

I'm running slimbean 4.3 and having the same issue so I guess its not rom related.

Thanks for the heads up.
[Verizon Samsung Galaxy S III] BrianAllred:
No problem. I just type until the character limit says 340 (for those that don't use MightyText, it starts at 500), hit enter, and keep typing. It's become pretty automatic. This is only for when my tablet isn't around and I can't use TabletTalk, of course.
[Verizon Samsung Galaxy S III] zachf714:
Happened once at school today but surprisingly only once . I go in between 3 campuses and the main has horrible service and only lost data once there
[Verizon Samsung Galaxy S III] zachf714:
CDMA heartburn ... Lies not fixed on d2vzw
[Verizon Samsung Galaxy S III] Amaze209:
Is there a build today?

Sent From A Flashaholic's S3
[Verizon Samsung Galaxy S III] zachf714:
If I remember right masta doesn't get back until Tuesday
[Verizon Samsung Galaxy S III] airmaxx23:
Have you tried the newest nightly?
[Verizon Samsung Galaxy S III] zachf714:
Use the same picks and some different ones to compile for myself
[Verizon Samsung Galaxy S III] Amaze209:
Zach do you release builds like chris and masta? And did chris release an 8/29?

Sent From A Flashaholic's S3
[Verizon Samsung Galaxy S III] Chris123NT:
I didn't build yesterday, I'll more than likely build today.