deeggo wrote:I've deleted cache, deleted data, removed TT, reboot phone, reinstalled TT, no change.

I did this routine again, but then freshly searching waze forum in Tapatalk, instead of loading it from my TT account. No change.

foxitrot wrote:Does Tapatalk work for you ATM?

Still problematic for me, barely usable. That's almost 4 weeks now. Really really fed up with it.,

khaytsus wrote:I personally find that tapatalk works great on many forums but is unusable on this one. Randomly can't get into some sub forums, posts are shown over and over, randomly get thrown back to the top level forum. Again, works great on several other forums I use, none of these issues on XDA forum etc. Oh well.

Are you on Android? I've been troubleshooting with them and a fix will come in TT4.

Did you guys try today's released beta? Also, make sure you do a clean install, so remove cache and data, then app, then reinstall from PS. The last one is pretty bugfree for me.

@foxitrot you cannot make a screenshot? Cause I surely don't understand it at all.

Don't see anything scrambled there?!?

Ah, by scrambled you mean that part of the url us replaced by .... I see the same as you. Is it not because the post you quoted didn't have the full information in the first place?

cherianchris wrote:My Tapatalk keeps jumping to "Recent", when I'm trying to access my "Favourites".

MB526 ->Tapatalk 2

Did you install the very latest beta of TT4? And did you remove cache, data and app and do a fresh install? It really is necessary.

@Tim, have you contacted Amit directly about this? I have sorted our various TT problems with both Amit and TT support when I first started using the TT4 beta. I started using TT4 because TT2 gave me duplicate threads and many many other problems since April. TT4 was not different, but after waze updating their plugin on my request and TT fixing things in their v4 beta client, it all works for me now. But hey, I have no capitals in my username. Just to say, push them to get things fixed!

Yes, ArtVictorP has. They say it's a setting Waze has to change, which I - again- said to Waze.

It may have been in the champs forum, or in an e-mail. Doesn't really matter though.