yashsingh1/xdaforums huggingface dataset:
[Sony Xperia XZ ROMs, Kernels, Recoveries, & Other ] jerpelea:
All build guides are updated with the Security updates

https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/

Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.

https://github.com/sonyxperiadev/bug_tracker/issues
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
Sony Mobile is committed to supporting the open developer community, and one way to show this is by publishing parts of our code as well as selected tools developed by our internal developers.

For some of the Xperia™ devices, we provide Android™ Open Source Project (AOSP) device configurations on GitHub. This means that the software will be open for you as a developer to use and contribute to. This is a way for us to support the open Android community, and it is also a tool for us to facilitate and verify contributions to AOSP.

If you want to build AOSP for your unlocked Xperia device, you find all the resources you need in the sections below.

https://developer.sony.com/develop/open-devices/

Unified 4.4 kernel sources

https://github.com/sonyxperiadev/kernel

Project git

https://github.com/sonyxperiadev/

Bug tracker

https://github.com/sonyxperiadev/bug_tracker/issues
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
Now you can build the latest Android with the latest 4.4 kernel
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] aquaboy11:
Thanks for all the hard work and keeping the resources easily accessible and up-to-date. I will be using them for sure :).
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Sepo190:
Thank you for providing these resources and keeping up development for the devices they support. I notice that the dynamic resolution switch in the extended settings doesn't work on android 8.0 or 8.1. Are there any plans to add support for this back in at any point?
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
we are working on the issue

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] gaijin1%:
It says here that we can change the display to native 4K at 60hz or 1080 at 120hz with your AOSP https://androplus.org/Entry/4577/

The previous comment says it's not working in 8.0 or 8.1, but I don't see an open issue about it in your bug tracker. Was it fixed?

If it wasn't available for 8.0 and 8.1, what version is it available on?
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] 喂喂金:
I hope los and rr now.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] iArvee:
Just to be sure, I opened an issue in the bug tracker for it.

[MENTION=359497]jerpelea[/MENTION], if you would like the issue to be closed, I'll happily close it.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
we are working on it

please leave it open
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
Vendor v11 is out

https://developer.sony.com/develop/open-devices/latest-updates
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Moarten:
Is there a changelog or something like that? I had issues with these binaries and AOSP builds from last week. A few days later I noticed a commit that mentioned these new binaries, but after that the "Fingerprint" setting is gone, so I'm now using a build of 08-03-2018 with the V10 binaries.

To be honest, I haven't tried a factory reset nor flashing userdata.img, so when I get home I'll update the repo, build a new version and do a full reset.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] lebigmac:
[MENTION=359497]jerpelea[/MENTION] why Sony remove the FM radio feature on all modern Xperia phones? Why??? The hardware capability is there. Why you cripple the phone on purpose?

Can you please give a logical explanation about this issue?

When will Sony give me back this feature?

And why Sony block the Displayport alt mode? Again you cripple the phone on purpose.

And why I cannot root my phone without losing DRM keys? How to backup my DRM keys??? Please tell me.

I am waiting for answers but my patience is slowly running out.

Thanks Sony for being so user friendly.

If Sony don't fix these issues soon I will never buy Sony products ever again and I sell my Xperia's, my Playstations, my Walkmans, my Sony TV's and all my other Sony products. And I tell all the people that I know to do the same.

It's your choice Sony.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Bitti09:
Nice try but Sony will ignore it like every other vendor.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
the fingerprint has been fixed and now it is working as it should (stability issues are fixed)

please update your device with the latest Sony Sw before flashing AOSP

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] lebigmac:
No. Some manufacturers actually care about their users. Not all smartphone manufacturers cripple the phone on purpose the way Sony does it.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
Unfortunately I can't answer those questions since I am just a developer

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Moarten:
Great, thanks. I've returned to the stock roms now, but will try AOSP again soon.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Miustone:
jerpelea... Remeber well from the early FXP Times back on My SONY Devices. Can't wait to try out XODP after Years without SONY Devices. Thanks a lot for still contributing that much to the Xperias! True Hero!
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] loukky:
i think you should support dual sim cards,i flash aosp for g8142 but it cant use 2 sim cards
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
I am using a XA2 Dual sim with Android 8.1 and it works fine

Regards

Alin
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Lawliet918:
any way you could support RAW in camera2 api so we could finally try google's hdr+?
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] loukky:
where is your rom download from?or buliding by youself?
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] No-New-Phone:
I do have a more general question. How does Sony decide to put a device on the open device list? For my current oneplus x device, it was as easy as to click the "unlock bootloader" button in developer settings. Done.

The new xz2 compact for me could be the perfect piece of hardware, small body, best processor. And I could live with Sony software for about a year maybe. More precisely, my question regarding open devices heads to the following direction:

- is this a random decision?

- a planned decision (x months after availability)

- immediately when official support ends

Maybe you can try to give us some insight on the matter, or forward the questions to the people involved, as it's very unlikely that I will buy a piece of hardware without knowing to own it completely.

Thanks!

Gesendet von meinem ONE E1003 mit Tapatalk
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] amakuramio:
any news about 120 hz?
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
For user security dm-verity and File Based Encryption are enabled by default

Please keep them enabled for all user builds

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
Hi,

Open Devices Program suports all devices built on a Qualcom SOC and XZ2 devices will be added soon.

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Lirannl:
Hey, I heard a lot of references to 120hz. Can the display actually run at 120hz on AOSP? I'm thinking of flashing AOSP soon.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] No-New-Phone:
As far as I can see in development threads of the xz1c, the biggest issue seems to be the handling of the camera once the bootloader is unlocked.

Do you have (or can you get) any more information regarding the camera stack? Of course sony has any right to protect its software, but adding devices to the open source program without having access to an essential part of the hardware seems to be a major issue. So, will this become available, as for the xz1c and / or xz2c?

Gesendet von meinem ONE E1003 mit Tapatalk
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] ponytojas:
[MENTION=359497]jerpelea[/MENTION] Since latest changes for dm-verity and force encryption, there's no way to get any build booting
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
I tested both Android 8.0 and Android 8.1 and they both boot fine

please update your odm partition with the latest vendor binaries

Regards

J
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] shoey63:
[MENTION=359497]jerpelea[/MENTION]

getting this error when compiling with latest android-8.1.0_r35 branch

vendor/qcom/opensource/camera/QCamera2/HAL3/QCamera3HWI.cpp:11560:14: error: use of undeclared identifier 'af_value'
if (atoi(af_value) == 0 && mCameraId == 0) {
^

Are you able to replicate it? Why is there a problem with <af_value> and how can it be fixed?

Please look into it when, and if you find the time.

Edit: it's been fixed upstream

The faulty line is now

if (m_bForceInfinityAf == 0 && mCameraId == 0) {
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] jerpelea:
All build guides are updated with the Security updates

https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/

Here is the list of all known bugs. If you find bugs you can always open a ticket in the bug tracker and we will check it ASAP.

https://github.com/sonyxperiadev/bug_tracker/issues
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Osleg:
After lots of tinkering I was able to build and flash AOSP 9.

It seems to work fine, the main question tho is where to get compatible GApps? Tried opengapps project, after flashing the phone doesn't boot anymore
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] shoey63:
Open gaps modifies system files therefore you need to disable dm-verity.

Flashing Magisk will do it for you.

So procedure is

- Flash images

- Boot to TWRP recovery

- Factory reset

- Flash gapps

- Flash Magisk

- Reboot

Do not boot to system and install gapps after. Gapps must be installed before first boot or after a factory reset.
[Sony Xperia XZ Premium ROMs, Kernels, Recoveries, ] Arzumanyan:
Anyone can answer the 120 hz question?
[General Topics] simpan:
Sometimes I get one and it's not very nice.. I'd like to get rid of it (my todayscreen is now 1-2 pixels too high..)

Is it possible to disable the vertical scrollbar in today screen, maybe a registry setting?
[General Topics] tmknight:
http://www.google.com/custom?hl=en&...0&ct=result&cd=1&q=vertical+scrollbar&spell=1
[General Topics] simpan:
Thank's. I already tried that, didn't find anything. :(
[General Topics] duprade:
There's a program out there that allows you to "shrink" the contents of your today screen and I can't remember what its called right now..

maybe someone else can enlighten us.
[General Topics] nuelo:
I know what you are complaining about. The today screen often fluctuates in length primarily due to Calendar, Tasks, and Email changes. I find it hard to have a nice background image because of this. But I think the market is shifting away from the Windows Today screen into a more finger and eyes friendly interface (examples for that are PointUI, SPB MS2.0, etc.).

I personally think that if your scrollbar is appearing then there is a reason for it. I think you may have too much clutter and you should clean up and fix the problem instead of removing the "warning sign". Or use one of those friendly new GUIs that are increasing in popularity. My choice has been SPB Mobile Shell 2.0.
[General Topics] txisko666:
Si, has de probar donde tienes el deco de la plataforma y asegurarte que no es un cable directo desde la antena hasta el deco, de ser así has de propagar la señal de satélite al resto de tomas de la vivienda. El Engel si no voy mal tiene entrada y salida de antena para poder tener dos decos con una antena pero la alimentación de lnb solo tiene que estar en marcha en el que se conecta directamente a la antena. Molesta lo que quieras que para eso está el foro.

Enviado desde mi Aquaris M5.5 mediante Tapatalk
[Xiaomi Redmi 3s Themes, Apps, and Mods] ankshious:
For those who are very much fond of FM Radio like me.:D

I have already go through into many Roms for just FM Radio, some Roms have this App but they are not stable. Some roms are stable but they have not this App.

So I decided to dig out this problem and I got success finally.

Question: What I did?

Answer: I extracted the FM Radio folder from a rom which already had this App. Then pasted this App folder in /system/priv-app folder and gave proper permissions. Most of you already know about permission.

But for a noob, here is the permissions setup.

1-For folder it should be rwx-rx-rx(755)

2-For files it should be rw-r-r(644)

That's it.

Typical yet effective.

Reboot and enjoy.:fingers-crossed:

Tested by me and it is working 100%.

Any suggestions are welcome.

Note: For permission, use any file explorer with root access. Be careful with permissions. I will not responsible for any damage.

Just extract the attached zip and do the above steps properly.

https://drive.google.com/open?id=1dzSKd_BZswm4u9dZBds_8SqdiN57pnkt
[Google Pixel 2 Questions & Answers] Djtrip83:
Hi everyone

More than a question, I wanted to share some steps I plan to follow to apply the monthly system update and check I am on the right track. I had a Google Pixel 2 for a few months and I am learning more about the model every day.

Previously, I tried to follow different procedures found here on XDA such as applying OTA with boot images temporarily restored but I ended up with a bootloop not event TWRP could fix since all data was encrypted.

Objective:

Update the system to the latest Pixel 2 update (in this case Feb 2018) avoiding bootloops or bricks

Current Status:

Pixel 2 Walleye with Jan 2018 update

Rooted systemlessly with Magisk

No Magisk modules installed

/system modified since I have AdAway and other apps

No BusyBox installed

No Custom Recovery installed

Proposed steps:

Uninstall Magisk completely

Remove root apps from Device Admin (such as Greenify, Tasker, etc.)

Download latest factory image from Google

Extract the following from the image zip:

bootloader.img

radio.img

boot.img

dbto.img

cache.img

system.img

recovery.img​

Restart phone into booloader

Fastboot bootloader.img

Reboot the bootloader

Fastboot the following commands in this order:

radio.img

boot.img

dbto.img

cache.img

system.img

recovery.img​

Reboot phone

Install Magisk by patching boot

Re-run root apps (AdAway, etc.)

Renable root apps as Device Admin (Tasker, Greenify, etc.)

Is the above safe enough to avoid bootloop and also not lose apps and data installed?

I am aware any modifications to /system will be lost.

Have a look, let me know if on track, and if you want, give me your blessing.
[Google Pixel 2 Questions & Answers] razrlover:
Yesterday I used Dueces bootloop recovery script to update without losing anything.

I had magisk + TWRP installed

Download full update not OTA, extract to program tools directory or where you keep your goodies. Pull all factory update in folder with deuces recovery script.

From stk rooted ROM reboot bootloader,

Run dueces script from bootloader

After finished script No to format data

Reboot system when done.

From there you should be good to go, you will need to repatch but image in magisk and all that but i lost no data and had no issues

So I was on 1.171019.019 installed 1.172019.21 from fastboot with script and wiped nothing and lost nothing..

** My directions are probably incomplete so follow his instructions in his OP.
[Google Pixel 2 Questions & Answers] nolimit78:
This has been discussed all over the place on the forums but you're over complicating the update process. Here's what you do:

Download the latest Pixel update
extract the update in your ADB folder on a computer
reboot to bootloader
look for the flash-all.bat and remove the -w at the bottom of that code, Save that file (the -w is what causes the device to be wiped)
run flash-all.bat
once that finishes you can fastboot boot twrp.img
it won't decrypt (Feb update broke TWRP decryption) but go read only and get into ADB Sideload mode
adb sideload kernel.zip
adb sideload magisk.zip
reboot

This is what I've done everytime (minus the adb sideload) and I have had zero issues. No loss of data being the biggest concern. Did this using the march update just yesterday and now I'm good to go.

It is worth saying when you start trying to flash (roms, kernels ect..) and you get a little crazy, Dueces Bootloop Recovery script is 100% something to have on deck if something /does/ go wrong.
[Google Pixel 2 Questions & Answers] Rukbat:
kernel.zip from where? The OTA? One you saved with TWRP on it?

I currently have TWRP and Magisk (default - nothing changed yet) installed on the February update. Is this going to be a monthly thing - flash the update, reinstall TWRP, reinstall Magisk? Not a complaint, just want to know what I'm doing. (Samsung, for all its faults, was a little easier after 6 years of not even having to look at what I was doing. I'll get comfortable with the Pixel, but this is my first update with TWRP and Magisk installed - it did the February update almost before I could read the screen.)
[Google Pixel 2 Questions & Answers] nolimit78:
The kernel.zip is whatever kernel you'd like to use (flash or elemental) but it's not required. I just rename for shorter commands for ADB Yes, you've hit the nail on the head. If you're going to be stock/rooted, you'll have to do this every month to stay current.
[Google Pixel 2 Questions & Answers] Rukbat:
And we're still waiting for Dees_Troy to figure out how to add decryption back to TWRP, so it's reinstall everything - including fingerprints - every month. Oh, well. (Hey, no pressure, Dees_Troy - I appreciate just having TWRP on this thing.)
[Google Pixel 2 Questions & Answers] nolimit78:
In my process outline, you don't have to remove fingerprints.
[Google Pixel 2 Questions & Answers] Rukbat:
To boot to TWRP to handle files that you already copied to the phone? TWRP doesn't decrypt the names any more, does it? So all you see is garbage (encrypted hash, I guess). If I want to restore a backup I have to remove the PIN, which seems to remove the fingerprints. Or are you saying to restore the PIN and the fingerprints are still active?
[Google Pixel 2 Questions & Answers] nolimit78:
No, this is only to apply the update and flash a custom kernel and magisk

No, it sure doesn't. This was caused by the Feb Update

Yeah, to do anything in TWRP (outside of ADB Sideloading) you'll need to remove the PIN.
[Google Pixel 2 Questions & Answers] Rukbat:
And evidently something else. I removed the PIN, updated, and the phone's been sitting on the G screen for half an hour. So I rebooted to the bootloader, locked it, and now I'm flashing 021. I have a bad feeling that I'm going to be stuck.

---------- Post added at 05:09 PM ---------- Previous post was at 04:10 PM ----------

As I feared. So I followed Google's instructions to flash the factory image. It went fine, until I got:

Then it wrote the system, but

It never reboots. If I reboot at that point, I get the recovery screen.

If I reboot into the bootloader and lock it, I get the bootloader with "ERROR: LoadImageAndAuth Failed: Load Error" at the bottom.

I was able to load twrp.img and use it to sideload twrp.zip, but that still doesn't get me back to Android. I tried b ooting into A and B and got the same result - TWRP.

What next? Is there a fix, or does this one have to be replaced also?
[Google Pixel 2 Questions & Answers] ajrty33:
Oh my gosh. Stop sending your phone back.

Update your platform-tools. Change cables. Change ports. Use the search function.
[Google Pixel 2 Questions & Answers] Rukbat:
I'm not exactly new at this. Different cable, every USB port (including a 2.0 port, new download of both Google's driver and adb/fastboot, a new download of the firmware (and the sha256 is correct).

The next thing I'm going to try, as soon as I finish eating, is another computer. If that fails, and I'm pretty sure it will, I'll call Google tech support. Since it happened twice during an OTA, on two different phones, I may be able to get someone who knows how to feed the firmware into a nearly dead phone. I'm just looking for ideas I haven't had, when I post here. I'm about out of ideas. Again.
[Google Pixel 2 Questions & Answers] Rukbat:
Evidently some computer manufacturers don't exactly build what they claim to build. My desktop has 2 USB 3.0 ports (which I already knew wouldn't work) and - supposedly - a USB 2.0 port. Flashing the firmware on the "2.0" port didn't work. Evidently it's not 2.0.

So I resurrected an old Windows 8.0 laptop. I think it has 0 cores running at 0MHz - it's SLOW! But it finally flashed the February update. Tomorrow (it's going on midnight here, and the phone is still downloading the last Google backup) I'll update to March.

Madness - but at least I have a working phone, and know how to get it working again if I need to (and have a few lifetimes to do it). And I have another laptop in the closet that actually works. That one gets resurrected next.
[Google Pixel 2 Questions & Answers] nolimit78:
So what you're experiencing isn't new or an issue with your phone that you'd need to RMA the device. It's a learning curve because the A/B partitions are a completely different beast compared to older/other Android devices. Use Duece's Bootloop Recovery script to fix your problems. It'll work and you'll be good to go. Just be sure not to wipe. During my testing, I had to figure out all this myself and was /REALLY/ close to RMA'ing my device. But I continued to research and plugging away and found that that script helps users in your situation, as I've been in that very same situation myself.
[Google Pixel 2 Questions & Answers] Rukbat:
No, it's a learning curve because, even though the USB ports on the back of the case are labeled 2.0, and have black plastic, they act like 3.0 ports with a Pixel 2. Doing exactly what both I and Google tech support did with the supposed 2.0 ports, on the aging laptop with real 2.0 ports, solved the "problem" that both Google and I were having. The phone was fine, what we were doing was right, the Acer desktop has a documentation error, and that was the only problem. (Even Google didn't seem to be aware of the USB 3.0/Pixel2 incompatibility, which many of the people in the Pixel 2 forums at XDA are.)
[Google Pixel 2 Questions & Answers] Telperion:
Follow the guide in my signature, it works, and you don't have to muck around with removing PINs and fingerprints.
[Google Pixel 2 Questions & Answers] Rukbat:
Thanks for paying attention, but what really bothers me is having to remove the fingerprints in order to do a backup or restore in TWRP. I'm used to just booting to it and flashing a backup if I need it for some reason. If only Google would leave the fingerprint file alone when we went to None for the lock screen, just putting the PIN back would bring the fingerprints back. There's really no reason to delete that file. Maybe delete individual prints at the user's discretion (like changing passwords every once in a while), but not delete the whole thing just because I want to back up my current configuration.
[Google Pixel 2 Questions & Answers] ashokabs:
What I do is uninstall Magisk. Then do the normal update from the update page in settings. After this I copy Magisk zip file to a usb drive. I boot into twrp using ADB. It doesn't decrypt but that doesn't matter. Use the USB as storage and install Magisk zip file through TWRP. Reboot and you are done updating with Magisk installed.
[Google Pixel 2 Questions & Answers] Rukbat:
That sounds like an easy way of doing it, but doesn't the update balk at the patched boot file? Mine balked at something yesterday, which is what started all the mess yesterday. (Or does Magisk have a "remove and replace the boot file" button?)
[Google Pixel 2 Questions & Answers] Djtrip83:
Thank you for the feedback!

One question I had for a while: flashing the data.img wipes what? Doesn't it wipe the apps you have installed?