Related
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
Hello!
There is a Nougat 7.1.2 lineage OS 14.1 rom available for HTC 816 (a5)
So I'm trying to build lineage os 16 for HTC 816
First of all I'm no expert . That's why I'm seeking for help.
I have gone through some steps by downloading sources and setting
up environment. (which took more than 14 hours )
But when Im hitting
breakfast a5
Click to expand...
Click to collapse
(A5 is our device code name for lineage os)
It is saying something like this .
Code:
[email protected]:~/android/lineage$ breakfast a5
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_a5".
21:42:42 dumpvars failed with: exit status 1
Device a5 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Found repository: android_device_htc_a5
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_htc_a5. Bailing.
Branches found:
cm-11.0
cm-12.0
cm-12.1
stable/cm-11.0
stable/cm-12.0-YNG3C
stable/cm-12.0-YNG4N
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_a5".
21:42:58 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_a5".
21:43:08 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_a5'
** Do you have the right repo manifest?
It's detecting device. but showing this.
now what to do .
If anyone know please help me out.
Thanks.
Am also getting same problem
am trying to build los 16 for TOMATO(yureka)... and am getting same problem..
any help
I am a htc 816 single sim user I also trying to make an android 9.0 rom but its still not worked yet but I think you should find a way to make some changes to build.prop it may work sorry about my language
Thank you
Any update... I want to use the los 16 on my a5dwg. Plzzz build this rom.?????
Build 24/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 13.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
Expanded volume rocker ( thanks to @agentfabulous )
Direct unlock with face unlock enabled, lock screen options
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 13.0
Added expanded volume rocker (thanks to AgentFabulous)
Added option to disable the direct unlock with face unlock enabled
Project name: proprietary_vendor_oneplus
msm8998: add missing blobs
Project name: android_kernel_oneplus_msm8998
tri-state-key: send proper input when updating keycodes from userspace
Revert "tri_state_key: import driver from msm8996"
tri_state_key: import driver from msm8996
Project name: android_device_oneplus_msm8998-common
msm8998-common: set project_name prop via init
msm8998-common: Add missing blobs
msm8998-common: add missing libmm-omxcore
msm8998-common: set perms on tri-state-key nodes
Project name: android_frameworks_base
Prevent NFE in SystemUI when parsing invalid int
Prevent NFE in SystemUI when parsing invalid int (2)
Prevent NFE in SystemUI when parsing invalid int
SystemUI: Fix FORCE_SHOW_NAVBAR handling on user switch
Clean up screenshot if nothing selected
IMMS should preserve selected IME upon boot
Add bluetooth icon.
Project name: android_frameworks_av
Request to reset effect buffer in clearInputBuffer
Revert "effects: fix volume burst on pause/resume with AudioFX"
Project name: android_frameworks_native
Respect source crop when capturing layers.
libgui: add docs to geometry states and captureScreen
surfaceflinger: fix captureScreen for landscape LCM
surfaceflinger: improve RenderArea needsFiltering
surfaceflinger: respect install orientation in DisplayRenderArea
surfaceflinger: add install orientation to DisplayDevice
surfaceflinger: make mPrimaryDisplayOrientation static
surfaceflinger: clean up captureScreen
surfaceflinger: silence some RenderArea errors
surfaceflinger: fix race conditions in captureScreen
surfaceflinger: remove ISurfaceComposer.h from RenderArea
surfaceflinger: reorder width and height in RenderArea ctor
surfaceflinger: documents RenderArea
Revert "Revert screenshot changes to exclude black cutout"
Revert "APP may display abnormally in landscape LCM"
Project name: android_vendor_lineage
Add APN ION Mobile & APN for Roaming
config: Remove duplicate keyguard.no_require_sim prop
overlay: Move managed profiles overlay to frameworks/base
kernel: Use build-image-kernel-modules instead of copying it
kernel: Use a macro for kernel build targets
kernel: Detect kernel module usage better
kernel: Move kernel module dir cleanup/creation to module install target
kernel: Move full kernel build guard flag below all targets
kernel: Add more threads to kernel build process
Project name: android_packages_apps_Snap
Snap: Fix picture size preference
Project name: android_packages_apps_Trebuchet
Lint fix: Invalid vector path in horizontal_ellipsis
Project name: android_packages_apps_Bluetooth
Update Bluetooth to use adaptive icon.
Project name: android_packages_apps_Nfc
NfcNci: make T3T/Nfc-F HCE optional
Project name: android_hardware_qcom_display
hwc: Handle validateAndSet failures in AD prepare call
Project name: android_hardware_qcom_display
display-hals: Allow building libdisplayconfig
Project name: android_hardware_qcom_audio
msm8960: Add SND_DEVICE_OUT_VOICE_MUSIC_TX
Project name: android_system_core
Fix path for treble default prop
storaged: change log level for health HAL calls
Project name: android_system_vold
increase timeout for waiting on block device
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP13_OP5.zip
MD5: 6872d0b9526c59fe125cb253bf5d6d72
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
Sources :
Rom:- https://github.com/LineageOS
Device:- https://github.com/LineageOS/android_device_oneplus_cheeseburger
Kernel:- https://github.com/LineageOS/android_kernel_oneplus_msm8998
Reserved
1st
Added to the OnePlus 5 Index Thread here.
Build 17/02/2018 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r31 10.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 10.0
Magisk included is now stable version
Project name: proprietary_vendor_oneplus
msm8998-common: add missing blobs
Project name: android_device_oneplus_msm8998-common
msm8998-common: add missing blobs
msm8998-common: selinux: fix some denials
Project name: android_packages_apps_SetupWizard
SUW: Change WizardManager activity default state to disabled
Project name: android_external_chromium-webview
Update x86/x64 Chromium Webviews to 71.0.3578.99
Project name: android_packages_apps_Settings
Settings: Add back summary_collapsed_preference_list for zh-rCN
Project name: android_packages_apps_LineageParts
parts: don't allow clock and network traffic to be enabled at the same time
StatusBarSettings: Hide network traffic settings if device has a notch
Project name: android_packages_services_Telephony
set config_enabled_lte to true by default
Project name: android_frameworks_av
effects: fix volume burst on pause/resume with AudioFX
Project name: android_frameworks_base
Informing app idle listeners on enabled state changes.
Fix for CTS testAllowWhileIdleJobInTempwhitelist
Null locale causing the VTS fail.
SettingsProvider: Allow accessing LineageSettings via settings command
Camera: Simplify code for Aux/Mono white and black lists
Camera: Force HAL1 for predefined package list.
SystemUI: Network Traffic [1/3]
SystemUI: Add Lineage statusbar item holder
fonts: Build different fonts.xml if EXCLUDE_SERIF_FONTS is true
Project name: android_device_qcom_sepolicy
sepolicy: Label vendor.camera.hal1.packagelist
Project name: android_device_lineage_sepolicy
Make backuptool permissive only in non user builds
Make sysinit permissive
lineage: Use set_prop() macro for setting adb tcp property
Project name: android_hardware_ril
Encode the Number of MNC Digits in CellIdentity
Project name: android_hardware_qcom_wlan
wcnss-service: Opt-in to disable copying WCNSS_qcom_cfg.ini to userdata
Project name: android_hardware_qcom_media
Revert "media: Avoid collision with FFMPEG plugin"
Project name: android_hardware_qcom_display
Make memtrack build with the VNDK.
Add missing includes.
libmemtrack: Add open method for apq8084.memtrack
display: Use generated kernel headers
hal: Added LOCAL_VENDOR_MODULE to set output path of the binaries
Use header lib instead of using global include path
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP10_OP5.zip
MD5: d44bee63f45eecdc0db9c8186e20d9eb
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.3_oneplus5.zip
Please dont mirror for now the roms zips, thanks
Build 09/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 12.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 12.0
Project name: proprietary_vendor_oneplus
msm8998-common: update blobs from 9.0.4
msm8998-common: add binhaxxed camera libs to fix front cam
Project name: android_kernel_oneplus_msm8998
block: Fix BFQ not being built
Project name: android_device_oneplus_msm8998-common
msm8998-common: update props for wfd
msm8998-common: pin camera blobs (front cam fix)
Project name: android_device_oneplus_cheeseburger
cheeseburger: require 9.0.4 firmware
Project name: android
5 March Security Patch
Project name: android_build_soong
Fix formatting
Project name: android_packages_apps_SetupWizard
SUW: Don't make google suw use material_light
SUW: Update wizard scripts for Pie
Project name: android_packages_apps_Settings
Update the timestamp used for time zone filtering
Project name: android_packages_services_Telephony
Stop generating ids in android namespace.
Fix resource warnings.
Project name: android_frameworks_base
Show mobile icons with left-to-right in order of slot index
Revert "SystemUI: Sort subscriptions in reversed order"
Project name: android_device_qcom_sepolicy
sepolicy: Fix video4linux "name" node labeling
sepolicy: Label persist.nfc.hci_network_reset_req
Project name: android_vendor_lineage
sensitive_pn: New United Kingdom helplines
Project name: android_hardware_qcom_display
display-hals: Expose c2d2.h even if TARGET_DISABLE_DISPLAY is set
Project name: android_system_extras_su
su: Add back mistakenly removed code
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP12_OP5.zip
MD5: 4593674d66a2040a50b11cbd6927f33d
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
danieldmm said:
Build 09/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 12.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 12.0
Project name: proprietary_vendor_oneplus
msm8998-common: update blobs from 9.0.4
msm8998-common: add binhaxxed camera libs to fix front cam
Project name: android_kernel_oneplus_msm8998
block: Fix BFQ not being built
Project name: android_device_oneplus_msm8998-common
msm8998-common: update props for wfd
msm8998-common: pin camera blobs (front cam fix)
Project name: android_device_oneplus_cheeseburger
cheeseburger: require 9.0.4 firmware
Project name: android
5 March Security Patch
Project name: android_build_soong
Fix formatting
Project name: android_packages_apps_SetupWizard
SUW: Don't make google suw use material_light
SUW: Update wizard scripts for Pie
Project name: android_packages_apps_Settings
Update the timestamp used for time zone filtering
Project name: android_packages_services_Telephony
Stop generating ids in android namespace.
Fix resource warnings.
Project name: android_frameworks_base
Show mobile icons with left-to-right in order of slot index
Revert "SystemUI: Sort subscriptions in reversed order"
Project name: android_device_qcom_sepolicy
sepolicy: Fix video4linux "name" node labeling
sepolicy: Label persist.nfc.hci_network_reset_req
Project name: android_vendor_lineage
sensitive_pn: New United Kingdom helplines
Project name: android_hardware_qcom_display
display-hals: Expose c2d2.h even if TARGET_DISABLE_DISPLAY is set
Project name: android_system_extras_su
su: Add back mistakenly removed code
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP12_OP5.zip
MD5: 4593674d66a2040a50b11cbd6927f33d
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
Click to expand...
Click to collapse
Does rom force encryption after flash?
Build 24/03/2019 #OP5
TugaPower ROM G+
Telegram Group: https://t.me/TugaPowerOP5
#TugaPower PIE 9.0.0_r34 13.0 LineageOS #laos #OnePlus
If you have some spare bucks consider donating, it will be really appreciated: https://www.paypal.me/TugaPower
If you are on other base rom, best practice is to factory reset prior to flash rom and new gapps.
After this steps if rom does not boot, probably you are encrypted, remove encryption and repeat the steps.
If after removing encryption rom still does not boot, make a factory reset again after flashing rom and gapps, then all will be fine.
Also be sure you are using proper firmware.
Relative to gapps, the advised ones is nano package for PIE ( ARM64 ):
Replaced built in OTA by OTA Updates app ( https://github.com/MatthewBooth/OTAUpdates )
OTA updates supported
Browser removed and replaced by latest TugaBrowser ( built in OTA for the Browser ) ( blocks ads and protect privacy)
TugaBrowser -> http://forum.xda-developers.com/android/apps-games/app-tugabrowser-t3472457
Support out of the box to microG GmsCore ( http://forum.xda-developers.com/android/apps-games/app-microg-gmscore-floss-play-services-t3217616 )
No more need to make microG system app
PoGO: Gonna catch then all
Powered by Magisk root stable version
Three fingers screenshot
SafetyNet changes to pass
WireGuard Support
Expanded volume rocker ( thanks to @agentfabulous )
Direct unlock with face unlock enabled, lock screen options
What does not works:
Let me know to add to secod post
Changelog: TugaPower P 13.0
Added expanded volume rocker (thanks to AgentFabulous)
Added option to disable the direct unlock with face unlock enabled
Project name: proprietary_vendor_oneplus
msm8998: add missing blobs
Project name: android_kernel_oneplus_msm8998
tri-state-key: send proper input when updating keycodes from userspace
Revert "tri_state_key: import driver from msm8996"
tri_state_key: import driver from msm8996
Project name: android_device_oneplus_msm8998-common
msm8998-common: set project_name prop via init
msm8998-common: Add missing blobs
msm8998-common: add missing libmm-omxcore
msm8998-common: set perms on tri-state-key nodes
Project name: android_frameworks_base
Prevent NFE in SystemUI when parsing invalid int
Prevent NFE in SystemUI when parsing invalid int (2)
Prevent NFE in SystemUI when parsing invalid int
SystemUI: Fix FORCE_SHOW_NAVBAR handling on user switch
Clean up screenshot if nothing selected
IMMS should preserve selected IME upon boot
Add bluetooth icon.
Project name: android_frameworks_av
Request to reset effect buffer in clearInputBuffer
Revert "effects: fix volume burst on pause/resume with AudioFX"
Project name: android_frameworks_native
Respect source crop when capturing layers.
libgui: add docs to geometry states and captureScreen
surfaceflinger: fix captureScreen for landscape LCM
surfaceflinger: improve RenderArea needsFiltering
surfaceflinger: respect install orientation in DisplayRenderArea
surfaceflinger: add install orientation to DisplayDevice
surfaceflinger: make mPrimaryDisplayOrientation static
surfaceflinger: clean up captureScreen
surfaceflinger: silence some RenderArea errors
surfaceflinger: fix race conditions in captureScreen
surfaceflinger: remove ISurfaceComposer.h from RenderArea
surfaceflinger: reorder width and height in RenderArea ctor
surfaceflinger: documents RenderArea
Revert "Revert screenshot changes to exclude black cutout"
Revert "APP may display abnormally in landscape LCM"
Project name: android_vendor_lineage
Add APN ION Mobile & APN for Roaming
config: Remove duplicate keyguard.no_require_sim prop
overlay: Move managed profiles overlay to frameworks/base
kernel: Use build-image-kernel-modules instead of copying it
kernel: Use a macro for kernel build targets
kernel: Detect kernel module usage better
kernel: Move kernel module dir cleanup/creation to module install target
kernel: Move full kernel build guard flag below all targets
kernel: Add more threads to kernel build process
Project name: android_packages_apps_Snap
Snap: Fix picture size preference
Project name: android_packages_apps_Trebuchet
Lint fix: Invalid vector path in horizontal_ellipsis
Project name: android_packages_apps_Bluetooth
Update Bluetooth to use adaptive icon.
Project name: android_packages_apps_Nfc
NfcNci: make T3T/Nfc-F HCE optional
Project name: android_hardware_qcom_display
hwc: Handle validateAndSet failures in AD prepare call
Project name: android_hardware_qcom_display
display-hals: Allow building libdisplayconfig
Project name: android_hardware_qcom_audio
msm8960: Add SND_DEVICE_OUT_VOICE_MUSIC_TX
Project name: android_system_core
Fix path for treble default prop
storaged: change log level for health HAL calls
Project name: android_system_vold
increase timeout for waiting on block device
Thanks all for the support.
Download: https://tugapower.net/TP/OP5/PIE/TugaPowerP13_OP5.zip
MD5: 6872d0b9526c59fe125cb253bf5d6d72
Required firmware: https://tugapower.net/TP/OP5/PIE/FirmwarePIE/firmware_9.0.4_OP5.zip
Please dont mirror for now the roms zips, thanks
For those searching along: The ROM is still maintained and currently up to Version P23. Downloads can be found at https://tugapower.net/?dir=TP/OP5/PIE
Currently you'll need to install firmware 9.0.6 which isn't hosted over there (yet?) but can be found in the OP5 OOS thread at https://forum.xda-developers.com/showpost.php?p=76943628&postcount=8
I'm receiving error 255 for flashing the 9.0.6 firmware as well as the ROM. Is this because I haven't formatted? I'm on the Android 7 version of TugaPower.
Where are the ROM sources mate? Would you kindly provide, or is it closed?
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.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Remarks:
This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
Once everything is mature, an official build may be possible.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Also make sure you've got the correct firmware installed before installing LineageOS.
More detailed instructions at:
Install LineageOS on crackling
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...
Donate to support development:
Donate via PayPal to LineageOS
Changelog
06.12.2021
updated lineage sources
11.09.2021
fixed livedisplay
updated lineage sources
22.07.2021
initial version
reserved
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
petexd said:
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
Click to expand...
Click to collapse
Livedisplay is not working at the moment.
I had to remove it because it wouldn't load my photos and I didn't have time to play around with it. It's actually my only phone. It did, however, instal basic flamegapps.
I also got error 255 when tryin to restore my backup but I'm up and running now with 17.1. I'll try 18.1 again soon when I have more time to mess around with it and if I can sort out error 255
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
ajjin0 said:
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
Click to expand...
Click to collapse
I've got so less time at the moment. I hope I'll find some to continue the work.
New build is up. Livedisplay is working now.
Download
Wow great work.
@115ek Thank you for the new build.
I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
Spoiler
Code:
01-01 21:28:58.399 4357 4357 I [email protected]: LiveDisplay HAL service is starting.
01-01 21:28:58.404 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.510 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.512 220 220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
01-01 21:28:58.512 4357 4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
01-01 21:28:58.513 4357 4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
01-01 21:28:58.514 4357 4357 E [email protected]: LiveDisplay HAL service is shutting down.
01-01 21:28:58.521 0 0 I init : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
01-01 21:28:58.521 0 0 I init : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
01-01 21:28:58.521 0 0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
01-01 21:28:59.391 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:28:59.391 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
01-01 21:28:59.393 219 4360 W libc : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
01-01 21:28:59.395 0 0 E init : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
01-01 21:29:00.392 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:29:00.392 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
My local manifest looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
<project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
<project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
<project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
</manifest>
Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.
mmustermann717 said:
Does your manifest look the same?
Click to expand...
Click to collapse
This should be fine, yes.
mmustermann717 said:
Are there any additional patches I have to apply to get it working?
Click to expand...
Click to collapse
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
Thank you very much! That worked.
I increased the system partition, a little while ago and backups were restoring OK so I've decided to try 18.1 again.
I must say, it performs really well for the stuff I need. I also like that I can now do calendar etc backups to my sdcard. Much more sensible IMO.
Thanks 115ek. A great job.
I'd like to have a go at building but I'm not sure where to start without the explicit menu like 17.1
Thanks to 115ek for the 18.1 set up and to mmustermann717 for his local manifest. I have managed to build 18.1 after a few errors which appeared to be out of memory problems.
I fixed that and was able to complete the build.
Thanks both of you
I was too quick to brag. Im getting a boot loop. I made the changes from 115ek's response #12, so I don't know where I've gone wrong.
Can either of you tell me please?
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
I've tried all of this several times. I get a successful build but a boot loop every time.
The lineage source says successful, it doesn't actually boot so I have no idea how to find any error? Is there anything I can look for? Or can you guess?
I'd appreciate the help if you can. Thanks.
Hey
petexd said:
how to find any error?
Click to expand...
Click to collapse
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
petexd said:
Or can you guess?
Click to expand...
Click to collapse
You could, but I'm not sure if that really helps.
petexd said:
Is there anything I can look for?
Click to expand...
Click to collapse
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
This is the line you asked about:
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.selinux=permissive
I've tried my build with your boot.img but it still bootloops.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I've tried again and the last 4 lines of the build are:
2021-10-18 16:11:33 - ota_from_target_files.py - INFO : done.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Compressing system.new.dat with brotli
warning radio-update: no radio image in input target_files; not flashing radio
[100% 24/24] build bacon
Package Complete: out/target/product/crackling/lineage-18.1-20211018-UNOFFICIAL-crackling.zip
#### build completed successfully
Is this OK? I thought bacon was another phone (oneplus?)
Hey
115ek said:
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I get this , just bfore the build completes successfully. Do you know if this has anything to do with the problem.
99% 463/464] Package OTA: out/target/product/crackling/lineage_crackling-ota-eng.pet
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/build.prop