Welcome, Guest |
You have to register before you can post on our site.
|
Latest Threads |
google will take control ...
Forum: General
Last Post: bilaljack23
7 hours ago
» Replies: 22
» Views: 8,515
|
PINETAB-V doesn't boot.
Forum: Getting Started
Last Post: FEC
9 hours ago
» Replies: 0
» Views: 12
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
Yesterday, 01:51 PM
» Replies: 4
» Views: 242
|
Trying to attach a serial...
Forum: RockPro64 Hardware and Accessories
Last Post: marietto
Yesterday, 08:50 AM
» Replies: 0
» Views: 27
|
Full desktop Surfing and ...
Forum: General Discussion on Pinebook Pro
Last Post: KC9UDX
08-02-2025, 08:55 PM
» Replies: 1
» Views: 242
|
Keyboard availability?
Forum: PinePhone Pro Accessories
Last Post: Peter Gamma
08-02-2025, 01:00 PM
» Replies: 8
» Views: 1,053
|
* /lib64 is a symbolic li...
Forum: PineNote Software
Last Post: Francus
08-02-2025, 08:16 AM
» Replies: 3
» Views: 179
|
incorporate a multimeter ...
Forum: General
Last Post: hinomi
07-31-2025, 03:39 PM
» Replies: 1
» Views: 380
|
Pine Phone Pro audio on p...
Forum: PinePhone Pro Software
Last Post: DominiqueM
07-31-2025, 05:37 AM
» Replies: 49
» Views: 36,115
|
Want to buy second hand P...
Forum: General Discussion on PinePhone
Last Post: MaryOtero
07-31-2025, 01:14 AM
» Replies: 1
» Views: 1,298
|
|
|
New PinePhone died after first WiFi setup |
Posted by: phero - 03-03-2022, 10:09 AM - Forum: General Discussion of PinePhone Pro
- Replies (8)
|
 |
Hi all!
I recently got my PinePhone and currently it's showing no signs of life. Not even a red led.
Here's what I did once I unboxed it.
1. Let it warm up to room temperature and dehumidify over 24 hours.
2. Removed the plastic covering the battery connections.
3. Connected the red USB to a USB2 charger and inserted the cable in the phone.
4. Waited approx. 5 hours. (Phone felt a little warm to the touch)
5. Removed the charging cable.
6. Held the Power button 2 seconds. Didn't work
7. Tried that a few more times. No luck.
8. Inserted the USB charging cable with power connected.
9. Held the Power button 2 seconds.
10. Phone turns on.
11. I complete the initial steps and finish off by entering my WiFi credentials.
12. Screen displays "Setup Complete"
13. Screen goes black with an audible click coming from the speaker. (Sounded like when the DC offset changes)
14. Phone stays off.
15. Power button does nothing.
16. No light from led neither red nor green.
17. Flash SD card with Mobian and insert it into the SD card slot.
18. Try to power on.
19. No life whatsoever.
Is the phone completely bricked or can I recover it somehow?
Thanks in advance for any help you can give me!
|
|
|
Getting Waydroid to work on the Pinephone Pro |
Posted by: Dragonborn - 03-03-2022, 10:03 AM - Forum: PinePhone Pro Software
- Replies (8)
|
 |
Went to a lot of trouble to get Waydroid running on the Pinephone Pro. Seems to be running pretty smooth now (as smooth as it will run without hardware acceleration anyways).
Waydroid is technically not supported yet on the Pro. Hardware acceleration is broken, so you have to disable it due to a Mesa / Android conflict. I am on Mobian Bookworm, so this post outlines what I did to get it working on Mobian Bookworm specifically. Your instructions might vary slightly on different distros or builds of Mobian.
Note: You will be editing your U-boot config file here if you are on Mobian. Doing this wrong can make your device not boot correctly. I’m not responsible for bricked devices if you break your config. The Mobian resource below has all of these instructions save for the hardware acceleration disabling. I’d recommend using the listed instructions over mine. The only thing in this post not included in either of these links is the hardware acceleration disabling.
Refer to these instructions:
Mobian specific, I used the desktop install method and not source compiling: https://wiki.mobian-project.org/doku.php?id=waydroid
Use the Ubuntu/Debian desktop specific instructions here: https://docs.waydro.id/usage/install-on-desktops
After you install the Waydroid package via the instructions, do not use
until you have done the Mobain specific instructions on the mobian page. This will cause Waydroid to not work for some reason. I got gbinder errors doing this, but your milage may very.
Mobain Specific Install Instructions
Add this to the bottom of “/etc/gbinder.conf” [NOTE: My file was named anbox.conf and it still worked]
Code: [General]
ApiLevel = 29
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is Mobian specific. I do not believe you need this on other distros. Refer to the Mobian wiki page linked above for this step.
Add this line to U_BOOT_PARAMETERS in “/etc/default/u-boot”:
after vt.global_cursor_default=0
Be very careful here. If you add this config wrong you might break u-boot. Please use the listed Mobain wiki resource here and ensure you add this correctly. I’m not responsible for bricked devices if this goes wrong. I triple checked my config versus the listed code on the Mobian wiki before running the next command.
After you are sure your config is written properly, run
and reboot the phone.
------------------------------------------------------------------------------------------------------------------------------------------------------------------
Almost done now. You need to disable hardware acceleration as of this post to make Waydroid work on the PPP.
Make the following changes in “/var/lib/waydroid/waydroid_base.prop”:
Change the value of ro.hardware.gralloc to "default" as shown:
Code: ro.hardware.gralloc=default
Change the value of ro.hardware.egl to "swiftshader" as shown:
Code: ro.hardware.egl=swiftshader
Save and exit the file.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is it, now run:
Code: systemctl enable waydroid-container.service
Now you can run
At this point it will install the LineageOS image and other dependencies. After this is compete, if you did everything correctly, you should be able to run
Code: waydroid session start
in the terminal and get Waydroid to work. The Mobain guide says starting via the Phosh app drawer will start the session. You can try it this way, but it takes around 20 seconds to get anything more than a blank screen. Seems spotty and slow to me, so if it doesn’t do it consistently I will add a comment to this post with a bash script to auto start the session on boot.
You can now launch the Waydroid app via the Phosh app drawer, and you are done!
Hope this helped you. Please refer to the documentation above for 99% of the instructions. Only thing I added to them was the hardware acceleration disabling.
|
|
|
Replace PPP sim card/sd card slot hardware |
Posted by: tckosvic - 03-03-2022, 09:10 AM - Forum: PinePhone Pro Hardware
- Replies (5)
|
 |
Looking for replacement for SA-2202-112 25-pin Micro-SIM and TF slot as referenced from PPP parts list.
PPP will not read my consumer cellular sim card and it is difficult to insert or remove sd cards. It used to read sim card fine and I could make phone calls, sms, and mms using manjaro-phosh. Now nothing. No software fixes work so it must be the hardware. Perhaps too many inserts/removals.
I can't find replacement on PPP spare parts site. Search for part doesn't pick up anything on internet. Amazon has some slot hardware but nothing looks simillar.
Anyone found a hardware source? Anyone changed one out successfully?
thanks, tom kosvic
|
|
|
What can/can't I do with a PineTime smart watch (sealed)? |
Posted by: danimations - 03-03-2022, 08:08 AM - Forum: General Discussion on PineTime
- Replies (7)
|
 |
Could someone please tell me what the PineTime (sealed) can and can't do? I'd like to use one as a conventional wrist watch, but with my own theme/skin if possible. I'd like to load my own custom font and background image for the display, and sound scheme (if it has sound). Anything else is a bonus. I haven't had a smart watch before, so I'm keen to learn about the device's potential. What information does the device send/receive via bluetooth?
*Edit: since posting, I've discovered that the bundled OS is called Infinitime, and the current version (1.8.0) appears to include three clock variations (digital and analog) plus some neat apps, like a metronome and stopwatch, and even a couple of games. There's a repo on GitHub and a website for InfiniTime that suggest more apps/features are on the way. I'm keen to learn what else is in the pipeline.
Thanks in advance.
|
|
|
Convergence Thread (PinephonePro) |
Posted by: magdesign - 03-03-2022, 04:55 AM - Forum: General Discussion of PinePhone Pro
- Replies (6)
|
 |
Convergence is "the thing" which I try to push on PinephonePro.
Connecting a 1920x1080p screen (even bigger ones do work) via USB-C to hdmi adaptor works so far.
Also simulating a mouse with the great app from [Adam Honse](https://gitlab.com/CalcProgrammer1/TouchpadEmulator).
But I have several issues which someone might help to fix or point me into the right direction:
The first time I connected a screen, the KDE Screen Layout Widget popped up and I was able to select the screen layout,
kind of this (was more squeezed over all screens):
![[Image: b656ec9c3c6e2db97a658cd7cc6e9fda4908de1d.jpeg]](https://forum.manjaro.org/uploads/default/original/3X/b/6/b656ec9c3c6e2db97a658cd7cc6e9fda4908de1d.jpeg)
However, when you select a wrong configuration here, you will never ever be able to get back to this widget.
Any KDE expert knowing how to trigger this widget? via terminal or via keyboard shortcut?
Where does KDE save this made joices, where is the whole screensetting stuff stored?
What I figured out so far:
=> get info about connected screens
Code: kcmshell5 kwindecoration
kcmshell5 kwincompositing
kcmshell5 kwinoptions
kcmshell5 kwinscreenedges
kcmshell5 kwinscripts
=> popups some screen related widgets
Sidenote:
Testing all kind of programs if and how they run in convergence, weird thing is, in convergence the navigation panel disappears and its hard to close any programm.
Would also be nice to be able to activate window borders to minimize and maximize each program.
Any constructive inputs very welcome :-)
|
|
|
|