liquidvx

This was a tough choice but I finally listed my Pro1 X for sale. It's a great phone with awesome keyboard but where I live only iPhone seems to work 😞 https://www.ebay.com/itm/195525497377

I've revisited this thread multiple times in hopes of finding a solution for Tmobile. I love my pro1-x keyboard, but i'm about to give up on this device because i cannot make phone calls. server not found, and cellular service drops entirely If a call connects, the audio drops out on both sides, i cant hear them or they can't hear me. i cannot even check my voicemail because the service can't hear my complete pin number Does anyone have experience with getting the phone to work with Tmobile in California?

@matf-kabouik i confirmed it is the pro1x image thanks @tschakram. I thought that would work but I get the same result. Droidian logo appears, pulses briefly then dims slightly and disappears. I'm running these commands. ╭╴╴╴liquidvx@UX482:~/Downloads/droidian/droidian-OFFICIAL-phosh-phone-fxtec_pro1x-api30-arm64-24_20220804 ╰╴$ fastboot format:ext4 userdata Warning: userdata type is raw, but ext4 was requested for formatting. mke2fs 1.46.2 (28-Feb-2021) Creating filesystem with 59072979 4k blocks and 14770176 inodes Filesystem UUID: 102e9c78-666e-4084-8ba7-6ed2902f2a66 Superbloc

@steeb $ ./flash_all.sh I: Waiting for a suitable device I: Flashing data/boot.img Sending 'boot_a' (34328 KB) OKAY [ 1.318s] Writing 'boot_a' OKAY [ 0.173s] Finished. Total time: 1.528s Sending 'boot_b' (34328 KB) OKAY [ 1.262s] Writing 'boot_b' OKAY [ 0.132s] Finished. Total time: 1.419s I: Flashing data/dtbo.img Sending 'dtbo_a' (119 KB) OKAY [ 0.013s] Writing 'dtbo_a' OKAY [ 0.002s] Finished. Total time: 0.02

@matf-kabouik I followed the 1-step instruction here and flashing went off without a hitch. But when the device rebooted it showed the Droidian logo and then went black. Can you offer any tips for getting Droidian running on Pro1X?

yep, same. is there a step missing?

Ditto. After a couple days my Pro1X with SailfishOS seemed to cause wifi problems and yesterday I had to reboot the router twice. Turned off the device last night and haven't had network problems since. The issue I'm experiencing reminded me of the Google home/Chromecast bug that was killing wifi by sending bursts (< 100k) of MDNS multicast discovery packets when the device exits sleep The linked article also mentions "phone" so maybe mobile devices could contain the firmware bug but hard to believe since it was like 5 years ago. If it is the same bug then it would expla

I'm having this same problem with Android, Ubuntu Touch and Sailfish so I doubt its a software issue. If the call actually does connect and the other side can hear me, I have about 10 seconds to say my piece before the network and call drops.

@tschakram thank you, your instructions got me further than any other. I am stuck on: $ fastboot format:ext4 userdata Warning: userdata type is f2fs, but ext4 was requested for formatting. mke2fs 1.45.5 (07-Jan-2020) Warning: RAID stripe-width 1 not an even multiple of stride 2. /tmp/TemporaryFile-sPSRJM: Unimplemented ext2 library function while setting up superblock /usr/lib/android-sdk/platform-tools/mke2fs failed with status 1 mke2fs failed: 1 error: Cannot generate image for userdata and $ fastboot reboot fastboot fastboot: usage: unknown reboot target fastboot then