yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S 5 Unified Development] cal002:
Comparing the video4linux subdev list, one is missing: "s5k2p2xx". And judging from the logs it seems

the msm_companion init isn't done, so the s5k2p2xx firmware isn't loaded (confirmed because

camera/rear/isp_core isn't set). However, the logs don't tell why. mm-qcamera-daemon is supposed

to do the init on first startup, but it does so based on info from the kernel's camera driver.

Maybe something goes wrong earlier during kernel startup, but of course the log is truncated :(

Could you try this:

dmesg -c

logcat -c

restart qcamerasvr

dmesg >log

logcat >log2

(.txt preferred over .zip)

Maybe you could compare the working camera driver with ours?

(kernel/samsung/klte/drivers/media/platform/msm/camera_v2/sensor)

[MENTION=2693412]haggertk[/MENTION]: How about increasing CONFIG_LOG_BUF_SHIFT=19 so we can catch full boot dmesg?
[Samsung Galaxy S 5 Unified Development] lingowistico:
Am I the only one who's noticed that the buildbox is very much dead?

http://www.team-hydra.org/
[Samsung Galaxy S 5 Unified Development] AddictedToB3er:
Why do you need the build box building when there are official nightlies? Correct me if I'm wrong but the build box was for before the official nightlies were approved.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Are you on the latest bootloader? If so have you tried flashing a previous one?
[Samsung Galaxy S 5 Unified Development] ScratMan38:
I had some issues with your commands, as some of them never ended.

I managed to get the logs attached anyway.

I'm on MM bootloader, but the issue waa present also with LP bootloader.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Have you run the boeffla cleaner script? Perhaps you have leftover kernel data interfering as very few people do actual internal memory wipes which has resolved one off issues like your having for me many times.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
I also tried with fully clean flash, wiping internal memory and removing external sd, but it doesn't help.

And Boeffla kernel cleanup script is used to clean other custom kernels before installing boeffla. It's configuration system doesn't interfere with stock kernel.
[Samsung Galaxy S 5 Unified Development] cal002:
The log is not useful, has lots of "Out of memory" and nothing interesting. Too many huge apps?

Right, "logcat" keeps logging, for one-shot dump use "logcat -d" (and "logcat -h" for help).

Your log has nothing after "init: Starting service 'qcamerasvr'...", if it means

"restart qcamerasvr" doesn't work for you, then this method won't help.

Try again, this time get "logcat" output, not just dmesg. But probably you

need a kernel with bigger logbuf to get the complete boot dmesg.

However, you could still try to reboot with "adb logcat | tee log" running

to get the bootup log (start it when you see the Samsung boot logo).

Maybe snip everything not related to mm-camera / mm-camera-sensor.
[Samsung Galaxy S 5 Unified Development] omgbossis21:
Yes I thinking perhaps some prior kernel leftover bits were causing the issue though wiping internal would of covered that.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
This time I used logcat -d and the log contains more thing regarding camera.

Also, I redirected the output of dmesg -c to a file too, and made ran the shell several times, and there is a "init: Starting service 'qcamerasvr'..." in the clear log, with other things after.

I'm not at home today, but I will try adb on boot when I can access my computer. Any prerequisite I need ? I didn't use adb for a while, and it was at work on a booted phone.

And thanks a lot for your help.
[Samsung Galaxy S 5 Unified Development] :
Cannot pass through setup wizard

Install fine and boots fine, about 4 seconds after starting the setup wizard the phone displays a lock icon on the bottom when I try to press the bottom two buttons, and I can't press them, also displays something about Validity not working. Does anybody know how to bypass it? I think my fingerprint scanner doesn't work and it's not allowing me to go through the setup wizard.
[Samsung Galaxy S 5 Unified Development] lingowistico:
Correct me if I'm wront but if someone bought you a buildbox and you're no longer using it per it's original purpose the least you could do is to remove all the dead links in your op about it.

Those dead links are screaming "neglect!!" in your face.

Aren't the nightlies in an XDA thread and the cyanogenmod site, usually, different?
[Samsung Galaxy S 5 Unified Development] haggertk:
Which nightly date? This hinting problem was fixed for me with the 24 Jul nightly.
[Samsung Galaxy S 5 Unified Development] airidosas252:
Using latest nightly build and so far no problems with it at all. Everything's working fine even at 1.5GHz with conversative governor. It's so much snappier than stock ROM. One thing though - Boeffla kernel gives me all sorts of problems, starting with random reboots, crashes, heating and etc. So for now I'm completely stock CM13 user. Battery life is still not as good as stock ROM definitely, there's some room for improvement. Other than that - wow. Quite an accomplishment here.
[Samsung Galaxy S 5 Unified Development] !crazy:
I use encryption together with sdcard as adopted storage and everything works well. The thing is, I have done it at least a year ago, and there was a catch, I had to try few times until I figured the workaround. One either had to do it immediately after installation, maybe before installing google apps, or don't know... I am sorry I cannot really help, but I can confirm it is possible to make encryption working. I will try to think about it, and check my posts from that time, maybe I will find something useful.

---------- Post added at 03:13 PM ---------- Previous post was at 03:05 PM ----------

Good password is much better protection, since PIN consists only from numbers. In my case encryption was successful with a password.

---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------

BTW AFAIK 11.5 is what you usually get from sasmung, probably because of few reasons. First there is giga byte and gibi byte issue (read about it. Usually we always talk about gibi bytes, even if we wrongly use giga, what means thousand, word. In short AFAIK only hard drive manufactures use multiple of 1000, instead of 1024. Your RAM for example is 16 x 1024 mibi bytes, but we say mega/giga bytes.), and further there is a part reserved for system (kernel etc, not system apps.).

[Edit] fixed 'hard drugs he manufactures' (crazy AOSP keyboard auto completion) to hard drive manufactures. Can imagine the reaction of one who never heard of gibi/mibi bytes after reading about their connection to hard drugs :)).
[Samsung Galaxy S 5 Unified Development] jdrch:
Anyone else having trouble with builds since 20160722 being stuck on the CM logo screen after dirty flash?

---------- Post added at 12:11 ---------- Previous post was at 12:10 ----------

Also: what's the best way to backup apps and app data on CM 13? Last time I checked Titanium Backup only worked with SuperSU and so is incompatible with CM.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
Yes, always have trouble with that but a reboot usually fixes it. Also, tb works fine with cm built in root.
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
Whatever man. Good luck with that brah.
[Samsung Galaxy S 5 Unified Development] jejemc:
At the best, thank you and good day to you ;)
[Samsung Galaxy S 5 Unified Development] Jaanto:
I'm afraid the developers will one day just say f#ck it and quit contributing here because of all the ignorance. Questions about fingerprint scanner implementation or when the new updates will arrive, its just cluttering up the whole thread.

But whatever, I can rant all I want but on the next page there will be another stupid question in a few hours. I wish I could just delete stupid questions and let the devs do their thing in peace.
[Samsung Galaxy S 5 Unified Development] tman23:
Well you can just quit with your damn faces because they don't help your case whatsoever....

1. Don't ask for ETAs (with or without cute little faces)

2. Its not albinomans or devortex job either to maintain this ROM, its simply a choice..so don't use the he hasn't said anything in 5 pages garbage..

3. Have common sense and read the op...

4. Oh yea..... ;)
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
Agree completely. And what's worse is when they get called out on their BS, instead of humbly learning a lesson and moving on, they treat it as if you're wrong for pointing it out. I can't imagine what motivates these devs anyway when all they get is narcissistic crap Anne a couple of genuine thanks.

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

Wasting your time man. This guy is part of the problem. You can see he states that he's done nothing wrong. We all need to be quiet because he didn't address us directly.
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
I've been on it since Sunday and aside from a truly epic BT flaw (just read back a couple pages for deets) I have no real problems. Battery charges slow and drains pretty fast. Not an issue for me as I have an 8500mah battery. But it could be for some. I have had no data, WiFi or in call problems.
[Samsung Galaxy S 5 Unified Development] FlemishDroid:
Battery is better then it was on CM12.1 for me but I use Greenify (+ donate settings in Greenify Xposed especially Aggressive Doze feature). I also get the slow charging message but it charges at 1800 mah like it was on CM12.1.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
And your charging speed?
[Samsung Galaxy S 5 Unified Development] FlemishDroid:
The same as on CM12.1 1800.

Verstuurd vanaf mijn SM-G900F met Tapatalk
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
He's gonna do really well here. Can't wait for the boot loop, followed by the begging questions. I won't be responding to the trolls any more. I'm hoping between the devs and the mods karma will be served.
[Samsung Galaxy S 5 Unified Development] Spanky':
Hello everyone been a little while since I've been around quick question.. I see that the ROM has an update for the 11th was that just for certain devices as I didn't see one for kltespr thanks! As the kltespr has the bug for constant bootloop in power saving mode also
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
I'm kltespr and I've had no boot loop. But I don't run power saving mode ever so maybe that's why.
[Samsung Galaxy S 5 Unified Development] Spanky':
Ya I clicked it once when the 15% battery notification popped up and as soon as I tapped it I was like wait NOOOO!! lol but it was to late had to fully wipe and reinstall, that's the only bootloop I've ever had with this ROM soon all good. This ROM is pretty much rock solid
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
Never heard of that happening. Thanks for the heads up. Think I'm going to switch back to 12.1 for a couple weeks. Give them time to fix a few things (and for the trolls to die).
[Samsung Galaxy S 5 Unified Development] Spanky':
Trolls will always be trolls haha who can't appreciate what they have been givin. I learn to just ignore them haha but ya if your willing to do it .. Switch to power saving mode once and see what happens for you.. Of course be warned may cause never ending boot loop lol [emoji6] also GPS isn't doing anything like if I hot directions to a business of of a google page it will bring up google maps to navigate but just sit there and never find a single or a route nothing.. Is that a known bug?
[Samsung Galaxy S 5 Unified Development] AuGmENTor:
I haven't had cause to use maps since installing. I'll try it out on my way home tonight and check back. I may try the power saving thing right before I reset. I've never heard of an unrecoverable brick.
[Samsung Galaxy S 5 Unified Development] Spanky':
Ya well if you do a full wipe and reinstall the ROM and gapps is all good but for me personally my phone started getting hot because it was just in continues bootloop.. But again.. Besides the GPS thing and that one time bootloop thingy I've have zero issues with this ROM i m very happy! Thanks [MENTION=3322708]albinoman887[/MENTION] and everyone involved!
[Samsung Galaxy S 5 Unified Development] luriert:
I have a sprint as well and haven't run into that bootloop issue and I have used power save. I did have a bootloop though when I changed my SD card to integrated or part of the internal storage and had to restart. Did you happen to have the same setup?
[Samsung Galaxy S 5 Unified Development] Spanky':
Well what the hell... I guess my phone hates me LOL
[Samsung Galaxy S 5 Unified Development] jdrch:
I tried rebooting and ran into the same problem. Just stuck at CM logo screen. Restoring from 20160722 Nandroid now.
[Samsung Galaxy S 5 Unified Development] Atento:
Read a few posts ago. It's been answered!
[Samsung Galaxy S 5 Unified Development] jdrch:
I'm having the same problem with my Verizon S5. Wish I could find a solution other than clean flashing or flashing back to TW then back to CM.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
Hello, I managed to grab the logcat during boot, using wtee (I'm on windows, and only a virtual machine for linux, not easy with USB when phone reboots).

I attach the log (sorry, it's zip file, the log is too big as txt for the forum).
[Samsung Galaxy S 5 Unified Development] Pavalev:
I am having problem with exsdcard that doesn't mount, it worked with past release but now it doesn't. I am on latest nightly
[Samsung Galaxy S 5 Unified Development] andacro:
+1
[Samsung Galaxy S 5 Unified Development] theelle:
Me too, sdcard doesn't mount....
[Samsung Galaxy S 5 Unified Development] Germain67:
Same here sadly ... !
[Samsung Galaxy S 5 Unified Development] cal002:
The previous logs were full of out-fo-memory errors, but not much hints about the source of your issue.

This log has:

298 E mm-camera-sensor: sensor_init_probe:366 EEPROM has sensor module information. Load this info
298 E mm-camera-sensor: sensor_init_probe:368 sensor name : s5k2p2xx actuator name : ak7345
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:998 ----- header ------------------------------
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:1012 source size 184164
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:1013 compressed size 42994
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:1015 ----- library -----------------------------
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:1054 loaded : size(184164)
298 E mm-camera-sensor: [mm]load_eeprom_sensor_lib:1055 ----- end of lib layout -------------------
298 E mm-camera-sensor: sensor_probe:183 LOAD from F-ROM
298 E mm-camera-sensor: sensor_load_library:80 s5k2p2xx : load from F-ROM
298 E mm-camera-sensor: sensor_load_library:83 fail to create dummy for sensor library
298 E mm-camera-sensor: sensor_probe:191 failed: to load s5k2p2xx

while on my device I get:

mm-camera-sensor: sensor_init_probe:382 Loading from EEPROM(new or higher version), but no actual F/W bin at F-ROM
mm-camera-sensor: sensor_init_probe:401 sensor name : s5k2p2xx actuator name : NULL
mm-camera-sensor: sensor_probe:187 LOAD from Phone
mm-camera-sensor: sensor_load_library:91 s5k2p2xx : load from phone

So you have a camera firmware in camera EEPROM while usually it is loaded from

/system/cameradata/F16QL_IspX_s5k2p2xx.bin.

It occured to me you can use "logcat -b kernel" to get boot kernel log, or maybe

better use "adb logcat -b all >log" during boot so we get the audit messages from

event log if they are dropped in main log. Maybe we can find the source of the

"fail to create dummy for sensor library". Or can you get rid of the FW in F-ROM?
[Samsung Galaxy S 5 Unified Development] AddictedToB3er:
They're only different if labelled unofficial... Otherwise the thread is for discussion, bug reports or the odd test builds to help iron out bugs before submitting code to the official line.

Yes maybe the dead links should be removed but honestly these guys work way too hard on these Roms that we appreciate their time going into fixes and changes to the rom rather than the thread.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
These are the logs resulting from the two commands you mentioned.

I also made the same with Boeffla kernel 3.0 stable, which boots in permissive, as it may show some interesting differences.

I don't know how to remove the FW from F-ROM. What is F-ROM ? is it the flash inside the sensor or companion chip ? As far as I know, there MUST be a firmware inside the device's EEPROM (at least, it's the case in the camera sensors from my company, otherwise it will not work), but in the case the FW provided by the operating system is newer, it will be used.
[Samsung Galaxy S 5 Unified Development] f0xy:
Nightly 24th is buggy on clean install, system force closes, some apps don't open browser for example
[Samsung Galaxy S 5 Unified Development] SB4BBs:
Which nightly has the best battery life at this point? I'm still on the 21 no issue's but battery seems in terrible on SOT.
[Samsung Galaxy S 5 Unified Development] f0xy:
I would advise against updating as yet. For battery life, depends on user
[Samsung Galaxy S 5 Unified Development] a7thousandths:
I ended up flashing oa6 through Odin and rooting all over again, it was a hassle but it fixed my issue.

I am not a developer so excuse my ignorance, but if someone could confirm what bootloader or kernel or firmware cm13 is based off from different variants that would be great! I think having the one that it is based off would lead for better compatibilty.
[Samsung Galaxy S 5 Unified Development] jdrch:
20160722 was the last one to boot properly. I can't get any build since then to even get past the CM loading screen after dirty flash. Then again CM nightly build quality in general is just terrible. Can't wait for S5 builds to go stable.

---------- Post added at 20:39 ---------- Previous post was at 20:36 ----------

There are specific builds - listed at cyanogenmod.org - for each S5 variant. CM itself is based on AOSP.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
Same issue here with any nightly after 722. I was able to get the phone to boot but once I entered the os none of my apps worked and the error I got was that internal storage was not mounted.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
They have had their challenges, yes, but I wouldn't call them terrible.
[Samsung Galaxy S 5 Unified Development] shirioko:
After dirty flashing 20160724 nightly (upgrading from 20160721) + xposed v85 and wiping cache my SIM card is no longer detected. Anyone else have this issue?
[Samsung Galaxy S 5 Unified Development] BeefTenderloin:
On 722 nightly the bottom of the screen is locked.

Touching skip/next or back doesnt do anything, and presents a little lock icon in the middle at the bottom of the screen.

I can swipe down and the notification bar comes down behind the set up screen

help?
[Samsung Galaxy S 5 Unified Development] airidosas252:
I think latest nightly has this issue fixed already. I had that previously, so I just flashed older build, set it up, and then dirty flashed this one and problems went away. :)
[Samsung Galaxy S 5 Unified Development] omgbossis21:
To save me going back several pages, can you link this camera firmware update you did? We can dissect that to look where exactly its overwriting the previous firmware.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
The procedure for flashing camera FW is there : http://xdaforums.com/galaxy-s5/help/camera-firmware-thread-t2832384

In short, you need a stock Touchwiz ROM, with the Samsung system tools inside, so avoid highly debloated ROMs as they often remove system test apps. In the dialer, type *#34971539# and wait for the Camera Firmware Standard screen to open.

Push the top button "Phone/Cam FW ver check" and it will indicate the firmware versions for rear cam, companion chip and front cam. As far as I understood, Phone = firmware available from the OS, Cam = firmware in device's EEPROM, and Load = used firmware (the latest of the two).

You need to place an empty (0 byte) file named "1q2w3e4r.key" (without quotes) in the root of internal storage in order to be able to use the "write" buttons. But anyway, I can't recommend to perform the write, as it seems it made me some problems :silly:

You may also use the "dump" buttons to backup the actual camera firmware.

Initially, I made this firmware update to improve camera behavior. In theory, using the embedded camera firmware is faster and more reliable than using external firmware. And I confirm that my camera is really fast to launch in Touchwiz, and much slower in CM (when it works).

But what I don't understand, is that I extracted the firmware files named F16QL_Isp0_s5k2p2xx.bin and F16QL_Isp1_s5k2p2xx.bin from different ROM, and they are all the same, while in the camera firmware flashing tool from Samsung, it indicated different versions. I extracted (the codes at the end corresponds to the FW version indicated by the camera FW flashing tool from Samsung for Isp0 and Isp1) :

- Touchwiz 4.4.2 ANG7 (from Alexndr) : HF01GB + HC0410

- Touchwiz 4.4.2 ANG9 (FTM - Orange France) : HF01GB + HC0410

- Touchwiz 6.0.1 CPEF (BTU - United Kingdom) : HF01SB + HC0410

But when I compare these files with the same files I copied from CM system, they are all exact same binary copies !! And they all mention at the end of the file, in ASCII, "F16QLHC0400" for Isp0 and "F16QLHC0410" for Isp1. :silly:
[Samsung Galaxy S 5 Unified Development] omgbossis21:
In system/cameradata I count 11 files, you? Assuming in the process you ran both dump camera options to backup your existing firmware their should be your original camera files somewhere. If you wiped internal since they may be gone however. Have you by chance tried putting the 0 byte file with the specific name in the root of your SD on a cm13 rom and load your camera?
[Samsung Galaxy S 5 Unified Development] lingowistico:
Oh, ok. Good to know.

Sure, I appreciate their work just as well as you do.
[Samsung Galaxy S 5 Unified Development] ScratMan38:
GOT IT !!!!!

I finally managed to make my camera work with stock CM13 kernel, with SELinux set as enforce !!!

By looking at the logs I provided, and comparing with the log [MENTION=7518817]cal002[/MENTION] made on his phone, I found my phone tries to find some informations about the camera module in a missing XML file :

mm-camera-sensor: [mm]check_version:715 firmware version file system/etc/F16QL_s5k2p2xx_module_info.xml
mm-camera-sensor: parse_module_xml:103 Could not find or parse file system/etc/F16QL_s5k2p2xx_module_info.xml

This file is present in the stock Touchwiz ROM, but not in CM, so I tried to copy the xml file from the last Samsung ROM I used to flash my camera firmware, and placed it in the /system/etc/ folder on my phone.

I rebooted, and tadaaaaa !!! camera is working !!!!
[Samsung Galaxy S 5 Unified Development] vphotographic:
so yesterdays update messed up my sdcard and i cant download the latest update to fix it. how do i fix this ??
[Samsung Galaxy S 5 Unified Development] jdrch:
It's quite normal for CM 13 to take a while to recognize the SIM card upon boot. Just be patient. If after 20 min there's still not detection, power down, pull the battery and SD card (and maybe the SIM card), sit for a minute or 2, then put everything back in and boot up again.
[Samsung Galaxy S 5 Unified Development] Cdub1976:
It should be seconds not minutes. They made some changes in the 24th build regarding the SD card which I believe is the culprit to our issues.

To those having issues with 24th build. Just go into twrp and wipe system then flash the previous nightly and your gapps then reboot. All your apps and data will stay intact and it's faster than restoring your backup.
[Samsung Galaxy S 5 Unified Development] jdrch:
Depends on which device you have I guess. My kltevzw build on SM-G900V often takes minutes after the lock screen appears for the SIM card to be detected.