I tested a little bit the mx4.

• WiFi: OK
• Camera: OK
• Flashlight: OK
• BT connection to Ubuntu Desktop: OK
• lockscreen notifications: OK
• phone crashes when App is allowed to use a device for the first time:
  • utorch: Phone crash when allowing access to camera service for the first time (worked after boot)
  • unav: phone crash when allowing access to navigation data for the first time (worked after boot)

Not tested: Phonecalls/SMS as the phone does not recognize SIM anymore (hardware defect)

@mariogrip said in Help testing new legacy image:

Is there someone that want to help us test our new images?

Hi, I did a little bit more testing on the mx4. With v2 I have the issue that my WLAN connection "freezes". That means indicator still shows connected WLAN, but the mx4 is not able to receive anything. I need to switch flight mode on/off. After that it works again for some time. There is no switching between different WLANs / SSID / Hotspots. I just have a single access point.

Can anyone else confirm this issue?

Thanks

I tested a little bit the mx4.

• WiFi: OK
• Camera: OK
• Flashlight: OK
• BT connection to Ubuntu Desktop: OK
• lockscreen notifications: OK
• phone crashes when App is allowed to use a device for the first time:
  • utorch: Phone crash when allowing access to camera service for the first time (worked after boot)
  • unav: phone crash when allowing access to navigation data for the first time (worked after boot)

Not tested: Phonecalls/SMS as the phone does not recognize SIM anymore (hardware defect)

It seems really strange. I am able to call other mobile numbers but no fixed line calls work. Same issue with another SIM card.

I reflashed with the current build (r269) but the probem persists

Phone App on devel_rc hangs after dialing,

• either calls out once (target rings), I am unable to hang up, if I hangup it immediately redials.
• or outgoing calls does not work at all. Phone App claims it was dialing but target does not ring. Only reboot solves the problem

I was never able to make more than one call. After that I had to reboot the device to be able to make a call again. Has anybody else the same issue? If so I'd file a bugreport.

Thanks,
Stefan