yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thuglifesk:
Any way to hide the clock on status bar? I've tried ROM control but it comes back after every reboot. I guess due to conflicting settings?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brekec88:
Don't use 4.2 gapps. Reflash ROM with 4.1 gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
Its a CM10 issue.

Just use Paranoid Kangdroid

Or AOKP

Don't use CM10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kaiso:
I was having problems with it also and deleted it. I'm using lean kernel with great success.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuRock:
I reflashed and the bottom mic seems to be working just fine now. Thanks for this awesome rom. Like McDonalds, "I'm loving it" :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I never used that, but I thought visual voicemail relied on touchwiz right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Ok, got the visual voicemail working again. Had to first follow the steps on this post #1

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

Once setup, it prompted me to update to the newest visual voicemail and all is good again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I'll check the log to see if there is anything wonky. But are you using the stock kernel or another one?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Thanks, completely stock and clean. I tried kt last time didn't help anything as far as I could tell.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] likonvampire:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Quick question:

Pie included does not show system status and notifications like LMT launcher or do we need to activate something in the ROM ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I just took a look at the log, and well all I could get from it was that something was causing kernel panic and forcing a shutdown. Looks like the camera has run out of buffer. I don't know what's causing it or why it only happens to your device though.

[29472.093846]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.100713]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.108588]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.127358]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.134225]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.142099]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.160869]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.167736]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.175610]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.194350]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.201217]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.209122]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.227861]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.234759]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.242633]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.261373]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.268270]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.276144]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.294884]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.301751]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.309656]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.328395]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.335293]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.343137]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[29472.361907]I[0:mm-qcamera-daem:15329] Waiting output 0 buffer. but it doesn't matter.
[29472.368774]I[0:mm-qcamera-daem:15329] msm_mctl_reserve_free_buf: stream is turned off
[29472.376648]I[0:mm-qcamera-daem:15329] nishu path_irq_2 - no free buffer!
[COLOR="Red"][29472.384858] [0:mm-qcamera-daem:15329] Going down for restart now[/COLOR]
[29472.391420] [0:mm-qcamera-daem:15329] arch_reset : clear reset flag
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Yeah both times I was using snap chat actually, thought it was just coincidence though because on previous clean flashes it happened randomly, usually when idle in my pocket or on my desk, but there seemed to be no consistency.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sguerra923:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Anyone having problems with gps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Nope, no problems here. I think that somewhere in the general sections for the T-Mobile variant that there was a GPS fix method for aosp ROMs. It involves reverting back to stock touchwiz and then going back to aosp, then GPS should be fixed.

Look here for more details: http://xdaforums.com/showthread.php?t=2111306

Just instead of downloading the T-Mobile firmware use the at&t firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
There was also a GPS "fix"... here. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

What happened to the "kill all" button in recents? I have also been noticing that apps don't always close properly, and I end up with every single app I've had open in my recents.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
It's quiet... Too quiet. I am hoping that has to do with klin working on a new build :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KAwAtA:
1) I find that normally, threads are quiet because the rom is dead.

or

2) the rom is too stable that no one is whining and b-wording.

Seeing as how klin is still actively patroling this thread, I think it's the second option
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

1) lol at "too stable".

2) It took me a second to figure out "b-wording".

3) Me too :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Pretty sweet bro, running with BMS Kernel....nice ars ROM ...though these tests really don't mean too much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jordanetodd:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

The reason i haven't been posting is that I'm compiling touch Ubuntu. Multiple projects and whatnot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Isn't the kill all button on the bottom left? Also for the apps not always closing properly, I think it is because when CM, AOKP and AOSPA were merged, they all had slightly different recent apps implementations and options which is causing a conflict. I am trying to track down where error is by comparing to CM10.1 code...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I think it disappeared with the 4.2.2 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Me three! :beer:

It looks interesting...I might go ahead and compile a test build tomorrow just to see how it runs. Though the base is essentially a CM10.1 mirror but stripped of the dalvik VM so that means no native support for android apps. We'll see how it goes.. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrk2815:
will this rom work with the Samsung i927 captivate glide or not. just wondering who ever has been the developers of the rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Right here on bottom left
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Most likely some duplicate options conflict is causing the clear button to disappear. Go into ROMcontrol and see if changing some of the recent apps options will get your clear button back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Wait...seriously??? You'd think that a ROM posted in the AT&T Galaxy S3 forum for the AT&T Galaxy S3 i747 will work on a completely different phone with absolutely no resemblance to the S3? I think you have come to the wrong place, mate. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Oh dang. You mean this option? :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

However, after finding the kill all button, it seems to kill all except the most recent, rather than ALL :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cuddlesy:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

ParanoidAndroid feature.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Yep. Because in jellybean 4.2 the recent apps will show all apps, even the one you are currently in. If you press the clear button, the app you are currently in will close as well. Kind of annoying, so in AOSPA they made it kill all apps except the one you are in so that you will not be exited out of what you are doing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Personally, I love this feature. At least half the time, I want to close everything but the last thing I was doing. The rest of the time I don't mind swiping it away, if I even care. You get rid of all of the memory sucking apps in one shot this way anyway.

I am loving the latest build. Stable as snot, great performance, excellent battery life.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Shouldn't it kill all of them if you are at the home screen?

Also, I am working on a better animation :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sir_Brizz:
Does anyone have Instant Upload albums in Gallery? I liked having those but it seems that I don't have Picasa Web Albums sync available in my account even after installing Google+.

Any ideas?

---------- Post added at 04:15 PM ---------- Previous post was at 03:29 PM ----------

I looked into it further. It seems that the CM camera doesn't do Picasa Sync. Sad face :(

I flashed the old Jelly Bean camera for now. It seems the 4.2 GoogleGallery is what is needed but the camera on there is all hokey. Is there a 4.2 camera that doesn't have the hard freezing problem when taking a picture with the flash on and without pre-focusing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
No, there isn't unfortunately. Unless the camera is built from source for the GS3 like the CM10.1 camera, any camera apk that you find will have the hard freezing problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Thanks, glad you enjoy this ROM. There will be another update tomorrow :p

Yeah I wish AOSPA would implement this feature, so that if you are on the home screen it will automatically kill all apps, but when you are in another app it will close all of them except the one you are in. Who knows...maybe they are working on it..:D

And looking forward to see your bootanim!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Awesome :)

I am more concerned with apps not being stopped properly to begin with. I'm having apps, even if I choose the quit option or even "hold back to kill", that stay in the queue like they are still open.

It'll be coming but I work 9 of the next 10 days :D So we'll see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
We have 2GB of RAM, what are you worrying about?? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Kills my battery life and turns up the heat on my phone to near-surface-of-the-sun temperatures XD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] oilers2010:
Sounds like a rogue app or an hardware issue in my opinion.

Try factory reseting the phone and clearing all data/cache (incl davlik). Leave the phone for a bit to see if the problem happens again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Did you see what we were talking about? Because of overlapping stuff in this ROM, apps are evidently not getting closed correctly, as well as staying in the recents list. It is common knowledge that leaving apps running means the CPU works harder, and higher CPU usage means higher temperatures and more battery drain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Common knowledge?

There have been long posts and sticky threads about this so I think the contrary is common knowledge.

Those apps aren't actually RUNNING in the back. It's actually beneficial in a few ways when you don't kill them.

Take a look at the many many threads about task killers.

Android will manage the apps properly and know when to kill them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cuddlesy:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Yeah, there's really a lot more to Android app management. That elementary view of "if it's running in recents you're wasting battery!!1" is a bit silly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

This may be the case in general, but klin mentioned about a page ago that because of the overlapping nature of this ROM, it isn't happening correctly.

---------- Post added at 11:54 PM ---------- Previous post was at 11:52 PM ----------

And I can notice a very discrete difference in my battery performance when I have apps "running" in recents, versus when I don't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cuddlesy:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I'm willing to bet you're just witnessing the placebo effect at work; that would also explain why there are so many applications on the marketplace that people say 'extend battery life' through aggressive task killing. I think I've cleared my recents menu once in the past year and my battery life is phenomenal.

Point is, apps stored in recents barely affect your phone's performance or negatively impact battery life. If you start running low on memory Android will auto-close them. Unless the app is poorly-designed/leaking memory all over the place, Android can handle it.

To avoid clogging up this thread, we should just call it quits and focus on development-related posts. No point in beating this long-dead horse.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Soooo anybody getting the crt off animations freeze of death preceded by a very laghy phone? I'm on ktoonsez's kernel, I've seen it posted there, just wondering if anybody else gets it. It happened like three times today.

I can't wait for an update, I'm having so many crashes and reboots.

Edit: dang it, just saw a new kernel posted I'll try that and see if it's helping
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgdaniel:
It was an issue with ktoonez 2/22 kernel after he merged cm commits for the display. Had to revert to the 2/19 for the issue, but seems like 2/24 fixed it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Yes that is an issue with the ktoonsez kernel. Flash the latest update of kt747 and it should be fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

It's still not perfect, black screen of death killed my alarm, almost didn't wake up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I have been having, since last night, no new flashing, a black screen of death every time I get a notification. I'm holding out for a clean flash until the update :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Anyone tried the PA gapps package with this ROM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TopHATTwaffle:
Has anyone been having Bluetooth Audio streaming issues. Mine seems to be completely fine sometimes, and other times the track will skip in and out every 15 seconds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I just had the craziest thing happened I've ever seen on my s3 or any smartphone I've owned, may totally be unrelated to the ROM, but I was just watching a YouTube video and the phone made an alarm sound and froze while the alarm sound was going off for about 10 seconds then shut down on its own without even rebooting I had to reboot it manually and of course is working fine now. But Wow, that was trippy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Encerspay:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

I'm really having trouble with Paranoid Android. Seriously, no matter how many settings I reset, I get things like this going on, impossible to read.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] omgdaniel:
Been using it with this rom, only issues are the camera issues (have to manually focus before shooting).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ElBeaner:
Anyone figure out how to invert the mms? I check the box and nothing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Have you tried setting Google now specifically back into phone ui and 360dpi? After doing that and a reboot it should be back to normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeeey:
This newest 02/21/13 update is magical!

Anyone here frequently use Bluetooth in their car or at home for music? I've tried Pandora Radio on my LG SoundBar and it still seems to sound very airy, like it's missing mid and bass. I just sold my car so I can't test the bluetooth in there, but I did just use the soundbar on a TouchWiz 4.1 rom prior to flashing and it worked fine.

EDIT: Disregard! Bluetooth is working great!

Also I'm noticing when I take an HDR shot, gallery crashes when processing the photo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Is it the photosphere camera?

I'm not having either problem. I use Bluetooth in my car nearly every day, and the only problems I've had on this ROM are Pandora related, not Bluetooth related :P

Speaking of which, is anyone else having trouble with Pandora not letting you add stations?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeeey:
Nevermind bluetooth is working great!

As far as the station issue. This has been happening for a couple months now since Pandora's latest release. For whatever reason they haven't fixed it and I haven't seen anyone mention the issue in the reviews on the Play Store. The issue persists on various roms. I ended up just installing an older .apk

Now the only thing I'm trying to figure out, which I've noticed on the current AOKP, ParanoidKANGdroid, and PACman, is the mic volume when recording. Whether it be Google Voice to Text or Facebook's voice messaging, it just shows the microphone volume really low.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xxsicknessxx:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

His latest netball had issues unless fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

ROM running great bro. I am still having some wired things happen while using YouTube though
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

What kind of weird things? Could you explain?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Ko

Yeah if u didn't see the post earlier , an alarm sounded during a YouTube video and it locked and shut the phone down. I booted it back up and uninstalled / reinstalled YouTube and it was running fine for about 20mins and while i am watching a clip it'll stop playing until you hit the play button again, it keeps doing it. I don't care enough about YouTube watching enough but cant figure out why it is all of a sudden doing it. I did flash jellybam for a few mins outta curiosity then reset formatted and restored backup to Pacman....maybe something lingering from that.. ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/21/13)

Could you get a logcat? Jellybam probably wasn't the cause of the problem unless you only restored system, not data, when going back to pacman. (which is the equivalent of dirty flashing)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
New PAC-Man release (2/26/13)

A new update is out! Happy updating :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/26/13)

Downloading now ! Excited ! Awesome job
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/26/13)

Def didn't dirty flashed i wiped it right lol

It is still running this is all over the place for sensor errors
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Hmm...that is interesting. Could you make a backup, full wipe, and then see if the sensor errors are still there? After that you can restore you backup. I just want to know what could be the cause because I've never seen those errors in my logcats. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wally3614:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/26/13)

Yeah ill do that tomorrow and see...it is pages of it. :D

Edit" just saw update ill flash as new install see what happens...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drinfernoo:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/26/13)

Can I ask what time zone you're in, klin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frosty5689:
Re: [ROM][OFFICIAL][4.2.2] PAC-Man ROM v20.0.0 ~AOSPA + AOKP + CM10.1~ (2/26/13)

Theres this werid @2131429753 setting on 02/26 build inside settings >toolbars

Tapping on it causes settings to crash.