yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] PorchSong:
[MENTION=7810360]nine7nine[/MENTION]

I do not know if you saw my post from a couple of days ago. But is the LightSensor suppose to nonstop poll in low light to dark conditions? Load up logcat and cover your front camera and watch the polling go crazy--as in 4-5 polls a second. The second you uncover the camera/sensor it immediately stops. Could this be a cause of excessive battery drain?

---------- Post added at 08:16 AM ---------- Previous post was at 08:09 AM ----------

Or you could have four Egyptian slaves carry your car old school like a throne. Look, riding on a rim is silly and your car is still not functioning properly. Putting on a spare means you have a flat--which we do not. This still doesn't make your analogy proper. But I get it, you are one of those people who refuse to admit they are ever wrong and will argue nonsense into the ground rather than say, "You know, it was probably not the best analogy."
[Samsung Galaxy S 5 Unified Development] :
...but it does absolutely nothing to fix the actual underlying problem. Please, take a moment to read and compute what someone is saying before commenting;

There's nothing wrong with installing adaptive rotation app to workaround the rotation problem and I never said that there was. :\ ... However, some of us actually have the source code in front of us, and thus would prefer to try and fix the actual problem, if possible (which benefits everyone) -> rather than just waiting for someone else to do it;

..and how exactly do you think 'known issues' get fixed? Hint: they don't get fixed when everyone just uses an app to hack around it, while they wait for someone else to fix it. lol :P
[Samsung Galaxy S 5 Unified Development] thaijunk:
Maybe I should stay out of it but wanted add a comprising point to sooth out this heated debate.

I think both of you have valid points.

Users who can't stand the rotation bug, go ahead and install the app while devs figure out the underlying problem.

However if you are you do install it, consider this to fall under "hacky crap" that might cause other issues and devs will not support that.
[Samsung Galaxy S 5 Unified Development] Jaanto:
I've read somewhere back that you have to change in build prop

ro.build.type=userdebug

to

ro.build.type=user
[Samsung Galaxy S 5 Unified Development] david825234:
Been working on G900P as well...
[Samsung Galaxy S 5 Unified Development] cchri78:
Have already done that and I still have bad battery life.
[Samsung Galaxy S 5 Unified Development] htb2050:
Was it a clean flash? And did you do atleast a few charge cycles before judging battery life?
[Samsung Galaxy S 5 Unified Development] haggertk:
kltespr and klteusc GPS Test

https://www.androidfilehost.com/?w=files&flid=130156

I'm not terribly confident that this alone will fix it, but it's worth a shot. I'd like a thumbs up/down from someone with the "GPS only works on airplane mode" issue on both devices.
[Samsung Galaxy S 5 Unified Development] BrX91:
Battery icon is missing on lock-screen statusbar or I am missing something?
[Samsung Galaxy S 5 Unified Development] Rocthrower:
Thank you sir! I will test on klteusc and report.
[Samsung Galaxy S 5 Unified Development] bbeds:
Should we wipe and clean flash?

kltespr
[Samsung Galaxy S 5 Unified Development] haggertk:
For this kind of change, you *shouldn't* have to. That said, if you don't mind doing it I certainly won't say no.
[Samsung Galaxy S 5 Unified Development] bbeds:
No prob. Wiped and clean flash and still getting 0 SATs unless on airplane mode. Thanks for giving it a shot. Appreciate your work.
[Samsung Galaxy S 5 Unified Development] cchri78:
Yes it is a clean flash and I lost 10% over night and yes I have done a few cycles.
[Samsung Galaxy S 5 Unified Development] :
[MENTION=2693412]haggertk[/MENTION] - Slightly O.T, but maybe more relevant down the line;

So I think SDCLANG may be problematic on KLTE, depending... Through my journey of getting DEXPREOPT/odexing working on my rom, I definitely ran into problems due to using SDCLANG. - It tended to cause bootloops.... I seem to recall in the Qualcomm compiler Lollipop XDA thread, that it was possibly related to compiling ART with SDCLANG, obviously that info is dated, but not necessarily irrelevant. So I'm avoiding using SDCLANG for the foreseeable future, as I've got a fully-odexed cm14 rom working, using the standard CLANG toolchain....

idk if down the line you are considering switching to SDCLANG or not, but there does seem to be some stability issues depending on other factors... It would be nice to test SDCLANG, but exclude ART from using it and do a comparison - it wasn't obvious to me on how to do that though. Maybe something to explore later.... Anyway, I just thought I would mention it as maybe other CM device devs are exploring similar things and you obviously talk to more of them then I do! ;)
[Samsung Galaxy S 5 Unified Development] david825234:
Clean installed your test build and can confirm it doesn't work unless on airplane work. Thanks for giving it a shot, though.

KLTESPR
[Samsung Galaxy S 5 Unified Development] haggertk:
We've been using sdclang since nightlies started. I haven't had any bootloops.

https://review.cyanogenmod.org/#/c/169999/

To exclude a particular target you need to edit that target's Android.mk like was done here:

https://review.cyanogenmod.org/#/c/170335/

Make sure that you are using the latest sdclang. They have had several releases in the last 6 weeks or so. Also, if you can definitively nail down a failure related to sdclang Qualcomm is apparently receptive to bug reports and will incorporate fixes.
[Samsung Galaxy S 5 Unified Development] Rocthrower:
I did a clean install of the test build for klteusc, and the GPS problem still persists. Only working in airplane mode. I really appreciate your efforst, and wish I could contribute more. In the meantime, I will happily keep testing builds.
[Samsung Galaxy S 5 Unified Development] :
Ah, maybe i'm not using the lastest release, I update a couple of weeks ago, but I should update again / keep right on top of it.

No, you wouldn't / i didn't get bootloops until adding;

WITH_DEXPREOPT := true

WITH_DEXPREOPT_PIC := true

WITH_DEXPREOPT_BOOT_IMG_ONLY := false

Standard CLANG works fine, while SDCLANG ends up blowing chunks. lol... But I should test this again on the latest SDCLANG, maybe there are rlevant fixes, since my last update.... Thanks for the tip on disabling SDCLANG, if the latest SDCLANG doesn't fix the issue with odexing, I will want to try excluding ART to test... cheers!
[Samsung Galaxy S 5 Unified Development] haggertk:
Well, damn near everyone is getting crapped on with that :)

https://review.cyanogenmod.org/#/c/170351/

https://review.cyanogenmod.org/#/c/171820/

If you can nail down a variable then post a comment to one of the changes. As it stands, CM is immediately backing away (again) from DEXPREOPT.
[Samsung Galaxy S 5 Unified Development] :
Hmm... Interesting. without going into too much detail (here), my odexed cm14 rom does have some differences pertaining to dexpreopt. I have some changes in ART and platform_build ~> I'll need to see If i can isolate it down to a change or two that are specifically causing the issues observed on CM (as my rom is really a combo of CM and CopperheadOS, so I do have some slightly more invasive changes not found in CM).

I'll also need to test with the latest SDCLANG, but if i can narrow it down, I'll let the CM guys know... At least for now, I DO have DEXPREOPT working with standard CLANG on klte (fully odexed system), so it IS possible.
[Samsung Galaxy S 5 Unified Development] lexridge:
I also still have no GPS except in Airplane mode with this version. Dirty flash, PF2 Baseband.

klteusc
[Samsung Galaxy S 5 Unified Development] isaactsg:
Just dirty flashed the newest ngihtly (11/17) over 11/15 on my GM-900W8, I'm getting reboots as soon as it hits the lock screen when I first boot. I've reverted back to (11/15).
[Samsung Galaxy S 5 Unified Development] aogakid:
didnt understand... is latest build working?
[Samsung Galaxy S 5 Unified Development] :
hmmm. I hit that yesterday too, but I thought it was due to a change in my own build, maybe not...

Can you remember if it happened as soon as wifi and/or data connected?
[Samsung Galaxy S 5 Unified Development] haggertk:
kltespr and klteusc GPS Test Round 2

I'm kind of slinging crap at the wall right now. These aren't full ROMs, but rather just some select blobs that can be flashed overtop of your current install. I'd like spr and usc users to first select the zip file that matches your phone. These are L blobs, which is what you had in cm-13.0. This might result in no satellites even in airplane mode if it behaves like my F, but I'm up for being surprised.

If that doesn't work, try the vzw blobs.

Link would help...

https://www.androidfilehost.com/?w=files&flid=130195

Please report success/failure. If this doesn't work re-flashing your current full build will put you back to where you were previously.
[Samsung Galaxy S 5 Unified Development] brandon79:
Same problem others have posted dirty flashed 11/18/2016 kltevzw on SMS902L and as soon as it gets to lock screen it reboots. Dirty flashed back to 11/16/2016 and its good again just thought I would post my results for the latest kltevzw
[Samsung Galaxy S 5 Unified Development] dyval:
Klte 20161118 boots only up to the lockscreen, then it will immediately reboots back to bootanimation. Flashed back 20161115 build.
[Samsung Galaxy S 5 Unified Development] haggertk:
Crap, the builds kicked before the DEXPREOPT change got reverted...

(https://review.cyanogenmod.org/#/c/171820)

EVERYBODY, wait until 19 Nov or later.
[Samsung Galaxy S 5 Unified Development] bbeds:
So the SPR blob gave me no SATs even in airplane mode. The VZW worked the same a previously with SATs only on airplane mode.

Again thanks for your work on this.
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
Same here. 1118 is broken. Causes bootloop. Reverted back to 1116.
[Samsung Galaxy S 5 Unified Development] RemusW:
Confirmed,

Constantly reboots on 11/18 nightly. Am using S5 klte. Reverting to 11/17.
[Samsung Galaxy S 5 Unified Development] david825234:
I've been at work so I couldn't flash the spr round 2 myself. But since it looks like someone else did it, I guess I'll wait for round 3 and hopefully I'll see the post sooner. But I might not see it since I might be at work from 9am-6pm eastern.
[Samsung Galaxy S 5 Unified Development] Rocthrower:
Same here. USC gave me a "no gps device found" message or something similar, and VZW the satellites only worked in airplane mode.
[Samsung Galaxy S 5 Unified Development] MrTrumpz:
How hard would it be to make it compatible with other variants? I don't think the developer will work on other variants as from what I can remember he does not own those phones hence he cannot test on them.
[Samsung Galaxy S 5 Unified Development] isaactsg:
I think it was when it connected to cell signal. But I'm not 100% sure.
[Samsung Galaxy S 5 Unified Development] haggertk:
Realistically, the differences between western variants are very minor and most are not even 100% required. I haven't looked at Andi's kernel config, but his old ones ensured compatibility with both pn547 and brcm nfc chipsets, which is the one real difference.

The real message is that he is busy and won't accept bug reports for other devices in the case of incompatibilities.

Flash at your own risk. And don't note a bug here if you are using a kernel other than the CM stock one.
[Samsung Galaxy S 5 Unified Development] :
Well, I'm 99.9% sure that the reboot is caused by not only the DEXPREOPT code not being reverted, but specifically as soon as wifi and or cell/data starts it hits an selinux denial... Background;

I've been experimenting with DEXPREOPT and I bumped into that issue yesterday, before CM enabled the problematic code that ended up on your device (interesting timing. lol). it took me a couple of tries, but after quickly switching to airplane mode on boot, the device no longer rebooted. I ended up changing an selinux policy that fixed the issue on my next build.

[MENTION=2693412]haggertk[/MENTION]

So I have a build (DEXPROPT'd + SDCLANG) that seems to be working okay, but it's not perfect. Occasionally, after installing a bunch of apps, it will hang on the next boot. Oddly, if I then go into twrp and restore it's boot.img, then it usually will boot => I'm not exactly sure why that is (?) -> I do remember in the past on CM, that my old htc wouldn't boot after updating the rom, unless I flashed the boot.img separately.... seems kind of familiar to me!

I've also picked a couple of commits from AOSP/sepolicy (one directly related to dexpreopt that was causing bootloops on some devices, apparently). Currently, I am also not using ART JIT/profiling, but i'm planning to test that next though. So for the most part, I do have it working well, manual intervention aside, but there still seems to be the odd bump to iron out yet.
[Samsung Galaxy S 5 Unified Development] bbernardini:
Also repeatedly rebooting on the Nexus 7 (2013) build. Looks like it might be a problem across the board.
[Samsung Galaxy S 5 Unified Development] soyimparable:
+1

Enviado desde mi SM-G900T mediante Tapatalk
[Samsung Galaxy S 5 Unified Development] dyval:
Downloading 20161119 build for klte. I hope this one will boot. I'll let you know guys [MENTION=2693412]haggertk[/MENTION] [MENTION=7810360]nine7nine[/MENTION].
[Samsung Galaxy S 5 Unified Development] notentirelysure85:
I am watching with great anticipation. Downloading cm-14.1-20161119-NIGHTLY-kltedv.zip for me. Fingers crossed.
[Samsung Galaxy S 5 Unified Development] Dieexe:
Latest nightly working just ok
[Samsung Galaxy S 5 Unified Development] notentirelysure85:
Latest nightly working great for me too on kltedv. My adopted storage is fixed! Thanks! :)
[Samsung Galaxy S 5 Unified Development] david825234:
11/19 build works fine. This is mostly the 11/16 build. Quite awful battery life. I'm going to do a clean install and stop using that other Kernel for the day.

---------- Post added at 01:24 AM ---------- Previous post was at 01:20 AM ----------

And somehow it completely died? Plugged it into the wall and it said 0% pre boot...
[Samsung Galaxy S 5 Unified Development] rayzen6:
[MENTION=7810360]nine7nine[/MENTION]

I found something that maybe useful for rotation issue. Idk if it has been already tried.

https://github.com/CyanogenMod/andr.../cm-14.1/core/res/res/values/config.xml#L2718
[Samsung Galaxy S 5 Unified Development] SB4BBs:
I'm using 11/15 unofficial build of haggertk, screen rotation seems to work with the temp fix. Battery life is a mixed bag for me. I'm with Koodo mobile and sometimes it will connect to Rogers Network. I've been playing with the APNs and I don't always get LTE. I downgraded from twrp 3.0.2 to 3.0.1 seems to improve a little bit when it comes to signal. It was an issue since cm13.
[Samsung Galaxy S 5 Unified Development] dyval:
klte 20161119-nightly boots. :good:
[Samsung Galaxy S 5 Unified Development] itsclarence63:
Same here... Klte boots
[Samsung Galaxy S 5 Unified Development] Rumple007:
Whats the SOT? Thank you
[Samsung Galaxy S 5 Unified Development] gerrycooper:
sim2 is muted for g900fd on the latest official builds cm-14.1-20161119, cm-14.1-20161118 and cm-14.1-20161116.

The first official build cm-14.1-20161113 works finde for sim2. [MENTION=2693412]haggertk[/MENTION]: Is the msim change not part in the last builds?
[Samsung Galaxy S 5 Unified Development] :
I think u need to be more specific... I'm familiar with the config.XML ur pointing out, but I don't follow you, on what u want me to try.

---------- Post added at 08:21 AM ---------- Previous post was at 08:18 AM ----------

It was a temp issue, all of the klte's should boot fine... The build servers just happened to start the last builds before a derpy commit got reverted...
[Samsung Galaxy S 5 Unified Development] rayzen6:
Did you enable system clock rotation thing?
[Samsung Galaxy S 5 Unified Development] :
Ya, that was already discussed further back in the thread, read back.
[Samsung Galaxy S 5 Unified Development] DJ-Studd:
First time fresh install of cm-14.1-20161119-NIGHTLY-kltedv, previously running CM13.

It's only been a few hours, but it feels nice! :D

---------- Post added at 08:19 PM ---------- Previous post was at 07:51 PM ----------

Battery status as text in the status bar, pin lock enabled, hide sensitive notifications on lock screen enabled. The battery status does not show in the status bar when the phone is on the lock screen.
[Samsung Galaxy S 5 Unified Development] muubase:
Same here. Everything else perfect.
[Samsung Galaxy S 5 Unified Development] bekolya:
He just didn't test it on G900FD. It has similair specs with G900F and a lot of stuff works here as well. I'm proving, that this kernel works on G900FD like charm and everyone, who is interested can try it too.
[Samsung Galaxy S 5 Unified Development] Cedric0303:
Is it just me or fingerprint scanner is broke in latest nightly (20161119) on klte (clean flash)
[Samsung Galaxy S 5 Unified Development] rodrigo.fac:
It's working for me.
[Samsung Galaxy S 5 Unified Development] lickwid:
Currently on 11/16 nightly for G900V, kltevzw. My phone has been experiencing reboots/boot loops once the battery gets down to around 15%. Plugged power in and for the most part it was fine to boot back up. Right now, I'm stuck. Boots up, but when trying to type in my pw on first boot, the keyboard pops up the Google Now microphone instead. Doesn't allow me to type anything. Phone appears to be functioning otherwise since notifications pop up, but since I can't unlock, I'm pretty much stuck at the lock screen. This is running Google Keyboard with open gaps full. Any trick to get around this?

I tried going into TWRP to reflash gapps, but since I have internal adoptable storage setup, the data files in download folder sit on the "external" portion of the storage and doesn't show up in TWRP. I only see about 5689MB in there when my eternal SD card is 64GB. Any tips? Thank you.

UPDATED: I had to reflash TWRP 3.0.2.-2 in Odin and now it recognizes my adoptable storage. Will try to reflash Gapps now to see if it fixes anything. At worse, looks like I will have to wipe, reflash rom and gapps.

That didn't work. Will try to dirty clash the nightly from 11/18 and gapps mini.
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
So I attempted to install 1119 three times dirty and twice clean and every time it just hangs at like 80% while installing system image unconditionally. I let it sit for about 45 minutes and it never finishes. Had to go back to 1116.
[Samsung Galaxy S 5 Unified Development] jt1975:
Maybe a bad download?
[Samsung Galaxy S 5 Unified Development] GGTheGooch:
Possibly. I'll give it another shot.

---------- Post added at 11:44 AM ---------- Previous post was at 11:21 AM ----------

OK it was a bad download. I downloaded 1119 from cm downloads and it boots. Still no GPS, but the negative storage and landscape issues seem to be fixed.
[Samsung Galaxy S 5 Unified Development] andrewrvincent:
I am on the VZW S5 and had to do a complete wipe to flash the 11/19 build - dirty flash caused a boot loop (I gave it about 15 mins) - flashed like a charm after complete wipe - flashing gapps now - fingers crossed.

Thanks for all the work - all you developers make it so this 43 yr old cop can stay on the bleeding edge
[Samsung Galaxy S 5 Unified Development] :
[MENTION=2693412]haggertk[/MENTION]

I've been checking 'adb bugreport' in a few of my builds now and I am noticing this, fairly consistently;

<3>[ 1.783777] mmc0: sdhci_msm_execute_tuning: cmd error (-84)
<3>[ 1.785848] mmc0: sdhci_msm_execute_tuning: data error (-84)

Why it is getting my attention is that I've noticed that sometimes I am getting the 'android is optimizing storage' after flashing and while most of the time it takes no time to finish, the odd time it just hangs (next boot works fine though). I also noticed that on my SDLCANG/DEXPREOPT builds, if i get a bootloop, removing the sdcard while it boots completely avoids the bootloop (?).... idk if it is my sdcard causing a slight issue (nothing fnacy just a 16g SanDisk) or whether (more likely?) there is a problem in the kernel with sdhci_msm....? (maybe a subtle bug introduced from linux-stable, idk.)
[Samsung Galaxy S 5 Unified Development] Swiss Cheese:
I have clean flashed 11/19 twice an am unable to get Busybox to install. Any suggestions?
[Samsung Galaxy S 5 Unified Development] :
Which busybox are u using? .... there are multiple versions in play store and elsewher (and not all are equal quality;))

I always use this one;

https://f-droid.org/repository/browse/?fdfilter=busybox&fdid=ru.meefik.busybox

It's always updated, never had any problems with it and is a full version of busybox, no need to pay someone on play store for their so-called 'pro' versions. ....just make sure root is enabled in developer settings.
[Samsung Galaxy S 5 Unified Development] bbeds:
Maybe I'm doing something wrong but i get a "problem parsing package" error when trying to install that.
[Samsung Galaxy S 5 Unified Development] BrX91:
Make sure that you have storage permission for system app "package installer". For some reason it sometimes loses it, and parsing problem is shown.

Wysłane z mojego SM-G900F
[Samsung Galaxy S 5 Unified Development] :
That is odd. I definitely don't.... I even just tried downloading and installing from the website and it worked fine.... Usually, I would use f-droid to install it though... idk, maybe there was a problem with the download (like it got corrupted?).

i suppose you could try f-droid and see if it makes a difference?

interesting, I've never encountered that. good to know, if I personally every bump into that.
[Samsung Galaxy S 5 Unified Development] bbeds:
I tried both f-droid and just the busy box apk. Will check permissions on package installer next and go from there.
[Samsung Galaxy S 5 Unified Development] bbeds:
Package installer has no requested no permissions.

Any idea how to fix that?
[Samsung Galaxy S 5 Unified Development] bbeds:
Must have been bad download I'm guessing all is working now.
[Samsung Galaxy S 5 Unified Development] :
Good. I thought that might be the case :) ... I think I bumped into a chromium apk downloaded manually that couldn't parse, at one point...
[Samsung Galaxy S 5 Unified Development] Swiss Cheese:
I have been using Stericson. Yours worked flawlessly.
[Samsung Galaxy S 5 Unified Development] :
good. :) ... ya, it just has a simple/straightforward installation method and it's source code is available on github, which i like ;)

Also, earlier in this thread people were having issues with busybox and it always seemed to be XYZ version on the playstore, where as this one just works.
[Samsung Galaxy S 5 Unified Development] BrX91:
Hmm, on CM13 it had it, but on cm14 it is now missing. Interesting... Maybe it is not the case anymore. :) For sure it worked that way on CM13 as I had this issue.

Wysłane z mojego SM-G900F
[Samsung Galaxy S 5 Unified Development] Swiss Cheese:
One other issue I am hoping someone my have an answer for. Each time I do a clean install the time is correct for my location. After I restore programs it revers to 0:00GMT and I have to change it manually to the correct time zone. I can't help but wonder if it is program that is causing the issue.
[Samsung Galaxy S 5 Unified Development] jt1975:
This is still existing in CM 13 also, it is a known bug,

go to settings, date & time and disable automatic time zones ( network provided time zones) and manually set your time zone
[Samsung Galaxy S 5 Unified Development] maguuss:
There's a bug on the 2 latest nighlys From klteduos. The chip with 2g/edge network stay mute on calls. I did a clean install on both, wiping everything but storage. This bug does not exists on the build From 11/13.
[Samsung Galaxy S 5 Unified Development] Swiss Cheese:
I had used CM13 since December and from the moment it booted it always was 5 hours ahead. On the clean flashes of CM14 I have done the clock has been correct. When I clean flashed today the time was correct for more than hour until I restored apps. It seems like it is close to working. :)