Recent content by eazilyled

Weird. It didn't boot for me for some reason. I have gone back to 3.4.26 for now. Will investigate more on Monday.

I installed the new version from the official link. I'm still getting a black screen on boot.

I noticed that the mi one download link is back. I downloaded it but the md5 is different than listed. Is this code correct: 14049672748627DC1E895550D72E078

Is there a way to mount USB in MI-Recovery? I'd like to revert to previous ROM until it is fixed. Or do I need to use an SD card reader?

Me too :-( I updated my MiOne using the updater app.

Device is Mi One Plus. MIUI version is 3.4.12. When typing using the keyboard, the dictionary does not appear to be active, i.e. no suggested words are offered apart from contact names, all typed words are underlined in red. Language is set to English (United Kindom). Android spell checker...

Just noticed that the English dictionary doesn't appear to be working when composing SMS. I'm using the standard Android keyboard.

Updated my Mi-One over the weekend from MIUIv4. What can I say? Amazing!

I'm in the UK. Not sure how to obtain gsm carrier code. In MIUIStats it shows 'Carrier' as 'Telefonica O2 UK Limited', if that's any help?

You're probably right :) , but if you any of you guys get a chance to fix it in the next version, that would be great.

Please could I report another wrong carrier in 3.3.8: Mine shows as O2-UK. It should be giffgaff. My phone is an Mi-One, so I'm running the V4 version of 3.3.8.

Weird. With 3.2.1, 'Giffgaff' was correctly displayed as my carrier. With 3.2.8, it's back to the incorrect 'O2-UK', which is how it was displayed prior to 3.2.1.

I'm liking the carrier hotfix. giffgaff is correctly shown as my carrier with this release. With previous versions it always showed O2 UK, which I always ignored as giffgaff runs on the O2 network.

OK cool thanks for the info!

Thanks I'll bear that in mind. However in this case, I wiped cache / wiped user data / wiped all data / updated system partition / installed update.zip twice, and the problem happened each time. Although I suppose the random error could have occurred twice due to bad luck.