yashsingh1/xdaforums huggingface dataset:
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Thanks, I just installed it! I will report in case I still see reboots.
[Galaxy S 5 Android Development (Snapdragon)] uriseja:
Installation not successful

Device: g901f

TWRP: 3.0.3

After installation of lineage-14.1-20170227-UNOFFICIAL-kccat6xx phone behaves strangely:

- usually powers off after statup, stops after showing lineage logo. Several reboots - no help

- rarely it reaches to init, but does not recognize SIM card

- tried factory reset, tried upgrade with wipe dalvik from CM 13 - no help

- tried different images - same behavior

any hints?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Can I check with you if you have flashed modem or bootloader?

This rom requires a minimum of CPE1 for both modem and bootloader to work well.
[Galaxy S 5 Android Development (Snapdragon)] uriseja:
Ok. That one I missed. Currently modem is BOC4, not sure about bootloader though.

I'll try to update and give update then.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Report regardless it's working or not.
[Galaxy S 5 Android Development (Snapdragon)] uriseja:
After upgrading bootloader/modem (tried CPE1 and CPHA) LineageOS updated successfully from cm13. Only issue is that mobile data is not detected. Will try factory reset + install next.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Check if you have your APN settings correctly configured.
[Galaxy S 5 Android Development (Snapdragon)] xShigiga:
My GApps were removed after flashing the update also the datamanager is away my i also lost my whatsapp chats etc what should i do?
[Galaxy S 5 Android Development (Snapdragon)] uriseja:
Tried to set APN manually by operator instructions no luck either, same state:

SIM Status -> Mobile Network State : "Connecting"

After factory reset + install mobile data is working.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Great to see all working again.
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
The phone is again fully stable since this build (Feb. 27). No more spontaneous reboots or shutdowns. :good:
[Galaxy S 5 Android Development (Snapdragon)] Vicky_666:
I'can instal your experimental rom via twrp 3.0.0 G906L."install error.this package can't install"please fix this T_T
[Galaxy S 5 Android Development (Snapdragon)] huntersub84:
What about the heat, anyone found any issues?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Depending on your usage.
[Galaxy S 5 Android Development (Snapdragon)] Klaass:
Does the camera app in lineage os 14.1 support UHD video?
[Galaxy S 5 Android Development (Snapdragon)] gengt:
Not here, but i don't have de last modem/bootloader, may be this is the problem
[Galaxy S 5 Android Development (Snapdragon)] :
I usually download my Stock ROMS from updato.org but I even tried restoring my phone to CPHA using Samsung Smart Switch on Desktop and my Serial Number.....

Upon hours more of investigation, I have found that my phone is not agreeing with the new kernels packed with LineageOS (UNOFFICIAL kccat6).

When I install 20170101 from IonKiwi.nl, It boots up in less than 60s (84s with Gapps) of Boot

But When I install builds from February (don't know which specific build), It doesn't boot at all with the Boot Animation running the whole time.

Upon DEEPER investigation

- No security features (Reactivation Lock) are enabled though it was enabled previously

- February and March LineageOS Builds boot on my G901F when a older kernel is applied or restored using TWRP

- /data is formatted as ext4

- Neither TWRP 3.0.2-0 or 3.0.3-0 work

I think this is a small but rare issue and shouldn't affect anyone else though maybe it's not a issue and it's just me xD

LineageOS has come so far for the G901F and I'm really grateful for developers like [MENTION=5876638]xamio[/MENTION] and [MENTION=3419717]cvxda[/MENTION].
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
I'm using boot loader CQA2 and baseband CPJ1.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
No. Hopefully "not yet". The problem is: we can activate UHD mode, but as soon as you try to use it, the underlying, proprietary camera server executable called "mm-qcamera-daemon" crashes. When using the exact same code on the klte sister device (G900x), mm-qcamera-daemon works fine, but our mm-qcamera-daemon crashes, and I have not the faintest idea why.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
[MENTION=5876638]xamio[/MENTION]

Do you want me to close the pull request or leave it as it is since Google Assistant is officially coming under Google Play Services?
[Galaxy S 5 Android Development (Snapdragon)] Klaass:
Since 2 months, I've installed cm 13 for the 901f. I've found 2 big problems; the battery life is not good at all (a maximum of 2 hours of screen on time). And the camera app doesn't work very fine, often crashes and the HDR mode doesn't work. Furhtermore there are often reboots. It works fine, but these problems are noticable.

So I've a question; How is the battery life in lineage 14.1 (SOT)? How works the camera?
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
FYI, the repositories supposed to become the basis for the move to official LineageOS support have moved since yesterday. The new repos can be fetched from the roomservice.xml file provide by the repo

https://github.com/github-cygwin/apq8084-roomservice.git

Please note that a rename has taken place:

kccat6xx -> kccat6

lentislte-common -> apq8084-common

So the repositories are now called

android_device_samsung_apq8084-common

android_device_samsung_kccat6

android_device_samsung_lentislte

android_kernel_samsung_apq8084

android_vendor_samsung_apq8084-common

android_vendor_samsung_kccat6

android_vendor_samsung_lentislte

The kccat6 build target is now called lineage_kccat6-userdebug without the double x. The kernel under android_kernel_samsung_apq8084 is the new kernel used for testing on the Resurrection Remix sister thread.

As far as your patch goes, I don't know if it's still required after the move of Assistant to Play Services, but either way, it should go into apq8084-common's system.prop, not kccat6's one.

Have fun,

Corinna
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Hi,

Without forgetting the truncated text, thanks for the reply. I will look into it and I do not think that my pull request is needed again. However, I will still study the new repo for future usage.

Thanks

---------- Post added at 05:56 PM ---------- Previous post was at 05:47 PM ----------

And I am new to this whole Android ROM and kernel stuff, so if I do make mistakes, please advise and guide me along.

---------- Post added at 05:58 PM ---------- Previous post was at 05:56 PM ----------

@xamio,

I think it's about time to set your repo to the base rather than using sktjdgns1189's repo as we have no officially moved to LineageOS.

New chapter, new repo perhaps? And I think [MENTION=3419717]cvxda[/MENTION] has already done the "renaming" of these repo by creating and rebasing it.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Well, I'm kind of new to this as well. I'm building ROMs since about April 2016 and really hacking on this stuff only since July or so :)

The idea was (and this is with [MENTION=5876638]xamio[/MENTION]'s consent) that the repos I created are the new base for now. It's hopefully temporary anyway, since I'm really trying to get them into LineageOS, so that will be the new base at one point.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Actually I like the new base created by you and I do hope [MENTION=5876638]xamio[/MENTION] rebase it based on yours. At least for now, we are no longer Cyanogenmod but LineageOS base.

---------- Post added at 06:12 PM ---------- Previous post was at 06:10 PM ----------

At this point now, I am not sure if we actually need to force enable Google Assistant via build.prop in /system/

Perhaps the people here can feedback a little on this?
[Galaxy S 5 Android Development (Snapdragon)] girtsn:
Guess this thread does not really care for bug reports or selective who is reporting? It would be at least nice to add them to the list...

The first one is a killer. I just realized there is proof for dsync of battery states - in OS it showed 4% left then just connecting charger 12%, thus maybe on the failed startup cases it thinks it has enough battery but then gets in sync with actual state and turns off? Any idea if this could be the cause and how to sync?
[Galaxy S 5 Android Development (Snapdragon)] :
Well, I used the NAND ERASE ALL Option and So far no hard brick. I took a massive risk today, would I recommend it, Yes if you are trying to fix problems with your G901F. But It must be done the right way.

I will be back once I try installing LineageOS again.....
[Galaxy S 5 Android Development (Snapdragon)] :
Still the same issue, Only builds from 2017-02-15 and earlier work, later builds boot but end up being stuck on the boot animation.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
I cannot reproduce all this problem you have just mentioned.

---------- Post added at 10:52 AM ---------- Previous post was at 10:50 AM ----------

I do not have problems booting up the February builds. So I really have no idea what is the exact problem you are facing.
[Galaxy S 5 Android Development (Snapdragon)] HelmHolm:
Bluetooth music player control issues

Hi there!

I have some issues with the music player. Bluetooth pairs fine with the car media system. Phone calls are possible, playback of MP3s works.

But the music player does not react to the car control buttons (e.g. pause / unpause, skip track).

Additionally the names of the music tracks are not displayed in the cars display. This worked fine with cyanogenmod 13.1 .

Any ideas ?

Best regards
[Galaxy S 5 Android Development (Snapdragon)] gengt:
After update de bootloader/modem from CPE1 to CPJ1, I don't have any reboot, seems that the problem is the old bootloader/modem. Now the rom is more stable
[Galaxy S 5 Android Development (Snapdragon)] :
I think the problem is in the kernel or BOOT partition because if I backup 2017-02-15 boot partition and I install 2017-02-27 and then restore the boot partition, It Finally boots. But if I just use the kernel located in one of the newer builds, (2017-02-27) It is stuck on the Boot Animation again........

Any recommendations as to why my phone is disagreeing with the newer kernel?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
What is the version of your kernel now?
[Galaxy S 5 Android Development (Snapdragon)] :
3.10.101
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
If memory serves me well, Xamio did mentioned something on 3.10.1xx that it's not booting up.
[Galaxy S 5 Android Development (Snapdragon)] :
Well I am running 3.10.101 right now so maybe it's the opposite.

Something on 3.10.101 makes my phone boot but not [MENTION=5876638]xamio[/MENTION] and newer versions make your phones boot but not mine. Doubt it's that simple though.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Sorry brah. I really have no idea what is going on. I got no knowledge with kernels. :(
[Galaxy S 5 Android Development (Snapdragon)] :
I know a bit but, as I said, upon investigation, me booting into newer builds doesn't save anything in the /data partition such as Setup Wizard Data or first boot Data.

I really really want to have the Latest Version of this ROM installed as quick as possible. Everything works except a couple of bugs including the YouTube Video 720p bug on this older build so that's 1 of the reasons I want to update so badly.
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
Everytime the kernel switched i can't boot. So factoryreset and new install solved the bootissue

always for me.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Really? I dirty flashed even when using an entirely new kernel, like switching from Say's kernel base to stock Samsung :confused:

Corinna
[Galaxy S 5 Android Development (Snapdragon)] :
Doesn't work for me, might try using LP Boot Loader and Modem as stated in the Ressurection Remix Thread
[Galaxy S 5 Android Development (Snapdragon)] schwatter:
Mh k...maybe i miss something.... but think it was upgrading from 20170202 to 20170212. I'm on CPJ1.
[Galaxy S 5 Android Development (Snapdragon)] :
Lollipop Bootloader and Modem dosen't work, I guess the next thing to do is for someone to build a unsecure working kernel (preferably from 2017-02-15 build) so I can do a logcat on build if someone would be so kind to send me :D
[Galaxy S 5 Android Development (Snapdragon)] ReaperZ:
I appear to be missing the System UI Tuner ? Any way I can get this. I've tried holding down on the settings gear, but it doesn't spin or give me the settings.

Samsung Health also fails to validate, even when the correct verification code it input.

Also this is my first time using a lineage ROM, is there any way to make the "apps" section look more graphical, rather than a list of a-z
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Hi,

First of all, moving from a stock Samsung rom to LineageOS (AOSP) is a very huge jump. Basically most of the things you are used to in Touchwiz will no longer be a thing in this ROM. As for your Samsung Health, I do not think that there is an app in this ROM at all, and even if you manually install the APK, it might not work.

System UI Tuner is actually working fine except for a small bug where changing the style of the battery icon will not work at all.

As for the apps section that look more graphical rather than A-Z, that is dependent on the launcher that you are using. Configure that through the settings for the launcher.
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
I am on build 27-02-2017 (clean install) and everything works except for pokemon go (laugh). I can't logon with my google account OR my trainer account in pokemon go (on this phone). On another phone/tablet it works fine. I tried reinstalling the app/wiping data from the app/checking the rights of the app.. I even installed root (afterwards) but to no avail.

My google account works fine on this phone..

Anybody?
[Galaxy S 5 Android Development (Snapdragon)] ToonBoon:
Isn't pogo blocked on rooted phones?
[Galaxy S 5 Android Development (Snapdragon)] ReaperZ:
Thank you, I'm happy to tweak and fiddle just wasn't sure what :)
[Galaxy S 5 Android Development (Snapdragon)] laivu:
[MENTION=3419717]cvxda[/MENTION] RR rom by u for g906 so amazing. Please support lineage os for G906 . thanks
[Galaxy S 5 Android Development (Snapdragon)] :
I obtained a logcat by running adb logcat on build 2017-02-27.

It is attached below.

After the last line of the logcat, the kernel just hangs and there is no further log.

Hopefully this can fix this bug.

[MENTION=5876638]xamio[/MENTION] [MENTION=2763012]ruchern[/MENTION] [MENTION=3419717]cvxda[/MENTION]
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
It worked on build 15-02-2017. (non rooted) but not anymore on build 27-02-2017 (non rooted). I tried this:

-edit buildprop (changed "test-keys" into "release-keys")

-hide root (ISU-app)

pogo still doesn't want to logon.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Cannot login shouldn't be a problem because of the rom. Unless you're referring to the safety net block.
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
I am just started reading up on this "safety net boot". It's a kernel thing right? Are you saying that the kernel of lineageos is the culprit?
[Galaxy S 5 Android Development (Snapdragon)] ToonBoon:
Can I just upgrade from 6.0 into Lineage 14.1 or is there an intermediate step that I need to take?

EDIT: I managed to install it now after first installing CM. It's not stuck on "Andriod is starting" for over 30 minutes... Is this something that I just need to wait out?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Yes. It is a kernel thing. I tried Sultanxda's solution regarding the boot, but because I am not very familiar with kernel, I dropped the idea.

Right now I am trying to build the kernel based on the current repository state but am pretty stuck now.

---------- Post added at 09:28 PM ---------- Previous post was at 09:27 PM ----------

To flash Android 6.0 to LineageOS 14.1, you will require to do a full data wipe before proceeding. This is because you are flashing to a totally new version of Android. Lineage 14.1 is based off Android 7.1 Nougat.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Sultanxda's patch is already in the kernel, see

https://github.com/github-cygwin/android_kernel_samsung_apq8084/commit/e2bf3770

Corinna
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Oh nice. Didn't know that. So are we using it since quite a while now?

---------- Post added at 08:22 AM ---------- Previous post was at 08:20 AM ----------

@cvxda

Do you have any idea why do I have dirty directory the moment when I pulled the kernel repo?
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Just to add on to xda commit with sultanxda, you need to have your su binaries hidden and enforcing selinux to pass SafetyNet.
[Galaxy S 5 Android Development (Snapdragon)] girtsn:
Strange. No advise on how to debug / get logs during boot?

Annoyed since the devs are just ignoring my reports. There are people reporting the same issues (reboots / shutdowns and power on not working after). Also the notifications issue has been confirmed though not the most urgent. And it is not hardware / battery failure as happening on both devices owned bought different times. Are people really not running an almost empty battery every day with the consumption as it is?

Though to be sure it isn't fixed I did a full wipe, clean install with 02.27 build and reproduced all 3 in the first day of trying. They have been happening in all the builds tried. Steps to reproduce in case anyone bothers to (do not connect the charger obviously):

1. After a day of usage (this seems to be important to reproduce), when battery to a close to empty state (has happended anywhere between 5 and 35 percent left) do reboot the phone - don't have to wait for it to reboot on its own / turn off which happens quite often when battery on the way out. What often happens is that the phone reboots, then goes to boot animation and then shuts down / turns off the screen with the vibration sound. After that, need to remove the battery to start it again - and even then it sometimes will do the same shutdown sequence on logo. It seems to be random, does not happen each time but happens OFTEN. As mentioned could be an issue with battery state sync as I saw a completely different number between OS and the charging screen when not booted (12% vs 4% or so).

If anyone would talk to me and tell me how to get a bootlog to happen on each reboot, I could get the logcat of such a case.

2. Just get the state to battery saver (happens before it though) and try to play a game or something else a lot to do with touching the screen, you shall see that the responsiveness of touch screen goes to useless, often does not work until lock & unlock the screen

3. This is easiest to reproduce. Send yourself a messsage or anything else to cause a notification when screen is off. Then when the screen half-turns on the screen, unlock. You will stay in this half-lighted mode.
[Galaxy S 5 Android Development (Snapdragon)] pbecks1963:
My phone was rooted (not anymore) and selinux is enforced. Still i can't get passed the safety net check. Perhaps i need to clean install again. (or perhaps there is an option in developers options that needs to be disabled)
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Check with [MENTION=3419717]cvxda[/MENTION] if the kernel is already live.
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
The patch is in all kernels since October.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Does the latest Safety Net code check for the KNOX flag, perhaps? I don't know, but the Safety Net code is developed further. There's a good chance that Sultanxda's patch from last year is just not enough anymore.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
Hang on. We're doing this here voluntarily in our spare time. I wasn't aware that the devs have to reply to all postings. If I had known this I wouldn't even have started to create builds in the first place and just kept it for myself.

Apart from running all reboots under adb logcat to catch this situation, idk.

Nope, can't reproduce.

Nor that one.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
[MENTION=5876638]xamio[/MENTION], [MENTION=3419717]cvxda[/MENTION]: I noticed that the camera display is again distorted in apps like WhatsApp on the latest build of LinOS (Feb. 27). See attached screenshot.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
I know that it has been fixed. I did not mix up. I actually did have problem with the CM File Manager before.
[Galaxy S 5 Android Development (Snapdragon)] Proioxis:
Done, thanks! I fixed my other issues aswell (completely my fault).

ROM is working smoothly atm, battery life is looking promising!
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
[MENTION=5876638]xamio[/MENTION], [MENTION=3419717]cvxda[/MENTION]: I just ran the QuadRooter Scanner app and it states that the phone is still vulnerable to CVE-2016-2504. It links to this page on codeaurora.org, which describes the bug and provides references to patches for the KGSL Linux Graphics Module. Would be good if you could incorporate this patch in one of the next builds.
[Galaxy S 5 Android Development (Snapdragon)] xamio:
Thanx! Fixed in lineage-14.1-20170108-UNOFFICIAL-kccat6xx.zip
[Galaxy S 5 Android Development (Snapdragon)] Maxtwax:
So this ROM is not compatible with G900F, only for G901F?
[Galaxy S 5 Android Development (Snapdragon)] Stamgastje:
Wow, that's fast... Thanks! :)
[Galaxy S 5 Android Development (Snapdragon)] Iron Steel:
Hi [MENTION=3419717]cvxda[/MENTION],

I'm actually on Norma V5 rom with bootloader CPI4 and modem CPE1. Can I install Lineage rom without install first a stock FW and TWRP and only make a full wipe and install rom and gapps.

my version of TWRP is twrp-3.0.2-1-b4-kccat6.tar.

and what's the good package of gapps (mini, stock, nano, etc) to use with.

thanks for answer.
[Galaxy S 5 Android Development (Snapdragon)] michaelbelachev:
Yea
[Galaxy S 5 Android Development (Snapdragon)] cvxda:
G900F and G901F are completely different devices. Thanks to Samsung for the naming confusion.

Corinna
[Galaxy S 5 Android Development (Snapdragon)] gencaslan2014:
many thanks to the developers!
[Galaxy S 5 Android Development (Snapdragon)] Proioxis:
First day of using the new ROM from 7am to 5pm.

The first part of the day was with minor usage, just to reply to some messages, charged it in the car on the way home, and after that been sitting on the couch browsing.

It drained pretty quickly with the screen on 1/4 brightness.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
If possible, cut down on Snapchat usage. That one drains battery quite significantly.
[Galaxy S 5 Android Development (Snapdragon)] Proioxis:
Haven't even used it much, I only check out other people, I don't make them much myself at all.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Alright I see.

If you do make one, got to keep an eye if the camera was left turned on by the app.

That last time I used that app, the camera was on and it did not shut as I shut Snapchat. Ended up my phone was heating up and drained completely to 0 in 2 hours.
[Galaxy S 5 Android Development (Snapdragon)] Proioxis:
I've had that happen to me before on other ROM's, but since then I obsessively close the applications I don't use.

I have greenify, doze and all that jazz, so when my phone is in my pocket it's most likely dozing.

I'm getting better batterylife from this ROM than from the 'original' CM13/CM14, but it's still not enough :/ If I don't charge my phone in the car it's dead before evening.
[Galaxy S 5 Android Development (Snapdragon)] ruchern:
Greenify to me drains more battery instead of saving my battery.