Search results

nope

Screenshot? I can't see any aligning problem on my device.

Well we switched from Baidu -> Google. So if there is a wakelock caused by Network Location, then that is either Google or too low level in MIUI for us to do anything.

Need more to go on than "doesn't work". Open a new bug report once you learn how to correctly post bugs.

Mirroring is fault of translators, not bugs. Search engines aren't a bug. I've added those /libs into scripts for MI2/MI2A/MI2S.

Its hard for use to expand and work on current bugs/features when a 2 year old device is holding us back. Just because Xiaomi made it, doesn't mean it should live forever, it must die like all devices. The only reason it got v5 was because everyone was bitching about it. The device sucks...

Don't see your post.

http://miuiandroid.com/community/threads/how-to-make-logcat-with-adb.18455/

There is a 50mb ISO included in the ROM for automatic driver install on Windows. We remove that bloat, since you only need to install drivers once :p

Finally SGS2. YES. I can flash it.

Thats why we are here. We do it, so you don't have it.

Well with such an obvious problem, why isn't there a logcat posted? How hard is it to run "adb logcat", do that thing, get it to crash, then submit that logcat? We can't fix what we don't have a logcat of.

I'm investigating this still. Will let you all know. Mine takes about 15seconds to lock on, compared to 2sec now.

I think there may be some translators with some strings that conflict with location. These strings need to be removed config_networkLocationProvider1 - framework-res - Italian config_networkLocationProvider2 - framework-res - Italian config_geocodeProvider - framework-res - Italian...

what u talking about noob

This will be difficult to figure out then, I've made some experimental changes. http://ibotpeaches.com/miuiandroid_aries_jb-3.5.3.zip MI2/MI2S ONLY 96f4420f24df823c26f721196a13d6ce miuiandroid_aries_jb-3.5.3.zip Give this a shot. Report back. Works fine for me, with full Google Maps support.

I've done some scripts cleanup, but I believe this stems from CWM. Still looking though.

I believe CWM blocks Updater from restoring your recovery back to MI, so I'm not exactly sure how do it get it back, but I believe that may be the problem.

Humor me, and go back to stock MI recovery, and flash via Updater.apk. I think there is something up with overwriting cache relating to framework-res that CWM might be causing.

Deleting the APK won't do anything. The location that Network is pulled from is defined by a few strings in framework-res.apk. <string name="config_networkLocationProvider1">com.google.android.location.NetworkLocationProvider</string> <string...