S3 Installer: Now looking for beta testers ...
-
Oh well turns out it went faster as expected... Now looking for beta testers for the installer...
-
@flohack
Hi, I have a S3 neo lying around here for many years. I'd really like to test the ubports installer. -
Same here it's just collecting dust right now so I'm in
-
Well its already real, you can install now with the UBports Installer found here: https://github.com/ubports/ubports-installer/releases
Enjoy
-
Successfully Installed Samsung III Neo without any problems besides my impatience in the end. (tried to reboot before the installation process was finished - that's why i needed to flash a second time. maybe a little remark in the installer like - don't switch off your phone until ... - might be helpful for ignorant people like me)
After the rather annoying pinephone experience i am now again a happy user of a functioning (and especially: affordable) ut device.
thx to the porter! -
Hi, tried the installer but the device reboots to Samsung splash screen.
Let me know which info I can provide you.
I can access adb shell while the device is stuck at the splash screen: if i run "uname -r" it returns the name of the ROM I had previously installed (even if I wiped the system in theory). So it's safe to say it did not install ubuntu...?
-
@owlbrick How can you run uname -r, how did you connect to the device?
-
@flohack The phone reboots to system after install, but hangs on samsung spash screen. I can connect to adb shell and run uname -r, but as it shows cyanogenmod (the ROM I had previously installed) I get that installation was not successful.
Could you point me to manual installation guide? If running it manually doesn't solve the problem we can rule out the installer.
I looked at https://pad.ubports.com/p/samsung-s3neo-alphatesting, but there seems to be a nextcloud link which is now empty (also someone translated it in spanish, but previous versions are accessible).
-
@owlbrick The installer works, and no, its not easy to install UT manually. You have to convert, resize partition images, mount images into images or unpack image files into a partition ^^
Thats why we have the installer. You can send me a log though, the installer creates a new one every time when you start it, so let it run through once, and then send me this. Somehwere in cache folder ^^
-
@Flohack Ok, I did some research... I had data and cache partitions formatted as f2fs while ubuntu needs ext4. Fixing this made possible to install Ubuntu Touch. Maybe it could be useful to say it in the installer!
Now I have another problem: phone is stuck at loading screen with the five flashing dots. How can I debug this?
-
@owlbrick Oh thats interesting, another user reported the same. It might be because of our devel channel is getting updates for Qt 5.12 - I will try to find out
-
Hi guys, yes, update 80 seems to break UI. I am looking into removing that faulty one
-
Unfortunately update cannot be easily removed, but we found the problem and are working on a fix....
-
Fix is committed. Now comes the fun part: You need to reinstall
- Boot to recovery with Vol-Up plus Power, until you see the recovery screen. From there take the installer. You can uncheck "Bootstrap" to make install a bit faster, and you MUST uncheck "Wipe userdata" obviously Good Luck!
-
@flohack Wow that was quick! It worked!
BTW I have something to report with the installer. After starting the installation with the phone in recovery, the phone rebooted to recovery again while the installer was downloading Ubuntu. After this, the installer got stuck on the "Preparing system image" screen. As I noticed that my machine didn't recognize any new device connected, I unplugged and replugged the phone (this time my machine recognized the device connected) and the installer immediatly started sending the image and correctly completing the installation.
-
@owlbrick Humm yes S3 Neo needs an unplug/plug event to see new host
I will update the popups -
I don't know whether to post it here. Sent SMS are not displayed correctly anymore. One can only see the top line and the bottom line of the "green" message. I can still read any one liner. But as soon as the message gets longer, there is no chance of deciphering it. Meaning that I have to remember, what I wrote. Works for 2 minutes. After that I forgot what I wrote and the guessing begins.
-
@vartojas
Hi, I had this issue some time ago but I think it has been fixed (at least on Nexus5).
A workaround is to copy the message to the clipboard and paste it where you can read it (I did it in the typing area for a new message).
To copy, swipe the SMS to the left then tap on the "stack of paper"... -
@applee thx for the workaround. now that you mentioned it. i remember, that the nexus5 has shown the same problem before.
the thing is (to say it in denglish), that the messages were displayed not long ago correctly. the problem must have caused by some update after #80. -
@vartojas has been fixed with update 94 or 95...
