Welcome, Guest
You have to register before you can post on our site.

Username
  

Password
  





Search Forums



(Advanced Search)

Forum Statistics
» Members: 29,712
» Latest member: marvin_ellis1212
» Forum threads: 16,264
» Forum posts: 117,211

Full Statistics

Latest Threads
what is the point?
Forum: General Discussion on PinePhone
Last Post: Zebulon Walton
5 hours ago
» Replies: 5
» Views: 155
Irradium (based on crux l...
Forum: Linux on Pinebook
Last Post: mara
Today, 07:38 AM
» Replies: 3
» Views: 11,846
Danctnix USB GPS for Pine...
Forum: PineTab Software
Last Post: biketool
Today, 06:09 AM
» Replies: 0
» Views: 33
Pinetab2 camera drivers
Forum: PineTab Software
Last Post: biketool
Today, 03:39 AM
» Replies: 10
» Views: 6,777
Old Danctnix server in Pa...
Forum: PineTab Software
Last Post: realchunkyflea
Yesterday, 05:01 PM
» Replies: 3
» Views: 266
PinePhone sensors - Gyros...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
Yesterday, 04:23 PM
» Replies: 2
» Views: 74
irradium (based on crux l...
Forum: Linux on Rock64
Last Post: mara
Yesterday, 10:30 AM
» Replies: 10
» Views: 15,925
irradium (based on crux l...
Forum: Linux on RockPro64
Last Post: mara
11-26-2025, 02:45 PM
» Replies: 10
» Views: 16,855
PinePhone, PinePhone Pro,...
Forum: PinePhone Hardware
Last Post: j_s
11-26-2025, 11:33 AM
» Replies: 4
» Views: 251
Quill OS for the PineNote
Forum: PineNote Software
Last Post: JhonSmith
11-26-2025, 01:42 AM
» Replies: 1
» Views: 167

 
  UT move to Ubuntu 20.04
Posted by: Concrete_panda - 11-09-2020, 03:50 PM - Forum: UBPorts on PinePhone - Replies (2)

Hello everybody,

I have got a question about the move of Ubuntu Touch to Ubuntu 20.04.

If I understand this topic correctly, Ubuntu Touch is currently bases on Ubuntu 16.04 and shall be moved to Ubuntu 20.04 in order to have newer packages.

But what will that exactly mean for Ubuntu touch? Will we then be able to install normal Linux apps and run them on Ubuntu Touch without Libertine?

I think that the ability of running normal Linux apps in Ubuntu Touch would really be a thing. Is that gonna come?

Best,
Thomas


Thumbs Up Well Done
Posted by: acid andy - 11-09-2020, 03:25 PM - Forum: General Discussion on PinePhone - Replies (5)

My Manjaro CE Pinephone arrived and I have to say given all the discussion about people finding many of the features unreliable (which I was OK with as it's an open platform that's under development by the community), I am astonished and delighted how good it is! Big Grin 

Thank you and well done to Pine64 and to everyone in the community for making a great Linux phone.

It arrived when DHL said it would. It was well-packaged and presented. I was impressed with the setup process which even included privacy-focused details like a link to UBlock Origin from the Firefox default home page.

Wifi, web surfing, the camera, all worked great. I put in my SIM card and tried out a couple of calls, expecting them to barely work but was pleasantly surprised to get crystal clear audio (the person's voice sounds altered, like talking to a different person, but it was clear and easy to understand). When I first called my partner I feared it wasn't working right because it sounded stuttery but it turned out that was just because I had it on Speaker and she was reacting to hearing her own voice! Big Grin Obviously some kind of echo-cancellation algorithm could help there.

The only very minor issues I've had so far are the rapid battery drain (which I can live with); at one point the lock screen wouldn't open when I entered the correct PIN multiple times but a reboot by holding down the power switch fixed that; and when some dialog boxes pop up on the Manjaro UI (for example from some Settings) I can't figure out how I'm supposed to close them: I've just been tapping at the bottom of the screen to show all the open windows and close the dialogs that way.

Once again, thank you Pine64, Manjaro and the rest of the community! Keep up the fantastic work!


  Update to 3GB/32GB mainboard not working
Posted by: tlo - 11-09-2020, 02:00 PM - Forum: PinePhone Hardware - Replies (2)

Hi,
the mainboard arrived today and installation went smooth, except now it doesnt boot anymore :-(
I tried to boot fromm emmc and with a Jumpdrive-sdcard in the sd-slot.
I re-installed the original board (UB-Ports edition) and that still works fine.
Am i missing something or did i get a dead board?


  video of opening up pinetab?
Posted by: hanscees - 11-09-2020, 12:47 PM - Forum: PineTab Hardware - No Replies

Hi,
I can't seem to find a way  to open the pinetab: the edges seem solid.
Is there a video somewhere perhaps?

thanks


  How cool would it be
Posted by: Markdanni123 - 11-09-2020, 12:39 PM - Forum: General - No Replies

Imagine how awesome it would be if there was an add-on for the pinephone that’s was along the lines of the Razer Kishi controller for phones that would allow you to play your retro games on? Just throwing that out there


  Password manager
Posted by: skaf2007 - 11-09-2020, 11:03 AM - Forum: PostmarketOS on PinePhone - Replies (4)

The best performing password manager ?
Apart from pass Wink


Wysłane z iPhone za pomocą Tapatalk


  PSA: Manjaro CE PinePhones with pmOS
Posted by: Luke - 11-09-2020, 09:17 AM - Forum: General - No Replies

A few days ago it has come to our attention that a number of Manjaro CE PinePhones have shipped with postmarketOS.

Following a brief investigation, it turned out that indeed ONE out of 100 mSD cards used for testing and subsequent flashing at the factory contains the postmarketOS image.

Please accept our apologies as well as those relayed by the factory.

Thankfully, flashing an OS on the PinePhone's internal flash storage is truly trivial:

If you have ever flashed a SD card for a single board computer, than this process is no different and ought to take no longer than a few minutes.

Once again, please accept my apology for this situation.


Lightbulb [12.11.20 Update] Latest PinePhone CE Manjaro - Device Arrival & Initial Tests Thread
Posted by: kern707 - 11-09-2020, 06:12 AM - Forum: General Discussion on PinePhone - Replies (11)

Hello everyone,



I was thinking, maybe it is a good idea to encapsulate all of the information for arrival and initial testing of the recently delivered PinePhone CE Manjaro, instead of opening a separate thread for each smaller subject.



I'd first identify which device have I got, and then describe my initial testing and thoughts:



My Device:

PinePhone CE Manjaro Convergence with 32GB eMMC and 3GB of RAM.

I believe it is pre-installed with Manjaro Posh (Update: Reading the paper leaflet that came in the box, my pre-installed Manjaro actually came with Lomiri according the paperwork that came with the device, even though I think the UI looks like Posh).



Delivery notes:
- Ordered on 31.10.2020, received in Europe on 09.11.2020 - pretty damn good I'd say!

- I have received the PinePhone in a small carton box, which held inside of it the actual white box which shows a nice "Pine64 Manjaro" graphic on top of it.

- Inside the box everything was packed carefully.

- What was in the box: the device it self, a charging cable, the Convergence dock, a mini-sim to normal sim (I think?) adapter, and a couple of paper leaflets with instructions / information.



So far my test results using the device right out of the box:



1. Popped up the case cover to remove the battery protection sticker, replace the battery into place and popped the case cover back on the phone.

2. Pressed the power key.

3. Manjaro logo appears on screen, and boots correctly.

4. Device is protected by a default PIN code, which was the factory 123456

5. Went through the initial setup wizard without problems and connected the device to Wifi

6. Could connect to my Wifi network, and browse the internet, Wifi connectivity seem pretty slow (took about 10 seconds to load pine64.org's homepage) - once again, I am not sure if this is an issue? or is the wifi on the device is just slow?

7. Overall the device UI responsiveness seem to run a bit slow when pressing on UI elements (e.g. tap on  Firefox, takes almost 3-4 seconds before it even pops up on the screen), not sure if this is an issue? since this is my first PinePhone, and real linux phone in general.

8. The PinePhone is connected to a charger, currently seem to charge fine (battery indicator was 94% and is currently 95%, so seem to charge)

9. The PinePhone is relatively warm on the top back of the device, not sure if this is normal ? or is it because I am fiddling with the device while it is charging? 

10. Cameras: I have just did a quick general test of the front and back cameras using the pre-installed "Megapixels" app, nothing fancy just wanted to see if the cameras actually function: both cams seem to work, one issue which I did encountered was that when I have switched from the normal cam to the front cam, and then tried to switch again back - the app seem to freeze. 

11. The "Software" app seem to hang on the "Looking for new updates.." screen when trying to look  for new updates ("Updates" tab), the message just hang in there forever - so not clear if it is still looking for something, or just stuck. 







UPDATE #1:

After having the PinePhone right out of the box, connected to a charger, no SIM card in it yet, only connected to Wifi... then and partially fiddling with it but most of the time just letting it lay on my desk, I have noticed something strange - a rather aggressive battery drainage ? about 10 minutes ago the charge indicator on Manjaro indicated a 98% charge, now after the phone has been laying on my desk (without usage), battery charge indicator had dropped and shows 95%, regardless of the device not being used and being constantly connected to a charger. anybody else have noticed battery problems when the device is very lightly used or not being used at all ?


UPDATE #2:

In my first update I wrote about charging issues, I am testing to see now if the problem was the charger block that I have used (my standard apple Iphone charger block), because I have seen that when charging using the apple charger, the status shows on the PinePhone as "Discharging" even when the charger is plugged-in, no idea why.. maybe it is too weak for the PinePhone? I have connected another usb charger which has a little higher charging amperage and suddenly the battery status was changed to "Charging" 

UPDATE #3 (Making / Receiving calls):
SIM Card inserted (was a bit of a hack with the adapter, but at least it help till I will get a duplicate SIM in a "normal" size), 
- I am using a German company (which uses a mix of 3-4 well-known companies depends on where you are, t-mobile, vodafone, o2 etc..).
- The PinePhone was able to identify the SIM and connect to the cellular network 
- I was able to make a call and receive as well.
- The audio sound quality is not crystal clear but not as bad, the voice on the other side can be understood as long as there are not too many background noises, the audio quality could also improve with the time.


** I have not yet tried to send or receive an SMS, I will add an update when I do about my result.


Currently the PinePhone is running updates (including a system update I believe), I will see how it all works out once the updates are complete.



** UPDATE 10.11.2020 **

After the latest update, currently running: 5.9.1-9-MANJARO-ARM

OK Continuing with my testing, after "spending the night" with the PinePhone CE Manjaro on my bed stand, with my SIM card inserted in it:

1. The modem shut down completely after (probably) some time of no usage, when I woke up in the morning I have noticed that when I have turned on the screen both cellular network and Wifi icons showed that they are re-connecting, which means that any usage of modem after the phone has been sitting still is questionable.

2. "Clocks" app: The alarm clock feature does not work - I have made a test, and set a timer to 6:00, it did not wake me up :-) must be some issue with the whole phone going into sleep mode? (Yes, I have tripled check that I set the date,time and timezone correctly on the phone)

3. Battery drainage is a real problem - even after waking up in the morning, and realizing that the cellular modem and Wifi were completely off the whole night, and with the device being constantly connected to a charger, I have still got a 96% charge when turning on the screen first thing in the morning (and tapping on top to slide down the upper toolbar which shows the charge status with %)

4. Remember what I have wrote in my upper portion of the post about the "Software" app being stuck up on the "looking for updates screen" ?
Well, strange enough, after inserting my SIM card and having it identified and connected - the "Software" app suddenly started to work and found a few updates :-) I did the updates, rebooted, and it seem to look like after the updates the overall UI "feels" better, work smoother.. Firefox works much better now! very nice indeed!

5. I was pleased to see the the Desktop app of Telegram functions as good as a mobile app, and that everything connected flawlessly.

6. "Megapixels" app still freeze up the moment you switch cameras twice - but the camera for me is not the highest priority  Wink

** UPDATE 10.11.2020 #2 **
I have noticed something in regarding the the charging of the PinePhone Manjaro CE, maybe this is the reason for why the device is never being able to get a 100% charge ?
- When the device is sited on my desk for long periods of time without being used, it seem to be that the charging procedure is being "detached" or stopped somehow.
  * Because when that happens, every time I press on the power button to turn on the screen, the battery icon shows the normal "battery" state (not charging), then only when I remove the charging cable from the device and plug it immediately back on - only then, the "charging" icon is coming back on.

What I am experiencing is a matter of fact, but the question which I am not able to accurately answer is, is this a hardware issue? or an operating system issue? since I thought that the hardware controls the charging and not the operating system.
 
** UPDATE 11.11.2020 **
1. "Clocks" app - I have tried again to setup an alarm clock for me, at 6:00 in the morning, this time I have woken up earlier to make sure the phone is not in "sleep" mode, I made sure the "Clocks" app is still running after I set my alarm, I configured the alarm to function in all days of the week, all of the configuration was double checked! unfortunately the alarm still does not work!
This is strange, because first I was thinking that because this is a real linux, that when the device is going to sleep mode it prevents the alarm from going off, but this is not the case, because even when the phone is not in idle mode (I made sure to fiddle with it every 5-10 minutes or so), the alarm still does not work.
This is not the most important app, but IMHO it is a very basic functionality, and I have no idea why it does not work? from my side, I am pretty sure that I was using it correctly. maybe a software bug? or something else? I am not sure.
2. "Software" App - I have tested the "Explore" tab and was able to search for all types of software, FYI: the search is not filtered only to mobile-compatible apps, so even software that was never meant to run on a PinePhone will be found and are possible to install. I have installed a few apps for testing: some did not even run, some crushed, other loaded fine but it was clear that those were Desktop-only apps so not usable on a PinePhone.
* As a software developer, I would love to know if there is any resource with information about developing apps for Linux arm, preferably something modern (It's been some time since I have done C programming), best if focused on development for smart devices such as the PinePhone (none of that embedded software type) maybe I could contribute somehow.



** UPDATE 12.11.2020 **

1. "Clocks" app - I have tried the alarm clock feature once again, this time it worked, the alert went of on time and work me up.
Yesterday I had to reboot the PinePhone after (once again!) the lock screen stopped responding, maybe it was that reboot which have settled down some changes in the system, which allowed the "Clocks" app the finally work correctly? no idea, but it is now working as expected.



Please share your own initial tests and insights here if you like, once you get your device (or if you already got it ), maybe we can build here a very useful thread that is focused on the new PinePhone CE release.





In the meantime, I wish a great day to all  Big Grin


  Wifi and bluetooth disabled after upgrading to PMOS kernel 5.9.1
Posted by: aithal - 11-09-2020, 01:17 AM - Forum: PostmarketOS on PinePhone - No Replies

I have been using Pinephone UBports edition since August. I have been trying out different OS versions, but always had a stable customized SXMO build of PMOS which I have been using with all basic phone functionalities working.
When I upgraded to kernel 5.9.1 pmos sxmo on another sdcard, the wifi and bluetooth stopped working.

The demsg log is as follows -

Code:
[    0.000000] Booting Linux on physical CPU 0x0000000000 [0x410fd034]
[    0.000000] Linux version 5.9.1 (pmos@build) (aarch64-alpine-linux-musl-gcc (Alpine 10.2.0) 10.2.0, GNU ld (GNU Binutils) 2.35.1) #4-postmarketos-allwinner SMP Fri Oct 30 07:37:12 UTC 2020
[    0.000000] Machine model: Pine64 PinePhone (1.2)
[    0.000000] earlycon: uart0 at MMIO32 0x0000000001c28000 (options '')
[    0.000000] printk: bootconsole [uart0] enabled
[    0.000000] cma: Reserved 256 MiB at 0x00000000b0000000
[    0.000000] NUMA: No NUMA configuration found
[    0.000000] NUMA: Faking a node at [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] NUMA: NODE_DATA [mem 0xafbcc100-0xafbcdfff]
[    0.000000] Zone ranges:
[    0.000000]   DMA      [mem 0x0000000040000000-0x000000007fffffff]
[    0.000000]   DMA32    [mem 0x0000000080000000-0x00000000bfffffff]
[    0.000000]   Normal   empty
[    0.000000] Movable zone start for each node
[    0.000000] Early memory node ranges
[    0.000000]   node   0: [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] Initmem setup node 0 [mem 0x0000000040000000-0x00000000bfffffff]
[    0.000000] On node 0 totalpages: 524288
[    0.000000]   DMA zone: 4096 pages used for memmap
[    0.000000]   DMA zone: 0 pages reserved
[    0.000000]   DMA zone: 262144 pages, LIFO batch:63
[    0.000000]   DMA32 zone: 4096 pages used for memmap
[    0.000000]   DMA32 zone: 262144 pages, LIFO batch:63
[    0.000000] psci: probing for conduit method from DT.
[    0.000000] psci: PSCIv1.1 detected in firmware.
[    0.000000] psci: Using standard PSCI v0.2 function IDs
[    0.000000] psci: MIGRATE_INFO_TYPE not supported.
[    0.000000] psci: SMC Calling Convention v1.2
[    0.000000] percpu: Embedded 22 pages/cpu s50008 r8192 d31912 u90112
[    0.000000] pcpu-alloc: s50008 r8192 d31912 u90112 alloc=22*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[    0.000000] Detected VIPT I-cache on CPU0
[    0.000000] CPU features: detected: ARM erratum 845719
[    0.000000] CPU features: detected: ARM erratum 843419
[    0.000000] Speculative Store Bypass Disable mitigation not required
[    0.000000] Built 1 zonelists, mobility grouping on.  Total pages: 516096
[    0.000000] Policy zone: DMA32
[    0.000000] Kernel command line: init=/init.sh rw console=tty0 console=ttyS0,115200 earlycon=uart,mmio32,0x01c28000 panic=10 consoleblank=0 loglevel=1 cma=256M PMOS_NO_OUTPUT_REDIRECT PMOS_FORCE_PARTITION_RESIZE pmos_boot=/dev/mmcblk0p1 pmos_root=/dev/mmcblk0p2
[    0.000000] Dentry cache hash table entries: 262144 (order: 9, 2097152 bytes, linear)
[    0.000000] Inode-cache hash table entries: 131072 (order: 8, 1048576 bytes, linear)
[    0.000000] mem auto-init: stack:off, heap alloc:off, heap free:off
[    0.000000] software IO TLB: mapped [mem 0x7bfff000-0x7ffff000] (64MB)
[    0.000000] Memory: 1709188K/2097152K available (10942K kernel code, 650K rwdata, 4064K rodata, 1792K init, 388K bss, 125820K reserved, 262144K cma-reserved)
[    0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[    0.000000] rcu: Hierarchical RCU implementation.
[    0.000000] rcu:     RCU restricting CPUs from NR_CPUS=64 to nr_cpu_ids=4.
[    0.000000] rcu: RCU calculated value of scheduler-enlistment delay is 25 jiffies.
[    0.000000] rcu: Adjusting geometry for rcu_fanout_leaf=16, nr_cpu_ids=4
[    0.000000] NR_IRQS: 64, nr_irqs: 64, preallocated irqs: 0
[    0.000000] GIC: Using split EOI/Deactivate mode
[    0.000000] random: get_random_bytes called from start_kernel+0x304/0x4cc with crng_init=0
[    0.000000] arch_timer: Enabling global workaround for Allwinner erratum UNKNOWN1
[    0.000000] arch_timer: CPU0: Trapping CNTVCT access
[    0.000000] arch_timer: cp15 timer(s) running at 24.00MHz (phys).
[    0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0x588fe9dc0, max_idle_ns: 440795202592 ns
[    0.000005] sched_clock: 56 bits at 24MHz, resolution 41ns, wraps every 4398046511097ns
[    0.000456] Console: colour dummy device 80x25
[    0.000470] printk: console [tty0] enabled
[    0.000562] Calibrating delay loop (skipped), value calculated using timer frequency.. 48.00 BogoMIPS (lpj=96000)
[    0.000571] pid_max: default: 32768 minimum: 301
[    0.000662] LSM: Security Framework initializing
[    0.000739] Mount-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.000759] Mountpoint-cache hash table entries: 4096 (order: 3, 32768 bytes, linear)
[    0.002520] rcu: Hierarchical SRCU implementation.
[    0.003148] smp: Bringing up secondary CPUs ...
[    0.004663] Detected VIPT I-cache on CPU1
[    0.004726] arch_timer: CPU1: Trapping CNTVCT access
[    0.004739] CPU1: Booted secondary processor 0x0000000001 [0x410fd034]
[    0.005705] Detected VIPT I-cache on CPU2
[    0.005736] arch_timer: CPU2: Trapping CNTVCT access
[    0.005744] CPU2: Booted secondary processor 0x0000000002 [0x410fd034]
[    0.006604] Detected VIPT I-cache on CPU3
[    0.006631] arch_timer: CPU3: Trapping CNTVCT access
[    0.006639] CPU3: Booted secondary processor 0x0000000003 [0x410fd034]
[    0.006711] smp: Brought up 1 node, 4 CPUs
[    0.006716] SMP: Total of 4 processors activated.
[    0.006721] CPU features: detected: 32-bit EL0 Support
[    0.006727] CPU features: detected: CRC32 instructions
[    0.020620] CPU: All CPU(s) started at EL2
[    0.020645] alternatives: patching kernel code
[    0.022461] devtmpfs: initialized
[    0.030904] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 7645041785100000 ns
[    0.030929] futex hash table entries: 1024 (order: 4, 65536 bytes, linear)
[    0.040529] pinctrl core: initialized pinctrl subsystem
[    0.041918] NET: Registered protocol family 16
[    0.043680] DMA: preallocated 256 KiB GFP_KERNEL pool for atomic allocations
[    0.043744] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA pool for atomic allocations
[    0.043895] DMA: preallocated 256 KiB GFP_KERNEL|GFP_DMA32 pool for atomic allocations
[    0.044861] thermal_sys: Registered thermal governor 'fair_share'
[    0.044866] thermal_sys: Registered thermal governor 'bang_bang'
[    0.044873] thermal_sys: Registered thermal governor 'step_wise'
[    0.044876] thermal_sys: Registered thermal governor 'power_allocator'
[    0.045640] cpuidle: using governor menu
[    0.045820] hw-breakpoint: found 6 breakpoint and 4 watchpoint registers.
[    0.045931] ASID allocator initialised with 65536 entries
[    0.046089] Serial: AMBA PL011 UART driver
[    0.085528] HugeTLB registered 1.00 GiB page size, pre-allocated 0 pages
[    0.085541] HugeTLB registered 32.0 MiB page size, pre-allocated 0 pages
[    0.085546] HugeTLB registered 2.00 MiB page size, pre-allocated 0 pages
[    0.085551] HugeTLB registered 64.0 KiB page size, pre-allocated 0 pages
[    0.087105] cryptd: max_cpu_qlen set to 1000
[    0.091407] iommu: Default domain type: Translated
[    0.091798] SCSI subsystem initialized
[    0.092148] usbcore: registered new interface driver usbfs
[    0.092209] usbcore: registered new interface driver hub
[    0.092301] usbcore: registered new device driver usb
[    0.093398] mc: Linux media interface: v0.10
[    0.093453] videodev: Linux video capture interface: v2.00
[    0.093775] EDAC MC: Ver: 3.0.0
[    0.095923] clocksource: Switched to clocksource arch_sys_counter
[    0.096177] VFS: Disk quotas dquot_6.6.0
[    0.096241] VFS: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
[    0.108042] NET: Registered protocol family 2
[    0.108527] tcp_listen_portaddr_hash hash table entries: 1024 (order: 2, 16384 bytes, linear)
[    0.108566] TCP established hash table entries: 16384 (order: 5, 131072 bytes, linear)
[    0.108723] TCP bind hash table entries: 16384 (order: 6, 262144 bytes, linear)
[    0.109058] TCP: Hash tables configured (established 16384 bind 16384)
[    0.109195] UDP hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.109254] UDP-Lite hash table entries: 1024 (order: 3, 32768 bytes, linear)
[    0.109435] NET: Registered protocol family 1
[    0.110008] RPC: Registered named UNIX socket transport module.
[    0.110012] RPC: Registered udp transport module.
[    0.110015] RPC: Registered tcp transport module.
[    0.110017] RPC: Registered tcp NFSv4.1 backchannel transport module.
[    0.110718] Unpacking initramfs...
[    0.183151] Freeing initrd memory: 1420K
[    0.184109] hw perfevents: enabled with armv8_cortex_a53 PMU driver, 7 counters available
[    0.188579] Initialise system trusted keyrings
[    0.188775] workingset: timestamp_bits=44 max_order=19 bucket_order=0
[    0.197396] NFS: Registering the id_resolver key type
[    0.197430] Key type id_resolver registered
[    0.197433] Key type id_legacy registered
[    0.197537] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[    0.197753] fuse: init (API version 7.31)
[    0.251203] Key type asymmetric registered
[    0.251211] Asymmetric key parser 'x509' registered
[    0.251269] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 247)
[    0.251276] io scheduler mq-deadline registered
[    0.251280] io scheduler kyber registered
[    0.257685] sun50i-a64-r-pinctrl 1f02c00.pinctrl: initialized sunXi PIO driver
[    0.259080] sun50i-a64-r-pinctrl 1f02c00.pinctrl: supply vcc-pl not found, using dummy regulator
[    0.279288] Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
[    0.292047] lima 1c40000.gpu: gp - mali400 version major 1 minor 1
[    0.292096] lima 1c40000.gpu: pp0 - mali400 version major 1 minor 1
[    0.292145] lima 1c40000.gpu: pp1 - mali400 version major 1 minor 1
[    0.292189] lima 1c40000.gpu: l2 cache 64K, 4-way, 64byte cache line, 64bit external bus
[    0.292580] lima 1c40000.gpu: bus rate = 200000000
[    0.292587] lima 1c40000.gpu: mod rate = 432000000
[    0.293008] [drm] Initialized lima 1.1.0 20191231 for 1c40000.gpu on minor 0
[    0.303316] loop: module loaded
[    0.303855] zram: Added device: zram0
[    0.305862] libphy: Fixed MDIO Bus: probed
[    0.305874] tun: Universal TUN/TAP device driver, 1.6
[    0.306227] VFIO - User Level meta-driver version: 0.3
[    0.307681] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[    0.307689] ehci-platform: EHCI generic platform driver
[    0.308176] ehci-platform 1c1a000.usb: EHCI Host Controller
[    0.308207] ehci-platform 1c1a000.usb: new USB bus registered, assigned bus number 1
[    0.308345] ehci-platform 1c1a000.usb: irq 20, io mem 0x01c1a000
[    0.323967] ehci-platform 1c1a000.usb: USB 2.0 started, EHCI 1.00
[    0.324794] hub 1-0:1.0: USB hub found
[    0.324838] hub 1-0:1.0: 1 port detected
[    0.325795] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[    0.325834] ohci-platform: OHCI generic platform driver
[    0.326074] ohci-platform 1c1a400.usb: Generic Platform OHCI controller
[    0.326095] ohci-platform 1c1a400.usb: new USB bus registered, assigned bus number 2
[    0.326228] ohci-platform 1c1a400.usb: irq 21, io mem 0x01c1a400
[    0.388681] hub 2-0:1.0: USB hub found
[    0.388723] hub 2-0:1.0: 1 port detected
[    0.390244] usbcore: registered new interface driver usb-storage
[    0.393794] sun6i-rtc 1f00000.rtc: registered as rtc0
[    0.393850] sun6i-rtc 1f00000.rtc: setting system clock to 2020-11-09T05:55:36 UTC (1604901336)
[    0.393857] sun6i-rtc 1f00000.rtc: RTC enabled
[    0.394058] i2c /dev entries driver
[    0.395756] sun8i-di 1e00000.deinterlace: Device registered as /dev/video0
[    0.398611] device-mapper: ioctl: 4.42.0-ioctl (2020-02-27) initialised: dm-devel@redhat.com
[    0.399324] sdhci: Secure Digital Host Controller Interface driver
[    0.399330] sdhci: Copyright(c) Pierre Ossman
[    0.399472] Synopsys Designware Multimedia Card Interface Driver
[    0.400619] sdhci-pltfm: SDHCI platform and OF driver helper
[    0.402005] ledtrig-cpu: registered to indicate activity on CPUs
[    0.402520] SMCCC: SOC_ID: ARCH_FEATURES(ARCH_SOC_ID) returned error: fffffffffffffffd
[    0.402600] hid: raw HID events driver (C) Jiri Kosina
[    0.403622] usbcore: registered new interface driver usbhid
[    0.403632] usbhid: USB HID core driver
[    0.405495] cedrus 1c0e000.video-codec: Device registered as /dev/video1
[    0.406594] ashmem: initialized
[    0.412375] NET: Registered protocol family 17
[    0.412475] Key type dns_resolver registered
[    0.412912] registered taskstats version 1
[    0.412920] Loading compiled-in X.509 certificates
[    0.430671] sun8i-rotate 1020000.rotate: Device registered as /dev/video2
[    0.435658] sunxi-rsb 1f03400.rsb: RSB running at 4000000 Hz
[    0.436139] axp20x-rsb sunxi-rsb-3a3: AXP20x variant AXP803 found
[    0.438190] input: axp20x-pek as /devices/platform/soc/1f03400.rsb/sunxi-rsb-3a3/axp221-pek/input/input0
[    0.443672] axp20x-adc axp813-adc: DMA mask not set
[    0.446286] axp20x-battery-power-supply axp20x-battery-power-supply: DMA mask not set
[    0.452103] axp20x-battery-power-supply axp20x-battery-power-supply: Configuring battery thermal regulation for Pinephone
[    0.454529] axp20x-usb-power-supply axp20x-usb-power-supply: DMA mask not set
[    0.455956] random: fast init done
[    0.456743] dcdc1: supplied by regulator-dummy
[    0.457198] dcdc2: supplied by regulator-dummy
[    0.457478] dcdc4: supplied by regulator-dummy
[    0.457755] dcdc5: supplied by regulator-dummy
[    0.458062] dcdc6: supplied by regulator-dummy
[    0.458329] dc1sw: supplied by regulator-dummy
[    0.458552] aldo1: supplied by regulator-dummy
[    0.458626] dovdd-csi: Bringing 3300000uV into 1800000-1800000uV
[    0.458929] aldo2: supplied by regulator-dummy
[    0.459192] aldo3: supplied by regulator-dummy
[    0.459467] dldo1: supplied by regulator-dummy
[    0.459770] dldo2: supplied by regulator-dummy
[    0.460184] dldo3: supplied by regulator-dummy
[    0.460623] dldo4: supplied by regulator-dummy
[    0.460709] vcc-wifi-io: Bringing 3300000uV into 1800000-1800000uV
[    0.461052] eldo1: supplied by regulator-dummy
[    0.461349] eldo2: supplied by regulator-dummy
[    0.461642] eldo3: supplied by regulator-dummy
[    0.461713] dvdd-1v8-csi: Bringing 700000uV into 1800000-1800000uV
[    0.461995] fldo1: supplied by regulator-dummy
[    0.462291] fldo2: supplied by regulator-dummy
[    0.462589] rtc-ldo: supplied by regulator-dummy
[    0.462868] ldo-io0: supplied by regulator-dummy
[    0.463161] ldo-io1: supplied by regulator-dummy
[    0.463229] vcc-1v8-typec: Bringing 3300000uV into 1800000-1800000uV
[    0.463541] axp20x-rsb sunxi-rsb-3a3: AXP20X driver loaded
[    0.469458] sun50i-a64-pinctrl 1c20800.pinctrl: initialized sunXi PIO driver
[    0.472047] printk: console [ttyS0] disabled
[    0.472144] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 32, base_baud = 1500000) is a 16550A
[    0.472197] printk: console [ttyS0] enabled
[    0.472201] printk: bootconsole [uart0] disabled
[    0.473972] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 33, base_baud = 1500000) is a 16550A
[    0.474189] serial serial0: tty port ttyS1 registered
[    0.475337] 1c28c00.serial: ttyS2 at MMIO 0x1c28c00 (irq = 34, base_baud = 1500000) is a 16550A
[    0.475519] serial serial1: tty port ttyS2 registered
[    0.481196] modem-power serial1-0: modem power manager ready
[    0.507412] sun4i-drm display-engine: bound 1100000.mixer (ops sun8i_mixer_ops)
[    0.509266] sun4i-drm display-engine: bound 1200000.mixer (ops sun8i_mixer_ops)
[    0.509793] sun4i-drm display-engine: No panel or bridge found... RGB output disabled
[    0.509812] sun4i-drm display-engine: bound 1c0c000.lcd-controller (ops sun4i_tcon_ops)
[    0.510036] sun4i-drm display-engine: bound 1c0d000.lcd-controller (ops sun4i_tcon_ops)
[    0.510071] sun4i-drm display-engine: bound 1ca0000.dsi (ops sun6i_dsi_ops)
[    0.511413] sun8i-dw-hdmi 1ee0000.hdmi: Detected HDMI TX controller v1.32a with HDCP (sun8i_dw_hdmi_phy)
[    0.512092] sun8i-dw-hdmi 1ee0000.hdmi: registered DesignWare HDMI I2C bus driver
[    0.512593] sun4i-drm display-engine: bound 1ee0000.hdmi (ops sun8i_dw_hdmi_ops)
[    0.513357] [drm] Initialized sun4i-drm 1.0.0 20150629 for display-engine on minor 1
[    0.513459] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    0.514580] ehci-platform 1c1b000.usb: EHCI Host Controller
[    0.514605] ehci-platform 1c1b000.usb: new USB bus registered, assigned bus number 3
[    0.514747] ehci-platform 1c1b000.usb: irq 22, io mem 0x01c1b000
[    0.514869] sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
[    0.527975] ehci-platform 1c1b000.usb: USB 2.0 started, EHCI 1.00
[    0.528781] hub 3-0:1.0: USB hub found
[    0.528821] hub 3-0:1.0: 1 port detected
[    0.530117] ohci-platform 1c1b400.usb: Generic Platform OHCI controller
[    0.530142] ohci-platform 1c1b400.usb: new USB bus registered, assigned bus number 4
[    0.530300] ohci-platform 1c1b400.usb: irq 23, io mem 0x01c1b400
[    0.592783] hub 4-0:1.0: USB hub found
[    0.592826] hub 4-0:1.0: 1 port detected
[    0.594175] usb_phy_generic usb_phy_generic.3.auto: supply vcc not found, using dummy regulator
[    0.595241] musb-hdrc musb-hdrc.4.auto: MUSB HDRC host driver
[    0.595268] musb-hdrc musb-hdrc.4.auto: new USB bus registered, assigned bus number 5
[    0.595374] phy id_det change to device
[    0.596106] hub 5-0:1.0: USB hub found
[    0.596145] hub 5-0:1.0: 1 port detected
[    0.701413] Goodix-TS 1-005d: ID 917S, version: 0200
[    0.704980] Goodix-TS 1-005d: Direct firmware load for goodix_917S_cfg.bin failed with error -2
[    0.709406] sun50i-a64-pinctrl 1c20800.pinctrl: supply vcc-pe not found, using dummy regulator
[    0.717453] sunxi-mmc 1c0f000.mmc: Got CD GPIO
[    0.720320] sunxi-mmc 1c0f000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[    0.724934] sunxi-mmc 1c10000.mmc: initialized, max. request size: 16384 KB, uses new timings mode
[    0.727984] input: Goodix Capacitive TouchScreen as /devices/platform/soc/1c2ac00.i2c/i2c-1/1-005d/input/input1
[    0.729721] sunxi-mmc 1c11000.mmc: initialized, max. request size: 2048 KB, uses new timings mode
[    0.732797] scpi_protocol scpi: SCP Protocol 0.0 Firmware 0.0.0 version
[    0.785819] mmc0: new high speed SDHC card at address aaaa
[    0.786660] mmcblk0: mmc0:aaaa SC32G 29.7 GiB
[    0.789380]  mmcblk0: p1 p2
[    0.913181] mmc2: new DDR MMC card at address 0001
[    0.914233] mmcblk2: mmc2:0001  14.7 GiB
[    0.914722] mmcblk2boot0: mmc2:0001  partition 1 4.00 MiB
[    0.915206] mmcblk2boot1: mmc2:0001  partition 2 4.00 MiB
[    0.920124]  mmcblk2: p1 p2 p3 p4 p5 p6 p7 p8 p9 p10
[    0.942291] Console: switching to colour frame buffer device 90x90
[    0.980374] sun4i-drm display-engine: [drm] fb0: sun4i-drmdrmfb frame buffer device
[    0.980397] sun6i-mipi-dsi 1ca0000.dsi: Attached device xbd599
[    0.980431] panel-sitronix-st7703 1ca0000.dsi.0: [drm:st7703_probe] 720x1440@60 24bpp dsi 4dl - ready
[    0.981594] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[    0.983873] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[    0.984439] dw-apb-uart 1c28000.serial: forbid DMA for kernel console
[    0.985738] Freeing unused kernel memory: 1792K
[    0.985924] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[    0.985933] cfg80211: failed to load regulatory.db
[    1.007999] Run /init as init process
[    1.008002]   with arguments:
[    1.008004]     /init
[    1.008007]     PMOS_NO_OUTPUT_REDIRECT
[    1.008009]     PMOS_FORCE_PARTITION_RESIZE
[    1.008011]   with environment:
[    1.008013]     HOME=/
[    1.008016]     TERM=linux
[    1.008018]     pmos_boot=/dev/mmcblk0p1
[    1.008020]     pmos_root=/dev/mmcblk0p2
[    1.127928] anx7688 1-0028: power enabled
[    1.128776] anx7688 1-0028: Vendor id 0x1f29
[    1.143923] anx7688 1-0028: power disabled
[    1.144226] anx7688 1-0028: plug irq (cd=1)
[    1.144348] anx7688 1-0028: enabling USB BC 1.2 detection
[    1.144396] anx7688 1-0028: setting vbus_in current limit to 500000 mA
[    1.159945] anx7688 1-0028: cable inserted
[    1.199936] anx7688 1-0028: power enabled
[    1.265033] anx7688 1-0028: eeprom0 = 0x03
[    1.265296] anx7688 1-0028: fw loaded after 40 ms
[    1.266694] anx7688 1-0028: OCM firmware loaded (version 0x2312)
[    1.277433] anx7688 1-0028: send pd packet cmd=0 05 00 32 90 01 26 12
[    1.313159] anx7688 1-0028: send pd packet cmd=1 05 01 2c 91 01 26 16
[    1.314837] anx7688 1-0028: send pd packet cmd=2 11 02 00 00 00 ec 00 00 00 00 00 00 00 00 39 00 00 51 77
[    1.317613] anx7688 1-0028: send pd packet cmd=3 05 03 00 00 01 ff f8
[    1.319286] anx7688 1-0028: OCM configuration completed
[    1.320676] anx7688 1-0028: status changed to 0x00
[    1.320687] anx7688 1-0028: cc_status changed to CC1 = SRC.Open CC2 = SRC.Open
[    1.320692] anx7688 1-0028: dp state changed to 0x00
[    1.412776] anx7688 1-0028: cc_status changed to CC1 = SRC.Ra CC2 = SRC.Ra
[    1.615869] using random self ethernet address
[    1.615878] using random host ethernet address
[    1.626825] usb0: HOST MAC 5a:5b:2e:43:59:4c
[    1.626868] usb0: MAC 0e:e7:54:d1:5f:33
[    1.664731] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[    3.796147] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[    3.828991] EXT4-fs (mmcblk0p1): warning: mounting unchecked fs, running e2fsck is recommended
[    3.871792] EXT4-fs (mmcblk0p1): mounted filesystem without journal. Opts: (null)
[    3.871849] ext4 filesystem being mounted at /sysroot/boot supports timestamps until 2038 (0x7fffffff)
[    5.728846] device-mapper: table: 253:0: linear: Device lookup failed
[    5.728856] device-mapper: ioctl: error adding target to table
[    5.742333] device-mapper: table: 253:0: linear: Device lookup failed
[    5.742342] device-mapper: ioctl: error adding target to table
[    6.199117] udevd[2015]: starting version 3.2.9
[    6.222950] random: udevd: uninitialized urandom read (16 bytes read)
[    6.224202] random: udevd: uninitialized urandom read (16 bytes read)
[    6.224257] random: udevd: uninitialized urandom read (16 bytes read)
[    6.289950] udevd[2015]: starting eudev-3.2.9
[    6.418497] i2c-gpio i2c-csi: using lines 141 (SDA) and 140 (SCL)
[    6.601725] NET: Registered protocol family 10
[    6.602809] Segment Routing with IPv6
[    6.655172] input: 1c21800.lradc as /devices/platform/soc/1c21800.lradc/input/input2
[    6.775401] input: gpio-vibrator as /devices/platform/vibrator/input/input3
[    6.784933] bt-sco bt-sco-codec: ASoC: sink widget Capture overwritten
[    6.784949] bt-sco bt-sco-codec: ASoC: source widget Playback overwritten
[    6.785058] simple-amplifier audio-amplifier: supply VCC not found, using dummy regulator
[    6.789852] debugfs: File 'Playback' in directory 'dapm' already present!
[    6.789867] debugfs: File 'Capture' in directory 'dapm' already present!
[    6.792114] input: PinePhone Headset Jack as /devices/platform/sound/sound/card0/input4
[    6.816748] iio iio:device3: interrupts on the rising edge
[    6.819492] iio iio:device3: registered magnetometer lis3mdl
[    6.916260] Bluetooth: Core ver 2.22
[    6.916376] NET: Registered protocol family 31
[    6.916380] Bluetooth: HCI device and connection manager initialized
[    6.916410] Bluetooth: HCI socket layer initialized
[    6.916420] Bluetooth: L2CAP socket layer initialized
[    6.916456] Bluetooth: SCO socket layer initialized
[    6.958482] sun6i-csi 1cb0000.csi: creating gc2145 4-003c:0 -> sun6i-csi:0 link
[    6.958495] sun6i-csi 1cb0000.csi: creating ov5640 4-004c:0 -> sun6i-csi:0 link
[    6.966073] Bluetooth: HCI UART driver ver 2.3
[    6.966087] Bluetooth: HCI UART protocol H4 registered
[    6.966177] Bluetooth: HCI UART protocol LL registered
[    6.966249] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    6.967221] dw-apb-uart 1c28400.serial: failed to request DMA
[    6.967418] Bluetooth: HCI UART protocol Broadcom registered
[    7.198951] i2c i2c-2: Added multiplexed i2c bus 5
[    8.279301] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[    8.542949] urandom_read: 5 callbacks suppressed
[    8.542958] random: mktemp: uninitialized urandom read (10 bytes read)
[    8.983590] random: dbus-daemon: uninitialized urandom read (12 bytes read)
[    9.363190] modem-power serial1-0: powering up
[    9.628036] modem-power serial1-0: wakeup ok
[   10.744219] random: crng init done
[   12.575842] modem-power serial1-0: status ok
[   12.576228] dw-apb-uart 1c28c00.serial: failed to request DMA
[   22.843466] usb 3-1: new high-speed USB device number 2 using ehci-platform
[   23.081962] usbcore: registered new interface driver cdc_wdm
[   23.091657] usbcore: registered new interface driver option
[   23.091725] usbserial: USB Serial support registered for GSM modem (1-port)
[   23.092091] option 3-1:1.0: GSM modem (1-port) converter detected
[   23.092545] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB0
[   23.092809] option 3-1:1.1: GSM modem (1-port) converter detected
[   23.094234] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB1
[   23.095691] option 3-1:1.2: GSM modem (1-port) converter detected
[   23.098746] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB2
[   23.099017] option 3-1:1.3: GSM modem (1-port) converter detected
[   23.099878] usb 3-1: GSM modem (1-port) converter now attached to ttyUSB3
[   23.111216] qmi_wwan 3-1:1.4: cdc-wdm0: USB WDM device
[   23.112690] qmi_wwan 3-1:1.4 wwan0: register 'qmi_wwan' at usb-1c1b000.usb-1, WWAN/QMI device, c6:bb:e8:65:3c:e6
[   23.112837] usbcore: registered new interface driver qmi_wwan
[   26.581509] modem-power serial1-0: ===================================================
[   26.581525] modem-power serial1-0: Project Name: EG25G
[   26.581534] modem-power serial1-0: Project Rev : EG25GGBR07A08M2G_01.001.10
[   26.581542] modem-power serial1-0: Branch  Name: 9x07_R07_NEW
[   26.581549] modem-power serial1-0: Custom Name : STD
[   26.581557] modem-power serial1-0: Build   Date: 2019-12-03,18:10
[   26.581566] modem-power serial1-0: Version:    SBLR07EG25G01_1:37500: Oct 17 2
[   26.581573] modem-power serial1-0: Version:    TZR07A03: Dec  2 2019
[   26.581582] modem-power serial1-0: Version:    RPMR07A03_1:37500: Dec  2 2019
[   26.581588] modem-power serial1-0: ===================================================
[   26.581597] modem-power serial1-0: Your modem has an outdated firmware. Latest know version is EG25GGBR07A08M2G_01.002.07. Consider updating.
[   26.591356] modem-power serial1-0: ADB KEY is '32251809' (you can use it to unlock ADB access to the modem, see https://xnux.eu/devices/feature/modem-pp.html)
[   27.635294] modem-power serial1-0: QDAI is '1,1,0,1,0,0,1,1'
[   27.647281] modem-power serial1-0: QCFG 'risignaltype' is '"physical"'
[   27.659370] modem-power serial1-0: QCFG 'urc/ri/ring' is '"pulse",1,1000,5000,"off",1'
[   27.675268] modem-power serial1-0: QCFG 'urc/ri/smsincoming' is '"pulse",1,1'
[   27.691291] modem-power serial1-0: QCFG 'urc/ri/other' is '"off",1,1'
[   27.703313] modem-power serial1-0: QCFG 'urc/ri/pin' is 'uart_ri'
[   27.715373] modem-power serial1-0: QCFG 'urc/delay' is '0'
[   27.727336] modem-power serial1-0: QCFG 'sleepind/level' is '0'
[   27.743366] modem-power serial1-0: QCFG 'wakeupin/level' is '0'
[   27.755288] modem-power serial1-0: QCFG 'ApRstLevel' is '1' (changing to '0')
[   27.779290] modem-power serial1-0: QCFG 'ModemRstLevel' is '0'
[   27.791309] modem-power serial1-0: QCFG 'apready' is '0,0,500'
[   27.803274] modem-power serial1-0: QCFG 'airplanecontrol' is '1,0'
[   27.815301] modem-power serial1-0: AT command 'AT+QCFG="fast/poweroff"' returned ERROR
[   27.839310] modem-power serial1-0: powered up in 18476 ms
[   31.715157] vbat-wifi: disabling
[   31.715197] avdd-csi: disabling
[   31.715260] usb-5v: disabling

Code:
[   27.839310] modem-power serial1-0: powered up in 18476 ms
[   31.715157] vbat-wifi: disabling
[   31.715197] avdd-csi: disabling
[   31.715260] usb-5v: disabling

I see vbat-wifi disabling at the end and rtl8723cs kernel module for wifi doesn't load on turning on the phone or when the phone is rebooted.

ipconfig -a output -
Code:
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:4 errors:0 dropped:0 overruns:0 frame:0
          TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:288 (288.0 B)  TX bytes:288 (288.0 B)

usb0      Link encap:Ethernet  HWaddr D6:BC:2F:DA:FA:00
          inet addr:172.16.42.1  Bcast:172.16.255.255  Mask:255.255.0.0
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

wwan0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          POINTOPOINT NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I have tried different versions of OS and it is same on all. wifi and bluetooth interface is never started on all.

Anyone here encountered this eror? I have tried different options browsing the internet with little, all kinds on help to fix this issue is welcome. Please help!!!


Question No HDMI signal from new Manjaro Community Edition phone dock
Posted by: brianary - 11-08-2020, 09:35 PM - Forum: PinePhone Hardware - Replies (13)

When I plug my new Pinephone into the dock, and the dock to HDMI and power, the screen geometry changes and the mouse pointer (from a USB mouse) disappears off the right side of the screen and takes some time to return, and lxrandr shows the HDMI connection, so I'm confident that the software is correctly detecting the HDMI connection, but there is no picture. I've tried several different HDMI cables and several different screens.

I haven't tried booting anything except the Manjaro distro that came with the phone.

It's a bit frustrating, since so many windows (especially config screens) do not fit on the phone screen, and can't really be used without a larger monitor since I don't know of a way to scale or scroll the display.

Am I missing something? Is there something else I can configure or test? Would I be able to try any USB-C dock, in case that's the issue?

Thanks for any insight!