- Feb 25, 2012
New one.Will you link the 13 builds here or in a new thread?
New one.Will you link the 13 builds here or in a new thread?
ohhhh, that's really good! Looking forward to flashing!Last 12 release it's here boys. Time to see if i manage to build 13
Availableohhhh, that's really good! Looking forward to flashing!
You can just flash it as usualIs there any way to update from the july build to latest without having to do clean install? I have some banking certificates and tokens installed that are a pain and a half to reissue and install again
It's a thread for PE+ based on Android 12.1PE13 BETA
It's a thread for Sony Xperia XZ1my Pixel 2 XL
Why do we need all this information here? XDGuess we're going back to stock Android 11...
I apologize. I didn't realize this was the PE 12 forum.It's a thread for PE+ based on Android 12.1
It's a thread for Sony Xperia XZ1
Why do we need all this information here? XD
: https://github.com/whatawurst/andro...izationSelector/res/xml/service_providers.xml gives me a 404. Did someone move it? Or is there a typo?Hello,
actually, XperiaParts (together with the reversed CustomizationSelector) does exactly what it is supposed to. For different reasons, we now do the mbn selection and flashing procedure completely independent of the /oem partition. One important reason is, and as opposed to stock, we cannot make use of loading the dynamic overlays for the CustomizationSelector from /oem because the rom isn't using the same signature, so it won't work. There are other reasons, but I won't get into it too much right now.
However, we can add support from other device oem's as well, it just has to be baked into the rom. I won't however do this globally, but rather on a case by case basis. Why? Well, because there are weird instances where this doesn't work and causes all kinds of havoc with the modem.
So please open an issue here if you want a specific carrier to be added (but only if you really know that it works - which I suppose you do): https://github.com/whatawurst/android_device_sony_yoshino-common
I will need a few pieces of information:
1) Which device are you running and want support for a carrier to be added to
2) From which device (and which stock fw) does the support come via the oem in stock
3) What is your exact MCC/MNC (and possibly GID) combination
To be more precise, I will have to do the following:
1) Make sure that that MCC/MNC/GID conversion to a "sim_config_id" is present in the CustomizationSelector overlay in our yoshino repo here: https://github.com/whatawurst/andro...izationSelector/res/xml/service_providers.xml - it should be because this I actually did compile from all available stock fw's (including carrier-specific ones) of all yoshino devices.
2) Make sure that the sim_config_id to config_id conversion is present in the CustomizationSelector overlay in poplar here: https://github.com/whatawurst/andro...nSelector/res/xml/configuration_selectors.xml . It may already be, or it may not. If not, then it should be in that for lilac (here: https://github.com/whatawurst/andro...nSelector/res/xml/configuration_selectors.xml ) since you seem to be using an XZ1C oem.
3) Add the correct modem.conf file, based on the config id to poplar, if not present here: https://github.com/whatawurst/android_device_sony_poplar/tree/lineage-19.0/config/modem . Again, if it's not there, it probably is in https://github.com/whatawurst/android_device_sony_lilac/tree/lineage-19.0/config/modem
and finally 4) See if the CarrierConfig overlay in poplar is present for this carrier or not (here: https://github.com/whatawurst/android_device_sony_poplar/tree/lineage-19.0/config/modem ) If not, again, it should probably be there in the one for lilac (here: https://github.com/whatawurst/andro...rlays/CarrierConfigOverlay/res/xml/vendor.xml ).
There is 13, flash 13...no reason to keep 12.Hi, im having an issue with this rom, im running latest version. So my phone ran out of battery and turned off before i could put it to charge, i connected the charger and tried to boot but now the phone takes a long ass time to boot and when it does i just get a black screen (the screen is on and i can turn it on and off with the power button)... Holding the power button gives me this white Android 9 esque power menu with only options being lockdown, restart and power off. I tried reflashing the rom already but its still stuck like this. any ideas?
Oh nice, does it require clean flash or is it posible to upgrade from this one to 13?There is 13, flash 13...no reason to keep 12.
I'm going to build new 13 release these days if everything goes ok. Wait for that, trust me, its better
Your bank requires you to personally go to bank for token reset? wtf? are you sure isn't possible from their website? Even PosteItaliane allow you to reset token from their website, and its probably one of the worst out there in Italy.Oh nice, does it require clean flash or is it posible to upgrade from this one to 13?
Asking mostly because of the banking apps i use that are a pain to set up due to having to go in person to the bank and stuff for device token reset.
I managed to get it working again by factory reset (thankfully that didn't invalidate my banking tokens) but if its gonna end up happening again then its kinda pointless to keep 12 anyway
Yeah, Argentinian banks are like 20 years behind everyone else. Mine requires to go personally due to "security concerns". I'll give dirty flash a try later then after i do a full app backup with titanium backupYour bank requires you to personally go to bank for token reset? wtf? are you sure isn't possible from their website? Even PosteItaliane allow you to reset token from their website, and its probably one of the worst out there in Italy.
In theory, should be possible to dirty flash without deleting anything, but i never suggest it. Feel free to try by the way.
There is PE 13....flash that. No reason to use 12 anymore. Also, this (12) is not supported anymore.Hi,
I have installed PixelExperience_Plus_Poplar-13.0-20230218-1044-UNOFFICIAL on my Sony Xperia XZ1 G8341.
So far everything is working great except for Android Auto. When I connect my device to my vehicle through USB-C the android auto icon shows in notifications on the device but nothing displays on the vehicle display. It doesn't even show that it's charging on the vehicle display but it does show on the devices. I've tested the Bluetooth connection and I'm able to make and receive calls. So wondering if anyone else has experienced this and if there is a work around or fix. I tried to uninstall and re-install android auto and updated google play service from aptoide but that didn't seem to change anything.
Sorry, I just realized that this is an Android 12 thread and not 13. I'll post to the 13 thread as I have flashed to the new 13 build as I mentioned in my first line.There is PE 13....flash that. No reason to use 12 anymore. Also, this (12) is not supported anymore.
bro how??I'm already flashed it successfully on my SO-01K,it works great,no bug so far.Thanks saving me from docomo!