Not working on Android 6.0

[ArkfrostLumas]

So... Apart from the fact that it is working for nobody as a 'just install the apk' app, but you have to:

1. Join a Telegram group to download the apk, where you cannot ask any questions as the admins have locked the group.

2. Follow an obscure guide that only works with rooted phones and needs Titanium Backup

...it is still not working for me. Here's that "guide" again:

1. Install the newest Original Jodel Client from the PlayStore and restore your Karma with Gdrive when you need it.
2. Save Jodel with Titanium Backup
3. Go to /data/system/users/0/ and open settings_ssaid.xml
4. Search "tellm" and copy the App ID (Example: ) The id is the strings with letters and numbers, in my example is 92ecb513362131bb my ID.
5. Delete Jodel
6. Install an older or the newest Version of JodelPatched but dont open it.
7. Turn of Internet connection.
8. Open Jodel Patched and give Phone permision.
9. Close JodelPatched.
10. Go to the File in step 3 and Replace the id with your id you saved in step 4. Important: Replace both IDs in this line with your copied id even if the ids are different.
11. Reboot ur Device
12. Restore Jodel Data with TB. But ONLY Data, not the App
13. Turn your Wifi or mobile data on
14. Start Jodel
15. Enjoy

I already get stuck at point 3. The path data/system/users/0/ doesn't exist on my phone and neither does the file settings_ssaid.XML
I am using android 6.0, so I don't have this file.

Also, you might consider renaming your app to JodelHacked, the way you have to do such obscure recoding to get it to run >_>

Very user-unfriendly and not worth the trouble for the majority.

[krokofant]

At this stage in the project we're very limited as to what we can do with the application since Jodel improved their obfuscation. What we currently provide is a continuously updated apk with the latest signature keys.

Join a Telegram group to download the apk, where you cannot ask any questions as the admins have locked the group.

When it comes to redistribution of someone else's property the history speaks a clear language. We've wanted to avoid mixing the version control of the (open source) patches and any (re)distribution of the app. If you've been a developer you might just have applied the patches yourself but a large majority of our users have not been developers.

The user group was muted because the same types of questions arouse all the time and we don't have the means to support any user. If it works it works.

Follow an obscure guide that only works with rooted phones and needs Titanium Backup

Personally I have not needed root to use this app. The only parts that intentionally required root was the account backup feature. I cannot speak to the success rate of the community-provided workarounds.

Also, you might consider renaming your app to JodelHacked, the way you have to do such obscure recoding to get it to run >_>

Before JodelPatched there was JodelXposed which utilised the Xposed framework. JodelPatched on the other hand has been made by applying patches onto the actual apk. We have not hacked Jodel and wouldn't want to imply anything of the sort.

Very user-unfriendly and not worth the trouble for the majority.

I agree, and perhaps this should be emphasised in the readme. If it works it works - and besides our efforts to update the app with newer keys - development has come to a halt.

[ArkfrostLumas]

At this stage in the project we're very limited as to what we can do with the application since Jodel improved their obfuscation. What we currently provide is a continuously updated apk with the latest signature keys.

I would mention that on the GitHub page, as long as this problem is resolved.

When it comes to redistribution of someone else's property the history speaks a clear language. We've wanted to avoid mixing the version control of the (open source) patches and any (re)distribution of the app.

I'm not very familiar with the legal status on this topic, but what you're doing is simply the same thing as WhatsApp+ did back then with WhatsApp. You are not selling JodelPatched and neither does Jodel sell the app. You're simply providing a forked, updated version of it. Basically an alternative client. More or less like Comodo Dragon as alternative to Google Chrome.

Personally I have not needed root to use this app. The only parts that intentionally required root was the account backup feature.

Well, as I have never used the app, I didn't know, it works without root at all, since in the Play Store even the title of the App already says "Titanium Backup - ROOT Needed".

I cannot speak to the success rate of the community-provided workarounds.

So this is just a community workaround. Are there any solutions on the Dev side in regards of that "Can't Connect to the Internet" HTTP Error that always pops up on several phones, blocking the app altogether?
As mentioned before, I don't have the file mentioned in that weird community workaround.

Before JodelPatched there was JodelXposed which utilised the Xposed framework. JodelPatched on the other hand has been made by applying patches onto the actual apk. We have not hacked Jodel and wouldn't want to imply anything of the sort.

If that's where you coming from, then I have to admit, the naming is reasonable. I also took that workaround written by a community member as official workaround, so my mistake there.

I agree, and perhaps this should be emphasised in the readme. If it works it works - and besides our efforts to update the app with newer keys - development has come to a halt.

It definitely should have a disclaimer, that currently you can't guarantee it working on several devices, due to recent official updates, that make JodelPatched cause errors on several devices.

[kontez]

What we currently provide is a continuously updated apk with the latest signature keys.

Hei @krokofant sorry for hijacking this issue, but I saw that you mentioned this and I didn't want to open another one.
Is there an ETA for a new working version? Currently stuck on 477. However, I tried extracting from the new apk using OJOC but it didn't work out as expected.

Thanks for any updates and keep up the hard work!

[Daedra22]

Hey @krokofant and @kontez same issue for me, 477 error since version 5.15.* and 5.16.1.
@krokofant do you have any idea how to deal with it?

Thank you for your effort!

Kind regards!