Because of breaking SDK changes (and in particular, location services changes), this results in us being unable to continue to distribute versions that work below Android version 24 (Nougat) via the play store - as of last fall. We can still build and sign a patched APK file that works on older versions (down to SDK 16, Jelly Bean according to the docs, and even SDK 15, Ice Cream Sandwich in testing!), but we'll never be able to publish it through the play store again.
This means that the change that would be required to allow I-J-K versions of Android (SDKs 15, 16,17,18, the only versions that don't do TLS 1.2 "out of the box") can't be pushed out through trusted mechanisms. The Play Store won't let us build for phones that old, and phones that old need a special patch to make secure connections to modern web servers.
I'll note that you can buy used "stumble" phones for around $20 USD that will happily support play-store updates - in the mean time, we'll do our best to keep "oldroid" working, but consider this a warning that we won't be able to keep phones lower than "N" updated, and things will continue to stop working with 10+ year old devices as Google continues to make changes and force upgrades.
For now I just hope you will be able to oublish an apk file.
A few notes:
- we're into sideload territory now, the play store won't allow support like this - loading this will be at your own discretion. Look up how to sideload an APK.
- yeah, this can't guarantee oldroid support for FOSS-only handsets. That would require an ongoing maintenance process to keep building in new libraries at creation time. I'm genuinely happy to help/coach someone who wants to do that, but I can't commit to doing that myself for the indefinite future for 10+ year old handsets.
- I have ONE real device where I can test this, and I have. It's a little wonky in that there's no way to track and confirm the TLS 1.3 download - so you'll trigger the error, it'll start downloading (make sure you have a network connection) and eventually it'll start working. I can't be sure a restart isn't required, but it shouldn't be necessary.
- I would LOVE to help get the community involved in maintaining this - there are loads of PRs between release 2.67 and the current app that COULD be ported/applied and tested (and probably rough edges that could be sanded off this hack) - but I'm not going to continue to work on this indefinitely (I have to keep maintaining and improving the current version).
https://github.com/wiglenet/wigle-wifi- ... g/pull/601
In the end both the uploads and downloads complete succesfully. So it seems just to be something cosmetic.
oh weird - just the first-time post install or continuously?
I will note that many devices rooted for FOSS can probably simply be updated to a FOSS Android image such as Lineage or Cyanogen with a TLS support stack that wasn't deprecated 10+years ago and won't need to use this binary.
Its a real shame that you cant upload the file directly from the app , I tried retrieving the CSV file and upload it from the Upload Dash Tab on the PC side its uplooaded
but hey it was a great to be able to do this via Wifi from within the APP Hoping that old Tablets can still be supported its usually the way in cheap Tablet with early Android version gets a lot of people started and generates a lot of data
Hope a solution casn be found
https://github.com/wiglenet/wigle-wifi- ... st/release
There is no solution relying on the Play store (nor will there be) - Google will no longer allow us to list apps that support 10+year old devices.
(the limitation is NOT just our app, but the whole SSL library for Android)
Who is online
Users browsing this forum: No registered users and 1 guest