yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
I had this problem with those first unofficial CM 10.2 release and after a few night it get fixed and hadn't any problem.

But now I went back to PAC for 4.3 and I can't use these 2 nightly version and both stuck in boot logo and even I turn the phone on and off many time, and it didn't help me at all.

Even that 10 second you talking about is not working either.

---------- Post added at 08:39 PM ---------- Previous post was at 08:08 PM ----------

I tried the CWM and I now I'm completely stuck on the boot, and now I have to do Odin again.
[AT&T Samsung Galaxy S 4 Android Development] King Cole:
So, does this ROM have a working IR blaster or not? I can't really tell from the mixed comments.
[AT&T Samsung Galaxy S 4 Android Development] Vaygr:
I wish I could help you, but I could only say a clean install would probably work (factory wipe, wipe both cache then install newest ROM, THEN install the new Gapps.). But it's extra work and hopefully you have backed up your data.
[AT&T Samsung Galaxy S 4 Android Development] Neoistheone2000:
With TV Terminator and TV off they give an error that they can't connect to the IR blaster, Smart IR remote dissent work at all either.
[AT&T Samsung Galaxy S 4 Android Development] tr2ride:
confirming I have boot issue with 16 and 17 still ... using philz clockwork mod recovery ... went back to my clean 4.3 rom for now
[AT&T Samsung Galaxy S 4 Android Development] JiNYx007:
Was having issues as well. Switched to plain cwm and worked fine

Sent from my tricked out S Quatro
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
I did wipe data , wipe cache and everything and it's kind of unstable and not working good.

Right now after I flashed many time and even I flashed the last CM nightly build too in the middle of it and all with wiping data, I can reboot my phone.

If I'm reporting this it's just because I want to let the maintainer knows that this bug was fixed in the latest CM ROM , he should look for it over there maybe it helps him to fix this problem for people like me.

---------- Post added at 06:08 AM ---------- Previous post was at 06:06 AM ----------

I have a new problem with the ROM, and it's everytime I'm making a folder in my home screen after a few time ( I don't know exactly how long ) it disappear and only the first icon of that folder remain over there.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
So I've read mixed feelings on the latest nightly.. Is it hit or miss or mostly good??...
[AT&T Samsung Galaxy S 4 Android Development] Intellectua1:
Been using it since yesterday only problem I had was notifications kept going off for nothing back to back and when that happened I started getting double texts but a simple wipe of cache and dalvik and fix permissions fixed that maybe it was a rouge app other than that everything is working fine for me
[AT&T Samsung Galaxy S 4 Android Development] soritong:
When I set my phone to recommended (360dpi) the status bar at the top cuts off a portion of my screen. Any suggestions would be helpful!
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
What happened ?

No more release ? it's been 2 days now and still the latest version is 8/17
[AT&T Samsung Galaxy S 4 Android Development] N12X93R:
Android OS is eating my battery.
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
Try to turn of location report and you should be fine and even if you have "Google Service" eating your battery, turn off the WiFi in the location access and you good to go.
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
I'm having the same issue which I've had in the past with many PA based ROMs and even with PAC specifically but the RC1 didn't have it and a few nightlies before then didn't either. In the past rebooting helped but it didn't this time. It's really annoying and drives me freakin' bonkers. Hopefully the next nightly doesn't have it. Or if any can suggest a fix that allows me/us to still use a lower dpi such as 340-360. I'm also using the phone UI as in 360p not 600p.
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
Also Titanium Backup isn't working for me and I do have the newest one which is suppose to be compatible with 4.3.
[AT&T Samsung Galaxy S 4 Android Development] shadowronemus:
You have to change your backup settings to legacy and it will work fine.
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
Ah I guess I'm just a moron then lol. I still have the over lap of the status bar though that sucks big time and interrupts some apps and makes them hard to use.
[AT&T Samsung Galaxy S 4 Android Development] Intellectua1:
Flash this SuperSU zip and it'll start working for u.. I don't know why TB is like that now

http://xdaforums.com/showthread.php?t=1538053
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
It was actually the problem that shadowronemus said it was. You have to change the location of the back ups to storage/emulated/legacy/TitaniumBackup because before it was in storage/emulated/0/TitaniumBackup and it doesn't like it for some reason? maybe because of the 0.
[AT&T Samsung Galaxy S 4 Android Development] Intellectua1:
Oh ok I've never had that problem with TB only problem I've had is it wouldn't restore it would just sit there. Flashing the zip fixed it for me..
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
Well that was my problem is that it wouldn't restore it'd just sit there but the whole legacy file location thing was the problem and solution.
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
What recovery are people successfully flashing the 4.3 ROMs with? I notice that Philz Touch is not updated for it yet. OUDHS doesn't have exFAT support. TWRP seems to be giving problems for people. I want to try 4.3 but don't want to format my sd to FAT32.
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
TWRP and CWM both fine, TWRP never gave me a problem and instead CWM gave me problem of flashing them.

Right now , most of the 4.3 ROMs are stable in boot, and you won't have an issue because most of them at the first won't boot up correctly and stuck in the first logo.
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I'm confused by your statement. You say they are

stable in boot

and I

won't have an issue

because they

won't boot up correctly

. Also, you say that both recoveries are fine but you had problems flashing with CWM.

Am I reading this wrong?
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
I just streamed Spotify over bluetooth in my car on my way to work and its working fine... Did not try calling over bluetooth but I don't much care about that.
[AT&T Samsung Galaxy S 4 Android Development] CZ Eddie:
Great, thanks.

A recent version of CM (the one that fixed bluetooth calling) kind of broke bluetooth streaming for me in that it was working, but would stutter quite a bit. The ROM I was on has not been updated yet and it sounds like CM might have fixed whatever it was, so I'll prolly give this one a go!
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
Question, the GAPPS linked in the OP are 03/01/13,

I have the 05/21/13 from the AOKP thread, does this matter? I would just assumed use the newer gapps but wanted to make sure, thanks
[AT&T Samsung Galaxy S 4 Android Development] apascual89:
You should be fine with those.
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
I am using the 5/21/13 GAPPS without issue. I tried to download the 3/1/13 GAPPS when I downloaded the rom last night but goo was having problems.
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
Thanks :)
[AT&T Samsung Galaxy S 4 Android Development] Hozae21:
Yea I'm actually using slim gapps with no problem.
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Tried Bluetooth calling in my car during lunch and it works for me.

sent from my mobile
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
so anytime I try to change app dpi settings I get a "unfortunately system ui has stopped" error over and over

I tried wiping cache and dalvik and fixing permissions, no dice.

Anyone successfully change dpi or lcd settings?
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Yes I have changed my dpi on system and a couple of apps without issue. Are you doing it with hybrid properties?

sent from my mobile
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
yes.

The first time I tried editing the build prop lcd density, and that gave me those errors, so I wiped and flashed fresh again.

Went into hybrid settings and then clicked the expert mode or whatever it says and changed the system app and user app dpi size to 380 wihthin the Interface sub menu,

those errors came again. and I went to revert them, but the errors stayed, so I restored back to TW rom.

Maybe 380 isnt supported? What dpi are you on?

I should note that in the normal interface settings, it didnt bork anything, but that would not let do what I wanted.

so after enabling expert mode and returning to interface settings, thats when it got borked.
[AT&T Samsung Galaxy S 4 Android Development] apascual89:
With the Hybrid properties settings, there's no need to mess with build prop. You saw what can happen.

We're starting a Q&A thread soon that will help with discussing all that.
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
I am using 420 dpi. 380 hurts my eyes to squint at that tiny setting.
[AT&T Samsung Galaxy S 4 Android Development] KINGDROID25:
Def gotta try this
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
thanks guys! I will try a higher DPI setting than 380 :)
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
One minor thing I have noticed is that when using the "Custom Carrier Label" setting from Rom Manager and "Show Wi-Fi Network Name" setting from System, the Custom Carrier Label is shown twice and the Wi-Fi Network Name is not shown in the notification pull down.

sent from my mobile
[AT&T Samsung Galaxy S 4 Android Development] Hozae21:
I have my dpi set to 320. Adjusting my dpi works fine.
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
thanks, I actually just got 380 working, not sure what the problem was before???
[AT&T Samsung Galaxy S 4 Android Development] KLLSWITCH:
good to hear :good:
[AT&T Samsung Galaxy S 4 Android Development] luigic81:
running Ktoonez kernel on this badboy, everything is groovy :)
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
Haha, Sorry for confusion .

All of the 4.3 CM based ROM when they get the release they had the boot problem ( at least I had with all of their first release ).

TWRP will be able to flash all of them, so you will be ok with that.

CWM maybe gave you hard time, like me that wasn't be able to flash anything and make me to ODIN my phone and then wait a back to TWRP and wait a few days to get fix for boot problem. ( because I thought it's recovery problem and I was wrong )

So by now both recovery are fine with any 4.3 ROM, because CM and PAC ( specially CM ) fixed the boot problem and I didn't have it anymore.

And the boot problem that I'm talking is when you flashed the ROM ( even if you had a wiped data, cache, ... ) it won't boot and stuck on the first samsung logo,
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Well, I tried it with TWRP. It flashed fine and even was able to reboot a few times. But, after all my apps were installed and I setup google wallet, it wouldn't reboot past the boot screen. It just kept flashing "Game Over" and "Insert Coin" for 20 minutes. I could get back into recovery by pulling the battery, waiting a while and then 3 finger dancing. I got sick of it and ended up restoring my nandroid. I had a similar problem with flashing the previous build with CWM only there was no boot screen. It was just black after the custom unlock logo.

Something I found to be odd is the fact that there is no icon for navigation. It's a GAPPS thing and not a ROM thing but it's weird.

Still loving the RC1 4.2.2 build.
[AT&T Samsung Galaxy S 4 Android Development] dany20mh:
I haven't use the Google Wallet so I don't know it may cause something or not, but if you would be able to see that boot screen "Insert coin" you should be more fine and I think maybe with some refalshing again or wiping cache and dalvik it would be pass that and you would be fine.

So far I'm using the 8/20 except only one bug I don't have any issue.

The bug is when I get some notification , and I open notification center by pulling down my finger , at least one of my notification was shown half way and the rest of it it's look like under of it self and when I dismiss all of my notification that one get correct and shown ok.

So I don't know how to fix this one !!!
[AT&T Samsung Galaxy S 4 Android Development] Dare{D}evil:
hey guys came from a clean install directly to 4.4 nightly pac_jflteatt-nightly-20130817.zip everything went fine except for the call log , i dun see it properly, is this a known one ??

the same thing still exists for me with the latest nightly too
[AT&T Samsung Galaxy S 4 Android Development] Mushroom.:
Just flashed the 8-21 nightly. Looks like the option for disabling the capacitive key backlights isn't there like it is in CM 10.2. Is there any other way to turn them off, like a build.prop setting or something? Hoping that toggle gets merged back in soon; it used to be in advanced settings.
[AT&T Samsung Galaxy S 4 Android Development] chinesestunna:
Love this rom so far but when I turn on recommended 360DPI/Phablet UI, the status/notification bar up top would block the top pixels of any app running. It almost seems as if the system doesn't realize there's a bar up top. Any ideas how to fix it? thanks!
[AT&T Samsung Galaxy S 4 Android Development] ThePublisher:
Anyone know if the CM bug where your mic and speaker don't turn on during a call is fixed? This was an issue on CM10.1 that made the ROM unusable for me.
[AT&T Samsung Galaxy S 4 Android Development] dhatch93:
I had that prob on 10.1 and haven't had it so far on 10.2 - but i know not everyone had it on 10.1 so i'd say nandroid and try it out. worst case restore back if it happens to you on 10.2
[AT&T Samsung Galaxy S 4 Android Development] ThePublisher:
Thanks for the feedback. I actually did a backup right after making my last post and will flash later on today and give it a shot. I loved PAC when I had it before, but couldn't handle the phone issues. Hopefully I can come back.

SOMEONE PLEASE DEVELOP A DUAL BOOT PAC/GOLDENEYE FOR THE S4!!!! That or put the Samsung camera on PAC somehow.
[AT&T Samsung Galaxy S 4 Android Development] holysnikey:
I have the same problem on all the 4.3 nightlies too. I had it on a few of the 4.2 nightlies but then it stopped or was fixed and didn't happen on the RC1 either but its back now.
[AT&T Samsung Galaxy S 4 Android Development] vkumar2695:
I seem to be having System UI fc's everytime my keyboard pops up or when I try to open to recents window via the home button hold on or pressing the nav button. This is on Tablet UI and whn I try to change to any other UI, it just fc's System UI again. Anyone else experiencing this?
[AT&T Samsung Galaxy S 4 Android Development] Mushroom.:
I get nothing but FC's when turning on the AOKP ribbons feature. Wouldn't go away even after turning off, had to wipe & reinstall to fix.
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I'm on the 8/21 build and I can't find the option for quick unlock with pin.
[AT&T Samsung Galaxy S 4 Android Development] mikew29:
So 8/20 or 8/21 nightly was good? Gots IR?
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I had problems with 8/20 booting but not 8/21. Followed same exact steps for each. 8/22 and 8/23 are up now, though.

Yes, IR works on both. I use Smart IR Remote and had to restore it with TiBU because it's been pulled from Play Store again, due to a copyright complaint by Touchsquid.
[AT&T Samsung Galaxy S 4 Android Development] guygreller:
cLock

How do you control the cLock widget on this rom?
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Keyboard FCs

Not since I updated to GAPPS 4.3 20130813.

Having said that, have you tried an alternative to the default keyboard? Perhaps the Google Keyboard or something like Swifkey from the Play Store?

Greg

---------- Post added at 08:00 AM ---------- Previous post was at 07:58 AM ----------

I've started experience quite a few forced closes (FC) since I went from the 8-21 nightly to the 8-22, and most recently 8-23 nightly. Did a proper wipe of cache and dalvik prior to the updates. I even run the update and re-installed gapps 4.3.

K-9 services and exchange services, among others, keep failing. Anyone else experiencing an increase in FCs since the upgrades?:crying:
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I'm getting a ton of FC's with Media, GAPPS, Play Store, Location, etc. on the 8/23 build. I also had a soft reboot. Now I have the boot issue again. Took about 20 tries to get TWRP to open.
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Yup...that exactly what I'm experiencing.
[AT&T Samsung Galaxy S 4 Android Development] guygreller:
FC

i just moved to 4.3 and had similar problem - this is not a ROM problem, this is apps specific issue.

My solution (I take no responsibility)

:

I saved my essentials from the SD card (DCIM, download) folders, backup the app data (TiBu)

Wipe my SD card in recovery and it is working ever since.

your SD may have some culprit data that doesn't play well with 4.3.

this is not fool proof solution because you are depended on the app developer to update his app to work with 4.3.

i am using secure setting (for Tasker) and since this App not updated as of yet, i will get FC. (i disabled it for now)

if the app data is important to you restore it manually, maybe this way, you will be able to identify which app causing your FC
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Are you wiping the internal SD,the external, or both? I'll try this after the weekend.
[AT&T Samsung Galaxy S 4 Android Development] guygreller:
only the internal (where you have the folder Android).
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
I am having the following issue on the latest nightly.

Baseband AMDL

Flashing with TWRP 2.5.0.2

Complete wipe

Flash rom

flash GAPPS

Rom boots up just fine, everything is working. I notice i'm not getting 4G. I go into Mobile Networks and I am on the ATT LTE pta APN, however my Network Mode is set to GSM/WCDMA. I change my network mode to LTE/GSM/WCDMA. This works and I have 4G, however if I reboot it reverts the network mode back to GSM/WCDMA.

I tried flashing KT Kernel, same results. I clean wiped and reflashed everything multiple times, same result.

I updated my radio to AMF3, wipe/flash same results.

Is anyone else having this issue?
[AT&T Samsung Galaxy S 4 Android Development] King Cole:
For the people experiencing force quits, my problem was that the GApps package the OP links to is heavily outdated. Go download the most recent GApps here and do a clean flash with that and the PAC Rom. You
[AT&T Samsung Galaxy S 4 Android Development] Mushroom.:
I don't think that is the source of the issue. I've been on the 8/13 Gapps for 4.3, and have been experiencing the fc's. They're not out of control, just once in a while, and usually from a Google app/service, like G+/ Play Store, etc.
[AT&T Samsung Galaxy S 4 Android Development] gs2usr:
That is correct, this issue has been resolved, and today's nightly should include the fix.
[AT&T Samsung Galaxy S 4 Android Development] lodidarkening:
That is awesome news. Thanks for all of your hard work gs2usr! I look forward to tonight's nightly.
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Yes, but there haven't been nighties in the jfleatt directory (at least not that I can see) in two days. Am I missing something?
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Did you find the zip?
[AT&T Samsung Galaxy S 4 Android Development] Intellectua1:
Same here I been only seeing the logs no zips.. Are the zips in another location?
[AT&T Samsung Galaxy S 4 Android Development] schergr:
So anyone have any ideas? Devs have any comments?
[AT&T Samsung Galaxy S 4 Android Development] douggiephresh:
So where have the past 2 nightlies been?
[AT&T Samsung Galaxy S 4 Android Development] Gordietm:
Please let us know if you notice any changes.
[AT&T Samsung Galaxy S 4 Android Development] dhatch93:
just flashed - got one System UI FC at startup but that's it so far... i'll install a new kernel in a minute to see if i get the splashscreen/boot animation black hole after like i did for the last few nightlies

GPS still wonky when i try to calibrate in GPS Status...

installed custom kernel - got 6 System UI FCs but working ok now...
[AT&T Samsung Galaxy S 4 Android Development] guygreller:
8/26

So far so good, no FC at all
[AT&T Samsung Galaxy S 4 Android Development] MrPlNK:
So i clean installed latest nightly, off break i had keyboard FC, got swift key installed and still have the FC, also have had about 2 system UI FC and has hung on Samsung boot logo before the rom boot logo.. No kernel flashed or anything.

What is the aosp keyboard called so i can delete it and stop these FC
[AT&T Samsung Galaxy S 4 Android Development] ripper4209:
Try using the update gapps for 4.3 on goo if you're having problems.
[AT&T Samsung Galaxy S 4 Android Development] evodon84:
Running the new nightly on a clean flash and no errors at all

fone
[AT&T Samsung Galaxy S 4 Android Development] Vaygr:
Last night's(08/26) is the most stable nightly I've installed so far. Gapps FC is definitely gone.
[AT&T Samsung Galaxy S 4 Android Development] disturbd1:
No idea whether this could be related to restored data from TB, or my Google account, or just dumb luck....but I haven't been able to get ANY push notifications from anything other than occasional Facebook pushes. Any ideas?
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Clean flash of 8/26 is sweet!
[AT&T Samsung Galaxy S 4 Android Development] lodidarkening:
Performed a clean flash of 8/26 this morning and have not had a single fc. Also I know benchmarks aren't everything but the quadrant score did go up from the 4.2 rc1. Super excited to finally catch up to you guys in 4.3.
[AT&T Samsung Galaxy S 4 Android Development] schergr:
8/27 Nightly

Looks like the 8/27 nightly didn't make it out of the shoot last night. Wonder what happened.
[AT&T Samsung Galaxy S 4 Android Development] schergr:
Anyone having issues with the status bar disappearing since 8/26. Also, a few random hard reboots as well. Hopefully resolved in the next nightly, although nothing on 8/27 and nothing yet today. Not even a build log.
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
I did have a few reboots when I tried to use the camera and the gallery. I wiped cache/dalvik and fixed permissions and it seemed to clear up. Hoping for a bug free day, still on 8/26.
[AT&T Samsung Galaxy S 4 Android Development] guygreller:
I noticed the status bar as well randomly and always during a call
[AT&T Samsung Galaxy S 4 Android Development] buggerritt:
Went a full day with no problems. I did notice that there are a few things that the build doesn't like. Rebooting from within any app seems to make it not boot. Quick boot does this as well as when any other app asks you "would you like to reboot now" and a button to reboot is clicked on. Also, I tried installing a few different fonts with font installer from within ROM Toolbox Pro and it kept the phone from booting. I had to restore a nandroid to get it to boot again. wiping cache/dalvik and fixing permissions would not fix it. I'm thinknig both of these things are related to 4.3 altogether. I remember that 4.2 was problematic at first with quickboot. The app might have to update to the build.
[AT&T Samsung Galaxy S 4 Android Development] King Cole:
I still don't totally understand the deal with the nightlies only being released every 3 days, but there being logs for the changes made on a day-to-day basis. Is the dev only uploading certain ones? Anyone know?