[Android General] 7awliet:
Attention To Language And Findings

He specifically asked for a

workaround

(see green text below).

Also, many of the questions asked in the last few pages of this thread - I answered most of them in post #807 (

PLEASE READ THE FULL POST (#807) FOR MORE INFO.

):

Furthermore, Qwerty, this one is to you: I really don't mean this in a spiteful way or anything, but, some of the advice you're giving can lead to some people's problems in understanding. It's not what you mean to say but rather how you are saying it. English may not be your first language but it can be a little difficult to make out the specifics sometimes. For example, when you say that "you can do [so and so] but it'll brick your phone" or "you can wipe [so and so] but it's not necessary", these can be quite indecisive. Many of us are new to this thing and many who are experienced may be new to this phone, so if doing something will lead to bricking their phone then perhaps you should say "don't try that, it'll brick your phone" instead, rather than say they have an option.

I understand that you use the

literal

definition of the word "can", for example when people ask "CAN I do [so and so]?", and you do answer correctly like "You CAN do [so and so] but..." - however, a little compromise from formal speaking to colloquial talk can be beneficial to many (for example, I just said "formal speaking" instead of "formal writing", because you write on a forum and not speak, but you still understood that because it is common talk - this is what I mean).

I really do appreciate that you've put a lot of effort into this thread and elsewhere and I appreciate you trying with kernel 3.10.54. For now, I gave my friend RR 5.6.8 (K-3.4.67) and she really likes it but I'm still working with K-3.10.54 to see what I can find out. I, too, have the same method as you when trying to port K-3.10.54 so it's good to know that we're on the same page there :)

I've still not received a reply from Ajit yet and as I don't have a Facebook account all of my questions and queries are still unanswered:

So I've been doing a lot of research myself but there's so much to take in.

babi, any chance you (or anyone reading this for that matter) could ask Ajit on Facebook for the Vendor Tree and Device Tree that he uses for MT6582, please? Or if he won't share them, where we can get them from? Or at least which device model's trees he is using? It would be so much help; thank you in advance.

Yeah, another thing I already answered in post #807 (see red text above). We may ALREADY have MM 6.0.1 on K-3.10.54, but we can't be certain (I've already said how we can find out).

The thing with people putting "kernel version 3.10" or "3.10.XX" or not telling us the kernel version at all, leaves us with no clue whatsoever. The Sublevel version number (.XX) could be anything from 00 to 99 or even 102 - a total of 103 possible answers.

Take this for example, we already have the full official Marshamallow MediaTek source code for MT6582 ROM and Kernel (albeit for sprout type devices):

https://android.googlesource.com/kernel/mediatek/+/android-mediatek-sprout-3.10-marshmallow-mr2

But if you take a look in the Makefile, you will see from the first 3 lines that the kernel version is 3.10.57, not 3.10.54:

https://android.googlesource.com/ke...mediatek-sprout-3.10-marshmallow-mr2/Makefile

Now we can either compare kernels 3.10.54, 3.10.55, 3.10.56, and 3.10.57 and see the change log for the patches that were made to to those kernels (3.10.55, 3.10.56, and 3.10.57) and apply the same patches to our MediaTek kernel source code when compiling (which isn't too hard because you only use the latest patches (i.e. skip .55 and .56) I think), BUT THAT WOULD BE IF WE WERE COMPILING FOR DESKTOP Linux and not our MT6582 kernel.

So instead we have the option to compare the differences between our 3.10.54 and that 3.10.57 and make the appropriate adjustments, while backing up the newly ported kernel into a separate folder everytime we replace ONE LINE or one file, just to be safe and truly know what adjustments our stock Lollipop (S124) will allow and not allow (will it boot or brick). Meaning we'd have to compile and flash after every adjustment to find out. Now if there were 5 of us actively working on this, it might be feasible... but unfortunately we're 3 blind mice following each other. I've only researched this phone a little over a week and found so much, yet I can't seem to get Ajit's VTs and DTs, because that would mean we would have RR 5.6.8 and 5.6.9 (and soon 5.7.0) with working GPS and band-aid-fix VPN in about a week's work.

OR we can - and as a way to illustrate the work, effort, and time, that our project would take - read through http://xdaforums.com/showthread.php?t=2274332 and have a MM 6.0.1 K-3.10.54 (or 3.10.99 or even the max. 3.10.102 if you wanted) ROM by the end of it. Any takers? :silly:

For the 4th time mentioning this, I've already said in post #807 how you can all really help out (each other) but I dunno how many of you are willing to do so.

I want to make clear though that I really do appreciate everyone finding little tidbits of information here and there, it all really helps out and adds up, so thank you for that. Again, nothing personal towards anyone about anything.

I appreciate it.