UMI Iron v1.8 changelog + SPFT download

orissacube

No doesn't solve clicking noise

neilsp

What about wifi problems? Umi promised that would be fixed in the following update

AndriusR

What about the slow speed of USB? it will be repaired in the future? or it issue of the hardware design  ?

loco026

the truth I do not notice any change in the phone

usb transfer equal 500 kb / s
camera flash in low-light conditions equal, without improvement
with noise in the headphones equal and when I use the phone, freezes with poweramp.
the camera, of  doogee dg550, still better than the IRON

Aching head with this, sincerely

rhen

\n\nAndriusR: I'm sure this is not a hardware fault. The speed is much larger in TWRP and with OTG. The problem can be a bad MTP driver.

loco026: I have updated from 1.5 and for me it seems like camera has improved. Flash seems like fire in the right time. The problem is seems like the camera uses much lower ISO settings when flash is fire. But I will test it with manual ISO setting tonight to see that this is really the problem.

All in all I think it is worth the upgrade from 1.5. There are still problems, but it is definitely better than 1.5.

Edit: I've tried the flash and it definitely works fine. The problem is that the camera tend to underexpose the picture. No matter what ISO setting I set manually. If I increase the ISO value, it increase shutter speed too to get the same result. So because there is no Camera2 API there is no way to workaround how the camera expose images with flash. Only UMI can change this behavior. Or they can implement Camera2 API instead and let the Camera app choose the right exposure.

th33xitus

So...seems like you need to do a fullwipe.

Thanks no... not for this stupid kind of update.
Why it is neccesary to do a fullwipe??
That's so stupid...

Is there ANY way to update without a fullwipe?
I used SPFT for updating...

bencebacsi

\n\n

th33xitus replied at 2015-12-1 18:28
So...seems like you need to do a fullwipe.

Thanks no... not for this stupid kind of update.

I've already asked UMI to improve Rootjoy's ability about this. Until that happens, as rhen said, you can update with TWRP and choosing just wipe the dalvik-cache only (that doesn't make sense if you format the cache partition or not), or if you use SPFT, just simply don't flash the data partition but flash the TWRP recovery (or leave that partition unchecked as well, if TWRP is already on your phone), then you can wipe only the dalvik from recovery.
Anyway, I've written a tutorial about this topic: http://community.umidigi.com/forum.php?mod=viewthread&tid=1596&page=1#pid10736

loco026

as expected iron umi iron and  iron pro, with different roms

th33xitus

@bencebacsi: thank you very much for the tutorial. it worked!

rhen

loco026 replied at 2015-12-2 03:32
as expected iron umi iron and  iron pro, with different roms

Custom build version is the same.

Anyway, They can build for the 2 phone from the same source.
My old phone's (Huawei G300) developer has maintained the G300 (MSM7227A) G510 Y300 (MSM8225) from the same source.
He has provided a daily/weekly build of CM10-11. The ROM's were automatically compiled by Jenkins. He just used some ifdef in board config to able to handle the differences of the devices.

If UMI works from source, I think they were able to do that for Iron and Iron Pro or even Rome, Fair and Hammer S.
But I can imagine that UMI works from an already compiled kernel provided by the OEM of the phone. And maybe this is why they are slow to fix low level bugs.