[Halium9-GSI] - Oneplus 3(T)
@kkeijzer said in [Halium9-GSI] - Oneplus 3(T):
@ernest Where can I find this watchdog script you made? The PinePhone is suffering from similar problems that I have been trying to solve for a while, and (parts of) it might be useful there as well.
I'm looking for a ratio between two output of ofono : battery_props_changed vs ril_netreg_get_signal_strength .
If there is too much battery_props_changed, I force ofonod and telepathy-ofono to restart.
I notice two issues and i've difficulty to assess if there are linked or not : ofonod doesn't mind that it is loosing the cell tower information ... Thus signaling to the stack above that everything is fine. I suspect an issue between rild and ofonod, however on H9, I didn't success to generate ril log
Then the other issue, is that somethime the dbus id of ofono is not updated then telepathy-ofono and the apps are lost (impossible to close a call even if the call is already finish).
I didn't yet create a repo however this is the script https://paste.ubuntu.com/p/KHS5DMNw3y/
I need to assess if that is still valid or not in V10 in arm64 (V9 is armhf).
Ps : you need to have ofonod started in debug mod : exec ofonod -ddd -P provision,udev*,dun*,smart*,hfp_bluez5,stktest,sap
@ernest A lot seems familiar. On the PinePhone the signal indicator always seems to work, but occasionally the modem just doesn't. So calls and texts don't come in and mobile data doesn't work any more.
When I then try a dbus call like
dbus-send --print-reply --system --dest=org.ofono /quectelqmi_0 org.ofono.Modem.SetProperty string:"Powered" variant:boolean:false, attempting to restart the modem, it will time out. So clearly something in oFono is stuck. (Normally that query should disable the modem and
variant:boolean:trueshould power it up again.)
The cleanest way to fix it is
sudo service ofono restart(better than
pkill -9 ofonodI'd say), after which mobile data starts working again. But then I run into the problem that the dialer app will show "No signal", and outgoing calls being impossible, with the logs printing something like:
error: "org.freedesktop.DBus.Error.NameHasNoOwner" message: "Could not get owner of name 'org.freedesktop.Telepathy.Connection.ofono.ofono.connection_640ce7767735c59d6fbc2542a9a06c68': no such name"
The fix for that is running
pkill telepathy-ofono(there doesn't seem to be a service to restart, and I'm not sure how this is spawned) with some sleep timers I'm still working on, but that also seems similar to what you're doing. It looks like you're sleeping 20 seconds after killing
ofonod, probably to give it time to re-initialize, but upstart would only give an exit code when
ofonodis back up. But still you'd probably need some time inbetween that way, because my experience is that killing
telepathy-ofonoright after upstart reports oFono as restarted won't work.
My problem only is that I'm still looking for a way to do a non-destructive API call to figure out whether oFono is locked up or not. I can't look at RIL logs because there is no RIL on the PinePhone.
On the PinePhone, sometimes the technology preference option disappears, and the
org.ofono.RadioSettings.GetPropertiescall would return "operation already in progress", which is a trigger for me. But sometimes the modem also locks up without this happening, so it's not ideal.
/usr/share/ofono/scripts/get-serving-cell-infocould be useful for you. You could check if this stops fluctuating and have your counter look at that?
Very interesting, it seems really similar what your are experiencing....
I've played a lot with busctl to try to extract a proper bus call response/property without much success, using the ofonod script was ending with a timeout response or very long response that was not acceptable for a watchdog.
I tried to switch on and off the modem through the ofono script and the results was not the expected one.
It seems that ofonod doesn't or dbus update it's id then telepathy is lost. I'll try to stop the service in a cleaner way, thanks.
Looking in sailfish ofonod github and forum, I didn't find a similar issue. Moreover OP3 with Halium7.1 doesn't present this bug.
I started using v10 without modifications a week ago, most things are working fine and many rootfs issues was fixed with switching to android9 branches. Once a day I need to reboot phone due cellular network, opening camera is causing system crash, dash charging and tri-state switch probably don't work.
@danqo6 which phone do you have a 3 or a 3T ?
On the 3T the phone switch off when taking a picture...can find any relevant log so far
Look in my gdrive i've dropped a file fixing dash, phone cell and switch
@ernest hi, how did the testing go? any major issues?
It seems way smoother, I've upload a fix for the GSI V10. However on the OP3T, taking a picture shutdown the phone ....
So far I've no clue as the logs doesn't seems talkative and also I'm wondering if this issue is only for the 3T.
I'm looking for help on this bug.
Hmm, this seems interesting. If you say "way smoother", that is also compared to the normal Halium7 port?
What about the bottom edge display? Does it have this partially desktop mode like on the Halium7 port as well, where many apps show the bottom edge as a button (like on convergent desktop) and thus break the layout of the app?
Way smoother than halium 7.1.
Bottom edge is normal, but I would like that to be configurable, I liked that button. Bottom arrow in some apps is moved a bit up, not sure why
I mean H7 (arm64) less smoother than GSI V9 (armhf) less smoother than GSI V10 (arm64).
(I've worked on the H7 port up to May this year... and didn't performed test with an up to date phone)
Really sad, that they changed between V9 and V10 the camera back-end management, that make the android layer crashing hard
I see. that sounds promising. is the camera thing something that could be fixed, or does it require a major rewrite?
I confirming that it's the OP3T camera creating issues.
I just tried it on a OP3, no issue with the camera and so far I didn't noticed issue with the phone except :
- The power menu doesn't switch off the phone,
- Some boot there is a race condition affecting the wifi and telephony.
I've updated my patch for the OP3 version 1.4
The phone feels really smooth.
For the OP3T camera, I presume significant amount and competencies are required to fix this issue, likely beyond mine.
For instance, we are not the only one with OP3T camera issue : https://forum.xda-developers.com/oneplus-3t/themes/mod-camera-hdr-fix-t3742366
Hello everyone, sorry for being a little off-topic and posting on an old thread:
I tried installing droidian on my treblized Oneplus 3 using Halium9 & GSI. However most things (wifi, torch, camera, screen brightness control etc) weren't working. Since these work with the ubuntu touch GSI how difficult would it be to make droidian work on that? And how would I go about doing that?
On ubuntu touch: Are new updated GSIs going to happen? Are there any plans for that? Or is it too much work? I thought with GSIs you only need one for every phone and halium takes care of the rest?
@saligari Sadly the OP3/3T in general, not only the GSI experiment has not seem much specific improvements since I originally switch to using UT on it about 1.5 years ago. The non-GSI version works reasonably with some quirks, but I think it is safe to assume that development isn't happening