Related
Can you rom devs help us MDDI KERNEL users to just update your ROM version that is currently compatible for our device?
Example:
Like PACman v20.0.1(the last pacman rom that is compatible to MDDI kernel). maybe you guys can update some little apps , libs, modules that will still be compatible to MDDI kernel. just to reduce some bugs or just to catch up from the latest versions?
we can handle the brightness bug by installing an app that reduces contrast that in turn reducing the battery use by a little.
Hi guys. I've been following both the android and original android development sections of the OPO forum and have found no kernel that can overclock the OnePlus One running stock (rooted and BL unlocked) CM11s.
So, my question is very simple: is there any kernel that overclocks CM11s? (Yes, i know it is plenty fast already, the only purpose i have for it is bragging rights at the bar TBFH and to see how far it can go)
There is currently no custom kernel with overclocking features that will boot on CM11S.
If you really want it then you can go and flash a custom ROM and flash a kernel such as ak kernel which does have overclocking up to 2880MHz.
Do not flash ak kernel while on 11S, your phone will not boot.
zephiK said:
There is currently no custom kernel with overclocking features that will boot on CM11S.
If you really want it then you can go and flash a custom ROM and flash a kernel such as ak kernel which does have overclocking up to 2880MHz.
Do not flash ak kernel while on 11S, your phone will not boot.
Click to expand...
Click to collapse
Thank you for you answer. Yes, I realize it wont boot on CM11S. infact, that is the first warning you read upon seeing the kernel.
I guess I will have to wait, since I think CM11S is by far the best ROM for the OnePlus... I had already installed 5 different roms on it and flashed furnace kernel only to see no difference in benchmarks (i think it's because it throttles, even though i stuck it in the cooler)
badjoras said:
Thank you for you answer. Yes, I realize it wont boot on CM11S. infact, that is the first warning you read upon seeing the kernel.
I guess I will have to wait, since I think CM11S is by far the best ROM for the OnePlus... I had already installed 5 different roms on it and flashed furnace kernel only to see no difference in benchmarks (i think it's because it throttles, even though i stuck it in the cooler)
Click to expand...
Click to collapse
Benchmarks mean absolutely nothing. Its all about day-to-day performance. Custom ROMs are better in my opinion because currently on 11S there are numerous crucial bugs that are affecting the phone from being used. Just to name some,
- In-call audio volume fixed.
- Some workarounds on the touchscreen problem.
... the list goes on and on but I don't feel like explaining all of them but custom ROMs offer a lot more features than what stock has to offer plus they give you a sneak preview of whats to come in the next OTA without having to wait for it.
The decision is up to you, they're all free after all. Thats the joy of custom ROMs and kernels
Hello, I wonder if I should install a custom rom and what to install, possibly stable and continuous updates. I have the XT1541 variant.
What do you recommend? Thank you and sorry if there are already similar post.
Welcome aboard, we have cookies here Probably you should start with the CyanogenMod. It's good for starters, it's stable and has great features. You get nightly updates (updating once in a few weeks or in a month is fine). Then you can move on to other projects.
As you are new to the custom rom world, I would recommend you to have a fastboot flashable firmware for your device variant handy, just in case.
Guide to flash stock firmware - http://forum.xda-developers.com/showthread.php?t=3187750
Index thread for stock firmware images - http://forum.xda-developers.com/showthread.php?t=3169639
Guide to obtain root access (custom roms are usually pre-rooted) - http://forum.xda-developers.com/showthread.php?t=3448572.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
Welcome aboard, we have cookies here Probably you should start with the CyanogenMod. It's good for starters, it's stable and has great features. You get nightly updates (updating once in a few weeks or in a month is fine). Then you can move on to other projects.
As you are new to the custom rom world, I would recommend you to have a fastboot flashable firmware for your device variant handy, just in case.
Guide to flash stock firmware - http://forum.xda-developers.com/showthread.php?t=3187750
Index thread for stock firmware images - http://forum.xda-developers.com/showthread.php?t=3169639
Guide to obtain root access (custom roms are usually pre-rooted) - http://forum.xda-developers.com/showthread.php?t=3448572.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
What do you recommend Cyanogen moto g 2015? After it has flashed I have to use another kernel? if so, what is the best?
I already have the 6.0.1 because of the touch screen bug. I have not the root, but do not know what benefits would result.
if I Root the phone what can I do?
Giovanni9921 said:
What do you recommend Cyanogen moto g 2015? After it has flashed I have to use another kernel? if so, what is the best?
I already have the 6.0.1 because of the touch screen bug. I have not the root, but do not know what benefits would result.
if I Root the phone what can I do?
Click to expand...
Click to collapse
There's no need to flash a custom kernel, unless you feel like your device is lacking on performance and hardware features. I recommend you to try CM13 with the bundled kernel and when you get the hang of it you flash one.
P.S: Custom ROMs have fixed the touchscreen issues
Henriquefeira said:
There's no need to flash a custom kernel, unless you feel like your device is lacking on performance and hardware features. I recommend you to try CM13 with the bundled kernel and when you get the hang of it you flash one.
P.S: Custom ROMs have fixed the touchscreen issues
Click to expand...
Click to collapse
I saw that there is also the 14 (based on Android nougat) this better or at least the 13.1?
Sorry for my bad english, but i translate all with Google translate
Giovanni9921 said:
I saw that there is also the 14 (based on Android nougat) this better or at least the 13.1?
Sorry for my bad english, but i translate all with Google translate
Click to expand...
Click to collapse
Haven't tested CM14.1 yet
Giovanni9921 said:
What do you recommend Cyanogen moto g 2015? After it has flashed I have to use another kernel? if so, what is the best?
I already have the 6.0.1 because of the touch screen bug. I have not the root, but do not know what benefits would result.
if I Root the phone what can I do?
Click to expand...
Click to collapse
1. Custom roms include their own (custom) kernels so flashing standalone custom kernels is purely optional.
2. You can try both cm 13 and 14.1, cm 13 is the marshmallow release and 14.1 is nougat one. Even being new, cm 14.1 is stable so no worries here.
3. About root on android - https://en.m.wikipedia.org/wiki/Rooting_(Android_OS)
http://android.stackexchange.com/questions/236/what-does-to-root-a-phone-mean
http://m.androidcentral.com/what-does-rooting-your-phone-actually-mean
http://www.androidcentral.com/root
Broadcasted from Zeta Reticuli
Gravemind2015 said:
1. Custom roms include their own (custom) kernels so flashing standalone custom kernels is purely optional.
2. You can try both cm 13 and 14.1, cm 13 is the marshmallow release and 14.1 is nougat one. Even being new, cm 14.1 is stable so no worries here.
3. About root on android - https://en.m.wikipedia.org/wiki/Rooting_(Android_OS)
http://android.stackexchange.com/questions/236/what-does-to-root-a-phone-mean
http://m.androidcentral.com/what-does-rooting-your-phone-actually-mean
http://www.androidcentral.com/root
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
OK thanks. I saw that the motion g 2015 the 14.1 nightly on the cyano official website and here on xda that developed by alberto 97.
Which one should I download?
I would like the style options OP3, with much options and other tools.
Giovanni9921 said:
OK thanks. I saw that the motion g 2015 the 14.1 nightly on the cyano official website and here on xda that developed by alberto 97.
Which one should I download?
I would like the style options OP3, with much options and other tools.
Click to expand...
Click to collapse
You can use the latest CM 14.1 nightly. For even greater customizability, use roms like Resurrection Remix, Zephyr OS or AICP. Note that nougat is still a WIP, so you may want to stick to the marshmallow releases for a while.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
You can use the latest CM 14.1 nightly. For even greater customizability, use roms like Resurrection Remix, Zephyr OS or AICP. Note that nougat is still a WIP, so you may want to stick to the marshmallow releases for a while.
Click to expand...
Click to collapse
Yes, i know it. Thx much.
If i have another questions can i edit this post?
Giovanni9921 said:
Yes, i know it. Thx much.
If i have another questions can i edit this post?
Click to expand...
Click to collapse
You can create a new reply with your question, no issues
Broadcasted from Zeta Reticuli
Folks,
now that CM has started shipping cm14.1 nightlies (which I am not yet ready to go with as the device is my daily driver and some of the issues reported so far aren't things I can afford to run into on this device): Can anyone recommend which ROM to go with wanting to stay on the CM13 code / feature base but not completely being cut off from receiving any kinds of updates? Just stay with the latest cm13 nightly until cm14 has improved? Go for something else such as RR? ...?
TIA and all the best,
Kristian
As for other custom roms, they will most likely drop support (nearly all have, already!).
See here - http://forum.xda-developers.com/showthread.php?t=3386367
Broadcasted from Zeta Reticuli
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
https://youtu.be/RxoNMuIPQbw
jaaa1976 said:
Hello.. I would like to ask developers which file we need to replace for normal boot (not opposite) ..some custom rooms for nexus 6 boot on moto maxx xt 1225...please look video.
Click to expand...
Click to collapse
Thanks bro...
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
vinydasilveira said:
I already knew that, but the Custom ROM developers for Quark are too proud to use what already exists for Nexus 6 in Quark. They prefer to stay back and stay on the hard way.
Click to expand...
Click to collapse
You really have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
moto maxx (xt1225) running rom stock of nexus 6. totally unstable. stock 7.1.1
*Kernel AOSP - Quark (This is merely @bhb27 LOS kernel or his standalone, there is NO such thing as "Kernel AOSP -Quark")
*Stock 7.1.1
Click to expand...
Click to collapse
Why would we want to run something like that (unstable Nougat ROM) on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our Quark phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the Quark custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the Quark custom ROMs actually use the SAME kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that YouTube post means is someone took @bhb27 kernel code and managed to horribly port a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the Quark kernel.
The reason why "stock" ROMs are not done are because they are boring. You wouldn't have the LED notification for instance that @bhb27 created, nor all the options present in Revolution Remix and crDroid. Even @calsurferpunk's LOS ROM is more of a hybrid -- LOS + some of the more popular options in RR. We already HAVE up to date 7.x Nougat ROMs. And they run well. How many more do you want?
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
What people WANT are Oreo ROMs. The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
ChazzMatt said:
You have no idea what you are talking about. Did you even go to that link and actually read? No, you didn't or you wouldn't be making comments like that.
Why would we want to run something like that on our Quarks when we already have VERY STABLE Nougat custom ROMs? Why would we want to run UNstable 7.1.1?
Plus, whoever wrote that seemingly doesn't know what they are talking about either....
If it's "kernel AOSP - Quark" -- well, there's no such thing. That means it's @bhb27's kernel code. There is no "AOSP kernel" for Quark. Whoever wrote that doesn't know much about Quark dev work. No ROM can run on our phones without a compatible kernel, and @bhb27 has coded both LOS stock kernel and his own advanced standalone kernel (with more features, options). All the custom ROMs (including AOSP) use the LOS stock kernel -- which @bhb27 coded. All the custom ROMs use the same kernel.
If he had said "LOS kernel -- Quark", that would be more accurate. Or @bhb27 kernel".
You can even run @bhb27 kernel with Motorola Marshmallow stock. You don't need a custom ROM. It's a great kernel!
All that post means is someone took @bhb27 kernel code and managed to horribly run a Nexus 6 stock-based ROM over it. They didn't do any magic -- any more than any other ROM like RR, LOS, AOSP runs on Quark right now, with @bhb27 kernel. All they did was badly port a Nougat 7.1 "stock" ROM that they say is unstable. Whoopee.
I'm all for more ROMs, but you need to understand how ROMs are made -- they are built on the foundation of the kernel. ANY Nougat ROM can be ported to our phones, as long as you use the right kernel.
The the only reason we don't have Oreo ROMs right now, because @bhb27 has to adapt the last kernel Motorola gave us (Marshmallow) to work on Oreo, the way he did for Nougat.
This Nougat ROM in this video is running on @bhb27 kernel code -- just like every other ROM we have. So, how is it any different?
Click to expand...
Click to collapse
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
vinydasilveira said:
Great. Amazing. You changed my mind ...
Now tell me. Why not use what we have from the Oreo of the Nexus 6 to advance the Oreo of the Maxx? Because the Nexus 6 devs already have Oreo 8.1.0 running on Nexus 6. When I talked about standing back and doing the hard way I was referring to that.
Click to expand...
Click to collapse
It's about the kernel. The kernel is the foundation of all ROMs. You notice the YouTube video is merely a Nexus 6 NOUGAT ROM that doesn't run well on Quark. Because we have Nougat compatible kernel right now.
@bhb27 actually said he is using some of the Nexus 6 stuff for CLUES to adapt the Quark kernel for Oreo. But it's not easy. Until you have a compatible kernel, no Oreo ROMs will run on Quark. @bhb27 has actually gotten Oreo Resurrection Remix to run on Quark. Have you not seen the screenshots? But at this point it's still unstable.
Once you have a kernel, you can have 100 Oreo ROMs on Quark in a week -- if you find 100 people willing to port the ROMs. It's almost plug and play (for dev maintainers who have those skills). This is why we have had so many "drive by" ROMs dropped into this forum and then those people walk away without ever updating them. They were taking advantage of @bhb27's kernel work. Take ROM, plug in kernel, done. But they never stuck around to keep them updated, or even test them thoroughly, and some didn't even own a Quark phone. One of them even used @bhb27's advanced standalone kernel (not his LOS stock kernel) in their ROM without his permission, so it made their ROM seem better than the other ROMs. It's the same kernel anyone can download and install themselves, but @bhb27 wants you to install that one yourself as it's more complex. He doesn't want it installed as a default kernel -- he doesn't include it in his own ROMs.
He's working on an Oreo-compatible kernel but while everything about Moto Nexus 6 is open source (thanks to Google), it's not the same with Moto Quark. Yeah, even LG Nexus 4 has Oreo, but again, it's totally open source so easier to adapt.
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
about the video posted on my channel, I just made a joke at home. I know the limitations, I know the hardware is different. it was only a joke of those who do not have much knowledge, but search knowledge, the kernel used is a custom ROM 7.1.1, I did not say that the kernel is stock 7.1.1.
I admire the work of the developers, when I use a custom ROM, I can imagine how much work it has done to make it functional with few bugs. :good:
---------- Post added at 04:25 PM ---------- Previous post was at 04:21 PM ----------
bhb27 said:
Replying the OP, theoretically what is needed is:
remove the checks from the zip regarding if the devices is Nexus 6, and after installing the ROM flash a compatible kernel, and the thing may boot like that.
But is a lost cause, the only thing similar with MAXX and Nexus 6 is the cpu/gpu and Motorola build it.
All the rest is not compatible, chipset, audio, video, wifi, radio, all the firmware, etc and etc is different, there is too many hardware diference for things to work.
And all of those are supported in a combination of ROM + kernel.
The source to build for Quark and for any AOSP device is not the same, yes is all on the same main Repo but the files used are not the same, that is way it device has it's own configuration/recipe and separated sources files inside the main Repo source.
The only reason way any AOSP device have updates easier is just like Chad wrote, they have all the sources files released, plus the AOSP source is made to be used with AOSP devices, so they need to make very little changes when google releases things to build a working ROM for they devices, plus there is literally hundreds of developers building for AOSP devices simply because is that simple anyone can build and help.
On the oppose to none AOSP devices were there is only a few developers as things are very hard because we don't have sometimes a clue in what to do, as we don't have the devices source, google changes the source on a way that only works with AOSP devices, so after a new OS is released a lot of things is need to be made from scratch.
If any one think is simple to build for any device just go for it, instead of be criticizing and posting none sense about thing you don't now how works.
Click to expand...
Click to collapse
perfect explanation... I admire your work