@MrT10001

the various options you suggest, dear helpers, will be tested, starting with a openSuse Slowroll image version 2024-11-17.
I'll need some time to come back and talk about it.
Thank you

@arubislander
@arubislander said " Could you boot up a live version of Ubuntu and see if your device is recognized in that? If so, then you know it has nothing to do with the OTA, but with an update on OpenSuse "

This is an option I'm considering after those explained above ....
So I need a little time to try out these options and I'll get back to you as soon as I can.

@stanwood
Yes, I just reinstalled “android-tools” to find adb and fastboot, but still need my pc to detect my phone and Ubuntu touch ....
it's an option I'll try after the one I mentioned to @MrT10001

@MrT10001
There has been no new kernel for at least 15 days.
I remind you that other devices (USB sticks, e/os and others are detected).
What I can do with opensuse Slowroll is go back to an earlier version with snapshot, to 2024-11-17 and see if it works on this.

@MrT10001
It's true that I haven't reinstalled adb and fastboot on this version of opensuse Slowroll that I've been using for 4 months ( experimental but quite accomplished, soft version of Tumbleweed ). I'm going to do it, but I don't see why it has anything to do with device detection ( adb fastboot necessary of course for reinstallation or whatever ), since it worked fine with rc ota-6 then ota-6 stable, the problem occurred after ota-7 stable.

@Keneda
Yes, however, the one I use every day is an original Oneplus cable.

@stanwood
It was well ticked.
So I unchecked it then restarted the phone, then checked MTP then restarted the phone, and unfortunately that didn't change anything.
Kind regards

@Keneda
It was well ticked.
So I unchecked it then restarted the phone, then checked MTP then restarted the phone, and unfortunately that didn't change anything.
Kind regards

@stanwood
It was well ticked.
So I unchecked it then restarted the phone, then checked MTP then restarted the phone, and unfortunately that didn't change anything.
Kind regards

Hello,

Since OTA-7, my Oneplus 5T is no longer recognized as a device when connected via USB cable to my PC, so it's no longer visible and I can't access the device from my computer.
Just the battery is only charged by the PC.
My operating system is openSuse, and e/os is recognized without any problem.
This is very annoying!
I introduce the subject on onePlus 5T for those who have the device and maybe the same problem.
Greetings

Oneplus 5T not detected by my pc ( Linux ) since ota-7

Hello,

Since OTA-7, my Oneplus 5T is no longer recognized as a device when connected via USB cable to my PC, so it's no longer visible and I can't access the device from my computer.
Just the battery is only charged by the PC.
My operating system is openSuse, and e/os is recognized without any problem.
This is very annoying!
I introduce the subject on onePlus 5T for those who have the device and maybe the same problem.
Greetings

An opinion from a UT user since 2016

At the time, I chose a phone pre-equipped with this operating system, developed at the time by Canonical, i.e. BQ Aquaris 5. I was very satisfied with this phone with UT.
It was almost entirely functional, and the translations were complete both in the settings and on the screen.
Of course, a number of technologies evolved, and we had to meet a certain demand for different services. This phone could no longer accommodate, for example, the banking services (which I still don't use) available via Waydroid.
But in anticipation of the evolution of technologies and also because the BQ Aquaris screen was cracked, I opted for a Oneplus 5T, seeing that, in the meantime, the community had taken up the torch from UT, and that for some time now, it had been doing a good job already visible on the BQ 5.
So I bought the oneplus 5T, and used it with 16.04 ota-24 and ota-25.
It was when the system was upgraded to 20.04 that things got complicated.
And here, I agree with @jojumaxx regarding his requests, which are not particularly mine, but in essence, for a user, who wishes to have a functional phone, on the basis of what was for a while a ranking by adaptability and functionalities of a phone model, it can be very confusing for someone who wishes to use the one he has chosen on this basis.
Of course, everyone will come with their bug reports, and their hopes that they'll be fixed as soon as possible.
And this is where, on such essential functionalities that belong to a cell phone, there are bugs that seem not to have been solved for years, as if, these are not as important as having the latest services accessible via Waydroid.
I have, of course, like many others, asked for certain problems linked to the use of my phone model to be resolved, such as audio failures after video recording, better translation (at least for certain international languages) of the phone, the flashing LED triggering after phone calls or sms, or messaging, and it's frustrating to note that - for the average user - of which I am, and who is not a developer, this seems to remain at a standstill, whereas we are at ota-5?
What conclusion can I draw from this, and it's only my opinion?
I'm waiting for ota-6, of course, to find out if any of these bugs have been resolved; I'd already be happy and feel that the request has been taken into account.
I'm not going to invest, as some people do, in several phones to find out which one suits me best, or to have the pleasure of blowing money for nothing when UT should be part of an ecosystem (since it's a phone, either second-hand, or part of a sustainable ethic); it's nonsense, as I've seen it written before, walk around with a UT, and eg. an Android, you can imagine the investment, which would reduce the thickness of my wallet but wouldn't be enough to carry 2 phones, and several phone numbers ... I rather feel that UT's original idea was to offer a sustainable, economical, privacy-conscious alternative. But it's true, one day it'll get tired and have to be changed before it's fully functional, and then, for a newer one, it'll be the same recipe all over again.
People will tell me that the system is in continuous development, which is fine, but even in the private sector, it's in continuous development, isn't it?
I think, of course, that there's a lot of good will in the development of UT, some interesting things that will be, in use, necessary, but also that many developers have their own specificities and interests in their work, of course, they often do it voluntarily, but it's an experience for them (business card), and UT brings together a bit of everyone who puts a bit of everything into it, and no longer concentrates on a requested base and perhaps not on the essentials of a UT smartphone, which for me would be what it should be and remain, first and foremost a system for devices, fully usable for the basic functionalities I've described, well translated, and what it was chosen for, i.e. its simplicity of use and respect for privacy.
This is the type of OS that I think many people would like to use, and that we could promote around us! Proficiat.
So, ota-6, yes, ota-7, if it comes out, we'll see if I try too
Thanks for reading.

@stanwood
Hello,
yes, it does, and we talked about it on https://forums.ubports.com/topic/9803/focal-20-04-is-out-for-quite-a-while-now-you-still-use-xenial-16-04-i-would-like-to-know-what-stops-you-from-upgrading/82
and you sent me your link https://github.com/ubports/ubuntu-touch/issues/2022 which @danfro also gave me.
What I'm noticing is that it works after a reboot, but after receiving an SMS, the audio no longer works, then after a reboot it works again ... I don't know if this also happens after a phone call ...
@peat_psuwit
Hello,
Thank you for your clarification. It would be interesting and necessary for this situation to be dealt with and corrected soon, in the hope that it will be for the ota-6.
A more secure ota-5, of course, so happy ota-5 !

@peat_psuwit
Hello,
I let myself go to the rc.
It says : « only critical and security fixes will be able to enter Ubuntu Touch 20.04 OTA-5 ; Normal bug fixes and new features will need to wait for our next release »
A few months have passed since ota-4, but ..
Ok, since it's like that, … fixed bugs and new features will come in the next one.
So I hope that from ota-6 I will be able to hear the sound after a video recording with the camera.
I say this because I think it's normal for it to work perfectly on a smartphone, as this feature has been used on cell phones for 20 years. As a UT user since 2015, I would like this basic function to work normally again. I won't wait any longer for ota-7. I disobeyed but Thank you for your understanding.

Hello,
I had the same problem as @armchairFF for dev channel updates. OPT5 wouldn't restart normally and stayed on Recovery boot, so I did the update on the stable release channel with Ubports installer, and I left my phone on the stable channel for now while waiting for the next ota-5.
But I think the problem had been mentioned somewhere 3 weeks ago ... ?

@stanwood
Hello,
Very good action !
Hopefully we'll be able to see the results of your work in ota-5.
Thank you.

@danfro

@vince-vs said in Call for testing a the new build-variant "standalone-kernel-method" (vs. full-system-image):

I know @vince-vs would love to see the LED fixed. (Would you also dare to flash a kernel to get the led working?

Hello,
Very true, but I think it will make many more people happy than I am, and if the LED flashes again after incoming missed calls, just like it does when the battery is full after charging, it will be Top again.
What's more, you had written to me that the new kernel could solve the problem of the camera sound after recording, ...so, for me, what more could I ask for, except that the project continues in this way towards the path of fluidity for its operating system....
Many thanks to you

@stanwood
Hello,
Ha, so it's been a long time already.
It's a shame for such an important feature on a smartphone ...
In any case, I can tell you that in 2022, on my OPT5,
it worked, because I had to use the camera and film ( with sound ) to show my car dealer that there was a problem in the steering of the car and fortunately because it was repaired ...
Anyway, maybe if the new kernel that @danfro is talking about will be available in a very soon ota, maybe that will fix this annoying bug.
Sincerely

@danfro
Hello,
Please note that the audio recording of the camera does not work after broadcasting a call from OPT5; during an external call, there is no such problem.
If the only solution will be the new kernel, for the moment, until it's in a stable release, I can't risk installing it on a phone I use every day.
Do you think the new kernel will soon be available as a stable ota release ?
Sincerely