Related
As we can see that any of custom roms doesn't support volte on our g3 (i'm using osprey), the sim (jio)we use doesn't allow to make a call if volte not enabled , if any of the developer can fix this issue and found the patch for this means we everyone can taste the custom Roms especially the future custom roms (nougat), i can help the developer to check the rom or anything else., send me a pm , best of luck we are waiting..:good:
VoLTE is a proprietary thing, if you can get the VoLTE stuff from Motorola, then we can do something about it
It's not as easy as you think. Developers are already working on it.
This will allow the Jio4Gvoice app to work on most custom ROMs, it isn't true VoLTE and you must go into developer settings and enable Cellular data always active or else you can't make and receive calls on WiFi. It will increase battery drain when connected to WiFi though.
Mr Sabeer said:
As we can see that any of custom roms doesn't support volte on our g3 (i'm using osprey), the sim (jio)we use doesn't allow to make a call if volte not enabled , if any of the developer can fix this issue and found the patch for this means we everyone can taste the custom Roms especially the future custom roms (nougat), i can help the developer to check the rom or anything else., send me a pm , best of luck we are waiting..:good:
Click to expand...
Click to collapse
Refer to below link...
Follow the instructions only..
http://forum.xda-developers.com/2015-moto-g/general/jio-custom-romsosprey-t3484950
acejavelin said:
This will allow the Jio4Gvoice app to work on most custom ROMs, it isn't true VoLTE and you must go into developer settings and enable Cellular data always active or else you can't make and receive calls on WiFi. It will increase battery drain when connected to WiFi though.
Click to expand...
Click to collapse
I know that app will let you call, read my post fully i said we need to enable it on all custom roms
kaustubh_lipare said:
Refer to below link...
Follow the instructions only..
http://forum.xda-developers.com/2015-moto-g/general/jio-custom-romsosprey-t3484950
Click to expand...
Click to collapse
There are a lot difference between using jio app and enbale volte on custom rom, volte doesn't work well on the app also the app doesn't woek if the data turned off
Mr Sabeer said:
I know that app will let you call, read my post fully i said we need to enable it on all custom roms
Click to expand...
Click to collapse
And maybe you should read any of the dozens of other threads here regarding Jio and VoLTE and custom ROMs... it doesn't work, it likely will never work, and we don't know how to make it work because for whatever reason, Moto did not use a standard implementation of VoLTE on this device. And only a few specific devices, the Indian and Brazil models I believe, even have support for it at all in the stock version.
If you think the developers here haven't been trying to make it work, your sadly mistaken. They have worked countless hours on it but there isn't really much more than can be done. The problem is the RIL (Radio Interface Layer) and the modems are proprietary by Moto, and the underlying communication to that layer needed to make VoLTE work require tight, specific integration that we don't have an understanding of because it isn't a "standard" implementation and is not documented. Without knowing how to access this layer and what instructions to send, we can't make VoLTE work on custom ROMs.
Maybe instead of of starting another new thread and asking for the same thing literally HUNDREDS of other people have asked for, you could switch to Linux, install Android Studio, Python, GNU Make, Git, and OpenJDK and start going through code and of a ROM and help figure it out?
Hai i have found some thing will this help to implement on custom rom VoLTE????
I dont know about comand and all soo m just asking...
Can any developer provide volte patch for cm13/14.1, as it was implemented in 14.1 but has been dropped.
pandyag said:
Can any developer provide volte patch for cm13/14.1, as it was implemented in 14.1 but has been dropped.
Click to expand...
Click to collapse
yeah that would be nice but that would disCredit the developer who worked very hard for making VoLTE work on our G3,
so .. it wouldnt be fair asking for such patches.. instead try installing their ROMS if you like..
NOTE: i am using RR with VoLTE 7.1.1 , sorry if my post is mean to you in any way :|
nandakis4 said:
yeah that would be nice but that would disCredit the developer who worked very hard for making VoLTE work on our G3,
so .. it wouldnt be fair asking for such patches.. instead try installing their ROMS if you like..
NOTE: i am using RR with VoLTE 7.1.1 , sorry if my post is mean to you in any way :|
Click to expand...
Click to collapse
No harm.. It was just that we have cm13 snapshot, i could use stable rom with volte.. But i get the point.. Thanks..
I realize that there may already be a thread about this and if there is (and it's not one I started) then please link it here so I can go read it. I've read just about every thread on this topic and I still can't find the answer I'm looking for:
In essence this phone is perfect in every way that matters to me...except for the fact that I can't enable Wifi-Calling. I have tried using the "Wifi-Calling" app in the Google Play Store, I have also tried modifying the setting (wfc_ims_mode=2) in adb, but still nothing. I guess part of my issue is that I can't understand how, if this ROM (Funtouch OS 4.0) is based on Android 8.1 and Android 8.1 supports WiFi-Calling...why this ROM does not?
Anyone with any ideas I welcome your feedback. Also, there are a series of ADB global settings that I can seem to find out what they do. Anyone have any ideas? Could any of these be the key to getting this thing working on this phone?
vivo_wifi_2_mobile_enabled=0
volte_vt_enabled1=0
volte_vt_enabled2147483644=0
volte_vt_enabled=1
wfc_ims_enabled1=0
wfc_ims_enabled=1
wfc_ims_mode=2
wfc_ims_roaming_enabled1=0
wfc_ims_roaming_mode=2
Thanks
M.
Hey,
over the last few weeks I've used my Christmas vacation to start working on the Z18 again. However since work is coming up again soon, I won't have that much time (and nerves) for working on this properly until the end of summer probably.
That's why I want to share my codebase with you, so maybe someone can pick up where I left off (and really, it's nothing big I did. I merely set up the device tree and made it compile more or less. It doesn't boot because of avb and I'm not aware of any way around that)
The device tree can be found here. It's still using a prebuilt kernel but I'll work on fixing the kernel source to a compileable state next.
If anyone wants to get involved, help or pick this up, feel free to do so. The community and I are always happy for help.
Explanations of what the next steps would be can be found below.
Again, do not install this unless you want to softbrick! It's not useable at all and will currently fail at boot verification!!
So what's next?
Fixing avb2.0: This isn't an easy task. How I understand, it either needs the official keys or I failed at signing the build with test keys from LineageOS. Either way this is the first step and top priority so the device boots again at least
EDIT: It seems that https://github.com/rockchip-linux/tools/tree/master/linux/Linux_SecurityAVB might be of some use (given that youyim123, the guy who also did the TWRP for Z18 starred this project). However I don't speak Chinese and putting my device in the hands of Google Translate is risky.. so anyone willing to translate, I'm open for DMs or anything
EDIT2: avb is working, so we can move on to breaking our system now (yay)
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Zahidul Hasan said:
Hi, Its a long time i am waiting for a suitable rom to be installed in my Nubia Z18. Can you tell me when this rom can get out? Your effort is highly appreciated.
Click to expand...
Click to collapse
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
curtisy said:
Sorry but I can't give you any ETA on this. I'm working on it in my little free time and I'm not even sure what I'm really doing with this. The source is all on the GitHub repo I linked in the OP though, so if you're hesitant and want to get a working ROM, just get involved. It's really not that hard, all it requires is time, patience and lots of googling for weird error messages and further features you want to implement.
You can mostly follow the guide here https://wiki.lineageos.org/devices/bacon/build just replace the bacon command with nx606j-eng and you're good to go and build this yourself. Maybe you can figure out avb since I can't do it by myself, so any help is appreciated.
Click to expand...
Click to collapse
Zahidul Hasan said:
Dear Sir, Thank you so much for your reply. Last day i tried to push a TWRP from here TWRP installed, but failed to install any gaapps. although process said success.
Click to expand...
Click to collapse
Yeah, that thread, if most of the development threads on the Z18 so far, was made by me. I also mentioned in post #3 that flashing Gapps doesn't seem to be working and I was trying to ask the GApps team for help. I never got an answer though, so I stopped looking into this and instead focused my effort on providing a working Lineage build for everyone. The result of that is this thread here
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
sky104hk said:
Hey curtisy, are u building lineage OS forZ18 right now?
im chinese and can help to test this rom if need tester, I've a Z18 on hand rite now and still finding a solution to solve the "GAPP" problem
try to flash GAPP package but no luck!
hope the Lineage can release soon for testing~tks!
Click to expand...
Click to collapse
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
curtisy said:
I'm not building it right now. As I said, the project is pretty much on standby for anyone to take it where I left it but I'm still working on it sometimes and try to get it to work. The big issue is that the Z18 uses avb2 which I'm not sure how to bypass and which is also why the Lineage I built will not boot correctly. I don't want to seem rude saying this over and over again, but rather than testing, it would help if I had some more people to get involved. Just download the source and follow the instructions I mentioned in post#4. Progress will be much faster if there was a team behind this and not only one guy who doesn't know what he's doing most of the time. Also getting support in the Lineage IRC is tedious because I can't be online 24/7, so having some more people nag about avb2 there would also be of huge help.
And when there finally is something to test, not only will you be satisfied by your own achievement, but you can also be the initial tester since you built the ROM yourself.
PS: The Gapps issue is probably because of avb2 as well, however I'm not too sure about that
Click to expand...
Click to collapse
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
sky104hk said:
OK I understand your situation, probably not as many ppl own this phone at all...there are many ppl doing developement in Oneplus 6 which I actually own that phone, the Z18 is actually my fd, therefore I cannot keep the phone long...just wonder if there have more ppl involve to this...the "avb2" I'll check to see if anyone on the net doing this, haha! the only solution is more developer involve to this phone!
Click to expand...
Click to collapse
As a quick update for everyone here as well because the discussion has somewhat shifted to the TWRP thread I worked around avb now. I also have a system.img but it's not working as of yet. If you want to get stuck in a boot loop, feel free to ask here and I'll attach the files in the OP for you to try and modify. Without building from source, there's probably not that much you can do though.
Hint: try booting phh-treble GSI first.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
curtisy said:
Thanks! Going to try that later but out of curiosity, isn't the reason this phone doesn't have google services out of the box that it wasn't certified by google? If so it's not treble compatible either right? Or am I missing something?
Click to expand...
Click to collapse
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
j1505243 said:
An uncertified device can be freely Treble compatible, so it's really worth to try. Remember to join the Telegram chat of phh-treble if you happen to need some quicker response.
Click to expand...
Click to collapse
Awesome. Thank you for the heads up! Might be worth to invest some time in this again then.
j1505243 said:
Hint: try booting phh-treble GSI first.
Click to expand...
Click to collapse
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
curtisy said:
Alright, I tried and I don't think it's working. I get stuck in a bootloop again which repeats every few seconds.
Since I got Lineage compiled, wouldn't it be a better idea to just get that working and be done with it?
Any help is much appreciated!
Click to expand...
Click to collapse
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
j1505243 said:
Booting non-GSI will only be tougher :/ Capture deep level logs and inspect that. If you need help, join a phh-treble chat somewhere.
Click to expand...
Click to collapse
Yeah that's actually the same point I stopped at with Lineage. Got it to boot to the Nubia logo, captured logs and I can see some weird errors. But getting replies on IRC is a pain, especially if I can only be online for 2hrs a day. That's why I had hoped someone would pick this up but to no avail. Guess I'll have to look into it again and experiment.
Thanks for your help so far! If there's any more tips you want to share, I'm always open for them
furiousjay said:
Hello curtisy, I wish you good luck with your work on the Nubia Z18. I'd love to help you, but unfortunately I have no skills at android developing. Anyway... in case you will get LineageOS to run, I'd be very happy to post an instruction for the installation on my website chinahandys.net. Liebe Grüße, Joscha
Click to expand...
Click to collapse
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
curtisy said:
Hey, sure thing I actually know the site well and got the idea of getting a Z18 from your site. In case you know anyone that might be able to help with logs or anything, I'm always open for suggestions and help.
As a general rule of thumb, so far the process isn't exactly easy because it requires proprietary software. The issue is with boot verification, so to get around that, I rooted my phone with some Chinese Windows application (still trying to reverse that to get the actual keys..) then I could start flashing. The process is tedious though as every failure means reflashing the original rom as well as running the root tool again. I'll try to make it simpler and cross platform once the rom actually works. But it's still a long way to that point.
Click to expand...
Click to collapse
Unfortunately I personally don't know somebody who has the skills to support you. I have included a call for support for your project in our review.
Here was a Guide. Someone said people don't care about Me or My Work so...
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
nolihowell said:
does it require an unlock bootloader?is it prerooted?does it have drm keys? sorry for the questions.
Click to expand...
Click to collapse
Yes, You need to be unlocked, otherwise is there no chance to flash with fastboot. Besides the rooting of the Kernel is everything Stock. Everything works so far even with GSIs
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
nreuge said:
Where did you get the Customized EU 55.1.A.0.748 J9210 ?? I does not appear on XperiFirm.
Click to expand...
Click to collapse
My Bad, it is the UK one... I'm also still waiting for customized EU which was always My Choice for Xperia Sources and Development. I'm currently working with GSIs on My Xperia 5 but think i will Release some Stock work soon since i prefer Xperia Android actually over AOSP...
Users will be able to use any Base Firmwares (Android 10) for it but i will personally Test on Custom EU :fingers-crossed:
@Miustone will you be releasing a boot.img for the latest security patch?
fcb13 said:
@Miustone will you be releasing a boot.img for the latest security patch?
Click to expand...
Click to collapse
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Miustone said:
Just downloaded J9210_Customized EU3_1320-1208_55.1.A.3.49_R2B. I will release a Update after getting it running on My X5 this Weekend alongside with a Magisk Module Update for XPIXELERIA https://github.com/Miustone/XPIXELERIA
BR
Click to expand...
Click to collapse
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
charlatan01 said:
@Miustone Sorry to bother you here, but I am struggling with patching the Xperia 1 .sin boot image with any current version of Magisk. I've tried a few versions but they all fail to create the image from the .sin file. Any help you can provide is greatly appreciated!
I should add, I was trying to use these instructions: https://forum.xda-developers.com/xperia-1/how-to/xperia-1-root-guide-t3938304
Click to expand...
Click to collapse
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Miustone said:
Just read the first Post of this Thread and You will get everything You'll need.
EDIT: Since You just need a .img File for Magisk is there no need to share it with Me actually. Just patch it in the Magisk Manager App and flash it with fastboot afterwards.
Click to expand...
Click to collapse
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
charlatan01 said:
Ah, okay. Thanks. One last stupid question.. for the firmware, does it matter if the img file comes from the Android 10 firmware? I am planning to flash my Xperia 1 with PE, which is still Pie.
Click to expand...
Click to collapse
Prefer a newer Base Firmware over a newer GSI. A Android 9 GSI will run better with Android 10 Kernel as vice versa. Pie will be no Problem if You run Android 10 Vendor and Kernels. Happy flashing! :fingers-crossed:
EDIT: There are also PE Android 10 Builds out there... https://forum.xda-developers.com/pr...iscussion/gsi-expressluke-built-gsis-t4003457
help me
hi i need a boot.img for my xperia 1 j8170 please help me 10 (55.1.a.3.107)
This method has always been magisk module not friendly. audio compat worked. But once i through more at it it bricked device and had to reflash with new flasher
Hi
Can you please patch this file for me (Device = J9210 Dual | Firmware = 55.1.A.3.149)
boot_X-FLASH-ALL-A2CD.7z
Kind Regards
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
BuyXRPnow! said:
After I get root, can I completely deGoogle my phone? Since there is no Lineage OS for XPERIA 5, can I manually get rid of all of Google's stuff?
Help is greatly appreciated.
Thank you.
Click to expand...
Click to collapse
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Miustone said:
Yes You can. But You can also install LOS 17.1 from the GSI Forums. I also did Instructions for flashing GSI Treble ROMs in the Xpiera 5 Guides Forum :good:
After that You may want to have Magisk to pass safetynet and to install MicroG or NanoDroid to get everything working. I'm actually running PHHs AOSP with My SOM Module and it's one of My Favorites so far. You may also like Havoc OS Official which also comes as no Google Apps Version. You can do the same on Havoc like You can on LOS but + endless Costomization
Click to expand...
Click to collapse
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
BuyXRPnow! said:
I really appreciate your reply, but I am a complete noob and all this is extremely overwhelming.
"PHHs AOSP with My SOM Module" - this alone gives me terrors
I know nothing about these things but I understand you, it's just everyday business for you coz you are a developer. I tried reading your guides and there are so many things I don't understand. I also was traumatized by rooting my S10, which I sold and got Xperia 5 instead. I read here people said I will permanently lose DRM keys after rooting. This is my biggest problem. With S10 I knew I could go back to stock and not worry. Here, if I go all the way and deGoogle my Xperia and it doesn't work the way it should I won't be able to go back and on top of that selling it will be harder and I will lose money since not everyone is willing to buy a phone which can't get Netflix and other DMR-dependent garbage.
Maybe I could sponsor you to help me flashing all the stuff. I just don't know if it's a crazy idea. Also, asking you to rewrite your guides for idiots like me is asking too much, given how busy you are.
If you have some advice I would greatly appreciate it.
Click to expand...
Click to collapse
First of all. Good choice to get rid of a Samsung Device Like i did with My S9+! Sammy is pushing Android into a Appleish Edge that shouldn't exist...
Just like Huawei. But different Story...
Out of My View with Years of expierence with different Brands is SONY one of the Most supporting OEM in Views of Android Development besides the Fact they Always excluded some functionality of the included Smartphone Hardware. For example:
-Xperia Z1 lost the Complete Camera Function after unlocking (Got fixed with a Update later after Claims from Customers) and lost Display enhancements + Camera Noise reduction
-Xperia Z3 lost the Vibrant Display Colors after unlocking (Aka Bravia Engine) which ended Up in washed Out Colors and was still loosing Noise reduction
-Xperia XZ Premium still loosing enhancements after unlocking plus the loss of Camera Noise reduction
And now the Xperia 5...
Sony used for the First Time Samsung Sensors for the Cameras instead of own ones with High Resolution. So no Noise Reduction needed anymore. Finally OLED, so no washed Out colors without Display Enhancements.
I'm quite Happy with this One since you don't loose Something Essential. Besides that have i Always Managed since the Z3 to fix almost all Problems on Xperias with native Android functionalities that is used on other Devices. Eg. For the Display, Audio, Camera, Mics and so on.
And thats the final Point. While older Devices Had the Chance to Backup and restore the TA Partition or even to use a Recovery on locked Bootloader (I've also worked with this for some Time) which allowed to make Your Device Complete Stock again. We don't really have that Options anymore. So i would say an Unlock is a final Step. But to be honest. I sold many Devices claimed as unlocked and rooted and it hasn't Cut the Price at all. And even if You Don't. I don't think a normal Person will See a difference after unlocking and relocking
Is it worth it? For Me a clear Yes! I never looked back after unlocking any of My "Hundreds" of Devices i used. Magisk and GSIs alone are really worth the Unlock Out of My View actually. You can do so much with Android and it finally doesn't feels Bad anymore on Xperias. My SOM (Magisk based ROM (Systemless-On-Memory) will do a lot of awesome Things with Our Xperias (1 & 5). Another good Reason maybe...
It could be smart to make a Video which explains how to get My Work on Your Xperias. From unlocking to Flashing... Would really like to do that after some preparing for it. Possible that there are a lot of People who don't even know about Bootloader unlocking so it really could be cool. I already did some Videos in the Past; https://www.youtube.com/user/TheMarius517
Think i got a bit lazy since the Software alone takes so much time These days. But i will do My best to get People in Touch and to Show everything step by step.
Lot of Text but Hope i made Your decision to Unlock or not easier... Don't think about the Future of Your Device. Think about what You want from it right now...:good:
Btw. Not Sure but You could try ADB to remove Apps. But idk. If IT IS possible with Google Apps (Locked Bootloader Method)
All the Best,
Miu
Thank you! You are a hero. I will be waiting for your updated guides and possibly a video for noobs. Appreciate your time!
Peace.
Optimized the Thread Structure and Instructions. Optimized Thread Title. Updated Boot Image / Kernel to latest EU .149
If i try to connect my bluetooth headphones on pixel experience they dont work can someone tell me how to fix this?
Edit: i found the solution if you guys are having problems like me make sure you have the "Use System Wide BT HAL" checkbox enabled on the Misc page of Treble App. If not, enable and reboot.
elosanta said:
If i try to connect my bluetooth headphones on pixel experience they dont work can someone tell me how to fix this?
Edit: i found the solution if you guys are having problems like me make sure you have the "Use System Wide BT HAL" checkbox enabled on the Misc page of Treble App. If not, enable and reboot.
Click to expand...
Click to collapse
How did you install pixel experience rom on Samsung A22 5g model?
Rifath836 said:
How did you install pixel experience rom on Samsung A22 5g model?
Click to expand...
Click to collapse
I used a GSI
Offtopic but your post made me realize it was a treble setting behind why V4A or any other audio mods weren't working. This was a problem that confused me for weeks. Thank you.