Phone app on Android Marshmallow has a contact in Favorites even though I don't contact her often OR have her marked as Favorite. Nice little glitch you have there, dev.

Oh fucking Huawei.
Fuck you.
Inventory:
- Honor 6x (BLN-L22C675)
- Has EMUI4.1 Marshmallow
- Cousin brother 'A' (has bricking XP!)
- Uncle 'K'
- Has Mac with Windows VM
Goal:
- Stock as LineageOS / AOSP

Procedure (fucking seriously):
- Find XDA link to root H6X
- Go to Huawei page and fill out form
- Receive and use bootloader code
- Find latest TWRP
- Flash latest TWRP
- TWRP not working? Bootloops
- XDA search "H6X boot to recovery"
- Find and try modded TWRP
- TWRP fails, no bootloop
- Find & flash TWRP 3.1.0
- Yay! TWRP works
- Find and download LineageOS and SuperSU
- Flash via TWRP
- Yay! Success.
- Attempt boot
- Boot fails. No idea why
- Go back to TWRP
- TWRP gives shitload of errors
"cannot mount /data, storage etc."
- Feel fucked up
- Notice that userdata partition exists,
but FSTAB doesn't take
- Remembers SuperSU modded boot
image and FSTABS!
- Fuck SuperSU
- Attempt to mod boot image
- Doesn't work (modded successfully
but no change)
- Discover Huawei DLOAD
Installer for "UPDATE.APP" OTAs
Note: Each full OTA is 2+ GB zipped
- Find, download, fail on 4+ OTAs
- Discover "UPDATE.APP Extractor"
Runs on Windows
Note: UPDATE.APP custom format
Different per H6X model
- Uses 'K''s VM to test
- My H6X model does not have
a predefined format
- Process to get format requires
TWRP, which is not working
- FAIL HERE
- Discover "Firmware Finder"
Windows app to find Huawei
firmwares
- Tries 'K''s VM
- Fails with 1 OTA
- Downloads another firmware ZIP
- Unzips and tries to use OTA
- Works?!
- Boots successfully?!
- Seems to have EMUI 5.0 Nougat
- Downloads, flashes TWRP
- TWRP not working AGAIN?
- Go back to XDA page
- Find that TWRP on EMUI 5 - NO
- Find rollbacks for EMUI5 -> EMUI4
- Test, fail 2-4 times (Massive OTAs)
- DLOAD accepts this one?!!!
- I HAVE ORIG AGAIN!!!
- Re-unlock and reflash TWRP
- Realise that ROMs aren't working on
EMUI 4.1; Find TWRPs for EMUI5
- Find and fail with 2-3 OTAs
Note: Had removed old OTAs for
space on Chromebook (32GB)
- In anger, flash one with TWRP
instead of DLOAD (which checks
compatability)
- Works! Same wasn't working with
DLOAD
- Find and flash a custom TWRP
as old one still exists (not wiped in
flash)
- Try flashing LineageOS
- LineageOS stuck in boot
- Try flashing AOSP
- Same
- Try flashing Resurruction Remix
- Same
- Realise that need stock EMUI5
vendor
- Realise that the firmware I installed
wasn't for my device so not working
- FUCK NO MORE LARGE DLs
- Try another custom TWRP
- Begin getting '/cust mounting' errs
- Try reflashing EMUI5 with TWRP
- Doesn't work
- Try DLOADing EMUI5
- Like before, incompatability
- DLOAD EMUI4
- Reunlock and reflash TWRP
- WRITE THIS AS A BREAK
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAARRRRRRRRRRRRRRRRRRRRRRRRGGGGGGGGGGGGGGGGGGGGGGGGGHHHHHHHHHHHHHH

Alpha
Beta
Cupcake
Donut
Eclair
Froyo
Gingerbread
Honeycomb
Ice cream sandwich
Jelly bean
Kitkat
Lollipop
Marshmallow
Nougat
Oreo
Pie
Q ?
R ?
S ?
T ?
U ?
V ?
W ?
X ?
Y ?
Z ?
And then?

Me: *Trying to get the mobile banking app*
App: Nope, you have a rooted device
Me: *disables root access for apps and adb*
App: Nope, you have a rooted device
Me: *Maybe a xposed module would help*
Xposed: Nope, you have android nougat
Me: *Maybe there's some LineageOS marshmallow rom for my phone*
LineageOS: Nope, just android 7.1

fml

I'm pretty sure my clients would fail the marshmallow test 9/10 times if not 10/10 times. We have a certain time period of the day set aside for me to look into new reported bugs but besides that I'm supposed to work on regular tasks. Of course, they ask me five hours after that time period is done, whether I can look into a new (non-urgent) bug. At the cost of the new thing they want to launch in 2 weeks. 🤔 I would love it if we actually had time to fix every single bug in the codebase but what typically happens is I get about 15 bug reports (most duplicates) and I'm expected to fix all of them in a span of 2 hours.

Just flashed a clean marshmallow kdz on my phone, finally running smooth after months of me raging at my phone. Hopefully I will start getting devRant push notifications now!

Wow, I didn't expect this! My phone brand (Huawei) actually updated my phone from Marshmallow to Nougat! I was so used to OEMs letting their customers die with old versions :)

Food and Programmers life:
Spaghetti —> My Code
Pizza —> We are spending the night working in the office
Power Drinks —> delivery date is tomorrow morning
Candy —> extra task
Coffee —> bug massage
Water —> wash your face, we have meetings in five minutes
Truffle —> fu** BlockChain
KitKat —> upgrade your phone please
Lollipop —> one more time please
Marshmallow —> do you like some Nougat?

That very moment! when your app is ready
but suddenly
Android Marshmallow has gone live
and every pips has updated their phones

and you forgot to implement about runtime permissions

I still have old crusty ass 5.1 Lollipop on my phone because I can't let go of the adorable blob emojis. So many good memories.

But now I can't update apps anymore -- can anyone tell a dummy like me how to upgrade from Lollipop to just Marshmallow, nothing newer (to retain the Marshmallow blobs)?

Android guys, is it true that marshmallow requires location enabled for Bluetooth pairing?

I find this popup odd.

I am using Permiso for runtime permissions in Marshmallow and up. So I spent hours finding a way to check if a user has selected "never ask again" while denying permission. And at last found it.

When your code misbehaves in production and you need all the ducks in the world to fix the problem😂😓

(Marshmallow doing some serious debugging!)

Lots of code not working, lots of job problems, lots of troubles in life, lots of sleepless nights…

But hey, I have marshmallow chocolate cookies :)

Just subscribed to devRant++ but it says there was an issue with the play store...

Moto G2 running Android Marshmallow

Which do you like Android
4.0 Kitkat
5.0 Lollipop
6.0 Marshmallow
7.0 Nougat

I found Flappy Marshmallow Droid embedded in my phone 😂😂

Not dev related really
but for mobile, do you guys know of any great tablet-compatible launchers? I got MEmu recently, and i'm not a fan of the default launcher. I found an ok marshmallow 6.0 launcher, but i wanna know if you guys use something different

Feeling bored about Android's cache issue. Since I first use ICS until Marshmallow, I still have to clear app's cache due to lack of space in my phone. :(

Devrant on Android marshmallow doesn't allow me to post images :/

Bricked my old Galaxy Tab 10.1 after trying to install Marshmallow on it.

// Sticking with code from now on

Question about conditioning my new android lithium battery.

I dont understand what's happening with my phone. Have old Xperia Z3 D6603 (running android 6.0 marshmallow).

Had problems with battery since it was not lasting even 5 minutes so bought a new battery from ebay and installed it yesterday.

So first time I put it to my phone it showed that it had 70% of charge. I've read in battery description that I have to discharge the battery and recharge 3 times.

First time I wanted to discharge from 70% to 1% and with a battery discharge app + youtube 1080p videos + wifi signal it took only around 1 hour and phone was at 1%. From 1% till complete discharge it took me extra hour and then phone died.

I plugged it to charge and after 15 minutes it showed that battery now is at 100% (which is insane, it should take 2-3hrs to charge it up to 100%). So I charget it for 2-3 hrs ignoring that it said 100% already.

I discharget it from 100% to 1% in 1 hour and now again phone is stuck at 1% and it took me 2 more hours to discharge phone until battery died completely.

I don't believe that this behaviour will fix itself. How can I fix this problem so that battery percentage would be distributed evenly? Now it drops from 100% to 1% in 1hr and then from 1% to 0% in 2 hrs.

which type are you ??

**Manager:** Hey, we've got a little hiccup in the production environment. I know it's Friday evening and you're probably daydreaming about pizza, but could you give it a peek?

**Type 1:** Man, this is like finding a needle in a haystack while wearing sunglasses at night. Might take me a few hours... or days. But hey, wish me luck and have an epic weekend!

**Type 2:** Eureka! Found the gremlin. It looks like XYZ person tried to be a bit too creative on commit number 2234324. Maybe they had too much caffeine? Anyway, could you have a chat with them? And oh, may your weekend be as smooth as a fresh jar of peanut butter.

**Type 3:** Detective mode activated! Found the sneaky bug. It was XYZ person's "masterpiece" in commit number 2234324. But fear not! I've put on my superhero cape and fixed it in commit number 345453345.

**Type 4:** This issue again? It's like a recurring bad dream about forgetting your pants! I've revamped the whole thing so we don't have to relive this nightmare. If someone tries to pull this off again, our CI/CD will roast them like a marshmallow over a campfire.

**Type 5:** Ta-da! Fixed the glitch, jazzed up the design, and sprinkled in some extra logging magic. Now, troubleshooting will be as easy as pie. Speaking of which, I've got time for a coffee and maybe a slice of pie before heading out. Cheers!
Type 6 **Gloomy**: Oh, the digital clouds have gathered again. This issue is like a never-ending rain on a Monday morning. I've peered into the abyss of our code, and it's... well, it's deep and dark. I'll need some time, a flashlight, and maybe a comforting blanket. If you don't hear from me in a few hours, send in a search party with some hot cocoa.