[ROM] MiniCM10-4.1.0 [RELEASED] [15/3/13]JB 4.1.2/CM10 for the Χ10 mini pro

[XepA]

@matmutant I totally forgot about that, Thanks anyway
@Trichelieu That's not what I was looking for but it's a good idea, maybe I'll do the same, Thanks

 

[Trichelieu]

@matmutant I totally forgot about that, Thanks anyway

@Trichelieu That's not what I was looking for but it's a good idea, maybe I'll do the same, Thanks

@XepA: Well actually I meant: "nope I don't think you can, here is alternatively what you can do:" ^^.
And you're welcome .

 

[belgianguy]

Thanks for the update! But I have an issue with the hardware keyboard. The phone is an Sony Ericsson X10 Xperia Mini Pro (U20i, mimmi), with an AZERTY hardware keyboard.

However, the AZERTY keyboard no longer functions correctly after the update. The regular letters (a-z, A-Z) still work, and Shift works as well.
But the Blue button and the Sym button no longer work. Their signals are still received by the OS (seen by printing KeyEvent.toString() in a custom App ).

This prohibits me from using numbers and symbols in an easy way.

I've read the MiniFAQ and tried both methods mentioned there without any luck, it seems to me that the latest version doesn't have any 'keyboard-config' folder in the 'usr' directory. I've even tried using my 'usr' directory from my backup, to no avail.

Is there a way to edit the keyboard configuration so that my AZERTY keyboard could once again use its Blue and Sym buttons?

I went digging around in the 'keyboard-config' folder of my backup and there I found a file called azerty.xml, which I presume took care of the button mapping of the Blue and Sym keys.

The file looks like this: pastebin.com/Zm53EWwS

But if it's no longer in use by Android 4.1.2, how would one add these button combinations back in?

Any help would be greatly appreciated!

 

[Trichelieu]

Thanks for the update! But I have an issue with the hardware keyboard. The phone is an Sony Ericsson X10 Xperia Mini Pro (U20i, mimmi), with an AZERTY hardware keyboard.

However, the AZERTY keyboard no longer functions correctly after the update. The regular letters (a-z, A-Z) still work, and Shift works as well.
But the Blue button and the Sym button no longer work. Their signals are still received by the OS (seen by printing KeyEvent.toString() in a custom App ).

This prohibits me from using numbers and symbols in an easy way.

I've read the MiniFAQ and tried both methods mentioned there without any luck, it seems to me that the latest version doesn't have any 'keyboard-config' folder in the 'usr' directory. I've even tried using my 'usr' directory from my backup, to no avail.

Is there a way to edit the keyboard configuration so that my AZERTY keyboard could once again use its Blue and Sym buttons?

I went digging around in the 'keyboard-config' folder of my backup and there I found a file called azerty.xml, which I presume took care of the button mapping of the Blue and Sym keys.

The file looks like this: pastebin.com/Zm53EWwS

But if it's no longer in use by Android 4.1.2, how would one add these button combinations back in?

Any help would be greatly appreciated!

When doing this:

9/ how can i fix my azerty/qwerty/qwertz... HardWare keyboard? (miniCM10-4.0.2+ ; mimmi)
first flash this : from here
and then the zip corresponding to your specific language : look here
/!\ choose "default input method" so that the KB works correctly, if you don't it will behaves strangely
/!\ do not modify keyboard_layouts and keyprints in any way if you want the above to work, edit: seems you can edit the xml finally
/!\ do not modify advanced>mimmiperts, make sure you have not touched it before processing the installs. it is recommended to start from a "fresh build" i.e. to wipe all user data, and so on.
defauld input and sym button should be back

You have to select the default input as virtual keyboard to make the physical keyboard work. It must be selected as default virtual keyboard. Sounds stupid, I know, and yet...
Flashing those files should create the folders you were searching for and the one I talked about before here:

You can edit azerty.xml or any other keyboard layout you can find in system/usr/keyboard-config/layout to bind the $ symbol to any key you want.
Ex: I edited azerty.xml to: "<key associatedShifted="$" associatedNormal="]" primaryShifted="D" primaryNormal="d" id="32"/>"
The key "d" does "d" when used normally. "D" if shift is pressed. "[" if blue key is pressed and "$" if both blue and shift keys are pressed.

Did this help you or I missed something?

Quotes, quotes everywhere.

 

[belgianguy]

When doing this:



You have to select the default input as virtual keyboard to make the physical keyboard work. It must be selected as default virtual keyboard. Sounds stupid, I know, and yet...
Flashing those files should create the folders you were searching for and the one I talked about before here:


Did this help you or I missed something?

Hi, got it to work!

First I retraced my steps, and did the first method again mentioned in #9.

I had set the input method to "Default", but I noticed that the checkmark next to AOSP keyboard didn't become empty, but was just grey.
To force the use of the "Default" keyboard, I had to delete the AOSP keyboard through the use of xdaforums.com/showthread.php?t=2094572" tool. (Do note that a spelling error in the program says "Delite AOKP keyboard", while it should say "Delete AOSP keyboard"). On reboot it only had the "Default" keyboard left and active.

After that, everything works as it's supposed to. I assume the AOSP keyboard wasn't transferring the keys correctly, and the removal allowed the Default keyboard to take over.

 

[Trichelieu]

Hi, got it to work!

First I retraced my steps, and did the first method again mentioned in #9.

I had set the input method to "Default", but I noticed that the checkmark next to AOSP keyboard didn't become empty, but was just grey.
To force the use of the "Default" keyboard, I had to delete the AOSP keyboard through the use of xdaforums.com/showthread.php?t=2094572" tool. (Do note that a spelling error in the program says "Delite AOKP keyboard", while it should say "Delete AOSP keyboard"). On reboot it only had the "Default" keyboard left and active.

After that, everything works as it's supposed to. I assume the AOSP keyboard wasn't transferring the keys correctly, and the removal allowed the Default keyboard to take over.

I remember being able to choose between the two of them, I don't know why you couldn't. I don't like this keyboard so I didn't try the new tricks to install it. May be the one you used was modified to block default input.

Glad I could help though .

 

[matmutant]

nightly

there is a new nightly available

please test and report about video recording and playback

 

[Ghorab]

Thank you,
i have update notification for version 4.1.2 , how can i update without losing App and ROM data ?
and how can i install stock keyboard [ SE keyboard ] support Arabic [QWERTY] ???

 

[allesand]

new nigthly has somtime a black Display bug !!!

 

[XepA]

I see that some people have trouble with Bluetooth, i have it too. It's not working, it won't turn on...
Does anyone know a solution?

Cheers

EDIT: Working now, i wiped phone and installed it again.

EDIT2: Not working again, it only worked once after i wiped and installed again...
Any solucions?

EDIT3: (hope it's the last edit ) I got it to work by following Trichelieu tip:

Rebooted with WiFi and bt activated (but no working, just pushed to on): bt was working when phone had rebooted

EDIT4: (I seriously need to stop this lol) File transfer worked, Bluetooth headset didn't work. I can't hear or be heard.

 

[allesand]

I see that some people have trouble with Bluetooth, i have it too. It's not working, it won't turn on...
Does anyone know a solution?

Cheers

EDIT: Working now, i wiped phone and installed it again.

EDIT2: Not working again, it only worked once after i wiped and installed again...
Any solucions?

EDIT3: (hope it's the last edit ) I got it to work by following Trichelieu tip:



EDIT4: (I seriously need to stop this lol) File transfer worked, Bluetooth headset didn't work. I can't hear or be heard.

turn firtst wifi on then Bluetooth now it works

 

[JozefSVK]

Best version, kernel is that?

Thank you.

Sent from my Nexus 7 using xda app-developers app

 

[JozefSVK]

Best kernel is nAa his. 32 kernel.

Sent from my LT22i using xda app-developers app

Thank you and which rom is the best?

Sent from my Nexus 7 using xda app-developers app

 

[isko95]

Thank you and which rom is the best?

Sent from my Nexus 7 using xda app-developers app

all them are ok!

 

[Taracair]

I don't have camera preview. I couldn't find any information about this in bugtrackers or known bugs lists. Is this normal?
I'm using latest nightly and latest nAa kernel.

 

[djtinxo]

nAa you are awesome man, I just have to use my x10 mini pro again and 1 year after you're still working on it. thank you!
BTW I wanted to ask if you're experiencing a heavy battery drain of the screen. I barely can use my device (beeing screen on) more than 1,5 hours, is that normal? not big trouble at all, just curious.
again, thank you very much.

cheers

 

[Jinghis]

Sorry to interrupt but I desperately need help

I've search so much about this problem, I don't have a clue where to start, so please don't skip this question meaning this is not belong here.

One day, when I was on wifi it went off, and then for a few day I turned on and off the WIFI and sometimes it worked some of them don't. Then after this a couldn't managed to acces to WIFI at all, just a gray ( or white ) WIFI simbol showing me: "I've been connected to the router, buuut not going to receive any data from router" ( Says my mimmi ). Bugging me so much about this problem, I started to search in forums, and I'v got a lot of tips:
- The router had set badly : Tried to fix it,meaning DHCP settings, Set to TKIP WPA2, or AES WPA2, or both --> NO SUCCESS
- Start from the beginning from the Stock rom, and flash the kernel and ROM : Done it --> NO SUCCES. PS: On the stock Rom the WIFI worked
- Tried if only my router is suck and on toher routers will be fine --> NO SUCCESS, STILL THE SAME THING

So I don't have a clue what is wrong with it. My Mimmi's statics :

Kernel : 2.6.32.60-nAa-jb-05
Rom : MiniCM10-4.1.0 Nightly 2013-05-18

I tried other ROMs as well like JB Mini Project but on that it showed no available connecions at all.

So please help me if someone can, it would be much appreciated

 

[jephimax]

Sorry to interrupt but I desperately need help

I've search so much about this problem, I don't have a clue where to start, so please don't skip this question meaning this is not belong here.

One day, when I was on wifi it went off, and then for a few day I turned on and off the WIFI and sometimes it worked some of them don't. Then after this a couldn't managed to acces to WIFI at all, just a gray ( or white ) WIFI simbol showing me: "I've been connected to the router, buuut not going to receive any data from router" ( Says my mimmi ). Bugging me so much about this problem, I started to search in forums, and I'v got a lot of tips:
- The router had set badly : Tried to fix it,meaning DHCP settings, Set to TKIP WPA2, or AES WPA2, or both --> NO SUCCESS
- Start from the beginning from the Stock rom, and flash the kernel and ROM : Done it --> NO SUCCES. PS: On the stock Rom the WIFI worked
- Tried if only my router is suck and on toher routers will be fine --> NO SUCCESS, STILL THE SAME THING

So I don't have a clue what is wrong with it. My Mimmi's statics :

Kernel : 2.6.32.60-nAa-jb-05
Rom : MiniCM10-4.1.0 Nightly 2013-05-18

I tried other ROMs as well like JB Mini Project but on that it showed no available connecions at all.

So please help me if someone can, it would be much appreciated

Wi-fi is working fine on miniCM10 for me, but not on JBMP2 like yours. Try flashing back to stock and repeat process.

 

[Jinghis]

Wi-fi is working fine on miniCM10 for me, but not on JBMP2 like yours. Try flashing back to stock and repeat process.

Do you use the Standard ROM or the Nightly?

 

[jephimax]

Do you use the Standard ROM or the Nightly?

I use the standard one.