yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] junkimchi:
One thing that's been bothering me for months now, randomly on some nightly updates, the phone just gets stuck on the Samsung splash screen and I have to pull the battery. Just checking if this happens to anyone else?
[Verizon Samsung Galaxy S 4] dmarden:
Just reading the last handful of pages, yes. Some people seem to experience this sometimes, some (like me) never do. Doesn't appear to have anything to do with CM specifically, though, as I see similar questions here and there, both AOSP and TW areas.
[Verizon Samsung Galaxy S 4] FernBch:
I did experience it at one time. I think dirty flashing the nightlies has something to do with it. When it starts happening, I manually boot into CWM, wipe cache/davlik, factory reset, flash twice, and reboot. After that everything seems fine.
[Verizon Samsung Galaxy S 4] junkimchi:
There's also something peculiar with the battery life on the past few nightlies? My S4 is losing about 6-7% per hour just standing by with only minutes of screen usage. No other apps using lot of batter either. I got a new job that is kind of underground so checking if anyone else is having similar issues.
[Verizon Samsung Galaxy S 4] Chris123NT:
Oh boy, get ready for the next nightly, I just ran a build that gets stuck on Starting apps... after a dirty flash, I think they broke something big time lol.
[Verizon Samsung Galaxy S 4] scarmon25:
They may not have had everything merged they needed for the changer they're after.
[Verizon Samsung Galaxy S 4] stickperson:
I currently have the 10/16 nightly installed. My phone was running super slow so I was going to erase and start with a fresh install, so I tried booting into recovery (TWRP). My phone froze at the TWRP logo. I tried restarting my phone, but it constantly tried to boot into recovery. Any idea what I can do?

Also, it was really low on battery so I have it charging. There's no status light though (phone is turned off). Does that mean anything?

edit: The bootloader finally loaded after hours. I rolled back to an earlier nightly after doing a factory reset, but my phone is still loading very, very slowly. For instance, when I try to wake my phone it takes about 5 seconds for the screen to turn on or sometimes doesn't at all/sometimes reboots. I got a message earlier when installing apps saying my internal storage was running low. It's around 2.24gb right now. Could this be the cause of my problems? If so how can I go about fixing it? Thanks so much.
[Verizon Samsung Galaxy S 4] Lw00d:
do you have a custom kernel? give us more info on what mods you have .

i suggest a clean flash of the latest nightly.
[Verizon Samsung Galaxy S 4] stickperson:
I flashed back to 10.1-20130809 version because the 10.2-20131016 was giving me problems. Current kernel is 3.4.0-cyanogenmod-gfbaa5c7 dp@build-vm #1 from Aug 9. I wanted to upload a screenshot but had to flash in gapps, now the phone won't boot into recovery.

Do you think it's the build or something with my memory? I originally upgraded just for the sake of doing it. That's when I ran into these problems, so I went back to the 8/9 10.1 thinking 10.2 did something to my phone. I'm getting problems regardless of builds though. When I flash, I just do factory reset in TWRP. Should I do an advanced wipe and wipe everything (maybe except my SD card contents?)

edit: I just noticed another odd thing. I was trying to reboot into recovery, so I went into Settings-System-Power Menu and made sure "Reboot menu" was checked. None of the options came up though, only reboot.
[Verizon Samsung Galaxy S 4] ITGuy11:
I am also losing battery very fast with the phone just sitting with the screen off. Phone Idle is eating battery 8-10% per hour. Just started happening a couple of nightlies ago.
[Verizon Samsung Galaxy S 4] Nath5:
I an also seeing really bad battery drain in addition to the force closes ( YouTube force closes when the phone starts up every time). I am using faux with the settings in the first post.
[Verizon Samsung Galaxy S 4] Chris123NT:
Those of you seeing bad battery drain, are you getting any wakelocks?
[Verizon Samsung Galaxy S 4] FernBch:
When I first began using the CM Nightlies I experienced many of the issues I have seen in the last few pages. Hang at boot logo, trouble booting into recovery, poor battery life (less than 12 hours), Youtube fc's, and a few others. I began to notice that they were more pronounced after one or two dirty flashes of the next nightly.

Usually you can dirty flash the next version without issue. That's been my experience, at any rate. Once I started clean flashing the next nightly I have had almost zero issue with each new nightly. While some may consider it a PITA to clean flash every time they get a new update I find it a more stable way to do a new version of CM for whatever reason that may be. Whatever it is, it seems as if the CM nightlies do not do so well to dirty flashing on top of the one before.

Currently I run 10.2-20131018-NIGHTLY-jfltevzw and I am noticing two issues.

First is since flashing the 10-18 nightly there is sometimes a 2-3 second delay when waking my GS4. After pressing the hard key the soft buttons light right away but there is a delay before the screen is active.

The second issue has been present for the last 5 or so nightlies. When the flash is fresh the soft menu key will bring up the menu, but soon after the only way to get to the menu is to either double tap the home screen or open the app drawer. If I open the app drawer, wait a second, then close it, soft menu key operation returns to normal for a short time.

Other than this thread and a couple others, is there a way way to "report" issues with nightlies. I know there is officially no bug reporting, but I am curious just the same.
[Verizon Samsung Galaxy S 4] scarmon25:
FWIW. I've flashed a **** ton of night lies back to back dirty and never had an issue. Also CM doesn't take bug reports on nightly builds.
[Verizon Samsung Galaxy S 4] FernBch:
Same here. I'm only talking about my personal experience, but for me, dirty flashing too many nightlies seems to make me see some of these issues as I don't when clean flashing. And that has only happened since coming to CM nightlies on the GS4.

I am aware of this, too. I was just curious if there was a way to "report" some of the things that are being experienced, even though there are no official bug reports being taken.
[Verizon Samsung Galaxy S 4] scarmon25:
Only unofficial way I know is to mention them in the IRC. freenode #sgs4
[Verizon Samsung Galaxy S 4] FernBch:
Just the answer I needed. Thanks!
[Verizon Samsung Galaxy S 4] Jacobxtyler:
Im running into the same thing. That and battery drain. Usually when im at school/work, so im assuming its my network location stuff/wifi.
[Verizon Samsung Galaxy S 4] bsimpson1:
I've always viewed the delay after pressing power on as a good thing, as it seems to indicate the device had been in deep sleep. If I let the screen shut off due to enough idle time passing and then immediately press power on, the wakeup time is basically instantaneous. If you press the power button to turn the device off, then press the power button once more right after, the delay returns, which I assume is because the fact that the user explicitly pressed the power button to turn the device off means that it can be assumed that the user no longer desires to use the phone (otherwise, why would he have pressed the power button?) And so the device is put into a deeper sleep at once.
[Verizon Samsung Galaxy S 4] FernBch:
Never thought of that. Maybe changing the governor to On Demand will help.
[Verizon Samsung Galaxy S 4] theRG:
Are there any tips on improving battery life? Maybe a kernel recommendation. I'm coming from TW roms (CleanROM/BoneStock) and got accustomed to the great battery life those provided.
[Verizon Samsung Galaxy S 4] crossen0:
Turn off Google now. I've seen significant improvement in one day without it on. I'm a delivery driver so it makes a difference.
[Verizon Samsung Galaxy S 4] junkimchi:
flashed the latest nightly, got 2 random reboots so far within like 5 minutes...

edit: just got another one. reverting back to an earlier nightly this one seems unusuable.
[Verizon Samsung Galaxy S 4] dmarden:
No issues like that on my end. Hopefully you can find a resolution.
[Verizon Samsung Galaxy S 4] scarmon25:
I have had nothing but a solid build. Battery is good. Performance is good. I haven't messed with anything other than just installing my apps.
[Verizon Samsung Galaxy S 4] Chris123NT:
Can you get a last_kmsg next time it happens please
[Verizon Samsung Galaxy S 4] gotroot801:
When the drain was at its worst for me last week, I saw a lot of wlan_rx_wake.
[Verizon Samsung Galaxy S 4] dmarden:
You should use an app like BetterBatteryStats to show you what apps are initiating those sorts of things. For example, a week or two ago I was seeing a large amount of network activity (though little actual traffic) and BBS revealed that Google+'s auto sync feature was running constantly, even when there were no new images to sync.
[Verizon Samsung Galaxy S 4] gotroot801:
BBS is what let me know what kernel wakelock was the culprit. I'll pull the app data once I've had a normal day.
[Verizon Samsung Galaxy S 4] scarmon25:
What I would suggest to anyone having issues. Flash a stock ROM after wiping data. Let it boot long enough to pull in any new network info and junk. Then boot back into recovery and wipe data and flash CM and Gapps. Don't flash any other kernels or anything like that. Just CM itself. Resintall your apps through the market, I know its a PITA, but trust me it will make for a very nice clean install. And check it from there. Anytime I switch Roms that is exactly what I do. I get good battery and everything seems to always work right. Just my two cents anyway.
[Verizon Samsung Galaxy S 4] chillware:
I'm getting the same issue on 10/21 build. my phone reboots within minutes of being up. am also going to try going back to 10/20
[Verizon Samsung Galaxy S 4] scarmon25:
I wonder why. I haven't had a single reboot since I flashed the latest build.
[Verizon Samsung Galaxy S 4] sd0070:
I also am getting reboots. Going back to last build now.
[Verizon Samsung Galaxy S 4] bkrickles:
quick question from an idiot (yeah me)

I flashed the wrong kernel by accident and my phone is in a constant boot loop

How do I get back into recovery

I tried vol up and power and it just went into my boot loop

vol down and power put me into odin, I think

any advice would be greatly; appreciated
[Verizon Samsung Galaxy S 4] chillware:
went back to 10/20 and it has been running smooth, no more reboot like 10/21.
[Verizon Samsung Galaxy S 4] dmarden:
It's power, home, and volume up.
[Verizon Samsung Galaxy S 4] dougmod:
try doing it a few times. so hold vol up and power and release when you see it says booting to recovery. it prob wont go in. but right after you release, hold it again to catch it on the next couple of loops
[Verizon Samsung Galaxy S 4] bkrickles:
I'm pressing all three simultaneously and I keep going to my never ending boot animation

I keep pulling battery, holding power, home and volume up

do I keep holding it even after vibration or let go as soon as it vibrates?

thanks guys
[Verizon Samsung Galaxy S 4] dmarden:
All 3 until vibrate, then release power until you see the blue loading recovery text, then release the last 2.
[Verizon Samsung Galaxy S 4] bkrickles:
thank you thank you thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

I had to do it like 8 times but it finally worked

I get so crazy when I do stupid crap like this

And my wife wants to kill me too......

what a great resource these forums are

sorry to hijack but thanks again!!
[Verizon Samsung Galaxy S 4] Chris123NT:
http://review.cyanogenmod.org/#/c/52192/

Hopefully this makes it into the new nightly, but from testing the commit this is reverting seems to be the cause of the random reboots. Give it a shot tomorrow and let me know.
[Verizon Samsung Galaxy S 4] crossen0:
I hope they add it. The random reboots are what's keeping me off anything cm based. At one point I noticed if I set my phone down "hard enough" my phone would reboot itself.
[Verizon Samsung Galaxy S 4] gotroot801:
Of course, today my battery drain is closer to what it was two weeks ago: 4%/hr. I don't know if I should be happy that I'm not scraping around 60% right now or pissed that I have no actionable data for you guys...
[Verizon Samsung Galaxy S 4] dmarden:
This made me LOL hard. I wanted to just reply with something like, "Man, you're lucky... if I throw my phone against the wall it just shuts off, no reboot." ...but, lol.

I wouldn't sweat it... I'm sure you'll be ready to share info when/if it happens again. When idle, I typically lose around 1.5%/hr. Obviously everyone's phone is different as far as what they've got going on, though.
[Verizon Samsung Galaxy S 4] crossen0:
Oh it'll shut off too. Just depends on how it's "feeling" I guess. Needless to say it isn't stable enough to run as a DD at this point.
[Verizon Samsung Galaxy S 4] dmarden:
I don't have any issues with reboots, apparently there was some sort of issue with reboots when on 3G in the 10/21 nightly (which was merged and fixed for the 10/22 nightly).

If your issue is somehow really tied to physical actions like putting your phone down, I'd say that is a whole separate matter.
[Verizon Samsung Galaxy S 4] crossen0:
Probably. It's the only Rom I've encountered it on. And I'll get sleep of death sometimes too. Turn the screen off, doesn't wake up until I pull battery or hold power button.
[Verizon Samsung Galaxy S 4] dmarden:
Beyond starting fresh with a clean install and no restored apps/data and sticking with the included kernel, I don't have a ton of advice.

Start fresh and see if it happens. Don't restore anything, don't use a different kernel, etc.

If it happens there it comes down to motivation. You can produce some logs to assist in the resolution/tracking of the problem or use another ROM if you're not experiencing it there (of course).

I keep up with this thread pretty regularly and I don't think I've read anyone else having reboot issues tied to putting the phone down or other normal physical movements. Perhaps you have some app installed that triggers actions based on that sort of thing? I really am only guessing, though.
[Verizon Samsung Galaxy S 4] sd0070:
I was getting reboots on WiFi/4g

SG4
[Verizon Samsung Galaxy S 4] just4747:
Ok apparently search function doesn't work - how come whenever I try to flash any version of the S4 developer edition boot animation, I just see a white horizontal rectangle over a black background at boot?

I've never had a problem changing animations before.

I even tried with the 421 enable custom animation zip I had from a while back for S4s first and still doesn't work.
[Verizon Samsung Galaxy S 4] Chris123NT:
Well try today's build and make sure it's fixed.
[Verizon Samsung Galaxy S 4] sd0070:
Not getting any reboots on today's build so far. However 2 things I noticed right away are no torch toggle in quick settings (is that what was removed to stop the reboots?), and the wifi signal in notates bar doesn't turn blue to show a connection. EDIT: a reboot fixed the wifi signal...it's now blue. Still no torch toggle.
[Verizon Samsung Galaxy S 4] scarmon25:
That's odd. I have torch toggle. Edit. I have it because I had it set prior to the latest nightly. When I go into settings and look its no longer in the list.
[Verizon Samsung Galaxy S 4] sd0070:
10/22 clean install I got no torch toggle. Did you dirty flash... if that would even matter?

I also notice I'm not getting 4g, just 3g, at home where I've never had signal issues before
[Verizon Samsung Galaxy S 4] scarmon25:
I edited my post.
[Verizon Samsung Galaxy S 4] Lw00d:
what???:crying: no torch.. i always use torch. in the Notification drawer settings.
[Verizon Samsung Galaxy S 4] sd0070:
Flashed again and still no 4g (or torch toggle obv). Went back to 10/20, and torch option is there. I also get 4g on the 10/20 build
[Verizon Samsung Galaxy S 4] scarmon25:
Yeah the torch option is gone. Haven't had a chance to test 4,G
[Verizon Samsung Galaxy S 4] Chris123NT:
Do you guys have a GPS option or is that gone too?
[Verizon Samsung Galaxy S 4] scarmon25:
GPS is still in the list.
[Verizon Samsung Galaxy S 4] d11dog11:
Torch toggle is still there for me on the 22 build after a dirty flash.
[Verizon Samsung Galaxy S 4] Chris123NT:
Fix for torch toggle is merged :good:
[Verizon Samsung Galaxy S 4] kvirus11:
4G is still broken on 10/23 FYI
[Verizon Samsung Galaxy S 4] scarmon25:
I'm at work and have LTE.
[Verizon Samsung Galaxy S 4] just4747:
Ahhh someone please help I cannot get a boot animation to work!!

Also, is there a way to get rid of the (what I think is) the tinted shade on the lockscreen? It seems dark to me..
[Verizon Samsung Galaxy S 4] kvirus11:
Just flashed 10/23 clean from PA and have 3G only. I haven't had the 3G on this phone since purchase.

Both CM nightly and Euro nightly-no 4G

EDIT: It just came back up. I'll go and stand in the corner now...
[Verizon Samsung Galaxy S 4] scarmon25:
LOL
[Verizon Samsung Galaxy S 4] kvirus11:
I have the water dept tearing up my lawn outside and I didn't notice until just now the presidential caravan of Verizon vehicles all over the area.

Rule number one: Do NOT report bugs on nightlies.....so into the corner I go...
[Verizon Samsung Galaxy S 4] scarmon25:
Hahaha. Its all good. Its not really bug reporting in here. Its mentioning things we see they might not know about. Even though most of the maintainers don't post here they still look through the threads from time to time.
[Verizon Samsung Galaxy S 4] ItsAaronR:
Has anyone else experienced a problem with the camera, after taking a picture the GPS icon stays in the notification bar, and if you go back into the camera app it shows it never closed, freezes and crashes? Seems like it started happening after the build from the 17th.
[Verizon Samsung Galaxy S 4] Lw00d:
yes i have that issue on 10/18 . i am going to flash 10/23 hopefully its fix.
[Verizon Samsung Galaxy S 4] resurektz:
Anyone know if the new nightly fixes random reboots?
[Verizon Samsung Galaxy S 4] d11dog11:
Been in it all day. No reboots so far
[Verizon Samsung Galaxy S 4] SonicJoe:
I can't get the 24th nightly to boot past the Samsung splash screen. Anyone else?
[Verizon Samsung Galaxy S 4] Chris123NT:
Did you try a battery pull?
[Verizon Samsung Galaxy S 4] SonicJoe:
Yes. 3 times just to make sure. Flashed back to the 23rd and all is fine.
[Verizon Samsung Galaxy S 4] SonicJoe:
I can confirm that messaging and notifications work fine for me.

I only use the stock app. Maybe the third-party apps are interfering?
[Verizon Samsung Galaxy S 4] mrtruckincowboy:
Yes some good stuff so far

Truckin's Galaxy S4 (cm 10.1)
[Verizon Samsung Galaxy S 4] keithce:
Agreed, I haven't seen any delays and I'm only using the stock app.
[Verizon Samsung Galaxy S 4] stackz07:
I wiped and installed tonight's (5th) nightly and it is stuck at Samsung Galaxy S4 boot screen. So i tried again and did a full system format and still stuck at lock screen, this happens for both Jellybeans and Cyanogen Mod. But slimbean is working great...???
[Verizon Samsung Galaxy S 4] thejondude:
Try any flash an aosp kernel if it formatting SD card I've had issues booting until I flashed a new kernel ... Worth a shot
[Verizon Samsung Galaxy S 4] stackz07:
Ok I flashed a new kernal a while back when jellybeans wasn't booting. i just formatted a few times and factory reset a few times with reboots in between. seemed to have work. if i flash cyanogen mod and it gets stuck is there a specific kernel i should try?
[Verizon Samsung Galaxy S 4] TechSavvy2:
Do you have a loki-fied recovery installed?
[Verizon Samsung Galaxy S 4] xXPrOwLeRXx:
Pie Controls

Can anyone verify if pie controls are working? I tried to install the script to get them enabled and I still do not see the option in the settings. Also has anyone been having issue with linking their Avast account in the Anti-theft agent?
[Verizon Samsung Galaxy S 4] calikorban:
CM 10.1 vs touchwiz avaliable space

I know there is a nice sd card slot but one thing i was expecting was to have additional space that touchwiz took up that would have been freed up with cm. To me it looked about the same.
[Verizon Samsung Galaxy S 4] arcanexvi:
The partition tables are still intact and will not be altered. Basically the area that cm is installed to has a bunch of extra space but isn't allocated for your use. Unfortunately there isn't a way to fix this easily.
[Verizon Samsung Galaxy S 4] SonicJoe:
The partitions are fixed sizes. Even though CM is a lot smaller, that space is reserved by the device. No ROM will give you that space back.

Edit: ninja'd

---------- Post added at 01:05 PM ---------- Previous post was at 01:00 PM ----------

For those who complained about the pictures being in 4:3 resolutions only, I was able to mod and rebuild the camera with the correct resolution. The only problem is I deleted my stock ROM backup, and I only took two pictures (both 8MP) so I don't have all the correct resolutions for each mode. Can someone please provide me the resolutions for each resolution? For example, 8MP is 4128x2322.
[Verizon Samsung Galaxy S 4] puma1:
deleted
[Verizon Samsung Galaxy S 4] csstamatin:
4128x3096. At least thays what it says in the camera app.
[Verizon Samsung Galaxy S 4] ushneb:
Just got my Note 2 yesterday and installed CM 10.1 nightly from 6/5. Today when I tried to make a call the celular connection cuts out and android.phone or whatever it's called crashes. Dunno what's going on. Anyone else experience this?
[Verizon Samsung Galaxy S 4] SonicJoe:
For which resolution?
[Verizon Samsung Galaxy S 4] dickenam:
Hopefully you installed CM10.1 for the Note 2 on your Note 2...

This is for the S4?
[Verizon Samsung Galaxy S 4] ushneb:
Oops, I posted in the wrong forum thread, my bad. But yes, I did install CM for Note 2 on my Note 2. lol
[Verizon Samsung Galaxy S 4] js2shanks:
Went from Stock rooted to CM 10.1, fast and stable but I have found some problems with it

1. GPS does not lock, I tried to fix seen in the thread it does not work

2. Screen off/ on lags a lot takes a while to turn off and power back on my screen

3. Youtube Video when watching it in landscape it gives a border around the video, and will not show full screen which is odd stock rom it showed at full screen.

Any suggestions?
[Verizon Samsung Galaxy S 4] stackz07:
I do. I have twrp installed through goo.im which is loki enabled. I have slimbean running now but I want to try Cyanogenmod but am scared to mess with it now. Do you think since it's fixed and running ok now if i do a proper flash (wipe, flash etc) I'll be successful in getting it to boot?
[Verizon Samsung Galaxy S 4] puma1:
dumb question: how do you take a screenshot with this rom? home + power does not work.
[Verizon Samsung Galaxy S 4] Slim1023:
I've been having that issue on the last few nightlies. Which recovery do you use? My issues started when I updated to CWM 6.0.4.4 a few days ago.

Also, for me, a battery pull used to do the trick to get it to boot. This morning on the 10-24 I had to pull battery, boot into recovery and flash. That worked ok.
[Verizon Samsung Galaxy S 4] SonicJoe:
I've been using CWM 6.0.4.4 since it came out.
[Verizon Samsung Galaxy S 4] Chris123NT:
Anyone unable to send texts on the latest nightly or did I just repo sync at a bad time last night?
[Verizon Samsung Galaxy S 4] scarmon25:
Sending and recieveing just fine.
[Verizon Samsung Galaxy S 4] cynicalirony:
No issues here with text messages.
[Verizon Samsung Galaxy S 4] Chris123NT:
Maybe it's because i use a 3rd party sms app (textra). Notice a commit went in to "fix" sms middleware, it probably broke it. :laugh:
[Verizon Samsung Galaxy S 4] scarmon25:
Very well could be it.
[Verizon Samsung Galaxy S 4] dmarden:
Not that it's the same app, but I use Facebook Messenger for SMS and it seems to still be working ok.