Pixel 9 (Pro) its so bad, wow...

The gear needed for wardriving

22 posts • Page 2 of 2

Postby arkasha » Fri Nov 01, 2024 12:17 am

Ouch, I've been side-by-siding my new Pixel 9 with my venerable Samsung Z-flip 3 for the last 24 hours.
- Throttle disabled
- Settings same or faster for scan speed
- "Keep Screen On" with a button push afterward to avoid burning up my battery immediately.
- ZFlip has an immense database from years of running (vs. the clean new Pixel 9)

The Z Flip 3 is seeing LITERALLY 3x as many WiFi networks as the new hotness. Google has absolutely nerfed these things to death.
Can you try withOUT the power button push -- as I've done more comparisons it does seem the damn screen has to be ON on for things to behave as we've been used to.
Image

Postby arkasha » Sat Nov 02, 2024 4:47 pm

I will, but it's pretty impractical for me, as a distance runner - I can't exactly leave it screen-on, plugged in.

Postby arkasha » Mon Nov 04, 2024 1:56 am

Alright WiFriends, new thing to check (maybe everyone here has already done this, and I'm late to the party- just got a recent pixel last week).

Apparently the recent Android updates started enforcing the new battery optimization system.

1. under the app battery settings for the WiGLE WiFi Wardriving app, you'll get a single row: "Allow background usage" followed by a toggle.
2. Tap the TEXT (not the toggle!) to get to the second menu, where you can permit the application "Unrestricted" background permission (effectively turning off the now-default "Optimized" behavior)
3. Restart your phone, launch the app, and rock on.

Performance is still not AS GOOD as my top stumbling phones, but it's far less grim than it was before.
Setting changed, phone rebooted, looking forward to giving this a try!
Image

Postby arkasha » Sat Nov 16, 2024 7:15 pm

Seeking confirmation:

if you look at your phone's net.wigle.wigleandroid logcat messages (requires an app or an IDE+cable) after a long run with one of these nerfed phones, do you see a lot of:

Code: Select all

culling pending queue. size: 512 culled pending queue. size now: 512 pending queue still full, couldn't add: xx:xx:xx:xx:xx:xx
blocks? It seems like maybe Google's patch isn't letting Android write or write enough with the screen off.
Curious to see how this turns out ;-)
Stratt3000 | Cana|Data | stratton.phillips@cana-data.com
Image

22 posts • Page 2 of 2

Return to “Net Hugging Hardware and Software”

Who is online

Users browsing this forum: No registered users and 8 guests