Please look at when those apps received their last update! LLs Video Player was last updated in 2021 (five years ago), Jollagram was last updated in 2015 (eleven years ago!), and I can’t even find ‘YouTube Downloader’ anywhere so it must be so old that it was never even updated for newer devices’ architecture.
Fernschreiber received an update recently (literally just two days ago), but before that it hadn’t been updated since 2023. However, I don’t know why it doesn’t work on your device. It seems to work for everyone else.
You can also copy the URL in the Browser by just tapping it and then (re)selecting it with a long-press, the way you select and copy text anywhere else.
the long press copy doesnt seem to work, long press url bar works sometimes, but as i said, my constructive view is this is not obvious to new users, it would be good to inform about it someway. Its just as bad as the pull down to refresh that was added to other mobile web browsers years ago (refresh icon hidden by default), or how all web and app developers chose to use three dots and three bars drop down menu, tiny and hidden away on pages, and in unison too as if it was industry standard. When i returned to using tech from a hiatus of a few years these features had been adopted en masse and its just counter intuitive ui design imo. Incidentally,Even this forum has the three bars which speaks of their prevalence. What is wrong with ‘Menu’ /off topic
Depends on what you want it to do. If you want to watch YouTube videos, have a look at some of the most recently updated apps on Storeman/OpenRepos (note that the search function frustratingly doesn’t show them in chronological order, you’ll need to check the dates yourself), there’s quite a few that offer YouTube playback. Microtube is one I know is kept up to date. From the same trusted developer you could get Pico Player (as an all-round video player) and Yottagram (a Telegram client). Another Telegram client you could look at is YAST Client, a brand new app created by a different trusted developer.
Another alternative for watching videos is File Browser, which should be able to play just about anything. Or just the Gallery app should also work, as long as your videos are in the default paths (that get indexed).
You make a good point about the functionality being hidden, and not being explained. Sailfish has a ‘hint’ system, which you’ve most likely already seen, so there’s no reason why a hint couldn’t be added about copying a URL, and selecting/copying text in general. I think I’ll create a topic later about things that should be added to the tutorial or as hints in the OS, because new users should be able to find out how they work without having to poke around or read forum threads first.
Microtube has no ‘Install’ option in storeman, on this device.
Also, I tried the YAST. It exhbits the same behaviour as Fern. I enter the phone number and it notifies confirmation sent. The weird thing I dont understand is, YAST reads: ‘We’ve sent the code to the telegram app on the other device’. What other device? The number i entered is linked to the simcard inside the XZ2 on which YAST is installed.
Its been many years since i setup telegram on the iphone I want to ditch. IIRC I just used the phone number inside the iphone and the confirm msg was texted to me, isn’t this howit works@???
Regarding Microtube, I just looked and there are three versions for the different device architectures, so it should be possible to install it, but Storeman can glitch out sometimes. Could you try closing Storeman, opening the Terminal app and running the following command?
pkcon refresh
Afterwards, open Storeman and look for Microtube again. If it still doesn’t let you install, try installing it from the terminal with this command:
pkcon install microtube
If that doesn’t work either, it should at least give a clear error message telling you why it isn’t working.
Regarding Telegram, I think Telegram’s default behaviour is that if you ever set up an account in the past and didn’t explicitly delete that account, it sends a confirmation code to that client instead of an SMS (and often doesn’t offer SMS as a fallback), and I don’t know if there’s a way around that. So basically you should be able to get the code from the client on the iPhone. You’re not the first one to run into that problem, but it’s Telegram making things more annoying than they should be.
the refresh worked , it installed via storeman but upon attempt play video i get no formats available error. likely linked to yt-dlp i assume. but i dl’d all the yt-dlp from chum, relying on it to install approroiate version.
a bit off topic.
odd that telegram stuff. Its extreme but I’d rather not ‘link’ the iphone to the sailfish. I managed to run telegram on java virtual machine with an android image, but i cant recall how that worked as the pc i ran it on did not have sim card slot. i’ll do a bit more research on this. thanks for the assistance.
I shall investigate why utube wont play videos.
edit: come to think of it , perhaps telegram doesn’t use the tel no, to send code, nor does it require that the sim assoc. with tel no. input is live in the device. prob just used tel numbers as a way to harvest data. doesn’t actually serve a purpose via SMS in the usual sense (for example logon verify on websites).
If I remember correctly, Telegram is complaining these days that some countries have too high SMS rates or that a lot of spam accounts are being created from that country. The official app asks for a “donation” (they call it a Telegram Premium trial) of 1$/1€/equivalent to send a verification code when registering a new device.
You should be able get around this by either transferring the old installation to the new device, or trying to register the device again and again until Telegram relents, and is willing to send the code for free, either as a Telegram message or SMS.
So as i said few posts post ago, the ghost input on the xz2 is a huge deal breaker. The thing is, it works fine when the device is plugged into a power source, so, from this it can be seen that the fault is something to do with surplus / lack of charge reaching the digitiser when on battery alone.
An idea - Is it possible to electrically isolate the finger print sensor on the phone by altering high level / kernel areas of the phone? I only suggest this sensor because it isnt used. Open to suggestions or ideas (especially from anyone with electrical background). Isolating sensors might redirect more evenly distribute charge.
someone had success with another xperia (later model) by ensuring adaptive brightness is enabled but i can confirm this does not solve it on xz2 compact.
It’s two months on now since using it and it’s fixed. Not one freeze not one ghost touch. I’m baffled at why but I have a theory that the brightness being set to adaptive makes sure the touchscreen has enough power but not to over power the screen which makes the electricity to disperse in irregular patterns. Which can cause the screen to freeze and cause ghost touches as the screen isn’t getting enough power or that area is getting too much and cannot differentiate between actual touch and surges of power in that area.
@shorterxp Assuming you were expecting my reply here regarding touchscreen firmware. I am not much into this subject as my phone worked fine when I got it. So, I just followed docs at that time, updated Sony android to whatever version it was then, and moved to Sony AOSP to start porting. xz2c is a bit weird, but its mainly loosing touch once in a while and power off/on of the screen restores it. never looked further into it.
please avoid PMs - just ping again publicly. I am mostly ignoring PMs these days as it makes no sense to start replying to all one-by-one. even today got a question regarding 5.1 tama update - that’s after writing in one of tama’s threads reply to that.
after xz2 was released, on various forums the ‘sensitivity’ issue was discussed. users reported a software update via sony pc companion fixed it.
to summarise ;
” My phone uses Cleartouch. The sensitivity issue is fixed in 51.1.A.4.265. The touch driver seems to be updated. In the “firmware info” page, the “fw rev” is now 0x05.02 ”
” TD4353jdi touch controller firmware was updated from 05.01 to 05.02 in 51.1.A.4.265”
Some users report units shipped with “rev2” and “rev3” on box didn’t have problem.
I’m not even sure if the ghost issue im experiencing today is the same as that discussed in these threads… therefor i want to check firmware on this compact.
however , the usual way to check is to input ## xxx ## on the phone dialler on stock android - but SFOS does not have this feature.
to re-iterate, it’s unclear if the correct firmware is in the sony image used for xz2c port by @rinigus. its an assumption seeing as the firmware was supposedly ‘updated’ ~2018.
it could be that the phone has to be patched prior to flash of SFOS and xperia blob!
i believe any info would help future users of this small phone and advance the sailfish cause in general.
Is it possible that the android version on the phone was too old. i recall the phone booting into android v9 when it was shipped with v10, as a consequence of the flash problems described among my first posts in this thread.
we are using sony released AOSP blobs that are flashed on top of sony released android (the one you have when you get the device). SFOS part is based on AOSP. so, my guess is probably as good as yours. not much firmware is in SFOS part
If anyone knowledgeable could chime in about how the android and blob interact that would be big help. i’m starting to suspect the flash of v12 (xperia blob) over v9 (android ver.) as opposed to v10 as recommended in the jolla guide may have upset things.
i’m gonna revert back to android, update via pc companion than re flash SFos, in order to see what firmware revision is present. its a pity sfos does not offer the “service menu” as seen in android.