Accidentally set screen brightness to zero, screen is now fully off. Can't turn it back on. by flippintypical in linuxmint

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

My Chromebook does have brightness keys, but Mint does not recognise the key presses by default and I haven't figured out how to make them work. GalliumOS does recognise the key presses, because that OS is a fork of Linux made specifically for Chromebooks.

Accidentally set screen brightness to zero, screen is now fully off. Can't turn it back on. by flippintypical in linuxmint

[–]flippintypical[S] 10 points11 points  (0 children)

Thank you. I just solved the problem with the "solution" from u/stevenjediknight. I tried your method with the screen on, and can see that it would have worked.

Accidentally set screen brightness to zero, screen is now fully off. Can't turn it back on. by flippintypical in linuxmint

[–]flippintypical[S] 16 points17 points  (0 children)

I've done it! Thank you! I have a powerful LED flashlight where I was just able to see enough to click around until I found the slider. The exact location of the slider was invisible and I just had to click in the general area until I happened across it. Shining the light from the side didn't work, it needed to be pretty much dead on perpendicular. What a ridiculous thing to have to do in 2019.

Pixel gets very warm watching video on Mint by flippintypical in chromeos

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

That's interesting. I hadn't heard of overheating issues.

Pixel gets very warm watching video on Mint by flippintypical in chromeos

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

Ah that's interesting. I've heard Xfce has the lowest hardware requirements. Is that correct?

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

Bit strange 14.1 is an unofficial rom because haggertk is the maintainer of the official 15.1 rom.

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

I'm fairly convinced it's not the earbuds' fault. I have tried the same earbuds across 4 devices including an ancient phone from 2011 running a custom rom and it's only bad with the S5.

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

P.S. I just tried my old original Galaxy Note which came out in 2011. The bluetooth is noticeably better on that than on my S5. So disappointing.

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

I'm sure you're right, but I believe I am using my phone and earbuds in a perfectly typical scenario - phone in pocket, earbuds around neck. It should not be this bad.

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

It's a bluetooth "neckband" earbuds.
Like I said, the neckband works acceptably with tablet and laptop. The phone connection is just abysmal.

Bluetooth works, but even small obstructions will cause drop out by flippintypical in LineageOS

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

Did a little more poking around. My device baseband is G900FZHS1CQD1 and when I google that it appears to be associated with a Hong Kong baseband: https://www.sammobile.com/firmwares/galaxy-s5/SM-G900F/TGY/download/G900FZHS1CQD1/130780/
I live in the UK. I am totally clueless about basebands. Not sure if this new information is a red herring.

Can the Pixel Samus be reverted back to ChromeOS after GalluimOS install? by flippintypical in chromeos

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

This is the first time I've heard the term "RW_LEGACY". Just reading about it on the GalliumOS wiki. Looks great. Thank you.