Webview is another one…. Security has been a recurring issue with e,/OS since a long time but eventually they’ll move to a better architecture for distributing updates:
If the team really had limited resources they wouldn’t spend them to develop another map app or another browser.
Claiming security is “an important topic” like if it was a cosmetic bug is really concerning. The microG vulnerability is an attack vector, it can be exploited, and all our data can be put out in the open.
In the end it’s all about management choices, and the choice is to leave a vulnerability exposed for all users.
Which microG vulnerability you are referring to ?
All security fixes are also available as patches to the previous release, v0.3.16.252432, …
0.3.16.252432 is the version shipped with 4.3.
Yes but the security patches provided by microg for this version of com.android.vending (as apk) cannot be installed by the user. They have to be integrated with the next OS update. The old time where e.g DivestOS could update microg or webview independently of the ROM was so nice…and speaking of resources DivestOS was mostly a single man project.
So join the team and help them ![]()
obviously you have a clear vision and are a dedicated person, tech industry is looking for people who don’t only write forum posts but also get their hands dirty
Reporting issues does not mean we have the skills to solve them. Both aspects are needed in the tech, by different persons
A user forum is a good place to point out potential issues IMHO.
I think that these software efforts are not bad (the own /e/OS browser will hopefully also solve the WebView update problem), but I also think that more resources should be made available for security updates.
To be fair, microG is probably a limited target because of the small userbase, but a fast update is still best practice.
@Manoj : Can you ask whether an update release can be distributed e.g. by AppLounge for microG? Or a patch version 4.3.x of /e/OS be made available?
The Release v0.3.17.252432 · microg/GmsCore · GitHub microg has already been added to the 4.4 code base which is undergoing beta testing.
That’s good, and the 4.4 release is expected for October 12. I think that this is quite acceptable. Still, I am looking forward to system app updates by the AppLounge.
Official v4.3.1 build for FP4 on A16 has been released.
It may not be visible in all locations and may take 1-2 days before being available for all FP4 users.
anything planned for community builds? Phone is basically unusable right now…
Update ist ready for download … Recheck the Updates on your phone
Hi Manoj,
How can I report bugs or issues in V3.4.1?
For example, when I want to listen to a voice message and hold the phone to my ear, the loudspeaker is automatically activated. I would like to continue listening through the earpiece, as it worked before.
However, this issue was already present in version 3.4.
Thanks!
edit: Sorry .. Thats not a bug . This was a config. problem at me ..3.4.1 works very good!!!
You can report issues is by raising them on gitlab. Follow the process given in this guide.
In the issue mention it is present in v3.4.1 and share details.
yes .. i do it .. many thanks ..
Many thanks @manoj!
But what about the rebuild retries for A15 and especially A16? (I’m specifically interested in /e/-4.3 A16 for kebab)
It failed in the initial attempts to build it. Have requested the build team to keep it in the list for the re builds. Will update on the progress of these builds.
Check out the document about how we rollout our updates.