Welcome, Guest |
You have to register before you can post on our site.
|
Forum Statistics |
» Members: 29,426
» Latest member: mugur
» Forum threads: 16,178
» Forum posts: 116,809
Full Statistics
|
Latest Threads |
Page turner for PineNote ...
Forum: PineNote Software
Last Post: Haroldkent
2 hours ago
» Replies: 1
» Views: 496
|
Request for CAD files of ...
Forum: General Discussion on PineNote
Last Post: Szybet
Yesterday, 11:22 AM
» Replies: 1
» Views: 896
|
? Introducing RoutineHero...
Forum: General Discussion on PineTime
Last Post: tllim
Yesterday, 01:13 AM
» Replies: 1
» Views: 108
|
Movuan distribution for P...
Forum: PinePhone Software
Last Post: merom
07-27-2025, 05:01 PM
» Replies: 5
» Views: 1,109
|
booting is looping
Forum: PineNote Software
Last Post: jabi27
07-27-2025, 01:36 AM
» Replies: 2
» Views: 87
|
Can’t login to Linux
Forum: Linux on Pinebook Pro
Last Post: fnosai
07-27-2025, 12:30 AM
» Replies: 0
» Views: 120
|
* /lib64 is a symbolic li...
Forum: PineNote Software
Last Post: jabi27
07-26-2025, 10:01 PM
» Replies: 2
» Views: 76
|
Invalid Signature by m-we...
Forum: PineNote Software
Last Post: Francus
07-25-2025, 05:26 AM
» Replies: 0
» Views: 77
|
Pinetab2 not starting
Forum: PineTab Hardware
Last Post: biketool
07-25-2025, 03:04 AM
» Replies: 12
» Views: 6,657
|
invalid signatures
Forum: Getting Started
Last Post: Dendrocalamus64
07-24-2025, 08:35 PM
» Replies: 2
» Views: 246
|
|
|
Troubleshooting and Understanding MMS |
Posted by: epiii2 - 05-31-2022, 07:44 PM - Forum: General Discussion on PinePhone
- Replies (74)
|
 |
I'm trying to figure out what my options might be for handling incoming MMS messages, with the understanding that they're not really supported by most software at the moment but there are some workarounds in use (like jmms for example). When I try out some test messages I can see the encoded data arrive via SMS and I can extract it to a file, but I'm stuck trying to make use of it because it doesn't seem to be formatted like other examples I see online. Does anyone have any experience they can share?
For example, here's what I see for a few MMS messages I sent myself the other day:
Code: $ mmcli --messaging-list-sms -m 4
/org/freedesktop/ModemManager1/SMS/2 (received)
/org/freedesktop/ModemManager1/SMS/1 (received)
$ mmcli --messaging-list-sms -m 4 -s 2
----------------------------
General | path: /org/freedesktop/ModemManager1/SMS/2
----------------------------
Content | number: XXXXXXXXXX
| data: 000603BEAF848C82983046303633443133454142373030303032413630303030313031008D908A808E0278008805810306977F83687474703A2F2F36332E35352E312E38372F736572766C6574732F6D6D733F6D6573736167652D69643D00891680XXXXXXXXXXXXXXXXXXXX2F545950453D504C4D4E00
----------------------------
Properties | pdu type: cdma-deliver
| state: received
| teleservice id: wap
(Just with the sender and receiver number Xd out.) And I can also dump that data chunk to a file like so and get the binary for that hexadecimal glob:
Code: mmcli -m 4 -s 2 --create-file-with-data message.sms
...but in any case the contents of the binary don't seem formatted the way tools like jmms expect. For example doing a hexdump on another test message:
Code: 00000000 00 06 03 be af 84 8c 82 98 30 35 30 36 33 44 35 |.........05063D5|
00000010 37 42 45 35 33 30 30 30 30 37 34 35 30 30 30 30 |7BE5300007450000|
00000020 31 30 31 00 8d 90 8a 80 8e 02 78 00 88 05 81 03 |101.......x.....|
00000030 06 97 7f 83 68 74 74 70 3a 2f 2f 36 39 2e 37 38 |....http://69.78|
00000040 2e 38 38 2e 31 30 32 2f 73 65 72 76 6c 65 74 73 |.88.102/servlets|
00000050 2f 6d 6d 73 3f 6d 65 73 73 61 67 65 2d 69 64 3d |/mms?message-id=|
00000060 00 89 16 80 XX XX XX XX XX XX XX XX XX XX 2f 54 |....XXXXXXXXXX/T|
00000070 59 50 45 3d 50 4c 4d 4e 00 |YPE=PLMN.|
00000079
So... what is this weird format? The main thing I see is that URL pointing to a Verizon server where I can hypothetically get the contents of the MMS (I think?) but I don't know what these other mostly-binary chunks are, aside from the sender's phone number and /TYPE=PLMN. The Verizon server never seems to respond to me no matter what I send (via wwan0, too, as I've read about elsewhere) but maybe I don't know what I'm supposed to give for the message ID. Any tips?
|
|
|
PPKB with phone; phone dies while charging |
Posted by: SwordfishII - 05-31-2022, 06:47 PM - Forum: PinePhone Hardware
- Replies (1)
|
 |
Hoping someone can help me out.
Running Arch, on my pinephone in the keyboard case. The keyboard case works fine, even got the top row symbols working.
I did megi's echo 1500000 > /sys/class/power_supply/axp20x-usb/input_current_limit
Problem is after using it, I plug it into a charger and the next morning the phone is dead. I have tried 5 different chargers including dumb 2.4a. This has occurred on every distro I have tried (all of them except manjaro).
Any ideas?
Edit: I should add that when not on ac power the keyboard charges the phone just fine, so it doesn't seems to be the pogo pins
|
|
|
Instructions to change the IMEI |
Posted by: kwdevel - 05-31-2022, 12:54 PM - Forum: PinePhone Hardware
- No Replies
|
 |
The other thread was closed before I had a chance to respond, so I'm just going to leave this here instead.
This works on the PinePhone Pro (Explorer). I have not tested on other devices. This works on the Quectel EG25-G modem.
FYI, I'm using Mobian, so you have to stop the modem-manager first or it will cause a conflict with minicom (terminal suddenly stops responding).
This feature is NOT documented in the PDF from Quectel, but it still works.
In a console:
Code: systemctl stop ModemManager.service
Now you can run minicom without it hanging.
Code: minicom -b 115200 -D /dev/ttyUSB2
Inside minicom, to get your current IMEI:
Code: AT+CGSN
860195057712345
To change your IMEI:
Code: AT+EGMR=1,7,"860195057754321"
OK
You can confirm it changed by running:
Code: AT+CGSN
860195057754321
That's it.
|
|
|
My Pine doesn't allow me to install to eMMC on different OS's |
Posted by: Kimberley van Buyten - 05-31-2022, 07:31 AM - Forum: General Discussion on PinePhone
- Replies (1)
|
 |
Tried several different ways to install Sailfish. But no matter how I try, when writing to eMMC memory it seems that nothing happens and then I get all kinds of errors: - ls: cannot access 'mmcblk2': No such file or directory
- Error: The location 256MB is outside of the device /home/adm1n/Downloads/mmcblk2.
- Error: The location 256MB is outside of the device /home/adm1n/Downloads/mmcblk2.
- Error: The location 6250MB is outside of the device /home/adm1n/Downloads/mmcblk2.
- The file mmcblk2 does not exist and no size was specified.
- mke2fs 1.46.2 (28-Feb-2021)
- The file mmcblk2 does not exist and no size was specified.
- mke2fs 1.46.2 (28-Feb-2021)
- The file mmcblk2 does not exist and no size was specified.
- mount: /home/adm1n/Downloads/root: special device mmcblk2 does not exist.
- mount: /home/adm1n/Downloads/boot: special device mmcblk2 does not exist.
Is it that I don't have the correct permissions? Which I would find strange, because I have really tried all kinds of ways. I used external terminal, I used Jumpdrive and I used terminal from the phone himself. Whatever I do, at the question Which SD card do you want to flash? nothing seems to work anymore
Could it be that I have a Pine 1.0? Have no idea what the differences are between 1.0 and 1.1.
What also struck me is that when I install Manjaro, for example, I cannot install 1 app from the store. For example 'Signal':
First the easy way, install Manjaro, configure it and go to Discover and search for Signal. Once clicked on it, immediately the first error:
signal-desktop;5.43.0-1;aarch64;community: could not find or read package
I ignore that and I press the install button and after a few seconds I get the next error:
Package download failed
There must be something wrong with the writing or things like that. Or do I miss something? Could I hard reset my Pine?
|
|
|
Update the PinePhone keyboard driver to support missing characters? |
Posted by: Peter Gamma - 05-31-2022, 02:35 AM - Forum: PinePhone Accessories
- Replies (8)
|
 |
The goal is to run LibreOffice in Posh on the PinePhone. It can be run by typing:
OOO_FORCE_DESKTOP=gnome-wayland libreoffice
into to terminal. The GUI cannot be started, the LibreOffice installation prevents the start.
I have the PinePhone keyboard connected to the PinePhone, which works also for the terminal. I tried to type:
OOO_FORCE_DESKTOP=gnome-wayland libreoffice
Unfortunately, I cannot print a «_» with the PinePhone keyboard. The characters are on the PinePhone keyboard, but neither control, Fn, Alt, AltG nor the special Pine key works to get the characters to be printed in the terminal.
How can I modify the PinePhone keyboard driver to support the missing characters?
|
|
|
baloo_file |
Posted by: Emilio - 05-31-2022, 12:59 AM - Forum: PinePhone Pro Software
- No Replies
|
 |
After installing the last Dev image on a SD and after entering the PIN this is the error I get. Does sny body know what does this file do? After closing the window, the normal desktop appears on the screen and I can keep on going but cannot understand the error and it's conscuences
We are sorry,baloo_file closed unexpectedly
You cannot report this error, because baloo_file does not provide a bug reporting address
Details:
Executable:baloo_file PID:3,810 Signal:Aborted(6)
Time:5/31/22 8:47 AM
Baloo is the file indexing and file search framework for KDE Plasma, with a focus on providing a very small memory footprint along with with extremely fast searching.
|
|
|
RockPro64 has no white led, nor will it boot past... |
Posted by: AnjinMeili - 05-30-2022, 05:38 PM - Forum: General Discussion on ROCKPRO64
- Replies (2)
|
 |
I have tried endless OS images, on both SD cards and eMMC, and am simply frustrated.
When I fire up a Debian buster image, it boots to the installer, gets all the way to the end, and then... Dies when it attempt to boot into the os for the first time.
The Armbian and ayufan images get to 'Flattened Device Tree blob at 01f00000' and 'Booting using the fat blob at 0x1f00000' and hangs.
There is no white LED at all as well.
Seems so strange as it grinds though so much doing the installer for Debian Bullseye.
Hoping this is just my own stupidity, and I am missing something obvious.
Thanks for the advice and guidance.
Cheers
Anjin
|
|
|
Mute function on calls? |
Posted by: scrwbigtek - 05-30-2022, 12:52 PM - Forum: General Discussion on PinePhone
- No Replies
|
 |
Hello All,
Will try again here.
Do any of the Pinephone releases have the mute mic function working?
If not any idea when?
So far I have tried Manjaro Posh. and KDE with no luck. I am off to Mobian next
Really did not have to run down the entire list of every release.
I see various release charts with features that work or do not work in various places.
Is there one official go to place for this with status listed?
I also saw "we have Pulse Audio to thank for this".
Are there any known verified workarounds?
thanks!
sbt
Update (well Mobian did not go well, not trying that again, almost bricked my phone).
|
|
|
Second USB3 port as OTG |
Posted by: softsr - 05-30-2022, 07:29 AM - Forum: General Discussion on ROCKPRO64
- Replies (1)
|
 |
Hello everyone!
According Wiki the USB3 Port on RockPro64 could be used as an OTG port.
I'm using Type C port for OTG device pretty succesfully, however there is a demand on having two OTG Ports simultaneously.
Till now I've managed to switch USB3 port into OTG mode with editing device tree over dtedit command where following string was set from "host" to "otg":
Code: usb1 {
compatible = "rockchip,rk3399-dwc3";
clocks = <0x8 0x82 0x8 0x84 0x8 0xf7 0x8 0xf9>;
clock-names = "ref_clk", "suspend_clk", "bus_clk", "grf_clk";
power-domains = <0x15 0x18>;
resets = <0x8 0x126>;
reset-names = "usb3-otg";
#address-cells = <0x2>;
#size-cells = <0x2>;
ranges;
status = "okay";
phandle = <0xf1>;
dwc3@fe900000 {
compatible = "snps,dwc3";
reg = <0x0 0xfe900000 0x0 0x100000>;
interrupts = <0x0 0x6e 0x4 0x0>;
dr_mode = "otg";
phys = <0x2b 0x2c>;
phy-names = "usb2-phy", "usb3-phy";
phy_type = "utmi_wide";
snps,dis_enblslpm_quirk;
snps,dis-u2-freeclk-exists-quirk;
snps,dis_u2_susphy_quirk;
snps,dis-del-phy-power-chg-quirk;
snps,tx-ipgap-linecheck-dis-quirk;
snps,xhci-slow-suspend-quirk;
snps,xhci-trb-ent-quirk;
snps,usb3-warm-reset-on-resume-quirk;
status = "okay";
phandle = <0xf2>;
};
};
After that I can see the second device under /sys/class/udc:
Code: rock64@rockpro64:~$ ls /sys/class/udc
fe800000.dwc3 fe900000.dwc3
However the second USB3 device (fe900000.dwc) doesn't work same as Type C port, no device appears there at all (I'm setting it as a mass storage).
So my question is:
is it generally a good idea to use two USB3 ports as OTG devices simultaneously?
If so, what could lack in setting it up?
|
|
|
|