| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,884
» Latest member: Instapro1
» Forum threads: 16,322
» Forum posts: 117,406
Full Statistics
|
| Latest Threads |
New Pinetab- error when a...
Forum: PineTab Software
Last Post: Raik
4 hours ago
» Replies: 1
» Views: 269
|
Systemupgrade fails
Forum: PineTab Software
Last Post: Raik
6 hours ago
» Replies: 0
» Views: 7
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: wdt
11 hours ago
» Replies: 1
» Views: 64
|
wifi password wont save
Forum: General Discussion on PineTab
Last Post: WEF
02-24-2026, 06:47 PM
» Replies: 2
» Views: 328
|
Powering two disks from R...
Forum: RockPro64 Hardware and Accessories
Last Post: evilbunny
02-24-2026, 04:43 PM
» Replies: 3
» Views: 256
|
Castle Game Engine on Pin...
Forum: General Discussion on PineTab
Last Post: michalis
02-24-2026, 04:39 PM
» Replies: 3
» Views: 3,249
|
ATTN: Pine 64 Marketing D...
Forum: Rock64 Hardware and Accessories
Last Post: georgegohl888
02-24-2026, 04:01 AM
» Replies: 5
» Views: 10,453
|
http://pinenote.mweigand....
Forum: PineNote Software
Last Post: HippopoStar
02-23-2026, 05:58 PM
» Replies: 1
» Views: 817
|
OpenClaw
Forum: Linux on Rock64
Last Post: keithy
02-22-2026, 11:57 AM
» Replies: 0
» Views: 184
|
Wi-Fi Issues (Plasma and ...
Forum: Manjaro on PinePhone
Last Post: krissprat73
02-20-2026, 12:16 PM
» Replies: 11
» Views: 17,985
|
|
|
| "no network devices available" |
|
Posted by: junefish - 01-21-2022, 09:11 PM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
 |
Wifi was working a few months ago on Debian 9, but then I didn't use it for a few months. The wifi was connecting but not getting any IP address (no other issues for other devices), and it was so out of date that I wanted to flash anyway. I booted to Kali via USB a week ago, and the wifi worked fine.
Today I started trying to flash SD > EMMC and had a few images fail to boot from SD. Now I'm using a validated image from [Kali](https://www.kali.org/get-kali/#kali-arm). I'm not sure what I changed to make this happen, unfortunately, but now I don't have any network devices via boot to EMMC or SD/USB.
Not sure what other info is needed to help troubleshoot this. TIA!
|
|
|
|
| Boot order |
|
Posted by: Barugon - 01-21-2022, 05:36 PM - Forum: General Discussion of PinePhone Pro
- Replies (13)
|
 |
I just read on the wiki that the PinePhone Pro EMMC has a higher boot priority than the SD card. Why did you do this? I have had several installations on the PinePhone become unbootable after an update and this means that the first time that happens, my phone becomes a paperweight.
|
|
|
|
| Implementing ANCS |
|
Posted by: wanderer_ - 01-21-2022, 04:21 PM - Forum: Development Discussion on PineTime
- Replies (2)
|
 |
For those of you who don't know, Infinitime does not work out-of-the-box with iPhones - like, at all. This is because Apple uses a proprietary service for notifications and music control, but it seems to be documented. I want to get cracking at this, but I'll be honest: I have basically no experience working with BLE. If anyone here has any suggestions on the direction I should go, your help would be much appreciated.
Here is the situation as I understand it:
a. Infinitime (on which I will be basing my work) is not set up to advertise like a regular BLE device.
b. If I am not mistaken, ANCS requires the NC (notification consumer) to be advertised like a regular device, so that iOS can do its GATT thing. If I am again not mistaken, this is why 3rd party apps cannot bond the watch with the phone.
I plan to make a quick-and-dirty (but working) script on a computer, learning as much as I can for the real thing.
My ultimate goal is to have working code in a pull request in the Infinitime Github.
Like I said, any ideas, thoughts, or notable resources would be invaluable, wish me luck.
|
|
|
|
| How to use "ufw" firewall with Waydroid? |
|
Posted by: tk1107 - 01-21-2022, 10:14 AM - Forum: Arch Linux on PinePhone
- Replies (1)
|
 |
Waydroid is still unbelievable. No problems. I can access the internet fine with my firewall "ufw" disabled. When I enable "ufw", I get no connection. I tried some basic allow rules for ufw and tried to allow the IP address listed on the "About" page inside Lineage OS, but still no luck. Before I break something, I wanted to ask for advice.
What do I need to do to let Waydroid through "ufw" (firewall) and access the internet? I have a VPN running, but there are no issues with this at all. I am comfortable with working in the terminal and I know about the rules file in /etc/ufw. Will there be some "routing" rules and if so, what would they be? When I looked a my network, I saw "waydroid0" along with "wlan0" and the rest.
Thanks for your time.
|
|
|
|
| keyboard and usb-c |
|
Posted by: oihantto64 - 01-21-2022, 09:56 AM - Forum: PinePhone Hardware
- Replies (17)
|
 |
Hello,
I have a pinephone with arch phos. Since I installed the pine 64 keyboard on my pinephone, the usb-c dock no longer works: neither the usb jack nor the rj45 jack, is it a hardware incompatibility or a software problem?
|
|
|
|
| LTE Modem option |
|
Posted by: bcnaz - 01-21-2022, 12:20 AM - Forum: PineTab Hardware
- Replies (1)
|
 |
Any news on the LTE modem option for the PineTab ?
It would be handy to not be limited to wifi for connecting, calls would be a bonus.
In an older thread, they had said the LTE modem was going to be available in the future,
as a user installed option for the PineTab.
|
|
|
|
| Very low battery (but charging) causes boot failures |
|
Posted by: Phillip Bell - 01-20-2022, 07:08 PM - Forum: General Discussion on Pinebook Pro
- Replies (7)
|
 |
PBP, Manjaro+KDE Plasma, 1TB memory chip extended.
When the battery is completely dead on PBP, I plug in the standard adapter. A few minutes later, I proceed to boot. In this state, the SOC seems to fail at different points, depending on the battery level.
Sometimes, it fails before the login screen. After another attempt, it will during OS initialization (I see the Manjaro logo, then fails to terminal faults). After another attempt, it will get all the way to the login screen, but after I login, it drops to terminal faults.
The workaround is simple - just wait about 10 minutes for it to charge a bit more, and all start-up works fine.
It seems that it is tied to the level of battery that is available, and it fails at different point, if the battery is at 1%
|
|
|
|
|