Camera does not working when using kernel compiled from OSRC source - Samsung Galaxy Note 8 Questions and Answers

Hi, I just got my hand on the Galaxy Note 8, I immediately tried to root and compile a custom kernel for it, I'm running Android 9 latest version and used the latest kernel source code on Samsung OSRC but for some reason, the camera refuses to work if I use my custom kernel.
I built my custom kernel simply by unpacking the stock firmware boot.img, replaced the zImage and put it back together.
After a while of investigating and tried to use custom kernel built by other people, I realize that they replaced the camera firmware in /system/vendor/firmware/ with the files fimc_is_lib.bin fimc_is_rta_imx333_3h1.bin fimc_is_rta_2l2_3h1.bin fimc_is_rta_imx333_imx320.bin fimc_is_rta_2l2_imx320.bin and the camera was functioning with their kernel but somehow I still unsuccessful on getting my OSRC kernel with a camera working on this phone with their firmware files.
I've searched all over the internet and there doesn't seem to be any thread talking about such issue so I'm currently in a dead end
So anyone knows what's going on with the camera firmware of this phone, please let me know.
Thanks.

Related

[MOD][PROJECT][WIP]Port Note 8(N8000) Mali drivers & lib files

This is not a place holder however there is no actual mod yet for us to test yet this is a work in progress and I Encourage anyone and everyone to help out...
THE CONCEPT:
I asked Gokhan Moral if it was possible to back port the newer Mali drivers CM 10.1 to be used in official Samsung firmware...
Now for this to work we need matching Android library files compiled for the kernel drivers...
His intriguing reply was that the recently released Galaxy Note 8 uses newer Mali drivers (turns out not the same ones as CM10.1 but newer that official S3 firmware) and assuming the Note 8 is running Android 4.1.2 then there is a good chance the lib files WILL be compatible with current S3 firmware...
It turns out the note 8 firmware IS 4.1.2 based and the kernel sources contain the necessary drivers so...
Let's give this a crack eh?
GOALS:
#1 compile Mali drivers from Note 8 sources into existing Siyah sources thus creating a working kernel.
#2 obtain and identify necessary matching lib files from Note 8 firmware.
#3 transplant these libs into an S3 custom ROM and see if they work
#4 create and release a CWM zip which will flash both the custom kernel and lib files which can be used to mod any existing 4.1.2 Samsung firmware.
#5 crack a beer any bask in the satisfaction of a job well done...
PROGRESS:
#1 Budding developer and valued contributor to this forum psndna88 is already merging the necessary code with the latest Siyah sources. A test kernel should be conceived soon...
If anyone else wants to give this a go with other sources please do
#2 A request was made on the Note 8 forum and I have the necessary lib files ready to be back ported once the test kernel is ready...
If anyone has anything useful to contribute please PM me and follow this thread so once something is ready to be tested you can wet your appetite.
Sent from my GT-I9300 using Tapatalk 2
Reserved...
Good luck,good work
But what's diffrent with note 8 and galaxy s3 firmwares?
LegendM said:
Good luck,good work
But what's diffrent with note 8 and galaxy s3 firmwares?
Click to expand...
Click to collapse
Well probably not a great deal in general however for this project we are interested in using the newer GPU drivers which are in the note8 firmware and apparently also the leaked 4.2.1 S3 firmware also.
The kernel side of things need to match the ROM lib files which are complied by Samsung using their closed xynyos sources.
Since the note 8 firmware uses the same android version as ours then HOPEFULLY we can use the kernel sources and transplant the lib files from the note 8 ROM and get it all working smoothly...
The question assuming this project succeeds is: Are the new Mali drivers noticeably better?
Sent from my GT-I9300 using Tapatalk 2
They give a documented 15-20% performance boost in the Epic Citadel benchmark.
siyah kernel compiled with n8000 mali driver,
but currently following things may be broken:
-mali touch boost
-step5 of gpu freq
-gpu uv
Can codeworkx port those drivers to cm? (I mean source available, binaries)
GR0S said:
Can codeworkx port those drivers to cm? (I mean source available, binaries)
Click to expand...
Click to collapse
the ones we are trying to port are older than current CM 4.2.2 mali drivers, but newer than current stock sammy 4.1.2 drivers
attached is a diff file for changes in stock mali kernel drivers and siyah kernel mali driver for stock rom
and diff for lib files between N8000 and I9300 stock roms
i havent fully applied all changes in mali driver taken from N8000 inserted in siyah kernel source before compiling
Good idea guys.. I have a note 10.1 the n8013 model if it helps
Sent from my GT-I9300 using xda premium
Hello,
Yank555 did something similar with his kernel ( he used the newer Kernel Sources from a Galaxy Tab and built a Galaxy S3 Kernel ), maybe you could send him a PM and ask for help ?
Best regards,
George
P.S: I could help you with the flashable packages and also do some testing if necessary.
OK it looks like the N8000 uses a very similar version of the Mali drivers so there might not be much to gain from this project
Sent from my GT-I9300 using Tapatalk 2

[Q] Problem with S3 LTE

I have a big problem with my S3 LTE (GT-I9305) and the JB4.3 rXTREME ROM + Beoffla or another kernel..
The Device keeps hanging sometimes and when I flashed this ROM, i have a camera issue (the camera hanging)
Anyone have idea?
Look in i9305 boeffla kernel thread. There is a special way to flash the kernel so that camera doesn't hang...
Look for the 1st beta of 4.3 kernel... details are in the post.
Overall, if you have the KNOX bootloader, you will have small issues with any custom ROM and / or kernel...

Unified kernel for msm8974 devices

Unified kernel for msm8974 devices
hi all
we are cooking 1 kernel for all msm8974 devices for all custom roms
Source
https://github.com/sonyxperiadev/kernel
in this moment Z1 (honami) and Z2 (sirius) are tested
feel free to fork, joyn and push back
XDA:DevDB Information
Unified , Kernel for the Sony Xperia Z2
Contributors
jerpelea, Kali-, tilal6991, cdesai
Kernel Special Features:
Version Information
Status: Testing
Created 2014-10-07
Last Updated 2014-10-13
By "custom" you mean based on stock roms or AOSP-derived?
adwinp said:
By "custom" you mean based on stock roms or AOSP-derived?
Click to expand...
Click to collapse
both
depending on what an developer wants to build
What will the impact of this project be on areas that have been problems for aosp projects such as hardware drivers ?
furrypotato said:
What will the impact of this project be on areas that have been problems for aosp projects such as hardware drivers ?
Click to expand...
Click to collapse
1 kernel to rule them all means that 1 hal fixed in 1 device works on all devices
1 patch merged in kernel to fix something fixes same problem on all devices
jerpelea said:
1 kernel to rule them all means that 1 hal fixed in 1 device works on all devices
1 patch merged in kernel to fix something fixes same problem on all devices
Click to expand...
Click to collapse
I hope I'm not presumptuous or wrong: will it come with CWM and/or TWRP recovery versions?
Many thanks.
bonderbond said:
I hope I'm not presumptuous or wrong: will it come with CWM and/or TWRP recovery versions?
Many thanks.
Click to expand...
Click to collapse
this is just source code so depends on developers on what android fork is used
jerpelea said:
both
depending on what an developer wants to build
Click to expand...
Click to collapse
Unless I'm mistaken, the sony source doesn't work with pure AOSP. All AOSP or derivatives roms use the CM android_kernel_sony_msm8974pro or forks of it.
My question is thus the following: is this kernel source compatible with AOSP or like "kernel-copyleft", only with stock rom derivatives?
My custom kernel works on the latter, but I need to use the "msm8974pro" trees for pure AOSP.
Unless I'm missing something?
adwinp said:
Unless I'm mistaken, the sony source doesn't work with pure AOSP. All AOSP or derivatives roms use the CM android_kernel_sony_msm8974pro or forks of it.
My question is thus the following: is this kernel source compatible with AOSP or like "kernel-copyleft", only with stock rom derivatives?
My custom kernel works on the latter, but I need to use the "msm8974pro" trees for pure AOSP.
Unless I'm missing something?
Click to expand...
Click to collapse
it works perfectly on aosp and derivates
new guides published
http://developer.sonymobile.com/knowledge-base/open-source/open-devices/
kernel is rebased
z3 platform (shinano) added to kernel
https://github.com/sonyxperiadev/kernel/commits/aosp/LNX.LA.3.5.1-01110-8x74.0
status
z1 - bringup in progress
z2 - boots
z3 - boots
feel free to push fixes
broadcom wifi is now merged in kernel
crash has been fixed
broadcom wifi crash fixed
Can't boot
@jerpelea I've compiled AOSP Lollipop and it boots fine. I've compiled the kernel from 3.5.2.2 branch of the unified kernel source and successfully made zImage. I've combined the zImage with the resulting dtb and the ramdisk from the AOSP build. I can't get the device to boot for some reason. It's stuck at the Sony boot logo. Did I miss a step ? I've searched online but couldn't get enough help about this.
Tried the same with Kitkat too but same result. Doesn't go past the sony boot logo.
UPDATE
Got it to work The command line argument in the guide provided has android boot device as qcom whereas the one compiled during AOSP has it as "shinano" Took me 1 build to understand this Back to work again
hi All
Busy weeks ....months ...
Progress so far
- unified 3.4 kernel is stable for daily use and community tweaking
As some of you have already seen we have started work on comunity 3.10 unified kernel
This kernel is not finished and not stable but is an invitation for developers to joyn, test and improve a kernel built "by community for community"
Br
J
build guide has been updated for easy reading
http://developer.sonymobile.com/kno...evices/how-to-build-and-flash-a-linux-kernel/
hi all
kernel 3.10 is progressing nice
it can soon be used on SONY AOSP Project
master branch on devices uses 3.10 kernel
l-mr0 branch uses 3.4 kernel
br
J
hi all
3.10 is progressing nice
at this point can be used for L MR1 and shows good battery savings
more enhancements and bugfixes will come soon
br
J
Hi @jerpelea, which of the branches should be used for the 3.10 kernel?
I ll be appreciated that the unified kernel can support d6563.

Kernel source camera problems?

Has anyone else here been playing around with building your own kernel based off the source that Huawei released? I managed to build a kernel and boot image sucessfully which boots my phone perfectly fine, but I am having a problem where the camera is unable to take pictures when running the kernel I built vs the one that came with the phone.
Known problem and Huawei has been notified.
Unfortunately no solution at the moment.
the kernel is missing camera drivers ...which are not in the kernel source

How to build custom kernel for Lenovo p1ma40, to support MagiskHide?

Lenovo p1ma40 runs on Android 5.1. And I want to use MagiskHide but am unable to do so, as , "Pre 6.0 kernels are very likely to have no mount ns procfs support, which is required for MagiskHide to work properly. This Linux kernel feature is only required to be added in Android 6.0."
So, as stated at xda forums, we need to rebuild the kernel with the required patch (https://lore.kernel.org/patchwork/patch/217023/). And set
CONFIG_NAMESPACES=y. My question is : 1) How do I patch the kernel source code(pls give exact steps)? 2)How do I flash the modified kernel? 3) do I need to unlock bootloader to do so?
Thanks in advance.....
Link: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/amp/

Categories

Resources