So after three days FINALLY I was able to make the fragment NOT reload itself when going back to it from the second fragment. Used show() and hide() in fragmentTransaction. Yayyyy! :D

Dealing witt activities and fragment lifetimes is painful

Soon lifecycle support lib will solve this shit for us, and livedata, you can check their alpha release if you want on Google developers website

What I did for multiple fragments was using a pager system there's a couple of code snippets for non scrollable pages, of you want to have a button press for next page type thing.

This way you can just use an array based system to load page fragments.

Not 100% if this is a good idea but seems to work great on all devices I've tried it on.

I can send you some code snippets when I get home if ya want :D

@f03n1x that could be a great hack! :o I could never have thought of that. Sure, send me the code if you would :D, I would love to try it! I think it would work very well in the fragment changing from drawer navigation with no reloads! - backstacks aren't used there.

@scout alright well I'll send you it the moment I clean it up lol ATM it's part of my work app but I can send you separate bits for setting up the fragment container and separate fragment class for setup since that is just Google's code lol

@f03n1x haha sure, any time is ok, thank you so much, and just bits n pieces would be okay, I can set up the whole thing from that :D and I realised just now while typing this that your nickname is actually "Phoenix" lol.

@scout well just got home I'll add a codeshare link once I'm done (shouldn't be too long) I think I'd be able to just cut/paste the classes that do the setup when I did the Android app modifications I made sure to make my methods as simple as possible lol.

Also, glad you noticed lol, I use to use Phoenix as a kid but because it's so common it'd always be taken. Oh and I noticed you're also an iOS developer too, cool, I'd give you code snippets for that but the iOS code is more tightly coupled :/

@scout wow 25 mins jeez glad I made it so loosely coupled lol also only 200 lines which is awesome, tons of comments probably make up a bunch of the lines though, it's 40 mins now but that's because I was adding stuff to the codeshare link

Anyways here ya go :D enjoy

https://codeshare.io/2jeQ6A

Oh right if you haven't used codeshare before any edits you do modifies the code so best just to copy and paste it, and sorry for the poor format my laptop screen is tiny lol, oh and the code gets deleted in 14 days

@f03n1x wow thank you so much! You've documented it so well and the formatting is perfect. :D I'll try it in the evening. Thanks again! :)

@scout no worries, it's so documented because for a few months I had to wait for my boss to get legal documents from a lawyer when I was at 90% completion for the app :/ needless to say I kept bugging him for 3 months before hand and he kept putting it off, I've wasted so much time lol it sucks.

@f03n1x oh :o well I hope it's completed now lol

@scout iOS is done just waiting for some emails from the NSA LOL (seriously though if you use encryption for iOS apps you need to make a self classification report:/) and Android is 99% done expect simple button clicks crash on Samsung phones for some reason, so with crashlytics I should hopefully find out how exactly lol

@f03n1x ah okay.. I hope it goes well! iOS submission is so frustrating, the latest one that I made has been rejected three times - because they say the Facebook login feature isn't working on iPad. (Though it works on iPhone, and iPad simulator, i dunno what to do), so I removed iPad support altogether from the app and submitted it. D'you know what they did? They somehow ran the iPhone version app on an iPad and sent me a screenshot of that, saying they require it to work that way. :@ huh.

@scout wow, that sucks well I haven't even gotten to trying out the submission, literally was thinking last Friday I'd be done and waiting for iOS review but it popped up with encryption stuff right at the end... And on a flipping separate page!

I guess I'm lucky with the whole testing bit, because CEO and general manager are both apple enthusiast and have a biased opinion of Android Lol, so I guess it's a double edged blade.

Oh I think I read something that said all apps need to be supportive on both iPhone and iPad if on the app store, but I can't specifically remember if it was 100% accurate :/ still though to force it to work on iPad is a joke :/