-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
binder: undelivered transaction
and binder_alloc_buf, no vma
#12
Comments
@kungfooman it might be a very bold step but has anyone in AOSP community tried building something for the Oculus devices? |
Hi @rajatgupta1998, thank you for the link! I wasn't aware of it and I just tried it and it works like a charm. I don't know what you mean by root solution, since the unlocked Go has root access. Can you elaborate on that? I don't know about a custom kernel, but if the community is able to fix this browser bug, then I would love to use or contribute to it. I didn't find any time for further testing so far if the browser bug even still exists in this unlocked version. |
@rajatgupta1998 I have been working on getting TWRP recovery ported to the Oculus Go. There are no device sources so I am having trouble with setting up a working tree. I got it booting but sadly I keep having trouble with setting up A/B partitioning. I have tried multiple things in order to try getting something to mount properly but I keep coming up short. To add onto that I have also tried working on getting the Mainline Linux kernel working on the device. It boots, but nothing except the display seems to work. I plan on trying to get the TWRP port mostly working then move on to getting AOSP or LineageOS ported. I am a beginner in porting but I have faith I can do it. |
I'm very happy to hear... I wish you a lot of success (and maybe a bit of luck 👀😵) |
Thank you, I appreciate that. I just realized, your name was super familiar and I just realized why lol I think I first saw your name in some group on Telegram, but I think I actually spoke to you in the Halium group |
@WolfLink115 Did you get any further on porting TWRP or build a custom firmware? I was looking into the same thing, but wanted to know how far you got? |
I got TWRP ported with almost everything working but I somehow bricked the headset (I booted LK2ND and tried to boot an EDK2 image I built to the headset and the speakers made a "pop" sound, went black, and showed up in the PC briefly then it cut off and never booted again as well as never showed in the PC again). I can't work on it until I get another headset so sadly there is not gonna be any progress from me until that happens. I got a job now so we shall see what happens. |
Might as well re-reply, but I got another Oculus Go and I am taking a stab at porting to it again. I wanted to build TWRP 12.1 for it again, but this time around I am getting a clang-12 build error. I dunno how to change it to use GCC or an older version of clang so I am currently stuck with using TWRP 9.0 for now. Again, pretty much most things are still working. I suppose I can attempt to port LineageOS for right now. Will likely take inspiration from another device that uses the MSM8996Pro chipset as I have never built a custom rom before (lol) I will be sure to update y'all on the progress though! Also thank you @rajatgupta1998 for helping with TWRP a bit :3 |
@WolfLink115 Wuhu.. great job.. I now have 4 headsets.. so if you need betatesters I would love to help, can probably also help to fix issues.. |
@MrMEEE Sure, I will be sure to message you if I get any progress. I also joined the Oculus Go Discord group, sent a message in General and I replied to someones message in Preservation as well lol |
Update here, I got pretty much everything working on the TWRP port (including rotation and OTA Update Support) Link to the device tree here: https://github.com/WolfLink115/android_device_oculus_pacific |
Dear Oculus team,
I used to be able to use my Oculus Go for VR development and I always had WLAN disabled to not receive any unwanted updates. However, a few days ago I decided to turn WLAN on again and it updated everything... first thing I had to do was a factory reset, because otherwise I would only see the three-dots-issue.
But after the update the entire Oculus browser fails to render anything. I connect to my local web server and the page is simply white. On one occasion it actually displayed the content, after I entered Firefox Reality, quit it and opened Oculus browser again (Firefox Reality renders properly). When I open a video, the sound plays but the video is just white aswell.
I tried to debug this issue, but since you took every opportunity to turn Linux into a straight jacket, it is very hard to do so even with years of C and Linux experience...
So the only pointer I have so far is
dmesg
:Based on this article [1]
[12513.651903] binder: 12416: binder_alloc_buf, no vma
indicates that probably a Chrome background process crashed or maybe some right issue regarding/data/data/com.oculus.browser
?Hereby I also inform you about the European Right to repair which requires you to allow me to fix my own system [2].
That means:
[1] https://chengyihe.wordpress.com/2015/10/19/android-binder-error-log-binder_alloc_buf-no-vma/
[2] https://www.europarl.europa.eu/meetdocs/2014_2019/plmrep/COMMITTEES/IMCO/DV/2022/03-16/MfR_RighttoRepair_EN.pdf
Thank you for your attention,
Hermann Rolfes
The text was updated successfully, but these errors were encountered: