DillonM
-
Content Count
23 -
Joined
-
Last visited
-
Days Won
2
Posts posted by DillonM
-
-
So is it a hardware compatibility or software issue? Is this likely to be resolved in a newer build at some point?
-
Can anyone show me where the NFC chip is located? I am having trouble getting my yubikey to read in LOS 20.
thanks
🤓
-
stopped fighting to get stock android and went to Lineage 20. completed the entire install on the first attempt within 20 minutes.
-
3
-
-
same error on the different computer. now i need to figure out my next step
-
Side note: during the extraction of the newly downloaded tar.gz files, I kept getting an error with the vmlinux file. maybe just my download or the computer so I will try both option on the other machine I am moving to test next
-
1
-
-
Update: tried with 2.1.5 version found in the GDrive share and received the same error.
I have been using a Surface 7 pro as my installation computer with a USB 2.0 hub attached to connect the phone. I am curious if the USB 3.0 port is still causing the issue despite the fact that a hub is attached. Going to switch to a different windows box to test this theory.
-
1
-
-
ya but at least i can say that i am trying to resolve the issue. and i get practice in flashing and restoring.
-
2
-
-
well i found an older backup of the release_sm6115_s701_gms_v2.1.2 that I had downloaded last year and it had the missing xml files but the error was the same.
-
1
-
-
Update: I am looking back over the PDF and the files and realize that i am missing the patch0.xml file.
I will now try and determine why it's missing and how to find and get it back
-
1
-
-
Trying to flash my Pro1-x back to stock from SFOS.
I am hitting an error "
ERROR: function: sahara_rx_data:276 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main: 982 Sahara protocol error
ERROR: function: main:320 Uploading: image using Sahara protocol failed
"
I am not sure what my next steps are at all, so any assistance will be greatly appreciated.
-
1
-
-
Sad to say but I am going to have to switch over to lineage or stock. After too many missed calls or unreceived texts from my SO, i am being request to fix the situation. and to not have to explain why the phone is worth a step down from my old note 20 ultra, i need the pro1-x to be more reliable (probably less bleeding edge) for a daily driver.
-
Ya I am trying to figure out another option for receiving MMS and RCS. My current thought is to use Waydroid and then something like Signal (I know they no long support SMS/MMS but just an example). But I am curious if there has been any work on getting the Android UI resolution to not appear as stretched when using the keyboard? And will any notifications from an android app pass through to the SFOS notifications?
-
Been using this as my daily driver for about 2 weeks now and the biggest complaint I have is that all my MMS messages from both android and ios users do not come through. (any suggestions)
There are times that I lose all network connectivity and I have to reboot but that has only been 1 or 2 times a day.-
1
-
-
13 minutes ago, epninety said:
OK, maybe it's not the same problem, wierd coincidence though.
For me, looks like some issue with SailJail. I edited /usr/share/applications/harbour-sailhn.desktop and inserted
Sandboxing=Disabled
into the [X-Sailjail] section and that now works normally when started from the icon. Not an ideal solution of course.
The same fix didn't work for the browser on the first launch, though it did for subsequent launches.
hmm ya too bad that work around didn't resolve it.
Thanks for the suggestion. What would you try next to troubleshoot? Seems weird that the Jolla store will install and load but not the browser.
Actually when I ping google in terminal, It appears to be resolving via IPv6. That makes sense to me why I might not be able to resolve other sites but I am not sure how to proceed.
-
10 minutes ago, DillonM said:
Ya that is exactly what I am seeing. Let me try launching from terminal and see if that is a good work around.
Nope. Launching from terminal does not resolve my issue. hmmm
-
10 minutes ago, epninety said:
@DillonM I might have the same issue (original Pro1 SFOS 4.4.0.64). Sometime in the last week, some of my apps cannot connect to the internet via wifi or cellular. Weather seems to be working again, but the browser and hackernews don't connect.
Your post reminded me to investigate further. I notice both work fine when started from the terminal, e.g. sailfish-browser, or harbour-sailhn.
Not sure what's different, but it's a workaround at least.
Ya that is exactly what I am seeing. Let me try launching from terminal and see if that is a good work around.
-
Any suggestions on where to start troubleshooting a networking issue where the Jolla store will load and install apps and some apps will load data but it is limited. For example, the built in weather app appears to update when I look for a new city but the browser will not connect to any page. This is happening on both Wifi and Data. However, I am also starting to doubt my T-Mobile service is working even though it shows all the network info because when I go to reconnect to a new SSID the 'sim' option for Internet is shown in white and not blue (which I am learning is the indicator of an active service in SFOS).
Thanks ahead of time.
-
1
-
-
On 10/24/2022 at 11:33 AM, DillonM said:
A somewhat novice question here: after running the initial 'sudo edl ....' command, the output stops at "main - device detected :)" . How long should this process take? Is there a way to monitor before I have to hard reboot my pro1x?
I can still see the device in lsusb so I am just not sure. And I see an 'edl' process running in 'ps' or 'top'
Just nervous about flashing a different OS without backing up my persist partition and this seems to be my roadblock on this process.
so i think my initial problem was that the 'adb reboot edl' command was not taking the device into a 'full' edl mode. when I used the key combo to enter, my command advanced past the 'device detected' phase, only to stop again at 'trying to read the first storage sector'.
How long should that process take?
-
1
-
-
How long should each of these processes take? My device gets to "firehose - Trying to read first storage sector..." and then just sits there.
-
2
-
-
A somewhat novice question here: after running the initial 'sudo edl ....' command, the output stops at "main - device detected :)" . How long should this process take? Is there a way to monitor before I have to hard reboot my pro1x?
I can still see the device in lsusb so I am just not sure. And I see an 'edl' process running in 'ps' or 'top'
Just nervous about flashing a different OS without backing up my persist partition and this seems to be my roadblock on this process.
-
agree that these are all question I want to have answered as well
-
so I scrolled through the responses from the IGG project owner (FX Technology) and pulled them out into a txt doc to review. it seems like most the responses are just copy/paste of each other but they did confirm that 622 will allow for external display. What I am not getting is the repeated statement that the 622 is better because it is just newer. All that means to me is that the EOL is futher out so hopefully support for the drivers will continue for a longer time period, not that it is better. is there anything that is an advantage other than longer support life?
-
1
-
Pro1X, Nfc only working for some tag-types
in Support
Posted
ya improving mobile connectivity is probably a higher need than troubleshooting a single brand's nfc non-reading.