yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] uVSthem:
Is anyone having problems with their screen not rotating?
[Samsung Galaxy S 5 Unified Development] fipsy:
Yeah, I had it too. It is a relatively common problem, the reason for which is not entirely clear. It can be a hardware defect of the sensors, but it can also be a software problem. Possibly also caused by a custom kernel (only my personal guess).
[Samsung Galaxy S 5 Unified Development] mpower25:
[MENTION=5110154]fipsy[/MENTION], i can't use boeffla kernel since I own a G900MD and it seems there is no kernel specific for my phone.
[Samsung Galaxy S 5 Unified Development] uVSthem:
I'm pretty sure it's not a hardware issue. It was working fine on the stock rom.
[Samsung Galaxy S 5 Unified Development] fipsy:
That's too bad. I'm afraid then there will be no solution to the problem.

---------- Post added at 02:12 AM ---------- Previous post was at 02:10 AM ----------

If you read a few pages back here in the thread, you will find that this problem has already been discussed extensively (about mid of december).
[Samsung Galaxy S 5 Unified Development] mattnin:
Does anyone have any info about Spectre and Meltdown vulnerability affecting the S5? Everything I have found points to the phone being not affected by either vulnerability. Am I right?
[Samsung Galaxy S 5 Unified Development] Amirk365:
ARM was confirmed to be affected and since the 801 uses ARM-based cores I would imagine it to be affected.
[Samsung Galaxy S 5 Unified Development] fipsy:
My research has also shown that at least the Qualcomm CPU installed in my G900F is not affected. The CPU-Z App shows "Krait 400" architecture. That's not on the list.
[Samsung Galaxy S 5 Unified Development] lopsided98:
The Krait 400 performs speculative execution (https://en.wikipedia.org/wiki/Krait_(CPU)), so it is likely vulnerable to Spectre. It is not vulnerable to Meltdown, as that flaw only affect Intel CPUs and the new Cortex-A75.
[Samsung Galaxy S 5 Unified Development] fipsy:
But the support of speculative execution does not necessarily mean that the CPU is vulnerable to Spectre. My notebook also has an Intel Core i5-3230M CPU that supports speculative execution and is not susceptible to Spectre (only to meltdown).
[Samsung Galaxy S 5 Unified Development] lopsided98:
Do you have more information on this? I was under the impression that all processors that did speculation were vulnerable to Spectre, and I'd like to understand why some are not.
[Samsung Galaxy S 5 Unified Development] fipsy:
I can't answer that question exactly. It depends on whether the hardware requires "kernel VA shadowing". To be checked in the PowerShell with "Get-SpeculationControlSettings". Intel writes that only CPUs with 45 and 32 nm technology are affected. Others obviously have this hardware protection against the exploit. That's off-topic now, though. ;)
[Samsung Galaxy S 5 Unified Development] mpower25:
I installed Smart Pack kernel. It didn't help.
[Samsung Galaxy S 5 Unified Development] fipsy:
Too bad! But it was just an attempt without the guarantee that it would work. However, since the charge function is at home in the kernel, it would be theoretically possible to solve the problem with appropriate background knowledge.
[Samsung Galaxy S 5 Unified Development] systemcrash:
[MENTION=2693412]haggertk[/MENTION] [MENTION=5795145]javelinanddart[/MENTION]

Do Qualcomm Fast Path/Hardware NAT/Flow offload provide any potential acceleration to "Access Point" functionality? It's my understanding that these "hardware NAT" things help NATed streams bypass the main CPU, at least for those devices where it is possible. For the LEDE/OpenWRT platform, the processing is done in the 'switch' - I'm unaware of whether something like this exists in our hardware.

This is probably a more generic LineageOS question than specific to KLTE hardware.

Edit: potentially also accelerations for VPN related traffic.
[Samsung Galaxy S 5 Unified Development] haggertk:
I would have to look into it, but my gut says that it wouldn't be applicable, if only because we have Broadcom wifi chipsets on klte and I would expect that you would want such a thing to be resident on the networking chip...
[Samsung Galaxy S 5 Unified Development] systemcrash:
Did you get a chance to look at RTC alarm/POA for klte variants? Just tested on my klte G900F, no go, it seems.
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=2693412]haggertk[/MENTION]

I don't know what I should think of the recent CPU "security issues" (meltdown & spectre) but is there anything LOS team can do against it, IF we have a security problem?

thanks & regards
[Samsung Galaxy S 5 Unified Development] systemcrash:
Intel & AMD, and one ARM CPU specific - our klte platform is unaffected. Mitigations should be performed higher up in the stack anyway.
[Samsung Galaxy S 5 Unified Development] javelinanddart:
To get it working, we'd need to mount a partition that could break booting on some devices.
[Samsung Galaxy S 5 Unified Development] systemcrash:
Who cares about breaking stuff. That's what nightlies are for ;)

Which partition? Is this about getting /persistent to work?
[Samsung Galaxy S 5 Unified Development] la0pe0Ue:
Disable SIM cards

Dear maintainer:

I learn from a reddit post, titled "Is there a method to disable/enable a SIM in dual SIM phones?", that one can disable a SIM card in LineageOS for dual SIM models. In addition, a poster suggests us to contact maintainer if the functionality is not there, therefore this post.

Thanks a lot for attentive maintenance.

Model: kltechnduo

Best wishes,
[Samsung Galaxy S 5 Unified Development] Saber:
Google is responsible for the mitigations. In case people misunderstood the articles wrt Qualcomm saying "Meltdown/spectre is not a concern", some of their chips are still vulnerable and should hopefully be patched with more security updates.

Another thing that isn't mentioned enough (just in a reddit thread) is that we could still be vulnerable against spectre (I don't know how credible the source is).

https://www.reddit.com/r/LGG3/comments/7o7frc/hate_to_break_it_to_you_but_it_looks_like_the_lg/
[Samsung Galaxy S 5 Unified Development] fitittome:
Just shove it on /misc. ;)
[Samsung Galaxy S 5 Unified Development] fitittome:
Again, FWIW I have notice that this problem much reduces if Developer Options -> Mobile Data always active is switched off. Prior to doing this I was getting a cycle between Wi-Fi and LTE especially if there was no mobile data, never quite connecting to the Wi-Fi. I still haven't managed to get a logcat with a virgin phone. :( But the problem present and very similar with the unofficial 15.1 too.
[Samsung Galaxy S 5 Unified Development] j1gga84:
On top of that 5GHz WiFi runs very crappy on LOS and derivates, especially if you are in a mixed environment with 2.4/5Ghz where the router switches between both frequencies. I have disconnects very often in my home wifi network.. I think this issue startet already in CM13..

regards
[Samsung Galaxy S 5 Unified Development] mattnin:
This is simply not true. My whole family is on LOS and they are always on 5 GHz streaming YouTube or Netflix or whatever and we do not have issues. Maybe it's YOUR home network. WiFi will drop with unstable network hardware or software.
[Samsung Galaxy S 5 Unified Development] j1gga84:
both, hardware and software, is normally not possible because on my Samsung Galaxy Tab S I have absolutely no drops..

I have the same drops with my Galaxy S5 in other mixed mode networks.

Everything is okay when I am on 5GHz OR 2.4GHz ONLY.

The errors occur only when I am in mixed environments.

There is also an error in the log, I will see if I can fetch it and post it here.

regards
[Samsung Galaxy S 5 Unified Development] fipsy:
I can confirm that. WiFi is sometimes very unstable and unreliable. Fitittome once said that the WiFi connection is often lost when the mobile data connection is also lost (small cross in the lower right corner of the status bar icon). I can verify that, I have now observed this several times. WiFi is not very reliable. It has nothing to do with the router or WiFi network.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Strange my home router regularly streams 2.4ghz to my Xbox 360, 5ghz to my Xbox one and our 2 s5 phones and direct connect to my PC. Neither my s5 or wife's have ever had any WiFi disconnects on lineage that I can recall. However, running the latest 2 nightlies I will frequently be unable to send text and it will eventually send on retry. I dont lose data or phone service, only MMS.
[Samsung Galaxy S 5 Unified Development] fipsy:
The WiFi thing is pretty mysterious. So far it is obviously not reproducible. It doesn't always occur with me either, but sometimes it's very massive. When and why I could not really determine so far.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
I also just realized that at my moms where I spend most my weekdays I'm on 5ghz using my phone and streaming 2.4ghz to the TV using Netflix. Never have any WiFi disconnects here either. Only thing that comes to mind is both homes run a Asus rt ac68u router so when those with issues say WiFi issues is it in ac WiFi mode or?
[Samsung Galaxy S 5 Unified Development] fitittome:
I see it most often when waking the phone up. I am fairly sure it has to do with mobile data (or lack of). It is difficult to see visually/confirm whether it is LTE or not as 'LTE' does not seem to be displayed above the Icon on the notification bar. However, when the little 'cross' is present 'LTE' is also displayed. I am seeing this with 2.4Ghz Wi-Fi, I think the 5Ghz issue may be a red herring or a different problem.
[Samsung Galaxy S 5 Unified Development] phalkon30:
Wifi stability may actually be an android 8 problem, see this massive thread on Google product forums

https://groups.google.com/a/googlep...forums.com?utm_medium=email&utm_source=footer

My 6P makes every device streaming audio in the house skip when it wakes up from sleep. It's ****ing awful. Some routers like the orbi are much more prone and will flat out restart, my netgear R7000 just skips and momentarily loses data
[Samsung Galaxy S 5 Unified Development] :
Why is there no new build of the rom for download?
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I see the last one dated "20180104"...

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Samsung Galaxy S 5 Unified Development] :
There is a weekly schedule so a new build should have been today, 20180111. I asked why that one is still not out.
[Samsung Galaxy S 5 Unified Development] Ibuprophen:
I, personally, prefer releases to be delayed in case of an issue than to have one rushed for a release as a weekly deadline.

I know that the Lineage Team stated "Weekly" but, I just take it as an approximation than an exact deadline.

I also take into consideration that the developers there may be working on other devices that may require a bit more attention.

Patience is a virtue... :)

~~~~~~~~~~~~~~~

I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.

PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
[Samsung Galaxy S 5 Unified Development] fipsy:
Since some weeks the Thursdays weekly always is released on Friday.
[Samsung Galaxy S 5 Unified Development] rcmaehl:
To quote LineageOS rules:

No ETA posts!
[Samsung Galaxy S 5 Unified Development] MagicRB:
Is there a way to forcefully disable usb charging? so that the phone keeps a data connection but doesnt drain the battery of whatever its connected to? I looked around in sys and proc, but i couldnt find anything. Also does this rom or phone, i dont know where the support is handled, support accessory mode? it would be very usefull. thx
[Samsung Galaxy S 5 Unified Development] fipsy:
Great news: As I just read, the next nightly will fix the lost HDR functionality in Snap Camera! Thanks a lot!!! https://review.lineageos.org/#/c/201737/
[Samsung Galaxy S 5 Unified Development] mpower25:
Whoa! Great news!
[Samsung Galaxy S 5 Unified Development] 10goto10:
You can, with a custom kernel (Boeffla), change the maximum current to be drawn from USB to be as low as 50mA.

Yay! Seems like it affected multiple devices too, wow. That must've been tough to track down.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I wonder if there will be a way to just flash the fixed Snap Camera app onto a Lineage based rom (that no longer gets updates) such as RR, etc.
[Samsung Galaxy S 5 Unified Development] alex19EP:
[MENTION=2693412]haggertk[/MENTION] Hello, I sent the patch. https://review.lineageos.org/#/c/201276/

I write because no one has approved it yet.

I'm blind and Gerrit is not very well accessible. can I have done something wrong?
[Samsung Galaxy S 5 Unified Development] systemcrash:
I think because there is lots written there about accessibility - e.g. the English comment for this string: <!-- Content description of the battery level icon for accessibility while the device is charging (not shown on the screen). [CHAR LIMIT=NONE] --> means that this message is spoken (only) for blind people. это сообщение наверное только полезное для слепых людей, и никогда показывют нигде на экране а наоборот систем говорит это сообщение звучно. но хорошо что нушёл)) :good:
[Samsung Galaxy S 5 Unified Development] javelinanddart:
You need to change this on crowdwin, not on gerrit. Sorry.
[Samsung Galaxy S 5 Unified Development] alex19EP:
and I don't find the russian strings for it
[Samsung Galaxy S 5 Unified Development] javelinanddart:
My bad. It's an AOSP string, and has to be changed on gerrit. I'm bugging our translation folks to see if we can get it merged
[Samsung Galaxy S 5 Unified Development] PeterFrostad:
I'm running a Galaxy S5 (SM-G900W8) and have had good lock with LineageOS so far except when a do an update I lose my adopted storage. Which means I have to adopt the external SD card all over again which nukes all the data or apps that is on the adopted storage.

Is this a bug or is this normal? Is there a way to avoid losing adopted storage when doing an update?
[Samsung Galaxy S 5 Unified Development] Paul_Lunardi:
It seems like a big I've got adoptable storage on sm-g900i model I've adopted half of my 128 GB SD card and have not ever lost it on an upgrade.
[Samsung Galaxy S 5 Unified Development] PeterFrostad:
Maybe that's a clue. I adopted my entire 128 GB SD card. I should try and adopt just half of it next time and see what happens.
[Samsung Galaxy S 5 Unified Development] fitittome:
Did you see this? https://xdaforums.com/showpost.php?p=72991631&postcount=7366
[Samsung Galaxy S 5 Unified Development] PeterFrostad:
Ahah! That was very helpful. I physically removed the external SD card prior to upgrading LineageOS and it worked. Thanks.
[Samsung Galaxy S 5 Unified Development] fipsy:
That sounds anything but trustworthy. If I read what you have to pay attention to with adopted storage so that nothing goes wrong, I would probably not trust my data to such a fragile system.
[Samsung Galaxy S 5 Unified Development] fitittome:
It nearly always end in tears. :crying:
[Samsung Galaxy S 5 Unified Development] fipsy:
Especially if you have a spontaneous reboot! Then the SD card is not removed when booting. According to what I read, all the data would probably be broken.
[Samsung Galaxy S 5 Unified Development] MagicRB:
I recently tried to write to the framebuffer directly, and I noticed it does not work, but it works in twrp, so im guessing its either the bootloader's, or android's fault, can you guys tell me how to enable framebuffer, I read smwh that it's something related to hardware overlays and gles. If you can I'd be very thankful. BTW it says, No such device when trying to access /dev/graphics/fb0, if i need to recompile the kernel or smth that's fine, i'll do anything :D i realy want framebuffer working
[Samsung Galaxy S 5 Unified Development] MagicRB:
So i found out that in fact it is a kernel thing, i don't know how to fix it still. But i'm getting there.
[Samsung Galaxy S 5 Unified Development] cal002:
I've been using adopted storage forever without any issue on updates. However, I'm not using f2fs but ext4 (rename or remove /system/bin/mkfs.f2fs, adopt storage, check "mount" output to confirm it's ext4). One guess maybe the official twrp uses an old kernel (from omnirom 6.0 branch) and it has f2fs issues? Seems unlikely, but then using haggertk's twrp build (which was made in lineageos-14.1 tree) could make a difference.

FWIW, I wouldn't trust my data to any unencrypted storage ;)
[Samsung Galaxy S 5 Unified Development] brianinmaine:
sometimes a particular version gets skipped somehow - I'm curious if this might have happened with the "klte" branch? or maybe there is a big bug or something that makes compiling fail? I'm just anxious is all - feels like I won some money when I see there is a new download - YIPEE!
[Samsung Galaxy S 5 Unified Development] fipsy:
I don't think so. However, I have also been surprised that this weeks "nightly" has been interrupted for the first time. However, as there are still more changes being added to the upcoming nightly every day, I assume that everything is okay and that the nightlies will only be released every two weeks in the future.
[Samsung Galaxy S 5 Unified Development] jdrch:
This has been a problem for well over 2 years now (since Marshmallow/CM 13). 1st of all, make sure you're using the latest TWRP. The only guaranteed workaround I'm aware of is to remove the adopted SD card after powering off your phone, then boot into recovery and dirty flash. Then boot back into the OS and wait for it to load. Then reinsert the SD card. The OS will spend 5 to 10 min checking it for errors and then will mount it and all will be back to normal.

---------- Post added at 16:22 ---------- Previous post was at 16:14 ----------

It is, but Google's documentation is poor. As long as you do backups you'll be fine.

Huh? No. Despite the lack of documentation, adoptable storage has very clear, predictable behavior. As long as your data is backed up there's nothing to worry about.

---------- Post added at 16:23 ---------- Previous post was at 16:22 ----------

Any situation in which critical data isn't backed up does.

---------- Post added at 16:26 ---------- Previous post was at 16:23 ----------

Not sure where you read that, but it's not true. You'll be fine as long as the following 2 conditions are not simultaneously met:

1) You are in recovery

2) The adopted card is inserted

If you bear that in mind, data corruption is easily avoided.
[Samsung Galaxy S 5 Unified Development] Atlantisvip:
Disregard please.
[Samsung Galaxy S 5 Unified Development] fipsy:
Well, but rather unencrypted data than lost data. ;) If the system is secure, it doesn't matter if the data is encrypted. And if the system is vulnerable, I wouldn't have a good feeling even with encrypted data. And within the CPU, the data is unencrypted anyway (just think of Meltdown or Spectre).

If you know what to do, adopted storage is no problem at all. But just the fact that I could accidentally boot into TWRP without having removed the SD card and then have to expect data loss is a KO criterion for me.

I make a backup every few days, but it would be annoying if the backup was 2 or 3 days old and I would loose the data of 3 days. I honestly don't want to use a system where I always have to pay attention to certain things so that I don't lose data.

I understood it like that there is a danger when you boot Android with the SD card inserted. In the above linked hints (praragraph 2) it was said that you should always boot Android WITHOUT an inserted SD card and should only insert the card after the boot process has finished. But maybe this only applies if you flashed an update directly before.
[Samsung Galaxy S 5 Unified Development] jdrch:
Put it this way: adoptable storage itself has never failed me. My Shield K1 has been using the feature since Jan 2016 with zero issues, for example, so I know the feature itself works reliably. What have failed me are TWRP or LOS in the way they handle adopted during flashing/recovery. I don't think that's an adoptable storage bug, I think it's a bug in TWRP or LOS, but as I've said previously no one seems to want to take responsibility for it and since the workaround is simple there isn't much incentive to.

Let me explain my workflow and why data loss doesn't worry me: my adopted card carried all my personal documents, pics, and video, which are constantly synced via Resilio Sync P2P to other machines I own. Ergo, if my adopted card gets wiped out for any reason I literally have an up-to-the-second backup. All I have to do is insert a new card (or reformat the existing one,) resync, and I'm back up and running again. As I said previously, I've never had that happen due to adoptable storage itself, only due to TWRP and SD card failure. I also run nandroid backups before each dirty flash attempt so no worries there either.

If you like giant PC-like storage on your device - and not having to deal with Android's nonsensical portable SD card permissions (a solution in search of a problem that accomplished nothing but resulted in a swath of Android apps that can't edit files on portable storage) - I cannot recommend adoptable storage strongly enough.
[Samsung Galaxy S 5 Unified Development] j1gga84:
What is the reason for the "missing" weekly last week? :confused:

I saw that the next weekly will have security patch of january and some other changes, for example in kernel :good:

https://www.cmxlog.com/14.1/klte/

regards
[Samsung Galaxy S 5 Unified Development] fitittome:
Infrastructure probs, I think they just abandoned all the missed ones rather than play catch up.
[Samsung Galaxy S 5 Unified Development] j1gga84:
New weekly was just released, finally :):good:

regards
[Samsung Galaxy S 5 Unified Development] fipsy:
Does the HDR function with Snap Camera work for you with the new build? Everything is the same with me as with the old release: HDR doesn't work. The version number of the camera app also didn't change. It's still 2.0.002.
[Samsung Galaxy S 5 Unified Development] J-Lindo:
Same here. Tried Snap with and without HDR, and I could see no apparent difference. Maybe we missed something about the nature of the fix?
[Samsung Galaxy S 5 Unified Development] fipsy:
Seems the fix only solved the problem with two pictures being stored. But not with the HDR functionality of the camera chip itself that got lost a few month ago.
[Samsung Galaxy S 5 Unified Development] johnyfrol:
Hi there!

Yesterday i have updated to LOS 14.1-20180118. Today i find out that Face unlock is not working. I have checked my setup for face recognition and this is what i get (see screenshot).:confused:

Camera is working fine!

Please could someone help me with this?! :D
[Samsung Galaxy S 5 Unified Development] fipsy:
I had never set up face unlock before. I have just tested it and it works fine for me. So obviously it is not a fundamental problem of this build.
[Samsung Galaxy S 5 Unified Development] HulkSmashBurgers:
I'm not seeing the face unlock feature, and searching settings turns up no results.
[Samsung Galaxy S 5 Unified Development] fipsy:
It's under Security -> Smart Lock
[Samsung Galaxy S 5 Unified Development] Rocthrower:
I had something similar happen a couple builds ago. I removed my trusted face, restarted the phone, and then I was able to add my face again. I've flashed several updates since (still on January 4th buidl), and Face Unlock has been working fine.
[Samsung Galaxy S 5 Unified Development] johnyfrol:
Yeah, I found the same solution but without restart. I removed saved trusted face and added new one. Now everything works fine. The reason why I need this function is because of this: [youtube]0k4fSricp5s[/youtube]
[Samsung Galaxy S 5 Unified Development] emacsomancer:
I seem to be having battery life issues with the latest build (containing the January security patches). I've had astonishing battery life up to this point (at 50% battery after 12 hours with decent SOT), but since the latest build I seem to be down to 30% after a few hours.