[AQUA] Two different "submodels" on D2403 topic

Two different "submodels" on D2403D2403

I have to give credits to @linuxct who was who discovered this. I'm feeling in the obligation to create this post, because aqua users could be confused tinkering with their aqua: installing roms, recoveries, and other things...

I'm sure that someone who is reading this, has been tinkering with his aqua, and knows that is not an Xperia M2, is an Xperia M2 Aqua. Something are changing between M2 and M2 Aqua (Hardware).

Ok,but, if I tell you that there are two different models under D2403? That's the @linuxct discover. During the manufacture of D2403, there was two different periods: old period, and new period. And what is the different? Simple, the accelerometer. Old period aquas has the same accelerometer as D2303, and the new period has a different accelerometer, and this is causing errors while installing custom roms, or recoveries.

So, what's happening? Because there are two different accelerometrs, the "event" number are changing. The "events" are the numbers which corresponds with a determined action. For example, "event6" = gpio-keys (vol- and camera button).

On D2303 devices (And old period D2403), the "event6" are the gpio-keys, those are the keys whereby we can enter to the recovery. But in new period aquas, the "event6" is not the gpio-keys, it's de accelerometer. In new period aquas, the gpio-keys are in "event7". And that's why is causing problems in recoveries. If the recoverie says that: event6 detect = enter recovery, we will never enter to the recovery, because event6 in new aquas is other thing, and not gpio-keys, wich we need to enter recovery. We can push camera or vol- buttons all day, but we will never enter on it.

Because new period aquas has other accelerometer, it will produce bootloops, because the driver changes. That's why (for me) is not working Omni, and is not working CM12.

I think that's all. Sorry for my bad english, but is difficult to explain this in other language :(. I will update this thread shortly ;)