I have test many roms but still slow, can someone create a kernel maybe for marshmallow for speed!!??
Related
I have seen to many kernel threads and none of them seems to say that the kernels are safe to use with the JB leaks.
I really don't see why they shouldn't, but I really wanted to be sure.
have anyone used a Franco, faux or similiar present kernel with the new JB leaks from Insert Coin or ARHD?
Do we have to repack them to be fine?
I know that kernel version should not be a problem, but we only have source code for the ICS kernel based in 2.6.X and the new kernel is 3.0.X
So I wanna know real experiences if possible
Thanks,
Santroph.
Hi, i have tried repacking a few of them as im keeping a list up together for the maximus thread but none of the linux 2 kernels have worked yet, will try trips kernel when i get round to it this week but it says no support for sense so probably a no go. I havent seen anything new yet but will keep my post updated as and when (link in my sig) they should work for other jb sense 4+ roms too :good:
Now that lollipop has officially been released to AOSP, do we still need to wait till LG releases their source code merged with Android 5.0 ? Or can devs simply grab it and compile from googles source code ?
Probably won't be able to get much functionality (i.e., it won't work!) until LG updates the hardware drivers.
Yeah.... I just mentioned this in another thread.... Any custom LP ROM that gets shared will be a hybrid.... Android LP built on top of LG's KK stuff (kernel, modems and drivers).
Not saying that it can't be done, but I would expect some issues... My only seat time with a ROM like that was running Kitkat builds for my Galaxy S3 back when KK was first released. If I went a day with only a couple of reboots, I was lucky (every time it switched from WiFi to mobile it would panic boot, for instance). And that was just a 'minor' upgrade (4.3 to 4.4).....
The unofficial CM rom is working really well for me and it is still in alpha. I think by December we should have some pretty stable 5.0 AOSP roms.
The Pac 5.0 rom is very stable, the only thing I found wrong with it was the IR Blaster
Hello Devs,
I think the new Lollipop version is great but at the moment we only have CM12 ROMs for our S4 Mini. Can someone of you build a pure AOSP Lollipop ROM for our device that other dev's can use as base for other ROMs? I do not like CM and at the moment I'm using SlimKat but it looks like there is no update to SlimLP in the next days so it would be great if someone can build a pure AOSP LP ROM.
I would do it for myself but I have no experiance in ROM development. I found this thread but I'm not sure how to add our device. Also I found this and this repo on GitHub but I do not know which from them (or maybe both?) I need to compile the ROM or if I have to change something on them because they are for CM and not for AOSP. It would be great if someone can teach me these steps because this is often my problem when I try to learn something about Android ROM developemnt.
Yours sincerely
Cilenco
Cm12 at the moment is just aosp, give it a try it's very good
hey guzs,
can someone build a custom rom based on lollipop when has no bugs in it every thing will work fine .its like dream come true..
So I've tried all the ROMs, I've tried Stock (When I first got the phone) I then tried CM12.1, then FlexOS, then back to CM, then BlissPop, then back to CM, then Cloudy's ROM, then Back to c-... you get the idea.
I looked in to trying to compile my own kernel, because frankly there isn't an updated d855 CM12.1 kernel to be seen anywhere that has features to make CM the least bit smooth and I decided that with my coursework becoming a bigger part of my life that I would simply have no time to put in the work (Or the knowledge).
So what I'm asking is simple, can someone please compile a custom kernel for cm12.1? I love this ROM, the lack of customization features is a feature in itself for me considering I love AOSP, CM is perfect for my usage but I just need a custom kernel so that it can be complimented and optimized for the G3, thanks.