| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,466
» Latest member: Creig
» Forum threads: 16,192
» Forum posts: 116,855
Full Statistics
|
| Latest Threads |
Pinephone Pro wont boot t...
Forum: General Discussion of PinePhone Pro
Last Post: KNERD
9 hours ago
» Replies: 1
» Views: 60
|
PinePhone Pro discontinue...
Forum: General Discussion of PinePhone Pro
Last Post: KNERD
9 hours ago
» Replies: 4
» Views: 143
|
Are there plannes to crea...
Forum: PinePhone Pro Hardware
Last Post: franzthiemann
Today, 04:43 AM
» Replies: 2
» Views: 799
|
prototyping to help someo...
Forum: General
Last Post: xerosenex
Today, 02:31 AM
» Replies: 0
» Views: 38
|
Password reset via u-boot...
Forum: PineNote Software
Last Post: lunnabae
Yesterday, 01:17 AM
» Replies: 6
» Views: 1,694
|
incorporate a multimeter ...
Forum: General
Last Post: lalisa12
Yesterday, 01:14 AM
» Replies: 2
» Views: 491
|
New PineNote: No WiFi aft...
Forum: PineNote Software
Last Post: krexplex
08-12-2025, 01:09 PM
» Replies: 5
» Views: 1,415
|
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: Pattienner
08-10-2025, 10:35 PM
» Replies: 2
» Views: 474
|
Any recommended brands/mo...
Forum: Pinebook Pro Hardware and Accessories
Last Post: fnfgopro
08-10-2025, 08:38 PM
» Replies: 2
» Views: 854
|
Thoughts after a year wit...
Forum: General Discussion on Pinebook Pro
Last Post: tantamount
08-10-2025, 02:25 PM
» Replies: 3
» Views: 619
|
|
|
| Does snapchat work on pine64 with android? |
|
Posted by: user875545 - 08-25-2017, 01:04 AM - Forum: Android on Pine A64(+)
- Replies (1)
|
 |
I know snapchat despises anything but 'real' ™ factory default phones so will it work with this or not?
I would like to get one of these sbcs for mobile programming work instead of buying a smartphone since they don't have the government surveillance crap hardwired into them like phones do but if I need to run snapchat and if it wouldn't work then I would have to maybe get over my paranoid delusions and buy a normal phone for this work  .
So has anyone run snapchat successfully on it or not?
|
|
|
|
| Ephemeral RTC Settings |
|
Posted by: Siliconserf - 08-24-2017, 06:39 PM - Forum: Linux on Pinebook
- No Replies
|
|
OK, I'm sure there is something I'm not doing right, but the RTC has me stumped. I use the access point in the upper right of the Mate desktop to set the RTC to use my time zone and report time in 12, instead of 24 hour format. I do this as a user with Admin privileges. And the clock changes appropriately...until the next boot, whereupon I see that it has forgotten the settings and has gone back to defaults. The menus are very explicit about setting the system clock options. So what have I missed?
|
|
|
|
Solved - Resize Root Filesystem (Xenial) |
|
Posted by: aussiemate - 08-24-2017, 05:38 PM - Forum: Linux on Rock64
- Replies (4)
|
|
This is for those less familiar with Linux, or running Linux from an SD card.
When you flash Ubuntu Xenial onto an SD card, the root filesystem size is only big enough to fit the operating system.
This is intentional; to keep the size of the image file as small as possible, making it quicker to download and flash to any size SD card (within reason).
After flashing the sd card and booting up for the first time, log in and do the following to expand the root filesystem by following these instructions.
There's a lot of code below, but the whole process took me less than 2 minutes, and you should be able to safely accept the default response to all prompts.
1. Fix the partition table to reflect the size of the SD card:
Code: rock64@rock64:~$ sudo parted -l
Warning: Not all of the space available to /dev/mmcblk1 appears to be used, you
can fix the GPT to use all of the space (an extra 60332032 blocks) or continue
with the current setting?
Fix/Ignore? F
Model: SD 5&DRP (sd/mmc)
Disk /dev/mmcblk1: 32.1GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 32.8kB 4129kB 4096kB loader1
2 4129kB 4194kB 65.5kB reserved1
3 4194kB 8389kB 4194kB reserved2
4 8389kB 12.6MB 4194kB loader2
5 12.6MB 16.8MB 4194kB atf
6 16.8MB 134MB 117MB fat16 boot legacy_boot, msftdata
7 134MB 1208MB 1074MB ext4 root
2. Increase the root partition size:
Code: rock64@rock64:~$ sudo fdisk /dev/mmcblk1
Welcome to fdisk (util-linux 2.27.1).
Changes will remain in memory only, until you decide to write them.
Be careful before using the write command.
Command (m for help): p
Disk /dev/mmcblk1: 29.9 GiB, 32099008512 bytes, 62693376 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 062EE0ED-2FD5-4D89-B424-771CB4465BD4
Device Start End Sectors Size Type
/dev/mmcblk1p1 64 8063 8000 3.9M Linux filesystem
/dev/mmcblk1p2 8064 8191 128 64K Linux filesystem
/dev/mmcblk1p3 8192 16383 8192 4M Linux filesystem
/dev/mmcblk1p4 16384 24575 8192 4M Linux filesystem
/dev/mmcblk1p5 24576 32767 8192 4M Linux filesystem
/dev/mmcblk1p6 32768 262143 229376 112M Microsoft basic data
/dev/mmcblk1p7 262144 2359295 2097152 1G Linux filesystem
Command (m for help): d
Partition number (1-7, default 7):
Partition 7 has been deleted.
Command (m for help): n
Partition number (7-128, default 7):
First sector (262144-62693342, default 262144):
Last sector, +sectors or +size{K,M,G,T,P} (262144-62693342, default 62693342):
Created a new partition 7 of type 'Linux filesystem' and of size 29.8 GiB.
Command (m for help): w
The partition table has been altered.
Calling ioctl() to re-read partition table.
Re-reading the partition table failed.: Device or resource busy
The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8).
3. Tell the kernel the partition table has changed:
Code: rock64@rock64:~$ sudo partprobe /dev/mmcblk1
4. Resize the root filesystem to fill the partition:
Code: rock64@rock64:~$ sudo resize2fs /dev/mmcblk1p7
resize2fs 1.42.13 (17-May-2015)
Filesystem at /dev/mmcblk1p7 is mounted on /; on-line resizing required
old_desc_blocks = 1, new_desc_blocks = 2
The filesystem on /dev/mmcblk1p7 is now 7803899 (4k) blocks long.
rock64@rock64:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 459M 0 459M 0% /dev
tmpfs 93M 3.9M 89M 5% /run
/dev/mmcblk1p7 30G 769M 28G 3% /
tmpfs 462M 0 462M 0% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 462M 0 462M 0% /sys/fs/cgroup
/dev/mmcblk1p6 100M 22M 79M 22% /boot/efi
Reboot and you're done!
...but don't forget to change the default password from rock64 
|
|
|
|
Rock64 Boot-up Bug with Serial Console Cable |
|
Posted by: MarkHaysHarris777 - 08-24-2017, 04:33 PM - Forum: Rock64 Hardware and Accessories
- Replies (1)
|
 |
Greetings,
The Rock64 often will not boot-up with a serial console connected to the console uart pins (6, 8, & 10).
Symptom: lights come on, nothing happens at all.
Solution: unplug the Tx line coming in on pin(10) prior to applying power for boot-up.
The Tx line often (if not always) has 3v3 on it when the other end is powered up, even in the idle state. This voltage present on pin(10) of the Rock64 prevents it from booting, sadly. I have reliably verified that unplugging the Tx line in on pin(10) of the Rock64 will allow the boot-up to start... as it boots up , carefully plug the Tx line back onto pin(10).
Also noticed that the Tx line (if left connected to pin[10] on Rock64 power-down) will back-feed into the board, which will dimly light the red LED (small glow) ! This back-feed is preventing boot-up.
Fortunately the serial console monitor does not need this line connected to monitor as long as it has the Rx connection and a good ground, so unplugging the line from pin(10) does not prevent monitoring the boot-up messages on the serial console.
Note: This problem occurs on both of my boards; dev board pre production, and the production master-piece which came last week !
Note: At this point I don't know if the current draw on the Tx line might damage the monitor ; currently I'm using my PineA64 desk machine as the serial monitor for my Rock64 boards.
|
|
|
|
| Q4OS Pinebook Questions |
|
Posted by: StewB - 08-24-2017, 03:53 PM - Forum: Linux on Pine A64(+)
- No Replies
|
|
Nice install of Q4OS to microSD and transferred to the Pinebook internal drive.
What is the proper procedure to log into Wireless? (I see 2 connections: waan0 and waan1)
Will the miniHDMI work?
Thanks, Stew
|
|
|
|
| Boot hangs on pine64, how to debug? |
|
Posted by: olh - 08-24-2017, 05:37 AM - Forum: Android on Pine A64(+)
- Replies (1)
|
|
I have a 2GB pine64 from July 2016. It has the android-7.1-r69.img installed on a 128GB card.
Now it happend two times that boot just hangs in that aninimated logo before the "Android" text appears. This is with a stock img. How can I check what it is waiting for, or what it is missing?
Is there a way to get not only the kernel messages on serial console, but also the 'adb logcat' output, or whatever else is Android logging during boot? So far I see the filesystems are mounted, some rc scripts are executed.
Thanks.
|
|
|
|
| emmc upgrade |
|
Posted by: Erik - 08-24-2017, 02:18 AM - Forum: Pinebook Hardware and Accessories
- Replies (1)
|
|
Hi Guys,
This morning I swapped out the 16 Gb emmc module for a bigger 64Gb one. Opening the case was easy! After rebooting from a know working SD card I simply tried to run
/usr/local/sbin/pine_install_to_emmc.sh xenial-mate I get 'You should boot from SD card' ,which I did....
Any help how to continue would be appreciated. Do I need to partition the drive first? I the emmc drive broken? (I checked it is firmly inserted...)
Erik
|
|
|
|
|
ame(
![[Image: 1744404_9489a23e92496f06bb62.png]](https://i.nyx.cz/files/00/00/17/44/1744404_9489a23e92496f06bb62.png)
![[Image: 1744403_4901d252463b1f3136d4.png]](https://i.nyx.cz/files/00/00/17/44/1744403_4901d252463b1f3136d4.png)
