" I flashed ubuntu over the baseband of cm12.1. I thought that was what the advice was! "
Yes, I think that was the advice.
My cheap advice about mixing systems -> " dual booting is just not worth the trouble."
@21347 Hi, I deleted my former post because it was out of the topic.
Regarding your qmi.h issue it seems to come from hardware/qcom/wlan being a different version from fairphone's one. I am trying to get a successful build without resorting to copy-paste (apart from the binary bundle I download from code.fairphone.com) so I modified my .repo/manifests/default.xml to remove the default hardware/qcom/wlan line and replace it by the one you can find in the Fairphone Open Source release. It's still building (and will be for a while) but I am pretty sure I am past the part where it used to block !
If you want to pm me on FP's official forum so we can coordinate and avoid duplicating efforts, my handle is Arvil (with Batman on LSD as my Avatar )
EDIT : It actually goes forward until I reach an issue with hardware/qcom/audio-caf, I'm still figuring it out
EDIT 2 : I removed audio-caf from the manifest and...
#### make completed successfully (01:03:35 (hh:mm:ss)) ####
YESS ! Now I have to try it, I'll put the manifest in a git repo soon
If this happens to you, it's probably because the sever has gone out to lunch.
I recommend an email to:
asking for a restart.
has become unresponsive.
Please, restart. Thank you.
Took them less than 10 minutes : )
Not sure where this should go, I have made some comments on the launchpad bugs pages.
Basically I think loads of the trouble I'm having with apps not starting, crashing or hanging after the initial loading screen is related to https://bugs.launchpad.net/ubports-android/+bug/1625832, would make sense if the web apps use Browser as a base?
Not sure why uNav would hang but maybe what is crashing the Browser app is also causing calls to web services in other apps to silently fail?
Telegram 100% works, so not a connectivity issue.
Hello again and sorry for my long absence to the forum. I've had a hdd crash and my linux os (secondary on the laptop) disappeared, so I was unable to read any messages.
I didn't figured out any new steps to make Ubuntu Touch working on my Nexus 10. It looks like there is some part missing in all the tutorials . I will reanimate my Ubuntu biulding environment to come back to the topic and will share my progress.
@apple.muncy Thanks for the reply and for the bug tracker link
In that case, since development is active, any updates on the missing components like camera and GPS, being added to the "working" list? I don't want an ETA (I know better, I've modded enough phones in my time with ROMS from XDA, to know not to ask for ETA's ), I'm just excited at the progress this project has made and I want to install it on my OPO Currently though, no camera and GPS (which I rely on daily), are a deal breaker to me
I own one also but since I also have own newer Nexus devices I will focus on using them.
Given the age of the 2012 devices I can't imaging much reason to open any new development and any system images that you do find will without doubt be full of bugs.
In the end I managed to get it inot the bootloader manually, vol up + down then power on. I flashed the factory android 6 back on and then did a fresh install of rc-proposed.
there is still something wrong with it though as "adb reboot bootlader" does not work.
Its not finished unfortunately, its not daily by a good amount, There will be an update coming at as soon as Marius can, unfortunately some new bugs in unity 8/mir had pushed him back from the original release date a few weeks ago.