I'm currently in deep distress: after removing a sim card adapter, it broke one of the SIM slot contact, the bottom left one.
Since this, the id number of the SIM card is not displayed when the PIN code is asked.
So, i've two questions:
* Is this contact really needed, or does it will reduce performance or disable functionnalities?
* Can I repair it easily, since my hands are far from steadies? I've a donor board, namely a 2Go one.
Here is a picture of the butchery.
Thank you in advances, I'll be very glad if someone apease my anxiety about this.
Also, thanks to the community, devs and Pine64 for this wonderful peace of tech.
I would like to find either a wifi or Bluetooth keyboard and mouse setup to use with my RockPro64 from across the room.
I'd like to use the RP64 as a media box and computer (Kodi/TwisterOS). So the IR and USB ports will be pointing right at me.
I have the remote and IR sensor.
I'd like not to have wires on the floor from the mouse and keyboard.
What would the best choice for RP64 be, wifi, or BT?
Thanks
Hats off to everyone who's worked so hard on the PineWatch hardware and the InfiniTime OS!
I received a dev kit a couple of weeks ago and have been using the sealed watch on a daily basis. I thought I would write down some first impressions.
I found it fairly easy to upgrade to Infinitime 1.2.0. (Can't wait to try out Wasp-OS when I have a little more time). I've been keeping it connected to my moto g(7) using Gadget-bridge (installed via F-Droid).
Battery life: about 3 days.
Bluetooth drops about once a day, I can get it back by restarting the watch, force stopping gadgetbridge, and starting it up again.
Flashlight feature has been useful.
Notifications for texts, MS Teams, Outlook, etc. work great!
Watch doesn't show incoming call notifications (though an incoming call test from gadgetbridge's debug screen works just fine).
Infinitime build instructions are fairly straightforward for anyone who's wrestled with building linux software packages and installing dependencies. Made a few tweaks to the digital watchface, recompiled, and uploaded with OTA over bluetooth to the unsealed watch without bricking it. The project looks very well-organized, and I'm looking forward to learning from studying and playing with the code.
Hello,
After, I believe, the second update on phosh 11 the system hangs at the manjaro login screen with the tiny characters before the numerical pad usually comes up. I haven't found any similar problems yet. Thanks for any advice or pointers towards resolving this problem.
I don't have half a clue how this happened. I was trying to install BitWarden desktop app from source and ran into a few snags with node-gyp during build
Below is just some random stuff I was doing in the terminal.
On the first line below, sudo worked. On the last line, sudo suddenly failed and has been broken ever since. Either something I did in the log below somehow broke sudo, or something in the background of PMOS broke it.
Any idea what's going on here? Is there any way to recover other than wiping my phone and reinstalling?
This is a mostly clean install.. PMOS only on the device for about 1 hour, and I only installed some dev libs, git.. basic stuff.
3 packages are looking for funding
run `npm fund` for details
found 0 vulnerabilities
pine64-pinephone:~/Source/desktop$ node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@8.1.0
gyp info using node@14.16.1 | linux | arm64
gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args '/usr/lib/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/home/user/Source/desktop/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/lib/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/home/user/.cache/node-gyp/14.16.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/home/user/.cache/node-gyp/14.16.1',
gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/home/user/.cache/node-gyp/14.16.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/home/user/Source/desktop',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
gyp: binding.gyp not found (cwd: /home/user/Source/desktop) while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/node-gyp/lib/configure.js:353:16)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Linux 5.11.0
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/user/Source/desktop
gyp ERR! node -v v14.16.1
gyp ERR! node-gyp -v v8.1.0
gyp ERR! not ok
pine64-pinephone:~/Source$ cd ..
pine64-pinephone:~/Source$ find . -name "binding*"
./node-gyp/docs/binding.gyp-files-in-the-wild.md
./node-gyp/test/node_modules/hello_world/binding.gyp
pine64-pinephone:~/Source$ cd node-gyp/test/node_modules/hello_world/
pine64-pinephone:~/Source/node-gyp/test/node_modules/hello_world$ node-gyp rebuild
gyp info it worked if it ends with ok
gyp info using node-gyp@8.1.0
gyp info using node@14.16.1 | linux | arm64
gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args '/usr/lib/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args 'binding.gyp',
gyp info spawn args '-f',
gyp info spawn args 'make',
gyp info spawn args '-I',
gyp info spawn args '/home/user/Source/node-gyp/test/node_modules/hello_world/build/config.gypi',
gyp info spawn args '-I',
gyp info spawn args '/usr/lib/node_modules/node-gyp/addon.gypi',
gyp info spawn args '-I',
gyp info spawn args '/home/user/.cache/node-gyp/14.16.1/include/node/common.gypi',
gyp info spawn args '-Dlibrary=shared_library',
gyp info spawn args '-Dvisibility=default',
gyp info spawn args '-Dnode_root_dir=/home/user/.cache/node-gyp/14.16.1',
gyp info spawn args '-Dnode_gyp_dir=/usr/lib/node_modules/node-gyp',
gyp info spawn args '-Dnode_lib_file=/home/user/.cache/node-gyp/14.16.1/<(target_arch)/node.lib',
gyp info spawn args '-Dmodule_root_dir=/home/user/Source/node-gyp/test/node_modules/hello_world',
gyp info spawn args '-Dnode_engine=v8',
gyp info spawn args '--depth=.',
gyp info spawn args '--no-parallel',
gyp info spawn args '--generator-output',
gyp info spawn args 'build',
gyp info spawn args '-Goutput_dir=.'
gyp info spawn args ]
internal/modules/cjs/loader.js:883
throw err;
^
Error: Cannot find module 'nan'
Require stack:
- /home/user/Source/node-gyp/test/node_modules/hello_world/[eval]
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:880:15)
at Function.Module._load (internal/modules/cjs/loader.js:725:27)
at Module.require (internal/modules/cjs/loader.js:952:19)
at require (internal/modules/cjs/helpers.js:88:18)
at [eval]:1:1
at Script.runInThisContext (vm.js:133:18)
at Object.runInThisContext (vm.js:310:38)
at internal/process/execution.js:77:19
at [eval]-wrapper:6:22
at evalScript (internal/process/execution.js:76:60) {
code: 'MODULE_NOT_FOUND',
requireStack: [ '/home/user/Source/node-gyp/test/node_modules/hello_world/[eval]' ]
}
gyp: Call to 'node -e "require('nan')"' returned exit status 1 while in binding.gyp. while trying to load binding.gyp
gyp ERR! configure error
gyp ERR! stack Error: `gyp` failed with exit code: 1
gyp ERR! stack at ChildProcess.onCpExit (/usr/lib/node_modules/node-gyp/lib/configure.js:353:16)
gyp ERR! stack at ChildProcess.emit (events.js:315:20)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:277:12)
gyp ERR! System Linux 5.11.0
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/user/Source/node-gyp/test/node_modules/hello_world
gyp ERR! node -v v14.16.1
gyp ERR! node-gyp -v v8.1.0
gyp ERR! not ok
pine64-pinephone:~/Source/node-gyp/test/node_modules/hello_world$ sudo apk add g++
sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
Code:
pine64-pinephone:~$ ls -l /usr/bin/sudo
-rwxr-xr-x 1 root 1000 141224 Jan 26 19:06 /usr/bin/sudo
Heyoh, I had purchased the PB-Pro Docking Deck recently and seem to be having some issues with it. Primarily, I can't seem to charge my Pinebook Pro off of it, and secondarily, It's not connecting to the plugged in ethernet...
The dock didn't come with any extra charging cables, so I just plugged in the PB-Ps charger directly into the docking bar, then the dock into the PB via the USB-C cable (in the one and only usb-c port). The PB does appear to be able to read SSDs that are plugged into the bar, so I feel like the USB-C itself is fine. The ethernet port is blinking as if it is transferring data, but only WiFi options appear. I'm using Manjaro ARM XFCE 21.04 atm, if that plays into it. Thanks in advance!
Hi! I run manjaro ARM on my pinebook pro. After the latest `pamac upgrade`, I've started to get regular lockups. Checking `journalctl` I have this kernel error in there:
To date, there are only 3 meaningful types of performant and readily available ARM64 desktop workstations:
- M1 Mac Mini / iMac
- Nvidia Xavier NX/AGX
- Honeycomb LX2
All other "look at me, I haz arm" devices are either laptops, puny tablets trying to imitate laptops or plain devboards with an Android image or a quarter-functional, outdated Debian..
They mostly use smartphone chips, sometimes higher frequency-binned and with a more liberal power limit. And they lack HW documentation. Or they are discontinued.
What is truly needed to kickstart the ARM64 ecosystem further is a good desktop workstation.
In such a board, I reckon there should be:
some kind of ATX standard form factor to mount it in a regular PC case with a regular PC power supply
socketed RAM
PCIe, USB, SATA, 3.5mm jack, RJ45..
a power and a force reset button
a chip to keep the bootloader on, so as to make the OS installation simpler
targetting Arm SystemReady certification, which given enough work on proper UEFI, would allow for installing OSes like on a normal PC, from a livecd etc..
an OSS-friendly SoC that can heat up as much as it wants - performance is key in this form factor! (without a broken PCIe implementation, I'm looking at you, Raspberry Pi...)
Intel-/AMD-compatible mounting holes for a cooler
DC/PWM fan headers (may be on a separate controller)
I was thinking, perhaps Pine could be a good vendor to tackle this? Of course, this is a complicated problem to solve, but discussion is a good thing.
