Posts made by Emphrath

Ok so halium 9 is also theoretically doable on 1+1 ^^

@flohack Thank you !

@alaraajavamma Afaik someone is working on making a backup solution working from the installer

Hey there ! Just a quick question: since I'm on Oneplus one, I see two processes in top I'm pretty sure weren't there on FP2: "Binder_2" and "sensors.qcom". I'd like to know what they are. Thanks !!

@xray2000 oh ok it needs the vendor partition ??

I've been thinking - I have a spare FP2 on my hands I don't plan on using anytime soon. I understand anbox is now based on treble and won't run on anything under Halium 9. There's a Halium 7 build for FP2. Wouldn't that be a good testing device to try and port anbox to Halium 7 ? What I'm trying to say is I'm willing to send this FP2 to Erfan it this can help the majority of UT users with Halium 7.

@lakotaubp I can't do that, because installing UT over cyanogen thoroughly bricks the phone I had to install OxygenOS over the manually flashed Cyanogen in order for UT to (I guess) get the partitions it expects. Now indeed I'd like to know if I need to flash any additional firmware since the last OS I installed was the Oxygen zip provided in the article for firmware thread. That should have flashed its contained firmware bits by itself, shouldn't it ?

@lakotaubp I agree with the latest statement. And yeah, partitions have to be different in some way

Ok. After almost three days of continuous try and error, I finally have a working OPO, complete with cellular and wifi ><
I would just like to share a few thoughts and ask a couple of questions. When I received the phone, I'm now confident it was running Oxygen, most likely the last version available for bacon. I flashed the firmware from the zip in the related thread (last Oxygen update) and it might already have been a mistake, because it probably was already running the last firmware available. Then I made a mistake for sure : I flashed non_static nvbk.bin to modem. It's meant to be flashed on stanoppo sth. If you read the thread "article needed for firmware update" somebody actually noticed this, but it has not been corrected in the main tutorial post, which resulted in me flashing two images in the same modem partition. Then, I tried to install UT, and had no modem (obviously). In the following attempts to install various roms and firmwares, I failed to notice than the user partition was not being properly read, and it happened after every installation of UT. So, one probably needs to format it from twrp or fastboot (the latter being more inconsistent in my experience). I finally managed to boot on something: CyanogenMod 12.1, after I manually flashed every bit of firmware and system partitions. But Installing UT on that resulted in a bootloop or a static splash screen. I then decided to install Oxygen OS, without flashing anything prior to sideloading the zip, in the hope that what "made it boot" wouldn't be erased by whatever firmware OxygenOS flashed in the install process (which did NOT boot by itself). I had to erase a string from a google script called "updater" in the Oxygen zip to bypass the check for "OnePlus" resulting in the infamous error :"this is a A0001". And here I am. So, what the hell ? Am I running an opo with half cyanogen 12.1 firmware, half Oxygen ? Is there a need to still flash anything from the Oxygen firmware now that it boots ? Does anybody understand anything about this absolute nonsense ?
On a lighter tone: it seems my proximity sensor doesn't work. The screen doesn't shut down when I pass a call and sensorstatus gets no data from it. I'm pretty sure it worked on android. All in all it's a minor inconvenience but I fear it's related to some firmware issue...

I tried with satble channel, and now i'm in a bootloop

Well UT installer goes through, but at the end of the process, when the recovery performs the update on its own ,i'm left on the recovery screen, it doesn't reboot by itself. And now it won't boot further than the splash screen ><

@daereth The stock OS for the AOOO1 is NOT OxygenOS. It's Cyanogen 12.1. The only valid ROM out there is here: https://androidfilehost.com/?fid=24369303960686196

Then follow this thread: https://www.thecustomdroid.com/restore-on/

You might be in trouble at the last part (flashing userdata image), at least it was the case for me - I had corrupted the user partition. Fastboot gave me an error message. In that case, flash a twrp recovery, go to wipe/advanced/reformat partition (data, obviously) and format it to ext4, then back to f2fs. Then, back to fastboot, and you can flash the user partition appropriately.

@bibaleebu THIS IS THE ONLY WAY I managed to boot on something again

Indeed it didn't.

I just received my OPO and... Gods be damned I'm having the same trouble than @bibaleebu except that I don't even have working calls or any network at all (it doesn't even see my simcard) All of this was working before. Prior to flashing UT, it was running cyanogen, but I flashed every bit of the firmware according to this thread BEFORE I flashed UT:
https://forums.ubports.com/topic/6193/article-needed-for-firmware-upgrade
Including the RADIO part. Maybe I shouldn't have. I'm now trying halium devel but judging from @bibaleebu experience I think it won't help

@keneda yep, sorry, my mistake.

@sam-strelitz UT is none of this but you're in for a huge disappointment if you're looking for "just linux on a phone". UT works by flashing an .img on your phone. It's quite static by nature and updates are made by re-flashing the whole system partition. This and the fact that root is read-only by design means you won't be able to run apt for instance, or if you do, by making root writeable, everything you installed will be wiped by the next update. Apps are installed from a store which uses an in-house format: .click. Most apps are sandboxed for security reasons and if you intend to write a custom script, expect hassles to access the hardware, which is heavily confined I believe. Now the way UT interacts with hardware is not by being an android app, or a VM, but it does use a layer of android to be able to use proprietary drivers (which, contrary to PC, is a norm on phones) and on top of that, there's also a level of "emulation" called Halium, and most phones run all this before they even start UT, except for "native" devices like volla or pinephone, and the Pixel is not one of them. There are numerous charts on this forum which describe the compatibility layers system better than I did. UT is focused on being a user-friendly experience and it achieves it. If what you want is tinkering, you might want to look elsewhere.

@jezek On my FP2 halium 5:
Simple test: 53 fps
Particle system: 32 fps
Dynamic lights: 17 fps

I guess the test should be ran multiple times since it does not reflect what I saw

@magnargj try killall camera-app

@bibaleebu btw, i suppose you've checked this ? It provides what's supposedly the last android package for opo:

https://forums.ubports.com/topic/6193/article-needed-for-firmware-upgrade

@lakotaubp I just bought one cause my FP2 was driving me insane. It should come in a couple of days. I don't know what rom's on it, but another seller claimed to have had lineage 18 installed on it. If it's true, it's a custom rom, but it should do the trick, firmware and partition wise, no ?