Bugs 2.3.2


I have problem with MIUIcamera on SGS2 ,i can't record video screen just freez after 3-4 seconds.
 
i had earlier miui ver 1.12.16 on Lg Optimus 2X..yesterday i updated it to 2.3.2 but after update it freezes on boot screen..
wiped data/factory settings and dalvik cache, reinstalled again but no success .pls help on this.
 
I got 2 restart:
1. When i was using parlingo
2. When i was calling

Screen freez, only power button work then restart.

Sent from my HTC Desire HD using Tapatalk
 
Known issue - no ETA for fix either :-( could be an APKTool issue
I am sorry for those got the screen freeze or camera freezing or FC on wifi tethering but I have to say that on the Acer Liquid MT 2.3.2 ROM (ported by lens_flare) none of those problem exist..
all works perfectly.
 
I am sorry for those got the screen freeze or camera freezing or FC on wifi tethering but I have to say that on the Acer Liquid MT 2.3.2 ROM (ported by lens_flare) none of those problem exist..
all works perfectly.

The topic should of been labeled Bugs 2.3.2 - ICS. Most of these problems are only in the ICS build (Currently Nexus S). As for the Liquid MT. I believe lens still has that on GB, so he hasn't encountered the large amount of trial and error with building an ICS ROM. Though if anyone can do it. lens_flare can.
 
That's true it's a gingerbread 2.3.7.
I am not sure to want see the ICS on the phone anymore... just because of the MTP mode when plugged on USB (but that is maybe not true anymore with miui rom...)

Maybe should we start to see ICS dev and GB dev seperated to prevent any confusion.
 
That's true it's a gingerbread 2.3.7.
I am not sure to want see the ICS on the phone anymore... just because of the MTP mode when plugged on USB (but that is maybe not true anymore with miui rom...)

Maybe should we start to see ICS dev and GB dev seperated to prevent any confusion.

We are working for a way to help seperate the development and ease the confusion for any members. Do you have any ideas to help further this?

Were currently using brackets [GB] and [ICS] to do most of the work.
 
I am sorry for those got the screen freeze or camera freezing or FC on wifi tethering but I have to say that on the Acer Liquid MT 2.3.2 ROM (ported by lens_flare) none of those problem exist..
all works perfectly.
if tethering is working he isnt modifying the framework-miui-res.apk
 
Nexus S running 2.3.2

1. Dialer doesn't seem to accept theme changes, it remains as is regardless of which theme is selected.

2. Dialer number attribution (matching to contacts) doesn't work fully.
if a number in a contact is stored as +44 7890 123 456 and incoming call from that contact is received (i.e. 07890 123 456) the dialer / phone app doesn't match it to any contacts.

Other than that, looks pretty good - keep up the good work!
 
Hi Arun,

Re 1. Themes under MIUI V4 are still considered unstable and incomplete, this should be considered the reason for your first issue. The developers are aware themes are very important part of MIUI.

Re 2. Also been reported as a known error, we are still waiting for confirmation from the MIUI development team on this one.

Thanks for your feedback. Enjoy the ROM :)
 
Nexus S running 2.3.2

2. Dialer number attribution (matching to contacts) doesn't work fully.
if a number in a contact is stored as +44 7890 123 456 and incoming call from that contact is received (i.e. 07890 123 456) the dialer / phone app doesn't match it to any contacts.

Other than that, looks pretty good - keep up the good work!

Hi and congratz for this nice rom :)

But I have the same problem (2.)
This problem exist on android stock rom (4.0.3)

if I save my contact with +33 (france) I see contact name on my dialer history but I don't see it on sms contact name, only number!

If I save my contact without +33 I see contact name in my sms history but I see only number on my dialer history!

The only way I found is to save 2 contact numbers by contact, 06xxxxxxxx and +336xxxxxxxxx :/
I try to delete account & sync again (like I saw in other forum) and I already have the same problem and I'm not the only one.

Rom can't match +33 (or indicative country) with national number.. :( This is a basic function !

Bug saw in:
*Nexus S / last miui 2.3.2 /rooted / FreeMobile (fr)
*Nexus S / android stock / other operator (fr)

Thank for you great work!
 
Dialer number attribution (matching to contacts) doesn't work fully.: I have the same problem with SGS2 MIUI V4 (all ports). But this is happening to SMS app.

From Mark's explanation, we'll have to wait. OK, it's perfectly understandable. Other SMS apps in Market can cover for that.
 
Will try and gather some information from developers tomorrow if they have time to speak to me. We've not forgotten about this or the other reported bugs, most are pending with Xiaomi at the moment.
 
Hi,
HTC Desire had previously 1.12.30 on the phone, updated through the update app to 2.3.2 (i assume [GB]).
Bluetooth issue. In my car I have a Blue&me phone system from Alfa and an BT audio adapter. The BT-Audio adapter still works, the Blue&me connects when i start the car and then "dies" some time later. I can not connect to it anylonger. Reboot phone does not help, bluetooth off/on does not help. Have to turn off the car and then later come back. Seems like the phone sends something to the blue&me system that "kills" it or whatever!? And it then needs some time to recover.
With 1.12.30 it worked very nicely.

How can I/we debug this?
Are there any way of logging what bluetooth does? Maybe I can try and return to the old, log what is happening. Update and then log the same again.
 
Hi,
HTC Desire had previously 1.12.30 on the phone, updated through the update app to 2.3.2 (i assume [GB]).
Bluetooth issue. In my car I have a Blue&me phone system from Alfa and an BT audio adapter. The BT-Audio adapter still works, the Blue&me connects when i start the car and then "dies" some time later. I can not connect to it anylonger. Reboot phone does not help, bluetooth off/on does not help. Have to turn off the car and then later come back. Seems like the phone sends something to the blue&me system that "kills" it or whatever!? And it then needs some time to recover.
With 1.12.30 it worked very nicely.

How can I/we debug this?
Are there any way of logging what bluetooth does? Maybe I can try and return to the old, log what is happening. Update and then log the same again.

It is an Alfa Guiletta Blue&me car phone system. The same is used in all Fiat and Alfa's equipped with a bluetooth phone system.

Found this in a previous version, same problem i assume :
http://miuiandroid.com/community/threads/miui-rom-2-2-24-ics-gb-roms-uploaded.15514/page-4

Have returned to 1.12.30 from a nanodroid backup. Then applied 2.2.17, the result is.

I had no problems with the bluetooth connection anylonger :) only the numbers of the people last called was missing. I did not test "received" calls, so can not say if that would have worked with 2.2.17.

Updated to 2.2.24 and still the same. Strange enough I called my home number and that is shown with a name in last called!? That Contact entry also contains my mobile number. With 2.2.24 "received" calls are only shown as a number in the car. On the phone it shows the contact.
All my numbers are with prefix +45 in the front, for denmark.

Maybe it is the same problem that some people has noticed with number with / without prefix?

Have now updated to 2.3.2 - lets see how it reacts later today.
 
Pushing the developers for solution for the number attribution issues. Should have some news soon I hope! :)
 
You can notconfigurethemailexchangeusing astandardtcp portother than 443!

:(
Exchange typically runs over SSL if your not within the Domain itself. What do you need to use it on a non-standard port for?
 
i've an Lg Optimus 2x and after the 2.3.2 update the system browser can't connect to the 3g data but only over the wifi. dolphin mini browser work fine instead.
 
Exchange typically runs over SSL if your not within the Domain itself. What do you need to use it on a non-standard port for?
Do not worry about it. I just want to know, as with all other ROMs do not have thisproblem if it is possible to solve it.