Increase volume steps in android 5.1.1 - Xposed General

Up to android Kitkat I used the xposed module Volume Steps+ to alter the behavior of volume increments in the volume panel.
Now I'm on lollipop 5.1.1 and this module does not work anymore, there's lots of people having the same problem.
Over here I could read that it should be somewhere else in the framework.jar file.
The only way I know to change the jar file is to decompile it with baksmali.
So I can try if I can find the location where I need to change some values.
But I'm still looking for an xposed module or a stand-alone program to change the increment values.
I even want to try to write my own program but then I need to know how to change the framework.jar file from within the code (still need to decompile it one way or another or is there another way to change these values).
Can somebody give me a solution or put me in the right direction?

You say others are having the same problem. It's not really a problem given the fact the module is designed for KitKat and hasn't been updated since November. The problem is expecting it to work where it wasn't designed to. ?
You don't mention what ROM you're running. Stock, aosp/cm? A lot of non-stock ROMs have that feature baked in.
GravityBox has a volume steps toggle but no option to select how many steps one wants IIRC.
It would be nice to see that module updated.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

deboopi2 said:
I could read that it should be somewhere else in the framework.jar file.
The only way I know to change the jar file is to decompile it with baksmali.
So I can try if I can find the location where I need to change some values.
Can somebody give me a solution or put me in the right direction?
Click to expand...
Click to collapse
here you go AndroidON [HOWTO]Smooth Scroll & Volume Step

This may not be quite what you are looking for but GravityBox has an option to increase the number of volume steps. Been using it for the last few weeks on 5.1.1, works perfectly
edit: oops, sniped in an earlier post by marcdw

Update
When I install GravityBox and click on more volumesteps, it can be managed by Volumesteps+.
From then on changes made in Volumesteps+ are treated after reboot.
So I have a workaround.
What I can see is that the section in framework.jar is under another header but none of these values is changed.
This seems to be normal as xposed modules seem to handle everything in memory.
So I can try to write an Xposed module but then I still need to know what to change (it is no longer the framework.jar I need to look at but something in memory, what and where ?).

@deboopi2, good job on discovering that workaround with GB and VolumeSteps+. ?
Will give it a try.
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

The subject of volume steps came up in a ROM thread so I mentioned the combo workaround. However, a user said VS+ works just fine on his 5.1.1 ROM with no GB.
You think maybe it's not a 5.1.x issue but a ROM or device one?
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

Always worked fine on my Nexus 5 through KK to latest stock. Just wondering, what device are you running? Did you have the LG compatibility mode enabled for when you were under KK? (mine never needed it)

I have a Sony xperia Z3 Compact running stock lollipop 5.1.1

FYI all, latest version of GravityBox now includes a slider for its volume steps feature. ?
LG G3 D851, Pac-Man ROM, Tapatalk 4.9.5

Related

[TUT] Implementing EPRJ RIL in Custom Roms by Yourself

A. Why change RIL?
Hey, everyone.
As a user that's been using custom roms since our bootloader was unlocked, I'm aware that some of us have some issue with telephony & mobile data (in short, RIL) - occasionally IMEI wouldn't be read on boot, which would lead to device not being registred on network. Sometimes, the network would "die" in a way - you'd get an error when trying to dial a number, and when someone would call you, they'll hear the ringing tone while your cell phone would not ring at all.
The cause of the problem seems to be some lazy coding by official CM developers/maintainers for our device. This was picked up by a developer named kholk, so he did his best to recode it properly, however it was never included into official CM device tree for reasons unknown to me (more info about the issue can be found here: http://review.cyanogenmod.org/#/c/47980/).
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
So, with the help of Adam77Root, I've learned a way on how to implement EPRJ RIL into other custom roms (since I still had RIL issue with default CM RIL in 4.3 roms even) - so far I've tested it with Vanir 4.3, Carbon 4.3, Carbon 4.3.1, and few 4.2.2 roms, and I havent had ANY issues I had in CM RIL.
So, this is a tutorial to show you how you can import EPRJ RIL to any custom rom you'd like, in case you have issues with cell connection.
-this should work on any kernel and any custom rom (4.2.2+)! Tested so far, as far as kernel goes, are iodak 8/8.5, WWJB8/8b, Optimus Prime several versions, Optimus Play! 2.53.
-KK roms tested are P.A. by @dcos which has eprj ril by default, official CM nightlies and several others
-some KK roms, for some reason, don't have x3ril.smali file in their telephony-common.jar. To implement EPRJ RIL in these roms, follow the tutorial up to point 5, and skip that one, since you don't have anything to delete. After point 13, you need to do one additional thing - you need to edit ROM's build.prop settings, look for this line: "#ro.telephony.ril_class=X3RIL", and delete "#" so this line would be included in build.prop. After that, you're ready to flash. Thanks goes to @gerciolisz for the tip on the build.prop settings.
-/As of 24.01.2014. i've added another zip file which contains x3ril.smali taken from P.A. port by dcos - i'd recommend using this one for 4.4.2 roms/
-as of 11.06.2014., I've added x3ril.smali (it's in omni-v1.rar) made by adam, which is based on omni's RIL but has eprj RIL recovery. if you're on 4.4.3 kitkat rom and have issues, i suggest you give this file a try first before others
B. What's needed?
First off, you'll need a few things:
- Android Multitool from http://forum.xda-developers.com/showthread.php?t=2326604, many thanks to @Flextrick
- Read the linked topic - it's the instruction on how to use it, and in case you encounter any errors, that's the place to search for solutions
- Attached is a RAR with two files in it, X3RIL_old.smali and X3RIL_new.smali. You need only one of those - but more info about them will be in the other steps.
- Custom ROM you want to edit
- Common sense
- WinRAR & JAVA
C. How to change RIL?
Steps:
1. First step is to open the .zip of your custom ROM you want to edit, and search for system/framework/telephony-common.jar
2. Extract it to AndroidMultitool/Files, and after extract is done, delete it from .zip
3. Open Android Multitool, under Decompiling select .jar, then select telephony-common.jar in AndroidMultitool/Files, click "decompile"
4. After you're done, check if there were any errors in the Log, in AndroidMultitool main window
5. Head over to AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and look for X3RIL.smali. This is CM's RIL implemented in custom roms, which we dont need anymore, so delete it
6. Now, you need to decide wether to use X3RIL_old.smali, which is RIL from EPRJ CM10.2 built on 20130813, or X3RIL_new.smali which is RIL from EPRJ CM10.2 built on 20131007. I'm using 20131007 atm, and it's working without issues
7. When you've decided, move it back into AndroidMultitool/Decompiled_jar/telephony-common/com/android/internal/telephony and rename it to X3RIL.smali
8. Back in AndroidMultitool, under Compilin, select jar, and for folder select AndroidMultitool/Decompiled_jar/telephony-common, press "compile", and check for errors in Log
9. Output should be classes.dex file under AndroidMultitool/Compiled_jar
10. Open telephony-common.jar in AndroidMultitool/Files with WinRar - you should see META-INF folder, with classes.dex file
11. Delete classes.dex file in WinRAR
12. Move classes.dex file from AndroidMultitool/Compiled_jar to telephony-common.jar opened in WinRAR
13. Paste telephony-common.jar into system/framework inside the custom rom .zip file
14. You now have modified ROM ready to flash on our device!
D. Thank You's
Thank you's go out to @kholk for his RIL programming, @dcos for first implementing EPRJ RIL into a rom (his P.A. unofficial port for our device) different than EPRJCM10.2, @Adam77Root for his tutorial that I basically beutified and made sure is easier to understand & his modification of x3ril.smali from omni, @gerciolisz for the tip about build.prop settings, @Flextrick for his Multitool with neat GUI to extract .jar files, and all the other devs of p880 making our device worth every dime I've spent on it.
Flying_Bear said:
Kholk did include his own custom RIL into his EPRJ roms, but the roms are kinda old and have iffy baseband (which seems to be kernel issue, as he's using his own, 3.4 kernel instead of CM's 3.1 kernel in other custom roms).
Click to expand...
Click to collapse
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologize about it, but saves you the time and effort of answering the question every day
MOD EDIT: watch your language please.
penguin449 said:
Dude, i think you missed out the clarification for the users on whether or not they need to use the EPRJ Kernel and if anykernel will still work or normal kernels will work etc. Because your bound to have the first person to ask a question will either be, "How do i declare java paths" and "Will 'kernel name here' work with it", this isnt me asking, more of an fyi post (Y)
I do apologise about it, but saves you the time and effort of answering the question every day
Click to expand...
Click to collapse
np, thanks for the tip. i'll add in OP that it works with any kernel
MODERATOR EDIT: @penguin449 watch your language
I flashed Vanir nightly 171013 with Optimus Prime 2.70 kernel and telephony was completely disabled. I was not able to find or register to the mobile network. I tried modifying the RIL file as explained in this post; initially with the "new" file which didn't seem to solve the problem (still didn't get signal) but I didn't wait I immediately tried flashing the ROM with the "old" RIL instead. Initially there was no signal although I was able to find networks, but after a reboot the phone finally managed to connect to the mobile network.
I'm not sure whether it would've worked after a reboot with the "new" but I'm guessing if it's working with the "old" RIL I got nothing to worry about right?
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Flying_Bear said:
Vanir is 4.3.1 while OP is for 4.3, i think thats your problem. Different RIL would not help in that case. Flash Anykernel version of OP, or find a version repacked with 4.3.1 ramdisk. Good luck!
Click to expand...
Click to collapse
As far as I understood, the 171013 version did not have the RamDisk issue so I figured the CM10.2 version of Optimus Prime kernel should've worked correctly?
So I get it from you that if I flash the original rom with the AnyKernel version of OP it should work fine? (no need for any RIL modifications?)
Yep, anykernel versions of all our kernels xcept iodaks should work on any android version without any modifications.
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
MilkyJoePD said:
Is there a way to do this with Linux?
If not, how about uploading modified telephony-common.jar for CM ROMs?
I tried just replacing the whole telephony-common.jar file but I couldn't send or receive any messages. Everything else seemed to work though.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Flying_Bear said:
not sure really, since i havent worked on linux systems.
and i dont think telephony-common.jar is universal for all roms (i might be mistaken though), so there's no use to upload it. however, if you want, upload your original telephony-common.jar file here and i'll do my best to mod it for you!
Click to expand...
Click to collapse
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I meant it would be a good idea to have a place to download the modified files for specific ROMs.
Here's the (unmodified) file for Vanir.
https://app.box.com/s/embcq9kuemfdkdb1qw63
Thanks.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Flying_Bear said:
well, we have way too much roms for me to download each one and replace the RIL ^^
anyway, here's your modified telephony-common ^^ enjoy!
Click to expand...
Click to collapse
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
MilkyJoePD said:
I suppose there is a lot.
I'll test the Vanir one and report back.
If it works then there's a start. I can send messages so it works so far. The only thing keeping me from staying on a CM ROM is the random signal loss.
Sent from my Optimus 4X HD using Tapatalk
Click to expand...
Click to collapse
check it out, this should fix that issue completely. and report when you have time ^^
Flying_Bear said:
check it out, this should fix that issue completely. and report when you have time ^^
Click to expand...
Click to collapse
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Sent from my Optimus 4X HD using Tapatalk
---------- Post added at 01:22 AM ---------- Previous post was at 01:08 AM ----------
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
If you can then that would be great. A download for each CM ROM would open up custom ROMs like never before.
Sort out the SD card/internal memory paths and stock ROMs would be not worth installing.
Sent from my Optimus 4X HD using Tapatalk
penguin449 said:
If you want some 4.3.1 repacks done i can do them? or if you want some experience, i have the tools to swap ramdisks on windows in my signature that you could use...
Click to expand...
Click to collapse
if you've got the time and the will, be my guest - however, i don't think it's quite worth it. Not many people have this issue, and those that do would be better off fixing it by themselves then downloading aged nightlies for the rom they're looking for.
MilkyJoePD said:
In CM ROMs I get crazy data switches from 3g to E and G. Everything is good so far. Time will tell...
Click to expand...
Click to collapse
hm, switches from 3g to 2g seems to show that there is a bad connection where you're at. try enabling 2g only or 3g only in custom rom options or quick tiles, most roms support it these days. that should save your battery for few more %.
Just wanted to say that since replacing the file I haven't had to reboot once to get SMS or network to work.
That's over a month, whereas I was having to reboot about every 2 days.
The G/3G switching has improved, but still more sensitive than stock.
Sent from my Optimus 4X HD using Tapatalk
hey what if.... there is no x3ril.smali?XD there is only ril.smali or many others
edit: its ok there just x3ril was missing
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
ottomanhero said:
I'm on a odexed ROM (mokee 4.2.2 release) so I don't know what to do with classes.dex file multitool generates.It was meant to be used for deodexed telephony-common.jar files.So I tried these steps:
1_)deodex the ROM (using deodexer 4.3),
2_)implent RIL
3_)odex the ROM(using universal odexer 6.3.1) again which I failed to do as something was wrong with decompiling before odexing.This is probably happening due to deodex process.
I got bootloop after odexing the ROM.So I'm curious if there is a way to do this on an odexed jar file without having to deodex first.
I also tried to simply delete the odex & jar file and replace it with deodexed and eprj RIL implented jar file but the rest of the ROM was odexed so it gave me a bootloop.
I don't know much about these stuff, but I did my best searching for a solution and I'm out of ideas.All I want is to have an odexed rom with EPRJ RIL implented, I'd appreciate any help
Click to expand...
Click to collapse
unfortunately, i encountered the same issue, and it's beyond my knowledge on what to do with odexed roms. i bypassed the issue by using a nightly which came after the stable was released (not sure if there are any for mokee though)

Xposed Framework for Gingerbread

Update on 2017.05.02
I discountined the repo.xml for Xposed Framework for Gingerbread.
For myself, I use Xposed Framework Gingerbread for my old phone.
Now I use pixel, and use Brevent without Xposed Framework.
Update on 2015.10.30
The back-ported xposed framework used a seperate repo.xml for the sdk.
I found many times my server hang up due to the parse of the module.
Now the repo.xml won't check any package outside of the official repo.
(as the size from rovo89's repo is limited to 8M)
Update on 2014.08.15
I have fixed my old phone by replacing the screen.
I think it's the last chance, as screws is broken, I cannot open the phone any more..
I will keep back-porting if I find more than 10 users and gb-devices are more than 10% in the google play store.
Reference: http://developer.android.com/about/dashboards/index.html
Update on 2014.08.04
As my old android phone (which shiped the android 2.3.5) is broken.
I have no gb devices anymore, so I won't maintain this project anymore.
For all the projects, there are opensource, and free to change.
Update on 2014.06.03.2
- rebuild busybox with armv5te
- try system's busybox if fails
Update on 2014.06.03.1
fix for error for xsharedpreferences
Update on 2014.06.03
fix for the soft reboot, which was disabled
Update on 2014.06.02.1
fix for the light theme
Update on 2014.06.02
update to the latest 2.6.1
Note: the light theme is not good on GingerBread, so it's disabled.
Thanks @rovo89, for great hack on app_process.
Now, I try to backported to gingerbread (api-10).
Update on 2014.05.04
The binary of XposedInstaller, XPrivacy are on github's release.
https://github.com/liudongmiao/XposedInstaller/releases
https://github.com/liudongmiao/XPrivacy/releases
Update on 2014.03.18
Please do NOT contact the original author @rovo89 or @M66B) for support on the back-ported Xposed, nor XPrivacy.
For any issues related back-ported, please contact me directly via PM, or post an reply with @liudongmiao.
And it's more encouraged to create an issue at the back-ported github project.
Xposed: https://github.com/liudongmiao/Xposed
XposedBridge: https://github.com/liudongmiao/XposedBridge
XposedInstaller: https://github.com/liudongmiao/XposedInstaller
XPrivacy: https://github.com/liudongmiao/XPrivacy
XposedAppSettings: http://github.com/liudongmiao/XposedAppSettings
Update on 2014.01.06
As I have no time to update this thread.
For other modules, please install XposedGB Installer, and check in the Download Fragment.
And, I think XPrivacy and Xposed App Settings are good enough to install Xposed Framework.
For a xml verison of the modules, please visit http://piebridge.me/repo.gb.xml
Update on 20140105
I have back-ported two module, XPrivacy and Xposed App Settings.
And rewrite Master Key Fix GB. You can get all in the back-ported XposedGB Installer.
If you find some module very useful, you may create an issue at https://github.com/liudongmiao/XposedGBModule.
When I have time, I may consider to back-port it.
Update on 20140104
Now I have updated the framework through modified repository.
I cannot promise to update the the apk in attachments.
Update on 20140103.1
And as you see, the back-ported XposedInstaller is rename to XposedGB Installer.
Currently the repo for XposedGB Installer is pointed to a file generated from original repo.
I will check the result of the file, and keep gb-only modules. This is done every hour.
Currently, modules back-ported by me are not added yet, I will add them later.(Added them on 2014.01.05)
For the source, please visit below links, and please DON'T contact the original author @rovo89 or @M66B for following framework/module.
// As @rovo89 and @M66B indicated that those modifications won't be merged, and GingerBread won't be supported in their original versions.
Xposed: https://github.com/liudongmiao/Xposed
XposedBridge: https://github.com/liudongmiao/XposedBridge
XposedInstaller: https://github.com/liudongmiao/XposedInstaller
XPrivacy: https://github.com/liudongmiao/XPrivacy
XposedAppSettings: http://github.com/liudongmiao/XposedAppSettings
I will keep back-ported and catch the upstream update for them.
For any feedback for back-ported xposed framework, please contact me or create an issue on the project.
For the back-ported xposed modules, please contact the back-ported contributer.
For other xposed modules, you may contact the original author, or create an issue at https://github.com/liudongmiao/XposedGBModule/issues
(Please note, I don't have much time to back-port all of them, so if you find some modules are very useful, please add some comments, I will consider it has a high priority.)
good work but where's download link of xposegb installer and xposed privacy
raokashan said:
good work but where's download link of xposegb installer and xposed privacy
Click to expand...
Click to collapse
Update on 2014.05.04
The binary of XposedInstaller, XPrivacy are on github's release.
https://github.com/liudongmiao/XposedInstaller/releases
https://github.com/liudongmiao/XPrivacy/releases
I am using xperia x10 mini cm7 install xposed framework successfully ,apps (appsetting xprivacy xloud etc) also install succefully but they didnt work like in appsetting I enable fullscreen,etc didnt work.Enabled module in xposed installer, save the config I made reboot but didnt work
Your work keeping Gingerbread safe is appreciated
Although there are a reasonable number of "thanks" clickthroughs for the work you have all done, I want to specifically thank you all, and let you know that the Gingerbread Xposed/Xprivacy has been very helpful...
Need help!
@liudongmiao
I've been using Xopsed for a long time on my ICS ROM's. Suddenly, I came to know about Xposed backported to gingerbread and i was thrilled!:laugh: So i installed my stock gingerbread ROM and decided to give Xposed a try. Everything worked well till version 2.4.1-gb and then I updated it to 2.5.1.
Unfortunately,after the update, the framework doesn't install correctly for me. I have attached a screenshot of the error. Please help me with this!
Can't install Framework
@liudongmiao Thanks for you efforts in this back porting.
You can see i'm new here, i hope you can help me.
I have an issue, cant install the framework, i have no problems installing the XposedGB apk, but in the app, in "Framework" section i get "Xposed is not (yet) compatible with Android SDK version 10 or your processor architecture (armeabi-v7a). reloc Library (1346):2507 cannot locate 'dvmLogExceptionStackTrace'...cannot link executable." I tried with fix permissions, uninstalling-installing the app, but i have same error.
I already test with version 2.4.1 and 2.5.1, same results.
My device is a ZTE V795 with 2.3.6, mediatek 6572, 512 ram, dual core 1 ghz. it's compatible?
Thanks in advance and congratulations again.
Alltid said:
@liudongmiao Thanks for you efforts in this back porting.
You can see i'm new here, i hope you can help me.
I have an issue, cant install the framework, i have no problems installing the XposedGB apk, but in the app, in "Framework" section i get "Xposed is not (yet) compatible with Android SDK version 10 or your processor architecture (armeabi-v7a). reloc Library (1346):2507 cannot locate 'dvmLogExceptionStackTrace'...cannot link executable." I tried with fix permissions, uninstalling-installing the app, but i have same error.
I already test with version 2.4.1 and 2.5.1, same results.
My device is a ZTE V795 with 2.3.6, mediatek 6572, 512 ram, dual core 1 ghz. it's compatible?
Thanks in advance and congratulations again.
Click to expand...
Click to collapse
i get the same result on stock 2.3.6 GB on the Samsung Infuse 4G
Dhanesh95 said:
@liudongmiao
I've been using Xopsed for a long time on my ICS ROM's. Suddenly, I came to know about Xposed backported to gingerbread and i was thrilled!:laugh: So i installed my stock gingerbread ROM and decided to give Xposed a try. Everything worked well till version 2.4.1-gb and then I updated it to 2.5.1.
Unfortunately,after the update, the framework doesn't install correctly for me. I have attached a screenshot of the error. Please help me with this!
Click to expand...
Click to collapse
it seems that you installed a incompatible busybox...please make sure the busybox works, or just remove the installed one.
Young_Azul said:
i get the same result on stock 2.3.6 GB on the Samsung Infuse 4G
Click to expand...
Click to collapse
please send me the file /system/lib/libdvm.so
Deleted..
dj88 said:
Where is main .apk file to install xposed??
Sent from my GT-S5830i using Tapatalk 2
Click to expand...
Click to collapse
Go to the first link in the post.
@liudongmiao Hi i am getting this error while installing framework
Please help me sort this
thanks
jay.dumbali said:
@liudongmiao Hi i am getting this error while installing framework
Please help me sort this
thanks
Click to expand...
Click to collapse
There is some guys reported this error.
Could you tell me the device name, and system information?
// android version, or not-android?
And if possible, could you tell me the rom address, so I can download it?
If not, could you compress /system/lib and /vendor/lib (if exists), then send it to me?
Dhanesh95 said:
@liudongmiao
I've been using Xopsed for a long time on my ICS ROM's. Suddenly, I came to know about Xposed backported to gingerbread and i was thrilled!:laugh: So i installed my stock gingerbread ROM and decided to give Xposed a try. Everything worked well till version 2.4.1-gb and then I updated it to 2.5.1.
Unfortunately,after the update, the framework doesn't install correctly for me. I have attached a screenshot of the error. Please help me with this!
Click to expand...
Click to collapse
+1 on this
This may be an idiot question to ask, but here goes: how do I install the XposedBridge? I downloaded the .zip from GitHub, but don't know what to do with it. I tried flashing in CWM, but it says "Installation aborted". Couldn't find an .apk to install.
Thanks for the great work!
https://github.com/rovo89/XposedBridge/wiki/Development-tutorial
Not necessary if your are a user.
SJ3316 said:
Not necessary if your are a user.
Click to expand...
Click to collapse
I downloaded the XposedAddition module and it requires XposedBridge to run.
Why it dsnt support miui roms?? (old bug!!)
(ported to cm7)
Thnx
Sent from my little monster using Tapatalk ||
Hit thanks if i help you
xposed problem
liudongmiao said:
There is some guys reported this error.
Could you tell me the device name, and system information?
// android version, or not-android?
And if possible, could you tell me the rom address, so I can download it?
If not, could you compress /system/lib and /vendor/lib (if exists), then send it to me?
Click to expand...
Click to collapse
I am using micromax a52 running on android 2.3.6, armv7,mtk6575.
Here`s the link to the rom i m using
http://www.mediafire.com/?f0wtsri9e23hcyh
Thanks

[Q&A] Omni

Make this pretty later
You just made my day
Sent from my Nexus 6
I just confused myself. Should i be flashing the bootloader, radio, etc from a nexus factory image and then flash omni? I have been using 20150605 build without doing this. Should i do this for the nightlies?
subterfugium said:
Code:
I:operation_start: 'Flashing'
Installing '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'...
Checking for MD5 file...
MD5 matched
Verifying zip signature...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
I:comment is 1477 bytes; signature 1459 bytes from end
I:failed to verify against RSA key 0
E:failed to verify whole-file signature
E:Zip signature verification failed: 1
Error flashing zip '/sdcard/Download/omni-5.1.1-20150623-shamu-NIGHTLY.zip'
I guess zip verification fails because of test-keys or what does that zip verification stand for?
Click to expand...
Click to collapse
Honestly, I've never used zip verification for all the years I've been flashing ROMs and have never had any issues.
I'm probably wrong but.. My theory is that packed somewhere inside the zip you are trying to flash lies a key, which is compared next a second key once extracted. If they don't match it throws an error and aborts the operation.
Sent from my Nexus 6 using XDA Free mobile app
I've never used zip verification for this exact reason, and therefore have never looked into it. This sounds like something for the TWRP thread that @Dees_Troy could answer maybe.
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
The Rom OP is a bit bare of info. Thanks
530farm said:
Does anyone have a rundown of what this Rom has to offer beyond stock aosp? The Rom OP is a bit bare of info. Thanks
Click to expand...
Click to collapse
Off the top of my head... battery icon customization, volume match orientation, volume wake, screenshot delete, advanced reboot menu, hide usb debugging icon, ambient display customization. Also, Omni is the only AOSP ROM where I don't get force closes when taking multiple HDR+ pictures in a row without pause.
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
I saw that the past few builds uploaded were all 0mb. Just wondering what's going on until the builds resume?
Gandalf said:
Completely stable device functionality with whatever you see on gerrit :good:
I will make a "features list" tomorrow
Click to expand...
Click to collapse
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Ngo93 said:
Not sure if feature requests are allowed or not, if not then just ignore this..
But I was wondering if the 5 second home button delay on app launchers (such as Swipepad) is something that may be removed? That'd make navigating the phone much quicker for those of us who do use app launchers.
Click to expand...
Click to collapse
jira.omnirom.org :good:
glockliberty said:
I saw opendelta mentioned in the main thread but I haven't seen any indication it exists within the ROM. Am I just missing it?
Click to expand...
Click to collapse
Updates to opendelta have not been merged yet
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
RanceJustice said:
I am certainly interested in giving OmniRom a try. A couple of questions...
First, I'm attempting to download the Omni 5.1.1 20150725 Nightly (newest as of this writing) and the download is going exceptionally slow (20-30KB/s) on the official dl.omnirom.org mirror. Is there an issue with the server at current or an up to date mirror?
Next, is there an overall feature list for Omni (on Nexus 6)? Many ROMs place a list of their main features as well as any other ROMs/kernels they incorporate (ie based on CyanogenMod 12.1, with latest CM12.1 commits added on every update etc..)).
Thank you!
Click to expand...
Click to collapse
The server is probably being slow. They just upgraded storage/cleaned it up a few days ago and it has been significantly faster, it might be your connection to the server or something else.
As far as a list of features, there isn't one to my knowledge but you can certainly check on gerrit to see what's been merged recently. Just flash it and see for yourself: highfive:
Does this rom have layers?
Omnirom 5.1.1 nightly sudden reboot+supersu freeze+bluetooth headset bugs
I installed Omnirom 3days ago and have to say; nice stuff. runs fluid, batterie's fine and overall i like user experience. BUT
I'm experiencing some bugs.
first of all sometimes there just are random sudden reboots. On stock rom this happened from time to time when battery was below 30% or something so i thought there has to be a powersaving feature or something in kernel that don't works correct.
Then i flashed TWRP+Omnirom and those sudden reboots started happening randomly; regardless of battery.
I googled and found that could be some setting that adapt display brightness(???) and/or some apps bugging/conflicting. and, from previous experience, i know that this could also be a hardware/battery failure(please not; can't send my phone back right now as i need it daily for work and my N5 has a broken touch )
i tried disabling that display feature and also installed and tested if 'Lux' has any impact on that as it, basically, does the same but no change.
i factory reseted my device multiple times and tried to find out what APP could force this but... right now there's only the bare minimum(contacts+ / messages+ / aquamail / maildroid / todoist /calengoo /business calender pro and google stock apps)and still same problem. sometimes even while calling what's very embarassing when having an important customer on phone ...
I gonna try Zen Kernel next just to see if different kernel with different cpu scheduler COULD make any difference.
Then the second bug is my bluetooth headset(Plantronics M165). Can't get it to pair. Before Omnirom this worked very well as it should. Now, most of time he finds nothing and sometimes he finds a mac address of the headset but not the name. Other bluetooth devices are working fine and the headset's still working perfectly well on my gf's HTC M8. Anyone any ideas?
Last bug i experienced is SuperSU. Always an app needs root i can't get SuperSU intercept my choice. I click on allow or deny but nothing happens and after 10seconds superSu autodenies(or allows; depends on settings )right after factory reset supersu just works fine but suddenly stops working. root's still there as i can perfectly tell supersu what to do in its settings. Only the on demand root question can't be answered. uninstalling/reinstalling supersu didn't change anything. It doesn't matter if i install supersu by playstore or by zip through recovery. also unrooting and rerooting doesn't help. only a factory reset helps; for a while.
I don't want to change my Superuser managment as i paid for the pro version ...
Hope to find some help here as it's one of my fav places for everything smartphone related since back in my tytn days
so much knowledge in here.
keep up the good work
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
nightfly.0684 said:
update:
sudden Reboot Problem solved, Same for superSu Problem.
just the Bluetooth problem's still there. flashing back to Stock resolves the issue but... stock and I really start liking omnirom...
anyone any ideas ?
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
M builds will be ready soon enough :good:
great news
Do we get the Update for M through opendelta or is a factory reset + reflash needed?
and if i understand right you assume that the Bluetooth Problem should be gone with M?
would be nice as, right now, I sometimes have to pick up important calls while driving ... and... i don't like that at all....
would try the homemade M build IF i wouldn't need it daily for work. about time to repair my n5 i guess
Sent from my Nexus 6 using XDA Free mobile app

[MODULE] DisableMultiUserMod (build.props) v1.3 (for Magisk 14.0)

Thats my first productive creation for XDA, so dont be to hard to me
I don't like to have features, which I never use, so I always disable or remove everythink i dont need.
On my custom roms I always diable the multi user mode by adding the following line to the build.prop:
Code:
fw.max_users=1
I was annoyed to edit this file after each ROM update.
So I created this module. It just adds the above mentioned line to the build.prop.
It is really simple, but now I don't need to edit the build.prop.
Maybe for someone this can be useful.
It works with:
- Android 6.x (Tested on OnePlus X and OnePlus 3 with CM13)
- Android 7.x (Tested on LOS 14.1 and OxygenOS 4.5.x)
v1.3: Update to Magisk Template 1400 (14.0).
Looks good but I would change the modid to something other than template. This is in the config.sh file and defines the folder it uses under /magisk. Anyways I used your zip as a template for my own build.prop edits that I will post shortly. I'll throw a little credit your way too.
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
dima-82 said:
Sorry, I was on vacation and than really busy...
@shinji257: Thank you for the hint. I changed it and uploaded the mod as v 1.1.
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
FHC1998 said:
That module probably still works (haven't updated it since posted) but the Magisk template is not updated.
My module does pretty much the same thing as yours, there is only one more line on the prop that I add.
fw.show_multiuserui=0
This disable all the UI and configurations sections for multiuser. Its not obligatory, but for me it makes sense to disable the interface aswell if you are disabling the function.
You can add that if the multiuser options keep showing even after disabling multiuser.
Click to expand...
Click to collapse
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
dima-82 said:
When I looked for the build.prop settings to disable multi user functionality I found the mentioned line as well.
But I cannot see any difference if I add it. At least it has not effect on my phone (OnePlus 3, CM13).
Click to expand...
Click to collapse
It depends on the device, I originally tested on a few, and some needed this line.
For instance, I tested your module on my device (ZenFone 2 laser) and it worked perfectly without the line, but on my friend's ZenFone 2 it kept showing the UI even though not allowing creating more users.
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
mp3deviant721 said:
@dima-82 Module works great for me. I'm running a OP3T on offical LineageOS. All the multiuser stuff is gone from the settings and notification shade.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
dima-82 said:
Thanks for the feedback.
The official LineageOS for OP3T is Android 7.x? Nightly builds?
Click to expand...
Click to collapse
The build I'm running is 7.1.1. Haven't tried 7.1.2 yet. Yes on the "nightly" build.
Sent from my ONEPLUS A3000 using Tapatalk
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Here is the module on my device :silly:
dariomrk said:
@dima-82,
Hello, I used your module to enable multi user mode, all I did is edited the file inside the .zip where the string to disable the multi user mode is located, and replaced it with the two strings to enable it.
Now I was wondering since this works, could I make a thread with the mod?
I would obviously credit You, and link to Your profile and this thread.
Click to expand...
Click to collapse
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
dima-82 said:
Of course you can do.
But as mentioned in post #3 there was already a similar module. I think it does exactly what you need.
Click to expand...
Click to collapse
Oh, I didn't see that, I will check if it does the exactly same thing (probably yes)...
---------- Post added at 03:06 PM ---------- Previous post was at 03:05 PM ----------
Just checked it out, and yes it does the exactly same thing
Please I need multiuser enable magisk module​ for Android 6
dima-82 said:
And actually I found already a similar magisk module created by user @FHC1998:
https://forum.xda-developers.com/apps/magisk/magisk-multiuser-enable-disable-t3552643
Click to expand...
Click to collapse
Here
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
dima-82 said:
I am running it on official Magisk 13.2 without any issues.
Did you also install other modules?
Click to expand...
Click to collapse
Yes have other 5 modules
You installed / activated only this very one module and got a bootloop?
Before I created this module I edited the build.prop manually. And if you make a mistake there, you will get a bootloop as well.
May be your OS does not support this property.
I tested on my devices only, and it worked always.
Eventually you can try an other module from @FHC1998, which should do the same:
https://forum.xda-developers.com/showpost.php?p=71936097&postcount=3
jhobc said:
Got bootloop after the install of this module.
Device: Zuk Z2
ROM: AEX 4.4
Unofficial Magisk 13.2 (170716)
Click to expand...
Click to collapse
You could eventually try this mod:
https://forum.xda-developers.com/apps/magisk/module-single-user-mod-t3639486#post73160966 by @seebz

[SOLVED] Battery drain on custom ROMs running on SO-02K(Japanese docomo model)

I'm using Xperia XZ1 Compact SO-02K (Japanese docomo model) unlocked bootloader via qUnlockTool.
I installed some custom ROMs like LineageOS 18.1, Havoc OS 4.8, 3.11.
Any ROMs doesn't go to deep sleep so the battery drain is so bad. I installed Android 11 ROMs and 10 ROMs, but both not working deep sleep.
Anyone know good solutions?
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
satokun2668 said:
Thanks for good solutions!
Actually, I couldn't find pn553.ko on the latest stock ROM(47.2.B.5.38), so I deleted all of NFC files in /Vendor (of cause I took /Vendor backup with TWRP.). The deepsleep little works (please check attached picture) but the battery drain is better than before.
Thanks anyway!
Click to expand...
Click to collapse
what files did you delete, can you help me to deep sleep?
mugenXperia said:
Hi,
great to see some other user from Japan with the SO-02K. I also recently installed a custom rom and had the same issues as you. The source is the NFC chip. Unfortunately the Japanese version have a different chip/driver because of the Felica services here (Felica was here in Japan well before Google was even thinking to integrate NFC in Android, so nobody to blame here, beside Google, not Sony.)
Anyway the fix is a bit ugly. However, there is help:
Download this image from here: https://forum.xda-developers.com/t/rom-lineageos-18-1-unofficial-2-0-update-2021-01-20.4047763/
Yes, this and only this. I know it has not been updated anymore, but the reason comes below.
Please check out this thread: https://forum.xda-developers.com/t/fixed-xz1-au-sov36-japan-deepsleep-on-g8341-custom-roms.4156209/
It is about the XZ1 AU version but it also applies to the compact. I summarize here to make the post complete:
Either you root the phone, which I did not do because I do not need root for anything and with root, some of my app do not work, like Spotify. So I recommend to do those steps in the TWRP. Simply mount all the partitions and go to the file manager under advanced options.
Go to folder: /vendor/lib/modules
and delete or rename file call pn553.ko
Restart your phone and it will go to deep sleep. Otsukaresama.
Now, why only this image. Because it uses the older NFC library. In all other images, this fix this not apply anymore, as the modules are not at that place. I really would appreciate if someone more experienced can point me to the nfc module drives in any newer LineageOS image.
PS: Of course NFC will never work with a custom rom (without trying yourself to find out how to make it work)
Best
Click to expand...
Click to collapse
hy bro, can you tell me list rom xz1 compact docomo that have pn553 ko?
bangsat69 said:
what files did you delete, can you help me to deep sleep?
Click to expand...
Click to collapse
See this:
[ROM] Havoc-OS 4.6 [OFFICIAL] [R]
Havoc-OS 4.x is based on AOSP, inspired by Google Pixel. Has a refined Material Design 2 UI crafted by @SKULSHADY. Many useful features that will blow your mind. All you can dream of and all you'll ever need. Just flash and enjoy... General...
forum.xda-developers.com

Categories

Resources