Related
CyanogenMod 11 for the LG G2 mini D620r
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.
*/
All Credits so far go to Quarx and his project CM11 for LG L90
What i have done so far:
Setup Ubuntu on my Laptop
Installed CM dev environment like described here!
Made a new device folder following THIS guide and build some recoveries.
Took the sources from CM11 for LG L90 and integrated them to my build environment.
CM11 for LG L90 builds fine but i can not test it.
Took the files i thought we need from L90 and put them to my d620 tree.
Trial and error till it compiled for d620.
For the kernel i use original LG sources extracted to kernel/lge/msm8226.
Switched to kernel source from Quarx and tweaked it for d620.
Find sources i use here.
Unfortunately the kernel i have build leads to boot loops. (Yes i have wiped everything)
If i only install the system with the original LG stock kernel i get an security error.
How can i find out why the kernel boot loops?
(had to use the dt.img from stock kernel because mine didn't work, phone gets stuck in fastboot)
Kernel now boots with recovery.
Touch only works if i copy the FW to system folder.
CM11 now works quit well.
Known issues:
- NFC not working at all
- Vibration not working at all
- Back/Main camara has overexposure on bright scenes
- LTE can only be activated by adding quick setting for LTE
Testers welcome.
Video review from simo14
Alpha: Download
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Any help appreciated.
Port rom!!
Good job! I think You can port rom l90 for g2 mini. Read it: http://forum.xda-developers.com/showthread.php?t=2545618 (my English is bad, sorry!!)
I think we need a "extract-files.sh" to extract device proprietary files with connected and enabled usb debbuging. I do some research but didnt luck. My English is weak and i don't know how to do this script. I know its necesary for boot and compile with success.
Maybe Quarx can help us.
Probably kernel boot loops because you compile with CM source and that its not compatible with stock rom.
Regards.
this is great progress
im trying like hell to make a custom recovery.
take a look at this zaaap
http://forum.xda-developers.com/android/help/building-kernel-error-lg-g2-mini-t2853390
maybe you could help me out a bit?
I'm extracted a system folder from TWRP backup and try to port by paste>copy method. I need a META-INF folder for our phone. I don't know how to make it.
Ok i found it.
I make four builds with AndroidKitchen but its always a update-binary script error.
Any help?
make -j4 otatools give me that error.
/media/radek/bee9f4ae-71a6-4ed8-9153-7dd674ea803d/CM11/out/target/product/generic/obj/APPS/SignatureTest_intermediates
"ebtables is disabled on this build"
find: `src': Nie ma takiego pliku ani katalogu
grep: /build/target/board/generic/recovery.fstab: Nie ma takiego pliku ani katalogu
No private recovery resources for TARGET_DEVICE generic
build/core/tasks/kernel.mk:91: **********************************************************
build/core/tasks/kernel.mk:92: * Kernel source found, but no configuration was defined *
build/core/tasks/kernel.mk:93: * Please add the TARGET_KERNEL_CONFIG variable to your *
build/core/tasks/kernel.mk:94: * BoardConfig.mk file *
build/core/tasks/kernel.mk:95: **********************************************************
make: Nie ma nic do zrobienia w `otatools'.
/build/target/board/generic/recovery.fstab exists in the directory.
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
partyzant_x said:
When try to compile kernel:
*** Can't find default configuration "arch/arm/configs/w7ds_open_cis_defconfig"!
***
make[2]: *** [w7ds_open_cis_defconfig] Błąd 1
make[1]: *** [w7ds_open_cis_defconfig] Błąd 2
make: *** [w7ds_open_cis_defconfig] Błąd 2
That's mean the Quarx kernel should work for us?
Click to expand...
Click to collapse
w7ds is an LG L90 dual sim.
Go to your kernel folder /arch/arm/configs and look for a g2m... ...defconfig where the name fits your device.
Try to compile with the g2m defconfig should work.
You might be missing touch and other hardware if you didn't get all property blobs needed for our device.
This is the point where I got struck at the moment.
/tmp/ccfkEagn.s: Assembler messages:
/tmp/ccfkEagn.s:166: Warning: swp{b} use is deprecated for this architecture
/tmp/ccfkEagn.s:192: Warning: swp{b} use is deprecated for this architecture
CC arch/arm/mach-msm/smd_private.o
CC arch/arm/mach-msm/smem.o
CC arch/arm/mach-msm/smd_init_dt.o
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
I'm try to compile the LG source with:
Run following scripts to build kernel
a) cd kernel
c) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
Zaaap can you share your device tree?
Ok. I fixed the errors. Now I have "zImage" how flash that?
What did you do to fix the errors? And wich toolchain did you use?
The zimage comes with some .ko files? You have to make a .zip file of those and flash it through custom recovery or a flash app from market! Like rashr
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
Don't flash the zImage as it is only a part of the needed boot.img.
There is a command like 'make boot.img'. I'll have to look for it.
I'll explain more later when I get to my laptop.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Now I'm trying to create a device tree manually. A bit of getting lost in this. Zaaap can share with your device tree. Rather than create new ones we can work on one and make any fixes.
partyzant_x said:
I fixed the errors that occurred when compiling. Compile the source cm and lg according to instructions in the readme.txt from lg. Thanks Zaaap changed command from w7ds_open_cis_defconfig on g2m_global_com_defconfig. After compiling I received two files zImage and Image.
Click to expand...
Click to collapse
where did you find the readme.txt where it said wich toolchain you should use?
invaderjohn said:
look at the last stages of this how to.
http://playfuldroidz.com/wiki/Compiling_a_Kernel#Making_a_Flashable_Zip
Click to expand...
Click to collapse
Give me: Error executing updater binary in zip.
Downloaded kernel source from lg site. Unpack it and there is two files readme.txt and packed kernel source, unpacked it copy kernel folder to cm source then cd kernel and:
make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi- g2m_global_com_defconfig zImage
When I have error for example:
arch/arm/mach-msm/smd_init_dt.c:24:25: fatal error: smd_private.h: No such file or directory
compilation terminated.
make[2]: *** [arch/arm/mach-msm/smd_init_dt.o] Błąd 1
make[1]: *** [arch/arm/mach-msm] Błąd 2
make: *** [zImage] Błąd 2
Click to expand...
Click to collapse
Then open smd_init_dt.c find line with smd_private.sh. Its look include <smd_private.sh> and change it to include "smd_private.sh".
Sorry for my English.
Make boot.img
Here you can find the official doc about making boot.img: HERE
I took the device tree from Quarx found here made a copy in a new folder 'd620' but i think 'g2m' would have been correct for phone.
Find my device folder here.
Find my vendor folder here.
The kernel source is located under kernel/lge/msm8226
I normaly compile a recovery and see if the kernel works with it.
Thus i don't risk a semi brick because if the kernel is bad, then recovery may not start but system will start and i can flash an other recovery with a new kernel.
If recovery boots, i can use adb to get dmesg.log and see what works and what not.
On my last try, touch didn't initialize complete.
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
partyzant_x said:
Thanks Zaaap.
I broke something in the source of CM. I have to download again. Can someone check zImage which I compiled.
Click to expand...
Click to collapse
It boot, but takes long to do so and there is no touch.
This is the same problem i have.
We need to get the correct touch firmware + patch.
Find log attached.
Kernel boots with touch
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Zaaap72 said:
Got touch working.
The firmware doesn't get copied to /system/lib/firmware.
When i copy the firmware in via AIK kernel boots fast and with touch.
Now i will investigate how to include the FW in compile process.
Click to expand...
Click to collapse
partyzant_x said:
Very good news. I asked for help a member of XDA @ moonbutt74. I hope he will have the time and inclination to help us.
Click to expand...
Click to collapse
okay so root is good
look in /proc for
/proc/config.gz
it might be there it might not. i need the stock boot.img please. looking through source right now and unsure of which defconfig.
your modules also depend on libraries in system/vendor - you need that entire directory for your device tree. you may also need
manufacturer/device specific/proprietary libraries from system/lib
starting in /system/vendor type in terminal
strings [nameoflib].so | grep "\.so"
these will bring up a list of additional libraires needed. the ones you already have in vendor don't worry about. the ones you
will find in system/lib are the additional ones you need to get for your device tree. go to the thread i'm working in with restl3ss and read through the whole thing but please do not post any questions there. post here use the mention function @moonbutt74
or pm me or click reply button below any of my posts in this thread and i will know by email.
m
on defconfig readme suggests w7ds_open_cis_defconfig but will try g2m_global_com_defconfig
can anyone help me out with this issue! I'm trying to port ubuntu touch for my device(Samsung Galaxy J5). But everytime when am trying to sync the sources using phablet-dev-bootstrap or repo init it throws out an error saying error 503 service unavailable. And what's the current stable branch for building ubuntu touch!!
ERROR:
[email protected]:/home/techkid# phablet-dev-bootstrap -r /home/techkid/cm13/ utouch/
INFO: phablet-dev-bootstrap:Changing to workdir /home/techkid/utouch
INFO: phablet-dev-bootstrap:Initializing repository
Get https://gerrit.googlesource.com/git-repo/clone.bundle
Get https://gerrit.googlesource.com/git-repo
Get https://code-review.phablet.ubuntu.com/p/aosp/platform/manifest.git
error: RPC failed; HTTP 503 curl 22 The requested URL returned error: 503 Service Unavailable
fatal: The remote end hung up unexpectedly
EDIT: Close this thread!! Have contacted canonical system admins about the issue,servers were down at that moment and now they have restarted the servers so everything's up and running fine.
ganesh varma said:
[...]
EDIT: Close this thread!! Have contacted canonical system admins about the issue,servers were down at that moment and now they have restarted the servers so everything's up and running fine.
Click to expand...
Click to collapse
How did you contact them? Because I want to try to port ubuntu touch to my phone, but have the same error downloading sources.
Thanks,
Stefano99
Stefano 99 said:
How did you contact them? Because I want to try to port ubuntu touch to my phone, but have the same error downloading sources.
Thanks,
Stefano99
Click to expand...
Click to collapse
You can contact the system administrators at channel #canonical-sysadmin in freenode IRC or upvote my bug and comment over here so that canonical will take any action immediately.
ganesh varma said:
You can contact the system administrators at channel #canonical-sysadmin in freenode IRC or upvote my bug and comment over here so that canonical will take any action immediately.
Click to expand...
Click to collapse
Submitted to your thread. Hope they solve this bug fast:fingers-crossed:
PS: now it works, thank you again!
Thank you,
Stefano99
I am writing this tutorial together in an attempt to help beginners which are trying to build a ROM from source for the first time.I faced many problems when I started building roms, so I thought it will be better to help someone who is trying the same thing.I have tried to make this guide easy to understand.Please feel free to PM if you have any doubts!!
And if you built a rom by following this guide then please press the thanks button, it will motivate me.
For Whom This Guide Is For
1. Who do not have a PC which meets required requiements for building a rom
2. Who cannot download the sources which might be upto 10GB
3. Who is building a rom for the first time
Prerequisites
1. Android Phone
2. A decent internet connection
3. A debit/credit card
4. Brain
Contents
1. Making a Google Cloud Account
2. Setting up the VM (Virtual Machine) on your phone
3. Setting up the build environment
4. Initializing and syncing the repo
5. Cloning the device,kernel and vendor tree
6. Building the rom
7. Uploading the ROM in Google Drive
1. Making A Google Cloud Account
NOTE:You will need a credit/debit card for making an account and it is free to use Google Cloud for one year only.
STEP 1:Open Google Cloud from here.
STEP 2:Click on Free Trial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
STEP 3:Login with your Google account username and password.
2. Setting up the VM (Virtual Machine) on your phone
STEP 1:Download Juice SSH app from here.
STEP 2:Open Juice SSH app and click on "Connections".
STEP 3:Navigate to "Identities" and create a new identity by pressing the "+" button.
STEP 4:Input the "Nickname","Username" (You can enter your name also in both places) and then click on "Private Key"(Set (Optional) button). Navigate to "Generate" and press OK and click on the tick icon.
STEP 5:Now long press the identity you just created and click on "Export Public Key" and click on ES Note Editor or Keep (You need any one of them) and replace the "JuiceSSH" written at the end with your username you entered in the identity and now copy the whole text.
STEP 6:Open Google Cloud and navigate to Computer Engine->Metadata->SSH Keys. Click on edit and then add item.Paste the text you just copied and save it.
STEP 7:Navigate to Computer Engine->VM Instances. Click on "Create Instance".Enter the name(Any name).Select Machine Type as "4vCPU". Select Boot Disk as "Ubuntu 16.04 LTS" and set the size to 1000GB.Tick both "Allow HTTP traffic" and
"Allow HTTPS traffic" and click on create.
STEP 8:Now it will take a minute.After it is created copy the External IP.
STEP 9:Now open Juice SSH app and navigate to "Connections" and create a connection by clicking on the "+" icon.Input the nickcname you entered while creating the identity.Paste the External IP in the "Address" column and click on the tick icon.
STEP 10:Now click on the connection you just created. This will open the terminal on which you need to work.
3. Setting up the build environment
NOTE:You just need to copy and paste the below codes one by one.
1. sudo apt update
2. sudo apt upgrade
3. sudo apt-get install git-core
4. git clone https://github.com/akhilnarang/scripts
5. cd scripts
6. bash setup/ubuntu1604linuxmint18.sh
7. mkdir -p ~/bin
8. mkdir -p ~/android/lineage (Replace lineage with your rom name or you can also use lineage for any rom for easy to understand))
9. curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
10. chmod a+x ~/bin/repo
11. cd ~/android/lineage
4. Initializing and syncing the repo
1. repo init -u https://github.com/LineageOS/android.git -b cm-14.1
NOTE:Here I am compiling lineage os 14.1 therefore I am using it's repo initializing command.
You can find repo initialization command for your rom by the following method:
(i) Google search "rom_name github" (Replace rom_name with your rom name)
(ii) Open the rom github in dextop mode.(Use Google Chrome)
(iii)Click on the "manifest" or "android_manifest"
(iv) Select the branch which you want to build and copy the repo initialization command given at bottom.
Some repo initialization commands:
(i). repo init -u https://github.com/ResurrectionRemix/platform_manifest.git -b nougat
(ii). repo init -u https://github.com/AICP/platform_manifest.git -b n7.1
(iii). repo init -u git://github.com/CandyRoms/candy.git -b c7.1.2
(iv). repo init -u https://github.com/BlissRoms/platform_manifest.git -b n7.1
2. repo sync -j8
Go get a coffee till the source is syncinc. It will take time depending on your internet speed.
5. Cloning the device,kernel and vendor tree
1. git clone device_tree_link_here -b branch_name_here device/manufacturer_name_here/device_name_here
Eg: git clone https://github.com/LineageOS/android_device_xiaomi_mido.git -b cm-14.1 device/xiaomi/mido
2. git clone kernel_tree_link_here -b branch_name_here kernel/manufacturer_name_here/chipset_name_here
Eg: git clone https://github.com/LineageOS/android_kernel_xiaomi_msm8953.git -b cm-14.1 kernel/xiaomi/msm8953
3. git clone vendor_tree_link_here vendor/manufacturer_name_here
Eg: git clone https://github.com/TheMuppets/proprietary_vendor_xiaomi.git vendor/xiaomi
NOTE:1.To find device tree link follow the following steps:
(i)Google search "Device_name device tree github"
(ii)Select the branch and copy the device tree link.
2.To find the kernel tree link follow the below steps:
(i)Google search "lineage os github".
(ii)Input your chipset name in the search box and select the repository for your device.
(iii)Copy the link.
3.To find the vendor tree link follow the below steps:
(i)Google search "The Muppets Github".
(ii)Find the repository for your device and copy the link.
If you can't find any tree with the above methods, then simply google search that tree for your device!!!!
6. Building the rom
1. export USE_CCACHE=1
2. prebuilts/misc/linux-x86/ccache/ccache -M 50G
3. export CCACHE_COMPRESS=1
4. . build/envsetup.sh
5. brunch device_name_here
or
5. make bacon -j8
Now it will take approx 7-8 hrs or more depending upon your internet speed.Go get a sleep till then.
7. Uploading the ROM in Google Drive
1. cd ~
2. wget https://docs.google.com/uc?id=0B3X9GlR6EmbnWksyTEtCM0VfaFE&export=download
3. mv uc\?id\=0B3X9GlR6EmbnWksyTEtCM0VfaFE gdrive
4. chmod +x gdrive
5. sudo install gdrive /usr/local/bin/gdrive
6. gdrive list
7. cd out/target/product
8. ls
Check your ROM name.
9. gdrive upload same_rom_name_here
Now it will show a link. Click on it and copy the code and paste it in the terminal.
Now your rom will start uploading in your Google Drive.
Congratulations You Built Your First ROM!!
Don't forget to press the thanks button
Donate MeIf I helped you a little bit then buy me coffee
Here
Or
CreditsSaurabhCR7(Me:fingers-crossed
@nitin.chobhe (For his images and guide for google cloud)
Akhil Narang(For his Scripts)
Google
XDA
Give credit in OP to @nitin.chobhe for the first part of your guide.
P.S: Thanks for the efforts in making this guide.
@Saurabhcr7 by any chance did you refer this thread (and screenshots there in) of mine?
Thanks @antariksh :good:
Nitin
I want to try
nitin.chobhe said:
@Saurabhcr7 by any chance did you refer this thread (and screenshots there in) of mine?
Thanks @antariksh :good:
Nitin
Click to expand...
Click to collapse
Why i get this? I dont set any password
Diki Saputra said:
Why i get this? I dont set any password
Click to expand...
Click to collapse
You are performing this step wrongly.
STEP 5:Now long press the identity you just created and click on "Export Public Key" and click on ES Note Editor or Keep (You need any one of them) and replace the "JuiceSSH" written at the end with your username you entered in the identity and now copy the whole text.
Saurabhcr7 said:
You are performing this step wrongly.
STEP 5:Now long press the identity you just created and click on "Export Public Key" and click on ES Note Editor or Keep (You need any one of them) and replace the "JuiceSSH" written at the end with your username you entered in the identity and now copy the whole text.
Click to expand...
Click to collapse
Ok,i try make du 8.1.0,i cant see source at du github
Diki Saputra said:
Ok,i try make du 8.1.0,i cant see source at du github
Click to expand...
Click to collapse
https://github.com/DirtyUnicorns/android_manifest
Saurabhcr7 said:
https://github.com/DirtyUnicorns/android_manifest
Click to expand...
Click to collapse
I want to try git clone https://github.com/LineageOS/android_device_xiaomi_kenzo.git -b cm-14.1 device/xiaomi/kenzo
But have problem
@Saurabhcr7 bro,when compiling the rom does it consumes data?
Huge amount or small
dean [email protected]# said:
@Saurabhcr7 bro,when compiling the rom does it consumes data?
Huge amount or small
Click to expand...
Click to collapse
It requires a small amount of data
Diki Saputra said:
I want to try git clone https://github.com/LineageOS/android_device_xiaomi_kenzo.git -b cm-14.1 device/xiaomi/kenzo
But have problem
Click to expand...
Click to collapse
You missed writing cm-14.1 after -b
Saurabhcr7 said:
It requires a small amount of data
Click to expand...
Click to collapse
Thanks bro.
Any help For this, I tried changing that "bacon" with "santoni" (device name which i am compiling'buildbot' for)
Saurabhcr7 said:
You missed writing cm-14.1 after -b
Click to expand...
Click to collapse
Always get this error.
Hey bro, in other forums it is given that it consumes a lot of data to download repo files(or something like that). By doing this in cloud won't it take data to do that??? If it doesn't make sense then sorry... I am a real noob
alnasnasu said:
Hey bro, in other forums it is given that it consumes a lot of data to download repo files(or something like that). By doing this in cloud won't it take data to do that??? If it doesn't make sense then sorry... I am a real noob
Click to expand...
Click to collapse
Actually it downloads repo and all data virtually that's why it doesn't take much data
So downloading directly to cloud means that google is downloading the data to cloud by our command and without our intervention
while downloading repo, if i turn off the internet connection it will still dowload in the cloud, Right???
What if I've to edit my device tree? How can i edit it if files are virtual
What if I've to edit my device tree? How can i edit it if files are virtual??
If you're in a hurry and just want to know the latest news, follow this link:
https://forum.xda-developers.com/showpost.php?p=80393641&postcount=58
Keep reading for some background info.
Hi there!
So... I'm trying to port LineageOS (version 15.1) from OnePlus - OnePlus2 device to the LeEco LeMax 1 phone.
Why I've chosen this device to port from?
It has the MSM8994 (Qualcomm Snapdragon 810) SoC, which is the same as Max1, so (supposedly) a kernel compile would not be too much hassle. Besides it also has many similarities in terms of hardware.
What I did for device dir:
I took the tree from https://github.com/LineageOS/android_device_oneplus_oneplus2 and modified it to meet max1 requirements.
Current tree: https://github.com/alexsmithbr/android_device_letv_max1
What I did for vendor dir:
I compared the tree with Max1 tree, excluding everything that was not found in Max1. The plan is to add more vendor stuff if necessary.
Current tree: https://github.com/alexsmithbr/android_device_letv_max1
What I did for kernel dir:
I downloaded Le_Max_OpenSource.zip from opensource.le.com (in fact, as the site is down, I got a copy from http://web.archive.org/web/20180626053054/http://opensource.le.com:80/ and, from there, I found the file I needed was named Le_Max_OpenSource.zip. I got it from here.
The kernel config in this zip file is exactly the same I get from the device itself, with adb pull /proc/config.gz.
Current tree: https://github.com/alexsmithbr/android_kernel_letv_max1
Interesting related threads:
https://forum.xda-developers.com/showpost.php?p=78690008&postcount=7
https://forum.xda-developers.com/le.../cm-14-1-android-7-1-unofficial-letv-t3530173
Other possibly useful resources:
http://web.archive.org/web/20180626053054/http://opensource.le.com:80/
https://forum.xda-developers.com/showpost.php?p=78676206&postcount=2402
These are thanks to @rico69310, specifically this post:
https://www.mediafire.com/folder/ff7hbpa62ivsg/
https://yadi.sk/d/RPfdh3glmhzarw
https://cloud.mail.ru/public/GP9g/cWpyeYbuK/
Another useful resource, in case you brick your X900. This is thanks to @Phsh:
https://forum.xda-developers.com/showpost.php?p=75157516&postcount=2375
Current status
I can build LineageOS 15.1 completely, but, once flashed, the kernel doesn't boot and phone enters bootloader (the penguin screen) and stay there.
What I need
It's pretty obvious I need the ROM working...
But the focus now would be to have a working boot.img. I really don't know what I'm doing wrong.
I can't get any logs, as LeEco patched the kernel so that we don't have a last_kmsg. Instead, they apparently put last_kmsg into another partition in /dev/block/platform/soc.0/f9824900.sdhci/by-name/letvconfig2. You can check this in the kernel, file kernel/printk/last_kmsg.c, line 124:
Code:
#define DEFAULT_KERNELLOG_FILENAME "/dev/block/bootdevice/by-name/letvconfig2"
char *kernlog_file = DEFAULT_KERNELLOG_FILENAME;
Well, I tried to give an overview of all steps I took. Please feel free to ask anything or give hints.
Together we can make LeEco LeMax 1 live longer!
Thought it would be nice to describe my build process.
Basically I'm following these instructions: https://wiki.lineageos.org/devices/oneplus2/build
Of course these instructions are for oneplus2, but the step-by-step is pretty much the same for any device.
I'm using Ubuntu 18.04.1 LTS, in which I created a user specifically for building LineageOS.
I followed all steps on the above link until breakfast oneplus2, since, at this point, I had to create my own device/vendor/kernel tree, so that I can breakfast it.
To do this, I did:
Code:
# clone max1 device
cd ~/android/lineage/device
mkdir letv
cd letv
git clone https://github.com/alexsmithbr/android_device_letv_max1.git max1
# clone max1 vendor
cd ~/android/lineage/vendor
mkdir letv
cd letv
git clone https://github.com/alexsmithbr/android_vendor_letv_max1.git max1
# setup kernel
cd ~/android/lineage/kernel
mkdir letv
cd letv
# change <path_to_file> to the correct path to Le_Max_OpenSource.zip
# you downloaded from the link on the previous post.
unzip <path_to_file>/Le_Max_OpenSource.zip -d max1
# as the zip has unnecessary subfolders, I just moved them
# to their correct names and deleted other rubbish.
mv max1/LeMax_kernel/kernel/ max1/msm8994
rm max1/LeMax_kernel/ -R
In the end, you need a structure like this:
Code:
~/android/lineage/device/letv/max1
~/android/lineage/vendor/letv/max1
~/android/lineage/kernel/letv/msm8994
Finally, put config.gz in its dir:
Code:
adb pull /proc/config.gz /tmp
gunzip /tmp/config.gz -c > ~/android/lineage/kernel/letv/msm8994/arch/arm64/configs/msm8994-max1-perf_defconfig
Okay, now everything is set up for the build to start.
Code:
source build/envsetup.sh
breakfast max1
export USE_CCACHE=1
ccache -M 50G
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
croot
Just before start building, I choose which kind of build I want:
Code:
choosecombo
Build type choices are:
1. release
2. debug
Which would you like? [1] 1
Which product would you like? [lineage_max1]
Variant choices are:
1. user
2. userdebug
3. eng
Which would you like? [eng]
Now, if you want a normal build, you can enter:
Code:
brunch max1
But, if you want a really verbose log (very useful to debug build errors), you can enter:
Code:
mka -j 4 showcommands
Note that -j 4 means 4 simultaneous jobs. You can specify another number. A rule of thumb is to use <number_of_cpus> * 2.
Now the system should build...
At this point:
https://github.com/alexsmithbr/andr...tree/0f9134dd09c269b2da9008c5598060b9d19ac2ef
https://github.com/alexsmithbr/andr...tree/9ece561a945867ab2af733c5ef890b6df5438a8b
The system builds and mka -j 4 showcommands bacon will build flashable lineage-15.1-20190128-UNOFFICIAL-max1.zip.
Unfortunately, when flashing this zip, and restarting the phone, it will vibrate twice when showing the LeEco first screen, then it vibrates twice again and shows me the penguin screen (bootloader).
No luck up to now.
Keep up with the good work... I hope you get the kernel working.
Spunkination said:
Keep up with the good work... I hope you get the kernel working.
Click to expand...
Click to collapse
Me too!
It's so hard to get any help... I've been to freenode as well and nobody wanted to help there. :/
So it feels like a very lonely path. But I'm still on to it.
Currently I'm recompiling everything, now getting "my" tree a bit closer to @ABM30 tree, adapted to LineageOS, instead of CyanogenMod.
Let's see what happens next.
No luck. Boots to penguin (bootloader) screen again.
---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------
I'm cheering for you. I would very much like 8.1 Good luck ! Good work!
htimsxela said:
Me too!
It's so hard to get any help... I've been to freenode as well and nobody wanted to help there. :/
So it feels like a very lonely path. But I'm still on to it.
Currently I'm recompiling everything, now getting "my" tree a bit closer to @ABM30 tree, adapted to LineageOS, instead of CyanogenMod.
Let's see what happens next.
No luck. Boots to penguin (bootloader) screen again.
Click to expand...
Click to collapse
Hope you are good friend?
How is the build going?
I updated the git repositories. The current version compiles as well and I get a ROM at the end, but unfortunately it doesn't boot. I'm probably missing something in the kernel build. I'm still investigating, but I don't even get to the LineageOS logo. When I turn on the phone, it goes straight to bootloader (penguin) screen.
I'll keep trying. Since a build involves a lot (really!) of variables, there's always something new to try.
And it's good that we keep this thread active. Maybe someone with more knowledge shows up and is able to help.
My biggest issue is I can't find a way of seeing what's wrong, since LeEco patched the kernel in a way there is no /proc/last_kmsg file, nor /sys/fs/pstore/console-ramoops. LeEco implemented it in a way the logs would be written to a partition called letvconfig2, but even there I cannot see any logs.
I read another way of seeing kernel logs would be to use the phone's serial port, but then I'd have to reach its main board, which is not an option currently, since this is my only phone.
In other words, my options now resume to keep trying.
Tomorrow I expect to have some time to resume the work. Will give it some more tries. I'm even thinking about checking out a previous version of LineageOS (when it was still called CyanogenMod), then, once I get it working, try to make my way to newer versions.
Stay tuned!
And again: any hints are more than welcome!
I really believe this thread may become kind of a roadmap to compile android for any unsupported device.
Update: by looking at recovery.img and comparing to the recovery partition on device, I noticed the kernel being built by LineageOS doesn't contain any DTBs. Without DTBs, the kernel won't be able to identify the phone's hardware.
How I checked this:
Code:
$ mkdir /tmp/boot
$ cd /tmp/boot
$ unpackbootimg -i ~/android/lineage/out/target/product/max1/recovery.img -o .
BOARD_KERNEL_CMDLINE console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom user_debug=31 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-5 androidboot.selinux=permissive buildvariant=userdebug
BOARD_KERNEL_BASE 00000000
BOARD_PAGE_SIZE 4096
$ split-appended-dtb-master/split-appended-dtb recovery.img-zImage
ERROR: Appended Device Tree Blob not found!
I'll try to find out how to automatically add DTBs to the images.
I know there was a variable called TARGET_KERNEL_APPEND_DTB, which should be set to true on older (cyanogenmod) versions, but it is now deprecated. So deprecated that even the "deprecated" messages have been removed by now.
As far as I could figure out, now the action of appending/not appending DTBs to the kernel image is guessed by variable BOARD_KERNEL_IMAGE_NAME. For example:
To add dtb to kernel image, one would do:
Code:
BOARD_KERNEL_IMAGE_NAME := Image-dtb
To don't add dtb to kernel image, one would do:
Code:
BOARD_KERNEL_IMAGE_NAME := Image
I was hoping this would change something, as for me that variable was defined without the -dtb suffix, but I figured out I broke the kernel build:
Code:
make[1]: *** No rule to make target 'Image-dtb'. Stop.
I guess this is because the original kernel is too old (3.10.84) and it's AndroidKernel.mk still relies on TARGET_KERNEL_APPEND_DTB, as we can see on line 68:
Code:
ifeq ($(TARGET_KERNEL_APPEND_DTB), true)
$(info Using appended DTB)
TARGET_PREBUILT_INT_KERNEL := $(TARGET_PREBUILT_INT_KERNEL)-dtb
endif
Patch the kernel? Wow! This is going deep...
* unpackbootimg is part of the android_bootimg_tools. I got it from here: wget https://storage.googleapis.com/goog...d-serialport-api/android_bootimg_tools.tar.gz
* split-appended-dtb is this tool: https://github.com/dianlujitao/split-appended-dtb
Turns out there are two ways of adding DTBs.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By checking my current recovery partition, I noticed DTBs are attached to partition, not to kernel. I also noticed it is not using a compressed kernel. So I'll configure BoardConfig.mk as:
Code:
BOARD_KERNEL_IMAGE_NAME := Image
If I wanted it gzipped, I'd make it Image.gz. If I wanted the DTBs attached to kernel (not to image), I'd do Image.gz-dtb.
Apparently no kernel patch will be needed... Anyway I created a git repository for it, just in case I need to change something.
Again, the build works, but it doesn't boot.
As I'm focusing on testing the kernel, I'm using the recovery partition.
I just dumped a copy of it with:
Code:
host$ adb shell
phone$ su
phone# cp /dev/block/bootdevice/by-name/recovery /sdcard
phone# exit
phone$ exit
host$ adb pull /sdcard/recovery
and I'm flashing it over and over to test.
To do this, I do
Code:
host$ adb reboot bootloader
# phone reboots
host$ fastboot flash recovery /path/to/recovery.img
# it flashes, then, holding volume-up, I type:
host$ fastboot reboot
Phone will reboot into recovery and test my image (up to now, I only get back to penguin screen (bootloader)).
To flash back my working recovery image, I do the same as above, just changing the path to recovery image.
Bless you and your work
Dude, I would definitely-definitely liked to help; I understand and root for your hard work. But unfortunately I don't possess any knowledge in this area. Yeah, I can flash using manual, but I'm lamer in terms of programming, not even close to IT.
htimsxela said:
Hi there!
Click to expand...
Click to collapse
I rarely meet such wonderful and persistent people like you. I sincerely hope you will succeed and achieve your goal! :good:
Santey Maas said:
Dude, I would definitely-definitely liked to help; I understand and root for your hard work. But unfortunately I don't possess any knowledge in this area. Yeah, I can flash using manual, but I'm lamer in terms of programming, not even close to IT.
Click to expand...
Click to collapse
Thanks, mate! I didn't give up yet. Each try brings more knowledge and I hope I'm able to share all I'm learning. Sort of paving the road for newcomers.
Tircon said:
I rarely meet such wonderful and persistent people like you. I sincerely hope you will succeed and achieve your goal! :good:
Click to expand...
Click to collapse
Thanks! My hope is that - if I succeed - more people can benefit from my work and give these phones a longer life.
LeEco Le Max (max1/x900) Secret Codes
A bit off-topic, but here it goes... While looking for a way to debug kernel boot, I came across those famous secret codes you can type on phone screen to access secret/test menus... This site, for example, says you can use code *#*#76937#*#* to have access to a menu where you can enable/disable some log, debug and AT commands options. I tested and it worked with my phone. Not happy enough, I did a
Code:
grep 76937 / -rl
on the phone and found out system/app/LetvDebugUtil/oat/arm64/LetvDebugUtil.odex was the only place where it occurred. Inspecting the file, I found, right next to the occurrence, the code 9439. Just to test, I entered *#*#9439#*#* on the phone and got to a Chinese menu (see attached picture). The translation of these Chinese stuff is "Launch China Telecom Network (CDMA)". I didn't check that box to see what happens.
Current known codes
*#*#76937#*#* - Menu where you can enable/disable some log, debug and AT commands options.
*#*#9439#*#* - Launch China Telecom Network (CDMA)
*#*#8888#*#* - Advanced settings. Here you can turn on logging of App, Modem, Net, Kernel, Bluetooth, GPS and WiFi. Logs are stored in /sdcard
*#0000# - About phone. Information about each card slot.
*#06# - MEID & IMEI numbers.
If you're having this error while trying to build LineageOS:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/android_build/android/lineage/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_l.cpp system/tools/aidl/aidl_language_l.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '/home/android_build/android/lineage'
You're probably having the same issue I'm having with Flex. The easiest option is to recompile it. And it's easy.
Code:
$ cd prebuilts/misc/linux-x86/flex
$ mkdir flex-2.5.39-src
$ cd flex-2.5.39-src
$ tar zxvf ../flex-2.5.39.tar.gz
$ ./configure
$ make
$ cp flex ../flex-2.5.39
$ cd ..
$ rm flex-2.5.39-src -R
The above commands will recompile Flex for your architecture and everything should be fine (with Flex).
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.1.x running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
htimsxela said:
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.0.1 running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
Click to expand...
Click to collapse
Thanks for your effort!
This phone is great and it's pity that it was left without support..
htimsxela said:
Some news regarding the overall progress with LineageOS.
I checked out the repo from cm-14.1 (cyanogenmod 14.1) and am now trying to build for it. If it builds, at least we'll have Android 7.0.1 running on device. And - I believe - it could bring some light to start a port to a newer version (Lineage 15.1).
Up to now, I faced the same compile errors I got when compiling for 15.1, so it's being straight forward. I'm anxious to see if it'll boot. :fingers-crossed:
As usual, I'll keep you posted.
Click to expand...
Click to collapse
BTW if someone is curious out there, here's the CyanogenMod 14.1 branch I'm working on: https://github.com/alexsmithbr/android_device_letv_max1/tree/cm-14.1
It was based on CyanogenMod 12.1 and the code is almost three years old (last commit), so I'm spending some time updating obsolete code, etc.
Donnie2Darko said:
Thanks for your effort!
This phone is great and it's pity that it was left without support..
Click to expand...
Click to collapse
Yeah, let's see if I can help changing this scenario.
I am trying to build a crdroid rom for the SM-T350. But i keep running into errors that im not sure how to fix.
steps i'v taken so far
Synced the CrDroid 9 repo
added a local manifest (this one https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml)
repo synced again
Code:
repo sync -c --no-tags --no-clone-bundle -j2
git cloned this https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/
ran
Code:
export CROSS_COMPILE=/home/lividhen/crdroid/arm-eabi-4.8/bin/arm-eabi- && export ARCH=arm && export SUBARCH=arm
Code:
brunch gt58wifi
Ended with
Code:
(ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it)
tried to build kernel, is that what i need to do?
Code:
(cd kernel/samsung/msm8916
ran
Code:
make menuconfig
then just saved with all the defaults, then ran
Code:
make msm8916_sec_gt58wifi_eur_defconfig)
ended with
Code:
make[2]: *** [scripts/Makefile.build:309: kernel/irq/irqdesc.o] Error 1
make[1]: *** [scripts/Makefile.build:455: kernel/irq] Error 2
make: *** [Makefile:834: kernel] Error 2
I feel as if I'm probably missing something important, I'm just not sure what. any help is appreciated. Do i need to provide more info? i am on WSL, but from what i'v heard, that shouldent make a difference.
Edit: ran make make VARIANT_CONFIG=msm8916_sec_gt58wifi_eur_defconfig again after running make clean and make mrproper in the kernel directory and got make: *** No rule to make target 'include/config/auto.conf', needed by 'include/config/kernel.release'. Stop
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
nubianprince said:
Try this.
Use this https://github.com/Nubianprince/local_manifests/blob/master/crdroid-pie.xml to update your crdroid-pie.xml file.
Delete device/samsung/msm8916-common
repo sync
. build/envsetup.sh && brunch gt58wifi
Click to expand...
Click to collapse
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
lividhen99 said:
It is still throwing "ninja: error: '/home/lividhen/crdroid/out/target/product/gt58wifi/kernel', needed by '/home/lividhen/crdroid/out/target/product/gt58wifi/boot.img', missing and no known rule to make it
15:08:48 ninja failed with: exit status 1"
Click to expand...
Click to collapse
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
nubianprince said:
In BoardConfigCommon.mk in msm8916-common folder what path are you using for TARGET_KERNEL_SOURCE and does it exist?
Click to expand...
Click to collapse
It pointed twards kernel/samsung/msm8916 which no longer exists, so I changed it too kernel/samsung/evervolv, then I had a bunch of problems with the ncurses libs, but eventually got that sorted out, then FINALLY, it built successfully. Thank you.
Aaaaaand, audio not playing and camera is broken. How was this fixed?
lividhen99 said:
Aaaaaand, audio not playing and camera is broken. How was this fixed?
Click to expand...
Click to collapse
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
nubianprince said:
msm8916.mk & boardconfigcommon.mk update your audio config path.. change from TARGET_COPY_OUT_VENDOR to TARGET_COPY_OUT_SYSTEM
make clean && brunch gt58wifi
Click to expand...
Click to collapse
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
lividhen99 said:
All the lines under audio already say TARGET_COPY_OUT_SYSTEM.
(also, quick off topic question, is the crdroid 6 usable yet? I'd guess not sence it hasn't been uploaded yet uploaded.)
Click to expand...
Click to collapse
How is this coming along?
nubianprince said:
How is this coming along?
Click to expand...
Click to collapse
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
lividhen99 said:
Um... not. i'm not sure what else to do as i have never done this before . I guess i'll just keep poking around to see if i can do anything.
Click to expand...
Click to collapse
Maybe there is something missing from my git repos, I will update those this weekend.
nubianprince said:
Maybe there is something missing from my git repos, I will update those this weekend.
Click to expand...
Click to collapse
Okay, thanks.
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
lividhen99 said:
Hey, I tried building with your latest commit, and I am not sure if that was supposed to fix anything,but it is still broken. I keep fiddling with the audio paths and can't seem to fix it ?
Click to expand...
Click to collapse
Did you do a clean build?
nubianprince said:
Did you do a clean build?
Click to expand...
Click to collapse
Yeah ? I'm just going to delete my entire android directory and start fresh.
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
lividhen99 said:
okay, here is what i'm doing, just in case i'v done something terribly wrong. Initalize the crdroid repo, added crdroid-pie.xml to local_manifests, repo sync, then i try to build and it gives a liblights error so i comment out all of hardware/qcom/display-caf/msm8916/liblight/Android.mk and do a clean build.
Edit 1: I forgot to correct the kernel path in BoardConfigCommon.mk so i fixed that.
Edit 2: i am now getting build/make/core/shared_library_internal.mk:17: error: hardware/qcom/display-caf/msm8916/libmemtrack: Illegal use of OVERRIDE_BUILT_MODULE_PATH. which i wasn't getting before, so... potential progress?? i don't know.
Click to expand...
Click to collapse
Sound like you messed something out in display-caf when you commented out liblight
okay, i got it to build again, i deleted display-caf and synced again, then commented the other of the two files defining liblights. now i'm back at the same issue again, neither camera nor audio works ?. all the audio paths in BoardConfigCommon.mk and msm8916.mk say TARGET_COPY_OUT_SYSTEM already, and i'm not sure what to do about the camera.
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
nubianprince said:
upload your device trees so I can take a look, I will upload my vendor trees and you can try building with those
Click to expand...
Click to collapse
device/samsung
https://drive.google.com/open?id=11V3pcrDgMEId13l0bXG7inpyPUVx7FWp