What is new with NemoMobile in December? Huge step forward in porting to Qt6. Updating UX. Fixes in pinquery, lipstick, usb-moded, tuning messages app and polkit-agent. 

http://nemomobile.net/pages/nemomobile-i...mber-2022/

Suppose we’re running Apache NuttX RTOS on PinePhone… How will we create Graphical Apps for NuttX?

Today we’ll learn about the…

1. Framebuffer Interface that NuttX provides to our apps for rendering graphics

2. What’s inside the Framebuffer Driver for PinePhone

3. Mystery of the Missing Framebuffer Pixels and how we solved it (unsatisfactorily)

4. Creating NuttX Apps with the LVGL Graphics Library

NuttX RTOS for PinePhone: Framebuffer

Hello,

I try to boot Armbian on the SoPine with baseboard from a eMMC module.

From armbian/pine64, I try some Arbian images.
I get this error:

Quote:U-Boot SPL 2022.07-armbian (Nov 30 2022 - 10:45:59 +0000)
DRAM: 0 MiB
### ERROR ### Please RESET the board ###

Quote:U-Boot 2022.07-armbian (Nov 30 2022 - 10:45:55 +0000) Allwinner Technology

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  73 devices, 22 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to use mmc 1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface11
eth0: ethernet@1c30000
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
MMC: no card present
** Bad device specification mmc 0 **
Couldn't find partition mmc 0
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Autoboot in 1 seconds, press <Space> to stop
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3259 bytes read in 2 ms (1.6 MiB/s)
## Executing script at 4fc00000
U-boot loaded from eMMC or secondary SD
Boot script loaded from mmc
155 bytes read in 2 ms (75.2 KiB/s)
MMC: no card present
** Bad device specification mmc 0 **
41777 bytes read in 4 ms (10 MiB/s)
3821 bytes read in 3 ms (1.2 MiB/s)
Applying kernel provided DT fixup script (sun50i-a64-fixup.scr)
## Executing script at 45000000
17114760 bytes read in 393 ms (41.5 MiB/s)
21934088 bytes read in 504 ms (41.5 MiB/s)
Moving Image from 0x40080000 to 0x40200000, end=41750000
## Loading init Ramdisk from Legacy Image at 4ff00000 ...
  Image Name:  uInitrd
  Image Type:  AArch64 Linux RAMDisk Image (gzip compressed)
  Data Size:    17114696 Bytes = 16.3 MiB
  Load Address: 00000000
  Entry Point:  00000000
  Verifying Checksum ... OK
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 48fad000, end 49fff648 ... OK
  Loading Device Tree to 0000000048f3a000, end 0000000048facfff ... OK

Starting kernel ...

done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... Scanning for Btrfs filesystems
done.
Begin: Will now check root file system ... fsck from util-linux 2.36.1
[/sbin/fsck.ext4 (1) -- /dev/mmcblk2p1] fsck.ext4 -a -C0 /dev/mmcblk2p1
armbi_root: clean, 69593/130816 files, 435596/523264 blocks

Hello,

I have a Sopine Baseboard Model A
This board haven't a SD interface, it's has a eMMC interface.

I downloaded the last 22.06's image of Manjaro Arm from manjaro-arm/pine64-lts-images's repository.

I flashed my eMMC Module and mounted it on the Sopine baseboard, I connected my USB serial console/programmer and I power on the Sopine.

My problem is during the boot, nothing happen after the `Starting kernel ...` line.

Quote:% sudo screen /dev/ttyUSB0 115200
U-Boot SPL 2022.04-2 (May 05 2022 - 08:29:42 +0000)
DRAM: 2048 MiB
Trying to boot from MMC2
NOTICE:  BL31: v2.6(release):
NOTICE:  BL31: Built : 08:29:42, May  5 2022
NOTICE:  BL31: Detected Allwinner A64/H64/R18 SoC (1689)
NOTICE:  BL31: Found U-Boot DTB at 0x209c938, model: SoPine with baseboard
SCP/INF: Crust v0.5.10000


U-Boot 2022.04-2 (May 05 2022 - 08:29:42 +0000) Manjaro Linux ARM

CPU:  Allwinner A64 (SUN50I)
Model: SoPine with baseboard
DRAM:  2 GiB
Core:  39 devices, 17 uclasses, devicetree: separate
WDT:  Not starting watchdog@1c20ca0
MMC:  mmc@1c0f000: 0, mmc@1c11000: 1
Loading Environment from FAT... Unable to read "uboot.env" from mmc1:1...
In:    serial
Out:  serial
Err:  serial
Net:  phy interface10
eth0: ethernet@1c30000
starting USB...
Bus usb@1c1a000: USB EHCI 1.00
Bus usb@1c1a400: USB OHCI 1.0
Bus usb@1c1b000: USB EHCI 1.00
Bus usb@1c1b400: USB OHCI 1.0
scanning bus usb@1c1a000 for devices... 1 USB Device(s) found
scanning bus usb@1c1a400 for devices... 1 USB Device(s) found
scanning bus usb@1c1b000 for devices... 1 USB Device(s) found
scanning bus usb@1c1b400 for devices... 1 USB Device(s) found
      scanning usb for storage devices... 0 Storage Device(s) found
Hit any key to stop autoboot:  0
switch to partitions #0, OK
mmc1(part 0) is current device
Scanning mmc 1:1...
Found /extlinux/extlinux.conf
Retrieving file: /extlinux/extlinux.conf
1:      Manjaro ARM
Retrieving file: /initramfs-linux.img
Retrieving file: /Image
append: initrd=/initramfs-linux.img console=ttyS0,115200 root=PARTUUID=1f2fe968-00ee-4b00-ad77-12e7c5c80fac rw rootwait audit=0 splash plymouth.ignore-serial-consoles
Retrieving file: /dtbs/allwinner/sun50i-a64-pine64-lts.dtb
Moving Image from 0x40080000 to 0x40200000, end=419e0000
## Flattened Device Tree blob at 4fa00000
  Booting using the fdt blob at 0x4fa00000
  Loading Ramdisk to 497f6000, end 49fff57e ... OK
  Loading Device Tree to 00000000497e9000, end 00000000497f5dd7 ... OK

Starting kernel ...

Hello all:

Please let me know the most recent Mobian image or Mobian installer image which you personally know works on the PP!

I'm having trouble getting a fresh install of Mobian to boot. I've used the Mobian image from 12/28 AND the Mobian installer image from that same date. I'm trying to troubleshoot where the problem lies; could it be with my install of tow-boot? The images from that date? Hardware? To isolate these effects and diagnose the problem, I'd like to use an image which is known to work. Thank you; you're really helping me out!

Some additional info:
I have reason to believe tow-boot was installed correctly: I installed the 2021/10-005 installer of tow-boot to an SD card and used the tow-boot installation GUI to flash it to the eMMC boot partition. Since then, the power on, volume up, and volume down behavior and LED lights has been consistent with tow-boot's docs, suggesting that tow-boot is functioning correctly.
I followed the instructions and didn't make any of the following obvious errors: I verified the sha256 checksums of all images. I unzipped them before dd'ing them. I flashed the right image to the right medium: Mobian image to eMMC via tow-boot's jumpdrive mode, Mobian installer image to SD card. Please do not post a link to the tow-boot or Mobian installation instructions. If you don't trust that I was following those, why bother responding at all?
The order of events is as follows: I try to boot from eMMC, and the LED stays yellow. Nothing ever displays on the screen. I try to boot from the SD card, and the LED stays cyan. Nothing ever displays on the screen. These behaviors are different if there is no SD card, or if the eMMC has been erased: Then it vibes and blinks red. So the phone is recognizing in some manner that the images are bootable in some way, it just never displays anything on the screen of the phone.

I have a 2022 (July?) Pinebook pro.

I installed the latest Tow-Boot on the SPI, that works, but won't boot the eMMC, SD card booting works, haven't tried NVME.

The current Tow-Boot is based on the 2021.10 u-boot, so I think the problems are common to both.

I also successfully re-built Tow-Boot myself, and was able to add a patch with some debugging statements.

The problem seems to start when Tow-Boot tries to read multiple blocks off the eMMC, and the eMMC returns timeout in response to the stop transmission command that is supposed to close off the read command, in u-boot file drivers/mmc/mmc.c / mmc_read_blocks:

My (patched) version

I've been testing Mobian Phosh on my Pinephone a64.

• I am using the unstable repositories. - Debian GNU/Linux bookwork/sid
  
• Gnome Version 43
  
• phosh 0.23.0
  
• Contacts 43.0
  
• Calendar 43.1
  

• I have entered the server address, user name, and user password in the Online accounts section of the Settings App.
  
• I have Calendar, Contacts, and Files enabled in the Online accounts > Nextcloud section of the Settings App.
  

The store listing says Ox64 boards are coming in January. Is there some more specific info? Is it the beginning of the month? The end? Will there be lots so anyone can get it, or just few dozen? Is there some sort of "waiting list" one can sign up to not to miss it? 

I would like to get my hands on a couple, but I missed the initial sale and ever since they aren't available. 

I also have a question about continued availability, is pine64 planning to manufacture a lot of them? I would like to avoid a situation where I do manage to get one or two, I spend ages on developing the software. Then I can't get any more (at all or for the original price) so all the software dev time is pretty much wasted.

I purchased my PBP in late 2019, and I've generally been happy with the physical build quality -- up till last week, when the bottom plate fell off.  No joke. Every single one of the plastic mounts that hold the captive nuts that the bottom plate screws screw into, has shattered.

           

Here's what came away with the bottom plate:

   

Thankfully, the PINE64 store will sell me a replacement for the damaged piece of the chassis (aka "PALM CASE WITH [variety] KEYBOARD") but I wanted to know if anyone else has seen this particular failure mode.  I'm a little nervous that the exact same thing will happen in another three years

Hello all!

I've been fiddling with the PP on and off since September 2020, and all in all it's been a great learning experience. Very empowering for folks like me who like to imagine a better way for smartphones to be.

I've found that what was holding back my use of the PP for a daily driver was a lack of a smart-wake. I had to choose between poor battery life (handset on, not suspended) or no notifications (suspended). I am aware that the phone can wake from suspend upon incoming call or text, a feature called crust. This is great but, as of the last time I checked, did not work for arbitrary push notifications such as emails, chats, or timers. 

In summer of 2021 I hacked together a solution which wakes the PP up for one minute out of every 15 or so to check for notifications. It works fine (really saves on battery), but isn't well-integrated or well-supported. Here's the thread: https://forum.pine64.org/showthread.php?tid=14564

So, do we have this feature yet? Last time I was actively following development was around 7 months ago.

Thanks all!