[ROM][All Quarks][7.1.2_r29][OFFICIAL] AospExtended ROM V4.5 [OMS/DU][15-08-2017]

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,326
14,179
253
Atlanta, Georgia
guys, split screen problem = do not flash Kernel BHB's BHB27! It may cause instability! trust me, I f**ked up myself when I flashed another kernel! :( pls guys use Dev Marsh's original kernel! cya :)
@Scrluiz, please educate yourself before you embarrass yourself.

1) Dev Marsh doesn't have a kernel. It's the same kernel @bhb27 coded for all Quark ROMs.

2) @bhb27 also has an advanced custom kernel, with lots more options as a standalone download/installation. THAT is what you are saying not to use. And plenty of people are using it with no issues.

But to reiterate you are REALLY saying "don't use @bhb27's kernel -- instead use @bhb27's kernel". EVERY kernel on every custom Quark is coded by @bhb27. It's the simple "stock" CM/LOS kernel used in all custom ROMs. It was originally coded by CM dev @Skrilax_CZ for Quark ROMs, but then that work has been taken over by @bhb27.

3) the split screen problem was long solved by @bhb27, by the way. TWO MONTHS AGO. This dev had not yet implemented the fix in this ROM it seems, on the version you are running. He says he would on April 11, and he released an update on that day.

April 11, 2017
I'll try to fix these bugs in today's update!
Do you have the April 11 ROM update with the fix -- or are you running an older version of this ROM?


If you are running the older version still, you can apply the fix yourself if you bother to read back a few posts.
https://forum.xda-developers.com/showpost.php?p=71778565&postcount=28
 
Last edited:
  • Like
Reactions: Hlcpereira

Scrluiz

Senior Member
Feb 18, 2016
70
13
0
26
Praia Grande, São Paulo
@Scrluiz, please educate yourself before you embarrass yourself.

1) Dev Marsh doesn't have a kernel. It's the same kernel @bhb27 coded for all Quark ROMs.

2) @bhb27 also has an advanced custom kernel, with lots more options as a standalone download/installation. THAT is what you are saying not to use. And plenty of people are using it with no issues.

But to reiterate you are REALLY saying "don't use @bhb27's kernel -- instead use @bhb27's kernel". EVERY kernel on every custom Quark is coded by @bhb27. It's the simple "stock" CM/LOS kernel used in all custom ROMs. It was originally coded by CM dev @ Skrilax_CZ, but then that work has been taken over by @bhb27.

3) the split screen problem was long solved by @bhb27, by the way. TWO MONTHS AGO. This dev has not yet implemented the fix in this ROM it seems. He says he will.

April 11, 2017


He hasn't yet, but says he will.

You can apply the fix yourself if you bother to read back a few posts.
https://forum.xda-developers.com/showpost.php?p=71778565&postcount=28
I'm sorry if you did not understand, but what I meant was that you should give it a try and use the Dev Marsh's kernel (I know it's based on bhb27) but I've had problems flashing over the Dev Marsh kernel, more than once. And I'm sorry if you misunderstood. Have a nice day! :)
 

Scrluiz

Senior Member
Feb 18, 2016
70
13
0
26
Praia Grande, São Paulo
Man it's only edit the build.prop as me and @ChazzMatt have been showed here a fill days...
sorry bro, I've just seen your post, only now :good:

---------- Post added at 08:54 PM ---------- Previous post was at 08:53 PM ----------

Man it's only edit the build.prop as me and @ChazzMatt have been showed here a fill days...
sorry bro, I saw your post, only now :good:
 
  • Like
Reactions: Hlcpereira

ChazzMatt

Recognized Contributor
Nov 30, 2010
18,326
14,179
253
Atlanta, Georgia
I'm sorry if you did not understand, but what I meant was that you should give it a try and use the Dev Marsh's kernel (I know it's based on bhb27) but I've had problems flashing over the Dev Marsh kernel, more than once. And I'm sorry if you misunderstood. Have a nice day! :)
I DO understand what you mean --but you are WRONG. That is what YOU need to understand. Read carefully!

1) DevMarsh does NOT NOT NOT NOT NOT have a kernel. He has ROMs, period. In both his ROMs he uses the same basic @bhb27 coded kernel from the CM/LOS tree all the Quark custom ROMs use.

Here, go read this post from his other ROM thread where it's explained and Dev Marsh agrees:

SAME KERNEL IN ALL QUARK ROMS
https://forum.xda-developers.com/showpost.php?p=71828888&postcount=12

Dev Marsh has never coded a kernel, does not offer a kernel. There's nothing wrong with that. ROM work is different from kernel work. ROM features are different from kernel features. This ROM can be GREAT, while still using the same basic kernel every other Quark dev uses. Dev Marsh merely uses the same kernel every Quark dev is using for every Quark ROM. THAT kernel is actually currently coded by @bhb27.

So, in your incorrect post , what you are saying is to use the basic @bhb27 kernel (from CM/LOS tree) that comes with the ROM, and not to use the advanced custom standalone kernel @bhb27 also offers. What you probably MEANT was "use the ROM kernel, not @bhb27 super duper advance standalone kernel". But you called it a "Dev Marsh" kernel, which is incorrect.

But even then you are WRONG, if you are saying the ROM kernel will solve the problem you are describing.

2) Your problem is not a kernel issue but a build prop issue. Dev Marsh fixed it on April 11, but you are running an older version of the ROM apparently. This split screen issue appeared in all the Nougat ROMs a few months ago and @bhb27 fixed it, and all the other ROM devs applied it to their ROMs too at the time. For some reason it has now appeared AGAIN in THIS ROM.

But Dev Marsh released an update on April 11 to fix it. If you are seeing that problem, has nothing to do with kernels but it's because you are running outdated version of this ROM. There's also a manual fix you can do, if you don't want to re-flash newer version of this ROM right now.

_________

Now having said that, on RR 6.X I run "stock" kernel. I do not run the custom @bhb27 kernel. Last time I tried for both mine and my wife's phone, hers had random reboots. That was back on Lollipop when we were on CM12.1. Mine phone was fine, hers had problems with that highly customized kernel. Whatever it was, may have been fixed since then! My goodness, over a year ago! And a different Android version. But I still didn't tell people "don't use that kernel!" -- just because one of our two daily phones couldn't handle it. Every phone is different. Lots of people run @bhb27 kernel and love it. Works great on their phones.
 
Last edited: