Database Develop

[FreeXperia Project] AOSP Android 5.1.x

Hi all,
We are starting today daily AOSP builds for all 2014 Sony devices so that you can enjoy a NEXUS like experience
Thanks
SONY for publishing AOSP base gits
All AOSP developers and testers
Sources
https://github.com/fxpdev
Download
http://fxpblog.co/

howto flash
download Android SDK
http://developer.android.com/sdk/index.html#Other
in adt-bundle-windows-x86_64-xxxxxxxx/sdk/platform-tools folder you have the required files
copy the following files in same folder where your AOSP image files are
adb.exe
AdbWinApi.dll
AdbWinUsbApi.dll
fastboot.exe
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash userdata userdata.img
disconnect device, press power and enjoy!

nice! thankyou! Merry Christmas FXP Team. have a break will ya?

What about the cam?

Thanks
Cam working?

Go to the page and check it.
Spoiler: no, it's not working yet.
Merry Christmas!

No build for sirius?

cheep5k8 said:
No build for sirius?
Click to expand...
Click to collapse
sisius will come today
we just fixed the build error

is cam working in latest aosp build ?

Do I need unlock my phone's bootloader? And what android version of it?

RyTekk said:
Do I need unlock my phone's bootloader? And what android version of it?
Click to expand...
Click to collapse
#1 Yes
#2 Android lolipop

OK, I'm testing build 20141226 right now (sirius).
So far, I can't get mobile to work at all, and I don't mean just mobile data, but even telephony (it's not asking for a PIN).
Sensors seem not to be working either. I'm looking into what can be fixed or what's wrong or missing.

Am i good to wipe data and avoid flashing the userdata
Or do i need to flash the userdata img

I'd say wiping userdata is good enough, I'm on my 2nd flash of the latest build right now and this time I didn't flash the userdata partition, I just wiped from TWRP.

Sounds good
Ill report back when i install this

Baseband is not found.. Krabappel2548 and me had this already fixed, I'm looking for the reason it's not working.

After flashing : boot.img , system.img and userdata.img and rebooting phone doesn't connect to mobile data and during searching for network reboots everytime.
Wifi connects , installed Google Camera from Playstore, after opening camera force closes .
Back to my back-up ...

Is the cam working here?

CorzCorry said:
Is the cam working here?
Click to expand...
Click to collapse
This question gives kittens cancer in the nut sack. Please refrain from asking it in every 5.0.x build thread.
It will not work until Sony rls its own 5.0 build.

Reb0rn said:
This question gives kittens cancer in the nut sack. Please refrain from asking it in every 5.0.x build thread.
It will not work until Sony rls its own 5.0 build.
Click to expand...
Click to collapse
u mad bro ?:crying:

[D6708] [Sony Xperia Z3v] LATEST Prerooted Lollipop 5.1.1 23.4.B.0.319 R30C w/ mods

Hello all! I would like to finally present to you the prerooted flashable zip of the latest 5.1.1, which also includes the patch fix for the Messages problem. I have also included into the zip a Torch flashlight boost and Z5 sound enhancements!
To flash this, be sure you have TWRP recovery installed. If you need to know how to have recovery, follow my guide in the link below to get your phone started.
This is the latest build straight from Xperifirm, that includes the patch for Messaging issues. This is not based off of anyone else's customized builds. This is stock being prerooted with some helpful mods.
Credits to:
@androidexpert35 for the Z5 enhancements
@[NUT] for XZdualrecovery
@olokos for the Flashlight boost mod
@zxz0O0 for the PRFcreator
Please hit thanks when I've helped you with everything you need for the best of your Z3v!
https://mega.nz/#!S5U0kL7L!DQvTvQjTnWXY-858Dr8WvjeeHdRgR-Kxfv2SFzpjqGY
Note: For those who want to get Xposed, go here http://forum.xda-developers.com/showthread.php?t=3034811. Be sure to grab the >>xposed-v80-sdk22-arm.zip<< as this is the one best compatible for our ROM.

The download is asking for a decryption key?

pvcdroid said:
The download is asking for a decryption key?
Click to expand...
Click to collapse
Same here

decryption key?

Same here

Sorry abut that guys, I fixed the link just now!

Thanks and thanked, nice job. Dirty flashed, no problems.
Afterwards, flashed the xposed-v80-sdk22-arm.zip to get xposed and greeted by lovely black screen. Bummer, not sure what happened. I used sdk21 back with 5.0.2 naturally. Also, don't recall why but never updated past v74 either

I had xposed and dirty fleshed then reinstalled and it was being weird. Rebooted a few times and finally got it all back. Apex launcher here, so I'm not sure what happened.
Edit: Thanks for the upload gigaspx.

Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail

darker_slayer said:
Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail
Click to expand...
Click to collapse
Sdk22 build 80 with apk 3 build 4 and gravitybox, blacklist, bubble upnp, xtether.

thanks for this, any plans to deodex this in the future?

darker_slayer said:
Which xposed version did you end up using?
I rebooted several times before giving up and reflashing 5.1.1 ftf. I'm leaving xposed alone for now. This is my only phone, and the reboot after flashing xposed or the ftf takes way too long for me try brute force without any confirmation
Giga your zip is working great, sorry to derail
Click to expand...
Click to collapse
direct link framework : http://forum.xda-developers.com/attachment.php?attachmentid=3631562&d=1454436745
Installer : http://forum.xda-developers.com/attachment.php?attachmentid=3383776&d=1435601440

Everything's good now, grabbed the wrong framework before

shakan09 said:
thanks for this, any plans to deodex this in the future?
Click to expand...
Click to collapse
That will be entirely up to @Tigerhoods to do this, alonng with whatever modifications he wants to make. I just make things easier for people by attaching along some goodies that can make the ROM more special.

How do you dirty flash this phone?

Great job many times over @GigaSPX!

Great job
Thanks for sharing this with us

clearionr said:
Can I just flash this via recovery? It's not showing up in flashmode
Click to expand...
Click to collapse
The best way to flash is through TWRP recovery.

Can someone try screen mirroring with this build? I'm having problems with the one tigershark made with which causes a forced reboot. Drm key issue? From the comments here it looks like this build started from the other current one he built in the dev section. It's a huge pita to try to debug because after every reboot it takes 20 minutes for apps to rebuild.

pvcdroid said:
Can someone try screen mirroring with this build? I'm having problems with the one tigershark made with which causes a forced reboot. Drm key issue? From the comments here it looks like this build started from the other current one he built in the dev section. It's a huge pita to try to debug because after every reboot it takes 20 minutes for apps to rebuild.
Click to expand...
Click to collapse
What? No! Mine isn't based off of his and it's the most current build with his not having the new patch that fixes messaging problem. I grabbed mine straight from Xperifirm.

[ROM][EXPERIMENTAL][BOOTLOOPS][XT907][KKBL][LineageOS][Nougat]LineageOS 14.1

THIS ROM BOOTLOOPS. NO NEED TO CONFIRM OR POST SUCH ANYMORE​
Basically this ROM is an experiment at building LineageOS 14.1 (Nougat) specifically for an xt907 KKBL
How I built it:
Set up a virtual Box (on Win7 64b) to build Lineage OS 14.1 (followed their instructions)
Source: https://github.com/LineageOS/
I used an existing xt907 KKBL device tree (https://github.com/LineageOS/android_device_motorola_xt907) it looks old, but I built a JBBL device tree based from this project, and that booted. I also built TWRP using this device tree, and I have been told that it works
Basically, I have done no "magic" here. If this ROM works, I may also be able to build crDroid & ResurrectionRemix Nougat as well. Actually, my JBBL from this device tree worked better for crDoid and RR than LOS
This is an experimental build of LineageOS 14.1, Android version 7.1.2, an experimental build for a non-official device (ie xt907 KKBL).
I personally do not have an xt907 with KKBL, but an xt905 with JBBL, so I can't easily test this KKBL ROM. PLEASE tell me if it works or not.
The good
It's LineageOS
It's Nougat!
It's for KKBL
It's built from a device tree that I hacked into JBBL, and that booted
A TWRP for KKBL was built using the same device tree, and I am told that that works
It Builds
The bad
I have no idea if it boots as I don't have a KKBL installed​
Since I do not own an xt907 KKBL, I cannot test this zip personaly, and hope someone with an xt907 KKBL will try the zip and let me (and others) know if it works?
What I hope is that if this boots and runs, I will try building crDroid Nougat (and maybe ResurrectionRemix) for the xt907 KKBL. If they also work, I personally will up[grade to the KKBL (my JBBL version of crDroid has numerous FC's)
Credits: All credits go to LOS contributors and CM maintainers before them.
Almost forgot, Flash this ZIP at your own risk, the responsibility is all yours, it is provided as-is, with no garantees or whatever and I will not be held resonsible for any damage to your device or its data etc etc etc
Installation:
1) Download the ZIP
2) Boot into TWRP recovery (I wou;d recomend updating to TWRP 3.x (see myh othere thread I have been told trhat it works)
3) Make a nandroid (you should definitely be going back) And remember, a nandroid is NOT 100%! if you don't understand this, maybe trying this is not for you.
4) Wipe system/data/cache/dalvik
5) Flash update package (ie install the zip)
6) Flash GApps (probably Open GApps pico...) if it doesnt work, try a wipe and not flashing GApps (it helps with crDroid for JBBL)
6) Reboot to system
If it falls over, please get some logcats and post them on hastebin/pastebin etc etc NOT HERE, only the links. Hopefully we can fix it and have some highly customisable nougat ROM's for your device. And the steps to make it work may also be helpful for the next Android iteration.
Download Link: https://clicknupload.org/uvu9uknep9ku
And please post how you go with this ROM, either way, I would like to know if it works or not to decide if to build crDroid and/or RR. If it does work and crDroid does not, I may get around to building a non experimental build, with Overclocking enabled.

Cant download from that link

Shmaks said:
Cant download from that link
Click to expand...
Click to collapse
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.

DiamondJohn said:
what exactly is the problem? have you tried a different browser? I can directly through chrome and also using TOR browser.
Click to expand...
Click to collapse
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))

Shmaks said:
Tried two browsers - chrome and firefox. Click free download - create download link - click here for download - have Error The requested URL could not be retrieved
Fix: downloading with TOR works))
Click to expand...
Click to collapse
It may of been a timing thing. I posted the link right after the upload finished.

Just flash it (with and without gapps) - neverended boot animation, bootloop

Shmaks said:
Just flash it (with and without gapps) - neverended boot animation, bootloop
Click to expand...
Click to collapse
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.
Never mind, I am also just preparing to build crDroid (Nougat) (source is a big and slow download). I found that with the KKBL code altered to JBBL, crDroid booted while LineageOS 14.1 did not. And maybe LOS13 will boot. The fact that LOS14.1 at least showed the animation is a big positive.
Out of interest, did you flash it using TWRP 3.1.1?

DiamondJohn said:
Out of interest, did you flash it using TWRP 3.1.1?
Click to expand...
Click to collapse
Yes, TWRP 2.8.6 didnt flash it

Shmaks said:
Just flash it (with and without gapps) - never ended boot animation, bootloop
Click to expand...
Click to collapse
DiamondJohn said:
how much time did you give it? I have found 8-10 minutes is the norm for the first boot, and I allow 15 before I concede its not going anywhere.?
Click to expand...
Click to collapse
One difference I have noted between MM and Nougat is that MM will play the boot animation for much shorter a time and go into the "Optimizing app 1 of XX", while Nougat will continue to play the boot animation all through the optimisation (ie a LOOOOONnng time), until it actually loads and displays the launcher. Just a thought, maybe a little hope...

Endless boot screen for me, both with and without GApps. Waited 20 minutes both times. Installed via KKBL TWRP 3.1.1.

I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.

DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Is this still an issue?

DiamondJohn said:
I think its safe to say, it will boot loop for everyone.
However, if you wish to possibly see this go further, if someone was to get a log of /proc/kmsg and logcat (and post on hastebin or such, not here), there may be something simple to change. Not that I am going to spend hour and hours on it, but you never know, it may be simple. To know how to get these logs from a non booting computer, you can get the kmsg while TWRP and the logcat maybe using adb over USB. There are plenty of guides on XDA.
Click to expand...
Click to collapse
Willing to test and post logs. Just not sure how to retrieve the logs.

Not happening
See https://forum.xda-developers.com/showpost.php?p=73567002&postcount=19
Although I would be interested in seeing the last_kmsg log on a KKBL, if anyone has some free time.

As with others, I entered endless bootloop as well. Thank you for making the build to try.

mr3p said:
As with others, I entered endless bootloop as well. Thank you for making the build to try.
Click to expand...
Click to collapse
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?

DiamondJohn said:
I am guessing you dont have a log of the last_kmsg :fingers-crossed:?
Click to expand...
Click to collapse
I apologize for not remembering to save the log. It wouldn't be the end of the world to revert back to KKBL and reload this build to get a log but I'll to find some time to play which is always the challenge.

This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.

DragonFire1024 said:
This wouldn't be a problem so much if Lineage didn't delete perfectly good builds/ROMs for this device when they took over. Why would they do that for this device and not others? That seems a bit too coincidental.
Click to expand...
Click to collapse
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?

mr3p said:
Just curious but if someone wants to run LineageOS, whats the downside of just switching over the to JBBL when builds exist?
Click to expand...
Click to collapse
I can't find working links to downgrade to JBBL

Anyone build AOSP successfully?

I build the AOSP successfully but in my case the microphone is buggy ... everything else is working. Is there Anyone who build it with a working mic? I've build r30 and r32 with the same result :/

I have not yet. Ordered my XZ1c yesterday. Should be here Monday. Hoping for more developer colaberation. Thank You for working on this!

Because of Treble it should be possible to build Lineage OS without interfering with the fingerprint sensor and T-Mobile VoLTE functionality, no?

Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.

N1ghtr08d said:
Can I ask, how is the camera on the AOSP build? Is it still the ****ty quality/green blob effect camera? I want to desperately have root on my xz1 and I know I can have it with AOSP but I don't want to sacrifice the camera.
Click to expand...
Click to collapse
It's still going to be bad. Until we get a proper DRM backup method all custom ROMs will take awful photos.

Issues Flashing Build
Hi there -
If you don't mind me asking, did you run into any issues when flashing the build? I was able to build android-8.0.0_r30 successfully. After flashing android-8.0.0_r30, my phone boots to a screen covered in distorted colors. There is a small message, but most of it is cut off. From what I can tell, it seems that something is corrupt, or so I believe the partial message said.
Did you run into any issues while flashing?
Could you please offer some insight into your process?
Thank you for your time,
Dominic
[Edit]
I am getting the same screen of distorted color after the Sony screen when flashing android-8.1.0_r7.
Before flashing again this time, I went to another machine and used Sony's flashing tool, Emma, to flash a stock Sony ROM back to the device. This allows me to boot to what I assume is Sony's most current build available. The phone boots no problem this way. I decided to try another flash.
My specific steps for flashing post build:
sudo fastboot flash boot boot.img
sudo fastboot flash recovery recovery.img
sudo fastboot flash system system.img
sudo fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v05_yoshino.img
[Edit]
I am able to successfully use Sony's Flash Tool, Emma, on a separate system to get the phone booting to the stock ROM. Emma shows the following under Software:
Application Software:
1307-7511 47.1.A.8.49
[(Delayed) Edit]
I rebuilt AOSP from source and was able to successfully boot into the OS after flashing the partitions.
Maybe a corrupt image was generated during the build process.
Either way, I am updating this in case anyone else comes across it. Downloading the source and rebuilding it resolved the issue.

[ROM][XZ][P][9.0][WEEKLY]OmniROM

XZ/KAGURA/F8331 OmniROM BUILDS
PIE 9.0
DOWNLOAD WEEKLY
REQUIREMENTS TO SUCCESSFULLY FLASH OMNIROM:
1. The device has the latest stock ftf
2. The device has an unlocked bootloader
3. The ODM image zip (version 9) has been downloaded from HERE, and the ODM image has been extracted from it
4. The WEEKLY zip file has been downloaded and copied to the device
INSTALLATION INSTRUCTIONS:
1. Reboot device to fastboot mode, and flash the ODM image with this command
Code:
fastboot flash oem <ODM image>
2. Reboot device to TWRP and flash the WEEKLY zip file
3. (If coming from an 8.1 ROM) Fix /dsp SELinux labels with the dsp-label-fixer.zip
4. (Optional) Flash a gapps package
5. Reboot device to system
CURRENT ISSUES ON OFFICIAL:
1. Device wakes up by itself every 5 seconds, reason unknown
2. Camera quality is suboptimal
KERNEL SOURCE: https://github.com/omnirom/android_kernel_sony_msm/tree/android-9.0
BUG REPORTS
REPORT BUGS ONLY:
- AFTER A CLEAN INSTALL
- USING STOCK OMNI KERNEL
- NO MODS OF ANY SORT
OMNI GERRIT REVIEW
https://gerrit.omnirom.org/
DISCLAIMER:
No one is responsible for any damage done to your device but YOU. You've been warned.
XDA:DevDB Information
[ROM][XZ][P][9.0][WEEKLY]OmniROM, ROM for the Sony Xperia XZ
Contributors
oshmoun, humberos, local__hero
Source Code: https://github.com/omnirom
ROM OS Version: 9.x Pie
ROM Kernel: Linux 4.x
ROM Firmware Required: latest stock ftf
Version Information
Status: Beta
Created 2019-03-17
Last Updated 2019-05-31

Thank you for the separate this from the other pie roms.
I will flash it after I arrive home.
Thank you all for the hard work!
Sent from my kagura using XDA Labs

I'm loving the fact Omnipie is official. I will be flashing this right now. Thank you so much.

Finally flashed! been using it for less than an hour, i can say that its definitely good for daily use. Camera seems better and hasnt crashed yet (like it use to), mic actually picks up audio properly, brightness slider is finally proportional to the brightness level, and its pie
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent), app opening times seem a little longer than 8.1, and 120HZ still doesnt work
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
anyways, thanks dev! (may be editing this thread after more use for battery etc)

XxperexX said:
however, the stereo speaker seems to muffle at high volumes (especially with the ringtones and less with youtube, but still a little prevelent)
Click to expand...
Click to collapse
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
XxperexX said:
im also curious why the linked odm isnt the latest one (im pretty sure the latest is 1st march not feb)
Click to expand...
Click to collapse
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.

sinivalas23 said:
Could it be this kernel bug: https://github.com/sonyxperiadev/bug_tracker/issues/336 ? Looks like the sonyxperiadev team is working on it.
The March 1 release says "Android 8.1", the linked one looks like the latest for Pie.
Click to expand...
Click to collapse
Ah, your correct it does say 8.1 my bad

opps

I saw this version from delta updater (using 8.1 omni) and immediately downloaded flashed oem for pie and downloaded omni 9 but it stucked new omni animated logo. Waited like 10 minutes but nothing happened then rebooted phone but same thing happened. Should i wait more or something went wrong?

Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.

KikiGames said:
Im here with OmniROM freshly flashed trough Open Delta.
I have some problems. First boot never ends, BUT restart worked for me but I have another problem.
Now I need 10 min to unlock the phone when Im lucky.
I unlock with the code and then its instantly relock and it say I cant use fingerprint for first unlock, so I use code again and not work again and still can't use fingerprint.
I do this A LOT OF TIME before I can use my phone. Sometimes it helps sometimes not if I not unlock my phone but use corner dial icon first and then if its ask for code i use it and then I got SystemUI crash error again and again and again.
As I said I try to repeat this methods for like 10 min after every restart. I tried to delete some maybe not compatible apps with this new update but still nothing. Now I will remove some Magisk modules. I will write again.
Click to expand...
Click to collapse
you need to do a full wipe before upgrading to p

Just as @oshmoun said; before flashing new ROMs, it's imperative to do full wipe (if you don't want to lose all your data, then do a full backup in TWRP), as flashing without full wiping can cause TONS of problems. Don't be lazy and follow the instructions properly.

oshmoun said:
you need to do a full wipe before upgrading to p
Click to expand...
Click to collapse
I used the same rom before but the last update. I updated through OpenDelta.

Hello !
It's cool to see our XZ is alive !
I have some problems with this rom after a full wipe and update to oem V6 :
- no sounds during calls, no mic, no earphone, no sounds on speaker
- Magisk 18.1 not working
- With official camera app, while using the flash, only the autofocus led is lit, the second and much powerful led is never triggered resulting on dark shots
For now that's all
Thx

Performance is somewhat distressed and the camera does not work for the sound is not working after restarting the device is improving

KikiGames said:
I used the same rom before but the last update. I updated through OpenDelta.
Click to expand...
Click to collapse
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread

Flashed data, cache and dalvik, factory reset. And installed latest nightly with gapps and magisk 18.1.
Only reason I did it this way is because I was on a unofficial build on Omni. Everything is working as it should. Very snappy and no lag. Still have to see how the ROM handles after it's settled for a couple day, but right off the bat it's amazing. Thank you very much Dev, and happy to see you back on XDA.

XxperexX said:
you cant do that. its pretty misleading having it available on that opendelta ota thingy. you have to follow the instructions in this thread
Click to expand...
Click to collapse
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/

KikiGames said:
Why this ROM showed up as an update then?
I just don't understand it.
Nevermind this is my main and only phone and I work 4 days straight before I can use my PC so I need to use this ROM buggy for me. :/
Click to expand...
Click to collapse
You need a PC to flash this. Follow all steps in order and it'll work. Always remember, unless you have a messaging app that backups texts, you will lose them flashing a cfw. Always always backup anything you don't want to lose.
---------- Post added at 12:56 AM ---------- Previous post was at 12:28 AM ----------
I've had a reoccurring issue on the unofficial and official builds so far. I do not have the option to use my phone when calling unless speaker phone or a Bluetooth headset. I cannot put the phone to my head and use normally. Is there any kind of option to fix this nuisance. Any feedback is truly appreciated

Every 9.0 ROM I ever flash, I always seem to have the same problem. Whether its dirty flashing, or starting with flashtool, to CMD, and then to TWRP, the same problem seems to happen. After the ROM has settled, audio quality through calls becomes a huge problem. I'm not sure if I'm doing something wrong, but it has been a persistent bug, next chance I get for the next nightly ill send a logcat, kinda cant not since back on stock. I need good call quality for work lol. Either way, thank you for bringing OMNI to 9.0 official

anyone having problems with video playback? videos dont play on instagram, youtube or snapchat. using magisk 18.1 and latest omni 9 rom
edit: nvm, found out that the Google camera fix module for magisk was the problem