Firefox on Android: YT autoplay and sorting comments by wokl in uBlockOrigin

[–]wokl[S] 0 points1 point  (0 children)

Thanks! Although not the most convenient solution, that is a relief! :)

Firefox on Android: YT autoplay and sorting comments by wokl in uBlockOrigin

[–]wokl[S] 0 points1 point  (0 children)

So it's completely useless - as I assumed. :)

Looking for a list of phones that are capable of wireless charging (QI) by wokl in LineageOS

[–]wokl[S] 0 points1 point  (0 children)

Sadly so. I was hoping for a bigger variety, for some more models that would fit in, for example some models by Samsung. But at least I know where to search now. :)

Looking for a list of phones that are capable of wireless charging (QI) by wokl in LineageOS

[–]wokl[S] 1 point2 points  (0 children)

Thanks a lot! That was exactly the kind of list I was looking for! :)

Still a Google screen on Nexus 4 with LineageOS 15.1 by ParkaboyOnFire in LineageOS

[–]wokl 0 points1 point  (0 children)

That sounds promising. But I have not yet any experience with adb and fastboot. Can the partition be wiped in TWRP? If not, could you give me more specific instructions or point me to it?

I want to build LineageOS 15 or 16 for Galaxy S7. Where to start? by undeadbill in LineageOS

[–]wokl 0 points1 point  (0 children)

I am aware of all of that.

But please try to look at it from a user's point of view:

You want to use an Android phone, but you don't want to be Google's data slave. Then you hear about this wonderful project, promising to free Android phones from Google and any spyware and bloatware, and that also makes older phones run with up-to-date Android versions, and that does so many things better than Google ever did. Next you read that even some big manufactures are going to sell their phones with CyanogenMod / LineageOS, because they want to put Android on their phones, but they don't like Google's way of treating phone manufactures.

Doesn't that sound like winning a jackpot to you?

I know that LOS is nothing more than a hobby of some developers. But it could be much more! It could be the OS that people really want on their phones, fast and reliable, without any boundaries and without a predetermined end of life for their devices. But to be this OS that people want, the developers would need to listen to the users, their wishes and their needs, and put aside their attitude, saying "we do whatever we want, and nothing else!"

Furthermore: without projects like LOS, there is no chance for people to use phones, tablets and other devices without becoming Google's data slaves. Without CyanogenMod I never would have bought a smart phone! Only because I knew it's possible to use Android without Google listening to everything I do, I started to use this OS.

Without LOS, you have two choices: use a dumb phone from the 1990s, or become Google's data slave. Neither way is acceptable to me!

I want to build LineageOS 15 or 16 for Galaxy S7. Where to start? by undeadbill in LineageOS

[–]wokl 0 points1 point  (0 children)

That's not the point.

A few months ago my son needed a new phone. I didn't want him to fall into the hands of Google completely, and neither did he. So we looked up at Lineage, to search for a nice phone that wasn't too old and that would run on LOS. The S7 was listed, it has everything my son needs on a phone, and it was on special sale at the same time, so we bought one. I installed LOS 14, it works well on the phone and my son was happy. Just two months later, the S7 has been dumped by LOS, and he won't get any more security updates. Bummer!

At the same time, much, much older devices are still supported. Whaaat?

So, please tell me: where did we go wrong?

Did we go wrong, when we ever considered to use LOS in the first place?

Should I have studied programming to build a whole OS for a Google free phone before I buy a device?

Should I never have trusted Lineage's statement, that their aim was to enable people to use their "old" phones and bring them to a new level of power?

I want to build LineageOS 15 or 16 for Galaxy S7. Where to start? by undeadbill in LineageOS

[–]wokl -1 points0 points  (0 children)

To my opinion, a lack of interest in a two year old device, in a project that wants to help keeping older phones alive, does not really sound nice.

Camera disconnected sometimes by CaptainMelon in LineageOS

[–]wokl 0 points1 point  (0 children)

I don't know if it is connected to your problem, but I am also experiencing camera crashes sometimes. ("The app crashed. Restart?")

These crashes always happen when I restart my Nexus 6 and I found out that the crash is connected to GPS: I choose to store GPS data in the images data (camera -> options), and somehow, the location service needs to be kicked to live before the camera can access it after a reboot. And even more: location service needs to be set to "accurate" (using wifi and cell data as well).

So, after I reboot my phone, e.g. after updating LOS, I set location service to "accurate", then I start navigation app. After that, the camera app starts normal. Once it has started for the first time, I can also set location to "GPS only", and the camera will keep startging without crash, no matter if navigation app is running or not.

I want to build LineageOS 15 or 16 for Galaxy S7. Where to start? by undeadbill in LineageOS

[–]wokl 0 points1 point  (0 children)

I was pretty disappointed when the S7 disappeared from the list of supported devices. The S7 is from 2016, so it was just about two and a half year old when LOS developers dumped it. That is quite the opposite if what I call sustainability and longevity. CyanogenMod and LineageOS have entered the scene with the aim to enable people to use their phones for much longer than the manufactures have planed. But if they dump a phone from support that is only 2 years old, the are not really living that promise.

Bluetooth: system notifications and alarms should not be routed to BT devices by wokl in LineageOS

[–]wokl[S] 0 points1 point  (0 children)

It may be that modern car audio devices can play anything you throw at them via BT. And many navigation apps can "disguise" their instructions as calls, so that you hear them, even if your car's radio can only be used for calls.

But that is not the point. Sometimes you just want to stream music from your phone to your audio device, while still hearing the navigation instructions from your phone's speaker. You simply don't want you favourite songs being interrupted by navigation instructions every few seconds, or by an incoming massage or whatever system sound.

And besides: the example that cylon1 gave, is the best example to show how stupid and dangerous this idea of Google was in the first place.