I'm working on a project that requires a BLE scanner to upload data to a database over cell network. I'm thinking this would be a perfect application for a Pinephone but I am unsure where to start. I haven't been able to find any support documents on how to access the bluetooth hardware on the PP. Can anyone here point me in the right direction? I was thinking I could find some Raspberry Pi examples and go from there. I have some experience in developing for Raspberry Pi but not much.
So far, I have the Pinephone connected to my laptop via UART and have access to the phone. Thinking I can scrub something from this github repo: https://github.com/sailfish-on-dontbeevi...t-firmware but I'm not really sure what.
I got a usb-c to vga adapter, but when I use it to connect a screen to the rockpro64 it does not work.
The adapter does work if I connect it to a laptop, so the issue here is about the rockpro64.
Does anyone know how to make the adapter work for the rockpro64?
I do not see any output in dmesg when I connect the adapter to the usb-c port, but if I connect other devices to it it works properly (I have a usb-c to ethernet adapter that works fine). So the problem seems to be only with the screen adapter.
One of my interest in this board is to evaluate and experiment with the RockPro64. Is it possible, and how, to disable only the A72, and use on the A53? And I would like to have the A72 disabled from power-on. One evaluation is ARM Trustzone on the board, and as the first step want to evaluate it only with the A53.
When I turn on the phone, it flashes the LED once, then the K-with-a-gear logo shows up. The gear turns briefly, then stops, then the phone turns off again.
This is the beta edition with the stock Manjaro Plasma OS. Yesterday afternoon I updated using pacman -Syyu. Everything was good yesterday evening. The phone turned itself off overnight, and this is what I found this morning. Removing and replacing the battery didn't help. Since I can't get it to stay on for a full minute, I'm not sure how to fix this.
I'm currently in deep distress: after removing a sim card adapter, it broke one of the SIM slot contact, the bottom left one.
Since this, the id number of the SIM card is not displayed when the PIN code is asked.
So, i've two questions:
* Is this contact really needed, or does it will reduce performance or disable functionnalities?
* Can I repair it easily, since my hands are far from steadies? I've a donor board, namely a 2Go one.
Here is a picture of the butchery.
Thank you in advances, I'll be very glad if someone apease my anxiety about this.
Also, thanks to the community, devs and Pine64 for this wonderful peace of tech.
I would like to find either a wifi or Bluetooth keyboard and mouse setup to use with my RockPro64 from across the room.
I'd like to use the RP64 as a media box and computer (Kodi/TwisterOS). So the IR and USB ports will be pointing right at me.
I have the remote and IR sensor.
I'd like not to have wires on the floor from the mouse and keyboard.
What would the best choice for RP64 be, wifi, or BT?
Thanks
Hats off to everyone who's worked so hard on the PineWatch hardware and the InfiniTime OS!
I received a dev kit a couple of weeks ago and have been using the sealed watch on a daily basis. I thought I would write down some first impressions.
I found it fairly easy to upgrade to Infinitime 1.2.0. (Can't wait to try out Wasp-OS when I have a little more time). I've been keeping it connected to my moto g(7) using Gadget-bridge (installed via F-Droid).
Battery life: about 3 days.
Bluetooth drops about once a day, I can get it back by restarting the watch, force stopping gadgetbridge, and starting it up again.
Flashlight feature has been useful.
Notifications for texts, MS Teams, Outlook, etc. work great!
Watch doesn't show incoming call notifications (though an incoming call test from gadgetbridge's debug screen works just fine).
Infinitime build instructions are fairly straightforward for anyone who's wrestled with building linux software packages and installing dependencies. Made a few tweaks to the digital watchface, recompiled, and uploaded with OTA over bluetooth to the unsealed watch without bricking it. The project looks very well-organized, and I'm looking forward to learning from studying and playing with the code.