| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,205
» Latest member: Karen68
» Forum threads: 16,384
» Forum posts: 117,596
Full Statistics
|
| Latest Threads |
Hardware Feature Suggesti...
Forum: Quartz64 Hardware and Accessories
Last Post: Independent Researcher
9 hours ago
» Replies: 0
» Views: 23
|
Single-board computers an...
Forum: General
Last Post: Spaker
08-29-2026, 08:12 PM
» Replies: 0
» Views: 65
|
Pinephone visibly losing ...
Forum: General Discussion on PinePhone
Last Post: baptx
08-29-2026, 11:18 AM
» Replies: 9
» Views: 8,380
|
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
08-28-2026, 01:32 AM
» Replies: 1
» Views: 12,775
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 125
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 189
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,627
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 393
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,040
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 175
|
|
|
| TicWatch Pro 2020 with Ubuntu Touch as a PineTime Pine64 device? |
|
Posted by: Peter Gamma - 09-21-2020, 11:41 AM - Forum: General Discussion on PineTime
- Replies (8)
|
 |
I m interested in Linux watch. I cam across the TicWatch Pro 2020. Posting here is a bit off-topic, but what makes a Pine64 device a Pine64 device? Does it need an Allwinner A64 processor?
I compaired the specifications of the PinePhone, the PineTime and the TicWatch Pro:
The PinePhone uses an Allwinner A64 processor, which has four Cortex-A53 cores clocked at 1.152GHz and a Mali-400 MP2 GPU. Its frame and case cover is made of plastic. It contains a 5 megapixel back camera and a 2 megapixel front camera and a USB-C port with USB 2.0 that supports DisplayPort alt-mode
PineTime Smartwatch - Display: IPS capacitive touchscreen, 1.3 inches (240 x 240 resolution)
- Communication: Bluetooth 5 Low Energy.
- Sensors: Accelerometer and Heart Rate Sensor.
- Battery: LiPo 170-180 mAh.
- CPU: 64MHz ARM Cortex-M4F.
- SoC: NORDIC Semiconductor nRF52832 (or nRF52840)
TicWatch Pro 2020 specifications - Processor: Qualcomm Snapdragon Wear 2100
- Display: 1.39 inches AMOLED with 400x400 pixels resolution Gorilla Glass 3
- Operating system: Google Wear OS
- RAM: 1GB
- Storage: 4GB internal storage
- Bands: 22mm leather/silicone hybrid
- Connectivity: Bluetooth 4.2 LE, 801.11 b/g/n WiFi, GPS/Galileo/GLONASS/Beidou, NFC
- Sensors: Accelerometer, Heart Rate Sensor, Gyro Sensor, Geomagnetic Sensor, Ambient Light Sensor
- Rugged ratings: IP68 dust/water resistant rating and MIL-STD 810G shock resistance
- Battery: 415 mAh non-removable
- Dimensions: 45 x 45 x 12.6mm and 222 grams
- Colors: Shadow Black and Liquid Metal Silver
There is custom ROM for the TicWatch Pro available. It is quiet advanced with 402 pages:
https://forum.xda-developers.com/smartwa...13/page402
The TicWatch Pro has a touch display, and it should be possible to run Linux on Android on it, and therefore Ubuntu touch on Android. With such an advanced custom ROM, it should also be possible to access the watch buttons and control those from Ubuntu touch.
What do you think about this project?
|
|
|
|
| Extracting a copy of SPI NOR flash contents using micro SD card and u-boot |
|
Posted by: hmuller - 09-21-2020, 11:24 AM - Forum: Pinebook Pro Tutorials
- No Replies
|
 |
This is a bonus. Using the previous post:
https://forum.pine64.org/showthread.php?tid=11567
A 32M sized micro SD card image should be sufficient to extract a full copy of SPI NOR flash contents. I performed the following successfully using a 64M sized image to extract a full copy of SPI NOR flash from u-boot prompt with micro SD card inserted:
Code: => sf probe 1:0
=> sf read $kernel_addr_r 0x0 0x1000000
=> save mmc 1:1 $kernel_addr_r spi_full.img 0x1000000 0
This will save the contents of your flash to the micro SD card, the file will be named 'spi_full.img'. You can then view the image using your favorite tool. As an example:
Code: $ xxd /path/to/spi_full.img | less
|
|
|
|
| Program SPI NOR Flash on Pinebook Pro with u-boot on micro SD Card |
|
Posted by: hmuller - 09-21-2020, 10:02 AM - Forum: Pinebook Pro Tutorials
- No Replies
|
|
Hello again!
Administrative: I apologize in advance for posting the actual instructions offsite as I have yet to figure out how to format headings using bbcode. If I ever figure it out or it becomes possible I will bring the content back over here. The instructions may be found at the link at the end of this post.
This process allows you to program/erase the Pinebook Pro (PBP) SPI NOR flash (flash) using u-boot on a micro SD card.
- The user is still required to remove the back cover to turn the eMMC switch off and the UART switch on.
- The user is also required to connect to the PBP over USB serial UART from a host machine (Rock64 with keyboard and monitor for example).
- You cannot use this process to recover from writing bad images to the flash though, you would still have to short the pins on the flash to boot from SD card again in this instance.
It is possible automatically write to flash using a boot.scr script (i tested this) but this is left as an exercise for the user. This also highlights why I think it is preferable for SD card to be at the bottom of the boot order and not at the top.
The mainline u-boot version as of this writing is 2020.10-rc4-g9de3126e. These are some observations I have made that you may find useful:
- The SPI flash is not automatically detected. I am not a u-boot expert yet but I assume it is because an alias for 'spi0 = $spi1' is missing from the device tree. And I additionally assume this is because rk3399-pinebook-pro-u-boot.dtsi does not #include rk3399-pinebook-pro.dts. I tested this theory by temporarily adding the alias to rk3399-pinebook-pro.dts and the SPI was detected (should have also tested by adding the #include to rk3399-pinebook-pro-u-boot.dtsi).
- CONFIG_ENV_OFFSET is set too low. CONFIG_ENV_OFFSET is automatically set to 0x140000. uboot.itb is written to 0x60000 and its current size is 949936 (928K) bytes which overlaps with 0x140000. If you want to safely saveenv you will need to set CONFIG_ENV_OFFSET to 0x150000. You could also place it at the end of SPI ((16M bytes - 1 byte) - 32K bytes).
You can find the instructions at this link:
https://gist.github.com/hxmuller/f1091f9...f893747482
Please reply to this thread for any questions or comments on the document found at the link above. Thanks!
|
|
|
|
| Pinebook Pro won't connect to wifi |
|
Posted by: Samuel Venable - 09-21-2020, 05:30 AM - Forum: General Discussion on Pinebook Pro
- Replies (4)
|
|
No matter what I do, I can't connect to wifi. I replaced the built-in Manjaro KDE Plasma with Manjaro Xfce. I'm using the wifi menu widget on the task bar to select my router, entered the correct password a million times, and it just pauses a great while trying to connect and then asks me to enter a password again. Does it every time.
This is the only device in my house that has this problem. I've used Wifi on my Pinephone, my android, and like 4 other computers, and my family has other devices with working internet. I've tried reconnecting to internet on a few of these devices and it worked. My new Pinebook Pro is the only device that refuses to connect to internet.
This has been happening for a full week now. I haven't even been able to use it effectively without internet. Without internet, it's extra space being used up in my house that I don't need if it won't work. (i bought a table for it)
Pretty frustrated, to be honest, because I'm pretty sure my 30 day warranty expired by now.
To top it all off, can't reinstall the operating system it came with, (or any operating system made for it, for that matter), because the micro sd card reader isn't reading my micro sd card. So unless I can fix wifi, I'm basically screwed.
Though a separate issue, it would be nice to have the micro sd card reader working again, too. Not sure if that will ever happen, either?
I'm a developer who ports my software to a lot of operating systems, including windows, mac, linux, freebsd, and I would like to get netbsd or openbsd working on my pinebook pro since my other machines are being used for other things at the moment and can't have their os replaced easily right now without being a big sacrifice.
Any help is appreciated, like you have no idea!
Samuel
|
|
|
|
| Camera app down, megapixels up |
|
Posted by: daniel - 09-20-2020, 09:10 PM - Forum: Mobian on PinePhone
- Replies (4)
|
|
Today I apt update and check what is new.
Camera app was black (don't remember if it was before upgrade)
I saw a new app, megapixels
This is much smoother than camera app. However, button didn't take any picture...
Not working yet, but at least something moving here...
|
|
|
|
| Pinephone dock with Pinebook Pro? |
|
Posted by: karlnicholas - 09-20-2020, 06:32 PM - Forum: Pinebook Pro Hardware and Accessories
- Replies (2)
|
|
Has anyone attempted (or had success) using the usb-c dock from the Pinephone convergence package with their Pinebook Pro?
I've been able to use it as a usb hub, but I have not gotten the HDMI out to work (I haven't had a chance to try the ethernet jack yet, that's on my to-do list).
I know there have been issues with PMOS and the HDMI on the dock, but I don't know if the the pbp would have the same issues (I'm running the out-of-the-box Manjaro on it).
|
|
|
|
| Kings Cross disappeared |
|
Posted by: bobblestiltskin - 09-20-2020, 04:45 PM - Forum: Mobian on PinePhone
- Replies (8)
|
|
I used 'Kings Cross' as my terminal under mobian.
Last week sometime it disappeared from my phone.
How do I re-install it? I can not see it under Utils in Software, nor does 'apt search cross' yield anything that looks suitable.
I did manage to install 'Terminator' but prefer 'Kings Cross' because I can access <ESC> and <CTRL> from the keyboard in 'Kings Cross'.
|
|
|
|
|
