Here's a quick question for the devs - I've noticed, since I use a Galaxy Note 4 - that in our thread, we have CM12.1 and CM13 - trouble is, CM12.1 is NO WHERE NEAR READY FOR DAILY DRIVER USE - so why the hell is anyone trying to put 13 up? Wouldn't it make sense to finish one first, instead of leaving half of us users with a half-finished ROM in pursuit of something bigger? Fair enough, it's a title to be the first with a new rom for a device, but seriously? I've been sitting here downloading 200+Megabytes DAILY to be able to TRY and use my phone with a custom ROM... What's so difficult about finishing one ROM before starting another? Merge all devs together on one type of ROM for a device, then tag-team all the other ROMs in a thread up to scratch? Might be an idea so we have multiple ROMs fully finished for many devices, then we can look into dual or even triple-booting those devices... Just asking - thoughts?
Related
OK, so here's the thing... I'm kind of new in the Android acknowledgement, so I hope that here will be the place where I will get my answers. So here's what I know...
At first I didn't know that Android was Java-based, using a modified Linux kernel which we all know it's C-based (entirely). After a while, I found that there were different firmwares (ROMs) from the original ones, called Stock ones and also different kernels. After reading lots of info about how things actually are, I've decided to root my stock and then I moved to a custom MIUI for my SGSII with a JB implementation. At first it was great, but I had some issues which left me disappointed. Then I moved on to the official MIUI (China - English one). Things got better after I got used to it. The major bugs disappeared, only small ones left and a few crashes, but in time most of them got fixed. Later it crossed my mind, "Why are there so many different kernels and which is the best one for my phone or ROM to be precise?" Well this is where I need your help. I've read some topics that siyah kernel is probably the best kernel, which fits the MIUI rom. The pointing of concrete kernels isn't the kind of answer I was actually searching for. To be honest, I need answers to questions like:
How many kernels are there ?
Which ones are safe ? (I've read that there are badly written ones, so yeah, it needs to be asked)
Statistically, which is the best kernel and is it for the MIUI rom ?
How can I tell that it's suitable for the MIUI rom ? (Since I've read that not all are)
What are the risks of changing the kernel?
How can you test the kernel's behaviour, an app which makes statistics in time or some other methods ?
Believe me, as annoying this topic might seem, lots of us (the newbie users) are burning up the google servers, just to find these answers. I'm really hoping for a reply spam with answers (if possible , spare the trolling ones). Thanks for reading my annoying topic, anyway
Since most of the source is available, basically anyone can build their own kernel at home, so it is hard to tell how many kernels are there.
what isn`t available as open source are most of the OEM-specific drivers. Samsung, for one, doesn`t make most of the drivers' source publicly available, so kernel developers have to make a binary kernel around the binary drivers and literally pray their work well together.
Siyah is safe, but I prefer the stock kernel (I like the stock ROM... go figure). The stock kernel is the only one that is sure to work properly with all the hardware in the phone, because it is the only built from sources for the drivers as well (read my previous paragraph).
Which ones are safe (other than stock and Siyah): you gotta try them for yourself, read other users' remarks and feedbacks, and so on.
Risks:
Very low. As long as the bootloader is good, if the kernel totally malfunctions, just reboot in download mode and flash something else.
Some app may work very well in one kernel and bomb in another. It may crash in some kernels. It is very empyrical.
The problem is that custom kernels don't undergo the same type of quality testing as stock kernels. Developers have very limited resources to do that, and some developers are more interested in having a short time-to-market than a quality product (well, many large corporations act like that as well). At the end of the day we - power users - are the beta testing and quality assurance teams for the kernel developers.
Out of curiosity i have been compiling CM10.2 for the last 2 days, and it now compiles successfully 100% (after many repo sync), but the thing is, when it's installed it doesn't even go past the S4 Bootlogo.. that's just sad, it's like the init file (ramdisk) is wrong so I tried the one from the aosp 4.3 ge builds, but that also didn't work, but it's probably not that. I don't know what it is, but of course without any logcat it's hard to find.
even my AOSP 4.3 compiled build went further than that.. it just showed me a black screen cause of the wrong egl libs but it showed a logcat at least. with the major errors of libc being faulty etc. (but it went further than CM.. in the early stage when there were almost no cm patches for cm10.2 yet)
Oh and yes I did include the proprietary files, and found that some of them don't even exist on the original 4.3 rom, so that's kinda lame..
here are the missing ones:
lib/libqmi.so
lib/libqmiservices.so
lib/libqmi_cci.so
lib/libqmi_common_so.so
lib/libqmi_csi.so
lib/libqmi_encdec.so
lib/libqcci_legacy.so
lib/libqmi_client_qmux.so
lib/libreference-ril.so
lib/libril-qcril-hook-oem.so
lib/libsecril-client.so
lib/libtime_genoff.so
lib/libWVStreamControlAPI_L1.so
lib/libidl.so
lib/libivxdrm.so (was spelled wrong by cm, it includes capitals)
that's a lot of libs, does someone know if one of them could be responsible for not going past the boot logo?
I can upload my build if anyone wants it but it does nothing so it's kinda useless
Any useful is appreciated very much! :silly:
just wait awhile..
xZain69 said:
just wait awhile..
Click to expand...
Click to collapse
Yes I will of course, and I have no problem with that. I'm just curious what the reason is for it not to boot at all. I want to learn as much as possible about the android system so that includes this
kernel problem ?
show this
http://forum.xda-developers.com/showthread.php?t=2348733
Syncing CM10.2 Sources now
Most of the low end devices have got 4.3 booting like HTC Pico and Optimus L5 etc.
PS: In HTC Pico CM10.2 Rom only BT and Camera is broken so I am sure we can get a fully stable one in a few tries. Obviously, we have to fix bugs
This thread over here at m919 has got cm10.2 working, well sort of. Check this out. http://forum.xda-developers.com/showthread.php?t=2348733
~~~~~~~~~~~~~~~~~~~~~
I am always on the mobile app and am always 'trying' to help others and moderators on the forum and learning something new everyday. I make stupid posts sometimes, but I never repeat a mistake more than once. I may not be a developer, but I know alot of stuff, so feel free to messsge me any questions and I'll be happy to answer them to the best of my ability.
~~~~~~~~~~~~~~~~~~~~~
I'm starting a video game company with my friend where we will be making Android games. message me for more info or go here: http://forum.xda-developers.com/showthread.php?t=2290843
got it working
So it has been a long time in the works and feels like have been working on this forever. First it was an AOSP Rom, then Caf and at some point both. For now the Rom is AOSP 5.1.1 based.
Is still not 100% but have decided to just go ahead and post the Rom and improve and update.
If you have seen the Test Flight CM based version that had been posted with the Starship Kernel the overall theme is pretty much the same.
The mission now is to first go over a few parts of the theme that bug me or did not translate well in the CM to AOSP Transition such as lightening up some text so is easier to read with darker backgrounds. Second mission is go over every APK one by one and fine tune the theme and add in any extra features. Will post an update as each APK has been completed. Most of the work is done in some form or another but have spent ages nitpicking everything to death and have an external drive filled with already completed images, Colour XML's and lots of uncommitted features so updates will come rather quickly. Honestly at this point am just going to start with the APK's in Alphabetical order so if you like the Rom and theme but a few particular things bug you just let me know and I will not mind jumping ahead. Also with each Rom update not only expect app and theme improvements but kernel and other system enhancements as most are already lined up and just need to be tested in the Rom's new incarnation. It has probably seen some better days but with my constant picking and changing have gone back and forth with so many things I think its best to just post so Starship is out there and now start finalizing. What is currently posted is bare bones themed and featuring a Kernel I have also spent almost a year working on. If you had used the Kit-Kat version of Starship then already know how fast the Rom will be improved and updated based on legitimate feedback. I know I am making things out like this is an incomplete Rom but have been using and been very happy with what is posted as my daily. Yes still need to improve a few things but the truth is I am never happy with anything I do and would have kept changing direction until Android N.
Until next time keep looking up!!
Installing
This version was not compiled using the new block based zip format so will take a bit longer when flashing the Rom. Just a warning for anyone who may think something is wrong. It Just takes a minute longer to flash.
Otherwise besides first performing the usual Wipe of Caches, System and Data also recommend flashing the Rom first, Gapps second and SuperSU last.
Downloads
Starship Rom
https://www.androidfilehost.com/?fid=24052804347762130
G-Apps
I recommend using the Banks 5.21.15 version of Gapps and have posted a link below. I don’t like reposting someone else’s work but just now discovered the 6.17.15 version seems glichy during the set-up wizard sometimes needing to be in landscape mode when making a selection so have reposted the version used during testing. Have also posted a link to the 6.17.15 version but found for example during the restore option selecting done will only register the selection in landscape mode.
BaNkS-dynamic-gapps-L-5-21-15
https://www.androidfilehost.com/?fid=24052804347762124
BaNkS-dynamic-gapps-L-6-17-15
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
SuperSU
https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
Kernel
I will continue keeping a separate thread for Starship Kernels that may update faster than the Rom so can keep a look out here.
http://forum.xda-developers.com/goo...t/kernel-starship-kernels-01-08-2014-t2997470
In staying with the Rules will find Source for the Kernel that is included here
https://github.com/Starship-Android/android_kernel_lge_hammerhead-starship/commits/lollipop
Starship Github
https://github.com/Starship-Android
Donations
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=MMEVCWUX83SXJ
I am not responsible for any effect using the downloads from this forum my have on any device and you download and use at your own risk.
Screen Shots
Okay, First of all, I know this is the incorrect place for a "development" thread, But I am currently unable to post in the correct area.. So here is the second best place.
I've had an idea. Since sadly I am gonna be giving back the Samsung Note 2 (Friend let me borrow it) I have to do something with the new Umi eMax I have.. Its a great potential phone but MEDIATEK wont freaking let us have the source code... So, Why not pull it off a rom? You can easily download something like ColorOS, Get the kernel, and extract the Source code, Am I not right?
I am wanting to do this because Umi has been sitting around barely doing jack trying to get the new 5.0 android up and running.. So installing CM 12.1 would be great!
This is probably totally impossible.. as I am a beginner at this kinda stuff, But, would this idea work or not?
I have the build.prop file if anyone wants to take a look at it.. Though we probably all know it runs off the MT6752.
So, Does anyone have any ideas? Or am I just getting completely over confident on this?
Trying to get 10 posts....
Hi! I have the Nexus5X and even though there are a lot of ROMs for the 5X, I don't really like any of them, so I was wondering how I would go about creating my own ROM. To start this off, I want this ROM to be a viable option for 5X users, a "legit" ROM, and I do not want to use a kitchen.
I do have previous Android building experience. Since I can do that, I want to know a couple specific things about making a ROM suitable for daily use.
First of all, how do I include the latest security updates from Google?
Secondly, how do I get OTA updates for my ROM(like AICP has an AICP OTA app)?
Thirdly, how do I know which revision to sync (r1, r2, r13) etc.
Fourth, are there any other things that I need to keep in mind when building this ROM and making it like other ROMs in the sense of stability, professionality etc (I can't really explain it, just that it's not simply someone adding random features)
Thanks