yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] Qiangong2:
[MENTION=7026648]AlaskaLinuxUser[/MENTION]

Here is my logcat: https://hastebin.com/juvajarafu.scala

I used a sensor test app. Once you pull your finger away from the proximity sensor, it still says you are near it.

---------- Post added at 03:53 PM ---------- Previous post was at 03:50 PM ----------

Huh. The GPS on mine works perfectly. I use Nokia here maps if that makes any difference
[T-Mobile Samsung Galaxy S 4] arikdahn:
I bought a new motherboard. Will see if that clears up any of my issues. I have already replaced the bottom board and the GPS antenna. It seems to be working great until it doesn't work (GPS). It will also occasionally lose all wireless signal and will not try to reclaim it. Wifi locks the phone up and mobile data just doesn't even try.
[T-Mobile Samsung Galaxy S 4] Qiangong2:
Yeah, it sounds like the motherboard. Does this even happen on stock though? Your motherboard may just have been used too much to handle 7.1
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Question:

These problems, which kernel are you using, the one with the ROM, or the aklu kernel?

Have you considered trying it with the other?
[T-Mobile Samsung Galaxy S 4] arikdahn:
I have... you know... just now when you suggested it. Hah! I have only tried with AKLU, not stock. Any idea how I can go back without re-flashing the ROM?
[T-Mobile Samsung Galaxy S 4] ckc90745:
wifi hotspot

does tethering work with this rom
[T-Mobile Samsung Galaxy S 4] arikdahn:
Yes.
[T-Mobile Samsung Galaxy S 4] darazor:
arikdahn

Not sure why you would not just flash the rom and gapps after cache dalvik cleared as I have done on many occasions switching back and forth kernels but I suspect if you just swap out the boot image from the rom zip into the kernel zip it would work.

ALU will no doubt get back to you and verify if my idea is possible.

-D
[T-Mobile Samsung Galaxy S 4] Qiangong2:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] have you gotten a chance to look at the proximity sensor problem?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Yeah, darazor is right, you can pretty much just dirty flash the rom again. I always recommend making backups. But read below, as you will see that you have to dirty flash the new rom which I just put out. ;)

Yes, that's right, you could just swap them in the zip, that works great. You can use winzip or any other zip tool ( I use zip on Linux....) I suppose I should make a "baseline kernel" with the original kernel in it for those who wish to go back.

As a side note, you can always immidiately make a backup of the boot partition before flashing the AKLU kernel.

Yes, I was just testing this. You are right, for some odd reason, the sensor apps I tried say that the proximity sensor always detects me near it. However, when I make a phone call (just tested again) the screen blanks when up against my face, and lights back up when I remove it from my face. I don't know why it doesn't work for you. Quite odd. I don't think the sensor tools are properly reading the sensor, as it works for both "wave to wake" and phone calls for me.

For the group:

Praise God! Another update! 20170901 is now available for download in the Nougat folder from the OP. Lots of little, behind the scene changes, as well as opening up more JFLTE phone options (for our non-t-mobile friends).... Here is a list of updates from the AOKP team, they do some great work! A new kernel will be posted in the kernel thread shortly (some of these changes may make the older AKLU kernel unstable under certain conditions...)

Telephony: Correct missing italian translation	AOKP/packages_services_Telephony
Settings: Always show Privacy Guard permissions	AOKP/packages_apps_Settings
Settings[Wifi]:fix the input invalid length for WEP encryption.	AOKP/packages_apps_Settings
AppOps: Switch to an HashMap	AOKP/packages_apps_Settings
Settings: Add a shortcut icon for carrier selection	AOKP/packages_apps_Settings
AppOps: Redesign	AOKP/packages_apps_Settings
CMParts: Add strings for DCI-P3 color profile	AOKP/packages_apps_CMParts
tasks: kernel: Kill unexisting wiki reference	AOKP/build
build: qcom_target: Add sdm660	AOKP/build
SF: Improve hwrotation handling	AOKP/frameworks_native
Add @hide annotation to the privacy guard ops set	AOKP/frameworks_base
Change visibility of the Privacy Guard ops set	AOKP/frameworks_base
Camera2: Fix Error Callback if buffer lost.	AOKP/frameworks_base
Camera: ignore torch status update for aux or compsite camera	AOKP/frameworks_base
base: audioservice: Set BT_SCO status	AOKP/frameworks_base
SEEMP: Adding auth framework for outgoing SMS messages.	AOKP/frameworks_base
PowerManagerService: fix HW button illumination timeout	AOKP/frameworks_base
Camera: Add NULL check on mDevice to avoid crash.	AOKP/frameworks_av
Camera: Add null check on mDevice to avoid crash	AOKP/frameworks_av
Use set_prop() macro for property sets	AOKP/device_qcom_sepolicy
ROMControl - Italian translations	AOKP/packages_apps_ROMControl
[T-Mobile Samsung Galaxy S 4] Qiangong2:
Could the AKLU kernel be the reason I'm having the proximity problem?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question.... Possible, but not likely.

Mainly because everyone would have the same problem if they use the AKLU kernel. By the way, 2 cent tid bit, it is the AKLU kernel because alucard has a kernel that some refer to as the ALU kernel, or alu kernel, and I'm not on that guys level ;)

But I was using the AKLU kernel when I tested the phone calls/proximity sensor function, and it worked.

However, it is possible that some setting that you can edit does change things. But it is easy to test, update to the latest build I just posted, and don't flash the AKLU kernel. Try it for a few days and see if that clears it up for you.

Now a question for you (times two) :

1. Are you using the default dialer, or some other dialer? Like a gapps dialer or app you downloaded perhaps?

2. Did you flash magisk or SuperSU? While okay for your personal use, they have caused known issues with this ROM.

I am a big fan of people doing anything they wasn't to their phone, I just have to ask for troubleshooting purposes. :)
[T-Mobile Samsung Galaxy S 4] arikdahn:
AKLU:

I used this update as an excuse for a clean install without using AKLU kernel. So far, so good. I don't seem to have the GPS problems anymore, nor do I have the weird wireless data dropouts, but I also don't seem to have an option to enable quick charge. The CPU undervolting I can probably live without since my phone spends the vast majority of its time in deep sleep anyway, but the QC would be nice. Does the kernel just not support it at all? Not sure if you would know this or not.

Things I've noticed about this release:

-Weather provider stuff (taskbar and lockscreen) seem broken on this release and the release before the last, BUT it worked on the last release.

-Auto-Brightness toggle in the quicksettings is gone

-Did something happen to the adaptive display setting to determine the times to start nighttime color wavelength profile? I don't recall having a problem finding this before but cannot now.

There may be more but I haven't really explored much. Timekeeping still seems to be wonky. I forgot to change to the correct time zone since it did auto-acquire properly upon initial install of the ROM. My alarm woke me up to go to work and I got showered at 4am.

HW button illumination is still nonworking as well and there are a few things in rom manager that don't work, but I don't recall which ones. I expect these are known problems though.

As always, you're the man!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
arikdahn,

The original kernel does not support QC, and it may still have a problem with WiFi hotspots. It also does not have Fauxsound or any of the other kernel mods. Just a plain Jane kernel. As you can see, it is the old CyanogenMod kernel, back when CM used to exist. It is very stable though, which is why I include it with the rom. The AKLU kernel is my attempt to learn how kernels work, and so you are all sort of my guinea pigs.... :p

Things I've noticed about this release:
-Weather provider stuff (taskbar and lockscreen) seem broken on this release and the release before the last, BUT it worked on the last release.
-Auto-Brightness toggle in the quicksettings is gone
-Did something happen to the adaptive display setting to determine the times to start nighttime color wavelength profile? I don't recall having a problem finding this before but cannot now.

You bring up a couple of good points. In the interest of security, sometimes updates lose things.

Based on what you are saying, I've left up the 20170621 build and renamed it the "rollback" build. If anybody wants to forgo the latest security, in the interest in the most features, they can use that build.

Anything I build for this rom now is just adding security updates from the AOKP team, so this rom, for better or worse, is as good as it will get under my care and skill level.

Interesting.... Where did that auto brightness quick tile go?

As for the display, if you look under settings -> display -> live display, you can adjust some of the when and how of the display changes, like night, or sunset, sunrise, etc, as well as the color. Remember though, it is heavily based on time, which if set to auto time zone seems wonky, thus it may turn on the display changes before/after requested.

There may be more but I haven't really explored much. Timekeeping still seems to be wonky. I forgot to change to the correct time zone since it did auto-acquire properly upon initial install of the ROM. My alarm woke me up to go to work and I got showered at 4am.

Sounds like it's working to me: that's what time I get up for work. :D

HW button illumination is still nonworking as well and there are a few things in rom manager that don't work, but I don't recall which ones. I expect these are known problems though.

As always, you're the man!

Thanks for the kind words! Just glad we can keep the old S4 kicking! :D
[T-Mobile Samsung Galaxy S 4] Qiangong2:
I'm using the default dialer and I haven't installed SuperSU or magisk. The only thing I've flashed is pico happy and the AKLU kernel
[T-Mobile Samsung Galaxy S 4] ckc90745:
international roaming

Hi I love this rom but for some reason, the data does not work when roaming in mexico, I have checked the apn and it is set up correctly, could anyone help me and confirm that internation data roaming works or do I need to do anything else.
[T-Mobile Samsung Galaxy S 4] Qiangong2:
[MENTION=7026648]AlaskaLinuxUser[/MENTION]

I updated today to the 9/1 build because the previous build was cutting out on my network connection. In the 9/1 build, the phone cannot read contacts from my SIM , but the previous build can
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
To be honest, I'm not sure, I've never travelled with this phone internationally.

It looks like your best bet might be to go back to 20170621 build, I renamed it "Rollback" in the downloads folder.
[T-Mobile Samsung Galaxy S 4] Qiangong2:
Am I able to install it over the 9/1 build?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
I don't think so. It should give you an error if you try in twrp. You will likely have to wipe first.
[T-Mobile Samsung Galaxy S 4] Qiangong2:
Just a factory reset right? Not a full ODIN downgrade.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Oh yes, just a wipe in twrp, no Odin required.
[T-Mobile Samsung Galaxy S 4] nmb52:
I am grateful for your effort! Last night I dirty flashed on top of the 8/15 ROM (in turn dirty flashed on top of 6/19), and loaded the new AKLU kernel as well. So far it seems to be holding GPS settings much better.

I do not want in the slightest to seem critical, however, you seem interested in the details, so I will mention a tiny bug. I have the status bar set to show the battery percentage in numbers. When I reboot the phone the battery status is not shown; I must go into the AOKP settings to the status bar and select the battery text display again. When I open it, the battery status shows selected as text, and tapping on it is sufficient to make the percentage pop up again in the status bar. It seems odd that it shows as selected but does not actually show it until tapped again, as if it is missed by some startup routine. For what it's worth....

Thanks again!
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks for the feedback, I'm glad that the GPS is holding better, and I don't mind the details, it never hurts to know what is having a hiccup, even if it may seem "trivial" to some. Pointing out a small glitch is not complaining. When my wife told me the truck dome light was not working, that doesn't mean she wants a new truck, just is wondering if I can fix the dome light. ;)
[T-Mobile Samsung Galaxy S 4] thesultan192:
I did a clean flash of this ROM, great work!

The only issue I found is that the brightness is auto-set to the lowest position.

Every time I turn on the phone, it goes to the dimmest brightness setting. It only changes brightness if I physically move the slider, then it goes back to the accurate brightness setting.

Do you have any idea how to fix this? Is this just a settings issue?

Thanks again for the ROM, its running great!

---------- Post added at 04:53 PM ---------- Previous post was at 04:29 PM ----------

I even tried downloading Velis Auto-Brightness, but it still is dim when the screen turns on.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Thanks! I'm glad that you like the ROM.

As for the brightness, I'll do a few tests here. Question: of you turn off auto brightness, and set a manual brightness, does this still happen?
[T-Mobile Samsung Galaxy S 4] jinkerz9430:
Bluetooth is not working well for me. I can pair with other devices however it wont receive nor send any files from other device.

Also, cast doesnt detect the chromecast from my tv even when im on the same wifi as the chromecast.

Any ideas?

Mine is the m919 aka jfltetmo
[T-Mobile Samsung Galaxy S 4] jinkerz9430:
Scratch all that. i found the problem with the chromecast. Before the hurricane irma came to miami, my father disconnected everything (including the ethernet cable connecting from the tv to the router) so that's why it wouldnt detect it.

Now about the bluetooth, i reflashed the rom again for the second time (Clean flash ) and now it works. However, the type of files i can transfer is very limited (seems like it). I was trying to transfer some apk files from my LG V20 and they wouldnt get through, on the other hand i tried to transfer a microsoft word document and it did transfer
[T-Mobile Samsung Galaxy S 4] hinghing1113:
I am having a big problem now.

I am unable to complete setup any custom ROM now.

I flash the ROM, and when setup, I connect my wifi. Then it stuck on "checking for update".

It happened on this rom, SlimRom and RR.

I tried dirty flash and clean flash. I also tried odin back to stock, but none help.

When i am back to stock rom, the wifi won't turn on, (don't know why). other seem working fine.

Anyone has any thought? Please help.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hmmmmm.... Sounds like a pretty big problem.

If you Odin back to stock, and WiFi does not work, and you are installing the proper ROM, then in afraid it may be no good.

You have loss of options, though. You could always double check you are flashing the newest Odin file. If so, redownload it to make sure it is not corrupt. Also, make sure you get it from the official Samsung site, just to be sure it is unmodified and legit.

Then, if WiFi still does not work, your device probably needs repair.

When on stock, does the 3g, LTE work? If so, you could continue using it without WiFi. During setup, you can chose cellular, or opt to not set up at this time and set it up later.

Or you could get a newer phone, or have yours repaired. You might check that everything is screwed in under the cover. Just a thought.
[T-Mobile Samsung Galaxy S 4] hinghing1113:
It work fine on 3g.

I just odin to stock then using smart switch to recover. It has the newer baseband, QA1.

Then wifi work on stock. Then i tried custom rom again, still unable to complete the 7.1.2 custom rom.

I downgraded to 6. I skipped most of the setup and everything work.

But i would like to have 7.1.2...

so here's my question.

the "checking for updates" should be part of the first time setup.

is there anyway to bypass it or take out that setup app?
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Sure, just don't sign into Google. You can sign in later. Choose to continue setup without WiFi or cell.
[T-Mobile Samsung Galaxy S 4] hinghing1113:
Not the google sign in.

IT's the window right after connect to wifi.

I tried connect wifi or using cellular data option.

But this screen just don't go away.

I left overnight, still same screen
[T-Mobile Samsung Galaxy S 4] mexicandroid:
Can root access be disabled in this ROM? I'm planning on installing this since it's the latest update and want my daughter to use it.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Hmmm... Other than not flashing gapps, I'm not sure. I thought you could select to not have WiFi or cellular during that, so as not to have to update.

The problem (I think) is the new QA1 I am still using the ok3 firmware for vendor blobs. Looks like the skipped P and went straight from ok3 to qa1.

Yes, it can be disabled. After flashing and booting, go to settings and tap on about phone, then tap on build until it enables developer settings. Now go to developer settings and you can disable root access for apps and /or adb.
[T-Mobile Samsung Galaxy S 4] Qiangong2:
I've noticed over the past couple of days that if I set my connection settings to prefer 3G, I get less drops in connectivity than I did on LTE. I am using the 8/15 build without the AKLU kernel.

The only downside is, GPS connectivity is hideously slow. Compared to when I was using the AKLU kernel, it was quick. If you could integrate those GPS fixes and keep the stability of the 8/15 build, I'd upgrade.
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Does this rom support disabling the charging led?

Its quiet important for me. Thanks
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great question, but no, no it does not support that.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Great thoughts, but I do not plan on making any edits to the original kernel. I only make edits to the AKLU kernel.
[T-Mobile Samsung Galaxy S 4] arikdahn:
I think some of my data dropout problems and perhaps GPS may have been due to a bad SIM card. My second motherboard kept saying "invalid SIM, rebooting device" before I did any upgrading or rooting. And this ROM also oftentimes spams me with SIM card messages I always assumed were just how it was. I also sometimes get a little SIM card image w/ a line through it on the taskbar. I am going to try to get a new SIM card next and see if that helps. Nothing else to replace on this phone honestly after both motherboards, the coax cables, battery, and back housing. If it doesn't work right after a new SIM I'll just give up and buy a new phone. I just hate every other phone.

I bought a new stereo for my car that has GPS in it so I just use that from now on if the SIM card doesn't fix the GPS.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Well, IF you have to buy a new phone, a cheap option is the T-Mobile LG G4 (h811).... They are pretty cheap on swappa and eBay. I happen to know a developer who works on the AOKP ROM for that phone, unofficially, of course. ;)
[T-Mobile Samsung Galaxy S 4] Scottchy112:
On lienage 13 and 14.1 it's supported(alucard kernel). On resurrection remix too(forgot if there was a custom kernenl). Yeah i know it's uncommon^^.

I don't know, it's just a small thing to make a custom rom perfect to me.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Whoa! I just learned something new today!

Thanks to my good friend [MENTION=2571065]darazor[/MENTION], who pointed out that you CAN disable the LED charging light!

Settings -> notifications -> gear -> battery light -> disable/enable or chose colors....

Tried it out, and viola, it worked! Just goes to show that you can't always take no for an answer! ;) wait to go darazor, and a good thanks to the AOKP team for slipping that in there!
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Nice. That's what i wanted to hear. Thanks darazor and alaska
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Please update your aklu kernel. Version of 5th september from another website works fine for me (i think it's version 9) , yours not.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
I'm afraid I don't quite understand. Can you please be more specific?

What kernel from what other website works? What about my kernel would you like me to update? Please be as specific as possible.

Thanks.
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Okay sorry, I'll try again.

So, yesterday i downloaded your aokp rom and the aklu kernel given in post#1.

Flashed the rom and gapps and everything works fine. After i flashed the kernel, my s4 won't boot up(stucks on samsung logo). I searched xda for newer aklu kernel and found a thread where it's said that if you use aokp rom from 1st September (the newest one), you need the newest version of aklu kernel which is version 9 from this link

http://www.mediafire.com/file/cmpzdxpiy5aolj5/AKLU-JFLTE-AOKP-N-20170905.zip

That kernel works, yours in post #1 doesn't.

I just saw it was you who opened that thread with a collection of nougat kernels for the s4.

So i just want to say, update the kernel in post#1 because it doesn't work anymore with aokp rom.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Scottchy112,

Thanks, but I just used the link in post#1, and it goes directly to that thread with the collection of kernels.

Either way, I'm glad that you found the right kernel. How do you like the rom so far?
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Sorry, my mistake.

I only checked the rom donwload link and found the older aklu kernel and the aokp rom in there. I didn't notice the link below where the updated kernel is.

The rom is great. Didn't find any bugs or mistakes so far apart from one. I wasn't anymore able to connect to any wifi and reboot didn't help. Flashed the rom again and now it's working.

Everything is fluent but I still have to test the performance while playing 3d games.

Battery life is ok, but i didn't play much with the kernel now. Maybe some tips for better battery life?

I'll keep testing your rom and give some feedback later on.
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Scottchy112,

Thanks, now I see the problem, that kernel should not have been in that folder. I have moved it to clear up confusion.

As for battery/performance, see post #58 from the kernel thread:

https://xdaforums.com/showthread.php?p=70525795

A pipe other factors new since then is GPU and CPU voltage control. These gains will be minimal, but can be tuned for one or the other. Read through the kernel thread for more thoughts there.

Note, if you go with heavy battery saving options, video or games may stutter.

Hope that helps!
[T-Mobile Samsung Galaxy S 4] Scottchy112:
Yes, that was quite confusing. No problemo.

Thanks for the tips. I'll read through the thread for some inspiration.
[T-Mobile Samsung Galaxy S 4] LilinC331:
Phone Not Being Able To Boot

Has anyone had a certain issue, where the phone just stops working and not being able to boot correctly to recovery and to fix it by flashing TWRP again and then having to Format The phone and install the whole 7.1.2 AOKP Again?:confused:
[T-Mobile Samsung Galaxy S 4] AlaskaLinuxUser:
Lilinc331,

Sorry that you are having trouble. I am not having that problem here. Maybe we can figure out the problem...

Here are a couple of questions:

A. Are you doing a clean flash? (Wipe then flash)

B. Which gapps are you using?

C. Which kernel are you using?

D. Are you flashing anything else over the ROM?

E. Are you installing magisk or SuperSU?

F. Which TWRP version and phone type are you using?

G. Which phone model do you have?

H. Are you using ext4 when you format the device?

Sorry for all the questions, but your problem sounds very unique, so I need as much info as possible to diagnose it.