yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] PeanutBR:
My bad I forgot to say that I'm using the latest crDroid 3.7 version. So it means that wait for the rom's developer update?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Yes... It will be better to stay on an old build... probably version 9 (one of the most stable version).
[Samsung Galaxy S 5 Unified Development] dazemc:
WiFi not working with Resurrection Remix on klte (sm-g900t).
[Samsung Galaxy S 5 Unified Development] Macavity_AU:
Ok

Black Camera issue still happening, regardless of camera app.

1. KLTEDV - 900i

2. Resurrection Remix

3. RR-N-v5.8.4-20170812-kltedv-Official - 8th Aug 2017 - Running OpenGApps

I've flashed the latest SmartPack kernel above and still have camera/video black screen. Like trying to look through a normal SLR with the lens cap on.
[Samsung Galaxy S 5 Unified Development] dazemc:
I just want to say that I experience the same issues with black camera even on stock kernel.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
[MENTION=6095717]dazemc[/MENTION] [MENTION=7909578]Macavity_AU[/MENTION]

Guys, the issue is expected in your case. I'll explain the story once again (though you can easily find from my previous posts.

LineageOS team recently did massive changes in the kernel source code (they actually switch the kernel repo itself into a completely new one and all the builds from the last week of August (I guess so) should be based on this new repo). Consequently, I'm also rebased SmartPack on the top of the new repo. So, the issues started here... the issues reported by most of you are using ROMs build on the first or second weeks of August and they use the old klte kernel repo. My kernel, which is solely based on the new repo will probably make all the sort of issues on such old ROMs.

So, this is my advice to all of you...

1. To use the latest SmartPack kernel, you should use the latest (or the 20170830) LOS, or any latest unofficial RR built by [MENTION=6018432]furkaan28[/MENTION] (I hope he already using the new kernel repo)

2. If you decided to stay with the old RR/crDroid builds, it is advisable to use an old build of SmartPack (preferable stable-v9 (dated on 20170802) which can be found in this folder)...

I hope everything is now clear?
[Samsung Galaxy S 5 Unified Development] marin.weigel:
[MENTION=7060205]sunilpaulmathew[/MENTION]

SM-G900F here,

very old base band XXU1POFE,

LOS 14.1-20170906-NIGHTLY-klte, dirty flashed,

Smart Pack v10_r1, dirty flashed.

Had to reboot once after installing Smart Pack, due to black camera screen in LOS, Open Camera, A Better Camera, WhatsApp.

16 hrs. later camera still works.

Thumbs up, really appreciate your tireless hard work, thank you so much!

Best wishes, Marin

Edit: 23 hours and counting...
[Samsung Galaxy S 5 Unified Development] bytes2bits:
I'm still on crDroid with Sprint so as per your advice I'm looking for V9 of the kernel dated 8/2/2017 for kltespr but the latest one of the old builds available seems to be kltespr_20170727. Is this the one I should use?

And thanks for all you do. It's greatly appreciated.

Update: I'm sorry. I see it now. I was jumping into the klte_spr folder. I see now it's listed outside of the folder. Gonna load it now. Thanks.
[Samsung Galaxy S 5 Unified Development] bytes2bits:
Warning! Stupid question...

I know not to set the sound control On Boot (because mic and earpiece go dead). So then does just launching Kernel Adiutor after I'm booted cause the kernel adjustments to be applied? Is it that simple?

Thanks.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks a lot marin for testing and conformed working...

The speaker and headphone (NOT Bluetooth) gain should work immediately after you increased the gain level in the Kernel Auditor app. The purpose of "Apply on boot" is to stick your fav settings after each reboots (otherwise it become re-configured to default).
[Samsung Galaxy S 5 Unified Development] Macavity_AU:
OK, I must have missed this info along the way. Apologies. I'll revert to Stable v9. Can I just flash this as per normal (Dirty flash and then wipe cache?)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Sure... just flash should be fine (you can even skip the wipe cache after flash)... it will simply replace present zImage with the one from stable-v9...
[Samsung Galaxy S 5 Unified Development] Macavity_AU:
Ignore my stupidity. Found the KLTEDV 20170802 kernel in the folder. Going to flash it

Original message: Just to confirm I went to folder listed and opened the 20170802 folder for KLTEDV. Do I just select the most recent listed kernel in there?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
For kltedv, this is the mentioned one (release date: 20170802)... enjoy...
[Samsung Galaxy S 5 Unified Development] bytes2bits:
Is there any way to reset the cpu voltages back to default values? I made several changes to it and I don't remember where it was when I started and there doesn't seem to be any sort of reset.
[Samsung Galaxy S 5 Unified Development] :
Are you using kernel auditor? If so, go to CPU voltage and disable apply on boot then reboot.
[Samsung Galaxy S 5 Unified Development] marin.weigel:
... camera apps still working...

[emoji106] [emoji108] [emoji122]
[Samsung Galaxy S 5 Unified Development] koobie777:
Thank you so much for this cause I can't get the unofficial build of RR to boot on kltespr so I'm still on RR 8-12 and had some issues with the current build of your kernel. Hopefully RR will get updated ?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
May be you can flash my latest kernel over the latest unofficial RR before rebooting. Then it might boot:p who knows
[Samsung Galaxy S 5 Unified Development] koobie777:
Tried that lol doesn't work but also if I flash your kernel before boot i get no service it's weird, so I boot first and do setup wizard reboot and install kernel. I'm curious though, how come no one does gpu OC? That was one thing I liked about gs3
[Samsung Galaxy S 5 Unified Development] dazemc:
I am running your latest build on RR's latest build and I only have the occasional black camera thing. But, when I first flashed the kernel I couldn't get wifi to work. So.....

1. I wiped everything

2. Installed latest RR build

3. Backed up boot partition only

4. Wiped everything again

5. Restored build that had the wifi issues

6. Restored the boot partition I previously backed up

7. Flashed latest smart pack kernel

I did all this with no reboot and like I said no problems except the occasional black camera. At least no problems on end user. So, maybe try that if people run into problems? Really through all those steps is I flashed the stock kernel over smart pack then flashed smart pack over that.
[Samsung Galaxy S 5 Unified Development] furkaan28:
Latest version, my latest rom ( and yes it uses the new kernel base )

Log for black camera
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I think you also noticed the camera black screen issue with stock kernel too, right?

Thanks. I'll check the log layer. Btw, are you sure that the camera issue is not observed in stock kernel. I do remember a comment that says so. Plz make it sure...
[Samsung Galaxy S 5 Unified Development] furkaan28:
I always flash my boot.img after testing your kernel and camera is working

I already tested boeffla venom newest test kernel which also has the rebase and there the camera works, too.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
May be you (RR) guys can try this test build...

Btw, in my personnel experience, the only (except this one) up-to-date kernel repo as per the GitHub (others might updated but not uploaded) is the original Boeffla kernel and nothing else. So, not sure abt venom...
[Samsung Galaxy S 5 Unified Development] culiacanazo:
Sir, all ("perceived"?) bugs aside, and realizing i may ask something obvious due to my lack of knowledge on the subject: how does this and a caf-base get along?
[Samsung Galaxy S 5 Unified Development] furkaan28:
Again black screen, i experienced that if you open panorama mode, the camera works..

Maybe this helps a little bit
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Why caf? Is RR switched to caf base?

Btw, caf is aosp with additional patches from codeaurora forum... it have all the chances to get along with aosp...

The main error (E/mm-camera****) seems to be same as that of the old log (before rebase)... and I have sadly no clues yet... sorry guys...
[Samsung Galaxy S 5 Unified Development] culiacanazo:
First of all, thanks for your answer.

RR didn't switch, the thing is, with Xposed for Nougat that we currently have, the only ROM that has taken what it is given with not even a hiccup whatsoever, is a CAF based...

And yes, I know better and take the word "optimized" with a grain of salt.
[Samsung Galaxy S 5 Unified Development] Macavity_AU:
I got the black screen again
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Mm... Seems like the issue in RR is difficult to fix. I'll soon test the unofficially RR build by [MENTION=6018432]furkaan28[/MENTION] by myself...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Many new commits are added into the LOS kernel source. I also added tons of commits (mainly related with f2f, tcp's, cpufreq etc) from the main stream Linux. Will push new builds tomorrow... It will hopefully improve the performance & stability. Let's see if it magically solve the issues too :p
[Samsung Galaxy S 5 Unified Development] FurFur_:
:fingers-crossed: fingers crossed it will work :) waiting patiently
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v10_r2

Changes: A lot of commits related with f2f (and few for tcp and cpufreq) are merged from the mainstream Linux. All the commits in the LOS kernel source code till date... This release will hopefully improve the stability and performance (and some issues in the worse case). Everything seems great in my kltekor running Lineage-OS.

For those using other ROMs like crDroid, RR etc, please read this before getting some trouble. The situation in RR is still not know. Anyway, I'll test the latest unofficial RR build today later...

Cheers...

/* Downloads */

kltekor

klte

klteduos

kltedv

kltespr

[B][COLOR="Red"]Plz remember to download the latest build (dated 20170914))[/COLOR][/B]
[Samsung Galaxy S 5 Unified Development] FurFur_:
Going to try and report :) Had many random reboots on Hexagon Ron with version 10 r1 but still used it . It worked better after I switched to ZZMove + Hotplug deactivated .

Thanks again ^-^

Edit :

So .. after some trying with the newest version my review after approximately 30 minutes (?)

1. Passes SafetyNet with Magisk 14 and overall working good :) + Ram management good again. From 300-350 MB free ram I've got 500-600 MB ram free :3

2. Smooth. On the older version I had several lags at boot up , recents apps panel & even in games where it never lagged . Now the lags are gone :) (finally!)

((Just so that you know I'm using always ZZmove always with the same settings))

3. No random reboots till now . Will update my post here if it happens but none for now ;)

4. Camera works perfectly :3 on Open Camera even twice better !

Thanks again dev :) !

For the record :

Model : Klte

Rom : Hexagon Rom

Kernel Version : V10 r2

[Kernel Settings for an overall good battery backup but yet smooth experience :

Governor : ZZMove (Nightmare is good too!)

CPU-Undervolt : -45 (or -50, works perfectly with every governor)

Hotplug : With ZZMove none as it's included in the governor (with Nightmare : Zen-decision)

No other change for now :) Battery lasts long ! Try and tell me if you've got the same results or wanna share some other good "Profiles" ! ]

Edit 2 : just happened without a reason . Camera completely black :/ sadly
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thank you very much for the wonderful review [MENTION=4478692]FurFur_[/MENTION] (one of the best review to my Kernel:p)

Happy to know that the kernel is now working pretty well without big issues...

Regarding the camera black screen, I don't think that it is too annoying like the old situation. I got it once, I just go to recent app switcher, close camera app, restart again, then it works perfectly. Not at all, a reboot is required. How abt your situation?

Btw, Hexagon Rom? Is that new ROM? link plz;)
[Samsung Galaxy S 5 Unified Development] FurFur_:
:D :fingers-crossed: You're welcome ! And. .. the issue is a bit .. stupid . The Camera just ends up in a black screen but the focus (no idea why) still works. It's confusing, I am able to use the camera in Telegram ... But then again the normal camera app or Open Camera doesn't work. It's kinda confusing :'D I don't know why it doesn't works completely sometimes though ..

Hexagon Rom from this thread. It works without any problems and is extremely smooth ! :)

Will flash the newest version with cleaning cache later on today! :) Had to revert back as I didn't exactly had a solution yesterday :cowboy:
[Samsung Galaxy S 5 Unified Development] ifellouttabed:
Hi! I wanna say thank you for this kernel! Increases my SOT and reduces drain while screen is off, making it easy to get through a whole day without having to plug in, all while running smoothly without lag. Great work!

I instilled this a while ago but left because camera crash would cause a restart. I see that you have put in a ton of work into fixing this, and I've happily moved back because there is no more restarts. Thank you!

I'm happily living with the one issue I have found - occasional black camera. - - - I know you are probably tired of hearing about this but I figured I would just share my findings:

1. When camera turns black it does not take photos, and for me I need to reboot to fix it, killing app doesn't work.

2. When camera turns black in one app, it is then black in ALL camera apps (stock RR, open, footej, snapchat, WhatsApp, Google maps) except it ALWAYS works in Google Street view app! I wonder what is different here, might be important.

3. Also when it is black I can't turn flash on.

Anyways, thanks for all your work on this. Klte 900T, RR rom nougat.

TL;DR THANK YOU for this awesome kernel, sharing some interesting info I found about camera.

Edit: clarity:)
[Samsung Galaxy S 5 Unified Development] FurFur_:
You're right in all points :) ! Btw what do you do to fix the black screen ? :confused: A reboot ? Or revert back a version and flash the new version after it ?
[Samsung Galaxy S 5 Unified Development] ifellouttabed:
Sorry, yeah just a reboot.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thank a lot [MENTION=5031178]ifellouttabed[/MENTION] & [MENTION=4478692]FurFur_[/MENTION]

Here I'm attaching one more test build for RR fans (though it should work for all other LOS based ROMs).

I did some changes in my build environment. It may or may not solve the black screen issue in RR (no tested by myself on RR). This build also includes all the recent commits in the LOS kernel source till date... the link is here...

/* Downloads */

klte
[Samsung Galaxy S 5 Unified Development] metasoul69:
Could you make for kltekdi?
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Extremely sorry friend. I do not want to add one more device to my building list (especially a less popular variant) to save my time and workload (of my laptop). You are free to try my klte build (if it works).
[Samsung Galaxy S 5 Unified Development] j1gga84:
[MENTION=7060205]sunilpaulmathew[/MENTION]

If you want to try out another unofficial RR you can try Blackjubel's builds:

https://www.androidfilehost.com/?fid=961840155545596624

he was out of the game since end of may but he is back now.

his old builds were compiled with linaro or uber toolchain and I was using them as my daily driver :good:

regards
[Samsung Galaxy S 5 Unified Development] Kingfisher25:
Installed on my S5 running latest RR Official, had the black screen with camera but a reboot fixed that and memory is down to 900Mb from 1.2Gb.

Everything seams to be working fine, thank you!
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks [MENTION=4699854]j1gga84[/MENTION]

I already noticed the return of Blackjubel yesterday itself. Let's hope for more good works from him.

Btw, I'll for sure test his klte build in my kltekor soon...

You can actually expect much more issues (random reboots, fingerprint not responding etc.) in the official RR built on August 12. The reason is explained here... If you tried an unofficial version, most of the issues (except black camera screen) might be fixed...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Anyone tried yesterday's test builds in RR? any updates?

Anyway, new builds will be uploaded later today or tomorrow morning (Korean time)...
[Samsung Galaxy S 5 Unified Development] FaTa1-Err0r:
I'm using Blackjubel's "RR-N-OMS-v5.8.4-20170917-klte-Unofficial", with "Open_gapps-arm7.1-super-20170918" and Magisk v14.0(1400).

Still get the black screen on camera with your "SmartPack-Kernel-klte-test-20170918.zip", sorry.

Is there anything from my side, I'm doing wrong?

With default RR kernel, camera works fine...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks for the comment. Btw, there might be any mistake from your side. I think RR doesn't like my kernel :p (kidding, I still need to find out the real issue with RR, since camera seems fine in LOS)... anyway, may be you can try the next build which will be uploaded in another few minutes (though I don't have much hope about RR)...
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
New builds...

Stable release: v10_r3

Changes: Another lots of commits related with f2f from the mainstream Linux. All the commits in the LOS kernel source code till date.

For those using other ROMs like crDroid, RR etc, please read this before getting some trouble...

Cheers...

/* Downloads */

kltekor

klte

klteduos

kltedv

kltespr

[B][COLOR="Red"]Plz remember to download the latest build (dated 20170920))[/COLOR][/B]
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Guys, finally I decided to touch the CPU clock speed. I'm currently testing an overclocked (2.84 GHz)/under-clocked (268MHz) version without much issues (plz ser the attachment). If anyone like to test, plz let me know with the device variant... cheers...
[Samsung Galaxy S 5 Unified Development] Blackburn119:
Does it make your phone overheat ?
[Samsung Galaxy S 5 Unified Development] cx-11:
God bro I'm just missing the Pegasus gov. THX for yor support :good:
[Samsung Galaxy S 5 Unified Development] Blackburn119:
You can try Pegasus alternative one like nightmare.
[Samsung Galaxy S 5 Unified Development] :
Ooooo 268 Mhz step! Can't wait for this to release. :)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I can not notice any overheat (ofc, I'm not doing any heavy things like gaming)

Is that really good (I never used). If so, I will think about adding back. Meantime try "Nightmare" which is really good.

Thanks... and I'll end your waiting now...

Here I'm adding the overclocked (and also underclocked) test builds after a day-long testing. The default maximum and minimum frequency will be 2.45 GHz (same as stock) and 268 MHz (one level lower than stock) unless you guys changed in KernelAuditor. For using the overclocked frequencies, plz change the maximum frequency in KernelAuditor (and set "Apply on boot" if you want to stick that changes after reboot). Avoid undervolting while using overclocked frequencies (some devs even recommended over-volting). Please be aware that overclocking will sometimes make issues (for safety, be sure to backup your non-overclocked boot.img in TWRP) . So, do it in your own risk :p

Download links are here... Enjoy...

/* Downloads */

kltekor

klte

klteduos

kltedv

Edit: I found some issues in my kltespr defconfig and, hence, the build is removed. Those who wish to test my kernel on kltespr, please use kltedv build (LOS now (after rebase) using same defconfig for both builds). From next build, I'll merge both devices.
[Samsung Galaxy S 5 Unified Development] Saber:
Nightmare is much better than pegasusq. Pegasusq is an old governor commonly used in the s2 era (without standalone hotplugging drivers), so I don't really think there's much to gain with it.
[Samsung Galaxy S 5 Unified Development] FurFur_:
My test so far ..

Somehow the CPU is on 100% no matter what I did. No matter what Governor or Hotplug. It's slightly warm even when screen is off and it is really ugly ^-^' Over - & Underclocking works actually really good but it seems like something isn't working properly .

Voltage control seems .. a bit mixed up. But I think you did it for best compatibility :)

Surprisingly the camera works extremely good :D

Edit : the one build before (R3 I think) is as .. Different as the other one. Something is really not working properly and it causes the phone to overheat without doing anything .. I will revert to R2 for now ^-^'
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
You mean the CPU use is always 100%? Can you check the cpu stats in the KernelAuditor first tab. Which is the most used frequency (2.8x GHZ?). In my LOS, everything seems just normal though I'm not sure abt the benefits of overclocking (not interested in gaming). I'm using Nightmare + Intelli plug (no under/over volting).

Btw, nice to know that the camera is fine...

By the way, anybody tested the camera in this experimental RR build by the official maintainer?
[Samsung Galaxy S 5 Unified Development] Prime Evil:
By the way, anybody tested the camera in this experimental RR build by the official maintainer?[/QUOTE]

Hi !

I use the latest RR Rom from Blackjubel (RR-N-OMS-v5.8.4-20170920-klte-Unofficial.zip.)

With your new Test Kernel I have continued Black Screen on Camera :(

Interestingly, only when take a picture.

When I make a video, all is fine (no Black Screen)

Greetz
[Samsung Galaxy S 5 Unified Development] PeanutBR:
Same here phone is getting really hot.

Btw I'm using this version for 9 hours and the camera still works great! I have only the overheat problem.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
[MENTION=7210496]Prime Evil[/MENTION]

Hi, its know that my kernel makes camera black screen issues with Blackjubel's and Furkan's unofficial builds. But I'm curious about the latest unofficial build provided by scrawnyb (the official RR maintainer). Probably some of you guys can try... It's here... http://resurrectionremix.fandroid.net/klte/experimental/RR-N-v5.8.4-20170921-klte-stable.zip

Alright. Now I notice the issue. The temperature is around 5 degrees higher even after limiting the maximum frequency to 2.5 GHz. Luckily I haven't added the commits to the main repo yet. Maybe I'll try to only add the 268 MHz cycle (and no overclocking)... Lets see how its goes... Thanks, anyway, for pointing the issues...
[Samsung Galaxy S 5 Unified Development] FurFur_:
Exactly. The least used are the frequencies under 1ghz. The rest is upward from 2,4-2,8 GHz. :)
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I suspect that the issue is related with the 268 MHz additional frequency (everything works flawlessly when I restrict the minimum freq to 300 MHz). I think it is better to remove the entire over/under clocking cycles (why should we invite more issues since we already have enough:p).
[Samsung Galaxy S 5 Unified Development] FurFur_:
Maybe try to add it when the Kernel is completely stable? :) You know, like trying something "new" after you have a solid base :cowboy: :fingers-crossed:
[Samsung Galaxy S 5 Unified Development] :
What are you guys using for thermal? Pick one only lol.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
I simply enable intellithermal and disable the rest...
[Samsung Galaxy S 5 Unified Development] Blackburn119:
After flashed your kernel on the latest LOS my phone keeps killing off apps from memory aggressively including pixel launcher, now back to stock kernel without apps being kill aggressively.
[Samsung Galaxy S 5 Unified Development] sunilpaulmathew:
Thanks...

I'm also recommending KernelAuditor...

over clocking is not yet implemented. however cpu voltage control is presently available...