Related
Hi,
Altough this is just the skeleton of it, let me share what I've set up until now.
I've also started a dedicated Google group here: https://groups.google.com/forum/?hl=en&fromgroups#!members/renesas-emev-osp
Anyone interested in contributing to develpment, plesae join!
1) Android
https://github.com/ffxx68/Renesas-device_emev
This is the entry-point to the GitHub repositories where I would put all the modification to the AOSP code which are specific to the Renesas EMEV for our Open Source Project.
Have a look at the README for further details and follow the progress, or open discussions, on our Google group.
2) Kernel
https://github.com/ffxx68/RenesasEV2-BSPGB-Kernel
This is the public GitHub repository for the 2.6.35.7 Kernel source code. It is customized to emxx code and it includes for the moment only the LCD patch that is necessary for the most common tablet (the kernel base code is aimed at the development board instead).
Same as above, anyone can contribute directly here.
3) Bootloader
https://github.com/ffxx68/RenesasEV2-bootloader
This is the public GitHub repository for the bootloader source code. It includes a patch for the 4 DDR tablet models.
I don't expect this to be changed much, but anyone can contribute directly pushing new files over here too.
4) Packaging
Some more details about how to wrap-up a fresh build and make a firmware for the tablet are found in the README mentieod above.
I've managed to boot Android from an SD card (see here: https://github.com/ffxx68/Renesas-BootSD) and I think a similar approach should be followed, at least for initial testing.
Kind of late to the party, but I'm really interested in this project... I applied to the Google Group, but I notice that the EV2 AOSP page you listed is gone... is there a specific reason for this? I would really love to contribute to this.
Hi, and welcome aboard!
I have edited a couple links above, which have changed a bit since then.
Thanks
I'm facing a problem with the touchscreen driver, which I have filed in the group list as well:
https://groups.google.com/forum/#!topic/renesas-emev-osp/smcwddwvNDo
(answer over there, if possible).
I can't understand why the driver for the touchscreen (found in drivers/input/touchscreen/pixcir_i2c_ts.c) is not loaded during the kernel init stages.
The touchkeys driver (ekt2201) is very similar in code structure and it's loaded as expected, while the _probe function of the PixCir is never called. This is the fragment from the dmesg kernel log:
...
<4>ekt2201_init
<4>ekt2201_i2c_ts_probe
<6>input: ekt2201 as /devices/i2c-0/0-0010/input/input0
<4>ekt2201:i2c_add_driver 0
<4>emxx_tsixcir_i2c_init
<4>emxx_tsixcir:i2c_add_driver 0
...
Note as the input device is created for the ekt2201 as the _probe is called, while the same doesn't happen for the pixcir.
Anyone with a clue?
thanks
Hi,
if anyone's interested in testing an experimental, pre-alpha version of the Open Source GB and Kernel build, leave a message here:
https://groups.google.com/forum/?hl=en&fromgroups#!topic/renesas-emev-osp/Mmd8r-YMaNo
Porting to JB has started: https://groups.google.com/forum/?fromgroups=#!topic/renesas-emev-osp/XSdLmPgD9Og
Welcome to CyanogenMod 7 For Micromax
Congrats Guys its the first CyanogenMod rom ever for ANY micromax device means Micromax A60 got the first CM7 compiled from sources ever!~!
Cheers!
This is fully compiled from CyanogenMod 7 sources!
Thanks [email protected] for helping me a lot....
This is build #1 so dont expect every thing working
Me and Keyur are working on CM7 to get a stable build for Micromax a60..
so please dont ask for ETAs please , we are working.
Working -
Project Closed!
Not Working -
Project Closed
How to show support.
1 Show your support by hitting thanks and providing us logcats
2 Post replies here so we can see you are interested
3 By helping us in fixing bugs...
Download Section-
Direct download link.
How to install-
1 Download it
2 Place in SD
3 WIPE DATA (most imp)
4 Flash Rom
5 Reboot.
Please help me with logcat... (type in terminal-)
Code:
su
logcat>sdcard/log.txt
let it complete then upload log.txt from SD
Dont spam this Thread...Dont mirror my work...
bro the download link not working
WTF ! No Replies
Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.
varun.chitre15 said:
Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.
Click to expand...
Click to collapse
hehe lol it is not binary port p350 is having same chipset as a60 namely msm7x27 and it is nearly same device so device config is ported to a60 !! first understand what is device config and what is compiled from source. can you tell me in what sense it is binary port ! device folder is open source ! checkout on my github : github.com/keyur2maru you gotta need to check boardconfig then you will know what is compiled from source first understand and then reply Regards , Keyur maru
rom2maru said:
hehe lol it is not binary port p350 is having same chipset as a60 namely msm7x27 and it is nearly same device so device config is ported to a60 !! first understand what is device config and what is compiled from source. can you tell me in what sense it is binary port ! device folder is open source ! checkout on my github : github.com/keyur2maru you gotta need to check boardconfig then you will know what is compiled from source first understand and then reply Regards , Keyur maru
Click to expand...
Click to collapse
Oh well don't tell that to me.
Same chipset doesn't mean that you just sync it from someones repo and build it?
Some common sense is needed to be used, you should have recommended him to build from CyanogenMod sources instead of pimping yours, and help him configure from scratch.
If this is the matter(and extent of your knowledge) why don't you mention what things you modified in the source in order to adapt for Micromax A60?
heehee lol first open my device config and check everything is modded ! for a60 and yeah you replied Rohan that Im copying ron stuff hehe !!
CM7 is Really Done by Drap and Pax0r not by Ron G
and about copying who said im copying I was the man for cm9 and checkout device config it is like written from scratch only checkout nothing is there related to p350 and if similar hardware is there ! it is ofcourse that we will port that device config to work with our device it is like RMCC ( LGE DeVICES MAINTAINER ) also do the same It is No need to write full from scratch i think you need to learn more not me
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
and we are not having having full source of cm7 it is only device config and source is synced from cm repo i think you need to learn more rather than me
---------- Post added at 02:21 PM ---------- Previous post was at 02:15 PM ----------
varun.chitre15 said:
Well just wanted throw a shout here.
I want to ask why P350 repo is used to do this? It is as same as performing a binary port with lots of data payload.
Click to expand...
Click to collapse
who said you p350 repo is used LOL :cyclops::highfive: and it is not repo it is device config :fingers-crossed:
rom2maru said:
heehee lol first open my device config and check everything is modded ! for a60 and yeah you replied Rohan that Im copying ron stuff hehe !!
CM7 is Really Done by Drap and Pax0r not by Ron G
and about copying who said im copying I was the man for cm9 and checkout device config it is like written from scratch only checkout nothing is there related to p350 and if similar hardware is there ! it is ofcourse that we will port that device config to work with our device it is like RMCC ( LGE DeVICES MAINTAINER ) also do the same It is No need to write full from scratch i think you need to learn more not me
---------- Post added at 02:15 PM ---------- Previous post was at 02:12 PM ----------
and we are not having having full source of cm7 it is only device config and source is synced from cm repo i think you need to learn more rather than me
---------- Post added at 02:21 PM ---------- Previous post was at 02:15 PM ----------
who said you p350 repo is used LOL :cyclops::highfive: and it is not repo it is device config :fingers-crossed:
Click to expand...
Click to collapse
This is where the noobish step was taken.
Boardconfig is meant to be constructed from scratch by analyzing the kernel configuration(Don't keep on shooting device specs are same)
Device specs doesn't mean you can grab the device configuration from it.
The location from where the source is synced doesn't matter(provided that its unmodded) but the Configuration matters a lot. Compiler analyses the configuration and readily modifies the source code and initializes compilation.
And this is why major functions are not working in your buid.
I saw your github repo of A60 and as it is a initial commit I cannot see what configurations you changed.
Can you mention here the modified lines?
And for "you need to learn more than me"
I would say no one is perfect, I agree that I have no experience in building a ROM from source(as I lack a good network connection) but that doesn't mean I have no knowledge in it. And for that statement you may receive a infraction from a XDA moderator These are fundamental aspects which are needed to be understood before proceeding with a build.
See bro I don't wanna fight but just i want to say that it is my own work it is not copied if you don't understand what are changes done how can you say im copying I don't fight It is my Own work Not any copied one
---------- Post added at 02:50 PM ---------- Previous post was at 02:48 PM ----------
and if you want to see edits just have a view at boardconfig can check nothing is related to p350 i just want to prove that it is my official work and not copied work and about i said
You need to learn more rather than me
I said that because you're statement is totally wrong ! i know im right so i said that
rom2maru said:
See bro I don't wanna fight but just i want to say that it is my own work it is not copied if you don't understand what are changes done how can you say im copying I don't fight It is my Own work Not any copied one
Click to expand...
Click to collapse
I don't have anything to do with if you copied or didn't.
But the approach Guided by you to Rohan is way tedious and will end both of you with nasty unremovable bugs which will point to binary port again!
You know this very well configurations play a vital role and are meant to be constructed from scratch instead of base them on other device
Yes you can use it for reference, but not use it for compilation as it contains device specific configurations.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
rom2maru said:
and if you want to see edits just have a view at boardconfig can check nothing is related to p350 i just want to prove that it is my official work and not copied work and about i said
You need to learn more rather than me
I said that because you're statement is totally wrong ! i know im right so i said that
Click to expand...
Click to collapse
What should I do with boardconfig? To see what's changed I need commits with those changes.
And how was I wrong?
Prove it pls.
See bro I don't think i should recieve infraction and about fixes it is not like in the first build we will get everything working even steve kondik will not able to do this our first aim was to get it booted and then fix bugs and about fixing bugs that are not fixed in rom ! they are fixed in device folder ! and about my way even RMCC do the same to get cm7 or cm9 on any new lge devices ! it is not written from base ! and check device folder most things are written from base and edited boardconfig and fixes will be done by adding new lines removing unnedded lines and all !
---------- Post added at 03:04 PM ---------- Previous post was at 03:02 PM ----------
varun.chitre15 said:
I don't have anything to do with if you copied or didn't.
But the approach Guided by you to Rohan is way tedious and will end both of you with nasty unremovable bugs which will point to binary port again!
You know this very well configurations play a vital role and are meant to be constructed from scratch instead of base them on other device
Yes you can use it for reference, but not use it for compilation as it contains device specific configurations.
---------- Post added at 03:00 PM ---------- Previous post was at 02:54 PM ----------
What should I do with boardconfig? To see what's changed I need commits with those changes.
And how was I wrong?
Prove it pls.
Click to expand...
Click to collapse
just compare p350 boardconfig from cyanogenmod repo and compare with my a60 boardconfig and even compare whole device tree everything is changed and edited and that's the way we get cm7 or cm9 on new device and about p350. our cm7 main dev drap also ported p500 device config
Alright! I will see what's done and send a pull request too if needed
Good luck!
Thanks Bro See I Don't wanna fight !
I Just wanna Prove that I was Right And If you want further Proof Wait i will first fork p350 repo and then do edits in further commits so you can see commits and check what's edited As right now im busy in releasing my ics weekly #1 for p350 and did i got infraction i think i should not
Good to see cm7 for a60 ! Congrats guys
Sent from my ZTE_U N720 using xda premium
GB 2.3.7 port to karbonn A1
Hey friends i have successfully ported a rom based on racer rom on my Karbonn A1 or Zte N721 or Zte Racer or MMX A60 all have same specifications .the base ROM is racers ROM based on CM 7 . If i flashed it as it is it does not boot earlier. Then i used android kitchen porting tool . Now the rom the booting on my device but the issue is that My WiFi, Bluetooth and No service with sim. Idnt understand whats the problem is i guess it is dude to drivers but i dnt know how to change them.I need suggestions so that i can start working further .
here is the link to ported rom .
http://www.mediafire.com/download.php?4pzwnb6pbbw5pym
I was wondering if you guys would be as much helpful in making a CM based ROM for Micromax A57, which is a simple midrange model. But we have got a large community of users, and small-time developers. It would be awesome to see CM booting up in our phone Please help us
jyothisthaliath said:
I was wondering if you guys would be as much helpful in making a CM based ROM for Micromax A57, which is a simple midrange model. But we have got a large community of users, and small-time developers. It would be awesome to see CM booting up in our phone Please help us
Click to expand...
Click to collapse
haha..i am the ROHAN in facebook and the CEO of geekyzz.blogspot.in....remember me?
forever king said:
haha..i am the ROHAN in facebook and the CEO of geekyzz.blogspot.in....remember me?
Click to expand...
Click to collapse
Ofcourse I do My buddy Adhithya speaks highly of you
jyothisthaliath said:
Ofcourse I do My buddy Adhithya speaks highly of you
Click to expand...
Click to collapse
who is he?
Is This Project Alive????
M.A.D. mod Kernel by Verevka
Custom Kernel created by Verevka for JiaYu S3 for MarshMallow ROMs.
Based on https://github.com/MediatekAndroidDevelopers source code.
This project is closed - dev has sold his phone.
Code:
#include
/*
* Your warranty is now void.
*
* We aren't 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 Kernel
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*/
Description:
This is custom Kernel created by Verevka for JiaYu S3 for MarshMallows ROMs.
This Kernel is based on https://github.com/MediatekAndroidDevelopers source code.
Features:
Added exfat & f2fs support;
Probably battery drop is fixed;
Linero 5.3;
Other features from Verevka's Kernel for Android 5.1
Bugs:
Hall sensor isn't working.
Installation instructions:
Flash via SP Flash Tools: CM13 version for CyanogenMod 13 by M.A.D Team, AICP version for AICP11 by M.A.D Team.
Download:
Take a look at Downloads section next to Discuss.
Author:
Verevka
M.A.D Team:
superdragonpt, DerTeufel1980, fire855
Kernel version: Linux 3.10.101
ROM Firmware Required: Android 6.0.1 from M.A.D Team installed, custom recovery installed
XDA:DevDB Information
M.A.D. mod Kernel, Kernel for the JiaYu S3
Contributors
Borizzz, Verevka
Source Code: https://bitbucket.org/Verevka/android_kernel_jiayu_s3_h560
Kernel Special Features: Includes exfat, f2fs support and others changes
Version Information
Status: Abandoned
Current Beta Version: Initial release
Beta Release Date: 2016-08-02
Created 2016-08-02
Last Updated 2016-08-03
Reserved
Reserved
Reserved for Dev.Purposes
Where can i find the download link? Sorry
pleasetouchmenot said:
Where can i find the download link? Sorry
Click to expand...
Click to collapse
Just like in CM/AICP/AOSPA threads - take a look at Downloads section next to Discuss/Screenshots.
Borizzz said:
Just like in CM/AICP/AOSPA threads - take a look at Downloads section next to Discuss/Screenshots.
Click to expand...
Click to collapse
Got it now. Thankyou
Please post source code. Else thread is going to be closed
Regarding special kernel features... Exfat, f2fs... It's totally useless because this is integrated on rom side (fuse - Filesystem in userspace) already. And kernel implementation is not even been used, although being present, if one does not force initramfs to use it (which breaks adoptable storage).
The M.A.D. Team
DerTeufel1980 said:
Please post source code. Else thread is going to be closed
Regarding special kernel features... Exfat, f2fs... It's totally useless because this is integrated on rom side (fuse - Filesystem in userspace) already. And kernel implementation is not even been used, although bring present, if one does not force initramfs to use it (which breaks adoptable storage).
The M.A.D. Team
Click to expand...
Click to collapse
Why you may be 2 years to spread the firmware and the kernel without the source code, and I can not? I'm not ready to shell out possibly a month.
We were not allowed by jiayu China.
You forked our gpl kernel. Yours has to be gpl as well because of this.
The M.A.D. Team
hi, how about twrp that also supports and read f2fs?
When I put the kernel to 5.1, Report response was exactly the same. Why you are allowed to upload 5.1 without source, but I do not? Double standards? =)
(When I uploaded my kernel 5.1 on the forum moderator said, too, that you why he will not say the same about the 5.1? Double standards? =) )
---------- Post added at 12:00 PM ---------- Previous post was at 11:45 AM ----------
He opened the source code in the cap threads.
---------- Post added at 12:06 PM ---------- Previous post was at 12:00 PM ----------
My work is over for this phone! Maybe we meet with someone on the forums Vernee Apallo Lite. Goodbye!
Hopefully with DerTeufel1980 I have not meet !!!
Goodby!
Also, we never released any kernel on xda, because we were not allowed to. Some people are just too stupid to read xda rules.
If you are going to release vernee kernel without sources, your thread gets closed as well.
Edit: which work is over? You didn't do a thing... [emoji30]
The M.A.D. Team
Just my sources for 5.1- https://bitbucket.org/Verevka/android_kernel_h560
Verevka said:
Just my sources for 5.1- https://bitbucket.org/Verevka/android_kernel_h560
Click to expand...
Click to collapse
So, why don't you just release the new sources? No one prohibited you to base your kernel on top of ours. Just release sources, or keep it away of xda
The M.A.D. Team
what is difference i dont understand i think that 2 kernel are the same
All work, efforts and contributions offered to the community as volunteers should be thankful and appreciated by all. @DerTeufel1980 , your attitude and the way you respond to @Verevka is not adequate. It seems presumptuous, arrogant, poor, uneducated and even disrespectful and insulting. Please, you should apologize
---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------
Thanks you for this work @Verevka ......
You do a lot to help make bigger and enrich this community. Thank you very very much
My first post was like: please add source code. His answer was like &!%!
I don't need to apologize for anything. If he does not want to share his kernel source, based off our open source kernel, he can go wherever he wants to, but not xda... He just should go there quickly
The M.A.D. Team
Verevka said:
When I put the kernel to 5.1, Report response was exactly the same. Why you are allowed to upload 5.1 without source, but I do not? Double standards? =)
(When I uploaded my kernel 5.1 on the forum moderator said, too, that you why he will not say the same about the 5.1? Double standards? =) )
---------- Post added at 12:00 PM ---------- Previous post was at 11:45 AM ----------
He opened the source code in the cap threads.
---------- Post added at 12:06 PM ---------- Previous post was at 12:00 PM ----------
My work is over for this phone! Maybe we meet with someone on the forums Vernee Apallo Lite. Goodbye!
Hopefully with DerTeufel1980 I have not meet !!!
Click to expand...
Click to collapse
Do not stop working on this smartphone. Do not give up, do not kneel. Thanks to your work is no longer only a single mode of development. thanks to your work this community is great. I appreciate your work ..... I appreciate the work of all developers: Portuguese, Russian, German, Spanish, Italian, Chinese and all countries of the world
---------- Post added at 03:16 PM ---------- Previous post was at 03:12 PM ----------
DerTeufel1980 said:
My first post was like: please add source code. His answer was like &!%!
I don't need to apologize for anything. If he does not want to share his kernel source, based off our open source kernel, he can go wherever he wants to, but not xda... He just should go there quickly
The M.A.D. Team
Click to expand...
Click to collapse
I have great sorrow and sadness after reading your words in this post.
:crying:
antonioantuan said:
All work, efforts and contributions offered to the community as volunteers should be thankful and appreciated by all. @DerTeufel1980 , your attitude and the way you respond to @Verevka is not adequate. It seems presumptuous, arrogant, poor, uneducated and even disrespectful and insulting. Please, you should apologize
---------- Post added at 03:02 PM ---------- Previous post was at 02:59 PM ----------
Thanks you for this work @Verevka ......
You do a lot to help make bigger and enrich this community. Thank you very very much
Click to expand...
Click to collapse
Actually he was simply stating what XDA rules demand for development threads ...
Also he was actually helping out the guy when he said his "commits " of adding exfat and all on kernel is useless .
Xfat,and this file systems...are not mandated by kernel , but at user level ...
Verevka seems not to understand very well MediaTek environment
( understandable, we all need to learn at some point ), he was actually helping the guy out.
The "rudeness" was simply a legitimate statement if we look at :
- XDA rules concerning GPL, and development threads.
- And, GPL rules and code of conduct , how to use commits, rebasing on an outside sources , cherry-picking, keeping git credits , and keep a git history.
This are all terms that you are most likely not familiar with
( understandable your not a kernel developer )
But its something that verevka will sooner or later must embrace, and follow this rules on future works like vernee, or simply on community based works .
His first reply was due to lack of verevka's source. Since there was only a link to M.A.D. repo of github, that did not reflect the source used on this kernel...
Our GPL is up, enyone is free to use it, and PLEASE USE IT.
But there's guidelines to follow...
Cheers
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.
I found this on youtube not sure if its real or not
https://www.youtube.com/watch?v=-SRqxkMpeMc
Poco F1, running a GKI kernel, and device specific modules loaded separately.
Video by Sumit Semwal
Additional Details:
* Xiaomi Pocof1 (beryllium) device config is hosted at:
https://github.com/pundiramit/device-...
* GKI (android-5.4.17) Image.gz and kernel modules are copied from
device/linaro/dragonboard-kernel project, built as part of the Android
CI.
* Kernel source for prebuilt vendor kernel modules (panel, labibb
regulator) and DTB is hosted at:
https://github.com/pundiramit/linux/t...
* Adreno firmware binaries are copied from stock PocoF1 images.
Yes, it's real. Don't be fooled by the Android R in About Phone - that's just what it says when you're running an AOSP master build. That's not what's important. What's more important is what they've done with the kernel.
https://www.google.com/amp/s/arstec...inline-linux-kernel-support-in-android/?amp=1
Tom Gall, the director of the Linaro Consumer Group, showed off a Xiaomi Poco F1 actually running the mainline Linux kernel under the usual Android OS. Gall told the audience, "There are major, major props to be given to the Google Kernel Team in particular for getting their code upstream so that we can boot devices with a mainline kernel
---------- Post added at 09:20 AM ---------- Previous post was at 09:19 AM ----------
good job brother for for trying to bring it to masses.
Repo's are gone :'(
Anybody get a clone of the second repo at least? PM or post, please!
This is well documented now on AOSP but the work done here would save a lot of time.
CosmicDan said:
Repo's are gone :'(
Anybody get a clone of the second repo at least? PM or post, please!
This is well documented now on AOSP but the work done here would save a lot of time.
Click to expand...
Click to collapse
GitHub - pundiramit/linux
Contribute to pundiramit/linux development by creating an account on GitHub.
github.com
D1stRU3T0R said:
GitHub - pundiramit/linux
Contribute to pundiramit/linux development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Ah thank you, there was only an extra t on the second URL - typo.
This is awesome. Hopefully more 845 devices get the GKI treatment so we can experiment with different modules from other devices that get more love/attention from OEM's