yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] goldsmitht:
might explain why all of a sudden i had some serious wakelock issues and crappy to the max batter life - killed it in 6 hours (little over 1 hour screen on time) when normally it would have been at least 10. hoping nightly fixes it. AND i even tried LeanKernel, but that was even worse. down almost 20% on my ride in, and didn't even turn on screen on. Phone was in my pocket the entire time.

:eek:

:confused:
[Verizon Samsung Galaxy S III] Atamagaokashii:
Fairly certain they're free anyways. I just ran into this problem myself the other day after clean flashing.
[Verizon Samsung Galaxy S III] titanshadow:
Can anyone let me know what RIL stands for? I of course have figured out it has something to do with the modem, and power management. Is the Q in QCRIL Qualcomm?
[Verizon Samsung Galaxy S III] SubwayJrd:
RIL = Radio Interface Layer

I'm pretty sure QCRIL = QualComm Radio Interface Layer
[Verizon Samsung Galaxy S III] Relentless D:
RIL =Radio Interface Layer
[Verizon Samsung Galaxy S III] zachf714:
It's the fact of my dad didn't want me rooting my dd in the first place but I know what I am doing so he let me

---------- Post added at 06:48 PM ---------- Previous post was at 06:46 PM ----------

HAL = Hardware Abstraction Layer :) now he knows them all
[Verizon Samsung Galaxy S III] goldsmitht:
I thought HAL was the computer?

:what:
[Verizon Samsung Galaxy S III] zachf714:
Nope there are hals in android .. qcom_display is a hal
[Verizon Samsung Galaxy S III] mastamoon:
10/28 build in the OP

-- added 3 new cherrypicks for testing, see 'added 10/28' for details

-- removed a kernel pick that got merged

-- changed the debug.composition.type from gpu back to dyn(back to stock), no more animation issues.

-- repo sync at 12:30 PM EST
[Verizon Samsung Galaxy S III] xyrcncp:
How do I force the ROMdb Tool to update? It prompted me of today's update, but it didn't let me download it. The ROM link location showed, but the download button was grayed out. Last time I downloaded from it was on the 10/25 update.

I cleared data on the app and when I re-ran it, it now shows a 10/24 update.

Obviously not an issue by any means, just thought it was odd. I just downloaded the update from the OP.
[Verizon Samsung Galaxy S III] thelangosta:
I was going to post a picture of HAL 2001 for reference for you but Tapatalk fc'd instead.
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
Question for you guys. I just installed Subway Surfers on my GS3 running masta's build from today and when I open the app I just get a black screen. I'm just wondering if this should be working or if it is known to be broken because of whatever. I've got a logcat if requested and I'm working on backing up my phone so I can wipe it and see if the issue persists. Just thought I would ask before I went to all that trouble.
[Verizon Samsung Galaxy S III] byproxy:
MOG Broken

Discovered something interesting today. Took me a while to dial it into the right build, but after multiple clean installs of different versions I figured it out.

So something changed between v49 (2013-10-11) and v50 (2013-10-15) of the ROM that broke MOG. In v49, MOG can connect to the network just fine and all is well. In v50 (and all subsequent rom versions) MOG is unable to connect to the MOG network.

I didn't notice until now because I generally work in offline mode with MOG. I only noticed once I tried to login so I could download a new album.

Anyway, after some googling around, It appears as though this is a systemic problem across all CM10.2 builds released past 10/14/2013.

Any ideas as to what changed between the two builds that may have broken MOG?
[Verizon Samsung Galaxy S III] cornelious1212:
Just thought I'd give an update to my experience. I flashed 10/23 fresh in a 3G area, went to strong 4G area and the phone would not switch over. I had to toggle my network mode in mobile network settings to get it to hand off to 4G, turning off data and airplane didn't cut it. I did a full wipe the next day of 10/24 while in a 4G area and 4G showed up right away. Till today I've been dealing with poor hand offs left and right. About 5 hours ago I nandroided back to my 10.1 backup. So far I have yet to have a problem with 4G hand off. I reverted while in a 3G area(work) and as soon as I went outside, within literally 30 seconds, I was on 4G. As I see it, I'm not really sure what I'm missing on 10.2 that 10.1 doesn't have. I'm sure I'll flash a 10.2 build or two in the coming weeks, but that is just because I like flashing. Seems for my phone, 10.1 is where it's at.
[Verizon Samsung Galaxy S III] CrustyMcLovin:
Something to try: First reboot or if you don't want to reboot just make sure that you close all the currently running apps. We just need to make sure the game isn't still running in the background. Then go into the Settings -> Developer Options -> Disable HW overlays and check that option. At this point you should try to run the game and see if it works.
[Verizon Samsung Galaxy S III] mastamoon:
Exactly how long are you waiting?

Some days I leave work and have lte before I can look at my phone.. Other days I'm about a quarter mile from my company's front door before it flips.

It may take a minute or 3 for it to flip but it always does. Just give it some time. We won't see the same behavior as cm10.1, unless the upcoming 4.3 updates gives us something good. Maybe the 4.3 radio will mesh a bit better than the 4.1 we are using now. :)
[Verizon Samsung Galaxy S III] cornelious1212:
I've let it go several minutes before I toggled to get it back. Once while at my house, where I should get good 4G, I turned off WiFi and there I was sitting at 3G. I was watching football so I just let it sit till the half, and it was still on 3G. Roughly 45 minutes I'd say. I agree with you about the official 4.3 drop. I'm sure you'll work your magic with the radio.
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
Ok, I rebooted and tried it out, still a no go. Had CatLog recording while I was testing.
[Verizon Samsung Galaxy S III] mastamoon:
Have you run an official build? Mine have those signal tweaks that may interfere. I don't think they should and I've never noticed with my 10.1 builds but you never know I suppose.
[Verizon Samsung Galaxy S III] cornelious1212:
I haven't run an official build of 10.2, but I did run official 10.1's until I found your 10.1, which is what I'm running now. The 7/31 build actually which I think was your last 10.1 build. I'll give a 10.2 official a shot and see what happens. Your 10.1 runs so well that I'm hesitant. No reboots, no handoff issues, no HD video playback issues.
[Verizon Samsung Galaxy S III] krazie1:
This is been a problem for months but none of the devs seem to care to fix. Subways surfers isn't the only game that don't work, I made a thread here to try to get help but got none: http://xdaforums.com/showthread.php?t=2482472 So if you can post your logcat here maybe the dev here or anyone can try to find what the issue is. I've been really wanting to play the new subway surfers.
[Verizon Samsung Galaxy S III] Chris123NT:
You are running the latest modem/firmware right? MF1?

Also go into Mobile networks, make sure network type is set to CDMA+LTE/EVDO
[Verizon Samsung Galaxy S III] zachf714:
+(I can't make an infinity symbol) :P worked for me
[Verizon Samsung Galaxy S III] cornelious1212:
Yes on the firmware. Toggling in and out of CDMA/LTE/EVDO was the only way to get 4G back. I'd be in it, and toggling data on and off or toggling airplane wouldn't get 4G back. Only toggling to any other network setting and toggling back to the correct setting would do it.
[Verizon Samsung Galaxy S III] Chris123NT:
Wow, that's really weird. Do you remember when this issue started for you?
[Verizon Samsung Galaxy S III] fromthesticks:
Ive had this same problem too. I'd connect to lte for awhile. Then I'd have no data connection all of a sudden. Really frustrating while out..
[Verizon Samsung Galaxy S III] zachf714:
Time to do some github investigating lmfao =P

---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------

https://github.com/CyanogenMod/andr...mmit/91d9471e7b59a288f006190e3aa1530be3179590

---------- Post added at 12:01 PM ---------- Previous post was at 11:59 AM ----------

I was just able to hand up to lte :P but have had his problem
[Verizon Samsung Galaxy S III] goatman101:
MastaMoon/Chris/Zach,

Is there any way one of you can make a build with these three reverts? I am trying to get Viper4Android working on 4.3 and would like to see if this breaks anything else. Apparently it was working until these reverts were committed.

http://xdaforums.com/showthread.php?p=46328675

Any help would be greatly appreciated.
[Verizon Samsung Galaxy S III] PerCompLLC:
Been reported before in this thread... But I don't think that a solution has been offered up yet.
[Verizon Samsung Galaxy S III] zachf714:
I read on the gerrit that the cm team does not approve of breaking to fix but I think they are working on fixing it
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4949513]Chris123NT[/MENTION] I just had to toggle my network type again to get lte =P

---------- Post added at 04:12 PM ---------- Previous post was at 04:10 PM ----------

[/COLOR [MENTION=4949513]Chris123NT[/MENTION] this may be causing it https://github.com/CyanogenMod/andr...mmit/2e02c842665e2b231a9e4d7fd867ece725ccab7c

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

I'm going to do some builds later when I get home ... I'm going to revert that npe change in one .. Some signal changes for SamsungQualcommRil in another and a build with both
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah see what works for you, I'm curious as I haven't had any issues on jf, haven't tested LTE handoff on my d2 in a while.
[Verizon Samsung Galaxy S III] zachf714:
Can you test later for me
[Verizon Samsung Galaxy S III] bmeek:
Right! Alphabetically just before IBM...
[Verizon Samsung Galaxy S III] jdommer:
Now now, Everyone knows HAL actually stood for Heuristic ALogrithmic... ;)
[Verizon Samsung Galaxy S III] zachf714:
=P get pwned lmfao http://www.vernalex.com/guides/sysprep/hal.shtml
[Verizon Samsung Galaxy S III] mastamoon:
10/29 build in the OP

-- removed the 'World Phone APN' cherrypick - got merged

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] zachf714:
When did this start for you ? an exact build would help me narrow it down,I know for me it started I am guessing right after qcril was merged into cm-10.2 which makes me think there are only 2 culprits to be the cause
[Verizon Samsung Galaxy S III] mastamoon:
Note about the 10/29 build..

Looks like my Signal Strength tweaks got hosed on my build box so this build wont have them included. Not at all sure how the hell that happened, but it did. No worries though, will be back tomorrow :)
[Verizon Samsung Galaxy S III] Chris123NT:
did you do a git checkout -f on fw/b? that would hose it
[Verizon Samsung Galaxy S III] zephymobile:
Does blue tooth and treve mod tethering work for this? I have trouble with 4.3 roms
[Verizon Samsung Galaxy S III] mastamoon:
Not that but basically rm - rf'd it.. I realized what I did after seeing my LTE status bar icon was blue which I was messing with all day and then remembered I had killed that directory a few times.

Oh well.
[Verizon Samsung Galaxy S III] goldsmitht:
That explains my blue LTE.... Thought it was theme gone haywire
[Verizon Samsung Galaxy S III] mastamoon:
Yeah I was working on a mod for myself and forgot to clean up before the build. :)
[Verizon Samsung Galaxy S III] Crewski:
Anyone else unable to send picture messages on the last two builds? Mine just says sending but never goes through. It worked on the 10/27 build.
[Verizon Samsung Galaxy S III] PerCompLLC:
Mine works fine...
[Verizon Samsung Galaxy S III] johnwaco:
I have had some pictures that get stuck on sending and others that send right away. Can't seem to find a pattern for what causes it
[Verizon Samsung Galaxy S III] lostwhat83:
My pics are hit or miss too. I delete the message and try again. I do this over and over when it doesn't work. I never said anything because sometimes it just sends the picture the first time.
[Verizon Samsung Galaxy S III] zachf714:
Ohhh [MENTION=4949513]Chris123NT[/MENTION] it worked :D http://review.cyanogenmod.org/#/c/52674/

Handed up to lte immediately in an lte area
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah, invisiblek tested a bit further and his repo sync from late yesterday morning was working, but his sync from the day before was not.

Mine handed up to LTE instantly this morning without that revert.
[Verizon Samsung Galaxy S III] zachf714:
I looked and nothing would have fixed it
[Verizon Samsung Galaxy S III] Chris123NT:
He said it was still broken on dlx so I'm thinking it's those chinese TSCDMA commits, first one broke, 2nd one fixed. That's my theory at least. When was your repo sync the other night?
[Verizon Samsung Galaxy S III] zachf714:
I sync' after the last TSCDMA stuff was merged .... If it is still broke on dlx its npe because the code revert fixed it for me and the way the code is written screams I'm going to break data .... =P
[Verizon Samsung Galaxy S III] Chris123NT:
Do me a favor, run a current repo sync today without the revert and see if the issue comes back. If it does then we have hard proof to push this with.
[Verizon Samsung Galaxy S III] zachf714:
Ok , I will run one here in a few min.. Have Dan run that revert on dlx and see if it works
[Verizon Samsung Galaxy S III] cornelious1212:
It started right after the qcril merge. I'm still rocking my rock should 10.1 build, fingers crossed you guys will nail this down.
[Verizon Samsung Galaxy S III] zachf714:
What I thought
[Verizon Samsung Galaxy S III] goldsmitht:
watch the size of your pictures you are trying to send. Masta tweaks his rom to be able to send bigger pictures, but i've had a couple that would NOT go through, and when i checked, they were very large .jpg files. there is a limit to what the bandwith will support.
[Verizon Samsung Galaxy S III] Chris123NT:
Did the straight repo sync build fix it for you?
[Verizon Samsung Galaxy S III] johnwaco:
Thought size might be factor but never checked since it wasn't a big deal to me. I'll check if it happens again.
[Verizon Samsung Galaxy S III] mastamoon:
I'm still running my 8-02 build and things are fine. Screen is a Lil slow to turn on sometimes but really that's it. Battery life is fine, on par with the last builds of 10.1 really. I got about 1hr screen on time with 20% battery loss which is right on with 10.1
[Verizon Samsung Galaxy S III] damnyouwaffles:
Yup. Still on your build with same results. Good job masta.
[Verizon Samsung Galaxy S III] Chris123NT:
yeah the new builds are screwed up because of the jb_2.6 stuff invisiblek merged in, and he won't believe us when we tell him it's a problem.

SU doesn't work (unless you use chainfire's SU apparently) and the phone does not go to sleep, definitely just confirmed that one.
[Verizon Samsung Galaxy S III] mastamoon:
I think 4.3 doesn't like to be crack flashed. Probably more background optimization than previous versions to speed things up eventually but might take a day to fully settle and that's when most of us flash another build.
[Verizon Samsung Galaxy S III] damnyouwaffles:
That's kinda what I'm thinking. It seems every problem I had disappeared within 24 hours of using the ROM.
[Verizon Samsung Galaxy S III] thevillageidiot:
Invisible I has 8/4 out now. Currently downloading. Will test and report
[Verizon Samsung Galaxy S III] zachf714:
It's the SELinux cherry picks on the gerrit, the jb_2.6 kernel commits don't seem to be causing me a problem
[Verizon Samsung Galaxy S III] goldsmitht:
What governor is everyone using? Defaults to interactive, but had been using ondemand till saw battery life was tanking.

So what's the consensus? Or is everyone using a third party kernel?
[Verizon Samsung Galaxy S III] thevillageidiot:
WiFi works. BT seems to work. Root also seems to be fixed.
[Verizon Samsung Galaxy S III] mastamoon:
Default for both.
[Verizon Samsung Galaxy S III] NedDasty:
Thanks thevillageidiot--any word on the screen on delay? I've noticed that if I hit the power button again before the screen goes on, it just...never goes on, and I have to battery pull. Happened about 4x last night.
[Verizon Samsung Galaxy S III] Chris123NT:
I'm not cherry picking SELinux. If you don't think it's a problem try something that requires root, or load up terminal emulator and see what happens. Also grab CPU spy and see if the phone is deep sleeping or not.
[Verizon Samsung Galaxy S III] tom108:
I am using powersave. Battery is great and have seen no other issues. I had 1 random reboot within the first 8 hours on the 8/2 build, after that it has been smooth as butter.

-Tom
[Verizon Samsung Galaxy S III] thevillageidiot:
Screen delay still seems hit and miss. After 8/3 settled in it got better. I'm assuming it will be the same for 8/4 as well. Haven't had a huge delay in screen lock/ screen on that 8/2 and before had though so it seems to be getting better.
[Verizon Samsung Galaxy S III] zachf714:
I still have root and get deep sleep, I also cherry picked these http://review.cyanogenmod.org/#/c/46949/

http://review.cyanogenmod.org/#/c/46950/
[Verizon Samsung Galaxy S III] Chris123NT:
Well then I give up, any of my builds with his kernel OR his build from today do NOT work. Wifi doesn't connect, no root, phone won't sleep, nothing.
[Verizon Samsung Galaxy S III] herooftimeloz:
Are there any third party kernels compatible with CM 10.2?
[Verizon Samsung Galaxy S III] ace000724:
Anyone else getting crazy reboots when using the camera on today's build?
[Verizon Samsung Galaxy S III] coldconfession13:
8/4 invisiblek build still no root and Bluetooth still doesn't work. Might just downgrade back to 10.1
[Verizon Samsung Galaxy S III] ace000724:
Not sure why root is not working for you , i had to install SuperSu through cwm it wouldn't install under the normal option.
[Verizon Samsung Galaxy S III] sivarticus85:
Ever since flashing the 10/29 build I've completely lost LTE. Toggling doesn't bring it back, and even flashing a TW rom doesn't bring it back either. I've checked the mobile settings and LTE is on, but it won't connect. It stays on 3G the whole time. I've also started having issues with bad reception no matter where I am. People are saying they can't hear me because of static on the line. Bad sim maybe? Coincidence? Any thoughts?
[Verizon Samsung Galaxy S III] mastamoon:
If going back to stock doesnt fix, there is something wrong with your phone/sim...

Did you just flash a stock based rom or do a full odin back to stock then reunlock, etc..?

Before bringing your phone back or whatever, I would try a full odin back to stock and see what happens.
[Verizon Samsung Galaxy S III] sivarticus85:
I just flashed a stck rom, I haven't tried ODIN-ing back to stock yet. I'll try that next and see what happens.
[Verizon Samsung Galaxy S III] zachf714:
Couldn't ssh into my box =( will try when I get home

---------- Post added at 07:00 PM ---------- Previous post was at 06:59 PM ----------

Change network modes... Masta Chris it's still here
[Verizon Samsung Galaxy S III] Chris123NT:
Huh?
[Verizon Samsung Galaxy S III] zachf714:
Somebody lost their lte when they flashed 29th .. I said to change network modes but I also said that the bug is still in here it seems

---------- Post added at 07:09 PM ---------- Previous post was at 07:08 PM ----------

And I am at school and forgot my box is off so I can't ssh into it, to build
[Verizon Samsung Galaxy S III] Chris123NT:
Try this then

http://download.cyanogenmod.org/get/jenkins/45953/cm-10.2-20131030-NIGHTLY-d2vzw.zip

Official for today, will be a easy test without you having to build
[Verizon Samsung Galaxy S III] sivarticus85:
Tried that... Didn't work for me. It's ok, I'll mess with it when I get home.

Edit: Aren't we on PRL 15154 or something like that? Mine's showing as 53243...
[Verizon Samsung Galaxy S III] zachf714:
I'm home now

---------- Post added at 07:57 PM ---------- Previous post was at 07:47 PM ----------

@Chris123NT if it is fixed today I wonder if it was the apnlist merge late yesterday
[Verizon Samsung Galaxy S III] mastamoon:
10/30 build in the OP

-- blue LTE data icon in yesterdays build should be fixed.

-- repo sync @ 3PM EST
[Verizon Samsung Galaxy S III] Stealth111:
Anyone noticing any issue with standard text messaging using stock app? Over the past week it seems like I am getting people who are not getting my texts. It says they have sent, but they did not indeed receive them. Today I sent someone 4 different texts while in the same room as me, sitting across the table, and they got the first one, but none of the other 3... AND, I had a NO DATA situation later this afternoon in a good LTE area, I had no data, airplane mode didn't fix, had to toggle data off then on to bring back, but this was on last nights official..
[Verizon Samsung Galaxy S III] woolbeo:
I have been having problems with the popup message window sending texts to the wrong person.
[Verizon Samsung Galaxy S III] Chris123NT:
Your PRL definitely isn't right. Mine right now is 15256, but this is on an S4, the version on the S3 might be different, but 53243 is definitely wrong.
[Verizon Samsung Galaxy S III] dmginc:
Yeah my S3 is on PRL 15256.
[Verizon Samsung Galaxy S III] sivarticus85:
Yeah I knew it... How do you fix that? Would ODIN-ing to stock fix the PRL too? I've been swapping my sim a lot between my Gnex and my S3 recently, so I wonder if maybe something got screwed up?
[Verizon Samsung Galaxy S III] Mixinitup4Christ:
I don't know if you are using Voice+, after flashing the build that needed the RIL DB deleted my messaging through Voice+ was all screwed up. I didn't test my carrier to see how that was doing. I did a full wipe this morning and flashed 10/29, and it seems to be performing a lot better!
[Verizon Samsung Galaxy S III] Chris123NT:
Not sure an ODIN to stock would fix that, you might just have a hosed SIM at this point.
[Verizon Samsung Galaxy S III] zachf714:
Same here

---------- Post added at 02:39 AM ---------- Previous post was at 02:38 AM ----------

I bet the gnex f*cked it up .. Ya know changing so much is constantly reprogramming the sim
[Verizon Samsung Galaxy S III] gr33nd3vil:
Don't feel bad whatever changed after 10/20 broke WiFi to 3g but WiFi to 4g works fine
[Verizon Samsung Galaxy S III] Chris123NT:
I just tested wifi to 3g, works fine. Can you post a log of the failure?
[Verizon Samsung Galaxy S III] gr33nd3vil:
Sorry meant on my gs4 cm10.2
[Verizon Samsung Galaxy S III] Chris123NT:
Weird, works fine on my gs4 as well :eek:
[Verizon Samsung Galaxy S III] gr33nd3vil:
I'm on us cellular was in the wrong forum
[Verizon Samsung Galaxy S III] funnyperson1:
So I've been having issues with audio after a while on the 10/28 build. I seem to lose audio notifications and alarms and I need to start playing music over speaker on Pandora then plug in headphones to hear it. Otherwise it just plays silently.

I just set lpa.decode=false in build.prop and will see if that fixes it.
[Verizon Samsung Galaxy S III] zachf714:
[MENTION=4949513]Chris123NT[/MENTION] LTE handups work now :D I wonder if it was fixed by the telephony.mk and was originally broken by enabling global mode