Related
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
well,
just a suggestion
if u just want to know the LP work progress and collect the news/info into this thread,
maybe u should change the title,
cause the title it's little 'demanding'
and for the first start, maybe u could collect the link and put in here,
also give some brief update about the progress, for example
1. Mokee 5.0.1 (link to source thread/info) - status WIP - RIL bugs
and so on...
cheers
naved97 said:
Hi Guys, it's been so many days Kernel Sources are released, and Syhost Provided Lollipop with RIL Bug, but now the excitement is increasing day by day. When the sources weren't released, Developers were saying to wait until Kernel Sources are released , to fix major bugs. But still no response. I appreciate Developers for Providing Custom Kernels and Updated Scripts in previous Roms.
I request you to post all Lollipop Related News over here. and about Developers work on Github.
Thankyou.
Click to expand...
Click to collapse
asking for ETA both explicit or implicit is a no no no... it's top rules in XDA.
if you want it really soon, use Mokee by syhost and try to fix RIL bug using kernel source code.
beside how hard is to see armani-dev commit in CM12 in github?
https://github.com/armani-dev/android_device_xiaomi_armani/commits/cm-12.0
Sorry I didn't get you.?
Didn't see anything posted on here about it, unless I was being blind, but seems Xiaomi have been pretty quick this time around in releasing the source for the Mi5
http://en.miui.com/thread-352351-1-1.html
The news that you have been anxiously waiting for is here. Xiaomi has released the official kernel sources for your beloved Mi 5/Pro. So all you Android fans can rejoice and start cooking custom ROMs, mods, patches and most of all help in development and make the Mi 5 a better devices according to your satisfaction and liking.
The kernel source can be accessed at:
https://github.com/MiCode/Xiaomi_Kernel_OpenSource/tree/gemini-m-oss
Click to expand...
Click to collapse
:good:
Really good news finally. We just have to wait for CM14 now...
DaveP2611 said:
Didn't see anything posted on here about it, unless I was being blind, but seems Xiaomi have been pretty quick this time around in releasing the source for the Mi5
http://en.miui.com/thread-352351-1-1.html
:good:
Click to expand...
Click to collapse
There is atleast two topics about it already, but hey, it's so good. Spread the word (=
there's already a thread in the guides section. kindly check first before creating a new thread.
Does overclock possible now?
Thread Closed, we already have threads on this topic and posted in the wrong section
Thanks
This is a test build I take no responsibility for what this may or may not do to your device.
Click to expand...
Click to collapse
NEED TESTERS
currently i don't have the device to test i will be getting my device in the next week .
Click to expand...
Click to collapse
1. Install CWM Recovery
2. Do Full Wipe If coming from another ROM
3. Flash ROM
4. Flash Google Apps (my recommendation is to install minipal gapps due to /system partition size limits)
5. Reboot
Click to expand...
Click to collapse
]Not Booting
Click to expand...
Click to collapse
Code:
[B]Source[/B]
Here are the device tree :
Device Tree (from cm13 Nexus 9) : https://github.com/vickdu31/android_device_xiaomi_mocha
Kernel Tree (from Xiaomi KK) : https://github.com/vickdu31/android_kernel_xiaomi_mocha
Vendor Tree (old Xiaomi KK) : https://github.com/vickdu31/android_vendor_xiaomi_mocha
Thank you
@faust93 for cwm
XDA:DevDB Information
CM-13, ROM for the Xiaomi Mi Pad
Contributors
Rohit99, tank0412, vickdu31
ROM OS Version: 6.0.x Marshmallow
Based On: CyanogenMod
Version Information
Status: Testing
Created 2016-12-10
Last Updated 2016-12-13
Reserved
Edit 1:initial build didn't boot for me, no adb can't get log
Ok im gonna try it.
If you want, i can leave logcat for you
OoSTARTERoO said:
Ok im gonna try it.
If you want, i can leave logcat for you
Click to expand...
Click to collapse
Can get logcat? Try please.
Ofc, it doesn't boot. And don't create threads without testing.
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
unfortunately....I couldn't get logcat too...
Sudeep Duhoon said:
Can get logcat? Try please.
Click to expand...
Click to collapse
we can't get logcat. It doesn't boot, i mean there are problems with kernel or init scripts or both. Kernel needs patches.
Nihhaar said:
Ofc, it doesn't boot.
Click to expand...
Click to collapse
As I thought
Prebuilt kernel from cm11
Sudeep Duhoon said:
As I thought
Click to expand...
Click to collapse
hey can i use prebuilt kernel from cm11 source @Nihhaar
Rohit99 said:
hey can i use prebuilt kernel from cm11 source @Nihhaar
Click to expand...
Click to collapse
Always try to build kernel with source. I think you can't, but you can try.
Please edit the link in OP, its me who miswrote it... : /android_device_xioami_mocha --> /android_device_xiaomi_mocha
You need to fix up SELinux and the init scripts. Taking a shield tablet device tree, renaming things to mocha and changing the fstab isn't enough. As far as I can tell the shieldtablet device tree also has dependency on a shield common tree. There's also no value in creating a new thread each time you push new commits
Our kernel from Xiaomi is also pretty useless without commit history. The device tree is also from shield tablet, not Nexus 9.
We also have a tree for building TWRP with OmniROM that you can compile TWRP 3.0.2.0 with.
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
highwaystar_ru said:
What kernel repo is upstream one for tegra android? Like CAF for quallcom.
I've tried to merge xiaomi changes on l4t kernel https://github.com/HighwayStar/android_kernel_xiaomi_mocha
Merged dts files and arch/boot/march-tegra with some required drivers, but still cant boot it. Found somewhere here that l4t kernels is not for android, but for GNU/Linux, but what kernel is for android?
Cyanogenmod's shield kernel?
Click to expand...
Click to collapse
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Harrynowl said:
git://nv-tegra.nvidia.com/linux-3.10.git
I used rel-tn8-l-r7-shieldtablet8 to make a start on doing this. You could also use android_kernel_shield from CyanogenMod repo as it comes from the same place. But it will have a lot of extra commits for things not useful for mocha.
Here's what I have so far:
https://github.com/harrynowl/nvidia_tegra-3.10
Click to expand...
Click to collapse
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
highwaystar_ru said:
Oh, intresting, cloned same url, but started other branch l4t/l4t-r21.5.
What status of your tree? Cant boot? We need minimal bootable kernel to be able to get dmesg and make further progress.
Click to expand...
Click to collapse
Untested, been doing device bring up. That kernel won't work yet anyway it's missing atmel, synaptic and battery firmware. (Plus the code that goes with it)
Some devs have one that gets to recovery but only 1 CPU core can come online and the CPU gets a bit hot. Unfortunately their commit history is hard to follow so I've not had a proper look at it yet
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
drakonizer said:
My my...it's been a while since I've seen a cringe-worthy dev thread on XDA. So OP just used the device tree from Nexus 9 (a 64-bit device with a different processor and nothing in common with the Mi Pad other than the fact that they use Nvidia SoCs and are both tablets), unmodified KITKAT kernel sources from Xiaomi (which takes work to make it boot, even on KK) and KITKAT userspace blobs to compile the ROM, and for some reason decided to share it without testing. The 10-post rule is meant to keep such people out of the development sub-forums, but obviously that's not working.
I do not understand why the moderators are allowing this thread to remain open. It's just a thread by a wannabe dev offering a non-bootable ROM that has the potential to brick the devices of many newbies who may decide to try this.
This thread is even more useless than the other "DEVS-ONLY" thread someone else made. Honestly, the entire Mi Pad forum is filled with people who either expect Android 7.1.1 to magically appear on their tabs just because Xiaomi released outdated kernel sources or just wanna create threads like this for the "thanks or whatever". The never ask for ETA rule seems to just float over their heads.
Now to some useful information. I believe, even if we patch the kernel enough for it to theoretically boot cm13, it probably won't, considering the outdated userspace blobs for the Mi Pad. Unless someone has the knowledge to take their tab apart and figure out how to get UART data, it will be virtually impossible for the mi pad kernel to boot any new version of Android. I heard another interesting approach taken by some russian devs at the Xiaomi forums. They've managed to port the kernel from the Nvidia shield (and apparently it's booting). Now this would mean we can use the userspace blobs from the Shield to at least get the ROM booting (most peripherals won't work, but that's step 2). I do not know whether they use GitHub or if they've even open-sourced their work, but now we know that it's possible, so that could be a possible method of approach.
EDIT: LOL. I just read the OP again. The "dev" expects donations to help him work harder. This from a person who posted his way into somehow compiling his first Android build without even having the damn device.
Click to expand...
Click to collapse
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Harrynowl said:
I agree, this device has no development threads. Only 2 give me thanks and here's my donation link threads.
They have indeed used GitHub, but I don't believe they want to share the repo just yet so I won't post it publicly. It has many problems to sort and also sadly, they didn't keep the commit history from Nvidia as it was initialised via zip DL. It does boot to recovery though.
Click to expand...
Click to collapse
Oh! I didn't realize we were talking about the same person/team. I'd love to start developing for this device. In fact, I'm working on KEXEC-hardboot and Multirom right now, but I'd like to follow what you guys are doing and contribute as much as I can. Is there an IRC channel/IM app you guys use for communication? If so, I'd appreciate it if you could PM the info.
Hi all
I have been started to work on gemini for two weeks (switched to gemini development from my old phone Galaxy W)
I didnt get the device yet (but will get it as soon as possible, probably in 2 weeks)
However i started to work on it, and i really wonder "upstream linux kernel 4.4 can be ported to gemini? and why not?" after i saw CAF added msm8996 (our device's chipset family) support into Linux 4.4 kernel
As you already know our main kernel version is 3.18 right now,
Whats the benefit of 4.4 kernel:
-Nearly thousands of changes which some of them are bugfixes and some of them are new sweaty kernel features :good:
-Better power management
-Better memory management
-More secure (vulnerability fixes)
- And so on
So i started to work to port CAF 4.4 into gemini
- i just forked CAF pure,vanilla 4.4 kernel which support msm8996
and started to add xiaomi mi5's drivers + device specific changes
its very very WIP stage right now
TODOS:
- Merge all gemini drivers and device specific codes into kernel
- Fix all merge conflicts
- Update driver kernel API calls into 4.4 APIs (that is the hardest thing)
- Fix all compilation errors
- And hope for boot
İf anyone has an ability to contribute/help etc. and/or interested in this project , it would be really appreciated :good:
Here is the source code: https://github.com/sirmordred/Kernel_LA.HB.1.1.5_CAF-4.4 "gemini" branch
Mod Edit
Thread closed by OP request/No longer supported.
Reserved
And also to everyone: Kernel porting is really hard job and its a long run so dont expect miracles
i think it is worth waiting for
I'll wait and try when you uploaded Sir.
Wow... thank u sir..best of luck??
Wow well we do need great kernel for our gemini.... Thanks keep it up
another dev kernel for gemini, does it will support eas and vox populli?
Do you think other devs didn't try it till now? You can join our Telegram group to collaborate with the others that are working on it.
https://telegram.me/joinchat/CQCWTj-9G7RzUdfzKHbqbw
BTW: Why do you create a thread for a project which you barely have started...? It will be a long way and don't expect this to finish in 2017...
@33bca dude let him work Maybe he created this thread to have some help from devs ? some advices ?
BTW: Why don't you wrote here that he fork wrong branch but you just laughed at him on telegram ?
Jawor245 said:
@33bca dude let him work Maybe he created this thread to have some help from devs ? some advices ?
BTW: Why don't you wrote here that he fork wrong branch but you just laughed at him on telegram ?
Click to expand...
Click to collapse
I think you got me wrong on Telegram. That was far away from laughing at him...! If he wants any help he can join us on Telegram.
33bca said:
Do you think other devs didn't try it till now? You can join our Telegram group to collaborate with the others that are working on it.
https://telegram.me/joinchat/CQCWTj-9G7RzUdfzKHbqbw
BTW: Why do you create a thread for a project which you barely have started...? It will be a long way and don't expect this to finish in 2017...
Click to expand...
Click to collapse
Main goal is the colloborate devs, people who work on gemini to make development better and faster,
And the giving info about possibilities what can be done for future development on gemini kernel
I joined the group on Telegram but is there any dev group which is less crowded (contains only devs)
sir mordred said:
Main goal is the colloborate devs, people who work on gemini to make development better and faster,
And the giving info about possibilities what can be done for future development on gemini kernel
I joined the group on Telegram but is there any dev group which is less crowded (contains only devs)
Click to expand...
Click to collapse
Why is dere any problem in that group if u wana collaborate u can also pm the dev on Telegram
dkmsn8 said:
Why is dere any problem in that group if u wana collaborate u can also pm the dev on Telegram
Click to expand...
Click to collapse
Because of not talking about "xxx how to disable xxx option on xxx rom, when will xxxAndroidVersRoms come to our device" questions and talking about only development related things,
well, not problem for me, just wanted to say, lets talk via PMs then
sir mordred said:
Because of not talking about "xxx how to disable xxx option on xxx rom, when will xxxAndroidVersRoms come to our device" questions and talking about only development related things,
well, not problem for me, just wanted to say, lets talk via PMs then
Click to expand...
Click to collapse
Yeah.. anyway good luck with this project. Do collaborate with other dev..
sir mordred said:
Main goal is the colloborate devs, people who work on gemini to make development better and faster,
And the giving info about possibilities what can be done for future development on gemini kernel
I joined the group on Telegram but is there any dev group which is less crowded (contains only devs)
Click to expand...
Click to collapse
No there is no such group... once we have tried to create such a developer group it did not work that well
PM should be fine for the most of the cases, but if you want to create a developer only group, you are free to do that.
Wow man it's brave to try porting to 4.4
If it gets to work it'll be a wonderful thing!
As the thread question states I am a junior Java/Kotlin developer and would like to contribute to custom rom projects.
I have been mainly using Lineage OS on my old devices for a past few years and I am genuinely thankful for this community and would like to give back.
I have no idea where to get started and the only threads I found were really old from 2013 and hence I am posting it here. I have only gone as far as compiling AOSP from source and managing to flash it to my device. ( Any guidance is welcome ).
I have 2 additional queries :-
1) Why most custom rom releases are based on AOSP or Lineage as source rather than working backwards from the manufacture's provided rom? In that way the device can retain most of this functionality.
2) I have observed QUALCOMM powered devices are much more appreciated in this community compared to MediaTek, Why is that so? Recent MediaTek Chips have been quite powerful yet support from the community isn't there yet ..... what are MediaTek chipsets lacking ?
Mediatek doesn't release their source code so it's very difficult to develop custom ROMs.
Correct me if I'm wrong
How does your self-built AOSP perform? Everything working correctly?
I think the first question is, because the manufacturer's ROMs are proprietary and closed source, so it's not impossible, but difficult I think. Dunno how Xiaomi.eu does it.
Second question is, because Qualcomm releases source code to CAF - Code Aurora Forum. Custom ROM/Kernel Makers pull a few bits & pieces from CAF into their AOSP ROM, for that added spice.
I think MediaTek does too, but only for few devices?