yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] hazysight:
I hate to add in and say yep my phone freezes up also, since its already been stated by others.

But I'm curious to know if when yall say the phone freezes does it leave it completely useless?

In my case the phone appears to freeze up but really the screen just won't turn back on. I've had several freeze ups but whatever app I was running continues to run. For example the other day I had my navigation(don't really look at is just use voice direction) and XM app running put the phone in my cup holder and after several minutes I picked up my phone to check email and the screen would not turn on. The gps kept giving me voice directions and the XM app kept playing audio. Data transfers also continue as this happened also while I was transferring a doc via bluetooth to my laptop and the screen would not turn on but the file transfer was completed.

Anyone having this hiccup? And this is different from a freeze up and my issue is just the screen won't turn back on?

Also I keep getting system.ui error on reboot :p
[Verizon Samsung Galaxy S III] funnyperson1:
I'm on the 15th, the only stability issue I have is a reproducible hard-lock when making phone calls. Basically if you make a phone call and leave the screen on, I think it locks up when the screen times out. If I manually turn off the screen, or use the phone it won't lock up. If I just leave the screen on the dialer, it will hard-lock and only a battery pull brings me back.

Can someone else try this? It might be because I restored call logs with TiBU. I tried clearing dialer data (which wiped out the call logs) but that didn't seem to help this lockup issue.
[Verizon Samsung Galaxy S III] Prack:
I haven't had time to post but I've been running each of the updates as they came out. I'm on the 3/24 3.15 build now with leankernel 5.0.2 exp 1 and it's pretty solid.

I do have one issue where the phone will boot to a black screen. I see my pull down menu and that's it. If I go to settings, apps and force stop my launcher the home screen will load. Minus this everything is great.

Thank's again notta!
[Verizon Samsung Galaxy S III] skusa93:
For those of you having screen of death issues on any of the builds I would suggest boosting the minimum Mhz that your CPU is set at. Usually SoD is caused by the processor going into a frequency too low for it to handle (every processor is different, you'll have to experiment to find a sweet spot)

I was having the issues on the 3/24 as well, but as soon as I turned up the minimum frequency setting the issues went away :good:
[Verizon Samsung Galaxy S III] jsdecker10:
sweet...i had a feelin that upping the min freq would stabilize it a little and somewhat alleviate the SoD issues some have been experiencing. What kernel and kernel version are you running? And just for a reference point, what WAS your min frequ set at? ...and what stable setting did you CHANGE it to? After you made that change, has everything been running smooth? No hiccups or SoD issues to note? Thanks!
[Verizon Samsung Galaxy S III] Badouken:
Still getting too many freezes and i even tried a different kernel and didnt even mess with the freq! Also kept getting the screen of death and my battery would loose alot of power after such events...I just switched to a different rom and ill be back on PA3+ as soon as the next update rolls around!
[Verizon Samsung Galaxy S III] RaiderX29:
Notta,

GideonX posted this in his BMS kernel thread. Might want to look at picking this up in the next AOSPA build.

https://github.com/CyanogenMod/android_kernel_samsung_d2/commit/1e7d08721e373fecd7a39db34a8cc8cbec10a02c
[Verizon Samsung Galaxy S III] jsdecker10:
your link is all jacked up.. it has the ... in it, so it takes you to a 404 page not found
[Verizon Samsung Galaxy S III] RaiderX29:
Thanks its fixed now. It was supposed to be: https://github.com/CyanogenMod/android_kernel_samsung_d2/commit/1e7d08721e373fecd7a39db34a8cc8cbec10a02c
[Verizon Samsung Galaxy S III] RaiderX29:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

New build up!
[Verizon Samsung Galaxy S III] Badouken:
Thanks for the update! Clean Flashing now! Will Update on any bugs later!
[Verizon Samsung Galaxy S III] jsdecker10:
which Kernel is recommended for this new 3-30 build? The included kernel? I prefer LK...would u recommend LK? I'm not too hip on SoD's and battery pulls lol..
[Verizon Samsung Galaxy S III] Badouken:
Im a huge fan of lean kernel as well, but with these past couple of builds ive been getting SoD's and battery pulls even with the default kernel! Im currently on the 3/30 build with the default kernel and i havent experienced any issues, I might flash lean kernel later.
[Verizon Samsung Galaxy S III] jsdecker10:
trivial correction..

I know this is trivial and doesn't matter at all for the functionality of this ROM, but I believe I've found a minor spelling error...lol. But anyway, if you navigate to SETTINGS -> Wireless & Networks -> "More..." -> Mobile Networks Settings ...under "Network Mode" , it says Preferred network mode: LTE / "CMDA" / EvDo / GSM / WCDMA...I could be totally wrong here, but isn't the "CMDA" supposed to be "CDMA" instead? Not trying to nitpick, it's just that every time I see that, it bugs me for some reason..lol Maybe I'm wrong? Maybe it's correct and I just didn't know? :confused:

---------- Post added at 08:00 PM ---------- Previous post was at 07:48 PM ----------

This may be a dumb question, but with the default kernel can we overclock and undervolt?
[Verizon Samsung Galaxy S III] Badouken:
Mine Says CDMA , no error on my phone? maybe its just your phone somehow?

Also you cant overclock with the default kernel but you can underclock!

EDIT* YUP Just got a SoD while listening to music on the 3/30 build... music just stopped and screen is black... Have to do a battery pull... :( , everything else seemed to be fixed though! UPDATE! Happened again after listening to music for 5 mins...
[Verizon Samsung Galaxy S III] badbeats:
Sorry if this is dumb but I cant figure it out.

My phone connects to my cars bluetooth without any problem. I was using a cord to play music. It hit me I should be able to play music via the bluetooth.

How do I do this?

Thanks!
[Verizon Samsung Galaxy S III] skusa93:
For those of you getting SoD, along with bumping up the minimum Mhz for screen off state like I mentioned on the last page the latest LK has been updated to fix the issue that Texan29 mentioned about a few posts ago. Between the two you should be able to solve any issues you might have been having lately.

Link to the newest kernel.
[Verizon Samsung Galaxy S III] Shaftamle:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

So I clean flashed both 3.15 ROMs and everything is perfect after boot. I have data, I can make phone calls, and everything in phone info is how it should be. But as soon as I reboot the phone when the screen comes back up it says waiting to activate. When I go back into the phone info everything is good including imei, connected to Verizon, pro, ROM, kernel, baseband, everything except the phone number which is either unknown or 000-000-2474. All of the mobile network setting are the same except it switches to ruin instead of ****/sim. I switch it back, nothing, reboot, nothing. I have an active data connection, just no phone. Any ideas?

Sent from a Shaftamle Galaxy S3
[Verizon Samsung Galaxy S III] Badouken:
Not 100% sure if this is what you are asking but I had a similar problem awhile back you have to mess with the mobile network settings, The network mode should be LTE/CDMA/EvDo , and CDMA subscription should be RUIM/NV. At least Thats what i currently have and that should change your phone number back to normal methinks!
[Verizon Samsung Galaxy S III] Lt. Barclay:
On latest build, anybody else notice the quick settings panel layout acting funky? The tiles aren't all staying in the spot I put them.

Otherwise build running pretty nice. Lock screen custom background is back!

EDIT: Reset my layout and everything is good. I initially deleted all the tiles and added them back in. Must of screwed something up. Don't do that.
[Verizon Samsung Galaxy S III] jsdecker10:
check it out....how strange....:confused:
[Verizon Samsung Galaxy S III] brockkk:
Got a random reboot last night, bumped up minfreq and haven't had a problem since. I'll knock on wood though
[Verizon Samsung Galaxy S III] Shaftamle:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

I tried switching to those settings. No luck. Its SK weird, everything is good after flash but after reboot, it switches to away from ruim/ nv and when I switch it back it does nothing. :banghead:

Sent from a Shaftamle Galaxy S3
[Verizon Samsung Galaxy S III] matthew4295:
Okay so I flashed the Lean Kernel (wiped cache before) and now it won't boot. It sits at a Pink s3 boot logo. What did I do wrong?
[Verizon Samsung Galaxy S III] Badouken:
What version of lean kernel did you flash? If its anything below a 5.0 build on 3.10 or above It gets stuck at boot I believe.
[Verizon Samsung Galaxy S III] matthew4295:
version 2.1???? And I'm on 3.15 for PA. Anyways, it's fine. I just flashed another kernel.
[Verizon Samsung Galaxy S III] Kreeker:
** Nevermind, I found it. I guess the lists of stable and nightlyish build haven't been updated in a while.

I don't see a download location for 3.1. Where is it?
[Verizon Samsung Galaxy S III] Badouken:
Haha wow that really blows my mind! how did that happen? Explain Phone!

Sorry to hear that.. that really sinks... i have a similar issue when i try to change frequencies and set it on boot... but no matter what I do it always resets to the normal frequencies! So annoying! no matter what kernel or ROM i use it has the same problem!
[Verizon Samsung Galaxy S III] JumperPunk:
I had a similar issue a while ago. In my case it would try to activate on boot, fail, and worked sans 4G. I restored my IMEI, reflashed, and that fixed it. I had tried all sorts of things before that, and it didn't work (clearing cache, re-install ROM, restore stock, etc). Check this link for details:

http://rootzwiki.com/topic/32397-tutorial-imei-backup-nv-with-qpst-us-variants/

Note: I know you said your phone shows the right IMEI, but mine did, too. And restoring the IMEI still fixed it.
[Verizon Samsung Galaxy S III] Prack:
PA 3.15 is linux 3.4 you need to flash a 3.4 kernel. Leankernel 5.0+ is all linux 3.4 any of the older leankernel builds will bootloop you due to not being linux 3.4.

Also for all the guys having to do battery pulls, you don't have to actually pull the battery. You can do volume up+power+home button for 8 seconds and the phone will shut off. Then just power up normally. Saves a bunch of time and hassle if you have an annoying case like mine :)
[Verizon Samsung Galaxy S III] SilentAce07:
This has been a problem on most aosp roms for the past few weeks. The official and unofficial cm threads have investigated this fully. The old solution of airplane mode toggle and such is only temporary and doesnt work.

We have figured out how to relieve this issue. You need to flash the rom, flash the gapps, wipe cache/dalvik, then DIRTY FLASH the rom again. For some reason, certain files are deleted or corrupted if you wipe data/cache/dalvik before booting. If you just wipe cache/dalvik without a dirty flash, your next boot (usually the first boot) will work flawlessly, but then will try to activate upon next boot.

We never figured out how or why this happens but the dirty flashing the rom a second time once it's been flashed normally solution fixes it permanently.
[Verizon Samsung Galaxy S III] Neverender326:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

Push play on your music player???
[Verizon Samsung Galaxy S III] SilentAce07:
I've had literally zero issues with the 3/15 build. I'll be staying on it until Key Lime Pie most likely.
[Verizon Samsung Galaxy S III] Badouken:
A New 4/1 build is up on GooManger now!!!! seems one of the changes logs are "Additional Kernels Merges"! seems like some good news to me!
[Verizon Samsung Galaxy S III] lilafleisch:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

Has anyone installed this in twrp?
[Verizon Samsung Galaxy S III] Badouken:
The Rom? Ya I exclusively use TWRP!
[Verizon Samsung Galaxy S III] charlieg90:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

So I was installing the 4/1 build on my 3 hr drive yesterday, and the instant I started the pre-flash wipe of System in TWRP the phone rebooted... not to Android, obviously, the system partition was at least partially gone, and yet recovery wouldn't boot either. It would just get to the Teamwin splash screen, then reboot.

Thankfully, download mode still worked, so I was able to ODIN back to stock, update TWRP, then actually flash the new build. It just took several hours, cuz our internet at home is borked. I had to ask to use my roommate's iPhone's Wi-Fi tethering to download the ODIN tarball. :|

So yeah, I guess the joke was on me this April Fool's, huh? The new build is running great though!
[Verizon Samsung Galaxy S III] nonsns3:
Low Res MMS

I'm running build 3/15. Everything runs great except sending MMS seems really low quality. For example I have a high quality image in my gallery. I send the hi res pic via MMS. Then click on the image in the message history. The image is pixelated and low quality.

Any ideas? Thanks for your time in advance.
[Verizon Samsung Galaxy S III] jsdecker10:
I think that's prob something weird on your end...try reflashing maybe? I've never experienced that problem on any builds, nor did I have that issue on that same build (3/15). You could also check out your mms settings.
[Verizon Samsung Galaxy S III] ticholas:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

This has unfortunately been a trait of this rom for some time, well before the 3.0 builds Not sure when it will change.
[Verizon Samsung Galaxy S III] jdeloach:
Re: [ROM] [AOSPA] PARANOIDANDROID 3.10 (Mar15) | 4.2.2 JDQ39 Linaro 4.7 O3

This is due to the MMS app compressing the pics before it sends. You can usually look around and find a MMS app to flash that doesn't compress.
[Verizon Samsung Galaxy S III] bwassef:
so I am having an issue with my camera....all my pictures have a weird blue tint. anyone else have this issue?
[Verizon Samsung Galaxy S III] element1966:
Strange bug found

Not sure if anyone here is using a car dock/cradle, but here is the issue I'm having when I dock the phone:

I insert it into my iBolt car dock and drive around with it while using Spotify or Poweramp for music.

My settings for audio are set to use dock USB audio. (Settings -> Advanced -> Sound -> Use Dock USB Audio)

After a short time of driving, listening to music through my aux in coming from the dock, and taking an occasional call via my bluetooth headset, the phone will not allow me to answer calls.

When it starts to act up; A call comes in. I accept the call using the button on my Jawbone or by sliding the button on the screen to answer the call. It seemingly answers the call and starts the in-call timer. There is no audio coming through the handset, earpiece, or stereo and the caller can't hear me.

If the phone is unplugged from the dock and removed at this point the same symptoms now persist until the phone is rebooted. I can make an outgoing call and the in-call timer will start, but nothing ever rings and there is no audio.. just the click sound through the handset when a call is placed, or the sound my Jawbone makes when a call is initiated/ended. The call never actually goes through. Disabling bluetooth and just using the handset or speaker at this point yields the same results. No incoming calls can be answered or heard and no outgoing calls can be answered or heard.

I played with it for a while and asked several people who called me during one of these fits what happened when I picked the call up. I got the same answer every time. The phone never picked up on their end.. it went straight to my voicemail after reaching the max number of rings.

Only solution is to reboot. And it happens A LOT when the phone is docked during my drives. I really want to use the car dock for audio passthrough too :crying:

This has occurred with my iBolt dock, my Samsung Infuse dock (got rid of it because it held the phone WAY too tight), my Jawbone Icon, and my Plantronics Voyager Pro.

Never occurred on stock ROM.
[Verizon Samsung Galaxy S III] dr wits:
gmail bugs

awesome build! would use this as a daily driver but there is one bug in gmail that stinks... when i go to a label in gmail and try to open up an email with that label it fc's. no clue why. this is on custom labels btw... drafts, sent, any native label works fine.

thanks for the great work!
[Verizon Samsung Galaxy S III] amaury48:
Just flashed the 9-01 build and my phone won't activate, have no data. Tried re-booting a couple of times, but no luck. un-locked, rooted, running g1 radio. Any ideas?

more info: flashed in CWM 6.0.1.2 touch recovery
[Verizon Samsung Galaxy S III] wera750:
I was having more than unusual data problems too. Couldn't get 4g etc. Note I've been on aosp based ROM's since Dhacker's first build.I understand the normal data problems. This was different.

---------- Post added at 01:24 PM ---------- Previous post was at 01:21 PM ----------

With that being said, I love PA. And will probably flash back soon lol.
[Verizon Samsung Galaxy S III] amaury48:
UPDATE: Lost IMEI on flashing this latest release, Fortunately I performed a IMEI backup with the Synergy_Backup_HWKeys_signed.zip tool and just reflashed the IMEI backup zip it created, phew....dodged a bullet.......forgot about the possibility of losing the IMEI on some of these roms.
[Verizon Samsung Galaxy S III] Clienterror:
Yea that zip is a freaking godsend. Supposedly you can lose you imei flashing anything but it seems like I'm seeing less and less posts about people losing it so I dunno if they are just repairing it easily now and not complaining or there are actually less people losing it lol

Sent from my Galaxy S III
[Verizon Samsung Galaxy S III] psufan5:
Where do you get that zip
[Verizon Samsung Galaxy S III] r1_2fast4u:
I hope I'm not going crazy or blind but where is the 9-1rom? All I can find and see is 8-29, 8-30

Builds
[Verizon Samsung Galaxy S III] aznguyen316:
Found the zip: http://xdaforums.com/attachment.php?attachmentid=1281376&d=1345868740

here's the thread: http://xdaforums.com/showthread.php?t=1792499&page=574

I backed up my IMEI via this: http://xdaforums.com/showthread.php?t=1802024

*edit*

Just used the zip in CWM. Made a backup in sdcard/synergyrom and then I just copied that over to extsdcard to have a safe backup. Hope I don't need it but glad to have it.
[Verizon Samsung Galaxy S III] drbveb88:
Are you talking about 8-31, I don't see a 9-01 build anywhere?

Shhh.. my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] r1_2fast4u:
One thing I remember back when I was with sprint and had the epic touch was to avoid touch recovery at all costs Lol for some reason they don't play nice with our phones.
[Verizon Samsung Galaxy S III] wera750:
Touch recoveries work perfectly fine. I've been using twrp and cwm touch with no problems. Many others have too.
[Verizon Samsung Galaxy S III] Stryker1297:
flash back to a TOUCHWIZ rom (any should work, synergy, beans, etc)

now perform a data reprovision by going in to the dialer and entering *2767*3855#

note that it will perform a factory reset on your phone. but your data should be fine.if it doesnt work, u may have borked your imei.
[Verizon Samsung Galaxy S III] drbveb88:
+1. Twrp2.2 has work for every ROM, mod or theme that I have tried. Being able to name your back up is really convienent as well.

Shhh.. my Galaxy is a little Paranoid
[Verizon Samsung Galaxy S III] GatorLCA:
BUG 8/29 build:

Settings --> Lockscreen --> Slider Shortcuts

When you save an App from the main choices (not Applications) and save it, it doesn't show up on the lock screen. The app is saved in settings when you go back so it's just not showing up
[Verizon Samsung Galaxy S III] aznguyen316:
does this rom flash the regular CM10 kernel with it too? I had used the kt kernel when I first flashed this.. wondering if I need to source the stock CM10 kernel or if the latest rom will just flash kernel as well? Thanks!

I also haven't gotten the notification LED light to work for anything =/
[Verizon Samsung Galaxy S III] KINGDROID25:
I have tht zip but do i wipe anything b4 flashing (cache, davlik)
[Verizon Samsung Galaxy S III] sasquatch080:
So you're one of the first to actually recover completely with the back up of the IMEI through the synergy zip. Good to know it really works. Got my backup also and feel more relieved that it works. Now on my flashing streak I go.:D
[Verizon Samsung Galaxy S III] xXJay_RXx:
Is anyone having issues with GPS? I have issues with other AOSP roms. Is it an AOSP thing?
[Verizon Samsung Galaxy S III] jonathonparker:
Here are some screenshots from my battery over the past day.

Wow so my img host wont work...
[Verizon Samsung Galaxy S III] THE SKATER DUDE:
when installing this for the first time do i need to do that counterclockwise method at the welcome screen?
[Verizon Samsung Galaxy S III] Badouken:
Randomly got Screens of Death when I was listening to music and again when an Alarm should have gone off... Cant Hard Reset like everyone keeps saying to do when this happens, it just doesnt work on my phone for some reason, ive tried every method... still no luck have to do battery pull everyime... on the upside when i do pull the battery and reset the battery life either isnt affected or lowers slightly... compared to before where the % would drop 5-10% at a time.
[Verizon Samsung Galaxy S III] Prack:
I updated to leankernel 5.1 exp 1 and have had 0 issues since. No more sleep of death, no more loading to black screens and having to stop my launcher etc. Just thought I'd throw that out there if anyone is having issues try adding lk 5.1
[Verizon Samsung Galaxy S III] hazysight:
Debugging

adb will not work on my phone. I connect it to my pc and everything shows up i can navigate thru the files etc.

I turn on Debugging and try to run for example AGPS patch and I keep getting: "error: device offline"

Odin can't find the device either. I have 3 machines I have successfully done these adb commands on before and now all of them give me the same issue. Should I flash again?
[Verizon Samsung Galaxy S III] natethegreat86:
You need to make sure you have the most up to date android sdk that is what caused the issue for me, after that you should get a popup on your phone about permission and then it will work, I'll see if I can find a link to the thread I read of some other things to try as well.

Here's the link http://xdaforums.com/showthread.php?t=2144709
[Verizon Samsung Galaxy S III] Ronde90:
I did a full wipe and a clean install of the latest build and everything works perfectly. Using the stock kernel with absolutely no issues in the 3 days that I have been running it.
[Verizon Samsung Galaxy S III] jsdecker10:
The newest build along with the newest LK build 5.1 works flawlessly for me as well..*knock on wood*
[Verizon Samsung Galaxy S III] brockkk:
There's too many damn versions of lk
[Verizon Samsung Galaxy S III] hazysight:
that worked. I was already on the latest, but I just deleted and installed again. This time when I run it i get a notification on my phone asking if I want to trust this machine never had it pop up before, but it all works now. Thanks!