yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdagreek:
is everyone giving up one the S3 ?

what device is everyone going to move to from here ... S5 ... S4 ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gocats7:
Anyone running rc2 having gps lock issues?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdagreek:
I went back to 10/1 the profiles were not working or in call volume
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
I had just noticed that myself; the GPS won't lock and (for some reason, might just be I had screwed something up) the Battery graph shows that the GPS has been on for like the last 12 hours even though I have confirmed that it was turned off. Weird. I'm going to play around a little bit and see if I can get GPS working again

[Edit]: I can confirm there is nothing wrong with RC2 itself. I've had GPS problems before when dirty flashing ROMs so I followed Enewman's instructions from good ol' S3Rx. See the second post here under "GPS Issues?":

http://xdaforums.com/showthread.php?t=2252932

So I flashed back to stock, did the NV Rebuild method, and on a clean install of PAC RC2 the GPS worked again. First lock took a few minutes but after that it could get a lock with 10 satellites in 2 seconds. Pretty good, I'd say. It seemed to revert after rebooting, taking another few minutes though, but went away again after another "first" lock.

I'm restoring my Nandroid backup now to see if I can get the GPS settings to carry over without having to set everything up again.

[Edit 2]: Nandroid restored and all is well! First lock took one minute 43 secs, every lock afterward (without rebooting) takes between 1-3 seconds as long as I'm standing by my window (I live in a very solid brick building).

After a reboot... First lock in 29 secs and the rest between 1-3.

Problem solved. :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
So there is an rc2 now even though we don't hear much from the developers?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
Lol. That's to be expected though; they're developers, not customer service reps. I just wonder if any of them even reads these threads anymore. We might have better luck just posting our problems on the PAC forums. Those are more likely to be seen.

That being said, has anyone else had issues on RC2 where the sound mode icon (e.g. the silent mode icon) won't show in the status bar even though silent mode is on? I don't think it start doing it to me until I had wiped my Dalvik cache this morning. I dunno what it could be but nothing really changed on my end. It seems like the systemui restarts itself a few minutes after bootup, which is when this occurs.

[Edit]: Restarting systemui fixes the problem for now but it doesn't answer the question of why it does it in the first place.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CaptnCaveman:
Which nightly has the best battery life?? The one I'm on sucks. 4.4.4 RC-1. it's from August 27th build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Anyone else notice that their volumes are *not* saving or at least not being respected by various apps? I'm currently using RC2, was previously

For example, I use Tasker to set my volumes in the morning. I've been using the same profile ever since 4.0 and it's always worked. However, I am finding that regardless of what I have set in Tasker all my volumes are always at max until I change it. Between reboots the volumes go back to max until I change it again.

This is also a problem as I use my phone as an alarm. In Tasker I set my alarm volume to 8/15 (set the volume steps in Settings > Sound), but in the mornings the alarms scream out at 15/15. Even manually running the Tasker profile (hitting the play button in the bottom left corner of the profile) doesn't change the volume levels. As well, going into the alarm app and setting the volume levels of individual alarms doesn't work either. Opening an alarm and checking the volume setting for each alarm always shows that it's at 100%. Even if I change that alarm's volume to say 50%, save the alarm, and open it again, it shows up as being at 100%.

This wasn't a problem at all with RC1. But I've been having this problem since day 1 of flashing RC2 about a week ago.

I have done the following, in different combinations with each other (have a Nandroid of RC1)

* dirty flash over RC1, restored apps (Titanium backup)

* clean flash, no restore apps (except directly from Play Store)

* clean flash, restored apps (TiBu)

* fixed permissions

* clear cache/dalvik (TWRP 2.8.0.1)

* clean flash, restored apps (Restore in TWRP)

Another issue that I have is that TiBu is not rebooting after scheduled backups. I have TiBu scheduled to backup all my apps at 3am and reboot upon completion. For the past 4 years, since having an Android phone, this has worked flawlessly and has never failed me. Now on RC2 it backs up all my apps but never reboots. It just sits there. I can confirm that clicking on the "Run" button to manually run the backup doesn't reboot it either.

Anyone else experiencing these same problems? I'm wondering if I should roll back to RC1 or a more "stable" nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Omega Hunter:
I'm on the 10/20 nightly now but as far as I know there were no problems with the RC2 volumes (aside from in the Profiles). I just checked with mine on the nightly and Tasker had no problem changing the volumes. When playing with the media volume, it even changed in real-time (I had a song playing and the volume went up as I increased it in the Tasker action). So either the problem is somehow on your end or they fixed whatever was causing it.

I've never set TiBu to reboot my phone but I just tested it for you and that also works without incident also. I had run a schedule manually, haven't tried letting it do it automatically but that should be fine too.

I installed through a dirty flash. No restoral of any apps cuz everything was still there. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Thanks for testing all this for me. I guess it's something in the RC2 that just doesn't like my phone. I downloaded the RC2 twice, and both times I still had the problem. I'll try with the 10/20 nightly on a clean install tonight.

Thanks again!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy_d0:
Can someone help with info?

I need to know what bootloader / baseband Pacman is on - I wiped my phone before checking and now can't get back to stock
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] daver68:
Anyone having trouble with apps just randomly force closing with night lies after 10/20? I've tried 10/20 - 10/26 and this problem keeps happening. It'll be fine for a few hours after a reboot, but eventually apps will just force close randomly. Could be something in the background or the current app I'm using.

I've originally thought it was because of a bad downloaded ROM file, but it's consistent with multiple flashes of differently nightlies for the past couple of weeks since the 10/20 build.

I might have to go back to RC 1 since that was the most stable build for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutname:
did they remove the ability to customize the dropdown notification in rc-3?

i've searched through settings and can't find any way to change my tiles/layout
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aromig:
Notification settings are now listed under PAC Settings. Most of the customization features seem to be there now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutname:
after reinstalling i have it.

so far running great with latest kt kernel and nova launcher (trebuchet wont let me force resize widgets so i switched)

are there plans to bring back a feature from 4.3, which allowed opening of custom apps along the bottom of the dropdown notifications?

or the ability to write notes in the notification bar? (i remember a 4.4 ROM having this feature, i don't remember which)

probably the wrong place to ask these questions, sorry.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stinky180:
Just flashed this rom after using BeanStalk for more than 1.5 years. I like it so far, but I'm still getting used to it.

I can't seem to figure out how to remove the google now search bar at the top of the desktop/home screens. Can anyone help me out with that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigfoot.kom:
Hello. Im not sure what launcher you are using. Try to long press on the home screen then when it changes either look for 3 dots in the shape of a triangle on the bottom third of the screen then press them for settings or there may be a setting button that appears after the long press.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jdagreek:
your using Nova launcher ... go into Nova Settings ... Desktop ... and it is listed there as persistent search bar ...

there you go ...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wutname:
dumb question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sfpcservice:
Display Battery Percentage

I just upgraded from a previous pacman ROM to 4.4.4 RC2. How do you display the battery percentage? I can't find the option in any of the settings menus. I had this on the previous version I was running. Thanks and great ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
I am using the latest release from December and I love it. :D Thanks for a great ROM. :good: Is there a camera app/setting/config/ magic dust that will keep me from having to reboot every few pics. I have downloaded the Cm camera fix from the play store. It seems to help some but not every time. Does anyone know if there is a working camera for the S3 on 4.4.4? :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
settings/pac settings/status bar/battery status style.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgpk:
Just picked up an s3 tonight. It came loaded with 4.1.1 (lucky me!!). But being as I have this rom on my s5 I guessed why the hell not? Well, after root, recovery, and boot up of this ROM, it came to my attention that I can't save any apns.... That's not good. Any work a rounds or recommended versions to use on a d2att?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
I have used this rom for quite a while with very few problems. Are you sue you are using the correct version for your phone? You should be using the d2lte unified build for a AT&T S3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgpk:
Yes sir, but now I'm thinking it's more an issue with my phone, I tried a unified CyanogenMod nightly and running into the same issue, no APN and no service. Maybe since I haven't updated from 4.1.1 yet it's conflicting with the radio or baseband? Anyhow just want to clarify it isn't the ROM, especially when it works fantastic on my s5....I'll keep working on this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Try updating the baseband to the latest first. Newer KK ROMs have issues with older basebands.

GS³: CyanideL + ShiftKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aumast:
Ils this ROM work with ART dalvik
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patcal:
Never tried ART.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgpk:
Yeah I updated to the ne4 baseband last night, works great now, but if I use ktoonzes kernel or leankernel I lose my service, not sure why, but as far as the normal kernel supplied with the ROM everything works as it should. Like I said, I have the same ROM on my s5, I've got no complaints for either one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
I am using the Quantum kernel 10-4 build flawlessly with this ROM now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
Match your kernel build date with the ROM build date. Some newer kernels have issues with signal loss on older ROMs. Especially if the kernel comes with a ramdisk like KToonz or Lean.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！

---------- Post added at 02:33 PM ---------- Previous post was at 02:30 PM ----------

There's an updated one of that, I think built around Christmas time...

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
It had some stability issues.... the 10-4 build was the most stable. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maheshzx:
I'm having problem with my camera on latest build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
No connection error?

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
Same here on galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maheshzx:
One Imp annoying thing

I cannot get my 3g connection work,ever since I started flashing custom roms,In stock I change to 3g by using *#2263# code.

Need help..... Camera solved,I grabbed an old pac rom's camera apk...now it's ok
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
What's the build date on your current install?

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgpk:
Yeah I wanted to try quantum but I didn't see any indication of it being AOSP compatible, I'll give it a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
What ROM date did you pull the camera from? I am on the 1/28/15 nightly and everything seems good but i still have a cam problem periodically and have to reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
FYI I am using the Google Camera from the play store flawlessly on the last nightly build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
Thanks. :good: I tried it on an earlier build and got the same results and I liked the original camera's ui and features better so I went back to it. I will give it another try on this build to see if it's better. Connecting and working trumps layout, ui and features. :fingers-crossed:

BTW the latest nightly is 01/28/15, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vbetts:
Latest stable build, with any 4.4.4 kernel except the stock Cyanogen 3.4 kernel I do not get a data connection. I've tried Quantum, KTweaker, and BMS with the same results.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
Has anyone tried this on i747 to fix the camera?

http://xdaforums.com/galaxy-s3/themes-apps/17-fixed-camera-app-lib-cm-aosp-roms-t2505973

I think I'm going to give it a whirl.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maheshzx:
i'm using the camera app from 28-8-14 nightly,

I'm on 31-12-14 stable release
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
I tried Google Camera. I can open it make settings changes take one pic and it locks up requiring a reboot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jfsat:
KitKat or Lollipop?

I just have a quick question; The title of this thread leads me to believe that this Rom is still KitKat, but a lot of the latest posts sound like Lollipop issues, so if I download the latest nightly, will it be 4.4.4, or 5.0.2 (or some other Lollipop iteration)?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mp3deviant721:
As far as I know it is still KitKat. They do not have any LP builds out yet.

GS³: SlimKat + leanKernel Edition™

ギミチョコ！！
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
Are we in a holding pattern currently? I noticed on the devices I checked that we are all stuck at 01/28/15 nightly. Will there be more nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
Kit Kat development has stopped due to Lollipop.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
So did the camera on 4.4.4 ever get sorted? Mine still acts up at times. It looks like there was a number of camera changes made in the changelog (several in early Feb) but after the 01/28/15 nightly I am using. So there isn't a recent nightly that would use these changes. :(

I'm not really interested in Lollipop yet. It seems to be pretty buggy at the source from what I read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
I have a question is it easy to revert back to the original ROM like I’m with Rogers and my phone is SGH-I747M, presently it’s on PAC Rom

but experiencing daily battery drain, I unplug my phone from the charger every morning after overnight charge and by noon my phone drains down to 40%, without even using it. So maybe my reverting back to the original ROM will stop the battery drainage. Your input needed.

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jfsat:
It could be (1) the ROM, (2) an app or a setting you have, or (3) the battery itself. I don't think it's a bad idea to try out a stock ROM, or even a LP ROM, I'm loving the battery life I get with LP. Obviously check the battery stats and location settings to see if anything is draining your power. If changing the ROM doesn't help, start scrutinizing your apps, and if that doesn't seem to help, consider a new battery.

Edit: Oh, and in answer to your question, yes. It's easy to put a stock or stock based ROM on there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hyewiz:
Thanks for your input, the only reason I’m not going with the LP, is the camera issue, I know there are few 3rd part Camera apps which seems working, but in my case I have an APP that uses camera and the 3rd party camera apps is not working with that app. Camera is a must for me . I wish they get the fix soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] btafoya:
I am right there with you, and quite honestly this ROM is rock solid!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
It is solid. I just want one more nightly to include the camera fixes that were added in February. Please... :angel: :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidAssassin:
I'm using a bell Canada i747mvlufnk2 s3 can i flash d2lte and d2att as i can with d2can files
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nasempire:
Whenever I plug in my headphones, the audio does not play most at times. At times it works but most often, it says unfortunately DSP manner has stopped. I seriously need my audio. Pls help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RamblingBarba:
I had a different device a couple of years ago that did that. The "fix" I used was freeze or delete DSP Manager. It is a signal processor, is Eq and sound shaping.

I don't have my headphones handy to try mine to see. I will tomorrow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheXGX:
Hey quick question.. Which bootloader and modem are you using? I can't seem to get LTE to work :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MrBrady:
Anybody know what's changed between the Dec 14 'release' of this ROM and the latest January 15 nightly?

I'm running the Dec release now and it's very solid! Only issue I've ran into is an occasional SystemUI crash where it throws me back to the lockscreen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nasempire:
Hi. Have you been able to fix the headphones not working when plugged in issue. I get it a lot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yapoyo:
I honestly don't know, as I got rid of my S3 back in June and I have a G2 now... Sorry.

---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------

I don't know if it's fixed or not, because I upgraded to a G2 in June... Sorry. And Dev please delete my previous post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Hey, I'm from the 5.1.1 pacman thread and since it was closed I have a question. Sorry, I know you guys said don't ask for ETAs but is there a rough ETA on when 5.1.1 will be moved here? I was thinking of just staying on the version of pacman I have on my phone until 5.1.1 is moved here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Modems are location based. They have nothing to do with ROMs. You will just need to try them out in order to find which one works best for your location. There's a modem thread in the development section that you might want to check out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
LOL my bad..I meant to say wifi tethering, as someone had asked about wifi tethering in either the verizon or the tmobile thread. :p

I saw that a patch was uploaded that fixes the driver so that secured wifi tethering now works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Flashed and loving it, but haven't played around too much because i just got proposed!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloud9x:
Congrats, drinfernoo

Great rom, tried it for a night but I got a little put off by the triple dot overflow menu that appears in every app - is there any easy way to get rid of this? Only issue I have, really.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Congrats
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidDude24:
Stability

Is this rom stable enough to use as a daily driver? Plus what are the bugs if any? Sorry I'm coming from a stock rom and dont want to flash and find out its unstable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blanco613:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

I've been using this all day and I would say so... No crashes or anything yet...Very smooth and stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bcvictory:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Please make a build for the Nexus 7!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AndroidDude24:
For stability I also mean like is 4g working, calls are ok, texts are coming through and nothing is out of the ordinary is going on with the device. And also if i do flash should i backup efi before installing? And also should i flash cm10.1 first than install this rom or directly install this rom from stock? And also I am using CWM. Want to make sure that its ok to use. Thanks in advance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wschamps42:
so for some reason, i get blank screens/no options under the AOKP rom control section in settings, and if i click performance i get a force close error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

+1

Might be a good idea to incorporate task's AOKP instead of the official, just since it's a little more feature filled and has Bluetooth more or less completely fixed :)

I am loving this ROM :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Near Perfect

Guy's please check FAQ in OP or look back a page for answers, it''s not like there are thousands of pages.

Thanks klin1344, super smooth, loving every minute of this ROM. Really appreciate you taking the time to make a smooth and feature complete 4.2.1 ROM. :good: :highgive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blanco613:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Well you should always make a back up and yeah man everything has been working great for me. 4G, calling, etc

---------- Post added at 05:18 AM ---------- Previous post was at 05:16 AM ----------

Also I would recommend the latest twrp recovery to flash this... I like it better
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Does this use the cm10 or aokp MMS?

Installing the inverted MMS.apk is the only way I can send picture messages on any rom(long story)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][4.2.1] PAC-Man ROM v19.9.0 ~AOSPA + AOKP + CM10.1~ | PIE | Hybrid | (2/8/13

Please read the FAQ. ROM control is a work in progress and will be fixed soon.

Also task uses aokp's source just like this ROM, except that he has patched up a2dp in the device trees and secured WiFi tethering in the kernel. These things I will fix in the next build.