[Porting] Call for Testers
-
@michi2302 said in [Porting] Call for Testers:
yes, fastboot devices is ok, but adb devices doesnot show any device when phone is in fastboot mode
adb devices never shows any devices when the phone is in fastboot mode. Unless you meant to say recovery mode, the behavior described is expected.
-
yes thats it - my phone was allways in fastboot-mode - new in recovery-mode all was fine
- THX -
so next problem, after successful installation - my phone is in the 1+ logo powered by android ??
I had originally installed a custom rom with trwp - maybe that's the problem ? -
@michi2302 I am not sure there already is a custom boot logo for the Oneplus 5/5T.
As long as your phone boots into Ubuntu Touch, then all is well.
-
@arubislander thx for reply
right - the bootlogo is probably from android 11 - other question to run "./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.img"
I have the recovery.img from "http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArT"
installed is that correct ? - because without recovery adb will not run.thx
-
@arubislander no phone does´t boots in Touch hangs on android boot logo
-
I will have to gracefully bow out now, as I do not have a OP 5/T.
But just to get this clear for anyone dropping by to help you. You are in fact saying the installation failed because your phone does not boot to Ubuntu Touch. Correct? -
@arubislander
yes, right - no problems during installprocess. but phone does not boot to ubuntu touch. -
@michi2302
You can fastboot into TWRP and use adb shell to connect to your phone and examine the image files.
They are in /data/.
android-rootfs.img (size 487022592)
rootfs.img (size 3221225472)
Sizes from my working OnePlus 5.You can also check if you have flashed halium-boot.img and vendor.img.
fastboot flash boot halium-boot.img
fastboot flash vendor vendor.img -
I did half of the device checks, I'll do the rest later.
Working
Actors: Manual brightness
Actors: Torchlight
Actors: Vibration
Bluetooth: Driver loaded at startup
Bluetooth: Enable/disable and flightmode works
Bluetooth: Persistent MAC address between reboots
Bluetooth: Pairing with headset works, volume control ok
Camera: Flashlight
Camera: Photo
Camera: Video
Camera: Switch between back and front camera
Cellular: Carrier info, signal strength
Cellular: Data connection
Cellular: PIN unlock
Endurance: Battery lifetime > 24h from 100%
GPU: Boot into UI
Misc: Shutdown / Reboot
Misc: Battery percentage
WiFi: Driver loaded at startup
WiFi: Persistent MAC address between reboots
WiFi: Enable/disable and flightmode works
Sensors: Automatic brightness
Sensors: Rotation
Sensors: Touchscreen
Sound: Loudspeaker
Sound: Loudspeaker volume control
Sound: Microphone
Sound: Earphones detected, volume controlNot working
Actors: Notification LED
Misc: Date and time are correct after reboot (go to flight mode before)
Misc: Online charging (Green charging symbol, percentage increase in stats etc) #No green charging symbol
Misc: Offline charging (Power down, connect USB cable, device should not boot to UT) #Boots into Oneplus logo -
@ianus can I also use Helium-recovery instead of twrp ?
thx for reply
-
This post is deleted! -
@michi2302
I don't know. But
fastboot boot twrp-xy.img
will not overwrite your boot or recovery partition on the phone. The phone will boot directly from the image file. -
@michi2302 No, sorry, the Halium recovery does currently not mount all the partitions correctly, and it wont give a warning, so if you try to push files with adb they are just pushed into tmpfs mounts. You can use it if you manually mount data in recovery. But for the moment I recommend TWRP, our recovery will only be needed when we have OTA updates in place
-
@ianus thx for reply
my /data is empty ?michi@Core5M:~/Downloads$ adb shell
root@OnePlus5:/ # ls /data
root@OnePlus5:/ #regards
-
@ianus
now I have tested ./halium-install-standalone.sh -p ut -s ubuntu-touch-android9-arm64.tar.gz system.imgand after success I had:
adb shell
root@OnePlus5:/ # cd data
root@OnePlus5:/data # ls
android-rootfs.img rootfs.imgand then I reboot phone
check again and /data is emty ??
-
so now the phone boots up !!
the problem was the recovery.img I downloaded from http://twoot.bin.org.in/nextcloud/index.php/s/2Zk2Lz8cZCdqArTnow I installed trwp an all went fine...
thx for help - have a nice day
-
@michi2302
You need the phone to be in TWRP to run halium-install-standalone.sh.
The filesystem you see from adb in TWRP and in Android/Ubuntu Touch is different.
I think recovery.img contains the original recovery, which I can't find how to use adb to connect to. -
I'd like to learn more about UT dialing software. Could someone point me towards right direction, where I should start studying and looking into in all that stuff, in order to learn to help with the development. I tested and saw that the phone dials and rings, but after accepting a call, there is no voice been sent or received. Also couldn't end the call and even if the other person ends it, it will still look like the call is on with the OT phone. (I rebooted the phone to get the call off). Also sometimes it seemed like there was 2calls on at the same time with the same person. So, what kind of a problem we are dealing with here?
-
@shadowbird2468 The problems are that calling in general has issues in Halium 9. Currently it makes no sense I believe you look into this things, there are other people already on it. There are 3 or 4 services involved in calling, plus the Android container also ^^
