yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] juancaperez2000:
Based on the way that use to do it with my evo you shoul just wipe cache an dalvic then flash the kernel
[Verizon Samsung Galaxy S III] Hurleyzero1:
Thanks to this kernel im running CM10 again. Thanks alot for this post.
[Verizon Samsung Galaxy S III] Mean Sixteen:
Glad I could help someone.
[Verizon Samsung Galaxy S III] juancaperez2000:
i want to report that my MMS is not working either wifi or 4g, somebody else having this issue
[Verizon Samsung Galaxy S III] Mean Sixteen:
You're welcome.

IMO is my favorite kernel dev. Can't wait to see how well he will make this thing run.
[Verizon Samsung Galaxy S III] Hurleyzero1:
I have horrible service here at my house and can rarly send out mms or receive. I was able to receive a mms but not able to send.
[Verizon Samsung Galaxy S III] juancaperez2000:
Built 24: no light on soft keys, mms not working
[Verizon Samsung Galaxy S III] Hurleyzero1:
Is anyone else having phone take up so much battery? is there anyway to fix?

Edit: This came from a full charge with light use. Very fast but horrible battery life so far.
[Verizon Samsung Galaxy S III] matt0715:
I was asking if cyanogenmod is working on making the official version, I understand that this is working but it's not the official version. Sorry for the confusion.
[Verizon Samsung Galaxy S III] salas2324:
I dnt think there's going to be any official aosp ROMS till the bootloader is unlocked

Sent from my Verizon Samsung Galaxy S3 4G LTE
[Verizon Samsung Galaxy S III] Hurleyzero1:
think i found the cure to you no light on soft keys issue. it might just be me and note i am also on build 24, i went into settings/display/notification light and turned notification light on and then back off and now the soft key lights are on. the weird thing is now they dont turn off unless the screen is off. i havnt tried a reboot yet.
[Verizon Samsung Galaxy S III] EGill42:
Dhackker29 has new build for 7/26 posted through his twitter. Just google dhacker29, and it come up.
[Verizon Samsung Galaxy S III] Randominator:
I installed this and had no problems with voice, 3g, or 4g, but I was unable to authenticate with an app which validated my phone number and MEID.

Looking in phone status, it showed that my MEID was some hex string that didn't seem to match up with my IMEI at all. After looking around and flashing back to stock, it became apparent that the MEID is supposed to be the IMEI minus the last digit, and thus all decimal digits. Because my MEID is fine in stock and all data/voice work, I'm under the impression that the MEID is somewhat generated in software from the IMEI. (Please correct me if that's not the case)

I started playing around with the Phone Info app to see what would happen if my phone activated with a different method.

If my phone starts up in LTE/GSM/CDMA mode, it recognizes the correct PRL and phone number.

If my phone starts up in LTE/CDMA mode, it recognizes the correct PRL and MEID, but with an unknown phone number.

If my phone starts up in GSM or WCDMA mode, it seems to crash the phone app constantly or break voice/data entirely. I had to wipe data after doing this.

Unfortunately, it seems like I'm unable to get both my phone number and my MEID to report correctly at the same time, but the IMEI is unaffected by these settings and voice and data work for both LTE/GSM/CDMA and LTE/CDMA. This leads me to believe that the phone number is read from the SIM card (requiring GSM) and the MEID is generated in one of two manners to reflect the current radio mode. Hopefully this means that it shouldn't be too difficult to fix the phone number appearing problem or the incorrect MEID problem.

I would have posted this in the dev thread, but I don't post on forums much and thus am not allowed yet.
[Verizon Samsung Galaxy S III] juancaperez2000:
Did you backup your IMEI before to start to play
[Verizon Samsung Galaxy S III] neyenlives:
So I've been noticing this build is always immediately following other CM10 builds.
[Verizon Samsung Galaxy S III] invisiblek:
Correct
[Verizon Samsung Galaxy S III] asenduk:
On the 8/28 build and having music randomly skipping with Apollo player. Other than that, its butter!!!

I did dirty flash though, so I'm gonna try a wipe later
[Verizon Samsung Galaxy S III] aqhilles:
I had the same issue over the weekend when I flashed the official cm10 8/24. I was using a different player. I also had an error on DSP ("profile could not be loaded" or something like that.) I flashed the unofficial 8/26 (dirty flash) and everything was back to normal.
[Verizon Samsung Galaxy S III] milan03:
I'm trying to find the ServiceMode.apk but not sure where. Any ideas?
[Verizon Samsung Galaxy S III] invisiblek:
doesn't work as it is but you might be able to modify it

i'm not really sure if it relies on any touchwiz frameworks, it probably does

its attached
[Verizon Samsung Galaxy S III] asenduk:
I see a new build... flashing now

:)
[Verizon Samsung Galaxy S III] Coderedpl:
I'm curious about the screen flicker and random hard reboot. I haven't seen too much talk about it in the past few days so i'm assuming its not really an issue anymore?

Looking to flash back to CM10
[Verizon Samsung Galaxy S III] mandie7312:
Wont Install

Every time i try to install this rom and the gapps it says error for some reason but when i try to installa touchwiz rom it works. please help :(
[Verizon Samsung Galaxy S III] invisiblek:
probably because of the assert

update your clockworkmod to 6.0.1.2 then try again
[Verizon Samsung Galaxy S III] milan03:
Not exactly sure what and how to modify. Any tips?
[Verizon Samsung Galaxy S III] WhammyDroid:
All, I loaded up the 8/26 nightly and am happy with it so far. One thing I am noticing is that I cannot view the log files via alogcat. Nothing appears in the application. I've also tried running the "fix permissions" in Rom Manager. Still no luck. Thoughts?

Also, this nightly is not remember applications defaults. Is anyone else experiencing this?
[Verizon Samsung Galaxy S III] milan03:
08/28 fixes pretty much everything i'd use. Stock Tether now works, GPS, Netflix, etc. not sure what else
[Verizon Samsung Galaxy S III] loryndm:
Just a few questions to the other early adopters on CM10 for the SIII.. i have been running 8/28 for a full day and a everything seems to be good however there are a few items id like clairfication on:

- battery life seems horrible. I recall battery life on stock rom lasting for at least 12 hours..after 2 hours of streaming ESPN radio im down to about 64% off a full charge.Are there any tweaks i can do to increase? When i do a battery review it seems the screen is taking most of the battery and my screen is off for most of the day.

- from 8/26 to 8/28 nightly i lost my alarm notification. I normally sleep through an atomic bombing so i set 2 alarms. Good thing because my alarm went off but no sound came out of the phone.

- Overall network connectivity seems to be an issue for my phone. I constantly loose 4G and it appears that the mobile network is just dropped. To fix i have to set the phone to airplane mode then turn it off for it to resync to the verizon network. It happens quite a few times a day and then ill just reboot. Is there an updated modem for the device now?
[Verizon Samsung Galaxy S III] Nnyan:
I've found that it can take a few full battery discharge cycles before a ROM gets "baked in". I will hold off on judging the battery until then. I've also noticed better results if I wipe my battery stats when I flash a ROM, YMMV.

Haven't seen that yet myself. I do notice that wifi/data are not as "sensitive" as stock (when I carry one stock phone and the other with an AOSP rom I get more bars and faster connection speeds on stock). There is at least one kernel out there you should give them a try.
[Verizon Samsung Galaxy S III] loryndm:
Just loaded 8/28 and still no notification sounds. Hmmm...
[Verizon Samsung Galaxy S III] milan03:
Works on mine 08/28 at least for texting and email
[Verizon Samsung Galaxy S III] morganpants:
does everything work? or any bugs that impact reliabilty? or is everything pretty solid?

(about to flash CM for the first tiem ever)
[Verizon Samsung Galaxy S III] tanpatnode:
Has anyone had the echo problem? I can't make a single phone call right now because the opposite person is echoing. I know that it isn't just my phone because I flashed 8-28 on my brother phone as well.

Has this been addressed previously in the thread? If there is anything I can do please let me know.

Also, has anyone else thought that the speaker was WAY to loud? It going to make me go deaf. Thanks
[Verizon Samsung Galaxy S III] strung:
Try build 8/26. 8/27-29 have the way too loud bug
[Verizon Samsung Galaxy S III] jdubau55:
I've had that problem for a while on different build.

---------- Post added at 05:14 PM ---------- Previous post was at 05:12 PM ----------

Look at your battery stats and see whats eating up the battery. I noticed very high Exchange usage when I flashed one of this weeks builds.
[Verizon Samsung Galaxy S III] trginter:
Only problem I'm having is my GPS guided navigation won't work. It's been stuck on "Searching for GPS..." for 15 minutes now.
[Verizon Samsung Galaxy S III] morganpants:
i'm getting a flickering on the top left side when scrolling (twitter especially) with the latest version
[Verizon Samsung Galaxy S III] trginter:
Same here, with various apps.
[Verizon Samsung Galaxy S III] itsmefu:
Try going to System Settings , Developer Options, and check Disable HW Overlways. See if that fixes it.
[Verizon Samsung Galaxy S III] skenney1993:
my sd card keeps on saying damaged when i insert it. I have fixed it but it happens again
[Verizon Samsung Galaxy S III] jlokos:
BT voice Dialing not working

Everything was working great on the 8/28 build until I attempted to use BT for voice dailing. It connected the first time and the voice dialer came up but did not respond to the voice commands. When I turned the BT off, it could not reconnect until I went into settings and BT and pressed on my BT device. I went into the bug tracker, and sure enough someone else previously reported this issue. Since I need BT voice dialing, I'll have to go back to stock until this is fixed.
[Verizon Samsung Galaxy S III] aqhilles:
I don't use the VZ voicemail svc. I use Gvoice. After flashing 8/29, the voicemail notification stays on the bar (not the gvoice notification.) I received a call this morning and went to voicemail, but no msg was left. Gvoice inbox was empty, yet the voicemail notification remains there, even after a reboot.

I tried wiping cache and dalvik and no luck...
[Verizon Samsung Galaxy S III] josephpalozzi:
You actually have a voicemail with verizon. This occurs from time to time even of you have selected GVoice as your VM provider. It will happen to me sometimes when I lose signal right as someone calls (like when I am getting on the subway). You can call the verizon voicemail system to listen to the VM - 215-510-8686 to get rid of the notification.
[Verizon Samsung Galaxy S III] sd_N:
LOOK

just an FYI...on the nightly 08302012_0616 build...i had totally not good GPS until this build...Now i got the first lock after boot within 30 seconds sitting in the bedroom with my girl... Serious guys... the August 28th build at 0616 has great GPS. Keep up the good work.

---------- Post added at 08:34 PM ---------- Previous post was at 08:29 PM ----------

This issue has been solved...you need to format your sdcard to FAT32. --------exFAT will not work well with CWR or our phones. I struggled with this for a while before I did formatted mine. You will have to find a third party program to do it cause windows can't. Hope this helps.
[Verizon Samsung Galaxy S III] aqhilles:
I thought of that too and checked but nothing. I had to go to the phone app and clear the data for the notif. to go away.

I had to go back to stock :( I am unable to receive calls -no sound. I can place calls ok. I tried a clean install with the kernel included in this rom and with imo's kernel. Same result -no sound at all. The call originator ends the call after a few seconds.
[Verizon Samsung Galaxy S III] aqhilles:
Sitting in the bedroom with your girl and you find the time to see if you get a gps lock?

Mhhh... tough choices: girl or gps lock... girl or gps lock...

Seriously, what's wrong with kids these days?
[Verizon Samsung Galaxy S III] invisiblek:
^ that
[Verizon Samsung Galaxy S III] mmalkin:
Semi-OT: HBO app has been updated. Claims to support JB now. I have not had opportunity to try it yet, though.
[Verizon Samsung Galaxy S III] jdubau55:
Try logging in online and see what that does for you.
[Verizon Samsung Galaxy S III] Obrien8403:
Just flashed 0901, NFC seems to work, at least I can turn it on and off, installed Google Wallet http://xdaforums.com/showthread.php?t=1794727 Seems to be running, Cards are set up and will test when I get off work and report back.
[Verizon Samsung Galaxy S III] nick.koutrelakos:
I had this problem as well, being an avid GVoice user. What happens sometimes is that GVoice now uses a call forwarding-esque system for Verizon, so when you set it up, you probably had to dial *71+GVoice #, *90+ GVoice #, and *92+ GVoice #. These settings get borked between ROM flashes, and what you end up with is being able to call people, they receive the call, but you hear nothing on your end.

To fix it, just dial *73, *900, and *920, one after the other. You should then be able to make and receive calls as normal. This resets any call routing services you may have had through Verizon.
[Verizon Samsung Galaxy S III] Obrien8403:
Google wallet is working, used it at McDonalds
[Verizon Samsung Galaxy S III] droidstyle:
hell with gps, i would be showing her that warm jellywiz rom :D
[Verizon Samsung Galaxy S III] renzo.olivares:
http://beta.androidfilehost.com/?fid=9390077933525139486

heres a build i just compiled with cm timer and stop watch...also updated build fingerprint to reflect RVALG7 instead of RVALG1 (RVALG7 is a leak) also changed it to reflect JRO03O and not IML74K and other cm changes
[Verizon Samsung Galaxy S III] salas2324:
What does this have, others don't?

Sent from my Verizon Samsung Galaxy S3 4G LTE
[Verizon Samsung Galaxy S III] renzo.olivares:
updated my post
[Verizon Samsung Galaxy S III] renzo.olivares:
oops didnt build with new timer and stopwatch heres the apk for whoever wants it http://beta.androidfilehost.com/?fid=9390077933525139487
[Verizon Samsung Galaxy S III] Dovigoldberger:
Nice !! Good to see you already started working on the device my money was well spent
[Verizon Samsung Galaxy S III] CKyl22:
Does the latest build have the call delay/audio issues like the official one?
[Verizon Samsung Galaxy S III] renzo.olivares:
someone pmed me and said mine didnt but i cant test myself right now so idk..

edit:confirmed call delay is still there
[Verizon Samsung Galaxy S III] corbs132:
Since 8-30, I've been getting Error processing purchase [DF-BPA-09] in the play store. Not sure if it's related, but it's really annoying.
[Verizon Samsung Galaxy S III] renzo.olivares:
reboot sometimes i get that too
[Verizon Samsung Galaxy S III] vaffanculo403:
is there any way to change the shortcuts in the notification drawer? When I was running CM10 I could customize them and I like to add the one to turn the hotspot on and off in there. Any ideas?
[Verizon Samsung Galaxy S III] renzo.olivares:
heres a new build if anyone wants http://beta.androidfilehost.com/?fid=9390077933525139512

cherry-picked quick message notifications from cm's gerrit and the stopwatch and timer...and newest changes from cm's github repo and changes to the build fingerprint and build description for VRALG7 and JRO03O..nothing much really

http://beta.androidfilehost.com/?fid=9390077933525139512
[Verizon Samsung Galaxy S III] revolt1:
clear data on Google frame work, market, and unsynce gamil and restart
[Verizon Samsung Galaxy S III] salas2324:
Anyone get force closes for adding a new lock screen icon ?

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] vaffanculo403:
Echo still present with speaker phone on 9/2 build. Clean install. Absolutely no apps installed. Made a call two seconds after initial boot-up and the caller said it was horrible. Also the call volume on my end was very very low. Back to Paranoid Android...
[Verizon Samsung Galaxy S III] salas2324:
You do know this is the same exact build as official only with a cherry picks? You don't have to post the same thing twice

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] vaffanculo403:
And you don't have to get your panties in a twist...
[Verizon Samsung Galaxy S III] drbveb88:
Odd.... I've had about two dozen calls today. I've had no delay on any of them.

Just had my wife call me from a land line and her Verizon.... No delay.

Shhh.... my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] salas2324:
Delay when YOU call someone. Its take 3-4 seconds to start ringing

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] drbveb88:
No sir. Mine starts ringing almost instantaneously. I went to stock rooted and flashed...everything but my GPS is working fantastic.

Shhh.. my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] neyenlives:
I don't get that but I do get the echo using speakerphone (which I always took as normal)
[Verizon Samsung Galaxy S III] salas2324:
Weird. My GPS WAS all effed up.. but while driving I just let it "give me my direction" and used the app fasterfix to fix my GPS. Now its accurate to 3 meters. :D

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] salas2324:
To fix GPS use the app fasterfix. Reboot. Turn GPS data on. Go to maps. Drive around for a while. In a while it fixes itself.

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] guthrien:
I haven't driven with mine yet but gps worked awesome with My Tracks. That was down trails so had to be pretty accurate.
[Verizon Samsung Galaxy S III] guthrien:
Why is this ROMs thread so quiet? I'm blown away how stable the 9/1 I'm running is. I have less issues than they're having in the Synergy thread right now. It's basically like having a Nexus device with the best hardware available. NFC cleared up after 8/31. My GPS seems mostly consistent.

Just want to say thanks to all those involved in compiling this version.
[Verizon Samsung Galaxy S III] aqhilles:
Thanks, Nick -this is good info to keep handy.

I actually had set up gvoice to get msgs by dialing my own number. I fixed it by going into the phone app and clearing data. Also, I could not hear any calls and be heard when receiving calls.

I think this whole wacky behavior happened when I started switching back and forth between the official and unofficial roms. I know they are very similar and Invisiblek cherry picks a few things here and there, but maybe... meh, who knows. I did a clean install and everything (I think) is fine.
[Verizon Samsung Galaxy S III] quattr0:
Just flashed 9/4 and my phone # becomes 000-000-1111 :eek:

Back to 8/31 :)
[Verizon Samsung Galaxy S III] aqhilles:
I'm on build 9/3 and have no echo or delay when making a call.

Receiving a call is a different story. Every time I receive a call everything is muted for 3-4 seconds, then you can hear and be heard.

Anyone else experiencing this? Is there maybe a build.prop entry for this?
[Verizon Samsung Galaxy S III] salas2324:
That's the delay...

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] aqhilles:
??

I thought your delay was when making a call... Mine happens when receiving.

Oh well, at least we agree on the delay part :good:
[Verizon Samsung Galaxy S III] Zalithian:
I already gave you my best suggestion on this. The phone info app is the only other thing I can think of. Try phone info first.
[Verizon Samsung Galaxy S III] guthrien:
I just did my first ever "dirty flash" going from 9/1 to 9/4. I promptly lost my IMEI. Yikes. Luckily I had a Synergy backup, flashed it and everything was fine again.

Update: Even after a clean install, YouTube reboots my phone every time I start a video. Rolling back.
[Verizon Samsung Galaxy S III] NegativeOne:
I am sort of watching this thread, but I'm still on the very first build, no problems. Sounds like it goes down hill eh? :P
[Verizon Samsung Galaxy S III] aqhilles:
??

I'm on 9/3 and everything works. The only issue I've had is a 3sec delay to connect when I receive a call (from the moment I answer the call.)

Other than that, lte/3g is reliable, wifi is consistent, gps locks fine, battery life is about 10% down every 4hrs with light use. With some use, I get 2hrs of screen time from 7am to 2am and about 35% of battery left.

If anything, I think this ROM keeps getting better and better.

---------- Post added at 02:53 PM ---------- Previous post was at 02:47 PM ----------

After the clean install, did you restore apps using titanium or any other app?

If so, it's almost the same as a dirty flash -I have the same issue consistently with google currents and every now and then with youtube.

If you wanna give it another try, try a clean install, wipe dav and chache and do not restore any apps or settings from a backup -don't even do the advanced->restore app partition (or whatever the menu says on the recovery.)

I'd do this first before giving up on the ROM. I'd try restoring app only too.

I flashed Synergy a couple of weeks ago to see what was new and it seems so slow in comparison. This ROM is so light :)
[Verizon Samsung Galaxy S III] guthrien:
I did not restore before the crashes. I was testing capability. I went back to 9/2 and everything works.
[Verizon Samsung Galaxy S III] milan03:
I'm back at 09/02 build. My phone on 09/04 would constantly reboot the moment I'm about to play a video. Youtube, WatchESPN, Netflix, etc... It would go to some quick boot.

Also beware of 09/05 as the cell radio seem to be non existent or non functioning. No matter what setting I use, I get no service.

Waiting on 09/06 :)
[Verizon Samsung Galaxy S III] guthrien:
Yep same as me. 9/2 is remarkably good I could sit here awhile.
[Verizon Samsung Galaxy S III] salas2324:
Thought was only me

Sent from my Verizon Samsung Galaxy S3
[Verizon Samsung Galaxy S III] e_droid:
Instagram was doing this to me (9/4 build) would make the phone completely reboot when trying to take a picture within the app. Regular camera works fine and still can share. As much as I love the CM ROM, I might go back to stock root. I miss the burst shot modes and a few other features within TouchWiz actually. (Unless there's a JB based ROM supporting these features).

Edit: Almost forgot, my 4G connections are pretty much nonexistent as well with this ROM.
[Verizon Samsung Galaxy S III] NegativeOne:
What do you mean by 'within the app'?
[Verizon Samsung Galaxy S III] odmejia:
He's talking about if you want to take a picture with instagram it would reboot his phone.

So everyone seems to like 09/02 might just have to download that today. I downloaded 09/04 last night and put in my SD card but seems like 09/02 is more stable.. I am still on 08/22 time to upgrade lol
[Verizon Samsung Galaxy S III] e_droid:
Yeah I really had no problems with the 9/2 build.
[Verizon Samsung Galaxy S III] guthrien:
I've been running 9/2 and previously 9/1 feeling extremely enthusiastic about the stability not being able to imagine leaving a JB rom. Unfortunately I had some serious situations today I needed my phone for and I got a reality check. I had a ton of reverb distortion on calls and using bluetooth quickly threw me into some boot loops. I don't fault the rom, I still think this is best cm10 available but I guess I had to get a little smarter and head back to a stock like rom until we get some jb leaks. I hope this build keeps getting better.
[Verizon Samsung Galaxy S III] 95talondsm:
I don't know if it was mentioned, but on the 9/4 build I haven't had s screen flicker until just now. It happened when the phone hit 19% battery left and only when I pulldown the notification bar from the lock screen. I don't know if its ROM related or kernel related. As stated before I'm on build 904 with leak kernel v.10 with the dark jelly theme.

VZW SGS3 CM10 Nightlies with DarkJelly Theme w/ LeanKernel v .10