Android - what's in your pocket?

For what it’s worth, this seems to be a limitation of current battery technology more than specific vendors. If you make 4 years of GOOD use on a mobile battery, consider yourself lucky. 2-3 seems to be the trend.

Just replace your S7 battery. You can get the replacement and tools for it online, it’s cheap, and you’ll be back in business.

EDIT: Sorry … S7, get it replaced at any repair point. Not as cheap but I forgot they are soldered in I think.

To be fair, the S7 Edge has pretty decent battery life. Better than the S7’s, anyway. I’d still rather it was thicker and longer lasting, but it’s the best in terms of performance v battery life I’ve had since I went from N95 to Android.

Check out this video comparing the Lenovo P2 with the Samsung S7 Edge, this is what I am talking about:

When I go into the city I use a battery pack case for my S7 but it makes it very heavy and bulky. I am just asking for a P2 with slightly better specs and no gimmicks.

Oh, sure, there’s much better battery life to be found on lower spec phones. It’s my main complaint about the big manufacturers’ flagship strategies. Nobody does a “Droid Maxx” type variant of the top-of-the-line phones and it’s infuriating. I’m just saying that, as flagships go, the S7 Edge is better than most on that front.

So after getting Android 7 I can no longer bluetooth connect to my WIthings Smart Body Analyzer.
did the “Debug Log Dump” from the phone to my email and sifted through loads of log files and saw it complaining during BT handshaking about “KNOX SDK” v2.4 vs v2.7 or something.

Didn’t spend much time troubleshooting it, but I no longer have the “smart” part in the “body analyzer”. (temperature sensor, air quality, fat mass, body weight…)

Correct me if I’m wrong, but I have to use the app on my phone to re-program my Withings scale each time I do a battery replacement. Hopefully whatever you have doesn’t prevent that?

The app tries to pair with the Withings scale and fails, and retries, and fails, and retries, a lot of times. Then it tells you that you can try to pair it yourself.

When you do it yourself, it will try to pair for a long time, then fail. Then you can retry.

For a brief second on one of the attempts I saw a error message related to something, but it was just a split second so couldn’t read it fully.

The log file just contains loads of these:

04-06 19:49:52.110 14856 14856 V BluetoothEventManager: onReceive :: android.bluetooth.device.action.BOND_STATE_CHANGED
04-06 19:49:52.111 14856 14856 D CachedBluetoothDevice: onBondingStateChanged :: Device [Withings WS50 26], bond state change to 10 -> 11
04-06 19:49:52.111 14856 14856 I BluetoothDevicePreference: onDeviceAttributesChanged :: Device = Withings WS50 26isBonded = 11 , mIsOnProgressAddVI = false
04-06 19:49:52.111 14856 14856 V BluetoothEventManager: onReceive ::     android.bluetooth.device.action.NAME_CHANGED
    04-06 19:49:52.114 18575 18575 D Sdl Router Service: Disconnect received. Action: android.bluetooth.device.action.CLASS_CHANGED
    04-06 19:49:52.120 17508 17519 I ContainerConfigurationPolicy: Bluetooth And NFC caller permission check
    04-06 19:49:52.120 17508 17519 D ContainerConfigurationPolicy: current version : KNOX_ENTERPRISE_SDK_VERSION_2_7_1, Required version : KNOX_ENTERPRISE_SDK_VERSION_2_4
    04-06 19:49:52.125 17508 17519 D BluetoothUtils: Utils::isKnoxBluetoothEnabled = false
    04-06 19:49:52.127 17508 17519 W BluetoothAdapterService: getRemoteClass() - Not allowed for non-active user
04-06 19:49:52.128 14856 14856 I BluetoothDevicePreference: onDeviceAttributesChanged :: Device = Withings WS50 26isBonded = 11 , mIsOnProgressAddVI = false
04-06 19:49:52.128 14856 14856 V BluetoothEventManager: onReceive :: android.bluetooth.device.action.CLASS_CHANGED
04-06 19:49:52.132 14856 14856 I BluetoothDevicePreference: onDeviceAttributesChanged :: Device = Withings WS50 26isBonded = 11 , mIsOnProgressAddVI = false
04-06 19:49:52.136  4221  4510 W BluetoothEventManager: showUnbondMessage: Not displaying any message for reason: 9
04-06 19:49:52.137 17508 17519 I ContainerConfigurationPolicy: Bluetooth And NFC caller permission check
04-06 19:49:52.137  4221  4510 I BluetoothDevice: removeBond() for device ##########  called by pid: 4221 tid: 4510
04-06 19:49:52.137 17508 17519 D ContainerConfigurationPolicy: current version : KNOX_ENTERPRISE_SDK_VERSION_2_7_1, Required version : KNOX_ENTERPRISE_SDK_VERSION_2_4
04-06 19:49:52.141 17508 17559 W bt_sdp  : process_service_search_attr_rsp
04-06 19:49:52.141 17508 17519 D BluetoothUtils: Utils::isKnoxBluetoothEnabled = false
04-06 19:49:52.142 17508 17519 W BluetoothAdapterService: getRemoteUuids() - Not allowed for non-active user
04-06 19:49:52.144 14045 14045 D GMHFPReceiver: jangil::printBTStatus()
04-06 19:49:52.146 17508 17597 D BluetoothAdapterService: removeBond : XX:XX:XX:XX:XX
04-06 19:49:52.147 17508 17559 W bt_btif : bta_dm_search_cb.services = 7fffffff***********
04-06 19:49:52.155 17508 17597 D BluetoothAdapterService: deviceProp state is not BOND_BONDED
04-06 19:49:52.155  4221  4510 V BluetoothEventManager: onReceive :: android.bluetooth.device.action.BOND_STATE_CHANGED

Guess I can figure it out during the weekend :-)

So the bluetooth on the Withings thinks it has paired with your device before, perhaps it’s the same name you gave your old device. They are failing to pair because one thinks it knows the other.

Without looking, I don’t remember if there is a way to tell the Withings scale to forget known devices so that you can re-pair.

What you see at the top there is them attempting to pair, but failing the agreed upon passkey. They need to match. Obviously you are pairing for the first time to the Withings with your new phone, but the Withings thinks it knows the device. “Caller permission check.” After a couple of fails it looks like your phone then unbonds because of the failure.

I don’t think it is related to the KNOX error, but without a reset on your Withings, that remains to be seen. And the shity part is if that too fails, now you have a scale with zero use pretty much, as you would need to reset it to get them to bond again.

At least it’s not the Fitbit Aria which only works with wireless A.

My Withings scale uses Wi-fi, although setup may have been with BT.

What about a factory reset?

I’ll try to find the factory reset on the Withings,
cheers :)

Seems silly that the Withings,considering it has a screen, would not show anything indicating it is a pairing error. At least it could show a message that "you’ve failed to pair 10 times in the past 15 seconds (yes, it tries many many times) so, if you step on the weight, and off, and on again, you’ll reset the configuration so you can make a new pair config.

Picked up a 32GB Moto Z with the JBL soundboost yoke for the equivalent of $320.

I knew about the small battery and tall bezels, but figured it was worth a punt as my S5 was on its last legs.

So far;
The battery life is better than the S5 which is pleasant, considering just how stupidly light and thin the Z is.
The OK Moto and the Moto gesture wave are fantastic. OK moto works on any screen and with screen off, which is useful when driving. The gesture wave is sublime and I don’t think I could use a phone without it.

I haven’t noticed any lag when using the phone, nor has it had to reload background apps once. I know Stusser loves his benchmarks but I genuinely can’t see why I need a faster phone than this right now, or over the next 18-24 months.

I think you mean wumpus… ;)

stusser will happily tell you modern Android devices are plenty snappy in real world use regardless of what artificial benchmarks may suggest.

Second time today I’ve meant Wumpus but used Stusser!

Hey guys, could use your advice. My beloved Nexus 5 is clearly on its way out, so I need to get a new phone. If I didn’t have a wedding in a few months, I’d she’ll out for a Pixel, but alas.

So since I’m on Sprint, I’m eying the HTC 10 or Sansung Galaxy S8+ based on their reviews. That said, I’m also open to suggestions if anyone has any. Any thoughts on the best Sprint Android phone to get?

Thanks!

Avoid HTC.

Oh really? I was considering them because the phone had good reviews and my previous phone was an HTC Evo, which I really loved.

I would recommend the s7, you can probably get a good deal on it right now.

Ohhhhh, not the S8?

Unproven as yet and more expensive.