Related
[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CALL scripts/checksyscalls.sh
CHK include/generated/compile.h
CC drivers/input/touchscreen/ft5x06_ts.o
drivers/input/touchscreen/ft5x06_ts.c: In function 'ft5x06_get_factory_id':
drivers/input/touchscreen/ft5x06_ts.c:432:45: warning: 'ft5336_bootloader_ver' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: ft5x06_ts.c:432
make[3]: *** [drivers/input/touchscreen/ft5x06_ts.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
DevendraMilmile121 said:
[email protected]:~/android/kernel$ make zImage
CHK include/linux/version.h
Click to expand...
Click to collapse
its toolchain error..use Linaro 4.6 toolchain
Luffy.d said:
its toolchain error..use Linaro 4.6 toolchain
Click to expand...
Click to collapse
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
DevendraMilmile121 said:
Thanks Bro Problem Now solved now another problem presist
Code:
CC drivers/video/msm/mdss/mdss_mdp_overlay.o
drivers/video/msm/mdss/mdss_mdp_overlay.c: In function ‘mdss_mdp_overlay_ioctl_handler’:
drivers/video/msm/mdss/mdss_mdp_overlay.c:2273:1: warning: the frame size of 1280 bytes is larger than 1024 bytes [-Wframe-larger-than=]
error, forbidden warning: mdss_mdp_overlay.c:2273
make[4]: *** [drivers/video/msm/mdss/mdss_mdp_overlay.o] Error 1
make[3]: *** [drivers/video/msm/mdss] Error 2
make[2]: *** [drivers/video/msm] Error 2
make[1]: *** [drivers/video] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain
Luffy.d said:
this also seem toolchain error bro....do one thing bro use sabermod toolchain
i successfully compile the kernel with saber toolchain
Click to expand...
Click to collapse
Im using 64bit os any problem with this and can u give me saber toolchain link
DevendraMilmile121 said:
Im using 64bit os any problem with this and can u give me saber toolchain link
Click to expand...
Click to collapse
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9
Luffy.d said:
os is ok....try this toolchain
https://github.com/SaberMod/arm-eabi-4.9
Click to expand...
Click to collapse
4.9 won't work, you'll need 4.7(i use linaro)
CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i use linaro 4.6 no luck i will try 4.7 and tell u tomorrow
CoreWolf said:
4.9 won't work, you'll need 4.7(i use linaro)
Click to expand...
Click to collapse
i tried it work...getting one or two error but compile successfully
I downloaded both tool chain Im trying today
@DevendraMilmile121 have you solved compilation errors? which toolchain you are using ??
Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo
DevendraMilmile121 said:
Used linero 4.7 2014 build. compile kernel but some problem in display driver it show only mi logo
Click to expand...
Click to collapse
how did you repack kernel? did you generate a dt.img?
thewisenerd said:
how did you repack kernel? did you generate a dt.img?
Click to expand...
Click to collapse
same question wat i have did you get the DT.img ???? m stuck there :crying:
Tarun93 said:
same question wat i have did you get the DT.img ???? m stuck there :crying:
Click to expand...
Click to collapse
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)
thewisenerd said:
p.s. compiled kernel, added s2w, dt2w (by showp1984) (thx showp1984)
Click to expand...
Click to collapse
i wanna get my carbon rom kicked up with the kernel source i have the kernel ready with a couple of governors n schedulers n working on other things too but i wanna have a stock kernel kicked in n booted first for the rom tried everything i could but cant get it started @thewisenerd do you have any idea how do i get around this ??
I pack kernel on windows I have two system .kernel booted but only show mi logo how to solve this
How to solve milogo bug
DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
What you had done with source code?
DevendraMilmile121 said:
How to solve milogo bug
Click to expand...
Click to collapse
the kernel wont work on old cm and old rom....try it on latest cm11 r15 and see the magic
Github repo: https://github.com/kernel-killer/android_kernel_huawei_h30u10
All changes I made since last commit are in my private repo.
Install packages (Not sure if it's right):
Code:
sudo apt-get install build-essential
Note: Please run ./mk ckeck-env to verify your build enviroment (Newer GNU MAKE will fail but the code compiles the same with new or older version)
Build:
Code:
./mk bm_new k
Testing your new kernel:
Download both attachments (KernelSwapper and BootimgRestore).
Append headers from stock kernel to zImage (which can be found at ./out/target/product/huawei82_cwet_kk/obj/KERNEL_OBJ/arch/arm/boot/zImage)
In KernelSwapper update 'kernel' with your own generated zImage rename it to 'kernel' and replace it inside zip.
In BootimgRestore replace 'boot.img' with your current ROM's boot.img in case that something goes wrong (e.g.: Phone not booting).
Copy the two new zips into phone's memory (or SD card) and flash KernelSwapper.
===== Reserved #1 =====
Thanks for the awesome work KK. I am on CM 13 3.4.67 kernel. Can i use this or do i have to be in stock rom for testing the kernal?
Sent from my Honor 3C using Tapatalk
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
Update : Flashed the kernel, phone booted but felt laggish while using. I am still testing, will let you know what happens
Sent from my Honor 3C using Tapatalk
karkeankit said:
Thanks for the awesome work KK. I am on CM 13 3.4.67 kernel. Can i use this or do i have to be in stock rom for testing the kernal?
Sent from my Honor 3C using Tapatalk
---------- Post added at 06:12 AM ---------- Previous post was at 06:02 AM ----------
Update : Flashed the kernel, phone booted but felt laggish while using. I am still testing, will let you know what happens
Sent from my Honor 3C using Tapatalk
Click to expand...
Click to collapse
Yes, I'm sure that the kernel has multiple bugs. The phone may feel laggish because there is enabled low-level kernel debugging over UART.
Thank you for testing...
kernel.killer said:
Yes, I'm sure that the kernel has multiple bugs. The phone may feel laggish because there is enabled low-level kernel debugging over UART.
Thank you for testing...
Click to expand...
Click to collapse
You are welcome, wishint you good luck for further development
Sent from my Honor 3C using Tapatalk
Hi, tnx for The kernel
if i Update my kernel VPN bug in CM12.1 will fix?
hamadk said:
Hi, tnx for The kernel
if i Update my kernel VPN bug in CM12.1 will fix?
Click to expand...
Click to collapse
Nope, it's ROM bug not a kernel bug plus I have released only development preview version which has enabled many debugging options and it may be quite buggy.
Thanks, but can this process led to a suitable kernel for CM13?
Does this kernel fixes the video playback problem and the recording problem?(Can't play or capture 720p videos, screen recorder works fine, just the camera.)
Sent from my Huawei Honor 3C using XDA Labs
Lumpbloom7 said:
Does this kernel fixes the video playback problem and the recording problem?(Can't play or capture 720p videos, screen recorder works fine, just the camera.)
Sent from my Huawei Honor 3C using XDA Labs
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=67848925&postcount=8
mhxygh said:
Thanks, but can it this process led to a suitable kernel for CM13?
Click to expand...
Click to collapse
Aim of this project is to make stock kernel sources stable for KitKat ROMs (It is originally for KK) but somebody else may patch them for CM 13. I am not working on this nor I'll do.
Will you be adding extra CPU governors and IO schedulers along with kernel level wakeups for double tap waking?
I was wondering who else is developing kernel 3.10.XX for this device ?
Ms_Julia said:
I was wondering who else is developing kernel 3.10.XX for this device ?
Click to expand...
Click to collapse
Actually, nobody is working on 3.10.X kernel. And I'm rather focusing on LineageOS for now.
What is the defconf for our device in kernel source
imranpopz said:
What is the defconf for our device in kernel source
Click to expand...
Click to collapse
This should include most configs
Code:
/* Mediatek common */
./mediatek/config/common/autoconfig/kconfig/AEE
./mediatek/config/common/autoconfig/kconfig/USER
./mediatek/config/common/ProjectConfig.mk
/* MT6582 common */
./mediatek/config/mt6582/autoconfig/kconfig/platform
./mediatek/config/mt6582/ProjectConfig.mk
/* h30u10 device specific */
./mediatek/config/huawei82_cwet_kk/autoconfig/kconfig/project
./mediatek/config/huawei82_cwet_kk/ProjectConfig.mk
kernel.killer said:
This should include most configs
Code:
/* Mediatek common */
./mediatek/config/common/autoconfig/kconfig/AEE
./mediatek/config/common/autoconfig/kconfig/USER
./mediatek/config/common/ProjectConfig.mk
/* MT6582 common */
./mediatek/config/mt6582/autoconfig/kconfig/platform
./mediatek/config/mt6582/ProjectConfig.mk
/* h30u10 device specific */
./mediatek/config/huawei82_cwet_kk/autoconfig/kconfig/project
./mediatek/config/huawei82_cwet_kk/ProjectConfig.mk
Click to expand...
Click to collapse
Replace Device Name with the configuration file found at:
Source/arch/arm/configs
It's written in this way something_DeviceCodename_user_defconfig
I need for the above step.. ☝☝☝
imranpopz said:
Replace Device Name with the configuration file found at:
Source/arch/arm/configs
It's written in this way something_DeviceCodename_user_defconfig
I need for the above step.. ☝☝☝
Click to expand...
Click to collapse
Well... This is Mediatek, DO NOT expect the sources to look nice. The configs are scattered through ./mediatek subdirectories, *.mk files are parsed and configs are assembled during build. Unfortunatelly, even if you manually assemble .config you will NOT be able to build the kernel. It is full of dirty hacks (Mediatek) and just typing "make" won't work, build will break.
Build:
Code:
$ git clone https://github.com/kernel-killer/android_kernel_huawei_h30u10.git
$ cd android_kernel_huawei_h30u10
$ export ARCH=arm && export ARCH_MTK_PLATFORM=mt6582 && export TARGET_PRODUCT=huawei82_cwet_kk
$ export CROSS_COMPILE=/path-to-your-toolchain/.../bin/arm-linux-androideabi-
$ ./mk n k
Code:
$ ./mk -h
Usage: (makeMtk|mk) [options] project actions [modules]
Options:
-t, -tee : Print log information on the standard-out.
-o, -opt=bypass_argument_to_make
: Pass extra arguments to make.
-h, -help : Print this message and exit.
Projects:
one of available projects.
Actions:
listp, listproject
: List all available projects.
check-env : Check if build environment is ready.
check-dep : Check feature dependency.
n, new : Clean and perform a full build.
c, clean : Clean the immediate files(such as, objects, libraries etc.).
r, remake : Rebuild(target will be updated if any dependency updats).
mrproper : Remove all generated files + config + various backup files in Kbuild process.
bm_new : "new" + GNU make's "-k"(keep going when encounter error) feature.
bm_remake : "remake" + GNU make's "-k"(keep going when encounter error) feature.
mm : Build module through Android native command "mm"
mma : Build module through Android native command "mma"
emigen : Generate EMI setting source code.
nandgen : Generate supported NAND flash device list.
codegen : Generate trace DB(for META/Cather etc. tools used).
drvgen : Generate driver customization source.
custgen : Generate customization source.
javaoptgen : Generate the global java options.
ptgen : Generate partition setting header & scatter file.
bindergen : Generate binder related information
sign-image : Sign all the image generated.
encrypt-image : Encrypt all the image generated.
update-api : Android default build action
(be executed if system setting or anything removed from API).
check-modem : Check modem image consistency.
upadte-modem : Update modem image located in system.img.
modem-info : Show modem version
gen-relkey : Generate releasekey for application signing.
check-appres : Check unused application resource.
sdk : Build sdk package.
win_sdk : Build sdk package with a few Windows tools.
banyan_addon : Build MTK sdk addon.
banyan_addon_x86 :Build MTK sdk x86 addon.
cts : Build cts package.
bootimage : Build boot image(boot.img).
cacheimage : Build cache image(cache.img).
systemimage : Build system image(system.img).
snod : Build system image without dependency.
(that is, ONLY pack the system image, NOT checking its dependencies.)
recoveryimage : Build recovery image(recovery.img).
secroimage : Build secro image(secro.img).
factoryimage : Build factory image(factory.img).
userdataimage : Build userdata image(userdata.img).
userdataimage-nodeps
: Build userdata image without dependency.
(that is, ONLY pack the userdata image, NOT checking its dependencies.)
dump-products : Dump products related configuration(PRODUCT_PACKAGE,PRODUCT_NAME ect.)
target-files-package
: Build the target files package.
(A zip of the directories that map to the target filesystem.
This zip can be used to create an OTA package or filesystem image
as a post-build step.)
updatepackage : Build the update package.
dist : Build distribution package.
Modules:
pl, preloader : Specify to build preloader.
lk : Specify to build little kernel.
md32 : Specify to build DSP md32.
tz, trustzone : Specify to build trusted execution environment.
k, kernel : Specify to build kernel.
dr, android : Specify to build android.
NULL : Specify to build all components/modules in default.
k <module path>
: Specify to build kernel component/module with the source path.
dr <module name>
: Specify to build android component/module with module name.
Other tools:
prebuilts/misc/linux-x86/ccache/ccache -M 10G
: Set CCACHE pool size to 10GB
Example:
./mk -t e1k emigen
: Generate EMI setting source code.
./mk -o=TARGET_BUILD_VARIANT=user e1k n
: Start a user mode full build.
./mk listp : List all available projects.
./mk e1k bootimage
: Build bootimage for e1k project.
./mk e1k bm_new k
: Build kernel for e1k project.
./makeMtk e1k c,bm_remake pl k
: Clean & Build preloader and kernel for e1k project.
./makeMtk e1k n k kernel/xxx/xxx
: Build(full build) kernel component/module
under the path "kernel/xxx/xxx" for e1k project.
./makeMtk e1k r dr Gallery
: Rebuild android module named Gallery for e1k project.
./makeMtk e1k mm packages/apps/Settings
: Change Directory to packages/apps/Settings and execute "mm"
./makeMtk e1k mma packages/apps/Settings
: Change Directory to packages/apps/Settings and execute "mma"
Edit:
I fixed the sources, so menuconfig can be used.
Apply patch:
Code:
$ git am 0001-Fix-build-using-make-command.patch
Build:
Code:
$ cd kernel && export ARCH=arm && export ARCH_MTK_PLATFORM=mt6582 && export TARGET_PRODUCT=huawei82_cwet_kk
$ export CROSS_COMPILE=/path-to-your-toolchain/.../bin/arm-linux-androideabi-
$ make -C $(pwd) O=output h30u10_defconfig menuconfig
$ make -C $(pwd) O=output
Append MTK headers:
Code:
$ ../mediatek/build/tools/mkimage output/arch/arm/boot/zImage KERNEL > output/zImage
*Note: I recommend using AOSP arm-linux-androideabi-4.9 toolchain.
Getting cp: cannot stat 'out/target/product/huawei82_cwet_kk_kernel.log
Make [1]: [kernel ] error 1
Make: *** [remake] error 2
I tried to compile kernel from official CM github, but I end up with this errors:
"Make [1]: *** No rule to make target� arch / arm64 / boot / dts / hydrogen-msm8956-mtp.dtb �, required for� arch / arm64 / boot / Image.gz-dtb �Stop.. "
I tried disable "build_appended_dtb" , but this is not correct.
it worked, but the Image still not boot
I tried to clone some of GitHub repos:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource
https://github.com/TheStrix/android_kernel_xiaomi_msm8956
https://github.com/zhaochengw/android_kernel_xiaomi_hydrogen
https://github.com/karthick111/android_kernel_xiaomi_hydrogen
All they show this error!
Help me please
It works after doing this:
Code:
cp -arn arch/arm/boot/dts/* arch/arm64/boot/dts/
cp -arn include/dt-bindings/* arch/arm64/include/
TEKME said:
It works after doing this:
Code:
cp -arn arch/arm/boot/dts/* arch/arm64/boot/dts/
cp -arn include/dt-bindings/* arch/arm64/include/
Click to expand...
Click to collapse
Make to compiling kernel xiaomi mi max Hydrogen with iptables function?
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Offline charging
Prerequisites:
TWRP version 3.0.2 (https://drive.google.com/file/d/1Hcc1T1-iUEo1ATpPf_Kcu3vXqGR3Boq_/view)
Galaxy Tab E SM-T113NU (reported by some users that works on T116 models, but this is not guaranteed)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Latest Image build:
https://drive.google.com/file/d/1xEq9lttRw752KqIwXnk5ccUFmLJe4BSJ/view
Source links:
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO
# Kernel
https://github.com/pstglia/linux/tree/T113NU_COM_A_MAO_NO_BOLSO
# device/vendor
https://github.com/pstglia/android_device_samsung_scx35-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_scx30g-common/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_vendor_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
https://github.com/pstglia/android_device_samsung_core33g/tree/T113NU_COM_A_MAO_NO_BOLSO
# frameworks/base (the commit that hacks camera count return to 0 is here)
https://github.com/pstglia/platform_frameworks_base/tree/T113NU_COM_A_MAO_NO_BOLSO
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
(My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note 1:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Note 2:
If you face a bootloop, you can try formatting your efs partition as described bellow (AT YOUR OWN RISK!)
https://forum.xda-developers.com/showpost.php?p=79995765&postcount=42
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
What do you need to get a working camera? I have an actual Samsung SM-T113NU
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse
MrLinDowsMac said:
What do you need to get a working camera? I have an actual Samsung SM-T113NU
Click to expand...
Click to collapse
Hi,
1) I'd need spare time to find a way to make it work.
2) more knowledge would be needed. To build this image, I had basically to adapt Samsung kernel to met 7.1 requirements (I basically cherry-picked commits from remilia15 - SM-G360H) and some other minor changes.
Camera probably requires advanced coding, which is a bit far from my current skills. Enabling it causes crashes during components startup (see bellow):
Code:
04-19 22:37:01.036 227 769 I SprdCameraHardware: getPropertyAtv:0
04-19 22:37:01.036 227 769 I SprdCameraHardware: getNumberOfCameras:2
04-19 22:37:01.036 227 769 I CameraService: disconnect: Disconnected client for camera 0 for PID 227
04-19 22:37:01.036 227 769 E CameraService: initializeShimMetadata: Error initializing shim metadata: Status(-8): '3: connectHelper:928: Illegal argument to HAL module for camera "0"'
04-19 22:37:01.038 585 585 E System : ******************************************
04-19 22:37:01.038 227 909 E isp-video: ISP_RAW: id:0x00, 00927 line, ispserver_thread : ISP_TOOL:isp-video server version 1.0
04-19 22:37:01.039 227 909 E isp-video: ISP_RAW: id:0x00, 00965 line, ispserver_thread : ISP_TOOL:log server waiting client dail in...
04-19 22:37:01.040 585 585 E System : ************ Failure starting system services
04-19 22:37:01.040 585 585 E System : java.lang.RuntimeException: Failed to boot service com.android.server.retaildemo.RetailDemoModeService: onBootPhase threw an exception during phase 600
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:145)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer$2.run(SystemServer.java:1538)
04-19 22:37:01.040 585 585 E System : at com.android.server.am.ActivityManagerService.systemReady(ActivityManagerService.java:13591)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.startOtherServices(SystemServer.java:1466)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.run(SystemServer.java:368)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServer.main(SystemServer.java:237)
04-19 22:37:01.040 585 585 E System : at java.lang.reflect.Method.invoke(Native Method)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
04-19 22:37:01.040 585 585 E System : at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
04-19 22:37:01.040 585 585 E System : Caused by: java.lang.IllegalArgumentException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.throwAsPublicException(CameraManager.java:694)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:778)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getCameraIdList(CameraManager.java:140)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.getCameraIdsWithFlash(RetailDemoModeService.java:492)
04-19 22:37:01.040 585 585 E System : at com.android.server.retaildemo.RetailDemoModeService.onBootPhase(RetailDemoModeService.java:569)
04-19 22:37:01.040 585 585 E System : at com.android.server.SystemServiceManager.startBootPhase(SystemServiceManager.java:143)
04-19 22:37:01.040 585 585 E System : ... 8 more
04-19 22:37:01.040 585 585 E System : Caused by: android.os.ServiceSpecificException: connectHelper:928: Illegal argument to HAL module for camera "0"
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1706)
04-19 22:37:01.040 585 585 E System : at android.os.Parcel.readException(Parcel.java:1645)
04-19 22:37:01.040 585 585 E System : at android.hardware.ICameraService$Stub$Proxy.getCameraCharacteristics(ICameraService.java:404)
04-19 22:37:01.040 585 585 E System : at android.hardware.camera2.CameraManager.getOrCreateDeviceIdListLocked(CameraManager.java:765)
Maybe sources under hardware/sprd/libcamera should be changed in order to make it work...
3) A device to test. The one I was using was borrowed from a friend, but already returned.
In any case, all source code I changed is available on github (check for pstglia on github - repository "local_manifests" maps all the changes (except platform_frameworks_base, which requires the last 2 commits from branch "T113NU_COM_A_MAO_NO_BOLSO".
Muito obrigado pela ROM
Falei com vc lá pelo YouTube e agradeço novamente pela rom. O tablet ficou novo em folha. Continue com seu ótimo trabalho ?
Heyyy, how you've made this custom rom?
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse
YggH said:
I'm trying to build that for my sm-t280, and all instructions doesn't ever exist. if you gimme instructions to build, you'll doing a huge help.
email: [email protected]
Click to expand...
Click to collapse
Hi,
Tried to write a simplified procedure to compile the custom ROM for T113NU. See the 8 steps bellow:
I) Assuming you already have a build environment set up (see [1] as reference), download lineage sources using repo commands (repo init, repo sync)
Note: Use branch cm-14.1 (nougat)
II) After syncing, download core33g.xml from my github ( repo local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO) and copy to .repo/local_manifests (create it if doesn't exists)
III) execute "repo sync" again. The files/sources I modified will be downloaded and updated on source tree
IV) Edit vendor/cm/vendorsetup.sh and add this lunch combo:
Code:
add_lunch_combo lineage_core33g-userdebug
This will allow you to select a target compatible with T113NU when running "brunch"
V) As pointed previous posts, camera was avoiding Android to start. To allow booting, cameras were disabled (forced returned number of cameras to 0).
So, for T113NU, commit "0acc7879a9794aacdff85ef1563807d051114917 - frameworks/base - HACK - Disable cameras" will be needed. This commit is on my github, repository platform_frameworks_base, branch T113NU_COM_A_MAO_NO_BOLSO)
VI) Before compiling, export these environment variables:
Code:
export USE_CCACHE=1
ccache -M 50G
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
export LC_ALL=C
I suggest you to include these on a file in your home dir (ex: ~/.android_profile) and include it every time you want to create a new build:
Code:
source ~/.android_profile
VII) Include build/envsetup.sh to config Android environment
Code:
source build/envsetup.sh
VIII) Compile the ISO using brunch (select lineage_core33g-userdebug option)
This should do it.
For your device (T280) you'll probably want to replace kernel by the one provided by samsung opensource.
Download it from Samsung Opensource Release Center (see [2]) and unpack it to kernel/samsung/core33g (clean previous files first)
Also:
A) After unpacking, cd to kernel/samsung/core33g and execute a "make mrproper" to remove any temp files under the source tree;
B) cd to kernel/samsung/core33g/arch/arm/configs and rename/copy one of the config files there to "cyanogen_core33g_defconfig" (select one that matches your device - in my case was goyavewifi-dt_hw04_defconfig)
C) You'll probably will need commits to make your kernel compatible with Android 7.1. Try cherry-picking the commits I used, starting from 8c97f3624701f53843b7b2da40185cdcd1c7a422
Play around with config/fw files and have lots of pacience. Creating a working image is not always a funny (consumes lots of time and requires much pacience, logging/debugging )
Good luck!
[1] - https wiki DOT lineageos DOT org/devices /bacon/buildcon/build
[2] - opensource DOT samsung DOT com
ps: Does your device uses Spreadtrum SOC, right?
ps2: Except for kernel, most of changes were minor. Most of this commits were based on remilia15 work. Kudos for who really deserve it!
@sasi2006166 @dhruvpatel_9880 Also works with T116!!
MegaStormBR said:
@[email protected]_9880 Also works with T116!!
Click to expand...
Click to collapse
I will try it today ?
@pstglia Thank you soo much For This ROM..I will try this ROM Today on my SM-T116NY.
Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166
pstglia said:
This is a custom ROM build to run on Samsung Galaxy Tab E (SM-T113NU).
This work was based on Remilia Scarlet/Nguyễn Diệp Quỳnh code for SM-G360H phone (which uses Spredtrum sc8830, just like this tablet)
Working
Wi-FI
Bluetooth (file transfer tested only)
Sound
Rotation
Not working:
Camera
Prerequisites:
TWRP version 3.0.2
Galaxy Tab E SM-T113NU (similar models were not tested)
Download links and source:
Please check my github (pstglia, repository local_manifests, branch T113NU_COM_A_MAO_NO_BOLSO)
Download link for compiled ROM can be found on README file.
All repositories are mapped on local manifest (core33g.xml )
branch used for all repositories is "T113NU_COM_A_MAO_NO_BOLSO"
Will update this thread with links when my user reaches the required points (new on xda)
Credits:
The LineageOS Team
Remilia Scarlet/Nguyễn Diệp Quỳnh for SM-G360H work
Fabio Júnior Chaves da Silva (lend his device, even knowing it might become a paperweight)
stephenpump (My first post on xda, so used one of your posts as reference )
Anyone i forgot to mention
Note:
This version of TWRP does not populate ro.build.product, blocking a generated package to be installed
So, if you compile from source "brunch core33g", you can apply the following workaround for you generated installation package:
Unpack generated package into a blank directory
Code:
mkdir /tmp/lineage-pkg
cd /tmp/lineage-pkg
last_gen_pkg=$(ls -tr ${OUT}/lineage-14.1-????????-UNOFFICIAL-core33g.zip | tail -1)
jar xvf ${last_gen_pkg}
Edit META-INF/com/google/android/updater-script and replace this:
Code:
getprop("ro.build.product") == "core33gdx"
by this:
Code:
getprop("ro.build.product") != "core33gdx"
Create a new "patched" package
Code:
cd /tmp/lineage-pkg
jar cvf lineage-14.1-patched-UNOFFICIAL-core33g.zip *
Version Information:
ROM OS Version: Android 7.1.2 Nougat
Kernel Version: Linux 3.10.17
Click to expand...
Click to collapse
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!??
I'll update if something happens..
Shreyas.ĒXĒ said:
Bro I installed twrp 3.0.2 and Wiped Data, Chache,Dalvik and system..And I flashed the ROM.. It showed "Unknown Command [log]" BUT FLASHING WAS SUCCESSFUL..So I Botted the tab and now it's showing the Lineage OS boot animation from 15 mins..Ik it takes a hell lot of time for the first boot but 15 mins?!
I'll update if something happens..
Click to expand...
Click to collapse
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg
sasi2006166 said:
Going to fix camera gimme sources
---------- Post added at 10:04 AM ---------- Previous post was at 09:58 AM ----------
Also pm me on Telegram @sasi2006166
Click to expand...
Click to collapse
Hi, this manifest has all the repositories changed (except framework-native, which also can be pushed from my github, branch T113NU_COM_A_MAO_NO_BOLSO)
# Local manifest
https://github.com/pstglia/local_manifests/tree/T113NU_COM_A_MAO_NO_BOLSO
# Framework-Native
https://github.com/pstglia/frameworks-native/tree/T113NU_COM_A_MAO_NO_BOLSO
pstglia said:
Hi
5 minutes is the maximum time. 15 minutes can be threated as a bootloop.
Some users reported this on youtube (for T113NU models).
Try pluging USB and check if you have adb connection. If so, check logcat/dmesg
Click to expand...
Click to collapse
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions??
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk
Thanks for the rom! I am using this ROM whit gapps pico and works everything so good! !!
Enviado desde mi Nexus 5X mediante Tapatalk
dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
dhruvpatel_9880 said:
I will try it today
Click to expand...
Click to collapse
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!
Shreyas.ĒXĒ said:
I took a Logcat file.But I am not able to attach it to this post it's showing"Bad Request"I think you are right my Tab is Bootlooped..Any solutions?
Edit: I have uploaded a Google drive link for the logcat.log file..pls see it..
https://drive.google.com/file/d/15491N45mEhIb-MZU72ef83VESCEK_WGi/view?usp=drivesdk
Click to expand...
Click to collapse
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia
This rom technically should work if the device code name is " goyave ".mine was sm-t116 and code name is "goyave3g".And working perfectly .
pstglia said:
Hi,
Unfortunatelly couldn't get any clue by logcat output. Can you post dmesg as well?
@All
Anyone with experience in LineageOS ROMS could give a clue?
Some user with identical device models I had in hand (T113NU) reported the same issue. In these cases, logcat stops logging at the beginning and I couldn't figure out any related message on dmesg?
I'm discarding hw failure because stock ROM works in these cases (based on reports from users)
Regards
pstglia
Click to expand...
Click to collapse
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
MegaStormBR said:
Hey man, I think something is wrong, T116NY and T116BU are identical. Here's what I've done:
- Made a Nandroid backup
- Downloaded Opengapps 7.1 ARM Pico
- Downloaded the ROM
- Downloaded TWRP 3.0.2 from dl.twrp.me/goyave
- Wiped System, Data, Cache and Dalvik
- Flashed the ROM, OpenGApps, then TWRP, in this order.
You should try it this way.
---------- Post added at 08:51 PM ---------- Previous post was at 08:47 PM ----------
If it still doesn't work, check if your using the correct version of TWRP (3.0.2) Download it at the link I gave you.
---------- Post added at 08:57 PM ---------- Previous post was at 08:51 PM ----------
PS: I wasn't able to reply the private message
---------- Post added at 09:38 PM ---------- Previous post was at 08:57 PM ----------
When I flashed the ROM, I noticed that it was running on a lower resolution than the normal (480p instead of 720p). If anyone else have this issue, just go to build.prop and change lcd_density to stock value (In my case is 160). Hope this helps!
Click to expand...
Click to collapse
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..
Shreyas.ĒXĒ said:
Sorry lol..I forgot to add dmesg..
I have given the LATEST logcat and Dmesg file in the link below..pls see it..
https://drive.google.com/folderview?id=1-8xJgzLeSE8TJxv5gh_ZXTLyXbB-0IcK
---------- Post added at 05:24 AM ---------- Previous post was at 05:21 AM ----------
Bro I tried your method but still It's Bootlooping(stuck on Lineage OS boot animation)
P.s: I have already installed Twrp version (3.0.2)..
Click to expand...
Click to collapse
Huh, thats weird. T116BU working.
Dear All,
I'm new to this forum, so apologies if this is not the right section for my question.
I'm entering the world of AOSP and I built the product target aosp_arm64-eng on a MacOS M1 (ARM64 processor).
Unfortunately when I launch the emulator I get a kernel panic with the below message and I would like to understand how I can debug it
Code:
RAMDISK: lz4 image found at block 0
RAMDISK: lz4 decompressor not configured!
Invalid ramdisk decompression routine. Select appropriate config option.
Kernel panic - not syncing: Could not decompress initial ramdisk image.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.18.94+ #1
Hardware name: ranchu (DT)
Call trace:
[<ffffffc00008a590>] dump_backtrace+0x0/0x128
[<ffffffc00008a6cc>] show_stack+0x14/0x1c
[<ffffffc0005ca064>] dump_stack+0x80/0xa4
[<ffffffc0005c95a0>] panic+0xe8/0x228
[<ffffffc00074ba34>] rd_load_image+0x2fc/0x5e0
[<ffffffc00074be30>] initrd_load+0x50/0x2cc
[<ffffffc00074b47c>] prepare_namespace+0xd8/0x1ac
[<ffffffc00074ad04>] kernel_init_freeable+0x1bc/0x1dc
[<ffffffc0005c8150>] kernel_init+0x10/0xf4
Rebooting in 5 seconds..Reboot failed -- System halted
From the message it seems that the kernel is not configured correctly.
How can I check if the kernel I build contained the LZ4 support with which the Ramdisk image seems to be compressed?
Thanks.
I think it's not possible to run an emulator on a mac with an arm processor see here