Open joelselvaraj opened 4 years ago
@joelselvaraj thank you, it was definitely 2.0 problem. i tried using my laptop with usb 2.0 port and used windows 10 with mi flash tool to install drivers.
Can the new ubports-recovery be used for installing ubports for the first time (avoiding the lineageos 16 step)?
Can the new ubports-recovery be used for installing ubports for the first time (avoiding the lineageos 16 step)?
Lineage 16 is required right now or else system won't boot
@Nandanrmenon @joelselvaraj is internet for anbox apps working now ??
@Nandanrmenon @joelselvaraj is internet for anbox apps working now ??
I did fix it in my latest update with a temporary workaround. It should work, if you fetch the latest boot.img and system.img from CI over here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/1101031496/artifacts/browse/out/
@Nandanrmenon @joelselvaraj is internet for anbox apps working now ??
I did fix it in my latest update with a temporary workaround. It should work, if you fetch the latest boot.img and system.img from CI over here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/1101031496/artifacts/browse/out/
Got lil confuse just confirm me.. i have already lineage 16 so just flash those both images and done right
@Nandanrmenon @joelselvaraj is internet for anbox apps working now ??
I did fix it in my latest update with a temporary workaround. It should work, if you fetch the latest boot.img and system.img from CI over here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/1101031496/artifacts/browse/out/
Got lil confuse just confirm me.. i have already lineage 16 so just flash those both images and done right
hello, you have clean flash los 16 making sure have the latest pie firmware(not ten). if you are already using los it is best to format data in twrp and flash boot and system img
@Nandanrmenon @joelselvaraj is internet for anbox apps working now ??
I did fix it in my latest update with a temporary workaround. It should work, if you fetch the latest boot.img and system.img from CI over here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/1101031496/artifacts/browse/out/
sir any chance of ubports installer?
sir any chance of ubports installer?
Proper Ubports Recovery is needed for ubports installer to work. while i did have uploaded the recovery with OTA support. it doesnt seem to work properly now. The partitions are not getting mounted for some reason. Without it, the ubports installer is not installing the system image + boot image properly in the final stage.
I need to work on this for few days to debug it, but unfortunately, this is my main phone. So i ll find time in the weekend or sometime to fix it. hopefully.
@joelselvaraj man volte is not supported ??
Not supported by Ubports themselves. Nothing we can do abt it. I ll probably add it in the checklist. But no one is working on it as far as i know. Its proprietary and no one completely know abt how it works.
From: Sagar Gaur @.> Sent: Wednesday, March 24, 2021 8:59:01 PM To: ubports-beryllium/projectmanagement @.> Cc: Joel S @.>; Mention @.> Subject: Re: [ubports-beryllium/projectmanagement] Porting Status (#20)
@joelselvarajhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fjoelselvaraj&data=04%7C01%7C%7C2a1719c430444be8d25b08d8eed98d28%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637521965424013100%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=XAjyy8hlZyl6Q8U%2BK7ZVFN6K07N%2F%2Fo%2BAjgCbvv%2FoVgk%3D&reserved=0 man volte is not supported ??
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fubports-beryllium%2Fprojectmanagement%2Fissues%2F20%23issuecomment-805922062&data=04%7C01%7C%7C2a1719c430444be8d25b08d8eed98d28%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637521965424023093%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=g7uTYwSmjnEf7t%2BuKHbsLBIUA2qaRp9VgBPKDmu2MUQ%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC77DEGHGCMCJ3FEHNZLDSTTFIAL3ANCNFSM4NBFXVQQ&data=04%7C01%7C%7C2a1719c430444be8d25b08d8eed98d28%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637521965424023093%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=4seS4g%2FZ%2F9FLCg3qfVOblrgYEUaCcJrvQK14Y3oHI8I%3D&reserved=0.
@joelselvaraj can we try halium-10.0 instead of halium-9.0 because it can a chaos installing back and forth the firmware please do let us know if the recovery is working again or not
can anyone give an guide how to install anbox
I was using Ubuntu Touch on the Poco F1 through Halium which mostly worked fine. However, I couldn't install the latest OTA so I thought I'd give the official UBPorts image a try, based on the instructions you posted over on XDA. I followed all of the steps carefully, but it just won't boot. It keeps displaying the Pocophone logo and that's it. It does boot into UBPorts Recovery when I hold volume up, so that confirms it was installed fine. Fastboot doesn't recognize the device, so it's pretty much bricked now. How do I recover from this (and also get the official UBPorts image working)?
Are you sure you u installed lineage 16 1st. then "format data" (not wipe data) before flashing the images?
From: Heimen Stoffels @.> Sent: Tuesday, April 27, 2021 5:49:37 PM To: ubports-beryllium/projectmanagement @.> Cc: Joel S @.>; Mention @.> Subject: Re: [ubports-beryllium/projectmanagement] Porting Status (#20)
I was using Ubuntu Touch on the Poco F1 through Halium which mostly worked fine. However, I couldn't install the latest OTA so I thought I'd give the official UBPorts image a try, based on the instructions you posted over on XDA. I followed all of the steps carefully, but it just won't boot. It keeps displaying the Pocophone logo and that's it. It does boot into UBPorts Recovery when I hold volume up, so that confirms it was installed fine. Fastboot doesn't recognize the device, so it's pretty much bricked now. How do I recover from this (and also get the official UBPorts image working)?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fubports-beryllium%2Fprojectmanagement%2Fissues%2F20%23issuecomment-827561568&data=04%7C01%7C%7Ce1ee2476ff804ebf81e208d90976b9f1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551227788782151%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=8pdzeWwBsJUsusEk38SEd1J%2Fo%2FlOx9kX81L%2FRODOjIQ%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC77DEHJLGVITLS5UFOC2VDTK2TVTANCNFSM4NBFXVQQ&data=04%7C01%7C%7Ce1ee2476ff804ebf81e208d90976b9f1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551227788792149%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=QIusJa6jbByh7GbdvFFJ0wtQx5P3%2FtNCaZrtOR%2F3jd4%3D&reserved=0.
Yes, that's what I did.
Hmmm. No idea what's wrong then.
From: Heimen Stoffels @.> Sent: Tuesday, April 27, 2021 5:53:57 PM To: ubports-beryllium/projectmanagement @.> Cc: Joel S @.>; Mention @.> Subject: Re: [ubports-beryllium/projectmanagement] Porting Status (#20)
Yes, that's what I did.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fubports-beryllium%2Fprojectmanagement%2Fissues%2F20%23issuecomment-827563987&data=04%7C01%7C%7Cd0dbd38d5cde4b69b76c08d909775532%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551230393541725%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=etfo9aQKH5IqeXzAoh%2BfUOSHVfss1xHF4wUKsI2vCPs%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC77DEBPULR4BFZ6M6Q3Z4TTK2UF3ANCNFSM4NBFXVQQ&data=04%7C01%7C%7Cd0dbd38d5cde4b69b76c08d909775532%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551230393541725%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EwPgoGomCioS3GoFFIJfmRWxVmQMgmRsJckEutfpVCY%3D&reserved=0.
But how do I recover from this now that only the UBPorts Recovery is working and fastboot isn't?
Fastboot should work fine. We are not doing anything that could break it. As i mentioned in above somewhere try using a different system with usb 2.0 hub.
From: Heimen Stoffels @.> Sent: Tuesday, April 27, 2021 5:55:56 PM To: ubports-beryllium/projectmanagement @.> Cc: Joel S @.>; Mention @.> Subject: Re: [ubports-beryllium/projectmanagement] Porting Status (#20)
But how do I recover from this now that only the UBPorts Recovery is working and fastboot isn't?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fubports-beryllium%2Fprojectmanagement%2Fissues%2F20%23issuecomment-827565197&data=04%7C01%7C%7C0b788aa9a81442cb8da508d909779c19%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551231582688622%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=le9wAlqDbaswFmlRXvmWOrv6PjPOCC3vIOzU46qjZWA%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC77DEBRN3K6U22IE3CZWCDTK2UNJANCNFSM4NBFXVQQ&data=04%7C01%7C%7C0b788aa9a81442cb8da508d909779c19%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551231582698615%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=qFKN%2F5p%2FrCgEe7EkfGFG2K0k5SXcNCNb3H0O5Qx3lh0%3D&reserved=0.
I did, but it still doesn't recognize it and fastboot even exits after a minute of trying and reboots the device.
Mm weird. I have kind of faced similar issues. But it would get recognized in that <1 min. U can try MiFlash tool to clean install fastboot stock rom. During that flash, it wouldn't restart automatically i guess. But try it on ur own risk. I flash stuffs every day and yet have not faced any unrecoverable brick.
From: Heimen Stoffels @.> Sent: Tuesday, April 27, 2021 6:06:28 PM To: ubports-beryllium/projectmanagement @.> Cc: Joel S @.>; Mention @.> Subject: Re: [ubports-beryllium/projectmanagement] Porting Status (#20)
I did, but it still doesn't recognize it and fastboot even exits after a minute of trying and reboots the device.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fubports-beryllium%2Fprojectmanagement%2Fissues%2F20%23issuecomment-827572516&data=04%7C01%7C%7Ce017f11599d54b81b1ee08d9097914b3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551237897692034%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=AQ0kBeZ2%2B7%2FRrx6OHLGNh3LQf8AJ2cZeIAHO1KUEtSY%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAC77DEDRWJLPGYY62O4FPSDTK2VUZANCNFSM4NBFXVQQ&data=04%7C01%7C%7Ce017f11599d54b81b1ee08d9097914b3%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637551237897702031%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=09k4A%2FECAhodoDD8nr55hZf3eMXzFLtKzewXxY7mZN0%3D&reserved=0.
Didn't work either. I guess it's dead, Jim… (or so to speak)
@joelselvaraj any updates sir?
Didn't work either. I guess it's dead, Jim… (or so to speak)
is your device showing up in fastboot devices?
Didn't work either. I guess it's dead, Jim… (or so to speak)
is your device showing up in fastboot devices?
Nope :(
The link to the GSI image is inaccessible.
The link to the GSI image is inaccessible.
@Nandanrmenon From here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/
You can click the latest job with "flashable" as name. Then click browse and then download from there. Whenever i create new CI builds, old ones are getting automatically by gitlab after sometime. I think that is the reason old link is not accessible.
@shubhambaid read this instruction from the previous message to get the latest images. GSI images are no longer maintained. Follow the post here: https://forum.xda-developers.com/t/rom-ubports-gsi-ubuntu-touch-for-poco-f1-pie-based-alpha-2-unofficial-updated.4133513/page-4#post-84559681
But use the link from above to download the system and boot image
@Nandanrmenon From here: https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1/xiaomi-beryllium/-/jobs/
You can click the latest job with "flashable" as name. Then click browse and then download from there. Whenever i create new CI builds, old ones are getting automatically by gitlab after sometime. I think that is the reason old link is not accessible.
any progress with bug fixes for Wi-Fi sir?
any progress with bug fixes for Wi-Fi sir?
@Nandanrmenon what wifi issues u have?
any progress with bug fixes for Wi-Fi sir?
@Nandanrmenon what wifi issues u have?
wifi automatically disconnects after some time and either restart or removing wifi settings and reconnecting helped me to get back online
@joelselvaraj there is one more bug which is really annoying, the touch screen. when phone is idle for a few minutes, using the recent and app launcher is nearly impossible. touch almost doesnt work too. again reboot or again keeping it idle fixes it.
@joelselvaraj I have one doubt if I install jiovoice which allow jio user to make call without volte will it work in anbox ?
@joelselvaraj I have one doubt if I install jiovoice which allow jio user to make call without volte will it work in anbox ?
Nah. i dont think so. Anbox dont have access to modem at all as far as i know.
Ubports is taking efforts to bring in support for VoLTE. Hopefully they ll make it work.
Thanks for the info I will wait until then
Congo 🥳🥳🥳 @joelselvaraj
Is notch problem fixed !! And its listed on the Ubuntu website 😁 can i wait or should i use as daily driver pls suggest me and what about upi apps in india is that supported 🙆
I'm pretty interested in this rom, but I dont want to replace android. I found a dual boot method for poco f1 called MultiROM. I asked if this supports MultiROM, but I haven't got any answer. I searched it on the comments of the XDA thread, but I think no one has answered. I also searched the internet, I found that MultiROM for nexus 5 supports ubuntu touch, but it was 7 years ago. Also, if you don't know either, does it soft brick, hard brick or bootloop if it doesn't work? I don't care of soft brick or bootloop but I'm scared of hard bricking my phone. Thanks for the hard work of porting this to poco f1!
Edit: I found the answer: you can use it only as the primary rom.
~I'm pretty interested in this rom, but I dont want to replace android. I found a dual boot method for poco f1 called MultiROM. I asked if this supports MultiROM, but I haven't got any answer. I searched it on the comments of the XDA thread, but I think no one has answered. I also searched the internet, I found that MultiROM for nexus 5 supports ubuntu touch, but it was 7 years ago. Also, if you don't know either, does it soft brick, hard brick or bootloop if it doesn't work? I don't care of soft brick or bootloop but I'm scared of hard bricking my phone~. Thanks for the hard work of porting this to poco f1!
Edit: I found the answer: you can use it only as the primary rom.
You can ask your question here. I'm pretty sure some people have successfully dual-booted it. Ubuntu Touch for Poco F1 https://t.me/ubportsforpocof1
Is 3D acceleration here?
Hi. I tried to apply workaround for automatic brightness control from XDA on recently flashed phone but it failed:
chcon: invalid context: ‘u:object_r:vendor_overlay_file:s0’: No such file or directory
Did i miss something?
Hi. I tried to apply workaround for automatic brightness control from XDA on recently flashed phone but it failed:
chcon: invalid context: ‘u:object_r:vendor_overlay_file:s0’: No such file or directory
Did i miss something?
I dont think that workaround will work on Ubports now. I should probably remove it.
For everyone's info, if you are not aware. The work has been upstream'ed to Ubports community repos over here. Development happens over there : https://gitlab.com/ubports/community-ports/android9/xiaomi-poco-f1
You can check the latest status over here: https://devices.ubuntu-touch.io/device/beryllium/
Thanks, Joel. You did a great job with the port of Uborts to the Poco F1.
We will track the status of all main functions here instead of separate issues.