Just updated the previous post. Somehow the SIM died.
Thanks for the answers. All that's missing now, is the firmware on my sons OPO....
Aaand one more update. Wifi works now - after reinstalling anbox (don't think it's related - probably the reboot). Still No SIM error which is really bad. Any way to go back to OTA6?
Update: I tried another SIM and that works. Somehow the SIM died just as I upgraded. It doesn't work in another phone either..
And for the record, I just reinstalled my own OPO (the other one is my sons), and lo and behold - both wifi and cell network are broken.
All I did was switch channels, and reinstall the anbox kernel. My sons OPO is using the normal kernel - anbox is not installed....
I have the same problem as mentioned here:
dmesg gives me request_firmware failed -2
Flohack suggested that the firmware might be missing, but how can I check that?
If it's missing, is there any way to install it without reinstalling an android rom?
Thanks in advance
I have both an OPO and a an MX4. I've been using the MX4 with 15.04 and it's been working with bluetooth and all.
For kicks, I tested the latest 16.04 dev on the OPO because of anbox. Pretty good, only problem is google play services, but that'll probably be solved.
Thing is though, that I use bluetooth a lot in my car, and the OPO doesn't work with bluetooth - at least not in my car. I thought - well I can just install 16.04 on the MX4, and with a couple of tricks, also make anbox run on that. That worked like a charm, but now bluetooth has stopped working on the MX4 too.
It behaves the same way as the OPO, so the problem is not something device/firmware specific.
Any tricks/tips or anything? I would hate to go back to 15.04 - especially now with 16.04 being better in many other ways....
Strangely enough, the other way around sorta works. The car can find the phone, and most things work. I can control the phone through the steering wheel, but sound doesn't work. It worked for a couple of seconds, then no sound. The bluetooth icon on the phone never changed to connected, even though it obviously was connected.
A little unrelated - my MX4 can power on after two days submerged in rice. There is still hope
Sigh - my MX4 just died because of rain, so I have to switch to my OPO.
Nice phone, but Bluetooth doesn't work, and I need that for my car, as I spend a lot of time in my car.
Any news on progress of Bluetooth or do I have to bite the Linage apple? Any other UBports-compatible phone where Bluetooth works?
@libremax Ok - thanks for clarifying that. I look forward to 16.04.
@Lakota - The Sim works in non-UBP/UT-phones. I also tried switching on/off aeroplane mode. Strangely enough, I can now recieve MMS's, but they're always from "Unknown number", which is a pita. This indicates that the problem is provider specific.
I'm sorry if my original post was too salty - it wasn't meant that way. I'm staying on UBP because I like it, but the way things are done (the show) tends to put focus on new functionality, rather than fixing bugs. Unfortunately I don't know how to code, so I just donate.
As for choosing one phone, I'd propose the OPO. Make that work flawlessly (or close). It's pretty capable, available and not too pricey.
I look forward to running on a OP3 or 5, but I'm afraid my MX4 won't last long.
Who can help me with SMS/MMS? I'll be happy to supply logs etc..
I've been a UT and UBP user since the E4.5 came out. I really like the gesture based control and a lot of other things, and I like this project to succeed. I also have a dislike in google and apple, which kind of limits my options
I use my phone as a daily driver, and currently I'm using the MX4. I also have a OPO where I've tried the different UBP versions.
But now my MX4 is starting to act strangely. When I wan't to use the phone app, it often hangs at "Initializing". It also loses network connectivity, but this seems to be a baseband/firmware thing. Time to start using another phone.................
My options are:
Soso hardware, and annoying baseband issues. Working bluetooth is good (and a must, since I have a long commute, where I use the phone alot for calling)
Good hardware, working radio, but bluetooth not working. I've created bugs on this, but nothing happens. No BT means no go.
I have one with a broken screen next to me. Battery life seems unacceptable, but maybe a new(er) one could help? Does it work with BT - anyone?
Too small, and BT is also flaky.
Same BT as E4.5?, but better size.
I can understand why the developers want to try all the new and fancy stuff, like libertine, anbox and so on. Since it's the developers that run the show, this seems to set the agenda.
You've probably heard this before, but how about choosing just one phone, and make sure that all (or most) of the kinks are sorted? Use some of the donated money to buy one for each of the key developers.
I still have problems using SMS and MMS is no go. I can live with that, but please fix bluetooth
Well "sudo reboot" works, but it prompts me for the password. I tried adding the job to sudo's crontab, but that doesn't work. The solution I described in post 1 works on a desktop ubuntu. After doing what I described, "sudo reboot" reboots the machine without prompting for password.
Too good to be true. After five days, it lost the connection again, and as usual it couldn't automatically reconnect. I looked at my script output, and I noticed that when there's no 4G connection, it doesn't run the cron job every five minutes. So somehow it's reversed - it's the baseband chip that keeps the phone awake. I'll try with just 3G - maybe that'll work.
How do I reboot my phone from the terminal, without having to type the password? I have a cron-job running to check connectivity, and I would like the script to able to boot the phone under certain circumstances. I tried adding: Cmnd_Alias SHUTDOWN_CMDS = /sbin/poweroff, /sbin/shutdown, /sbin/reboot & phablet ALL=(ALL) NOPASSWD: SHUTDOWN_CMDS with visudo after remounting / as rw, but it still prompts me. Any ideas?
I've been using UT since the Aquaris E4.5 came out. I really like the gesture based control, and whenever I have to use an android phone, it seems awkward and not intuitive.
I still have the E4.5 - my son uses it. I also got the MX4, which I'm using right now. Biggest problem is/was that it doesn't automatically reconnect when it loses coverage. This can be mitigated by waking it every 5 minutes (with cron), but otherwise it's a good phone. Battery life is not stellar though, and the cron job surely hasn't helped that either . The connection issue seems to be related to the baseband chip and not UT.
I also have a OPO, and it works pretty well. It doesn't lag the same way the MX4 does - even though it's slower. I can't use it as a daily driver though as bluetooth doesn't work, and that's a deal breaker for me, as I use 2-3 hours every day commuting.
I saw in another post, that this might get fixed soon, so I cross my fingers.
Anbox could be nice, but I only miss one android app (mobilepay - a danish money transfer app).
MMS doesn't work at all - and that's on all of the phones. This seems to depend on the operator, so I have no idea if it's ever gonna get fixed.
@wilfridd I have the same revision as you. However, I created a cron job running every 5 minutes. All it does is ping 184.108.40.206 once. This seems to "cure" the problem - maybe it prevents the phone from entering a deeper power save state. It didn't loose connection yesterday at all with the cron job running, which is unusual. If the problem comes back, I expect the ping will time-out, and I can use that to trigger a reboot. There may be better ways than ping to detect the lost connectivity. Some of the other scripts in /usr/share/ofono/scripts/ look interesting...