I thought of developing a kernel so that i can use it with my CM11 that im going to port shortly. I thought I'll compile the stock kernel from source itself. I use android pre-built tool chain (arm-eabi-4.6)
I get a lot of compiler errors on stock kernel without any modifications itself...
Do i need to change my tool chain?
Sent from my One V using XDA Free mobile app
I never tried to build the stock kernel, but I think they did it with the android 4.0 toolchain.
To run CM, you need a CM-Kernel. You have to port things from the stock or a custom kernel (like Hellboy by maxwen) to the cm11 kernel.
Try to use rastomanchiks kernel sources (https://github.com/rastomanchik/android_kernel_htc_primou). This kernel is mostly working, stable and has a good battery life now.
I'd also like to build cm11, but my download speed is to slow to download the sources.
Exactly. Even my download speed is slow. And i have a cap also. After 8GB, my download speed drastically decreases. It takes ages to sync the sources...
Sent from my One V using XDA Free mobile app
How different is Cm kernel from stock? I mean what changes should i make?
Sent from my One V using XDA Free mobile app
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Help
jonas2790 said:
Cm needs many features which aren't included in the stock kernel and also you should get ION memory allocator working.
Click to expand...
Click to collapse
Yeah. How do I port?
What happened to your CM12 project?
hehaichi said:
Yeah. How do I port?
What happened to your CM12 project?
Click to expand...
Click to collapse
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
jonas2790 said:
I started working on cm12 again yesterday and finally have cm11 sources now, so expect a cm11 build in some days
I can't help you with porting, because all the porting work was done by rastomanchik and I chatted with him. You'd have to ask him about this, but he wasn't online the last weeks and can't speak english without google translator.
Click to expand...
Click to collapse
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
hehaichi said:
Actually I insist on porting myself so that I can learn building properly.
Actually these things are also interesting.. fixing bugs and all...
Have series of exams till May end. I cant build properly until then. I thought why not learn something..
Where did you learn about building and other stuff. Also I want to build the device tree on my own.
If you could specify some sources to learn, that would be grateful!
Click to expand...
Click to collapse
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
jonas2790 said:
This is exactly the same point of view I had when I started some months ago
Sadly, there isn't much documentation about own device trees and own kernels out there.
There also is no reference device tree, so every dev does it in his own way. I'm always trying to have a clean, easy device tree and use the CM ones as a reference.
You can find some tutorials about building cm, but only with downloading a ready-to-use device config and kernel.
I just played around with it one or two weeks and learned the most.
If you have enough time, please at least try to get into this stuff, maybe we can get cm12 running.
You can reach me on irc in the channel #hov on freenode.
Click to expand...
Click to collapse
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
hehaichi said:
I have sufficient time only after May. Till then I'll have to do some research and learn the basics.
I saw on the CM wiki page, it says you can run a prebuilt kernel also... So would it work if we could tweak the stock kernel a bit?
And how do I apply patches to the kernel?
Click to expand...
Click to collapse
Yes you can use a prebuilt kernel, but it will only work if the kernel supports you cm version.
You apply patches to a kernel by changing files or directories in the kernel. For example you can use another fs module (maybe with more functions) by copy and pasting the folder for the module from another kernel. The problem is, the new module may require some functions your kernel does not have so it won't compile.
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
hehaichi said:
Hey i had mailed rastomanchik and he said 3.4.x kernel is an impossibility for cm11? Why?
Sent from my One V
Click to expand...
Click to collapse
1. It would be much, much, much work.
2. I think there are some device-specific drivers that only work with 3.0
I'm ready to do that work only if i knew how to...
Sent from my One V
hehaichi said:
I'm ready to do that work only if i knew how to...
Sent from my One V
Click to expand...
Click to collapse
Try to get into it yourself or talk with people who know about kernel developement, I'm also new to android developement.
Related
helllo xda, many of you might have heard that I AM building CM10 from source and I have heard the we need the (kernel,gpu.....) drivers,
now broadcom released them and this is good.
my question is : how to use them ? pls help me
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
tingtingin said:
Many of u have heard?
Phone Slow? go ------>HERE<------
_____________________________________
"All my life I had one dream to achieve many many goals"
Click to expand...
Click to collapse
Yes I have made a thread for that
Sent from my GT-S5360 using xda premium
Gamer R said:
As I said earlier,
Building from source is better than porting.
But... if you're building from source , you'll be stuck having the same bugs as CM9 by whitexp has.
Sources which broadcom released (actually patch files, not actual source) are mostly meant for CM7. That's why whitexp couldn't proceed with CM9. It you see the madteam forum, and check whitexp's comment on asking proper release of sources , you'll get to know what I'm trying to say.
Also,
I did say earlier that whitexp made CM10 via sources and had end up getting the same bugs as CM9. Try fixing CM9 , if possible
Click to expand...
Click to collapse
They cant work for cm10
Sent from my GT-S5360 using xda premium
mohamedrashad said:
They cant work for cm10
Sent from my GT-S5360 using xda premium
Click to expand...
Click to collapse
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
celisdelafuente said:
Maybe, maybe not. Patched blobs Broadcom made available for CM7 could be linked to specific version of libraries in CM7 that could have changed in CM9 or CM10, the only way to know is trying to build CM10 using this blobs, they must be placed somewhere under vendor/samsung/totoro/propietary/lib
You better read the whole Getting Started section here first, then the thread from Whitexp about building CM7 and adapt it for CM10.
It will be useful if you had previous experience building succesfully the Linux kernel for any architecture or something like Linux From Scratch, a good understanding of how a Linux system works is critical to be able to set up the environment and do a succesful build.
Be prepared to spend a lot of time reading, hunting and fixing missing dependencies! Good luck.
Click to expand...
Click to collapse
thanks
I want to create a custom kernel for the LG E980.........what do I need to learn to do so.......I have never made a kernel before so any help would be appreciated.....Thanks In advance
This belongs in general not development
Sent from my LG-E980 using Tapatalk
justin860 said:
This belongs in general not development
Sent from my LG-E980 using Tapatalk
Click to expand...
Click to collapse
Sorry I'm new to XDA
rjmxtech said:
I want to create a custom kernel for the LG E980.........what do I need to learn to do so.......I have never made a kernel before so any help would be appreciated.....Thanks In advance
Click to expand...
Click to collapse
read. lots and lots of reading. and be patient.
search around xda for the how-to threads on kernel building and customizing.
i started work on a 4.3 kernel a while ago before we had stable cm-10.2 official builds, but abandoned it after the switch to the lge-kernel-gproj sources because i just don't have the time.
my suggestion is to check out the sources for other devices' custom kernels, such as those for the lge mako/optimus g, htc one/m7, and samsung gs4/jflteatt. you can probably cherry pick batches of commits from some of those kernels, but be sure you have a sense of what the changes do, or at least which modified files do what. also, it's worth noting that not all kernel sources are structured the same way even though they're all linux kernels. so cherry pick with caution.
be sure that you update the defconfig for the correct device in arch/arm/config (or create a new one for your custom kernel). if you're forking the lge-kernel-gproj sources from cyanogenmod (which i highly recommend as your base), there is already a defconfig for the e980.
um...other things...as far as over clocking and undervolting, when you browse other kernels' sources, you'll want to look at the commits involving cpufreq and/or acpuclock-8xxx (don't recall the specifics off the top of my head). iirc, start by looking in arch/arm/mach-msm and see which files were most recently modified.
good luck, and if you need help, i suggest checking out the project rookie threads (search xda). as long as you ask nicely and keep a courteous attitude, folks in those threads are extremely helpful.
Presenting CM13 unofficial. Built from mostly pure CyanogenMod sources, with a few tweaks that I try to keep updated on my github. This is only possible due to the work of Ziyan and MWisBest.
Instructions
First time flashing CM13 to your toroplus (or coming from another ROM)?
Unlock & install a recovery
Wipe data & cache partitions
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Updating from a previous build?
Just install the latest ROM zip. If you had Google Apps installed, they will be reinstalled automatically.
Click to expand...
Click to collapse
Downloads
Latest cm-13.0 build: https://www.androidfilehost.com/?fid=24588212152305191
Final cm-12.1 build: https://www.androidfilehost.com/?fid=24438995911970260
All builds: https://www.androidfilehost.com/?w=files&flid=23531
Unofficial TWRP recovery: https://www.androidfilehost.com/?fid=24459283995311440
Google Apps: http://opengapps.org/
- Platform: ARM
- Android: 6.0
- Variant: pico (recommended), or nano
Bugs
LTE Data does not work. (3G works)
XDA:DevDB Information
UNOFFICIAL CyanogenMod 13.0 (DDK 1.9), ROM for the Samsung Galaxy Nexus
Contributors
musical_chairs
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-09-25
Last Updated 2016-07-15
now with Marshmallow!
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
illinoissparks18 said:
Will this be updated to work with the new GPU drivers? Thank you!
Sent from my LG-LS980 using XDA Free mobile app
Click to expand...
Click to collapse
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
OK I am going to be on board with testing for sure. I left a post in the now no longer current official thread that I flashed the last official build yesterday and I had perfect 3G to LTE to 3G handoff, rock solid WiFi strength, basically everything seemed to work very well. I am looking forward to seeing how things progress. I haven't been able to keep any of the official CM builds from bootlooping until now. Hopefully you stick with it because I am getting better performance from this device than I have seen in a long while
Sent from my Galaxy Nexus using Xparent Gray Tapatalk 2
musical_chairs said:
Short answer: yes. I'm going to try grabbing the relevant code from MWisBest's githib. If it turns out to be too involved for my limited skills, it will have to wait until Ziyan submits the changes to CM.
Click to expand...
Click to collapse
Awesome!! Thank you!!
Sent from my LG-LS980 using XDA Free mobile app
I should've had a machete to hack through the jungle of build errors from pulling a modified OmniROM device tree into a CyanogenMod build. Looks like the build is rolling now though, with any luck it might just complete successfully - who knows, it might even boot.
The only thing slower around here than me is my poor old computer.
Its kind of ironic that the Galaxy Nexus was the first official LTE device for Sprint and I am only just recently starting to get LTE on a semi regular basis.
@musical_chairs, take your time with your builds. I assure you that they are appreciated. Now that this device is actually getting decent (for Sprint) signal and still has current builds makes it more enjoyable to use than just about any time I can remember....I just miss Imoseyon's Lean kernels. I got GREAT battery on those. They were compiled in the now deceased (I think) CMRemix ROMs but the LTE is definitely a plus
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
musical_chairs said:
Update: For now, I have stopped working on building CyanogenMod with the DDK 1.9 drivers. I was ending up with a completely unsustainable mess of a device tree, and was still running into build errors. If new drivers are what you want, use FML. I'll focus on keeping the regular CM builds updated for the time being.
Click to expand...
Click to collapse
Link to toroplus build for fml?
Zeinzu said:
Link to toroplus build for fml?
Click to expand...
Click to collapse
I'm following its developements, but haven't had time to try it personally yet.
http://forum.xda-developers.com/galaxy-nexus/sprint-develop/rom-fml-fork-life-10-13-2014-t2903695
Thanks for trying anyhow. I'm glad cm11 still has a fighting chance with the GNex, thanks to you, and all the others who are able to help out.
We're all waiting for cm12 to get to a buildable state. In the meantime, I've been working on upgrading my build box. My old machine was just barely capable of building android, the 'new' one isn't new but it was a real beast in its day. Time for a clean build has dropped from a day and a half to two and a half hours. I'm happy...
jd14771 said:
just curious, how difficult is it to compile roms? Do you need to know how to write your own code or is it over glorified copy and pasting with packages and stuff?
Click to expand...
Click to collapse
I do a lot of copying and pasting, a lot of reading guides, and a whole lot of google-ing. I don't know how to write my own code, but I have lots of experience with applying patches. Compiling roms is not that hard if you're a Linux user, have a working knowledge of the command line, and have a basic understanding of git. Take away any one of those things and it becomes a whole lot harder.
jd14771 said:
Yeah i haven't gotten to play with linux, nor do i know what git's are (i think they are large batch's of code posted in plain text?) . always wanted to try but don't have the time.
Click to expand...
Click to collapse
git is the software the devs use to keep track of changes in the code. Most Android devs have their git repositories on Github, those are probably what you are thinking of. Every little change (called a 'commit') has its own unique hash number. It's pretty amazing, you can look through somebody else's commits and find one that fixes a bug you are working on, or split tens of thousands of changes in half, then in half again, then in half again, etc., and pinpoint the exact commit that causes a bug on your system - though that's more useful in Linux kernel development than in Android.
I don't really have the time either, but it's such a fun hobby...
Using quickboot?
Coming from Vanir. Really like the facility quickboot gives. Anyone "enabled" it? I can't seem actually show the field to turn it on. Settings search finds it, but that's it... Noticed Dev options is hidden also. What's up?
Props for keeping CM11 updated. Really like I can actually use SMS in Hangouts.
I haven't been following the nightly changes since toroplus went dark, but I ran a build today--nothing special, just the latest cm...whatever changes they are. I could post it but don't know if I should make another thread or just link to it in here.
Anything substantial get added to general cm in the last few months?
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
yotvb531 said:
I tried to run a build of cm12 but it looks like things still aren't ready for building yet, either that or I'm not sure how to switch back and forth between the cm11 repo and cm12 without getting repo update errors.
Click to expand...
Click to collapse
I got cm12 built and booting for toro for the first time today. I'm trying to get mobile data working on that, then I'll give toroplus a shot. Looks like it shouldn't be too much trouble. Feel free to post any of your builds here, or start your own thread if you prefer.
Here's my cm11 build from yesterday--equivalent to a plain nightly. It's been running fine since I dirty flashed it last night. Md5sum is linked as well and noted below.
https://www.dropbox.com/s/lp4j3yayuktmlot/cm-11-20141227-UNOFFICIAL-toroplus.zip?dl=1
https://www.dropbox.com/s/z1b72j7oh70eg5w/cm-11-20141227-UNOFFICIAL-toroplus.zip.md5sum?dl=1
MD5 Sum: e6c265c57e00b4949362d6ff53c9a799
Well I got cm12 built and booting on toroplus, unfortunately the RIL is completely borked, so no cell service at all at this point. I'll keep working on that, in the mean time check out the updated cm11 build in the post right above this one.
UnityROM-2 v.3.0.1
LG Optimus G - Sprint US ONLY ( LS970 )
(INTERNATIONAL VERSION NOT HAPPENING || NO GEE/B EVER!!! || DO NOT ASK)
Basic Overview
Source built Cyanogenmod 11.0 with a bucket of butter poured on top .
Compiled and Built with SaberMod GCC 4.8 Toolchains with a lot of optimization flags set.
BUILDTYPE = SNAPSHOT ONLY
(Not meaning only once a month or so like CM Inc.)
Aroma Installation.
Purpose
Just trying to make a cleaner, faster, and generally more optimized build basically, without changing the ROM itself (apps & such). With some extra nice things thrown in even if there's is no visible difference in the ROM
Credits
@IAmTheOneTheyCallNeo for all of his help getting GCC 4.8 up and running finally. I owe you big man.
@Captain_Throwback for his original commits and help with the original thread & in this one as well.
@gruesomewolf for all of his help learning how to build a custom kernel.
Cyanogenmod Inc. & Google Inc. of course. For everything they do, way too much to try listing here.
LiquidSmooth for some additional build flags.
And please, if you like my work or the work others have contributed to this project, hit the thanks button. Thanks.
Features & Links
*** Global O3 & Strict-Aliasing=3 Optimizations & lots more ***
Full-Modular Aroma ROM & Gapps WITHIN the main package, yet still in separate directories.
Clean or Dirty ROM Flashing Options in Aroma.
Multiple LCD Density Options in Aroma.
System App Remover in Aroma.
Works with or without Gapps Installed
***UnityKernel-3.0.1 Features***
Optimized same as the UnityROM-2 only with GCC 4.9.
I/O Schedulers: SIO & FIOPS.
Governors: Intellidemand & Intelliactive.
LZ4 Compression/Decompression.
Current Release:
https://www.androidfilehost.com/?fid=95784891001602827
UnityKernel-3.0.1 Updater (includes previous 2.7.0 Kernel)
Current Release (UnityKernel Only):
Not available yet sorry
Development Section
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
will this work on geeb?? ill defintely test if so
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
dr3adl0ckd said:
will this work on geeb?? ill defintely test if so
Click to expand...
Click to collapse
LiquidSmokeX64 said:
Extract the build.prop. It will tell you cause I really don't know lol. All I really know is I added the LS970 dependencies to my repo, did the UnityKernel mod and built it. So you tell me cause I'm not at my PC
Click to expand...
Click to collapse
I am fairly certain it will run, but you might not have access to SD card or camera. If not, find out if there is a GEE/b kernel you can flash afterwards or if the OP can create a GEE/b kernel since it looks like it has a new kernel, aside from any other currently available. I know I've never seen UnityMod kernel anywhere.
To the OP, if you ask any of the other kernel devs what changes they made to produce a Gee/b kernel of the same settings I am sure they would provide some advice.
EDIT: some changes may be necessary in the build.prop as well to allow access to GSM.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
LiquidSmokeX64 said:
Ok. I am the OP BTW. Founder/Creator.
The UnityKernel cannot be found. It's the major unique feature of UnityROM-2. How it is done is quite simple. To me. But I remember when I had this phone. How badly it needs a good stable ROM. Just like jewel did till I did this.
So trying to do y'all a favor lol. The best ROM for Evo LTE now coming to the next Sprint "Problem Device".
Click to expand...
Click to collapse
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
EDIT: Don't really want to be part of this thread anymore and I haven't said anything useful
LiquidSmokeX64 said:
Please anyone who downloads the test. Report back. Then we know if we are going to continue our work here or not
Click to expand...
Click to collapse
You did a great job, it works fine. I think you should continue to work on perfection of Rom. As far as I understand, you need to go to another forum thread(Optimus G Original Android Development). When using the camera - got two crashes . everything else works perfectly, quickly and smoothly! Antutu received 20673 balls without my optimization. Thank you for a wonderful job. I know little about it, but it seems to me that all is well. This gproj or aosp based? You use the new driver for the camera? Excuse me for my english.
Well thanks for the feedback. I'll run 2.7.0 for LS970 now. Tons of new things added for the build and kernel
dopy25 said:
I saw you were the OP, that's why I quoted you too LOL. No worries. Thank you for building this ROM. I haven't tested it yet because I am working on getting the G3 port to work on our Sprint OG. But I am happy to check it out. I just wanted to let you know that you can build the geeb kernel too. I don't think it takes much, I think only adding or switching a branch for your build.
Also, if you created this ROM and built from sources, you might want to think about having this thread moved to Original Development instead of Development. This one is more for ports and changes to an existing rom in order for it to work on our phone. The new Roms and creations should go in the Original Development.
Click to expand...
Click to collapse
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
+1 would also want a geeb kernel for this.
dr3adl0ckd said:
interesting.. @LiquidSmokeX64 let us know if you do the geeb kernel def anxious to try this rom out!
Click to expand...
Click to collapse
Well if I knew what I need for geeb I would gladly make it for you guys. I just grabbed the stuff listed in CMs LS970 device cm.dependencies file.
I can always add more or a new defconfig file to have it look at while building. Either way will work
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
Yes sir!
LiquidSmokeX64 said:
If I can get my net to cooperate, I have 2.7.0 ready and attempting to upload.
Y'all ready for this?
Click to expand...
Click to collapse
with impatience [emoji14] [emoji14] [emoji14]
Vadik56 said:
with impatience [emoji14] [emoji14] [emoji14]
Click to expand...
Click to collapse
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
LiquidSmokeX64 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Fully featured now with all my normal modifications.
Yes Google apps are built-in... technically...
The separated internal directories make it OK to do this legally.
Enjoy everyone
Click to expand...
Click to collapse
Thank you, download started. I feel will be a bomb-)-)
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment cm-UnityROM-2-v.2.7.0-ls970.zip.log.txt
Vadik56 said:
UnityROM-2 v.2.7.0 has arrived and is now posted
Installation fails
View attachment 2974972
Click to expand...
Click to collapse
Looks like you're flashing for the wrong device, or wrong recovery.
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.