1.3.0 update - Issues (Accessibility Permission)

Technical Support
1

I was looking forward to only 3 things getting fixed in this update:

  • Bluetooth History dialog is now visible and you can reconnect to previously connected devices.
  • Manual Network Selection now it’s visible and you can choose the network you want to connect to manually.

however…

  • Accessibility Permission, is still broken despite Developers agreeing that it a bug and it shouldn’t have been removed. Still didn’t get fixed.
    How to close apps? - #20 by urszula

Worth to mention none of these are new features, these are standard AOSP features that were simply hidden/broken by whoever is building this.

Again I repeat accessibility permission is necessary for apps that improve accessibility for people that have vision, hearing or mobility issues. As some of you know, E-ink devices are very popular with people that have disabilities, so not fixing this issue in this update is a joke.

I’m ok with you being hostile to the community and only providing shitty open source code that still requires access to your private repos, or still including the shitty logging tool credentials to build a release. but…this is what you guys said when you finally replied on the matter that was broken during 1.2.0 update:

We have confirmed this behavior and reported it as a bug to our development team. Restoring this menu is now a priority for us.

Maybe tagging more people will work :thinking:
@urszula @michalstasiuk @Michal_Kicinski @Lukasz_Siecinski

So please explain to me! How showing somebody this:

  • Timing Controls, Vibration & Haptic, Audio balance

To an app that is requiring Accessibility Permission, how is this logical?

Other issues I noticed quickly, will update if I see more:

Offline switch is still broken:
WIFI doesn’t turn on automatically when you disable the offline switch. (when it was on before u enabled the offline switch).

Brightness Slider:
The increments make no sense. Use less than 10% of the bar, 90% of the slider is useless. You need baby fingers to actually set the optimal brightness.

Minimum volume on loudspeaker:
Can’t confirm any change, still super loud at the lowest volume.

I’ll stop talking now before I say something else that I regret.
Thanks for coming to my TedTalk.

17 Likes
2

It is absolutely ridiculous that this hasn’t been fixed in this update especially as it was identified immediately after the first update, it is bizarre that it was not prioritised. I just want to sideload a killallapps because I do not want to keep manually closing all applications and removing this feature doesn’t allow me to.

Just to confirm, my Wi-Fi comes on as normal after taking the phone out of offline mode.

4 Likes
3

Works for me as well, I flipped Offline+ on disabled screen as well as with that brightness/connectivity menu. Wi-Fi re-enables and reconnects.

3 Likes
4

@jdot @buiosu

It’s related to the bug unwiring functions from the offline switch.
For some people it manifests as “camera loses the permission”. For me wifi doesn’t turn on automatically.

Doesn’t matter how long I wait, it wont turn on. But not a big issue, I’ve gotten used to it.

2 Likes
5

same thing happens to me and i end up wasting battery accidentally using cellular instead of wifi

1 Like
6

@gezimos I’ve asked our team about this & I will return with an answer when they respond.

1 Like
7

Thank you Urszula

1 Like
8

@urszula you said a roadmap update would come after 1.3.0, is that still happening?

1 Like
9

Our team has said that they have confirmed this behavior and reported it as a bug to our development team. Restoring this menu is now a priority for us. However, they did mention that they never committed to fixing it by 1.3.0. I am waiting to hear when it should be fixed.

10

@urszula Thanks for the response.

And my response to this is:

This is a joke. Priority means priority. The bug wasn’t there in 1.1.1 when I bought the device, it came with 1.2.0 with a lot of other bugs. We’ve reported this bug ~1 week after the 1.2.0 update.

Sorry, but if your team can’t solve this in 2 months, maybe you should get somebody who know what they’re doing?

5 Likes
11

@gezimos I’m sorry to hear your disappointment. All I can do is pass on your feedback on to the team.

2 Likes
12

@urszula
Thanks for all of your hard work!

2 Likes
13

As someone working in software engineering I can’t agree more. Everywhere I’ve worked regression bugs were something that MUST be fixed ASAP. Things that have previously worked being broken by the update may be annoying but it happens so whatever, but breaking things and leaving them broken – that’s just not the way to treat your users.

4 Likes
14

That’s why there is .0 after 1.3 right?

1 Like
15

The update fixes the Bluetooth and the fingerprint reader (partially, it still doesn’t always read fingerprint but now you can just try again).

Again, I wonder why Mudita didn’t leave AOSP features intact and why they didn’t just build on existing apps, just optimise interface.

The reason the CEO gave is that they didn’t want to build on a codebase with GPL license or similar where they’d have to make the code public. That would decrease their competitiveness. I call shenanigans. Competition with whom? Boox? Bigme? Those vendors already have excellent apps. I know, because I have a 10 years old Boox which until recently even still received updates. They even fully support sideloading, with e-ink settings and extra optimisations for third party apps, e.g. increasing contrast of interface elements and bleaching the background. Spotify gets a white background, to give an example.

It’s the inverse: NOT building on existing apps will decrease the competitiveness of Mudita. Why shouldn’t people pick a Boox Palma once it gets a 4G modem? Privacy? Size? Maybe.

3 Likes
16

This is exactly what I’ve been trying to say for a while. There are tons of great FOSS apps out there that do what the Mudita apps do but better, they might just need some e-ink optimization tweaks. As you said, there aren’t enough e-ink competitors out there to really worry about and open source just helps the community overall. Their competitors are already ahead of them in many ways, just lean into the things the MK should be better at, like the size and privacy.

Plus it’s weird that in addition to removing AOSP features and rebuilding apps that already exist, they chose a really old AOSP version. Why not go with a newer version? Or even better, use Lineage, which is built with security in mind and still strips out the Google tracking crap? Why include the Sentry tracking which has been a sore spot for a lot of people and makes me not want to use MK apps even when they get updated to be more functional? But I digress…

2 Likes
17

I agree with you whole heartedly. I am desperately trying to make this Mudita thing work as I don’t know of another valid option. I have spent so much time trying to fix things it is driving me crazy.

4 Likes
18

It mostly works for me. It’s just frustrating to replace all of the stock apps to get decent functionality but then sometimes the system doesn’t recognize the new apps (for example, I found a FOSS phone app that is better than the MK version in every way but when a call comes in, if the stock MK app is disabled, it won’t pop up with the FOSS version, thus making it impossible to answer the call).

2 Likes
19

The Bluetooth for me is still not working after the update, whenever I try to connect to a bluetooth device, the bluetooth just turns on and off for days and it drains my battery. Hopefully someone can help me fix this soon.

1 Like
20

Did they comment on the brightness slider or the wifi not turning back on when exiting offline+ mode?

1 Like