Related
Guys,
Recently, I am struggling between using cm12.1 and stock .222 firmware foe my Z because they both have something I desire ( system ui and camera for .222 and cm theme engine for cm12 ). My question is can they exist on my phone at the same time? If so, what ROMs or addons should I apply to my phone?
Many thanks!
(Sorry for my poor English)
I think you should try xposed + addon Xtheme engine or HKThemeManager.
well83 said:
I think you should try xposed + addon Xtheme engine or HKThemeManager.
Click to expand...
Click to collapse
I have tried those but none of them works om my device…
Try RRO layers
Some apps can be themed,status bar and navigation bar on stock deodexed rooted
No, it cannot. And neither can RRO Layers (fully). Both theme engines depend on native code changes, not just Java/Smali changes, which means an .so file must be modified at source, which means Xposed (or any stock mod method) will not work - firmware needs to be modified at AOSP level and compiled from scratch. And since we don't get full Sony source code, it's practically impossible. Not feasible is more accurate.
Source: My own research.
[/thread]
Sent from Xperia Z via Tapatalk
CosmicDan said:
No, it cannot. And neither can RRO Layers (fully). Both theme engines depend on native code changes, not just Java/Smali changes, which means an .so file must be modified at source, which means Xposed (or any stock mod method) will not work - firmware needs to be modified at AOSP level and compiled from scratch. And since we don't get full Sony source code, it's practically impossible. Not feasible is more accurate.
Source: My own research.
[/thread]
Sent from Xperia Z via Tapatalk
Click to expand...
Click to collapse
Ok. Thanks!
iSaidyiu said:
Ok. Thanks!
Click to expand...
Click to collapse
Or u can use Multirom.
I had installed stock fw as primary rom with kexec enabled kernel like Zombie kernel and used Multirom for installing secondary roms like cm12.1 and DU.
langeveld024 said:
Or u can use Multirom.
I had installed stock fw as primary rom with kexec enabled kernel like Zombie kernel and used Multirom for installing secondary roms like cm12.1 and DU.
Click to expand...
Click to collapse
True that.
Another tip if you do this is to use Link2SD (might need Pro, I do but I'm unsure if what I'm about to say is possible in Free version). You can link apps to ext# partition on microSD, and also data for those apps (I think that's the pro feature) - which means you can share user apps between both ROM's with data shared across both.
Keep in mind though that both ROM's need to have same format of apps for this to work. For example its impossible to share between 5.0 and 5.1 apps because 5.1 has a changed file structure for apk's (all their libs and the apk itself goes into a subfolder under apps in 5.1, unlike 5.0) and Link2SD can't handle that (yet, if ever).
I'm guessing CM12.1 and all other 5.1 AOSP Rom's use the same structure as stock 5.1 though, just thought I'd point this out in case you want to use a 5.0 ROM one day.
Sent from Xperia Z via Tapatalk
I attach the build prop from mi 5(Gemini). Which is rooted via magisk 16 and I extracted the build prop file. As I'm not a developer, but very active user. So I let you guys see the new MIUI 10 build.prop if you can do something with this. Thanks in advance.
The build.prop is just a set of values, I don't think you can "extract features" since if they are present, those are built into that specific rom, even if you put that "new" values on another rom, you won't add any extra functionality (Example is Camera 2 API, you can enable it into the MIUI but it is just disabled by default, you're not "adding a feature", just enabling it)
lukypuie said:
The build.prop is just a set of values, I don't think you can "extract features" since if they are present, those are built into that specific rom, even if you put that "new" values on another rom, you won't add any extra functionality (Example is Camera 2 API, you can enable it into the MIUI but it is just disabled by default, you're not "adding a feature", just enabling it)
Click to expand...
Click to collapse
Okay thanks, so in order to retrieve new features from that version which file do I need to access? Can you show me!
Hi,
Please guide me how can I add VoLTE icon in the status bar, as the original ROM doesn't support the same, as the developers doesn't like the icon, please don't ask me to ask the developer to add the icon, and neither to switch to another ROM.
On his part he is right to do the same, so I want to add and build it for personal use. I know how to compile a ROM from NOS source.
Have searched the internet for the same, but I am getting commits for the same for Oreo and not Pie.
Thank you, I eager to learn something new.
Currently i am using pixel experience rom and dt2w works great. However id like to return to stock and keep that feature. Is there some module that i can separately install via magisk or otherwise to enable this feature on stock?
There is a zip files in telegram group named dt2w_stock (I attached it here), try it if it works
How to make sony XZ2 nttDOCOMO SO-03K ROM to global ROM, make temproot and unlock VoLTE?
I cannot find any posts regarding this anywhere.
Can anyone please help me with it?
AlexHunt099 said:
How to make sony XZ2 nttDOCOMO SO-03K ROM to global ROM, make temproot and unlock VoLTE?
I cannot find any posts regarding this anywhere.
Can anyone please help me with it?
Click to expand...
Click to collapse
bro,
working volte requires those things :
a/ your service provider is Volte-compliant, and your package might be volte-compliant too
b/ your service provider must have sent his volte parameters to phone manufacturers
c/ your phone manufacturer might have implemented volte parametrs, aka profiles (.mbn files) within the shipped phone, or lately via OTA/updates.
volte profiles are stored in the EFS system, which is different than the common space disk used for stock rom or alternatives (lineage..)
they explain it well :
IMS
IMS features in Android more or less only work for recent Qualcomm devices at the time of writing, due to several changes in implementation per Android version, and lack of a standardized interface between the telephony frameworks and proprietary components. While IMS features themselves are standardized, the software implementations of them unfortunately are not.
Click to expand...
Click to collapse
Android Telephony Basics
Understanding Android Telephony
lineageos.org
means that if your phone doesnt support it, it might un-fortunately ne-ver support it. Welcome to the real world