Thanks to the Neptune Pine community, here’s a very clear answer and picture on resolving your wristband issues with the Pine, shown here. Thanks to Bianca Cornick and Brian Sieber!
Pine users have reported that some headsets and headphones (headset is considered a headphone with a microphone) don’t behave properly with their Pine. The Pine isn’t alone in this, as even Sony has had headsets that have the same issue.
There’s two headset standards, OMTP and CTIA. What I believe is happening is the pine uses OMTP, while the more recent standard is CTIA. Plugging a CTIA headset into a OMTP port will usually result in strange behavior (Like Google Now starting), or just not working at all.
The resolution is fairly simple, just have to use an adapter. Basically the converter will flip the GROUND and MIC poles on a 4-pole(3 black band) headset, so if the Pine is CTIA it should make your OMTP headset work, and vice versa… Like these below:
Calibrating a smartphone battery doesn’t technically make it last longer. What it might do is ensure that the battery level display is more accurate, so that when it says it’s at zero, it’s actually at zero.
I noticed that when I first got the Pine, the battery % behaved strangely (sudden sharp dip in consumption, even though activity hadn’t changed on the device, charging jumped from 15% to 40% in a matter of minutes, etc..)
Is the battery on your Pine behaving funky, or maybe you don’t want to go through days of multiple charge/discharges before the battery stats settle in? Try this:
You must have rooted your Pine.
- Download Root Explorer. Install.
- Charge the Pine to 100%.
- In Root Explorer, navigate to /data/system.
- Delete batterystats.bin
- Unplug and let the Pine fully discharge.
- Charge the Pine to 100% “offline”.
- Do this by shutting down your Pine, and plugging it in.
- Once to 100%, unplug, power-on, enjoy. 🙂
Latest beta of SWAPP Link Pine Companion app
Stock ROM is located here in case anyone needs it, or if any enterprising developers would like to leverage it->
First out of the gate- I don’t work for Neptune. I’m not affiliated with them in any way, nor do I communicate with them in any professional capacity. These are my opinions based on technical facts, and just my assumptions given my work in the Software and Hardware industry.
I wanted to write this up to answer the questions around why *I think* Neptune eventually cancelled their iOS Companion App. There’s two sides to the coin probably, general knowledge, and then of course the hard requirements to work with an iOS device.
Here’s my take, which are ASSUMPTIONS. Again, I don’t work for Neptune-
- Development knowledge. Neptune didn’t/doesn’t have any in-house software developers. I think this is the case based on the largely unmodified version of Android on the Pine, and the lack of any homegrown apps on their part to go with the Pine. Given this factor, I can see how it’s very easy for them to have looked at similar devices (ie- the Pebble), and assume this task would be completely possible for the Pine.
- Priorities. We don’t really know how many iOS users backed the Pine wanting to use it as a companion device. My gut feeling is that it’s a low number compared to the community of people that wanted Android pairing, or to use it as a standalone device. Maybe not, I don’t think Neptune ever did a survey, so it’s hard to say.
Now for the hard fact- Apple Notification Center Service. Let’s look at the requirement for Apple’s Notification Center Service that was updated to include rich notifications in iOS 7 last fall:
- Bluetooth Low-Energy. This is the baseline hardware requirement. If the accessory device does not support BTLE, then you’re out of luck.
- But the Pine has BT 4.0! Yes, the hardware supports BT 4.0. BUT- the OS version/drivers on the Pine do not support BTLE. Android 4.3 is the first revision of Android to officially support BTLE.
So there you have it, regardless of management or poor assumptions made by Neptune- it’s ultimately a hardware requirement in iOS that prevented Neptune from accomplishing this task. Could they have done more homework before stating compatibility? Should they have stated things differently in the KS campaign? Yes, probably.
It’s clear to me that their main goal with the Pine is that it is a STANDALONE device, in the form-factor of a SmartWatch. That’s the main vision for the product, which they surely have accomplished. Chalk this lesson up in the list for when they do a post-mortem of their first product, which I’m sure they’ve learned many valuable lessons from.
Lastly, my personal opinion? I think it’s awfully silly to want to pair a iPhone with an Android phone. Just my two cents.
I’d been slow to put this up, but here is the permalink to the download and steps to utilize your SD card for Apps on the Pine!
For those adventurous users out there, Cyril is working on a major revamp of SWAPP Link. Below is the link for the beta APK:
For those who haven’t installed SWAPP Link via Playstore, this is the latest version of SWAPP Link.
New in this Version:
Toggle Wifi, Wifi Hotspot, 3G Data and BT
Set Ringer mode
Set Ringer Volume
Turn Flashlight on (will turn off after 30s if not turned off before)
Turn Screen on
Launch Google Now (and turn screen on)
(Settings and actions will be shown if the remote device support them)
Custom cut and fit perfectly for the Neptune Pine:
Hat tip to Robert Wosner!