What the fuck, Android



  • @jaloopa said in What the fuck, Android:

    My problem with Bluetooth audio is a bit different.

    I have a similar problem - sometimes Spotify will try and play despite Podcast Addict even having the notification thing with the controls up. I don't know why it thinks this is the case but there we go.

    I also an issue where my Galaxy S7 will, every now and then, insist that it is still connected via Bluetooth to NISSAN CONNECT, despite the fact that the car is off and parked on the first floor carpark on the opposite side of the shopping centre I am on the other side of on the ground floor, and then wonder why I can't hear anything when I answer a call. Turning Bluetooth off and on again relieves it of this notion, but it requires me to see the little jiggers next to the Bluetooth icon in the notification area.

    My old Moto X Play and a Nexus 6P that also connect to the car never behaved in such a way and I don't have anybody else with an S7 to test it with.

    @sloosecannon said in What the fuck, Android:

    I'm talking about the Android Auto app - which basically changes the phone into the Android Auto screen and makes it more vehicle-friendly to use...

    I hired a car a couple of months back and drove it to, around and back from Adelaide. I put the Android Auto app on so I could have satnav and a somewhat usable interface for music (car had Bluetooth and a touchscreen head unit but no satnav). Even when the music was coming through quite nicely, the satnav directions that played over the top of them sounded like I was listening to them via AM radio.

    Apart from that and the fact that the idiot thing kept trying to get me to through the Britannia Roundabouts, I was quite happy with it and would ideally like to get a car with Android Auto integration in the future.


  • BINNED

    @douglasac said in What the fuck, Android:

    my Galaxy S7 will, every now and then, insist that it is still connected via Bluetooth to NISSAN CONNECT, despite the fact that the car is off and parked on the first floor carpark on the opposite side of the shopping centre I am on the other side of on the ground floor

    Another car with the same Bluetooth name? I don't know if BT just uses the name or if there are unique identifiers instead



  • @lorne-kates said in What the fuck, Android:

    @hungrier said in What the fuck, Android:

    @lorne-kates Well, I don't know if it'll solve all your problems but I use Shuttle for music, and BeyondPod for podcasts and audiobooks.

    will try

    Update, looked at the reviews for BeyondPod and will not try. All recent reviews are "UI interface changed for no reason. Hard to use. Basic features stopped working. Can't scroll without risking deleting files. Actively looking for alternative".

    I get enough randomly changing UI, half-implemented features and use-case ignorant devs just browsing the web, thank you very much.



  • @pie_flavor said in What the fuck, Android:

    @dkf said in What the fuck, Android:

    vibration-induced erroneous hits.

    :giggity:

    "Using the phone one handed"

    :giggity: :giggity:



  • @atazhaia said in What the fuck, Android:

    @jaloopa At least the Google keyboard got a bit of prediction going on when swiping too and will autocomplete words so you don't have to swipe them fully in some cases.

    Double fuck that shit. I don't use autocorrect/predictive. It's never helped me in any way, and ends up fucking up most of what I type. I can enter text at least 10x faster with a swype than tap. That's why I switched back to Swype from Google Keyboard after using it for 2 weeks. You can't turn off autocorrect AND have swipe on. And the autocorrect fucks up a lot, so you have to catch it AS you enter it, which slows me down.

    At least with Swype, if I screw up a word and it doesn't register until a few more entries later, all I need to do is tap the word. Swype automatically selects the word, and shows the alternate words for that entry based on what my swype was. OR since it is highlighted, I can re-enter.

    Compare that with GK-- if I screwed up the previous word, I can hit backspace. It will show me the alternatives for the word currently on screen, but not the words based on my swiping. And if I tap a word from a few entries back, it doesn't select it. So I have to double tap or whatever the fuck works (I still can't 100% reliably select a word, it's like fucking voodo or something).



  • @lorne-kates said in What the fuck, Android:

    I don't use autocorrect/predictive. It's never helped me in any way

    You must be :doing_it_wrong: . Swipe-text feels really weird for me since I like actually selecting my buttons, and predictive text is really great for regular typing (once you've taught it words like PrintStream and TDEMSYR).

    @lorne-kates said in What the fuck, Android:

    (I still can't 100% reliably select a word, it's like fucking voodo or something).

    How is it rocket surgery for you people? Long-press a word. It will then select that word. :drum:



  • @pie_flavor said in What the fuck, Android:

    @lorne-kates said in What the fuck, Android:

    I don't use autocorrect/predictive. It's never helped me in any way

    You must be :doing_it_wrong: . Swipe-text feels really weird for me since I like actually selecting my buttons, and predictive text is really great for regular typing (once you've taught it words like PrintStream and TDEMSYR).

    You like Discourse. None of your opinions count for anything.

    @lorne-kates said in What the fuck, Android:

    (I still can't 100% reliably select a word, it's like fucking voodo or something).

    How is it rocket surgery for you people? Long-press a word. It will then select that word. :drum:

    Here, let me highlight for you:

    100% reliably

    Even long-holding sometimes doesn't work, or mis-fires and counts as a tap, or your finger isn't 100% still so it causes a scroll, or the word is near the end of the screen so it doesn't register, or it selects the wrong word, or it instead activates a cursor instead of a select, or there's a hyphen and the OS shits itself trying to figure that out, or or or



  • @lorne-kates said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    @lorne-kates said in What the fuck, Android:

    I don't use autocorrect/predictive. It's never helped me in any way

    You must be :doing_it_wrong: . Swipe-text feels really weird for me since I like actually selecting my buttons, and predictive text is really great for regular typing (once you've taught it words like PrintStream and TDEMSYR).

    You like Discourse. None of your opinions count for anything.

    @lorne-kates said in What the fuck, Android:

    (I still can't 100% reliably select a word, it's like fucking voodo or something).

    How is it rocket surgery for you people? Long-press a word. It will then select that word. :drum:

    Here, let me highlight for you:

    100% reliably

    Even long-holding sometimes doesn't work, or mis-fires and counts as a tap, or your finger isn't 100% still so it causes a scroll, or the word is near the end of the screen so it doesn't register, or it selects the wrong word, or it instead activates a cursor instead of a select, or there's a hyphen and the OS shits itself trying to figure that out, or or or

    Let me delete the parts of that that are user error and inevitable with a touchscreen and manifest in literally every other application you use.

    @lorne-kates said in What the fuck, Android:

    Even long-holding sometimes doesn't work, or there's a hyphen and the OS shits itself trying to figure that out, or or or

    Haven't experienced this behavior.


  • Impossible Mission Players - A

    @jaloopa said in What the fuck, Android:

    @douglasac said in What the fuck, Android:

    my Galaxy S7 will, every now and then, insist that it is still connected via Bluetooth to NISSAN CONNECT, despite the fact that the car is off and parked on the first floor carpark on the opposite side of the shopping centre I am on the other side of on the ground floor

    Another car with the same Bluetooth name? I don't know if BT just uses the name or if there are unique identifiers instead

    It pairs based on MAC address, but in this case it might be the bluetooth just not disconnecting despite being out of range (i'm assuming it's a Low-Energy 4.0 thing).


  • Impossible Mission Players - A

    @lorne-kates said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    @dkf said in What the fuck, Android:

    vibration-induced erroneous hits.

    :giggity:

    "Using the phone one handed"

    :giggity: :giggity:

    I use my phone one handed all the time, actually. My interface is much more precise than most, I guess.


  • Dupa

    @jaloopa said in What the fuck, Android:

    @lorne-kates said in What the fuck, Android:

    swipe typing

    I've never got on with that. A decent prediction engine that means you don't need to fully type words is a lot faster IME, especially when swiping doesn't recognize a word and you have to delete it and type it out anyway

    I kinda like swiping when lying down on my stomach.



  • @tsaukpaetra said in What the fuck, Android:

    It pairs based on MAC address, but in this case it might be the bluetooth just not disconnecting despite being out of range (i'm assuming it's a Low-Energy 4.0 thing).

    I'm thinking this but I can't think of any reason why it would want to do that. I've paired it with wireless headphones and such and there it's only the car that it has issues with disconnecting with. Probably some weird Samsung quirk.



  • @lorne-kates said in What the fuck, Android:

    So the first time someone uses lock screen they'll enter 4 digits, then sit there starting at the phone waiting for something to happen. And then, even after they discover how this shitty UI works, they'll still have to use an extra tap every time they unlock!

    ...wat?

    1. even on my previous phone (windows) my unlock pin was 7 digits. everywhere i can use it I do, because it's such an automatic motion for me that it requires extra mental effort to stop myself after the first 4

    2. even on my previous phone, as well as on my current android, a) there's no "enter" key, b) as soon as I enter the last digit of the correct sequence, it unlocks

    meaning, what kind of crap phones have you been using?

    @lorne-kates said in What the fuck, Android:

    Ios

    ...oh.



  • but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.



  • @sh_code said in What the fuck, Android:

    but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.

    I wouldn't know - Verizon adopts the 'fuck you, give me money' stance towards mobile hotspots, so I have to stick to tethering. The fact that they can price-lock a hardware feature is TR:wtf:.


  • Impossible Mission Players - A

    @sh_code said in What the fuck, Android:

    but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.

    Yeah, it is awkward. It also affects how your phone is named in Bluetooth when pairing. Basically, phone name, Bluetooth name, and Wi-Fi SSID are all the same for some reason.


  • Impossible Mission Players - A

    @pie_flavor said in What the fuck, Android:

    @sh_code said in What the fuck, Android:

    but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.

    I wouldn't know - Verizon adopts the 'fuck you, give me money' stance towards mobile hotspots, so I have to stick to tethering. The fact that they can price-lock a hardware feature is TR:wtf:.

    They can price lock whether you can connect to data networks, they figure the can control the privilege for other devices to connect through theirs to connect to their data network. :man_shrugging_tone3:



  • @sh_code Doesn't do that on mine, or nearly any other I've owned (a long way, the original HTC Desire was my first).

    Likely some stupid implementation on your phone's manufacturer's behalf.



  • @sh_code said in What the fuck, Android:

    but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.

    It seems to be different for every device. In Vanilla Android you can't rename your device at all, it's just not an option. With some customized versions of Android the name is based on the device's Bluetooth name, and apparently for you it's based on the wifi hotspot name. I dunno what's so wrong with a separate setting for the device name so I can identify it from other android devices on my wifi network.



  • @sh_code said in What the fuck, Android:

    but since we're on the topic of "wtf android"...
    ...why does naming my wifi hotspot renames the whole device? that seems pretty weird.

    Because the iPhone does it that way and Android must "follow the (perceived, not actual) leader".



  • @lb_ said in What the fuck, Android:

    In Vanilla Android you can't rename your device at all, it's just not an option.

    Settings -> Bluetooth -> top-right menu -> Rename this device



  • @kt_ said in What the fuck, Android:

    @sloosecannon said in What the fuck, Android:

    @lorne-kates said in What the fuck, Android:

    So Android has managed to fuck up any goodwill I had for Bluetooth.

    When I was carrying around the iPhone, I paired it to my car stereo. It was great. I would get in the car, turn on the car, and my music would start playing. I turn off the car, it stops playing. I hit BACK or NEXT on the car stereo, and the track goes BACK or NEXT right away. There's even a button that lets me browse the playlists on the phone so I can easily switch.

    Now comes the Android. I sit in the car and turn on the car. One of a few things will happen:

    1. Nothing, because I don't have the device set to "play when connected"
    2. Nothing, because I DO have the device set to "play when connected", but since the car stereo was off when it connected, it's now playing into nothing, even if I turn the stereo back on. Now I need to switch off of BLUETOOTH AUDIO then back on.
    3. Nothing, because I DO have the device set and the stereo was on, and the track is showing on the dashboard, but I still have to press "Play"
    4. The track will start, sometimes, but always at the START of the track, not where I left off (ultra annoying if listening to a podcast)

    Oh, and there's the times when the car stereo is OFF, but it connects to the Android, who instantly starts playing the track because "play on connect" is on, even though the stereo is off. Fuuu...

    Then there's the whole "back/next" thing. They work, but the process used to be this:

    1. Press NEXT
    2. iPhone goes NEXT instantly
    3. The track starts playing instantly
    4. The track shows up on the dash instantly
    5. Lorne can instantly (less than 0.5 seconds) tell if he wants to listen to this track or press NEXT again

    The process now is:

    1. Press NEXT
    2. 1 second elapses
    3. The Android goes to the next track
    4. No sound for 0.5 seconds
    5. Sound
    6. The dash says "SAMSUNG GMWHATEVER"-- the name of the phone, not the track
    7. Another 1-2 seconds elapse
    8. The name of the song FINALLY appears on the dash
    9. So rather than 0.5 seconds into the song, it's now 5 seconds in that I decide if I want to listen to this or not

    What sort of goddamn Rube Goldian hamster wheel of shit is going on that makes switching tracks a FIVE SECOND LONG ordeal?

    oh oh oh and the best for last. Remember that super cool button on my car stereo that lets me browse the playlists (well, actually, ALL the tracks by artist or album or whatever, but let's just go with playlist for now). That button doesn't work on Android because there's some different fucking protocol or something. A2DP I think. It either does or doesn't support it meaning the only thing it'll respond to is PLAY STOP NEXT BACK (poorly, as we noted)-- but no file browsing.

    HOW THE IDIOTSHIT is "respond to a protocol" such a hard fucking thing to do, Android. The iPhone 4s that came out in 2012 does it. Android's been out since 2005. How the shit have you idiot fuckers not figured this out?

    New tagline for this OS. Android: Does Everything. Half-Assed and Poorly.

    That could not be any different than my experience using in-car Bluetooth. My Pixel (and the 6P before that) are exactly like the iOS experience, only they also launch Android Auto

    Or maybe that's because it works that way only if you have an Android Auto-compatible vehicle? Not every car is.

    Nope, I have a Note 3 running an S8 ROM and in my old car with an aftermarket stereo it worked as expected. Start car and Spotify starts playing where I left off without taking my phone out my pocket.
    My new car has a user-hostile Ford central entertainment thing that in spite of being crap works just the same.

    I'd say the problem is with the radio in that car.


  • Impossible Mission Players - A

    @cursorkeys said in What the fuck, Android:

    the problem is with the radio in that car.

    Agreed. My mom's Jeep technically plays Bluetooth. But your device needs to already be playing music when you switch to it, it must manually connect from the phone (ie the Jeep won't seek out a phone to connect to, ever), and when it does connect (and is playing sound) you have to manually switch over to Bluetooth. This process can take as long as 30 seconds, meanwhile the stupid unit is happily blasting FM radio while I patiently wait for it to be able to start playing my music.


  • Dupa

    @cursorkeys said in What the fuck, Android:

    @kt_ said in What the fuck, Android:

    @sloosecannon said in What the fuck, Android:

    @lorne-kates said in What the fuck, Android:

    So Android has managed to fuck up any goodwill I had for Bluetooth.

    When I was carrying around the iPhone, I paired it to my car stereo. It was great. I would get in the car, turn on the car, and my music would start playing. I turn off the car, it stops playing. I hit BACK or NEXT on the car stereo, and the track goes BACK or NEXT right away. There's even a button that lets me browse the playlists on the phone so I can easily switch.

    Now comes the Android. I sit in the car and turn on the car. One of a few things will happen:

    1. Nothing, because I don't have the device set to "play when connected"
    2. Nothing, because I DO have the device set to "play when connected", but since the car stereo was off when it connected, it's now playing into nothing, even if I turn the stereo back on. Now I need to switch off of BLUETOOTH AUDIO then back on.
    3. Nothing, because I DO have the device set and the stereo was on, and the track is showing on the dashboard, but I still have to press "Play"
    4. The track will start, sometimes, but always at the START of the track, not where I left off (ultra annoying if listening to a podcast)

    Oh, and there's the times when the car stereo is OFF, but it connects to the Android, who instantly starts playing the track because "play on connect" is on, even though the stereo is off. Fuuu...

    Then there's the whole "back/next" thing. They work, but the process used to be this:

    1. Press NEXT
    2. iPhone goes NEXT instantly
    3. The track starts playing instantly
    4. The track shows up on the dash instantly
    5. Lorne can instantly (less than 0.5 seconds) tell if he wants to listen to this track or press NEXT again

    The process now is:

    1. Press NEXT
    2. 1 second elapses
    3. The Android goes to the next track
    4. No sound for 0.5 seconds
    5. Sound
    6. The dash says "SAMSUNG GMWHATEVER"-- the name of the phone, not the track
    7. Another 1-2 seconds elapse
    8. The name of the song FINALLY appears on the dash
    9. So rather than 0.5 seconds into the song, it's now 5 seconds in that I decide if I want to listen to this or not

    What sort of goddamn Rube Goldian hamster wheel of shit is going on that makes switching tracks a FIVE SECOND LONG ordeal?

    oh oh oh and the best for last. Remember that super cool button on my car stereo that lets me browse the playlists (well, actually, ALL the tracks by artist or album or whatever, but let's just go with playlist for now). That button doesn't work on Android because there's some different fucking protocol or something. A2DP I think. It either does or doesn't support it meaning the only thing it'll respond to is PLAY STOP NEXT BACK (poorly, as we noted)-- but no file browsing.

    HOW THE IDIOTSHIT is "respond to a protocol" such a hard fucking thing to do, Android. The iPhone 4s that came out in 2012 does it. Android's been out since 2005. How the shit have you idiot fuckers not figured this out?

    New tagline for this OS. Android: Does Everything. Half-Assed and Poorly.

    That could not be any different than my experience using in-car Bluetooth. My Pixel (and the 6P before that) are exactly like the iOS experience, only they also launch Android Auto

    Or maybe that's because it works that way only if you have an Android Auto-compatible vehicle? Not every car is.

    Nope, I have a Note 3 running an S8 ROM and in my old car with an aftermarket stereo it worked as expected. Start car and Spotify starts playing where I left off without taking my phone out my pocket.
    My new car has a user-hostile Ford central entertainment thing that in spite of being crap works just the same.

    I'd say the problem is with the radio in that car.

    Or with the stock rom. So it looks like TR:wtf: is Samsung, yet again?



  • @timebandit said in What the fuck, Android:

    @lb_ said in What the fuck, Android:

    In Vanilla Android you can't rename your device at all, it's just not an option.

    Settings -> Bluetooth -> top-right menu -> Rename this device

    Doesn't do anything for me. My router still shows a random string of characters as my device's name. That only renames the bluetooth name.


  • SockDev

    @lb_ said in What the fuck, Android:

    @timebandit said in What the fuck, Android:

    @lb_ said in What the fuck, Android:

    In Vanilla Android you can't rename your device at all, it's just not an option.

    Settings -> Bluetooth -> top-right menu -> Rename this device

    Doesn't do anything for me. My router still shows a random string of characters as my device's name. That only renames the bluetooth name.

    That's no surprise: changing the Bluetooth name won't change the device name. For the device name, you need to go to Settings -> About -> Device Name.



  • @raceprouk said in What the fuck, Android:

    Settings -> About -> Device Name

    I don't have that. Android 7.1.1 on Nexus 6


  • SockDev

    @timebandit said in What the fuck, Android:

    @raceprouk said in What the fuck, Android:

    Settings -> About -> Device Name

    I don't have that. Android 7.1.1 on Nexus 6

    Really? That's what it was from 4.2, and I'm fairly sure it works that way in 6. Guess it must have changed.



  • @timebandit said in What the fuck, Android:

    @raceprouk said in What the fuck, Android:

    Settings -> About -> Device Name

    I don't have that. Android 7.1.1 on Nexus 6

    Works for me on 7.0 on an LG G6.



  • @raceprouk said in What the fuck, Android:

    @lb_ said in What the fuck, Android:

    @timebandit said in What the fuck, Android:

    @lb_ said in What the fuck, Android:

    In Vanilla Android you can't rename your device at all, it's just not an option.

    Settings -> Bluetooth -> top-right menu -> Rename this device

    Doesn't do anything for me. My router still shows a random string of characters as my device's name. That only renames the bluetooth name.

    That's no surprise: changing the Bluetooth name won't change the device name. For the device name, you need to go to Settings -> About -> Device Name.

    No such option for me. Though when I have seen it on other phones, it's read-only.


  • Impossible Mission Players - A

    @raceprouk said in What the fuck, Android:

    @timebandit said in What the fuck, Android:

    @raceprouk said in What the fuck, Android:

    Settings -> About -> Device Name

    I don't have that. Android 7.1.1 on Nexus 6

    Really? That's what it was from 4.2, and I'm fairly sure it works that way in 6. Guess it must have changed.

    I'm on 6.0.1_r68 (according to the build info), and yeah it doesn't have an option there.

    Also, apparently I'm rather horrible at Flappy BirdAndroid...



  • @pie_flavor said in What the fuck, Android:

    Let me delete the parts of that that are user error and inevitable with a touchscreen and manifest in literally every other application you use.

    "This input method is 100% reliable except for all the times when it isn't". Brillant.

    Haven't experienced this behavior.

    Oh good, so that makes you an expert at deciding if an UI element is usable.

    "I've never had a car crash, therefore airbags are 100% safe!!"



  • @sh_code said in What the fuck, Android:

    ...oh.

    I said iOS was the one that work, dork-nibbler.



  • @pie_flavor said in What the fuck, Android:

    I wouldn't know - Verizon adopts the 'fuck you, give me money' stance towards mobile hotspots, so I have to stick to tethering. The fact that they can price-lock a hardware feature is TR.

    Once again, Pie_flavor is the actual real WTF. I used Verison when I was in the States. It gave me the "lol pay u monies" bullshit. I circumvented it in seconds with a quick Google search and an app.

    Pie Flavor: the Discourse of users.



  • @lorne-kates said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    I wouldn't know - Verizon adopts the 'fuck you, give me money' stance towards mobile hotspots, so I have to stick to tethering. The fact that they can price-lock a hardware feature is TR.

    Once again, Pie_flavor is the actual real WTF. I used Verison when I was in the States. It gave me the "lol pay u monies" bullshit. I circumvented it in seconds with a quick Google search and an app.

    Pie Flavor: the Discourse of users.

    I could install an app to do a hotspot IF I could root my phone. But I'm not willing to go to that effort for a feature I'd never even use since I don't have unlimited data.



  • @pie_flavor said in What the fuck, Android:

    I could install an app to do a hotspot IF I could root my phone. But I'm not willing to go to that effort for a feature I'd never even use since I don't have unlimited data.

    I rooted my phone no problem, and I'm a :belt_onion: who still uses Firefox 22, and I managed to root my phone.

    So you like to use an inferior product, refuse to take any easy steps to make it easier to use, then actively argue with people about how that's the right way to do it.

    You are a fucking Discodev.



  • @lorne-kates said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    I could install an app to do a hotspot IF I could root my phone. But I'm not willing to go to that effort for a feature I'd never even use since I don't have unlimited data.

    I rooted my phone no problem, and I'm a :belt_onion: who still uses Firefox 22, and I managed to root my phone.

    Old phones have tried-and-true methods. New phones are more risky.

    So you like to use an inferior product, refuse to take any easy steps to make it easier to use, then actively argue with people about how that's the right way to do it.

    No, I like to use a product which is less likely to brick, refuse to take risky steps which could brick it to give it features I won't use, then actively argue about how Verizon is a piece of shit for designing it so that it's even a question.
    I prefer my updates, my non-tripped Knox, etc. If I had a second Android device which wasn't completely necessary to me, I'd root it.

    You are a fucking Discodev.

    Boy, you really like claiming that, don't you?



  • @pie_flavor said in What the fuck, Android:

    Old phones have tried-and-true methods. New phones are more risky.

    It was a new phone at the time.

    boy, you love claiming that

    I cannot help but speak the truth.



  • @lorne-kates Regardless, I'm still allowed to complain that Verizon is shitty even if I refuse to install a (risky) hack that goes around their shittiness. They should have sold me a non-shitty product in the first place.



  • @pie_flavor said in What the fuck, Android:

    @lorne-kates Regardless, I'm still allowed to complain that Verizon is shitty even if I refuse to install a (risky) hack that goes around their shittiness.

    Actually, you aren't. This is a tech forum. If you stubbornly refuse to install a (non-risky) way of solving a simple problem, it's entirely on you.

    @pie_flavor said in What the fuck, Android:

    They should have sold me a non-shitty product in the first place.

    Wrong. You shouldn't have bought a shitty product in the first place. If you bought a tech product without researching it first, it's entirely on you. Surely there must be at least one Discourse instance dedicated to cell phone reviews.



  • @lorne-kates said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    @lorne-kates Regardless, I'm still allowed to complain that Verizon is shitty even if I refuse to install a (risky) hack that goes around their shittiness.

    Actually, you aren't. This is a tech forum. If you stubbornly refuse to install a (non-risky) way of solving a simple problem, it's entirely on you.

    Actually, there are actual downsides to this, such as tripping Knox or not getting immediate Android updates anymore. The benefits do not outweigh the downsides for my use-case, especially because since this a problem I (repeat) don't have a use for solving.

    @pie_flavor said in What the fuck, Android:

    They should have sold me a non-shitty product in the first place.

    Wrong. You shouldn't have bought a shitty product in the first place. If you bought a tech product without researching it first, it's entirely on you. Surely there must be at least one Discourse instance dedicated to cell phone reviews.

    Geez, the assumptions. I got a Verizon phone because sharing a data plan with my already-Verizon parents was cheap. The ability to price-lock the hotspot is a Verizon thing, not a Samsung thing.



  • @pie_flavor said in What the fuck, Android:

    Knox

    Root uninstall it immediately, along with all the other bloat junk.

    or not getting immediate Android updates anymore.

    You will never get those anyways.

    The benefits do not outweigh the downsides for my use-case, especially because since this a problem I (repeat) don't have a use for solving.

    You only don't have a use for it because you insist on using a broken phone that doesn't do what you need it to do.

    I got a Verizon phone because sharing a data plan with my already-Verizon parents was cheap.

    Like I said, you got a phone without researching it, and got exactly what one gets when they rely on telcoms to not screw them. :thumbsup:



  • @lorne-kates said in What the fuck, Android:

    You will never get those anyways.

    I'll never get updates? Commit fallacies harder. Eventual updates != no updates.
    @lorne-kates said in What the fuck, Android:

    You only don't have a use for it because you insist on using a broken phone that doesn't do what you need it to do.

    No, I don't have a use for it because I don't have unlimited data. Are you even reading my posts?

    @lorne-kates said in What the fuck, Android:

    Like I said, you got a phone without researching it, and got exactly what one gets when they rely on telcoms to not screw them.

    I don't dispute the second half of this sentence, but I researched the phone. I don't know exactly why you're assuming I didn't.

    You can go ahead and buy me a better phone if you're so morally opposed to me having my current one. I have the model due to personal choice, and the carrier out of necessity. So remove your lawn from under me.


  • Impossible Mission Players - A

    @pie_flavor said in What the fuck, Android:

    not getting immediate Android updates anymore.

    100% of all the phones that I've owned that had a locked bootloader have had a maximum of one OS update in all the years I've owned phones. And usually said update was a year after the actual launch date of said version.

    Updates my ass.



  • @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    not getting immediate Android updates anymore.

    100% of all the phones that I've owned that had a locked bootloader have had a maximum of one OS update in all the years I've owned phones. And usually said update was a year after the actual launch date of said version.

    Updates my ass.

    I've had eight in two years. You must be :doing_it_wrong: .


  • Impossible Mission Players - A

    @pie_flavor said in What the fuck, Android:

    @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    not getting immediate Android updates anymore.

    100% of all the phones that I've owned that had a locked bootloader have had a maximum of one OS update in all the years I've owned phones. And usually said update was a year after the actual launch date of said version.

    Updates my ass.

    I've had eight in two years. You must be :doing_it_wrong: .

    Yeah, I'm the one doing something wrong when it's the carrier's phone they're supposed to be updating.

    I'd rather just root it and get my own updates, TYVM, but then "Oooh scary! Knox might trip!"



  • @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    not getting immediate Android updates anymore.

    100% of all the phones that I've owned that had a locked bootloader have had a maximum of one OS update in all the years I've owned phones. And usually said update was a year after the actual launch date of said version.

    Updates my ass.

    I've had eight in two years. You must be :doing_it_wrong: .

    Yeah, I'm the one doing something wrong when it's the carrier's phone they're supposed to be updating.

    I'd rather just root it and get my own updates, TYVM, but then "Oooh scary! Knox might trip!"

    I don't actually claim to know what it is, so I don't know whether that's a bad thing. I do know that it prevents Samsung Pay from working, but I don't use Samsung Pay. My point is that rooting the phone has unintended, detrimental side effects, and would be for a feature I don't care about.


  • Impossible Mission Players - A

    @pie_flavor said in What the fuck, Android:

    My point is that rooting the phone has unintended, detrimental side effects

    Citation needed.



  • @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    My point is that rooting the phone has unintended, detrimental side effects

    Citation needed.

    What, like potentially bricking your phone?


  • Impossible Mission Players - A

    @pie_flavor said in What the fuck, Android:

    @tsaukpaetra said in What the fuck, Android:

    @pie_flavor said in What the fuck, Android:

    My point is that rooting the phone has unintended, detrimental side effects

    Citation needed.

    What, like potentially bricking your phone?

    Charging your phone can potentially brick your phone. Receiving a text message with specially arranged characters can potentially brick your phone. Potentially speaking, someone just died.

    I don't live in fear of potential.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.