| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,964
» Latest member: gesav72643
» Forum threads: 16,334
» Forum posts: 117,438
Full Statistics
|
| Latest Threads |
Looking for engineer for ...
Forum: PinePhone Pro Hardware
Last Post: Andrey_voce
Yesterday, 08:44 AM
» Replies: 0
» Views: 59
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
04-05-2026, 03:03 AM
» Replies: 19
» Views: 8,529
|
Finally got Kali working ...
Forum: General Discussion on Pinebook Pro
Last Post: qingss0
04-04-2026, 08:00 AM
» Replies: 0
» Views: 128
|
Charging problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
04-04-2026, 07:30 AM
» Replies: 0
» Views: 71
|
Latest firmware for PineP...
Forum: PinePhone Software
Last Post: baptx
04-03-2026, 08:37 AM
» Replies: 106
» Views: 215,702
|
Updates have gotten me ex...
Forum: General Discussion on PineNote
Last Post: bills2002
04-02-2026, 05:16 PM
» Replies: 0
» Views: 121
|
Voidlinux working on eMMC
Forum: General Discussion on PineTab
Last Post: tllim
04-01-2026, 04:14 PM
» Replies: 1
» Views: 188
|
Pinecil V2 doesn’t power ...
Forum: General Discussion on Pinecil
Last Post: Juptin
03-28-2026, 02:37 AM
» Replies: 1
» Views: 2,022
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: williamcorlin
03-26-2026, 04:22 PM
» Replies: 3
» Views: 897
|
BT PAN - we need iptables...
Forum: Mobian on PinePhone
Last Post: biketool
03-25-2026, 12:57 PM
» Replies: 1
» Views: 575
|
|
|
| Has this forum resulted in changes to new pinephonero? |
|
Posted by: tckosvic - 05-05-2022, 07:54 AM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
Thousands of thoughts, observations, and insights have been posted in this PinePhone Pro forum. Have these reverberated back to Pine64? Is the PPP you got in January the identical PPP you receive now on a new order? I am questioning whether any software or hardware updates have been made to the basic phone. The ad pages for PinePhone do not seem, from a superficial review, to have changed at all.
tom kosvic
|
|
|
|
| Discover crashing (terminal output included). |
|
Posted by: allworlds - 05-04-2022, 06:55 PM - Forum: Manjaro on PinePhone
- Replies (1)
|
 |
Manjaro-Plasma installed from the "Factory Image 202203111950" to the eMMC. Discover worked at first but then broke. Running from the GUI apps menu shows the start splash for a while then nothing; running from the terminal gives a segfault error. I think an update by pacman -Syu from the terminal is what broke discover but I'm not completely sure about that.
I have the output from running plasma-discover $> out.txt in the terminal.
Code: qrc:/qml/DiscoverWindow.qml:116:19: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86): This returns 1 when using Qt HiDPI scaling.
kf.kirigami: Units.wheelScrollLines is deprecated (since 5.86): Use Qt.styleHints.wheelScrollLines instead
file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:674:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 14. Use 'sequences: [ <key> ]' to bind to all of them.
file:///usr/lib/qt/qml/org/kde/kirigami.2/PageRow.qml:670:5: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 13. Use 'sequences: [ <key> ]' to bind to all of them.
QObject::startTimer: Timers cannot have negative intervals
qrc:/qml/DiscoverPage.qml:42:37: QML Shortcut: Shortcut: Only binding to one of multiple key bindings associated with 15. Use 'sequences: [ <key> ]' to bind to all of them.
org.kde.plasma.libdiscover: error loading "fwupd-backend" "Cannot load library /usr/lib/qt/plugins/discover/fwupd-backend.so: (libfwupd.so.2: cannot open shared object file: No such file or directory)" QJsonObject({"IID":"org.kde.muon.AbstractResourcesBackendFactory","archreq":0,"className":"FwupdBackendFactory","debug":false,"version":331520})
adding empty sources model QStandardItemModel(0xaaaabb016450)
file:///usr/lib/qt/qml/org/kde/kirigami.2/private/PrivateActionToolButton.qml:74:5: QML Binding: Binding loop detected for property "value"
kf.kirigami: Units.wheelScrollLines is deprecated (since 5.86): Use Qt.styleHints.wheelScrollLines instead
kf.kirigami: Units.devicePixelRatio is deprecated (since 5.86): This returns 1 when using Qt HiDPI scaling.
file:///usr/lib/qt/qml/org/kde/kirigami.2/BasicListItem.qml:273:18: QML QQuickItem*: Binding loop detected for property "implicitWidth"
file:///usr/lib/qt/qml/org/kde/kirigami.2/GlobalDrawer.qml:333:17: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
file:///usr/lib/qt/qml/org/kde/kirigami.2/GlobalDrawer.qml:354:13: QML ColumnLayout: Binding loop detected for property "height"
file:///usr/lib/qt/qml/org/kde/kirigami.2/GlobalDrawer.qml:354:13: QML ColumnLayout: Binding loop detected for property "height"
QQuickItem::stackBefore: Cannot stack QQuickItem(0xaaaabb2c9d10, parent=0xaaaabab0d0a0, geometry=0,0 0x0) before QQuickPopupItem(0xaaaaba95a9d0), which must be a sibling
file:///usr/lib/qt/qml/org/kde/kirigami.2/GlobalDrawer.qml:333:17: QML RowLayout (parent or ancestor of QQuickLayoutAttached): Binding loop detected for property "preferredHeight"
file:///usr/lib/qt/qml/org/kde/kirigami.2/AbstractApplicationWindow.qml:282:5: QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15 after any QtQuick imports and set
the restoreMode of the binding to fix this warning.
In Qt < 6.0 the default is Binding.RestoreBinding.
In Qt >= 6.0 the default is Binding.RestoreBindingOrValue.
And then it segfaults.
Searching the web I've not been able to find much useful. https://forum.kde.org/viewtopic.php?t=173712 reported what might be the same issue, including the error about fwupd, but got no solution.
I tried reinstalling plasma-discover and packagekit but no help. I don't know where the relevant configuration files are either.
|
|
|
|
| Umbrel Server |
|
Posted by: Shaeroden - 05-04-2022, 06:14 PM - Forum: RockPro64 Projects, Ideas and Tutorials
- No Replies
|
 |
I bought this board in the hopes that i could spare myself the hassle of getting a raspberry pi 4 during a chip shortage on top of a scalping mania, and run umbrel on the rockpro64 board.
has anyone come across some good tutorials for this? I tried going through this tutorial but I contacted the author through twitter and he said the whole blog post is out of date, given umbrel's many updates since then.
they make it sound so easy to set up on the raspberry pi 4, and I went ahead and overpaid for one anyways, but I'd still like to be able to run umbrel on the rockpro64, since there have been reported power delivery problems with running multiple drives on a raspberry pi.
|
|
|
|
| Sold my Pinephone |
|
Posted by: Frankie - 05-04-2022, 08:48 AM - Forum: General Discussion on PinePhone
- Replies (3)
|
 |
Greetings,
So I finally sold my PinePhone as I just couldn't live with trying to use it as a phone. As a device it's been great to play around with but as a phone it just didn't work out at all IMO.
I've read post on here of people saying they use it and well, good for them, if it works for you then great. However I tried Mobian and Manjaro Phosh but they just didn't work well enough for me. When I was out and about it would just go to answer phone if somebody called. If it did manage a call then when it switched from 4g to 3g it would just go silent and I would have to end the call, if I locked it to one then it would just go to answer phone again.
These problems and the terrible battery life meant I could not live with it.
I love the idea of a real Linux phone though and would be willing to pay quite a bit more if somebody comes up with something better in the future. Kept my PineTime as apart from a few lines it has developed on the screen and the fact that it sometimes wont do anything when I press the button to active it for a while (usually works if I place it on it's charger) then I am more than happy with it for the price!
Happy to have supported the project and I let the phone go for cheap to give somebody else a chance.
|
|
|
|
Pinephone user experience - Possibly compromised by commercial & state-based hackers? |
|
Posted by: danimations - 05-04-2022, 06:11 AM - Forum: General Discussion on PinePhone
- Replies (15)
|
 |
I have experienced extraordinary and inexplicable behaviors with my Pinephone (Community Edition) since using it as a daily driver from late 2020.
I've asked myself why what I believe to be temporary hacks may be undertaken and have formed a few hypotheses that I'd like to share with fellow users.
Firstly, many people here should be savvy enough to realise that the Pinephone represents a threat to the otherwise aggregious access into users lives that Android and Apple devices provide. As such, there is a case for three and four letter agencies in various countries to conspire to degrade the user experience of Pinephone users in a targeted way. Why do this? To deter their use as daily drivers, quell early adopters' enthusiasm and generally slow the device's spread into the wider community. That I believe is the potential government motive for such nefarious activity.
The other parties interested in achieving similar goals are Pinephone's commercial competitors, of which there are many. The likes of Google, Apple, Samsung, Sony, LG, Nokia etc. would all consider Pinephone a small but real threat to their business interests. Would tech corporations commission hackers to target early adopters to damage the reputation of Pinephone and slow its uptake? I can only speculate... but I can see a clear motive for them to do so.
So where does this leave us, as determined enthusiasts that want to see Pinephone and other Linux phones thrive in the wild?
I think it would be helpful for people here to compare notes on how to best secure our devices against cyberattacks/hacking, and combine resources in investigating cases where it occurs or is likely to have occurred.
My own circumstances have an extra layer of confounding context, due to my ongoing, personal soft advocacy for the release of Julian Assange, founder and publisher of Wikileaks, who faces extradition to the USA after years of torture in the UK. Last year, it became a matter of public record that the CIA had cast a dragnet to intrude into and interfere with the lives of his remaining supporter base, after years of malicious attempts to erode it and smear Julian's character. That agency's interest in my life has made itself known in Australia, so if you think "this couldn't happen to me" it may pay to reflect on the far-reaching nature of the surveillance state today, our political context and what Pinephone represents. Pinephone is a smartphone for the people, by the people... and one that allows those of us who seek to, to draw the blinds on the covert use of our devices for commercial or political purposes.
I look forward to other users' thoughts on this subject.
|
|
|
|
| Screen Lock |
|
Posted by: Dinosaur1946 - 05-03-2022, 05:03 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
Hi All
After many months of using the Pine64 with Mobian, I am basically happy with it.
Have even been able to install Geany and run my application in Debug to control industrial hardware.
BUT, just two annoying issues.
1: At unpredictable times the screen won't come on and I have to power the phone down
and back up again.
2: Password not recognized so I have to reboot.
Worth noting here that I am doing the daily update / ugrade, ie: today 76 upgrades.
Have seen many improvements over the last few months, but have been patiently waiting to see
if the above two issues are getting resolved.
Alas, no.
Browsing and looking for solutions produced zilch.
So, the question, is there a fix out there for at least issue 1:
Not knowing that your phone is non-responsive is an issue when Text messages and phone calls don't get through.
Regards
|
|
|
|
| Battery Life is it possible?? Tech Question (sort of) |
|
Posted by: scrwbigtek - 05-03-2022, 04:44 PM - Forum: General Discussion of PinePhone Pro
- Replies (4)
|
 |
Hello,
Really dumb question. I'm not super up to speed yet on the whole Pinephone stuff so forgive me.
Got the Pinephone Pro and I realize it is still in the works. Most know the battery life is an issue right now, no complaining here, just curious.
So will it be possible to get iPhone like battery life one day out of it?
I have a iPhone SE2 now. How in the world do they get that much battery life out it?
Is it a bigger battery? Is it sophisticated power management software? Both?
If Apple can do it Linux can do it right?
Or is there some hardware limitation that the Pinephone Pro that it will not be able to sip and and conserve its battery like an iPhone?
thanks!
|
|
|
|
| Change tow-boot boot order or otherwise make Mobian on uSD the default? |
|
Posted by: allworlds - 05-03-2022, 06:50 AM - Forum: PinePhone Software
- Replies (3)
|
 |
I've dusted off my old Pinephone and I'm giving it another go. New(ish) to Pinephone, new to Manjaro, not new to Debian or Linux generally.
I've installed tow-boot as directed by Mobian's Wiki, flashed Manjaro-Plamsa to the eMMC, and have Mobian-Phosh on the micro SD card. With this setup it boots to the eMMC install by default, but at the moment I'm mainly using Mobian and want to boot to that by default. Rather than having to remember to hold volume down after every reboot.
|
|
|
|
|