yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] Badouken:
Wow my battery life is also just terrible now... Check out these screenshots.... Its almost impossible to believe...

These were taken after I've literally done nothing with my phone...

Update* so ya my phone only lasted 3 hours... In standby... No idea what it could be...
[Verizon Samsung Galaxy S III] 1900mcm:
I would consider trying a different kernel. I'm using LeanKernel v9.3 1/21 (see rootzwiki its listed as for d2 as all the d2vzw is now rolled under a single build).

I had a battery problem as well, with BetterBatteryStats reporting a Kernel dma wait lock which I had not seen before the 1/21 notta build. after switching the kernel, things have gone back to sanity.
[Verizon Samsung Galaxy S III] Badouken:
Ya Ill probably try that, I used to use leankernel all the time but have been using stock for the past couple months.

Also Beta 4 has just been released!!! Sure Notta is already on it! Check it!

AOSPA 4.0 Beta 4 <2014-01-27>

Restored two finger quick setting pull down

Improved lightbulb activation time on tablets

Immersive mode fixes (also, now a dual tile)

Network toggle tile is disabled if Google dialer is installed

Sleep tile long press opens power menu

Long press rssi (mobile network) tile takes you to data usage

Dimmed dual tile switch icon

Downloads notification now expandable (show download speed)

Fixed Nexus 10 bootanimation

Add SuperSU to settings, hide app from launcher

Little performance improvement

PA OTA fixes
[Verizon Samsung Galaxy S III] kuntri:
Nav Bar & Hybrid Settings

Has the nav bar setting been removed? I'm on 4.2.2 1/21 build. Tried searching and found no results.
[Verizon Samsung Galaxy S III] jaynole:
I have to say, so impressed with the current build, running KT.

In the past few days, only 2 random reboots and a few apps that don't show up in the app drawer after installing. Most likely a 4.4 issue.

No Bluetooth issues, no iDock issues. Flat out impressive. Keep up the fantastic work.
[Verizon Samsung Galaxy S III] JumperPunk:
I had the same thing happen once when I tried a different kernel (leanKernel). Reflashed to the same build and it worked. I'm actually running leanKernel now (maybe an updated version?) and it works great. Do a clean flash and you will probably be fine.
[Verizon Samsung Galaxy S III] Badouken:
Notta uploaded beta 4 (1/28) to goo if anyone was curious or unaware!
[Verizon Samsung Galaxy S III] doratheconquistadora:
I've been out of the loop for a while.

I'm currently 12/15/2013 build with 0-day PA gapps.

Can I dirty flash over this with the newest build or should I clean flash. I usually go the clean route but I'm getting a little lazy heh.
[Verizon Samsung Galaxy S III] notta:
BETA4

BETA4 Update brings; Dialer UI Updates plus Dark Paranoid, Quick Settings 3.1, Restored two finger quick setting pull down, Improved lightbulb activation time on tablets, Immersive mode fixes (also, now a dual tile), Network toggle tile is disabled if Google dialer is installed, Sleep tile long press opens power menu, Long press rssi (mobile network) tile takes you to data usage, Dimmed dual tile switch icon, Downloads notification now expandable (show download speed), Add SuperSU to settings & hide from launcher.

http://goo.im/devs/notta/roms/d2vzw
[Verizon Samsung Galaxy S III] Badouken:
I'd say that you would be fine with a dirty flash but you are a couple updates behind , would be wisest to clean flash if you are over a month out of date. Your choice I suppose. Anything goes wrong you can always reflash a backup or clean flash if you experience any issues.
[Verizon Samsung Galaxy S III] doratheconquistadora:
For a clean flash. Just wipe data, cache, and dalvik and then flash the ROM. I don't need to flash gapps since I'm using the 0-day PA gapps correct?
[Verizon Samsung Galaxy S III] Badouken:
Correct, except not 100% about the 0-day gapps, I normally just flash them again because when you wipe it wipes all the apps. You could always not flash the gapps again and see if they are missing then return to recovery and flash them again, I've done that before with no problem, then again it's up to you.
[Verizon Samsung Galaxy S III] meowcats:
pretty good battery life for me

running KT kernel
[Verizon Samsung Galaxy S III] doratheconquistadora:
Which version and where do you get it? I've always stuck with the stock kernel with this ROM but never really had stellar battery life.

Did a full backup and decided to try out dirty flashing (just wiping cache and dalvik first before flashing the ROM).

The only problem I hit is my camera is force closing from different things (a reboot fixes the "Can't connect to camera" issue).

I'll clean flash later today and that should fix the camera issue.
[Verizon Samsung Galaxy S III] jguns112:
I installed this rom but on boot it just repeatedly says "Unfortunately, Phone has stopped." Making it impossible to do anything. Any suggestions?
[Verizon Samsung Galaxy S III] flyestAC:
Clean flash and try again.
[Verizon Samsung Galaxy S III] jguns112:
I did a clean flash. Tried multiple times even, to no avail. I have the latest recovery (TRWP 2.6.3.1)... Although the thread suggests CWM recovery, so maybe that's the issue.
[Verizon Samsung Galaxy S III] flyestAC:
Redownload the ROM? I flashed with twrp no problem.
[Verizon Samsung Galaxy S III] Badouken:
I had a ton of issues with TRWP 2.6.3.1, including roms not flashing / backups not working, unable to factory reset... ect. ect. , ive had these issues ever since 4.4.2 roms came on the scene... I switched to CWM and have had no issues but pretty sure im in the minority with that issue.
[Verizon Samsung Galaxy S III] doratheconquistadora:
I had an issue with CWM today actually. After the dirty flash and not liking the camera not working I decided to restore my backup and it kept giving me a md5 mismatch. To fix that I deleted the contents of the nandroid file as a workaround according to an article I found on the issue. I got the backup to "work" but I lost data to apps and other minor settings. Not sure what happened there.

But it's whatever. I was going to redo apps after the fresh install anyways.
[Verizon Samsung Galaxy S III] Badouken:
did you rename the file? Heard that causes that issue... Nonetheless that sucks... TWRP and CWM really need to update with some bug fixes it's been awhile... But free is free I guess and they don't really owe us anything.
[Verizon Samsung Galaxy S III] doratheconquistadora:
I didn't rename it. The article mentioned not too as well. But yeah bugs happen.
[Verizon Samsung Galaxy S III] Gutsman:
I've had a weird issue where sometimes, videos won't buffer on YouTube over LTE. They do buffer if I switch to 3g. I tried the Gravitybox data rate monitor, and it just stays at 0 without attempting to load the video. Everything else works though. It occurs randomly, at least a few times a day, and persists through reboots. It doesn't matter whether I use the official YouTube app, an unofficial one (Viral), or go through my browser. I'm currently on beta 4 with latest ktoonsez kernel, optimized dalvik, and ML1 baseband. This has been an issue since beta 3, and I've been clean flashing since beta 2. Other than that, this rom has been perfect!
[Verizon Samsung Galaxy S III] anonymity:
Unfortunately, Bluetooth Issues Persist

I just flashed the Jan 28 build and unfortunately I'm still seeing the same BT issues with my car. This is after a clean flash, I did a factory reset (data and cache wipe), and wiped System and Dalvik cache, twice. The ROM is running great otherwise, which is what makes it even more of a shame. I use bluetooth in my car too much to be without it. I've been trying to deal with it for weeks now, since I first started testing the KK beta builds but I can't keep it up. Looks like I'll have to go back until this gets worked out. I have to say though, other than the BT issue that plagues all KK ROMS for the S3, I love this ROM. Great job in all other aspects.
[Verizon Samsung Galaxy S III] stu1811:
My BT issues went away with Beta 3. Have you tried unpairing and repairing your phone?
[Verizon Samsung Galaxy S III] manaox2:
Same here. It's almost as good as it was on 4.2 for me now, only issue is that I have to reboot every time I want to reconnect or I get no audio.
[Verizon Samsung Galaxy S III] therobut:
You have to do a clean flash, but also wipe system. This problem is caused by the Google dialer. If you don't wipe system before flashing, the installer will automatically back it up, and then reinstall it after the rom.

Go to recovery, wipe Data, Cache, Dalvik, and System. Then flash away.
[Verizon Samsung Galaxy S III] jguns112:
That worked! Thanks!

I suspected it might have something to do with installing the Google dialer, but I hadn't read anything about it.
[Verizon Samsung Galaxy S III] jguns112:
Sorry if this is a dumb question, but I can't find a way to enable the quick toggle after saying no to the first prompt. Is it possible?
[Verizon Samsung Galaxy S III] corbn89:
Same here. No video while on data. this may be a YouTube bug. The latest version of the app is getting a boatload of complaints.
[Verizon Samsung Galaxy S III] Kreeker:
Is there any easy way to remove the ASOP keyboard notta baked into the room? I'm trying to upgrade to the new release and it's saying I can't upgrade because the app was signed with a different key.
[Verizon Samsung Galaxy S III] meowcats:
Kt747 1/18 & PA 1/21

Coming on 48 hours with stock battery
[Verizon Samsung Galaxy S III] manaox2:
I just got around to trying the 1/28 build. I had an issue after reboot where the CPU wasn't scaling up past 384Mhz in interactive mode (stock). Put it on Ondemand which seems better. It was very slow with just maps and poweramp connected over Bluetooth. Curious as to how that happened.

Edit: seems to be linked to Google maps. Using PA full modular 123a.
[Verizon Samsung Galaxy S III] therobut:
Not a dumb question. It's not even close to obvious how to do this.

System Settings -> Backup and Reset -> Reset Preferences

Have fun :)
[Verizon Samsung Galaxy S III] somerandomguy1:
How much screen on time?
[Verizon Samsung Galaxy S III] meowcats:
23% is screen on, minimum brightness, only check email or txtmsg. most time spent at 189mhz.

67% spent in deepsleep.

using ktoonservative governor.

you can see battery percentage decreases at very linear rate... because I did not use it much in that time. But it is good to see phone is spending lots of time in deepsleep.
[Verizon Samsung Galaxy S III] rfranken:
Does this Rom have things like;

-Active notifications

-Lock screen customizing (other than widgets)

-Halo

-Status bar customizing

-Quick tile customizing(found it but seems very limited. Audio would be nice

Thanks
[Verizon Samsung Galaxy S III] focalguy:
It does take a while to find the answer by searching but no. If you check the PA official page you'll see they don't have it working on 4.4 yet so we don't have it here.
[Verizon Samsung Galaxy S III] Keekers:
AMAZING! Thanks for the advice. I flashed the Kt747 Kernel and my battery life is better than ever.
[Verizon Samsung Galaxy S III] meowcats:
also enable autohutplug for ktoonservative and min cpu=189mhz, seems to be working very well. had to disable google+ in app settings though... kept cpu awake for 8hours+
[Verizon Samsung Galaxy S III] somerandomguy1:
Wow, impressive. I'll give that a shot when I flash over the 12/08 Beta build...it's doing all sorts of weird stuff and my battery life is all over the place. Best I've gotten was 48 hours on my extended battery.
[Verizon Samsung Galaxy S III] Badouken:
Quite happy with battery life now! Before it was at something terrible like 4-6 hours on stock kernel... I flashed lean kernel after not using it forever and my results are posted below... Stock battery!

About an hour of talk time and two hours of screen time!
[Verizon Samsung Galaxy S III] MDB2313:
You are Awesome for keeping this ROM going!! :good:
[Verizon Samsung Galaxy S III] CKyl22:
I can't figure out how to turn off the battery charge light in this build.

Also, how do you enable the blurry translucent lock screen in this build? I can make it see through but not foggy.
[Verizon Samsung Galaxy S III] Keekers:
Thanks for your help. Kernels are a completely different language for me! I have no idea what I'm doing with the settings so I just leave them alone.
[Verizon Samsung Galaxy S III] rfranken:
Does PA have a Twitter account to follow? Do they have a website? I'm a recent convert to this rom and can't make heads or tails of anything as it all seems to be a cluster F.

I see a link to a what looks like a dead website. If I google search for a website I get taken to a place where all the downloads are labeled as gapps.

The op of this thread only points to ancient builds.

What am I missing here?
[Verizon Samsung Galaxy S III] NZitney:
https://plus.google.com/app/basic/+ParanoidAndroidCorner?source=apppromo
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Did you look in the second post (where all the info is) and click the rom-goo.im link? The most recent builds are at the bottom, its listed in date order.
[Verizon Samsung Galaxy S III] rfranken:
There is no info in the 2nd post.

and their twitter must be dead and closed.

I'll see what I can find on their G+ community.

thanks.

edit. well their G+ page just talks about features that aren't in their Rom. So confusing.
[Verizon Samsung Galaxy S III] therobut:
Just circle their g+ page, and read the updates as they come out. You'll catch on to what's happening sooner than you think. I still don't understand every detail they mention, but I understand what's relevant to me now. Just takes some effort.

Btw Google is your best friend. If you don't understand a term or phrase, just Google it. You'd be surprised.
[Verizon Samsung Galaxy S III] SlimSnoopOS:
Ahh, my bad I was referring to the actual rom DL itself.

Like the other folks have posted, the PA G+ page is where all of the main info is presented for official releases. Since Notta posts these unofficially, when he is able to post a new build, he'll also include general info about the new changes in his post (latest release here).
[Verizon Samsung Galaxy S III] JumperPunk:
Sorry. It can be hard for those of us who have been around a while to remember that some of this info isn't as obvious as it seems. Some of these issues have been answered a gazillion times, but that is long buried in the forum now. Crash course in PA:

Paranoid Android (aka AOSPA or PA) developed the Hybrid Engine, per app color, PIE, and Halo.

The PA team only builds for Nexus devices, plus a few others. The S3 is not one of those devices.

Our beloved developer notta compiles from source for the d2vzw. Thus, you will not find builds for our device on the PA site. Builds are available on goo.im.

PA 3 is based on JellyBean (Android 4.1-4.3). PA 4 is based on KitKat (Android 4.4).

The PA team announced that they would be rebuilding stuff from scratch for Android 4.4 and releasing features as they are finished.

So far, there is no Hybrid Engine/PIE/Halo etc in the 4.4 builds. It should be just around the corner.

The best way to know what is going on in PA is to follow their G+ account (not the community). Read the posts from about October 2013 for a full view of what is going on with AOSP 4.4/PA 4.

goo.im folder:

http://goo.im/devs/notta/roms/d2vzw

latest AOSPA 3 build:

http://goo.im/devs/notta/roms/d2vzw/pa_d2vzw-3.99-RC2-L13N-20131017.zip

latest AOSPA 4 build:

http://goo.im/devs/notta/roms/d2vzw/pa_d2vzw-4.0-BETA4-20140128.zip

Hope this helps! Happy flashing!
[Verizon Samsung Galaxy S III] rfranken:
thanks a alot!! (someone nudge the op to put that on his first post for us new guys coming over to PA)

fyi...the PA 4.4 build runs way better than the carbon 4.4 build. good job!
[Verizon Samsung Galaxy S III] Badouken:
Just go to there google + page like others have shown you! They post a decent amount on there its quite nice! There last post pretty much says they will have an update next sunday!!
[Verizon Samsung Galaxy S III] Quickpaw:
I've had a good week of using BETA4 (JAN28), and so far, not too bad. I was dirty flashing since BETA1, but I decided to do a fresh wipe and install for this. Here are the issue I've found so far:

The camera seems to crash more often than with the previous BETAs. I can take about 2 to 3 pictures before it locks up my phone. I have to do a battery pull to get it back.

YouTube works for the most part, but when playing a video, I am forced to go to the pull-down settings and toggle the Verizon Wireless/LTE network. Once the network comes back, I can play a video. If I want to play another video, I have to repeat the process.

Every so often if I'm using a login screen within Chrome to log into a website (even XDA), my phone will lockup and only a battery pull can bring it back.

As mentioned a few pages ago, the program DeaDBeef (used for playing chiptunes) doesn't seem to work with BETA4. Worked with all previous versions.

Overall, good speed and great as a Daily Driver. Keep up the great work notta!
[Verizon Samsung Galaxy S III] Nicene Nerd:
Is the Paranoid OTA available in this ROM? I can't find it anywhere.
[Verizon Samsung Galaxy S III] NegativeOne:
I can't see many recent comments on the sstability of everything in recent builds. Can anyone comment?
[Verizon Samsung Galaxy S III] icyhandofcrap:
Experiencing same issues, also Bluetooth does not seem to reconnect automatically again.
[Verizon Samsung Galaxy S III] murraydeath:
Its been pretty smooth for me so far...been about a week as my daily.

Only issues I had was the play store not working but a reflash of gapps fixed.

My gmail seems to download in bursts instead of all the time. But that might be a design choice
[Verizon Samsung Galaxy S III] Badouken:
Been using the newest beta for about a week and I've had no issues, except if i remember correctly my phone freezing once when using Google play music but thats it, i dont use bluetooth really though so not sure if that's 100% or not. Camera seems fine for me and wifi has been dynamite!
[Verizon Samsung Galaxy S III] JumperPunk:
I've got some strange Bluetooth issues on the newest build. I know others have issues with automatically reconnecting, but mine seem a bit different. I have a Jawbone ERA.

When I turn of the headset, the phone doesn't realize that it's gone. It still thinks it is connected. This causes some strange audio issues. Also, the phone never tries to reconnect because it never knew it was gone to begin with.

The phone does not know when I push the button on my headset. I can press it (or "TapTap") and the headset thinks I've answered the phone, but the phone just keeps ringing. I can do the same to hang up, and the headset makes the built-in sound to hangup, but the call stays connected.

The media connection just drops after a while. I can be playing a game or listening to music, and the sound just stops. It doesn't come back until I break the media connection and reconnect it.

Often times, after one of these issues happens and is fixed (especially if it fixes itself somehow), the phone reboots a few seconds later.

Has anyone else noticed these issues? I think I may have a bad flash, but I haven't gotten to it yet. I've noticed some similar issues on previous builds and good flashes, but not quite to this degree. Hopefully, I will have time to reflash tomorrow. I'll post an update if I do.
[Verizon Samsung Galaxy S III] t1231:
I have somewhat the same issue, using the jawbone era and Belkin air play. Sometimes connects instantly other times multiple attempts and no luck. Had had the same issue with the jawbone thinking it has answered and phone keeps ringing also thinks it has hung up but hasn't. I also get the reboot but only when streaming music is paused and hang up on call

Kt747 Kernel
[Verizon Samsung Galaxy S III] stu1811:
Same here. Beta 4 broke my bluetooth again. I lost the ability to control my phone from my car. I reverted to beta 3 and it worked again.
[Verizon Samsung Galaxy S III] Maphack:
Just thought I'd mention a new version was released. I am about to flash it.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] notta:
BETA4 Update

There is not much going on via PA's side. Everything more or less is coming from CM's changes. I did update Dark Paranoid (TRDS) light condition tweaks from SlimRoms! Some of those CM changes include bluetooth fixes and so far I'm auto connecting fine.

http://goo.im/devs/notta/roms/d2vzw//pa_d2vzw-4.0-BETA4-20140208.zip
[Verizon Samsung Galaxy S III] Badouken:
Well Paranoid Android usually releases weekly updates on their google + page on sundays right!? They have been updating every Sunday except last Sunday for the past month it seems and they said to wait till tomorrow for an update in a previous post! Hoping for Halo or something cool in the next build from them!!!

Also Thanks for the update Notta! :good: been using your builds for over a year and they have been more or less amazing! Keep up the good work! :D
[Verizon Samsung Galaxy S III] Maphack:
Dirty flashed no problem btw.

Sent from my SCH-I535

:thumbup:
[Verizon Samsung Galaxy S III] aypeeootrek:
For people with bluetooth issues, try gideons bms 2/5 test build kernel. It fixed my bluetooth issues on 4.4. You can find it on his Google + page if he didn't update his kernel thread. On Google + it's bms kernel I believe
[Verizon Samsung Galaxy S III] Badouken:
Clean flashed and whenever I'm on data it says "roaming indicator off" and I searched everywhere and have no idea how to fix this? Also I no longer get 4G anywhere I walk a couple miles a day to school and back and I usually have 4G the entire walk but now it just says 3G, not sure if speeds are actually slower or not thoufh, it just says 3G instead of 4G now. (but this has been a problem for me a various builds). I've tried many things to fix this as well and have no idea how to fix it. I've had this problem in the past and ive flashed back to roms like CM and im able to get 4G so I'd only assume it's a problem with the PA rom.

If anyone has any input or solutions that would be cool! Thought I'd just share some issues I've been having!

Edit* but I'm also on lean kernel so I might either try another kernel or wait for the next build and just see how it is on the stock kernel.
[Verizon Samsung Galaxy S III] johnnytraveler:
Go into settings-mobile networks-cdma subscription and make sure ruim/sim is checked. Then back in network settings go to preferred network type and check lte/gsm/evdo. Also, are you using the ml1 radio? It's the newest radio.

Sent from my Cromix TF700T tablet.
[Verizon Samsung Galaxy S III] Badouken:
Ya, I already did all of those things that's why im super confused that I still have the problem!?! wonder what it could be :confused: Ill just clean flash again tomorrow and hope it fixed.

Edit* Randomly don't have have the "roaming indicator off" message anymore. But still have the 3G/4G problems.
[Verizon Samsung Galaxy S III] johnnytraveler:
If there is another kk rom that you run, that gives you 4g, you can always dirty flash (just cache and dalvik) this one over it. Earlier this month people were using this method to get data on a rom that upon initial install did not have data. Obviously nandroid before you do. May not be something you want to try. I don't make it a habit of doing this.

Sent from my Cromix TF700T tablet.
[Verizon Samsung Galaxy S III] Badouken:
Ya I might flash CM or something and then Flash back to PA next build, I've done that in the past and it seemed to maybe work?! I didn't really pay attention too much in the past. Ill mess with it and hopefully find a temp solution. Update*: Ya still have only 3G on my phone... kinda lame... even on other roms... I think it could be verizon... PRL version updated awhile back and thats when i started having the problem I think... sooo ya darn... Might just order a new Sim card see if that helps.

Edit* In other news seems like Beta 5 is coming!!!

AOSPA 4.0 Beta 5 <2014-02-10>

Quiet hours

National data roaming

Updated and fixed a few APNs

Enable transparency on Manta

Update ParanoidOTA (no longer requires root access)

Bug Fixes

Download speed not showing/expanding

Quick settings fixes

Manta flashlight toggle fix

A few AOSP fixes