LG nexus 5, welcome screen is shifted upwards after switching power on
-
@keneda Googlandroid is very uncomfortable... and, this is not right way
-
@markatrafik To run uTouch correctly on an android native device, you need the good android version installed on before, this is the only way...
-
@keneda That's clear... so how does UT still use part of Android to interact with the hardware? And the community does not have the power to normally port all drivers into the mainstream Linux kernel. There is no way to convince manufacturers to do this - there is no market yet. But, what does "correct" Android mean? I guess it's the one that was installed by the manufacturer on the phone when it was sold, and updated in the normal way? And while UT wants Android 9 but not Android 10 - as there are some problems in interfacing with its components? This is all very sad of course... as no one wants to change the situation, or simply there is no power.
-
@markatrafik
I don't get your point...For each device, for each halium or non halium uTouch port, you need some specific android to be on this device prior installing, that's the way it is for android native device and no one can change this.
Now if you don't want any android part, there is the pinephone, and maybe one day, Librem 5.
-
@keneda If the community will not set a goal of independent operation of UT with smartphone hardware as it do Librem and Pine, after a while Google will shut down the ability to use its components to work UT. For this, cryptographic means of binding of software and hardware can be used by Google. On the other hand, we can go the current way, then if UT gains more popularity, we can make own HAL, independent of Android, and the manufacturers themselves will write drivers for Linux and fit it into that HAL.
-
If I get your point of view, as long as AOSP is open sourced there is no risk.
The interface with the drivers and any binding with the hardware can be integrated within UT.A port has to know which android version was previously installed in order to assess correctly how to access the drivers.
If a driver is not in the right version than there is a risk the API changed and induced bugs... -
Hi all,
thank you for the discussion about that topic.Interesting, I have to update to the newest android system before
the installation of ubuntu touch!I can understand the explanation above for that procedure but it is
unexpected. In the common documentation and the device page I did not remark any hints to that fact.Probably, I can use the ubports-installer to install the latest recommended android image.
After that, I have to install ut again and start the setup from scratch
again.Do I guess right?
-
Does ur screen stay this way permenantly? Ive ported several nexus5's and the one i recently bought does this glitch. But when i turn the screen on and off it goes away. If i do a factory reset the glitch will be there. But its strange because ive only seen it and ive ported 6 nexus5's so far.
-
@unrealb2
Sorry for my late answer, I haven't visited the forum for a longer time.
You have described exactly the behavior, I see. In the answers above, the probable cause is described. The device, I bought had an older android version and updating to the most recent one - for the nexus 5 - and then reinstalling ubports should solve that behavior. I didn't try that till now. Perhaps, I will find the time the coming weekend. -
final status:
Today I have flashed the device with the last available android image for the nexus 5. I followed the description on https://developers.google.com/android/images#hammerhead.
After that I repeated the ut-nstallation with the UBports installer. The phone seems to work and the screen issue is fixed.