Related
The developer site is still listing KitKat as the newest build, so here are the links to the instructions to build Lollipop using the official source:
Lollipop 5.0: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r1-partner
Lollipop 5.0.1: http://nv-tegra.nvidia.com/gitweb/?...a=blob_plain;f=README;hb=rel-st8-l-r2-partner
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
berryman13 said:
Cheers mate. It is still listing the 1.2.1 OTA as the latest but just by changing the branch url i was able to find the newest.
Lets hope for some more development on this device. I'm going to PM you soon - I will be building my own ROM and/or Kernel.
Click to expand...
Click to collapse
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
twistedumbrella said:
You do realize those are the links posted above. There is no need to switch branch names or search for the current files. Just click the one you want.
Click to expand...
Click to collapse
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
berryman13 said:
Of course, mate!
I was saying that I found the proper page by changing the URL to hb=rel-st8-l-r2-partner, before this thread was posted. So I appreciate you enlightening other folks about it!
Click to expand...
Click to collapse
Even without already having the branch name, it's just a matter of going to http://nv-tegra.nvidia.com/gitweb/?p=manifest/android/binary.git;a=summary to find it
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
diigibio said:
Hi, @twistedumbrella could you please spare a second to help (or point me in the right direction) I've successfully built Lollipop for my Oneplus One using Ubuntu, but when I try to set up first repo sync; well see below:
When I run: repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r2-partner -m tlk/shieldtablet.xml
I get: fatal: manifest 'tlk/shieldtablet.xml' not available
fatal: remote github not defined in /home/diigimatrix/.repo/manifests/tlk/shieldtablet.xml
Please could you get me on my way. I love all your work and hope to gain further knowledge through your support.
Thanks in advance
Phil from Blackpool
Click to expand...
Click to collapse
I'm trying to figure out what's up with it now. I know when I synced it was r1, and tlk/shieldtablet.xml was valid.
Hopefully I can track down why it is coming back invalid in r2.
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
diigibio said:
Thanks @twistedumbrella, glad in a way its not just me. Thought I was running the wrong command. . Happy New Year!
Click to expand...
Click to collapse
Same to you. It updated ok but now I have to see if it'll re-init. It may be a delay on their end. The readme for the portable was up a week before the source.
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
diigibio said:
Cool. I'll give it another try once I've finished work. Been a member for years and helped a lot in the old windows phone days. But thought enough of just relying on other people, time to start getting my hands dirty again. But new to building Android. Need to read up on manipulation of ROMs rather than just building a stock ROM. Any tips on tools to manipulate ROMs? Am i right by merging commits then build, then manipulate ROM? I will read up on it but just thought you might have some pointers. Thanks
Click to expand...
Click to collapse
Best bet is to either find something you like and merge it or try to find something similar and recreate it to start. Once you get comfortable, then start coming up with your own.
Building from source is mostly Java for modifying with some C for drivers and such. Usually when you have a device configuration already set up, though, the C part is already done.
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
diigibio said:
Just wanna say a big thanks to @twistedumbrella. I set up a new ubuntu build environment and I'm now compiling my first Android build for Nvidia Shield Tablet EU-LTE. No mods yet other than stock, but hopefully with time.
Click to expand...
Click to collapse
Glad to hear it's all up and running. Best of luck!
twistedumbrella said:
Glad to hear it's all up and running. Best of luck!
Click to expand...
Click to collapse
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
entelekia said:
Hi! I'm trying to compile but get error trying no find:
./packages/apps/UnifiedEmail/src
After repo sync, I don't have "src" directory for this package.
Thnx in advance.
Click to expand...
Click to collapse
It looks like they are still working out a few issues with new updates. I don't maintain the source, so the only advice I can provide is to keep on eye on nvidia's gitweb for when they publish a solution (or occasionally sync and try over), or attempt to fix it yourself (which usually only works if there is an issue with the code, not code missing altogether).
Compiled! I have resynchronized all the project from scratch from git repository.
I'm going to test the compiled ROM in my tablet, but I suppose, I have to provide almost the essential pack of Google apps (basic providers and play services).
I think to flash *.img files, except recovery.img (I'm on TWRP), and then install from TWRP PA Gapps. Is this approach correct?
Thnx in advance and regards.
EDIT: No luck booting custom rom (TWRP nor stock recovery...)
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
GethPrime said:
Seem's like there's a new source three version out:
repo init -u git://nv-tegra.nvidia.com/manifest/android/binary.git -b rel-st8-l-r3-partner -m tlk/shieldtablet.xml
Click to expand...
Click to collapse
Anyone managed to build this one yet? Its not working for me..
Okay, I'm trying to build Marshmallow preview 2 for the Nexus 7 2012, and I'm unsure of the source tagging on Google git.
I want to download the files using repo init, but obvious branch names aren't working.
I've tried this:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b m-preview-1
But this returns a 404 error.
I think the manifest file is correct, but "m-preview-1" is a tag and not a branch name like last year's "l-preview" branch.
TL;DR
What is the repo init command to download the Nexus 7 2012 Android M preview 2 branch?
P.S
M preview 3 isn't on the git, which is why I'm doing preview 2.
WeShallFall said:
Okay, I'm trying to build Marshmallow preview 2 for the Nexus 7 2012, and I'm unsure of the source tagging on Google git.
I want to download the files using repo init, but obvious branch names aren't working.
I've tried this:
Code:
repo init -u https://android.googlesource.com/platform/manifest -b m-preview-1
But this returns a 404 error.
I think the manifest file is correct, but "m-preview-1" is a tag and not a branch name like last year's "l-preview" branch.
TL;DR
What is the repo init command to download the Nexus 7 2012 Android M preview 2 branch?
P.S
M preview 3 isn't on the git, which is why I'm doing preview 2.
Click to expand...
Click to collapse
Hello and thank you for using XDA Assist.
There is no XDA forum dealing specifically with building M Previews at this time, and I could only find the same external links you probably tried already. Even though it's not really device-specific, you may want to ask your question with all relevant details in the Nexus 7 Forum at http://forum.xda-developers.com/nexus-7 but I also see some related discussion in the Nexus5 area, such as http://forum.xda-developers.com/google-nexus-5/devs-only/android-m-source-t3122123 where the experts familiar with the Marshmallow build process might be able to guide you.
Good Luck!
Mike B. said:
Hello and thank you for using XDA Assist.
There is no XDA forum dealing specifically with building M Previews at this time, and I could only find the same external links you probably tried already. Even though it's not really device-specific, you may want to ask your question with all relevant details in the Nexus 7 Forum at http://forum.xda-developers.com/nexus-7 but I also see some related discussion in the Nexus5 area, such as http://forum.xda-developers.com/google-nexus-5/devs-only/android-m-source-t3122123 where the experts familiar with the Marshmallow build process might be able to guide you.
Good Luck!
Click to expand...
Click to collapse
Thanks, I'll see what I can do.
Hi, I am trying to build CyanogenMod for the Samsung Galaxy Avant (for learning purposes), but it not supported by the ROM. This is my first build ever, so please cut me some slack. I have been following a tutorial to build one for this phone, and was successfully able to get to the "lunch" stage of the build. When I "lunch" the device name, however, I receive an error in Terminal:
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
Device afyonltetmo not found. Attempting to retrieve device repository from CyanogenMod Github (ht tp:// github . c om/ Cyanogen Mod).
Repository for afyonltetmo not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
** Don't have a product spec for: 'afyonltetmo'
** Do you have the right repo manifest?
This prevents me from continuing with the build, so what do I do to fix it? How do I manually add it to my local_manifests? I am doing this on Ubuntu 14.04 64 bit, by the way. Also, I can use the stock kernel to for this build right? The current ROM I am running does not support wifi or using the camera. Sorry for this noobish question, and thanks for all of your help.
shash222 said:
Hi, I am trying to build CyanogenMod for the Samsung Galaxy Avant (for learning purposes), but it not supported by the ROM. This is my first build ever, so please cut me some slack. I have been following a tutorial to build one for this phone, and was successfully able to get to the "lunch" stage of the build. When I "lunch" the device name, however, I receive an error in Terminal:
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
Device afyonltetmo not found. Attempting to retrieve device repository from CyanogenMod Github (ht tp:// github . c om/ Cyanogen Mod).
Repository for afyonltetmo not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:234: *** Can not locate config makefile for product "afyonltetmo". Stop.
** Don't have a product spec for: 'afyonltetmo'
** Do you have the right repo manifest?
This prevents me from continuing with the build, so what do I do to fix it? How do I manually add it to my local_manifests? I am doing this on Ubuntu 14.04 64 bit, by the way. Also, I can use the stock kernel to for this build right? The current ROM I am running does not support wifi or using the camera. Sorry for this noobish question, and thanks for all of your help.
Click to expand...
Click to collapse
Hi,
Thanks for using XDA Assist.
Try posting your query in Android Q&A,Help and Troubleshooting or in the friendly Q&A thread here->[Ask Any Question][Newbie Friendly] .Experts there may be able to help you.
Good luck
Hi there,
I'm trying to make a lineageos ROM for our great Xperia XZ but I face some problems.
I done all the steps of the ultimate ROM making thread on XDA, and i can't see my XZ in the device list of the lunch command.
To be precise i see it as aosp_f8331 and not lineage_f8331 nor lineage_kagura.
I already tried to build aosp on XZ without any success.
Maybe someone can light my candle.
Thanks
fastbooking said:
Hi there,
I'm trying to make a lineageos ROM for our great Xperia XZ but I face some problems.
I done all the steps of the ultimate ROM making thread on XDA, and i can't see my XZ in the device list of the lunch command.
To be precise i see it as aosp_f8331 and not lineage_f8331 nor lineage_kagura.
I already tried to build aosp on XZ without any success.
Maybe someone can light my candle.
Thanks
Click to expand...
Click to collapse
Looks like you haven't changed the "vendorsetup.sh" file
Should look like THIS (But where carbon is, put lineage)
You can also use "lunch lineage_kagura-userdebug"
THANKS,
Maybe this will help me a lot !
I was looking all over internet to find an answer and you gave it.
nzzane said:
Looks like you haven't changed the "vendorsetup.sh" file
Should look like THIS (But where carbon is, put lineage)
You can also use "lunch lineage_kagura-userdebug"
Click to expand...
Click to collapse
hey, now i'm here.
Code:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
Device f8331 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for f8331 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
** Don't have a product spec for: 'lineage_f8331'
** Do you have the right repo manifest?
can you guide me or pm the steps.
I would like to write and post a detailed tutorial for building roms for our phone with all the links to the needed files etc.
Cheers
fastbooking said:
hey, now i'm here.
Code:
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
Device f8331 not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).
Repository for f8331 not found in the LineageOS Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
build/core/product_config.mk:249: *** Can not locate config makefile for product "lineage_f8331". Arrêt.
** Don't have a product spec for: 'lineage_f8331'
** Do you have the right repo manifest?
can you guide me or pm the steps.
I would like to write and post a detailed tutorial for building roms for our phone with all the links to the needed files etc.
Cheers
Click to expand...
Click to collapse
https://github.com/nzzane/device-sony-kagura/blob/cm-14.1/vendorsetup.sh
Like that
Yeah I just understood that way and done that, the error is after the edit
fastbooking said:
Yeah I just understood that way and done that, the error is after the edit
Click to expand...
Click to collapse
@nzzane
fastbooking said:
@nzzane
Click to expand...
Click to collapse
Is your repo clones from the official device repo or made yourself?
nzzane said:
Is your repo clones from the official device repo or made yourself?
Click to expand...
Click to collapse
I cloned the lineageos repo and added Sony's device specific files after and edited local_manifest.xml
fastbooking said:
I cloned the lineageos repo and added Sony's device specific files after and edited local_manifest.xml
Click to expand...
Click to collapse
Can you link me to your repo?
I can have a look for you and see whats up
nzzane said:
Can you link me to your repo?
I can have a look for you and see whats up
Click to expand...
Click to collapse
Hum I'm a bit new, i need to fork everything i used ?
Or maybe i can upload my entire work file (i have fast internet 950mb/s Down and 250mb/s up)
fastbooking said:
Hum I'm a bit new, i need to fork everything i used ?
Or maybe i can upload my entire work file (i have fast internet 950mb/s Down and 250mb/s up)
Click to expand...
Click to collapse
Just upload your device folder: device/sony/kagura
and setup a new repo if you haven't already https://github.com/
and upload your Kagura folder's contents into the new repo
I see, I'll do it after school tomorrow (16 yo french boy), thanks for help tho
fastbooking said:
I see, I'll do it after school tomorrow (16 yo french boy), thanks for help tho
Click to expand...
Click to collapse
All good, XDA is a great place to learn, as long as the devs are friendly ?
If you need help, you can reach out to me
I figured out for the build issue,( thanks to @nzzane)
Now the kernel issue some files are missing so if anyone can help me,
I'll post a full tutorial from scratch and give ALL the needed files for building
?
Hello there!
Many of you want to get a nougat working rom for our Xperia E3. We have kernel sources, vendor files, device... So if you wanna try to make the rom this guide is for you.
Prerequisites
64 bit computer with 64 bit Linux OS installed (or virtual machine)
At least 4gb of RAM and about 100GB of free storage (more if you enable ccache)
Much patience (the process will be long)
Getting started
Android SDK
You can setup android SDK by running
Code:
sudo apt-get install adb fastboot
Installing required packages
For that you can follow the steps on https://wiki.lineageos.org/devices/nicki/build#install-the-build-packages
Setting up directories
Create a folder in which android source will be downloaded
Code:
mkdir -p ~/android/lineage
Note: "~/android/lineage" is an example, you can create whatever folder you want, but in the next steps be sure you change paths.
Install the repo command
Like before you only need to run
Code:
sudo apt-get install repo
Initialize the LineageOS source repository
Now we can start to prepare sources download. Enter the following to initialize the repository:
Code:
cd ~/android/lineage
repo init -u https://github.com/LineageOS/android.git -b cm-14.1
And we need to prepare local manifests:
Code:
git clone https://github.com/rmnhg/local_manifests.git -b cm-14.1 .repo/local_manifests
Download the source code
To start the download of the source code to your computer:
Code:
repo sync
Note: This process will be long (over 30gb are going to be downloaded) and can be longer if your connection is slow so be patience.
Prepare the device-specific code
After the source downloads, ensure you’re in the root of the source code, then type:
Code:
source build/envsetup.sh
breakfast flamingo
This will prepare flamingo sources to be compiled.
(Optional) Turn on caching to speed up build
You can setup ccache if you want to speed up subsequent builds by running:
Code:
export USE_CCACHE=1
and adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want ccache to use by typing this from the top of your Android tree:
Code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration. See more information about ccache on Google’s Android build environment initialization page.
You can also enable the optional ccache compression. While this may involve a tiny performance slowdown, it increases the number of files that fit in the cache. To enable it, run:
Code:
export CCACHE_COMPRESS=1
or add that line to your ~/.bashrc file.
You can also change ccache files path by running:
Code:
export CCACHE_DIR=[COLOR="YellowGreen"]<path of your choice>[/COLOR]
or add that line to your ~/.bashrc file.
Configure jack
Jack is the new Java compiler used when building LineageOS 14.1. It is known to run out of memory - a simple fix is to run this command:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
Adding that command to your ~/.bashrc file will automatically configure Jack to allocate a sufficient amount of memory.
Start building
Now you can start compiling LineageOS. You can start running:
Code:
croot
brunch flamingo
NOTE: If terminal tells you "croot/breakfast: command not found" just run
Code:
source build/envsetup.sh
and try again.
NOTE 2: If you receive the error "SSL error when connecting to the Jack server. Try 'jack-diagnose'" check this post for a fix.
This will finally compile LineageOS for flamingo :good:
If it finishes succesfully, you will have in out/target/product/flamingo two files:
recovery.img, which is the LineageOS recovery image.
lineage-14.1-<date>-UNOFFICIAL-flamingo.zip, which is the LineageOS installer package.
You have to flash ano and copy installer zip into the phone.
Then reboot into recovery (Power+Vol down) and install this zip.
You can flash flash recovery running
Code:
sudo fastboot -s 256M flash recovery <pathtorecovery.img>
Thanks to @infus for his trick (-s 256M) with fastboot commands for big images.
I hope this guide has been useful for you
PD: If you want to discuss about development of this ROM, you can join our Telegram group here.
Join now
UPDATES
[06/13/2017] Guide successfully builds Lineage, but we have to fix kernel becouse it's not booting. I've also updated my local_manifests repo, so you need to run in android/lineage this
Code:
cd .repo/local_manifests && git pull origin cm-14.1 ;
cd ../..
[06/23/2017] Booted! But there are some bugs, we will upload ROM when that bugs are fixed
[07/25/2017] After a month we got this working for all variants, with basic hardware working (no camera yet) and with latest TWRP working . I'm working now on getting camera working and other small projects (on Xperia E3 also) but I am being slower to release new things because I have not much time and internet to work, I'm sorry.
[09/01/2017] Camera driver is now working! I have ported stock camera driver to renaissance kernel (LA.BF.1.1.3.. CAF) in another folder with the tag CONFIG_MSMB_CAMERA_FLAMINGO
Camera is still not working because of the HAL but it is nearer
[12/15/2017] I'm sorry we paused releasing updates for the compiled ROM, but I've changed much code and worked hard on camera (which is published on another branch named cm-14.1-cameratesting). Soon I will get some things finished and continue some other projects I had for this device. By the way I wish you a merry Christmas!
Reserved.
First of all I'm thanking you that at least you started to create the ROM for our device...
I really want to help you but I can't, due to internet connection, I don't have much data that I can download those sources (over 30gb)
But I really appreciate your work and hope someday you develop the ROM....
Hello! First of all, this version of Lineage is a very good thing for the Android Community ! I saw in the title that you are facing some difficulties, I'll try to help you. I have a friend who have the phone you talk about. We will probably try it on Wednesday. Did you need a log or something after you did ? Do you have the phone, or do you want my friend's one to test it ? Do you think that your ROM is compatible with your variant ? Or mine ? Thanks for passing some time on the gid build ! Have a good day !
infus38 said:
Hello! First of all, this version of Lineage is a very good thing for the Android Community ! I saw in the title that you are facing some difficulties, I'll try to help you. I have a friend who have the phone you talk about. We will probably try it on Wednesday. Did you need a log or something after you did ? Do you have the phone, or do you want my friend's one to test it ? Do you think that your ROM is compatible with your variant ? Or mine ? Thanks for passing some time on the gid build ! Have a good day !
Click to expand...
Click to collapse
The problems I have are related to system libs when compiling. Some of them fail to compile and I have to fix them manually, becouse of that system.img is not ready. All I have are LineageOS recovery and boot img files for LTE variants (for me that is not working but maybe for your phones things go well). On friday I can upload that imgs for you for test (remember that I have not system compiled so you can install recovery, boot.img may not work with other roms.
With my friend (who owns the xperia e3 d2203) we have started the step currently on the step of 30gb download
You can make a group with telegram to avoid polishing xda to speak and try to solve the problem encountered if you want it by giving the invitation link
infus38 said:
With my friend (who owns the xperia e3 d2203) we have started the step currently on the step of 30gb download
Click to expand...
Click to collapse
Cool, tell me if you start compiling process and, if you have errors, oleaje tell me what errors are given by terminal
infus38 said:
You can make a group with telegram to avoid polishing xda to speak and try to solve the problem encountered if you want it by giving the invitation link
Click to expand...
Click to collapse
Good idea! I'm going to do that
EDIT: Created a telegram group. You can join here https://t.me/xperia_e3
Hello ! After trying to compile the build, it stops and says that the error 1 has occurred. I tried many times but I always got this error (the only thing that changed is the time before the error occurs). I maybe didn’t correctly write the part with java and jack, but I just started to rewrite all from the beginning, I will keep you informed !?
I will prepare a computer to do this. It is almost done, just need a mouse I will download all these sources and start asap. Any help is much appreciated
EDIT: I have a Xperia E3 ready to test anything you want to. Just PM me for better contact info.. I'm here to help the development of this ROM.
I'm still using CM11 ;-; (can't live without camera)
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
@AmulyaX please see this
jpzex said:
I will prepare a computer to do this. It is almost done, just need a mouse I will download all these sources and start asap. Any help is much appreciated
EDIT: I have a Xperia E3 ready to test anything you want to. Just PM me for better contact info.. I'm here to help the development of this ROM.
I'm still using CM11 ;-; (can't live without camera)
---------- Post added at 11:36 PM ---------- Previous post was at 11:31 PM ----------
@AmulyaX please see this
Click to expand...
Click to collapse
Best of luck. I don't have the E3 now but if you need any help or ask about any error, feel free to PM me. ??
@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?
Ｄｈｒｕｖ said:
@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?
Click to expand...
Click to collapse
For now I am at the build of the rom with the help of rmnhg if you want to come help us you been free under the agreement of rmnhg to come on the group telegrame create for this purpose ??
Ｄｈｒｕｖ said:
@jpzex, @infus38, @rmnhg, I think you all have D2203. So, will you Port this ROM for D2212 after development of this ROM?
Click to expand...
Click to collapse
Yes, that is not difficult. I think that a little kernel change and some build.prop tweaks could do the trick, but first we need to complete a single build for D2203, which is the main model.
rmnhg said:
Yes, that is not difficult. I think that a little kernel change and some build.prop tweaks could do the trick, but first we need to complete a single build for D2203, which is the main model.
Click to expand...
Click to collapse
can i join too ?
Nicklas Van Dam said:
can i join too ?
Click to expand...
Click to collapse
Of course! Everyone is useful and will be welcomed
rmnhg said:
Of course! Everyone is useful and will be welcomed
Click to expand...
Click to collapse
Which source that you used as device and kernel tree? And are you building nougat? I'm D2202 user
anyway, for D2202 only available source for cm12.1 when i see from @hell_lock. Will our device run with that device tree?
Nicklas Van Dam said:
Which source that you used as device and kernel tree? And are you building nougat? I'm D2202 user
anyway, for D2202 only available source for cm12.1 when i see from @hell_lock. Will our device run with that device tree?
Click to expand...
Click to collapse
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).
rmnhg said:
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).
Click to expand...
Click to collapse
Okay, thanks sir. I was recently trying to fix for D2202 too. i'm using different source code, this for device tree device tree & this for yukon platform yukon tree. anyway for kernel itself i don't know which source that i must using it, i'm using xperia open kernel device by jerpelea and using yukon codename. but i'm still not compile it yet since i've problem with los 13.0
---------- Post added at 05:35 AM ---------- Previous post was at 05:30 AM ----------
rmnhg said:
We are using this kernel with this device tree. That sources are mainly designed for LTE variants, but in yukon repo there is more support for D2202/12 devices (see this commit).
Click to expand...
Click to collapse
and anyway, when i check your kernel source that is for D2203 mode (arima_8926SS) for single sim. can we use that kernel? since i'm using same config too?
I'll try to using your source and report it back
Nicklas Van Dam said:
Okay, thanks sir. I was recently trying to fix for D2202 too. i'm using different source code, this for device tree device tree & this for yukon platform yukon tree. anyway for kernel itself i don't know which source that i must using it, i'm using xperia open kernel device by jerpelea and using yukon codename. but i'm still not compile it yet since i've problem with los 13.0
---------- Post added at 05:35 AM ---------- Previous post was at 05:30 AM ----------
and anyway, when i check your kernel source that is for D2203 mode (arima_8926SS) for single sim. can we use that kernel? since i'm using same config too?
oh ya, and vendor source? when i saw from themuppets. Flamingo only updated until cm-12.0 and after that in cm-13.0 until cm-14.0 flamingo doesn't exist in that branch?
Click to expand...
Click to collapse
For vendor I'm using https://github.com/kj77/vendor-yukon on cm-14.1 branch
I think you need to include some device tree files for D2202/D2212 in kernel, since as you said that kernel is specific for D2203. I could try to make basic support for it.