Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,451
» Latest member: librem.d.s
» Forum threads: 16,190
» Forum posts: 116,847
Full Statistics
|
Latest Threads |
Upgrading Armbian from v2...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
Today, 06:53 AM
» Replies: 1
» Views: 686
|
PulseAudio dropouts after...
Forum: Linux on Pinebook Pro
Last Post: P. Siera
Today, 03:03 AM
» Replies: 3
» Views: 158
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: P. Siera
Today, 03:02 AM
» Replies: 6
» Views: 301
|
Hello from Ukraine
Forum: P64-LTS / SOPINE Projects, Ideas and Tutorials
Last Post: Dendrocalamus64
Yesterday, 07:13 PM
» Replies: 1
» Views: 41
|
Simple Outdoor Weather St...
Forum: General Discussion on PineTab
Last Post: aria22
Yesterday, 12:47 PM
» Replies: 0
» Views: 44
|
Armbian fix, current vers...
Forum: Linux on Pinebook Pro
Last Post: Sb2024
Yesterday, 08:49 AM
» Replies: 0
» Views: 45
|
Experimental Mobian kerne...
Forum: PinePhone Pro Software
Last Post: teekay
Yesterday, 05:39 AM
» Replies: 2
» Views: 140
|
Pinephone Pro not in stor...
Forum: General Discussion on PinePhone
Last Post: P. Siera
Yesterday, 02:12 AM
» Replies: 1
» Views: 200
|
Libre Office on Pinetab2?
Forum: General Discussion on PineTab
Last Post: Kevin Kofler
08-07-2025, 09:50 PM
» Replies: 1
» Views: 75
|
Won't boot with a MicroSD...
Forum: General Discussion on PineTab
Last Post: acruhl
08-07-2025, 06:59 PM
» Replies: 0
» Views: 35
|
|
|
Just feeling kind of frustrated tbh |
Posted by: ImmyChan - 07-27-2022, 03:26 AM - Forum: General
- Replies (1)
|
 |
A few months (or maybe even more than a year ago now) my PineTab broke itself, possibly the battery swelled and destroyed the screen, I’m not sure. But there’s nothing I could do about that since there aren’t PineTab replacement parts available.
A member of Pine64 did reach out to me offering a replacement PineTab as well as some other stuff to review on my YouTube channel, which was much appreciated but sadly that never went anywhere and I never got much word as to whether it was still going ahead or not.
I get that the Pine64 team are busy but I can’t help but feel frustrated since I’m left with not much word as to what’s going on and a PineTab that I can’t use (which is a shame because I love the PineTab)
|
|
|
Battery Management |
Posted by: jsch - 07-26-2022, 01:33 PM - Forum: Mobian on PinePhone
- Replies (4)
|
 |
Is there something like a battery management for the PinePhone?
If you plug in the usb charger, the battery level will raise up to 100% (as expected).
Would it increase the lifespan of the battery if battery level would be kept in a reasonable range (e.g. between 60% and 70%)?
Would it increase the lifespan of the battery if charging is not with full power (1.5A) if not needed?
|
|
|
Shipping Updates |
Posted by: curtisg - 07-26-2022, 12:26 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
I placed my order last week, and I haven't gotten any sort of tracking info yet?
Does anyone on here know about their shipping habits, I paid for express, but I haven't heard back from anyone?
|
|
|
New Pinephone for sale, Beta w Convergence Package |
Posted by: megst - 07-26-2022, 11:40 AM - Forum: General Discussion on PinePhone
- No Replies
|
 |
Have had this Pinephone (32 GB flash, 3 GB system memory) Beta with Convergence package for a few weeks. Decided to return within 15 day return period as I need a phone with a smaller form factor. Just checking to see if anyone wants to buy it first. Have made no changes to software and OS that came with it. Put in a SIM card and it works. Sent a few texts and made a few calls. Could not get my headphones to work with the headphone jack. Please PM me with questions. I can send photos. Reply by July 31st, as it will be shipped back then.
|
|
|
Battery problem with a Pinephone keyboard and Mobian |
Posted by: elode - 07-26-2022, 06:25 AM - Forum: Mobian on PinePhone
- Replies (2)
|
 |
Hello,
I have a Pinophone equipped with the Pinephone keyboard (operating system: Mobian).
As indicated in the instructions, to recharge the Pinephone, I plug the usb cable from the charger into the usb input on the keyboard.
Until a recent update, with Mobian, once the battery was charged, the charge indicator showed 200%. It seemed a little strange to me, but considering that with the keyboard battery, the device has two batteries (keyboard battery + Pinephone battery), there is a logic to the matter… and there was no problem. My Pinephone had a battery life of about two days.
But since a recent update, things have changed:
I can still charge the Pinephone by plugging the usb cable into the keyboard input, but it seems that mobian no longer detects the keyboard battery.
After charging for a whole night, the charge indicator in mobian only shows 65% maximum. Also the keyboard battery doesn't seem to charge the Pinephone battery
Result: the autonomy of my pinephone went down to about ten hours!
Does anyone have a clue to help me?
Thanks
|
|
|
Rrkisp issue with CSI camera input. |
Posted by: Randomuser - 07-26-2022, 03:22 AM - Forum: Linux on Quartz64
- No Replies
|
 |
I'm using kernel 4.19 from the repo shared by Shaggy013 user with some modifications in the imx219 camera driver to support extra modes. I have backported the dts from latest RC kernel so mostly everything is working (hw encoding etc.) However the picture I'm getting doesn't look right(very dark, when camera gain is raised it looks very green - other colors are present so it is not un-debayered, but there is an excess of green). It may be simply because I'm getting a raw unprocessed picture, or there is some problem. At the same time I have the following errors. Are those errors perhaps related? Maybe ISP is not doing some image processing? (or perhaps I haven't requested it yet). Either way please let me know what those errors mean if anyone knows.
Additionally I get those errors in dmesg:
[ 0.886617] imx219 3-0010: driver version: 00.01.02
[ 0.911298] imx219 3-0010: Model ID 0x0219, Lot ID 0x4c2015, Chip ID 0x066e
[ 0.912483] iommu: Adding device fdfe0000.rkcif to group 7
[ 0.912540] rkcifhw fdfe0000.rkcif: Linked as a consumer to fdfe0800.iommu
[ 0.913203] rkcifhw fdfe0000.rkcif: can't request region for resource [mem 0xfdfe0000-0xfdfe7fff]
[ 0.915928] iommu: Adding device fdff0000.rkisp to group 8
[ 0.915984] rkisp_hw fdff0000.rkisp: Linked as a consumer to fdff1a00.iommu
[ 0.916183] rkisp_hw fdff0000.rkisp: is_thunderboot: 0
[ 0.916216] rkisp_hw fdff0000.rkisp: max input:0x0@0fps
[ 0.916259] rkisp_hw fdff0000.rkisp: can't request region for resource [mem 0xfdff0000-0xfdffffff]
[ 0.917220] rkisp rkisp-vir0: rkisp driver version: v01.07.00
[ 0.917639] rkisp rkisp-vir0: Entity type for entity rkisp-isp-subdev was not initialized!
[ 0.917681] rkisp rkisp-vir0: Entity type for entity rkisp-csi-subdev was not initialized!
[ 0.919844] rockchip-csi2-dphy csi2-dphy1: dphy1 matches m01_f_imx219 3-0010:bus type 4
[ 0.920677] rkisp-vir0: Async subdev notifier completed
Looking at the dtsi that has those devices(it is included from rk3568.dtsi - I know rk3568 is a different device, but the include statement is the same as in mainline so I assume those dts entries are common to rk3566 and rk3568, but mainline of course doesn't support rkisp etc yet so I'm using rk3568.dtsi from the BSP) it says:
(scroll to see the whole thing)
Code: rkisp: rkisp@fdff0000 {
compatible = "rockchip,rk3568-rkisp";
reg = <0x0 0xfdff0000 0x0 0x10000>;
interrupts = <GIC_SPI 57 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 58 IRQ_TYPE_LEVEL_HIGH>,
<GIC_SPI 60 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "mipi_irq", "mi_irq", "isp_irq";
clocks = <&cru ACLK_ISP>, <&cru HCLK_ISP>, <&cru CLK_ISP>;
clock-names = "aclk_isp", "hclk_isp", "clk_isp";
resets = <&cru SRST_ISP>, <&cru SRST_H_ISP>;
reset-names = "isp", "isp-h";
rockchip,grf = <&grf>;
power-domains = <&power RK3568_PD_VI>;
iommus = <&rkisp_mmu>;
rockchip,iq-feature = /bits/ 64 <0x3FBFFFE67FF>;
status = "disabled";
};
rkisp_mmu: iommu@fdff1a00 {
compatible = "rockchip,iommu-v2";
reg = <0x0 0xfdff1a00 0x0 0x100>;
interrupts = <GIC_SPI 59 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "isp_mmu";
clocks = <&cru ACLK_ISP>, <&cru HCLK_ISP>;
clock-names = "aclk", "iface";
power-domains = <&power RK3568_PD_VI>;
#iommu-cells = <0>;
rockchip,disable-mmu-reset;
status = "disabled";
};
and for the cif:
(scroll to see the whole thing)
Code: rkcif: rkcif@fdfe0000 {
compatible = "rockchip,rk3568-cif";
reg = <0x0 0xfdfe0000 0x0 0x8000>;
reg-names = "cif_regs";
interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "cif-intr";
clocks = <&cru ACLK_VICAP>, <&cru HCLK_VICAP>,
<&cru DCLK_VICAP>, <&cru ICLK_VICAP_G>;
clock-names = "aclk_cif", "hclk_cif",
"dclk_cif", "iclk_cif_g";
resets = <&cru SRST_A_VICAP>, <&cru SRST_H_VICAP>,
<&cru SRST_D_VICAP>, <&cru SRST_P_VICAP>,
<&cru SRST_I_VICAP>;
reset-names = "rst_cif_a", "rst_cif_h",
"rst_cif_d", "rst_cif_p",
"rst_cif_i";
assigned-clocks = <&cru DCLK_VICAP>;
assigned-clock-rates = <300000000>;
power-domains = <&power RK3568_PD_VI>;
rockchip,grf = <&grf>;
iommus = <&rkcif_mmu>;
status = "disabled";
};
rkcif_mmu: iommu@fdfe0800 {
compatible = "rockchip,iommu-v2";
reg = <0x0 0xfdfe0800 0x0 0x100>;
interrupts = <GIC_SPI 146 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "cif_mmu";
clocks = <&cru ACLK_VICAP>, <&cru HCLK_VICAP>;
clock-names = "aclk", "iface";
power-domains = <&power RK3568_PD_VI>;
rockchip,disable-mmu-reset;
#iommu-cells = <0>;
status = "disabled";
};
Also I have no other devices occupying those memory regions. I checked in /proc/ here is the excerpt:
Code: fdeb0000-fdeb0fff : rk_rga@fdeb0000
fded0480-fded04bf : iommu@fded0480
fdee0800-fdee083f : iommu@fdee0800
fdef0800-fdef08ff : iommu@fdef0800
fdf40f00-fdf40f3f : iommu@fdf40f00
fdf40f40-fdf40f7f : iommu@fdf40f00
fdf80800-fdf8083f : iommu@fdf80800
fdf80840-fdf8087f : iommu@fdf80800
fdfe0800-fdfe08ff : iommu@fdfe0800
fdff1a00-fdff1aff : iommu@fdff1a00
fe010000-fe01ffff : ethernet@fe010000
So before I try using rkisp programmatically I would like to find out if I'm having some problem with it?
|
|
|
PBP (PPP) docking deck : no hdmi sound |
Posted by: Rosbeefandino - 07-24-2022, 06:19 PM - Forum: Pinebook Pro Hardware and Accessories
- No Replies
|
 |
Hi all,
I'm using my PBPDD with My PPP.and is working as all know.
the thing i didn't see on all bugs commented is that i can not select audio out toplay sound thrue the HDMI inteface.
As i saw the IT6564 spec the chip should accept the output sound on hdmi.
Is the hardware is connected or driver exists ? should it works ?
I don't know anything on making driver then if you have any idea and knowledge your help is welcome.
|
|
|
RK3566 Memory map |
Posted by: Gridley - 07-24-2022, 04:34 PM - Forum: General Discussion on Quartz64
- Replies (2)
|
 |
I can nowhere find any info regarding the location of the RK3566's memory mapped registers. The Rockchip data sheet contains much about the SoC's electrical specification, but, so far as I can see, nothing about programming the peripherals, or even the address at which main memory is to be found.
Any ideas?
|
|
|
PinePhone Pro Motherboard with sim card holder |
Posted by: tckosvic - 07-24-2022, 11:01 AM - Forum: PinePhone Pro Hardware
- Replies (1)
|
 |
I have yet to receive any response from pinephone on my request for the replacement sim/sd card holder for PPP. Sent pictures as requested per their instructions. Not even an acknowledgement after 2 months. No one else has acknowledged ever receiving one in my related thread.
It looks like I will have to replace whole motherboard to get a replacement sim/sd card but the only item in PPP parts store is a mb for the keyboard not the phone and some screws.
Anyone with info as to availability (now or future) of PPP mb replacements? I hope the sim/sd card holder is included on the mb. For the PP, it does seem to be included as seen in that parts store.
thanks, tom kosvic
|
|
|
|