| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 28,147
» Latest member: SamCoffee
» Forum threads: 15,694
» Forum posts: 114,605
Full Statistics
|
|
|
| Phonebook does not link with calls |
|
Posted by: canaac - 02-07-2021, 01:49 PM - Forum: Mobian on PinePhone
- Replies (3)
|
 |
Hi all,
Well, that's basically it. When I select a contact from the phonebook and click to call, it doesn't call, I think because the phonebook is not related to the calling application.
Someone else happens? How is it solved?
Thank you.
|
|
|
|
| Keypad not working during call |
|
Posted by: Zebulon Walton - 02-07-2021, 10:30 AM - Forum: Mobian on PinePhone
- Replies (4)
|
 |
Today I noticed that the keypad no longer seems to be working during a call for accessing automated menu systems. It was previously working.
Since the last time I tried that feature probably at least a week ago, I've done a few updates via apt-get dist-upgrade. Also today I decided to take the plunge and update the modem firmware. So everything in the phone is at the current patch level.
Anyone else here notice this feature stopped working for them recently? Any fixes?
|
|
|
|
| Green power LED not working |
|
Posted by: Zebulon Walton - 02-07-2021, 07:26 AM - Forum: PinePhone Hardware
- Replies (9)
|
|
The green power LED on my Pinephone has stopped working though the phone works normally otherwise. It's been a while since I had this thing apart - are the LEDs integrated into the mainboard? I'm wondering if it could be a loose connection, but if soldered to the mainboard I assume the LED just went bad. It's only a minor nuisance since everything else seems to work OK, aside from the vibrator which I'd posted about previously.
No power light, no vibrator... maybe the battery will last a wee bit longer. 
|
|
|
|
| Anbox: install Google Services |
|
Posted by: sonic - 02-07-2021, 04:45 AM - Forum: PinePhone Software
- No Replies
|
|
Hey there,
I am pmOS (Phosh) user and I am trying to get Google Services into my Anbox images.
First I tried to install OpenGApps. I manually extracted the anbox image from /usr/share/anbox/android.img, installed gsfcore-all, gsflogin-all, gmscore-arm64 and vending-arm from ARM64/7.1 pico variant of OpenGApps and then packed it back (you can look here [1], [2] or [3] to get some idea how to do it). It works, partially. I can see the Play Store in app list and start it. But the anbox crashes every time after about one minute - does not matter what I run, F-Droid, Play Store, or just settings.
So next time I tried to microG project. There is some info on this forum here. Unfortunately, after this patch the anbox does not run at all. My personal guess is that services.jar are for x86.
Have anyone of you had better luck with these?
[1] https://gitlab.com/postmarketOS/pmaports...e/APKBUILD
[2] https://github.com/geeks-r-us/anbox-play...aystore.sh
[3] https://aur.archlinux.org/cgit/aur.git/t...mage-gapps
|
|
|
|
| Zwave module not loaded |
|
Posted by: caragk - 02-07-2021, 02:55 AM - Forum: Linux on Pine A64(+)
- No Replies
|
|
Hi !
I recently had to reinstall my Pine64's DietPie (raspbian mod). I use this SBC as home automation (formerly Jeedom, trying now Hass.io) with the Pine64 Zwave GPIO module.
Before this module was well recognised with Jeedom. But after reinstall (and DietPie upgrade) it isn't anymore. I first thought about a problem in HassIO's Zwave integration but it isn't. I mean /dev/ttyS2 don't link to the module :
Code: # dmesg | grep -i tty
[ 0.000000] Kernel command line: root=UUID=45e3e951-caf9-4aa6-909d-ceb24242c91e rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 consoleblank=0 loglevel=4 ubootpart=1dd8dfdc-01 usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u
[ 0.000460] printk: console [tty1] enabled
[ 2.036068] printk: console [ttyS0] disabled
[ 2.036157] 1c28000.serial: ttyS0 at MMIO 0x1c28000 (irq = 38, base_baud = 1500000) is a 16550A
[ 2.049344] printk: console [ttyS0] enabled
[ 2.050667] 1c28400.serial: ttyS1 at MMIO 0x1c28400 (irq = 39, base_baud = 1500000) is a 16550A
[ 2.050812] serial serial0: tty port ttyS1 registered
[ 6.022066] systemd[1]: Created slice system-getty.slice.
[ 7.861583] usb 2-1: FTDI USB Serial Device converter now attached to ttyUSB0
[ 7.866494] usb 4-1: FTDI USB Serial Device converter now attached to ttyUSB1
Here is my lsmod and my kernel version :
Code: # uname -srv
Linux 5.10.12-sunxi64 #21.02.1 SMP Wed Feb 3 20:42:58 CET 2021
# lsmod
Module Size Used by
xt_conntrack 16384 1
xt_MASQUERADE 20480 1
nf_conntrack_netlink 49152 0
xfrm_user 40960 1
xfrm_algo 16384 1 xfrm_user
nft_counter 16384 15
xt_addrtype 16384 2
nft_compat 20480 4
nft_chain_nat 16384 4
nf_nat 40960 2 nft_chain_nat,xt_MASQUERADE
nf_conntrack 135168 4 xt_conntrack,nf_nat,nf_conntrack_netlink,xt_MASQUERADE
nf_defrag_ipv6 24576 1 nf_conntrack
nf_defrag_ipv4 16384 1 nf_conntrack
nf_tables 176128 45 nft_compat,nft_counter,nft_chain_nat
nfnetlink 16384 4 nft_compat,nf_conntrack_netlink,nf_tables
br_netfilter 28672 0
bridge 233472 1 br_netfilter
aufs 229376 0
overlay 114688 0
sunxi_cedrus 36864 0
ftdi_sio 61440 2
snd_soc_hdmi_codec 20480 1
usbserial 45056 5 ftdi_sio
videobuf2_dma_contig 24576 1 sunxi_cedrus
axp20x_battery 16384 0
axp20x_ac_power 16384 0
v4l2_mem2mem 36864 1 sunxi_cedrus
sun4i_gpadc_iio 24576 0
axp20x_adc 20480 0
lima 57344 0
videobuf2_memops 20480 1 videobuf2_dma_contig
videobuf2_v4l2 24576 2 sunxi_cedrus,v4l2_mem2mem
industrialio 65536 4 axp20x_battery,sun4i_gpadc_iio,axp20x_ac_power,axp20x_adc
gpu_sched 32768 1 lima
videobuf2_common 49152 3 sunxi_cedrus,videobuf2_v4l2,v4l2_mem2mem
sun4i_i2s 24576 4
dw_hdmi_cec 16384 0
dw_hdmi_i2s_audio 16384 0
videodev 241664 4 sunxi_cedrus,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
snd_soc_simple_card 24576 0
mc 49152 5 sunxi_cedrus,videodev,videobuf2_v4l2,videobuf2_common,v4l2_mem2mem
sun8i_ce 28672 0
snd_soc_simple_card_utils 24576 1 snd_soc_simple_card
display_connector 20480 0
crypto_engine 20480 1 sun8i_ce
cpufreq_dt 20480 0
realtek 24576 1
pinctrl_axp209 16384 0
dwmac_sun8i 28672 0
mdio_mux 16384 1 dwmac_sun8i
i2c_mv64xxx 24576 0
I found some threads (like this one but also for others dist or SBC) about I2C, SPI, UART and hdi_uart (Bluetooth) so I've tested to add any of those kernel modules without any success...
My kernel I2C config :
Code: # cat /proc/config.gz | gunzip | grep -i i2c
CONFIG_NFC_FDP_I2C=m
CONFIG_NFC_PN544_I2C=m
CONFIG_NFC_PN533_I2C=m
CONFIG_NFC_MICROREAD_I2C=m
CONFIG_NFC_MRVL_I2C=m
CONFIG_NFC_ST21NFCA_I2C=m
CONFIG_NFC_ST_NCI_I2C=m
CONFIG_NFC_NXP_NCI_I2C=m
CONFIG_NFC_S3FWRN5_I2C=m
CONFIG_REGMAP_I2C=y
# CONFIG_SENSORS_LIS3_I2C is not set
CONFIG_NET_DSA_MICROCHIP_KSZ9477_I2C=m
# CONFIG_NET_DSA_SMSC_LAN9303_I2C is not set
# CONFIG_MOUSE_ELAN_I2C is not set
# CONFIG_MOUSE_SYNAPTICS_I2C is not set
CONFIG_TOUCHSCREEN_AD7879_I2C=m
CONFIG_TOUCHSCREEN_AR1021_I2C=m
# CONFIG_TOUCHSCREEN_WACOM_I2C is not set
# CONFIG_TOUCHSCREEN_WDT87XX_I2C is not set
# CONFIG_TOUCHSCREEN_SIS_I2C is not set
CONFIG_RMI4_I2C=m
CONFIG_SERIAL_SC16IS7XX_I2C=y
CONFIG_TCG_TIS_I2C_ATMEL=m
CONFIG_TCG_TIS_I2C_INFINEON=m
CONFIG_TCG_TIS_I2C_NUVOTON=m
CONFIG_TCG_TIS_ST33ZP24_I2C=m
# I2C support
CONFIG_I2C=y
CONFIG_I2C_BOARDINFO=y
CONFIG_I2C_COMPAT=y
CONFIG_I2C_CHARDEV=y
CONFIG_I2C_MUX=y
# Multiplexer I2C Chip support
CONFIG_I2C_ARB_GPIO_CHALLENGE=m
CONFIG_I2C_MUX_GPIO=m
CONFIG_I2C_MUX_GPMUX=m
CONFIG_I2C_MUX_LTC4306=m
CONFIG_I2C_MUX_PCA9541=m
CONFIG_I2C_MUX_PCA954x=m
CONFIG_I2C_MUX_PINCTRL=m
CONFIG_I2C_MUX_REG=m
CONFIG_I2C_DEMUX_PINCTRL=m
CONFIG_I2C_MUX_MLXCPLD=m
# end of Multiplexer I2C Chip support
CONFIG_I2C_HELPER_AUTO=y
CONFIG_I2C_SMBUS=m
CONFIG_I2C_ALGOBIT=y
CONFIG_I2C_ALGOPCA=m
# I2C Hardware Bus support
# I2C system bus drivers (mostly embedded / system-on-chip)
CONFIG_I2C_CADENCE=m
CONFIG_I2C_CBUS_GPIO=m
CONFIG_I2C_DESIGNWARE_CORE=y
# CONFIG_I2C_DESIGNWARE_SLAVE is not set
CONFIG_I2C_DESIGNWARE_PLATFORM=y
CONFIG_I2C_EMEV2=m
CONFIG_I2C_GPIO=m
# CONFIG_I2C_GPIO_FAULT_INJECTOR is not set
CONFIG_I2C_MV64XXX=m
CONFIG_I2C_NOMADIK=m
CONFIG_I2C_OCORES=m
CONFIG_I2C_PCA_PLATFORM=m
CONFIG_I2C_RK3X=m
CONFIG_I2C_SIMTEC=m
CONFIG_I2C_XILINX=m
# External I2C/SMBus adapter drivers
CONFIG_I2C_DIOLAN_U2C=m
CONFIG_I2C_ROBOTFUZZ_OSIF=m
CONFIG_I2C_TAOS_EVM=m
CONFIG_I2C_TINY_USB=m
# Other I2C/SMBus bus drivers
# end of I2C Hardware Bus support
CONFIG_I2C_STUB=m
CONFIG_I2C_SLAVE=y
CONFIG_I2C_SLAVE_EEPROM=m
# CONFIG_I2C_SLAVE_TESTUNIT is not set
# CONFIG_I2C_DEBUG_CORE is not set
# CONFIG_I2C_DEBUG_ALGO is not set
# CONFIG_I2C_DEBUG_BUS is not set
# end of I2C support
# I2C GPIO expanders
# end of I2C GPIO expanders
CONFIG_BATTERY_BQ27XXX_I2C=m
CONFIG_SENSORS_LTC2947_I2C=m
CONFIG_SENSORS_OCC_P8_I2C=m
CONFIG_MFD_AXP20X_I2C=y
CONFIG_MFD_MADERA_I2C=m
# CONFIG_MFD_DA9052_I2C is not set
# CONFIG_MFD_MC13XXX_I2C is not set
# CONFIG_HTC_I2CPLD is not set
# CONFIG_MFD_TPS65912_I2C is not set
# CONFIG_MFD_ARIZONA_I2C is not set
# CONFIG_MFD_WM831X_I2C is not set
# CONFIG_MFD_WM8350_I2C is not set
CONFIG_VIDEO_V4L2_I2C=y
# IR I2C driver auto-selected by 'Autoselect ancillary drivers'
CONFIG_VIDEO_IR_I2C=m
# audio, video and radio I2C drivers auto-selected by 'Autoselect ancillary drivers'
# SPI I2C drivers auto-selected by 'Autoselect ancillary drivers'
# I2C encoder or helper chips
CONFIG_DRM_I2C_CH7006=m
CONFIG_DRM_I2C_SIL164=m
# CONFIG_DRM_I2C_NXP_TDA998X is not set
CONFIG_DRM_I2C_NXP_TDA9950=m
# end of I2C encoder or helper chips
# CONFIG_DRM_I2C_ADV7511 is not set
CONFIG_SND_SOC_I2C_AND_SPI=y
# CONFIG_SND_SOC_ADAU1761_I2C is not set
CONFIG_SND_SOC_ADAU7118_I2C=m
# CONFIG_SND_SOC_CS42L51_I2C is not set
# CONFIG_SND_SOC_CS4271_I2C is not set
# CONFIG_SND_SOC_CS42XX8_I2C is not set
# CONFIG_SND_SOC_ES8328_I2C is not set
# CONFIG_SND_SOC_MAX98373_I2C is not set
CONFIG_SND_SOC_PCM1789_I2C=m
# CONFIG_SND_SOC_PCM179X_I2C is not set
CONFIG_SND_SOC_PCM186X_I2C=m
CONFIG_SND_SOC_PCM3060_I2C=m
# CONFIG_SND_SOC_PCM3168A_I2C is not set
# CONFIG_SND_SOC_PCM512x_I2C is not set
# CONFIG_SND_SOC_SSM2602_I2C is not set
# CONFIG_SND_SOC_TLV320AIC23_I2C is not set
CONFIG_SND_SOC_TLV320AIC32X4_I2C=m
# CONFIG_SND_SOC_WM8804_I2C is not set
# I2C HID support
CONFIG_I2C_HID=m
# end of I2C HID support
# I2C RTC drivers
CONFIG_RTC_I2C_AND_SPI=y
# SPI and I2C RTC drivers
# CONFIG_MOST_I2C is not set
CONFIG_ADXL345_I2C=m
CONFIG_ADXL372_I2C=m
CONFIG_BMA400_I2C=m
CONFIG_BMC150_ACCEL_I2C=m
CONFIG_IIO_ST_ACCEL_I2C_3AXIS=m
CONFIG_KXSD9_I2C=m
CONFIG_MMA7455_I2C=m
CONFIG_BME680_I2C=m
CONFIG_IIO_MS_SENSORS_I2C=m
CONFIG_IIO_ST_SENSORS_I2C=m
CONFIG_AD5696_I2C=m
CONFIG_BMG160_I2C=m
CONFIG_FXAS21002C_I2C=m
CONFIG_MPU3050_I2C=m
CONFIG_IIO_ST_GYRO_I2C_3AXIS=m
CONFIG_HTS221_I2C=m
# CONFIG_BMI160_I2C is not set
CONFIG_FXOS8700_I2C=m
# CONFIG_INV_ICM42600_I2C is not set
# CONFIG_INV_MPU6050_I2C is not set
CONFIG_ST_UVIS25_I2C=m
CONFIG_BMC150_MAGN_I2C=m
CONFIG_IIO_ST_MAGN_I2C_3AXIS=m
CONFIG_SENSORS_HMC5843_I2C=m
CONFIG_SENSORS_RM3100_I2C=m
CONFIG_BMP280_I2C=m
# CONFIG_MPL115_I2C is not set
CONFIG_VL53L0X_I2C=m
Code: # ls /sys/bus/i2c/devices/
i2c-0 i2c-1
As a n00b, I forgot to dd an image of the SDcard before erasing it (precisely I said f***k the moment I press Return)...
|
|
|
|
| PinePhone UBports Edition Success Stories? |
|
Posted by: K_Research - 02-06-2021, 04:46 PM - Forum: General Discussion on PinePhone
- Replies (1)
|
|
Looking for some PinePhone UBports Edition Success Stories are their any?
Looking to connect with PinePhone UBports Edition owners who have actually used their PinePhone UBports Edition to
1. Take pictures
2. Make phone calls
3. Send and receive text messages
Any other PinePhone UBports Edition success stories welcome, send receive email, web browsing etc.
Thanks in advance.
|
|
|
|
|
