The issue with the touch screen not working on the FP4 screen was noticed on only one of the test devices. This was when we were testing the /e/OS S >> /e/OS T upgrade build.
The issue was not replicated across other devices on which we were testing the upgrade build. The /e/OS T dev build does not have this issue.
v2.0 is a major release. The upgrade build release as mentioned has been pushed to v2.1 to avoid mixing these two important releases for the FP4. FP4 users who are on stable or official /e/OS S will not face this issue on v2.0.
Thanks for the details, but to me that still does not explain why for the same device the bug appears on stable and not on dev… I would guess that if such an important feature as touch screen were buggy it would have been seen on the dev branch.
The bug showed up on only one device. The same build on different FP4 devices did not show the issue. We were unable to replicate it again, but for the sake of safety for all users decided to delay the release of the stable or official FP4 OS upgrade build.
Oh ok it showed up for only one device…very sneaky. Thanks a lot for the information.
This is the 5th or 6th straight release, though. It’s really quite disappointing that you keep pushing a device Murena is actually selling like this.
Just to reply as the previous topic was closed. Considering the last update on F-Droid date all the way back to 2013, I doubt it is Trebuchet (as it is still maintained by LineageOS and get regular updates). From what I know “com.android.launcher3” is the base AOSP launcher, but this one looks like a very old build.
I think you’re correct. The version of Trebuchet running in the latest LineageOS 21.0 builds is v14. That and earlier versions can be obtained from APK Pure
I gave a spin to the 2.0 beta build on my FP5.
Outside of long standing issues (sudden reboots, recent app view soft-locking), the new icons looks better than the old ones.
As for Bliss Launcher v3, if it feels a little more snappy, I didn’t see any visible improvement outside the redesigned widget page.
All the issues I had with V1 are still there. No way to reorder widget, or even move them to other places like showed in the sneak peak long ago, No way to quickly access an app parameters, no way to disable or hide apps you don’t use… I’m gonna stick de Kvaesitso for the time being.
@Manoj you mention that V2 will have “UI and wallpaper updates”. Can you answer the question I posted last week?
Does this mean version 2.0 will allow us to go to Wallpaper & Style in Settings and choose our own colors including Material You styles?
Also, last year @GaelDuval mentioned that the Advanced Privacy will be made available independently as an app. Is that available yet? If not, is there an ETA?
Thank you for all you and the devs do!
On my FP5 the answer seem to be no. There is no such option in the settings app in the current v2 beta build.
Also, last year @GaelDuval mentioned that the Advanced Privacy will be made available independently as an app. Is that available yet? If not, is there an ETA?
It’s not available and there is no ETA for it, since it’s a low internal priority compared to all other projects we have.
Porting this to a standalone app could also be a community thing, as it’s open source. We’d be very supportive of this.
Material You is disabled in /e/OS and not expected to be enabled in future versions of builds.
If porting Advanced Privacy could happen, I’d be most grateful. Can’t run e/OS on all my devices. It’d also be great to be able to have the e/OS App Lounge available as a stand alone.
Not skilled enough to accomplish this myself, but e/OS has great appeal to me as I’ve despised “big tech” long before it was “cool” or even on the consumer radar.
For those concerned about Bliss Launcher, I don’t use it. I’m using Nova Launcher as it is way more flexible. Runs well on my P7 and P7Pro. I’ve got an old copy that doesn’t have the modern license verification scheme (keeps me from having to sign into google). Yes, my copy is legit, sadly google has gotten plenty of money from me in the past due to lack of choice.
That’s disappointing to hear. Hope you reconsider this in the future. Not sure how disabling it improves privacy but it sure takes away freedoms. I don’t intend to come across disrespectful as I indeed respect and appreciate all the hard work that goes into developing a privacy focused OS.
Thank you @Manoj for your reply and your hard work as well.
The reason for disabling has more to do with it not matching our UI guidelines. The effort to customize it is too complex plus the amount of testing required will be time-consuming. Hence it has been disabled.
Thank you @Manoj for the detailed reply. My thought was since /e/ OS is based off Lineage OS that keeping those customization options in “Wallpaper and style” settings, that LOS has, was easier than taking the effort to remove them. However, as you mentioned it is more complex than that. Again, thank you for the detailed reply and explanation.
I wish there was at least a way to enable it using ADB like it used to before Android 12, even if it means it doesn’t match /e/ OS UI guidelines. But yes, thanks for the explanation anyway.
Yes, please!!! That would be great.
But how does the app even work? If it changes the host file, I suppose it has to be a default/system app to get the required rights.
If it uses an internal DNS, I think it isn’t possible to block ads this way on Android phones due to Google automatically adding their dns BEFORE even the DHCP provided ones?
As an example, I have a Pihole at home on 192.168.0.250, but my Android phones automatically puts Google DNS before that, unless I use a VPN (In my case a Wireguard that point to my ISP Router), in which case the Google DNS isn’t added.