yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] A Sad Napkin:
Good point. That's why I stayed with freedom OS on ext4. Stock rom doesn't even boot on ext4.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
OOS 4 is working fine with ext4. You just need to install from scratch, but then it works.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ScratMan38:
Config app can't work, it says kernel config is pending, needing reboot. I rebooted twice already, still same issue.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Why do I put all required information on my web page when nobody reads it?

http://boeffla.de/index.php/support/installation-how-to

There is a huge troubleshooting section there, especially what to do when you encounter this.

Explanation (once again):

If this message comes up after you already restarted the phone, something is wrong on rom side.

Because it means, the app was not able to autostart during last boot.

And as I do not know you guys installations / roms, there is absolutely zero I can help when the troubleshooting section does not help you.

Of course this is not a general issue as I would have it then as well.

Good luck

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] akoyaxd:
I also get the Problem with the App.

OOS 4.0.2 (encrypted)

TWRP 1.0.4.0

SuperSU SR79

Edit1:

I already tried to reflash the Kernel without succes.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] ScratMan38:
I tried the things in the support page, and the app doesn't start automatically. The bc.log file is only created when the app is started manually, but giving the message above.

I'm on stock ROM, no mod, file system is ext4 (because as you, I'm not confident with f2fs), encrypted with scheme to boot, TWRP 3.0.4.0 and root by SuperSU systemless SR79.

bc.log of manual launch is attached.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] 64ashg:
It's a shame that it has come to this. That a company calling itself developer friendly is doing this to its community in the name of data protection. I hope a workaround comes up, or they have successfully made the devs to choose sides between custom and official roms. Thus making the community of to migrate to the latest devices for frequent updates, as atleast till the end of each device's lifecycle, devs wouldn't support custom roms. OR switch developers, developers whose work they have been using since they (the user) knew android itself. All of this for a device that hasn't been out in my market, worlds second largest mobile market(India) , for two months.

Sorry for my rant, this is xda, not every other social ranting media website. But this is the only place I know users will be able to comprehend what I am saying. And thank you Andi, I am greatful.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Then I am out of ideas, sorry.

Last you can check is... reboot and take a logcat after the boot. Maybe something useful is shown there.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Just one thing to mention which I came across... it seems, SuperSu 2.79 is not working always fine on OOS 4.

What I did is:

- fully unroot via the configuration menu in supersu app

- flash stock kernel

- flash supersu 2.79-SR3 modified systemless version

- flash Boeffla

Since then my OOS 4 installation feels much more consistent and fluid.

Just a side comment...

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] megaslx:
same problem on H2OS 4.0 open beta2

follow your instruction,update supersu from 2.79 to 2.79 sr3,but nothing change.

the app doesn't start on boot and no log file created until I menully open it.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Duncan1982:
Guys what version of boeffla app are you using?

As you can see its working well for me (i am on freedom OS) but its base is 4.0.2....:good:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
That is another not at all supported rom (at least officially) :)

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
Thanks for reporting.

Of course it does for the majority of the people. But not for everyone, and I can just hope these people find out why.

When the app is not getting started, this is fully out of my reach.

And I am quite sure, with a fresh install everything would go well. But this is work of course...

(and I did also dirty flash over oos 3.x. on both OP3T and OP3 without issues...)

So - something (!) must be different for a few people. Only the affected people can be the ones to find out unfortunately.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nihilista:
First thx for your new kernel, using it for a long time on onyx and now on op3t, great as always :good:

But 2 little questions:

1. I see we can set little and big cpu clusters, default settings are 2188 for little and 2342 for big, is that ok (because i remember normally there is 1593 for little only)?

2. I used zzmoove governor normally, but here i can't changethe profiles. Are there no profiles for this device and is it ok to use this governor (or isn't it fully integrated and tested and so better not use that)?

Btw, till now i had no problems with supersu (1.79sr3,systemless) which i had installed before on stock kernel,using unencrypted f2fs, it was taken over with new kernel without reinstalling su.

thx
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
1) I always had he 2188 step in, also on stock kernel.

2) There are no profiles for zzmoove in big/little edition currently. Maybe ZaneZam will add some one day, but not in the very near future.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] A Sad Napkin:
config app is working fine for me

All i did was flash boot image (i'm on freedom OS so i flashed the boot IMG from that)

Installed SR3 SuperSU

Flashed Kernal

rebooted, opened up config app, made sure it had all permissions and root access. Forced closed the app then rebooted. Had no problems.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] nihilista:
Ok, thx for quick answer. but is it good to use zzmoove or is i tbetter to use stock (or maybe i have to test that for myself ;)?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Clark789:
Hi,

i had the problem as well, but i solved it for me on this way:

1. flashing OOS 4.0.2 with TWRP 3.0.3-1

2. After flash, wipe Dalvik and Cache and restart to recovery

3. Flash SuperSu 2.79 systemless and direct afterwards fllash boeffla kernel in one go and then wipe Dalvik and Cache again.

4. Restart to system aaannndd

5. everything went fine!!! :)

I tried it different times and the boeffa app wasn't started by the system. I reverted to OOS 3.5.4 with my backup, installed the newest boeffla app already here (!) and started again a the flasing process. In the end i was succesful by the way, i described above.

Good luck!!

Cheers

Clark
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Would decrypting or using MultiROM be an option? It is very easy and works wonderfully unlike dual boot patcher which is very cumbersome.

Edit: can you not do the backup/restore on other encrypted devices as well, or just the OP3T? Is it because OOS4 and Lineage use different crypto libs?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
Eh? What are you talking about? Encryption is standard on modern android phones and required by Google if the hardware supports it. And with the latest encryption implementations, there is negligible performance loss. So encryption is actually a good thing, though I'm currently running decrypted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
I think you have to test yourself.

I can only say, interactive (which is stock gov) is the by far most stable governor.

BTW, screenshot attached with CPU frequencies of little CPU cluster with stock kernel.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Clark789:
Hi Andi,

what do you mean with consistent and fluid? Did you have lags or stutters?

And did you flash the stock kernel, SuperSu and your kernel in one go?

Regards

Clark
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
With previous supersu I sometimes had the issue, an app could not get root rights for 30 seconds. When the app was started once again it worked magically. So I had some inconsistent behaviou, however I had no lag or stutters as such.

And yes, I flashed these three zips in one go in TWRP without reboot, that works just fine.

Andi
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] andip71:
*** To all that have the issue with Boeffla-Config not autostarting (and subsequently getting a kernel is not initialized message when opening Boeffla-Config ***

You know the old phrase - log or it did not happen :)

This time, Boeffla-Config logs do not help as when the app is not started, it cannot create a log at all.

So what we need is a logcat directly after a system start (or lets say, 2-3 minutes after it).

I just took one (with free Logcat Extreme app), filtered for boeffla and the first message in the screenshot is the interesting one - this is the message telling us the rom has initiated the autostart of it.

So, to those that have this issue, I can just say:

- install Logcat Extreme app

- reboot

- open the app after 2 minutes

- type in boeffla in the filter field

- check if you find this ActivityManager: Start proc... message at all

If you find it, it was the apps fault and there might be an error message coming later somewhere (I would need that).

If you do not find it - and I am 99,9999% sure this is the case - the rom's activity manager did not start the app at all. Then it is not an app issue but a rom/configuration issue where I cannot further help.

So, let's the "investigation games" begin :) The root cause is for sure a very simple thing finally...

Also have added a dedicated troubleshooting section under support now on www.boeffla.de:

http://boeffla.de/index.php/support/troubleshooting

Andi
[Galaxy S 4 i9505 Android Development] CarefulThrone65:
<3 <3 <3
[Galaxy S 4 i9505 Android Development] cmert:
thnx to your rom

are there any bugs? does it work camcorder ?
[Galaxy S 4 i9505 Android Development] BenLue:
Jup,

OTA isnt working

Sometimes CAM is crashing (Cant connect to device) After reboot, its working fine
[Galaxy S 4 i9505 Android Development] kenetix:
Looking forward to flashing

Thanks for the new build. One thing i like already is the file size. Nice and small. I like to run lean as possible. I will test it out and see how it rolls.:good:
[Galaxy S 4 i9505 Android Development] gugugrp:
I'm having trouble accessing the download site, and the link to Mega is invalid.
[Galaxy S 4 i9505 Android Development] BenLue:
Sorry, sync fail :/ Download Links are updated.

Greetings
[Galaxy S 4 i9505 Android Development] H3M3L:
Can I pm you?
[Galaxy S 4 i9505 Android Development] Exodusnick:
deleted
[Galaxy S 4 i9505 Android Development] DROCSID:
Thanks - works like a charm
[Galaxy S 4 i9505 Android Development] Exodusnick:
Thanks@BenLue

Thank you for the rom is very stable have hitherto no bugs can recognize :D
[Galaxy S 4 i9505 Android Development] Sasagato:
Hi I noticed that when I take a screenshot andò I try to open it through the statusbar. The Gallery app gets freeze. Am I the only one that gas this bug?. Thanks:svetius:
[Galaxy S 4 i9505 Android Development] gugugrp:
I'm not currently using ROM, but you can download the latest Build to see if it has already been fixed.

http://cm.s3root.ovh/builds/full/
[Galaxy S 4 i9505 Android Development] Sasagato:
No it isn't fixed In already on the latest build.:(
[Galaxy S 4 i9505 Android Development] Deniken:
Thanks man!
[Galaxy S 4 i9505 Android Development] The_Voice_70:
[MENTION=7876431]BenLue[/MENTION]:

Is it possible that you use another mirror for your builds?

This one is very slow:

http://cm.s3root.ovh/builds/full/

;)
[Galaxy S 4 i9505 Android Development] chashmaa:
provide gapps link here.
[Galaxy S 4 i9505 Android Development] The_Voice_70:
http://opengapps.org/

Check this one. I took ARM / 7.1 / nano and everything works fine.
[Galaxy S 4 i9505 Android Development] Exodusnick:
Diese Website ist nicht erreichbar

Die Antwort von cm.s3root.ovh hat zu lange gedauert.

Versuchen Sie Folgendes:

Verbindung prüfen

Proxy und Firewall prüfen

ERR_CONNECTION_TIMED_OUT

This website is not available

The answer from cm.s3root.ovh took too long.

Try the following:

Check connection

Proxy and firewall

ERR_CONNECTION_TIMED_OUT
[Galaxy S 4 i9505 Android Development] Exodusnick:
cm-14.1-20161222-UNOFFICIAL-jfltexx.zip

http://cm.s3root.ovh/builds/full/cm-14.1-20161222-UNOFFICIAL-jfltexx.zip

3,5-7,5 Byte/s - 190 MB von 361 MB

This one is very slow
[Galaxy S 4 i9505 Android Development] Exodusnick:
https://mega.nz/#F!bJ9kmT5A!EvXRZuDW021l2v-0KP8_qA
[Galaxy S 4 i9505 Android Development] andy hall:
The advice when changing android version or switching ROM providers is always clean build.

Upgrading and downgrading the same rom can be done dirty but might have issues depending on other mods in system partition.
[Galaxy S 4 i9505 Android Development] side:
just use the benlue's one
[Galaxy S 4 i9505 Android Development] Exodusnick:
update 24.01 online
[Galaxy S 4 i9505 Android Development] killer!os133:
I had read there that the lineage OS OS had already ported the CMTE and was fully functional, also said that this was already since yesterday in the builds of lineage OS, is this true?
[Galaxy S 4 i9505 Android Development] wooser:
I somehow doubt this, at least active battery life, considering no patches were made to the battery optimization
[Galaxy S 4 i9505 Android Development] Exodusnick:
CMTE ???
[Galaxy S 4 i9505 Android Development] Exodusnick:
update lineage-14.1-20170125-UNOFFICIAL-jfltexx ;)

update lineage-14.1-20170125-UNOFFICIAL-jfltexx.html
[Galaxy S 4 i9505 Android Development] islandman75:
update

Hi, sorry maybe it's been talked about but I didn't find it... anyway: autoupdate says there's new version, which is the one above. After download I click update and the system says will reboot in recovery but screen goes black and after 5 min reboots itself without any installation.

Where has the file downloaded been stored?

If I want to manual install have I to:

- start recovery

- flash new file

- reboot system ?

or

- start recovery

- flash new file

- flash GApps

- wipe Calvik

- reboot system ?

Thank you

Galaxy i9505

TWRP 3.0.2.0.
[Galaxy S 4 i9505 Android Development] forfriends:
Has anyone tried to use whatsapp or wechat voice and video calling on los14? It didn't work for me on the latest cm13 nightly (but did on the snapshot from August 2016).
[Galaxy S 4 i9505 Android Development] Exodusnick:
;)

---------- Post added at 10:41 AM ---------- Previous post was at 10:39 AM ----------

:)

---------- Post added at 10:44 AM ---------- Previous post was at 10:41 AM ----------

Yes i have it worked have it tested

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

Manually into- start recovery

- flash new file

- wipe Calvik

- reboot system

update is /data/data/org.lineageos.updater/app_updates

Manually into start recovery

- flash new file

- flash GApps

- wipe Calvik

- reboot system

update is /data/data/org.lineageos.updater/app_updates

So I always make no problems;)

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

update 25.01. is online on mega here ;)
[Galaxy S 4 i9505 Android Development] Exodusnick:
Update online (afh)
[Galaxy S 4 i9505 Android Development] Mittaa:
Link to Changelog from post #1 https://mega.nz/#!ooZxGLQb!OITWbTNun...DJ_Haz3FreQvxk is broken or removed :eek:

This should work ... LINK
[Galaxy S 4 i9505 Android Development] qd42:
Do you guys have any plans about fixing camera issues? This problem is huge right now and actually makes your ROM unusable for many users (including myself), despite many other things which works good in it.
[Galaxy S 4 i9505 Android Development] forfriends:
[MENTION=5968293]side[/MENTION] made some camera modifications which fix the issue in his roms (optimised los14.1, resurrection remix, his unofficial LOS rom). I hope there is some way to use it with stock LOS.
[Galaxy S 4 i9505 Android Development] Exodusnick:
Check update to afh
[Galaxy S 4 i9505 Android Development] Mittaa:
Check what, where and why ! :cyclops:

---------- Post added at 09:35 AM ---------- Previous post was at 09:26 AM ----------

BTW any news about adding S4 to LineageOS as a official build ? :fingers-crossed:
[Galaxy S 4 i9505 Android Development] Exodusnick:
Check update to mega
[Galaxy S 4 i9505 Android Development] Mittaa:
Could you be a bit more specific PLS ?

Is it a comment to camera issues?

What file or changelog are we talking about?
[Galaxy S 4 i9505 Android Development] Exodusnick:
changelog is afh
[Galaxy S 4 i9505 Android Development] Mittaa:
Date?
[Galaxy S 4 i9505 Android Development] Exodusnick:
Check changelog to mega

---------- Post added at 10:11 AM ---------- Previous post was at 10:07 AM ----------

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

https://mega.nz/#F!bJ9kmT5A!EvXRZuDW021l2v-0KP8_qA
[Galaxy S 4 i9505 Android Development] Mittaa:
Yes yes yes ... got a change log from 27/01 and then what?

Good damned ... why can't you just point out what you mean instead of playing this "hide and seek" game :mad:
[Galaxy S 4 i9505 Android Development] forfriends:
I read the 20170126 and 20170127 log... Don't see anything interesting relating to camera (but I only read it on my mobile so might have missed)
[Galaxy S 4 i9505 Android Development] Exodusnick:
What a hidden game I only provide the updates

Sorry
[Galaxy S 4 i9505 Android Development] forfriends:
I think he just meant a new nightly is out and that the changelog is now available too.
[Galaxy S 4 i9505 Android Development] Mittaa:
Guess your right.

I know that [MENTION=7876431]BenLue[/MENTION] is OP and dev behind this build and [MENTION=6504624]Exodusnick[/MENTION] is his supporter :good:

Really don't want to offence anybody ... just frustrated about the current level (lack) of communication :rolleyes:

What I really would like to know is:

Do [MENTION=7876431]BenLue[/MENTION] want to apply for maintainer role so we can get a official jfltexx 14.1 LineageOS ?

Did [MENTION=7876431]BenLue[/MENTION] add or modify anything to this ROM or is a clean build ?

Page #1 states that "his is a port of LineageOS 14.1 to Galaxy S4 i9505 based on Nougat 7.1.1_r9 and nightlies of LineageOS 14.1 from Sun Jan 8 07:49:59 UTC 2017" .... is this true or is just outdated information?

Thanks ...
[Galaxy S 4 i9505 Android Development] Exodusnick:
This is a message from benlue to me

Depends on. There is no solid planning. Must me again with Invisibilek. The is ex Maintainer of the SG4

Micro is quiet and cm14 is not yet stable for a release

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

The info is for the time being satisfying

Mi englisch is not so got sorry ;)
[Galaxy S 4 i9505 Android Development] Mittaa:
Hi Exodusnick

Language problems explains it all :good:

Thanks for your reply
[Galaxy S 4 i9505 Android Development] Exodusnick:
Update is online lineage-14.1-20170128-UNOFFICIAL-jfltexx.

lineage-14.1-20170128-UNOFFICIAL-jfltexx.html
[Galaxy S 4 i9505 Android Development] forfriends:
Hey, sorry to bother again. Can I also check with anyone if voice calls in WeChat or WhatsApp work?

The reason why I asked is that in the latest CM13.0 nightly 20161218 it didn't work for me (I think I said video call last time I asked when I meant voice call).

Thanks again and sorry for bothering.
[Galaxy S 4 i9505 Android Development] abdu.awad:
i don't know about WeChat but WhatsApp voice call is working fine with me
[Galaxy S 4 i9505 Android Development] Exodusnick:
WhatsApp video & voice call is working fine with me
[Galaxy S 4 i9505 Android Development] Sartolo:
I'm kind of newbie. Do I have to install every update or can I just flash the last release? :D
[Galaxy S 4 i9505 Android Development] abdu.awad:
The last release is enough
[Galaxy S 4 i9505 Android Development] ErichRc24:
I have some questions, on how to install an advanced recovery in Samsung S4 from At&t

Can anyone help me? Please
[Galaxy S 4 i9505 Android Development] rw_on_xda:
sudo heimdall flash --RECOVERY twrp-3.0.2-0-jfltexx.img --no-reboot --verbose

on a linux box.

without "sudo" on a windows box (I guess) in an terminal started as admin
[Galaxy S 4 i9505 Android Development] ErichRc24:
Is there any tutorial on how to do it?
[Galaxy S 4 i9505 Android Development] wooser:
That was the tutorial. Basically it only works on AT&T if you have UCUAMDB or UCUAMDL bootloader if you own an AT&T s4. Check if you have one of those. Google how. If you do, and you're on linux, follow your instructions. If you're on windows, run cmd.exe (search in start menu) as admin and follow his tutorial without sudo. :)

---------- Post added at 12:37 PM ---------- Previous post was at 12:34 PM ----------

Hey, seeing as you understood what [MENTION=6504624]Exodusnick[/MENTION] said, do you think you could do me a favour and say it in english please? I'm having a hard time understanding exactly what it is he wrote.

Did he confirm anything about a maintainer or not? Is it [MENTION=7876431]BenLue[/MENTION]? Any timeline for lineage official or not? Thanks!
[Galaxy S 4 i9505 Android Development] Exodusnick:
update lineage-14.1-20170129-UNOFFICIAL-jfltexx.zip ;) AFH

lineage-14.1-20170129-UNOFFICIAL-jfltexx.html
[Galaxy S 4 i9505 Android Development] Mitsch79:
Flash the last release. If you are coming from a rom that's not Android 7.1.1 based or twrp shows you "can not flash on top of incompatible data" then you have to do a full wipe (system, data, cache, dalvik). You might have to delete the .android_secure folder on your external sd if you have one. And you have to flash opengapps for Android 7.1 arm (choose nano since pico sometimes causes problems). And if you want root access you have to flash the extra su package from download.lineageos.org

You will most likely loose your data and stuff. So backup what you need.
[Galaxy S 4 i9505 Android Development] forfriends:
I know this is a known issue, but has anyone figured out a way to fix or work around the video recording bug? And is there a plan to tackle this?

Cheers for the hard work, not meaning to complain.
[Galaxy S 4 i9505 Android Development] Buff99:
I'd imagine Camu would work, as it usually does.
[Galaxy S 4 i9505 Android Development] qd42:
My solution on CM 13.1 was to disable default camera app and using third-party camera app with it's own binaries like Open Camera, Camera MX, Snap etc. This worked for me.

Another solution is to use LineageOS build by [MENTION=5968293]side[/MENTION] with implemented patches for camera. I'm using this option right now and it works great. I had only one isolated "Can't connect to the camera" episode in the last ~20 days.
[Galaxy S 4 i9505 Android Development] rw_on_xda:
Don't know if I have that bootloader.

Me phone is an german S4, GT-I9505ZKADBT

[MENTION=7634533]ErichRc24[/MENTION]

there are tons of howto's in the Inet, google is your friend !

[MENTION=6504624]Exodusnick[/MENTION]

am besten du schreibst deine statements in Deutsch, dann kann ich die übersetzen.

you better do write your statements in german, so I will translate them to english.

for the people with battery drain:

battery => battery saver and performance => Automatic optimization

brings my draining down to ~5%/24h (don't kown if that hits other unwished impacts)
[Galaxy S 4 i9505 Android Development] Exodusnick:
schau mal hier https://xdaforums.com/galaxy-s4/general/ref-galaxy-s4-i9505-modems-bootloaders-t3315987/post65350237#post65350237

XXUHPK2 –LATEST-- GSM and NON-HLOS

BOOTLOADER den hab ich auf mein samsung s4 I9505
[Galaxy S 4 i9505 Android Development] Exodusnick:
lineage-14.1-20170130-UNOFFICIAL-jfltexx.zip Afh

lineage-14.1-20170130-UNOFFICIAL-jfltexx.html Afh