| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 30,200
» Latest member: luka
» Forum threads: 16,382
» Forum posts: 117,593
Full Statistics
|
| Latest Threads |
Fixing the Quartz64 USB3 ...
Forum: Quartz64 Tutorials
Last Post: mig
Yesterday, 01:32 AM
» Replies: 1
» Views: 12,750
|
Pinecil as a Pocket-Sized...
Forum: General
Last Post: Arsen
08-27-2026, 09:15 AM
» Replies: 0
» Views: 76
|
SlateOS feedback needed!
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-24-2026, 08:00 AM
» Replies: 0
» Views: 147
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: Nambo
08-23-2026, 12:17 AM
» Replies: 18
» Views: 13,534
|
Hello, I am a new member ...
Forum: General
Last Post: WhiteRabbit0
08-20-2026, 12:17 PM
» Replies: 0
» Views: 343
|
Need help compiling andro...
Forum: Android on Pine A64(+)
Last Post: ahegarosib97
08-20-2026, 08:45 AM
» Replies: 2
» Views: 2,006
|
RAM-free SBCs with SODIMM...
Forum: General
Last Post: anchor
08-20-2026, 08:21 AM
» Replies: 0
» Views: 151
|
Default password
Forum: PineTab Hardware
Last Post: dissimilar_goose
08-20-2026, 05:02 AM
» Replies: 0
» Views: 211
|
New SlateOS features
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:47 PM
» Replies: 0
» Views: 241
|
SlateOS for PineTime
Forum: Development Discussion on PineTime
Last Post: highjumpman
08-17-2026, 07:33 PM
» Replies: 2
» Views: 521
|
|
|
| App Development |
|
Posted by: rkveale - 01-22-2021, 07:45 AM - Forum: PinePhone Software
- Replies (4)
|
 |
I am interested in doing some app development for Linux phones. I have developed some Android apps using Android Studio but I am not that familiar with Linux except for some tinkering with Python for the Raspberry Pi and the Jetson Nano. I need some big picture instruction of the tools and methods I need to develop apps for the Pine Phone. This newbie needs some help.
|
|
|
|
| Hanging on PINE TIME screen - UPDATE now just blank |
|
Posted by: andystratton - 01-22-2021, 04:45 AM - Forum: General Discussion on PineTime
- No Replies
|
 |
So I charged my Pine Time on Saturday, updated Infinitime (using nRF and OTA) to 0.8.3 (which I validated) then 0.10.0 (which I didn't) and then sometime yesterday the battery ran out.
I put it on charge - and the green 'PINE TIME' screen comes up (after a brief bit of random static).
The PINE TIME screen just stays on until the battery dies again (I haven't fully charged it, since it could take a long time to run out of battery).
If I press the button, or long press (10 seconds+), nothing happens.
UPDATE - now with the charger on, it is blank screen - no static, no PINETIME, and button doesn't do anything. This acts completely dead.
Any advice please.
Note: I'm trying to do this without disconnecting the battery - though since I've run the battery to switch off - it shouldn't be different (should it?). I'd like to be able to develop without having to have the back falling off all the time - I'd really like to glue the back on...
Thank you in advance
Andy
Update again - left off charge for a while - when put on charge, reverted to original hanging behaviour - static - PINE TIME then hang.
|
|
|
|
| Screen Protector |
|
Posted by: JayKyburz - 01-21-2021, 10:48 PM - Forum: PinePhone Hardware
- Replies (9)
|
 |
Hi All, My KDE edition arrived today and I super excited to start playing around with it.
I have one tiny problem, it looks like somebody has put a screen protector on it before shipping it to me, but they put it on crooked and there a few air bubbles.
Do you think if I try and pull it off I'll damage the screen?
Jay.
|
|
|
|
| Verizon call/text fix |
|
Posted by: syrinx - 01-21-2021, 03:01 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
According to https://wiki.pine64.org/index.php?title=...rt#Verizon "Some Verizon users have had calls and and text stop working after around 2 weeks of use. This can be resolved by contacting Verizon support." Has anybody managed do do this successfully? If so, what should I tell support. After the massive headache of getting them to send me a sim, I am not in the mood for spending all day on the phone trying to explain to them what a pinephone is
|
|
|
|
| Kernel oops after big-ish writes |
|
Posted by: gaeb - 01-21-2021, 01:05 PM - Forum: Linux on RockPro64
- Replies (1)
|
 |
I've been trying to set up a rockpro64 for the purposes of a home server for backups; I have flashed the SPI so as to be able to boot off a USB. I had a Debian official installation on an SD with encrypted root going back in December when I noticed that any write operations larger than a few MB would give me a kernel oops (using tools like scp and rsync), and when I left it up for the holidays for a couple weeks, the machine crashed on its own. This problem seems to be independent of which OS I use; I've been trying to switch to Manjaro by flashing a USB stick and then rsyncing the contents of the root partition to a luks volume on an sd card, and I get a similar oops.
It seemed very similar to the problem described in this thread, but the solution offered here (compiling my own device tree blobs with trusted firmware) didn't yield any different behavior; although the thread leads me to suspect that it may have something to do with my having flashed the SPI partition, and there's firmware from when the rockpro64 booted off SPI still running that the kernel bumps into? However, I've used ayufan's as well as sigmaris' latest releases (sigmaris seems to be using atf for the dtb), and I continue to get kernel crashes.
What follows are the kernel messages from the most recent crash. I'm fairly new to dealing with things like this, so please let me know if I'm missing information that would be helpful.
Code: #### lots of rsync to sd happening before this, when suddenly... ####
[ 283.352255] Unable to handle kernel paging request at virtual address 000000000000b200
3,797 100% 14.[ 283.353084] Mem abort info:
60kB/s 0:00:00 (xfr#7615, ir-chk=1015/10770)
rsync: connecti[ 283.353853] ESR = 0x96000004
on unexpectedly closed (478578 bytes received so far) [generator[ 283.354546] EC = 0x25: DABT (current EL), IL = 32 bits
]
rsync error: error in rsync protocol data stream (code 12) at[ 283.355484] SET = 0, FnV = 0
io.c(228) [generator=v3.2.3]
[ 283.356229] EA = 0, S1PTW = 0
[ 283.356735] Data abort info:
[ 283.356994] ISV = 0, ISS = 0x00000004
[ 283.357335] CM = 0, WnR = 0
[ 283.357603] user pgtable: 4k pages, 48-bit VAs, pgdp=00000000f5a93000
[ 283.358171] [000000000000b200] pgd=0000000000000000, p4d=0000000000000000
[ 283.358775] Internal error: Oops: 96000004 [#2] SMP
[ 283.359207] Modules linked in: btrfs blake2b_generic xor xor_neon zstd_compress raid6_pq dm_crypt zram des_generic libdes cfg80211 8021q md4 garp mrp stp llc realtek rc_cec hci_uart snd_soc_simple_card dw_hdmi_cec snd_soc_audio_graph_card snd_soc_simple_card_utils btqca pwm_fan btrtl btbcm dw_hdmi_i2s_audio panfrost btintel dwmac_rk gpu_sched stmmac_platform bluetooth rockchip_rga hantro_vpu(C) stmmac rockchip_vdec(C) videobuf2_dma_sg ecdh_generic v4l2_h264 v4l2_mem2mem snd_soc_rockchip_i2s ecc snd_soc_rockchip_pcm videobuf2_vmalloc rfkill dw_wdt mdio_xpcs videobuf2_dma_contig videobuf2_memops phylink videobuf2_v4l2 videobuf2_common snd_soc_es8316 rtc_rk808 rockchip_saradc snd_soc_hdmi_codec rockchip_thermal gpio_keys rockchipdrm analogix_dp dw_hdmi cec rc_core dw_mipi_dsi drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm drm_panel_orientation_quirks
[ 283.366001] CPU: 1 PID: 690 Comm: rsync Tainted: G D C 5.9.13-1-MANJARO-ARM #1
[ 283.366735] Hardware name: Pine64 RockPro64 v2.1 (DT)
[ 283.367185] pstate: 60000005 (nZCv daif -PAN -UAO BTYPE=--)
[ 283.367688] pc : fsnotify_destroy_marks+0x1f4/0x420
[ 283.368124] lr : fsnotify_grab_connector+0x28/0xf0
[ 283.368548] sp : ffff800010c03d60
[ 283.368843] x29: ffff800010c03d60 x28: ffff0000f6f51c80
[ 283.369315] x27: 0000000000000000 x26: 0000000000000000
[ 283.369786] x25: 0000000000000000 x24: 0000000000000000
[ 283.370258] x23: ffff800012daa000 x22: ffff800012daa0c8
[ 283.370730] x21: 0000000000000000 x20: ffff800013004020
[ 283.371201] x19: 000000000000b200 x18: 0000000000000000
[ 283.371673] x17: 0000000000000000 x16: 0000000000000000
[ 283.372143] x15: 0000000000000000 x14: 0000000000000000
[ 283.372614] x13: 0000000000000000 x12: 0000000000000000
[ 283.373085] x11: 0000000000000000 x10: 0000000000000000
[ 283.373555] x9 : 0000000000000000 x8 : 0000000000000000
[ 283.374027] x7 : 000000000000003f x6 : ffff0000e0cd5600
[ 283.374498] x5 : 0000000000000305 x4 : 0000000000000000
[ 283.374970] x3 : 0000000000000001 x2 : 0000000000000001
[ 283.375440] x1 : 0000000000000000 x0 : 0000000000000000
[ 283.375912] Call trace:
[ 283.376137] fsnotify_destroy_marks+0x1f4/0x420
[ 283.376540] fsnotify_find_mark+0x1c/0xa4
[ 283.376899] dnotify_flush+0x58/0x180
[ 283.377229] filp_close+0x50/0x90
[ 283.377528] __close_fd+0x24/0x40
[ 283.377826] __arm64_sys_close+0x24/0x60
[ 283.378178] el0_svc_common.constprop.0+0x6c/0x170
[ 283.378605] do_el0_svc+0x24/0x90
[ 283.378905] el0_sync_handler+0x90/0x19c
[ 283.379256] el0_sync+0x158/0x180
[ 283.379559] Code: 88037c82 35ffff83 17fffaba f9800271 (885ffe60)
[ 283.380100] ---[ end trace 051f29ebb0bb4ed4 ]---
[ 330.448063] kauditd_printk_skb: 9 callbacks suppressed
Violación de segmento
|
|
|
|
| Wifi very slow on PBP Manjaro? |
|
Posted by: WeaseleyRon - 01-21-2021, 05:40 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
 |
My pbp is 1 month old running default Manjaro it came with.
I am able to connect to wifi but I am only gettting 0.33, and up to 1,5 Mbits/s. On the same connection my phone get 12+ Mbits/s.
What are some tips for me to debug this? I'm not even sure how to do the proper updates.
So far I've done all the updates in the software center, in whatever the UI system is on Manjaro (separate question: what is the UI/GUI called on Manjaro), and ran pamac update && paman upgrade and this did some stuff.
|
|
|
|
| Pinebook Pro has become dead, no lights? |
|
Posted by: JohnKarpenter - 01-21-2021, 05:37 AM - Forum: General
- Replies (3)
|
 |
Hi people
I've had a PBP working successfully for a month or so. But now it's dead.
It's sat in an inmoving position, connected to the mains with the barrel charger which I switch on from time to time to top up the battery. It's mostly used for flashing to my pinephone so it's not been used heavily, I also have tried a few OS's so it has been booting from multiple SD cards and the emmc (from original Manjaro) successfully.
Yesterday I flashed opensuse to the emmc (booted and rebooted a few times) and decided it wasn't for me so I flashed Manjaro again but after I tried to reboot it crashed so I had to force shutdown with 10s hold on power button. After that it failed to start up (no lights on front but charger is lit red when plugged in).
After leaving it for an hour or so it started, but after a reboot it went back to dead. And next day that's how it still is.
As it's not been moving it's unlikely to be a loose cable inside so I hesitate to take the back cover off.
Are there any known issues that may help me? Could repeated plugging of mains/SD/USB cause this?VidMate Mobdro
|
|
|
|
|