This is a patch to fully enable GSM on every Stock Rom, on every AOSP Rom and on every Android version.
This in not for US users, in US the GSM is locked in RIL.
Release 4.x
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
-Call Forwarding
I'm constantly updating only this main thread and I will answer only in it, I have no time to update and control every thread in sub-forums.
I'm using this thread only for major notifications.
Mentor.37 said:
This is a patch to fully enable GSM on every rom and on every Android version.
This patch will enable:
-GSM
-SMS
-MMS
-3G Data
-USSD Code
The patch and the guide are available here.
If you want you can download a specific patch for the CyanogenMod 10.1.2 here.
Click to expand...
Click to collapse
it's worked on XT894 with Hashcode's CM10.1.2, i have tried it
such a nice work :good:
Does this enable the US GSM bands as well?
No, I'm sorry but it can't enable US GSM.
Awesome, added this to my GSM guide. Thank you.
Lum_UK said:
Awesome, added this to my GSM guide. Thank you.
Click to expand...
Click to collapse
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Mentor.37 said:
You are welcome but you wrote in your GSM guide that this patch is for non stock ROMs but it is for stock ROM also.
Then, please, give me credits on how to manually edit build.prop to enable GSM since you completely copied from my site in your thread.
Click to expand...
Click to collapse
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Lum_UK said:
Sorry I didn't realise you wrote that patch+website, thought you'd just posted the link. I will add you to the thanks section immediately.
I thought stock-based ROMs didn't need any GSM patch since they have the settings in the menu to switch to GSM?
For the record I didn't completely copy from your site. I already had all but two of the build.prop settings in that thread via Olegfusion and a couple of random posts in the CM10 thread.
edit: Ok, I've changed it to say "for all ROMs use this GSM patch, unless the ROM states that it is a GSM ROM", added you to the thanks section stating that you wrote the GSM patch and instructions, and also added a link to your ROM under the section about adding additional languages. Is that OK?
Click to expand...
Click to collapse
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Mentor.37 said:
Yes, that site is mine.
If you edit the build.prop in the stock rom as i mentioned you will correctly enable the GSM. The stock rom is strictly linked to the CDMA settings.
Here on the forum was recommended to edit the build.prop only in this way:
Code:
telephony.lteOnCdmaDevice = 0
ro.mot.phonemode.vzwglobalphone = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
persist.radio.ap.phonetype = 1
but in this way you will not correctly enable the gsm in fact there were many problems on aosp roms for gsm users.
Thank you for updating your thread.
Click to expand...
Click to collapse
Can I use LTE (gsm networks sim) in my country with this patch (Be, Europe) ?
You have to se what are lte frequencies in Belgium.
The lte on xt894 only works at 700 mhz.
Maybe next time you should give credits to the original author... *cough cough*
Are you talking with me?
I'm the original author.
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
But they differ in a few lines, I think that tobby disabled the LTE. Anyway for nightlies is better to replace only the lines needed.
The world is full of people there is a chance that two of them to work on the same thing.
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Regards
Sent from my XT894 using xda app-developers app
lucize said:
Tobby replaced only the lines needed in build.prop vs mentor who copied the whole file.
Click to expand...
Click to collapse
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
lucize said:
Anyhow I don't understand why the full apn list are not included in motorola roms by default.
Click to expand...
Click to collapse
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
With copy, I was telling the way that you implemented the patch, and regarding to apn it was only a comment because in other cm releases(not motorola), the apn list is full (~180kb vs 17kb).
I personally downloaded the tobby zip first, but I use this device only recently (previous was d3) so who was the original poster I can't say.
Regards
Sent from my XT894 using xda app-developers app
I do not understand why you think I would have copied the way to implement the patch, patches are all made in the same way.
Personally I use my stock rom but several users who use AOSP roms have contacted me exposing the gsm problem and so I easily fixed with this patch using the settings that I use in my rom file build.prop.
At short will release a new version of my rom with a new build.prop file with new settings and I'll update this patch also.
I honestly did not know existed nor Tobby nor his zip, I created this patch because asked me.
Regarding the file APNs-conf.xml depends on the fact that the phone is born to the CDMA network Verizon and therefore not serving the other APNs, the file APNs-conf.xml in the stock rom is ~ 43KB.
What is the Tobby's zip?
Mentor.37 said:
I copied what and where?
I did not know Tobby before now and with a quick search I found only this.
Please, let's be serious.
Motorola includes an apn list depending on the terminal, this phone is sold for the market cdma verizon and so it do not include others apns.
The apn list added in this patch is extracted from a motorola stock rom.
Click to expand...
Click to collapse
Ah c'mon. Take a look into your own files. In apns-conf.xml is still my copyright... Its not extracted from Motorola Stock-ROM. Also not from CM. It's based on several sources on the internet (most of it is based on CM, but several more sources were added). It took days to combine the sources, remove duplicates, sort it, use the same style for every entry and so on. It's not a problem to use or copy this. But to say you did this yourself is not fair.
But apns-conf.xml is only one part of your mod. Second part is the automatic build.prop changer. (GSMbyMentor.sh)
Look at your GSMbyMentor.sh:
Code:
#!/sbin/sh
#
# Patch to enable GSM on Verizon by Mentor
# Build: 17.07.2013 17:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=GB/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.modem.mode =1/persist.ril.modem.mode =2/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.vzw.cdma.mdn=/persist.radio.vzw.cdma.mdn=deleted/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc = 1/ro.telephony.gsm-routes-us-smsc = 0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.ap.phonetype=2/persist.radio.ap.phonetype=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
Now let's take a look at the Bash-Script of "TobbysMod":
Code:
#!/sbin/sh
#
# Tobbys build.prop Anpassungen für das Droid 4
# Stand: 15.03.2013 04:43
#
/sbin/sed -i "s/\ =/=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/=\ /=/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.language=en/ro.product.locale.language=de/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.product.locale.region=US/ro.product.locale.region=DE/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/telephony.lteOnCdmaDevice=1/telephony.lteOnCdmaDevice=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.ril.ecclist=911\,\*911\,\#911/persist.ril.ecclist=911\,\*911\,\#911\,119\,118\,999\,08\,000\,112\,110/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.default_network=10/ro.telephony.default_network=3/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzwglobalphone=0/ro.mot.phonemode.vzwglobalphone=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.telephony.gsm-routes-us-smsc=1/ro.telephony.gsm-routes-us-smsc=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.hwKeyboard.capsLockNoAlt=true/ro.hwKeyboard.capsLockNoAlt=false/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.phonemode.vzw4gphone=1/ro.mot.phonemode.vzw4gphone=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/persist.radio.lte.mm.disable=0/persist.radio.lte.mm.disable=1/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.mot.lte_on_cdma=1/ro.mot.lte_on_cdma=0/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dateformat=MM-dd-yyyy/ro.com.android.dateformat=dd.mm.yyyy/g" /system/build.prop > /system/build.prop
/sbin/sed -i "s/ro.com.android.dataroaming=true/ro.com.android.dataroaming=false/g" /system/build.prop > /system/build.prop
Let's take a look at the differences.
- You removed my credit and changed the date
- you removed a few lines which were necessary for the keyboard-mod included in the original mod and necessary for European date-format and emergency calls
The rest stayed the same. Even the sequence/order. And you use exact the same trick for removing spaces. You can't say this was coincidence...
Third part of your mod is the edison install script. This looks different. Seems to be your own work.
Two of three parts in your mod copied from me. It's ok! I always wanted to remove the parts which are necessary for my German friends so everybody can use it, but I didn't have enough time. So it is good someone (you) did that. But please don't say it's your own work when you just copy files...
Link to original Thread for "TobbysMod": http://www.android-hilfe.de/motorol...82-tobbys-automatische-rom-modifizierung.html
Google translation: http://translate.google.de/translat...82-tobbys-automatische-rom-modifizierung.html
I added that apns-conf.xml at the suggestion of an user that tested my patch, I repeat that I'm on stock rom so I have not tested directly the patch. If you wont I can give you his email address.
In a first moment I made this patch as you can see here with the apns-conf.xml that I personally extracted and that I use in my rom for months without any problem. Anyway I removed that file.
About the sed is a common command for any linux user to manipulate text.
About the sequence/order it is different, I used the same in the build.prop.
About the point of the gsm patch, so the build.prop settings there are a lot of differences:
My:
Code:
telephony.lteOnCdmaDevice=0
persist.ril.modem.mode=2
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
persist.radio.vzw.cdma.mdn=deleted
ro.telephony.gsm-routes-us-smsc=0
persist.radio.ap.phonetype=1
ro.mot.phonemode.vzw4gphone=0
Yours:
Code:
telephony.lteOnCdmaDevice=0
ro.telephony.default_network=3
ro.mot.phonemode.vzwglobalphone=1
ro.telephony.gsm-routes-us-smsc=0
ro.mot.phonemode.vzw4gphone=0
persist.radio.lte.mm.disable=1
ro.mot.lte_on_cdma=0
These lines are missing in your:
Code:
persist.ril.modem.mode=2
persist.radio.vzw.cdma.mdn=deleted
persist.radio.ap.phonetype=1
and the lines that are equal in the two files have known each other forever and they are everywhere in the forums so what are you saying?
With the settings in my build.prop users solved their problem on aosp roms.
#Postedit
I found this and this with your patch and then this and this with my patch.
apns-conf.xml: As I said: You don't need to remove the file. It's ok I created this file to help users. Additionally because of the sources, I am not allowed to forbid the usage of this file for some users. You also don't NEED to give credits, because it's already included. I just wanted to mention you are not using your own file. Not more ore less.
Bash-Script: Yes, sed is a common linux command. But it's usage on the phone was a little bit different than on a normal linux machine and the trick with the spaces (sed -i "s/\ =/=/g") is not necessary for the function of this script. It's just to make some things a little bit easier. That's why it's hard to believe you found out the exact same thing as me and used it in exactly the same way. If you did: Grats mate! You must be a soulmate of me If you just used this because you saw it "somewhere" else: please don't remove my credit.
To the missing 3 lines: two of them are included in version 1.3 of 07/16/2013, one day before you created yours. Just "persist.radio.vzw.cdma.mdn=deleted" is not included in my Mod. I am just curious: What does this line do?
But we schouldn't argue about it. As I said: Feel free to use my work. I hope I am allowed to do the same with your work. Instead of argueing we should combine our work!
I reinserted the apns-conf.xml that I use in my rom.
I used the sed command intuitively how I use it.
The line "persist.radio.vzw.cdma.mdn=deleted" deactive the mdn on cdma network. I use these settings from time.
You can use my work without problem.
I just answered your allegations because I spent a lot of my free time for this my mod.
About a possible collaboration I like this idea, the work is much, time is short and one hand is always a pleasure.
Related
Here's a few more modules for the stock kernel if anyone's interested.
CIFS (+slow-work.ko) should work with CIFS Manager (in the market), but I have yet to test it (can't here at work).
And I know Sogarth was looking to try out a FUSE solution for the webtop, so I went ahead and added that module.
Haha. Neat.
btw, has anybody verified if the kernel on the 4.1.57 update is different/incompatible? It claims to be kernel 2.6.32.9-00005-gde8e6dc.
Sogarth said:
Haha. Neat.
btw, has anybody verified if the kernel on the 4.1.57 update is different/incompatible? It claims to be kernel 2.6.32.9-00005-gde8e6dc.
Click to expand...
Click to collapse
You mean did they change CONFIG_MODVERSIONS to 'n' ? Otherwise, our source tree should be close enough for most purposes right?
PS. Nice work agentdr8.
EDIT: Here are the differences in the orig/OTA kernel. Mostly VPN related?
Code:
diff config.orig config
4c4
< # Sat Feb 5 02:50:36 2011
---
> # Tue Mar 1 09:16:01 2011
435c435
< # CONFIG_XFRM_MIGRATE is not set
---
> CONFIG_XFRM_MIGRATE=y
437c437,439
< # CONFIG_NET_KEY is not set
---
> CONFIG_XFRM_IPCOMP=y
> CONFIG_NET_KEY=y
> CONFIG_NET_KEY_MIGRATE=y
452,453c454,455
< # CONFIG_INET_AH is not set
< # CONFIG_INET_ESP is not set
---
> CONFIG_INET_AH=y
> CONFIG_INET_ESP=y
457,459c459,461
< # CONFIG_INET_XFRM_MODE_TRANSPORT is not set
< # CONFIG_INET_XFRM_MODE_TUNNEL is not set
< # CONFIG_INET_XFRM_MODE_BEET is not set
---
> CONFIG_INET_XFRM_MODE_TRANSPORT=y
> CONFIG_INET_XFRM_MODE_TUNNEL=y
> CONFIG_INET_XFRM_MODE_BEET=y
461c463,464
< # CONFIG_INET_DIAG is not set
---
> CONFIG_INET_DIAG=y
> CONFIG_INET_TCP_DIAG=y
467,475c470,479
< # CONFIG_IPV6_PRIVACY is not set
< # CONFIG_IPV6_ROUTER_PREF is not set
< # CONFIG_IPV6_OPTIMISTIC_DAD is not set
< # CONFIG_INET6_AH is not set
< # CONFIG_INET6_ESP is not set
< # CONFIG_INET6_IPCOMP is not set
< # CONFIG_IPV6_MIP6 is not set
< # CONFIG_INET6_XFRM_TUNNEL is not set
< # CONFIG_INET6_TUNNEL is not set
---
> CONFIG_IPV6_PRIVACY=y
> CONFIG_IPV6_ROUTER_PREF=y
> # CONFIG_IPV6_ROUTE_INFO is not set
> CONFIG_IPV6_OPTIMISTIC_DAD=y
> CONFIG_INET6_AH=y
> CONFIG_INET6_ESP=y
> CONFIG_INET6_IPCOMP=y
> CONFIG_IPV6_MIP6=y
> CONFIG_INET6_XFRM_TUNNEL=y
> CONFIG_INET6_TUNNEL=y
2136c2140
< # CONFIG_CRYPTO_NULL is not set
---
> CONFIG_CRYPTO_NULL=y
2163c2167
< # CONFIG_CRYPTO_HMAC is not set
---
> CONFIG_CRYPTO_HMAC=y
2173c2177
< # CONFIG_CRYPTO_MD5 is not set
---
> CONFIG_CRYPTO_MD5=y
2195c2199
< # CONFIG_CRYPTO_DES is not set
---
> CONFIG_CRYPTO_DES=y
2208c2212
< # CONFIG_CRYPTO_DEFLATE is not set
---
> CONFIG_CRYPTO_DEFLATE=y
2231a2236
> CONFIG_ZLIB_DEFLATE=y
Cool..I just did the OTA update to 4.1.57, any possibility to get this module for that version of the kernel. Although the version appears to match, the 4.1.57 kernel string
is
2.6.32.9-00005-gde8e6dc
EDIT: Damn should have read the previous thread, sorry. So has anyone verified, otherwise I might give it a shot here.
bekarhoo said:
2.6.32.9-00005-gde8e6dc
EDIT: Damn should have read the previous thread, sorry. So has anyone verified, otherwise I might give it a shot here.
Click to expand...
Click to collapse
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
I recompiled them with the localversion set to 00005-gde8e6dc so see if these work with the OTA update (I haven't applied the update and probably won't until true root is found, so I can't test these). I checked the vermagic with modinfo -F vermagic and they check out as 2.6.32.9-00005-gde8e6dc SMP preempt mod_unload modversions ARMv7
EDIT: Removed attachment -- not working on new kernel
agentdr8 said:
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
Click to expand...
Click to collapse
They seemed to insmod fine for me on .57 (the originals)
agentdr8 said:
(I haven't applied the update and probably won't until true root is found, so I can't test these).
Click to expand...
Click to collapse
Hmm I'm pretty OK copying su around. I kinda hope we save whatever gems are left for gingerbread. I sense more OTAs coming, there are so many bugs left... we could give up all our aces with a cat and mouse game
agentdr8 said:
Even though the major & minor kernel versions haven't changed, the addition of the localversion might throw off the vermagic in the original modules I posted.
I recompiled them with the localversion set to 00005-gde8e6dc so see if these work with the OTA update (I haven't applied the update and probably won't until true root is found, so I can't test these). I checked the vermagic with modinfo -F vermagic and they check out as 2.6.32.9-00005-gde8e6dc SMP preempt mod_unload modversions ARMv7
Click to expand...
Click to collapse
I'm getting:
insmod: error inserting 'cifs.ko': -1 Unknown symbol in module
I have rooted .57
Edit: May be it is because the way I installed cifs.ko.
I just remounted /system and copy cifs.ko in /system/lib/modules/
Did I forgot something?
Try using the original ones for the stock kernel. I think someone said they work fine with the new OTA kernel.
I already did that and no luck. I'm doing something wrong ...
Edit: I'm an idiot. slow-work.ko has to go first, then everything works. Thanks!
Any chance someone would be willing to walk a noob getting this on the atrix? I've updated to the latest 1.83. I'm real interested in getting cifs up and running. To be honest, I'm floored it's not included by default. Any risks/issues with doing this? I got no problem hacking away at this so long as there's some clear step-by-step directions so I'm confident I won't botch it up
Thanks!
Looking for a working utf8.ko
Help
Sent from my MB860 using XDA App
Can someone please post the new versions that would work for the latest GingerBread build from OTA update? Thanks!
these modules are included in faux custom kernel, not sure about others
Enviado desde mi MB860 usando Tapatalk
My kernel is 2.6.32.9 from new version 2.3.6. Does anybody could help me to compile an cifs module to work on this new stock rom (my bootload is locked yet).
2.3.6 kernel mods
I'm interested in getting isofs.ko and udf.ko and ext4.ko kernel mods working, I've tried compiling from source that's posted on source forge, but it's not working.
here's a thread I was working out of: http://forum.xda-developers.com/showthread.php?p=26892952#post26892952
Please help!
HTC released gingerbread via OTA but they did not support additional modules. This thread has flashable zips for both the leaked kernel and the one from the "OTA".
Added flashable modules to attachments that are flashable in recovery.
I have created a zip of some of the more useful modules for our device:
Code:
cpufreq_conservative.ko
cpufreq_smartass.ko (thanks Chad for the help here)
ext4.ko
jbd2.ko (necessary for me to load ext4)
tun.ko
perflock_disable.ko (I actually compiled this one a little different but confirmed it would load and not get the exec format error)
Update: Smartass is working now with assistance from chad in resolving those errors. Decided to not worry about interactive for now.
Further information:
If you don't use the CWM flashable zip you will need to load perflock_disable a special way as it needs to be called with a special parameter to make it work correctly. Try adding below to a script. Credit to Calkulin for the script.
Code:
if [ -e /system/lib/modules/perflock_disable.ko ]; then
insmod /system/lib/modules/perflock_disable.ko
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
addr=`awk '$3 == "perflock_notifier_call" { print "0x"$1; }' /proc/kallsyms`
if [ -n "$addr" ]; then
insmod /system/lib/modules/perflock_disable.ko "perflock_notifier_call_addr=$addr"
if [ $? -eq 0 ]; then
echo "Perflock DISABLED"
else
echo "ERROR!!! Perflock could NOT be DISABLED"
fi
fi
fi
fi
Credits:
Conap (for BootManager and helping me test ext4 on an SD ROM)
XDA (for teaching me so much about Android)
HTC (for the kernel source)
Chad0989 (for assistance in getting smartass CPU governor working)
Coolbho3000 (perflock_disable)
Calkulin for the module load script
anyone else who inspired me (apologize if I forgot)
I have attached a zip file to this. If you are not a dev you can still use the modules here but some basic ADB/terminal knowledge would be needed. The modules are open for testing though.
Attached zip files and CWM-flashable zip files for both OTA and leak-based ROMs.
inc_modules.zip - Just the loadable modules.
inc_modules_ota.zip - just the loadable modules - OTA-based ROMS (August leak)
inc_modules_ota_091811.zip - just the loadable modules - OTA-based ROMS (actual OTA from September)
inc_modules_CWM_flashable.zip - flashable zip that will also autoload modules at boot.
inc_modules_ota_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (August leak)
inc_modules_ota_091811_CWM_flashable.zip - flashable zip that will also autoload modules at boot - OTA-based ROMS (Actual OTA from September)
I'm glad some one took this up I had been wondering the same thing since HTC opened the dev section. I had found another site that had a more extensive write up on how to build kernels but I'm not very fluent in linux and was a little intimidated at trying. At least I now know that it can be done. Maybe we can get Chad to try and port it over?
Awesome. A ray of hope.
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
jermaine151 said:
Good job Tiny! I know someone was just asking for a tun.ko module and now I can't remember who it was. Hopefully they see your post.
Click to expand...
Click to collapse
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
tiny4579 said:
Thanks!
I'm trying to add more existing modules but my compiler treats warnings as errors so it won't build. Chad, if you see this post, any advice here?
Click to expand...
Click to collapse
--prefix
Sent from my ADR6300 using XDA App
hightech316 said:
--prefix
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I actually got them to build but they won't load still. I will play around with it more.
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
oh wow this is incredible great job tiny!!! and the reason you probably cant get those other governors to work is because htc released an uncomplete source
jskolm said:
This is awesome. I was hoping for a tun.ko module! Now, do I just grab these and drop then in system/lib/modules and they should just work? Or are there steps I need to take to make them work? (I am honestly only concerned with the tun.ko)
Click to expand...
Click to collapse
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
tiny4579 said:
Just drop in the ones you want and run insmod /system/lib/modules/tun.ko for tun.ko. You will have to do it at boot each time or get the dev to write an init.d script to load it.
Click to expand...
Click to collapse
would i need to make one for every module?
JoelZ9614 said:
would i need to make one for every module?
Click to expand...
Click to collapse
Joel,
No, just one script should work. I believe Synergy ROM already has the init.d script for some of them. See 00cpufreq_modules in /system/etc/init.d
All,
Updated OP with latest zip file. If you have downloaded previously, redownload to get the latest.
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
JoelZ9614 said:
would it be likes this?
http://www.multiupload.com/J9WTSA4VWF
Click to expand...
Click to collapse
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
tiny4579 said:
The first line should be:
Code:
#!/system/bin/sh
and it needs to have execute permissions or it won't execute. Also make sure to save it in UNIX format. I would also add the smartass module as it is quite popular. To test type lsmod from adb or terminal after boot. Hope this helps.
Click to expand...
Click to collapse
eeh im not good with init.d scripts lol
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Every shell script should contain
#!/system/bin/sh
Sent from my ADR6300 using XDA App
JoelZ9614 said:
ok i think i got it would it be like this?
Code:
#!/system/bin/sh
/system/bin/insmod /system/lib/modules/tun.ko
Click to expand...
Click to collapse
Exactly!
Then just make a line for each module.
EDIT: Though you could just write it like this:
Code:
#!/system/bin/sh
insmod /system/lib/modules/tun.ko
Though to be safe and to make sure you are running that particular insmod command you can leave it the way you have it.
ok done its in my rom RLS3 Thanks Tiny Great work
JoelZ9614 said:
ok done its in my rom RLS3 Thanks Tiny Great work
Click to expand...
Click to collapse
No prob! It's been a good project for me.
Update: I got ICS SuperCharged! See Post 92!
And hey, rank the thread n click thanks n stuff
So I had indeed been working on V8 SuperCharger and when V6 got really hot, I kept pretty busy making it better and better.
Of course, this leads to a much better V8 than would have been possible.
At the time, it was very much Milestone specific in that I made an overclocking feature that makes a file just like 10overclock as below.
Code:
#!/system/bin/sh
echo "5 1100000000 66" > /proc/overclock/mpu_opps
echo "4 800000000 45" > /proc/overclock/mpu_opps
echo "3 600000000 35" > /proc/overclock/mpu_opps
echo "2 400000000 27" > /proc/overclock/mpu_opps
echo "1 200000000 22" > /proc/overclock/mpu_opps
The new file will be /system/etc/init.d/99sc-overclock
10overclock is untouched.
The 99sc-overclock settings will stick because it will run after 10overclock.
UnOverclocker simply deletes 99sc-overclock
Big thanks to skadude66 for helping me with testing out the Overclockerthingie!
This V8 Alpha also has an early implementation of 3g TurboCharger and user selectable colours.
I have these older screen caps that I'm using since I had lost my Milestone...
This is what it looks like....
Code:
\\\\ V 8 S U P E R C H A R G E R - M E N U ////
==============================================
1. SuperCharger & Launcher Status"
2. Aggressive 1 Settings {6,8,24,30,40,50 mb}
3. Aggressive 2 Settings {6,8,25,30,35,35 mb}
4. Balanced 1 Settings {6,8,24,26,28,30 mb}
5. Balanced 2 Settings {6,8,26,27,28,28 mb}
6. Balanced 3 Settings {6,8,26,28,30,32 mb}
7. MultiTasking Settings {6,8,22,24,26,26 mb}
8. Gaming Settings {6,20,40,70,80,90 mb}
9. MegaMemory Device {6,12,75,125,150,175 mb}
10. Cust-OOMized Settings {See Slot 3 Tips!}
11. OOM Grouping Fixes + Die-Hard Launcher
12. OOM Grouping Fixes + BulletProof Launcher
13. UnDo Kernel/Memory Tweaks
14. UnSuperCharger
15. 3G TurboCharger + Hardware Acceleration
16. Overclocker {99sc-overclock SuperCedes OC}
17. UnOverclocker {Removes 99sc-overclock}
18. REBOOT! (WARNING - There is NO Warning!)
19. Exit
WARNING: This is only for goofing around with!
The overlocker and unoverclocker are the ONLY useful features as the current V6 SuperCharger has different OOM groupings and the current 3G TurboCharger, which was just released, has 5 different configurations to choose from
If you do apply SuperCharging with this early V8 version, UNSUPERCHARGE V6 BEFORE supercharging with this V8.
Other ROMS on other phones, I don't know what would happen if you tried the Overclocker
Lastly, if you can donate, please do since it will help make further updates and a more polished V8 much quicker
Installation Instructions are the same as found in the monster V6 SuperCharger thread
Wow!
I loved the V6 and i'm using it right now!
I'm downloading this V8 and ill post a feedback.
Thanks for this great work man!
Good work Zeppelin! I got caught up in all of the V6 supercharger and haven't been keeping up with the latest betas! I'm keen on trying this out
If you lost your Milestone, what phone are you using right now? :O
A crappy samsung thingie... updates from over a month ago till now are done "in my head"
Engine Flush, Nitro Lag Nullifier, the new 3G TurboCharger, KAK... I haven't seen them running with my own eyes as of yet LOL
Of course, V8 Alpha was done before that... I think this was done in May/July...
Oh and I forgot to thank you in the OP for assisting with the OCing at the time
zeppelinrox said:
A crappy samsung thingie... updates from over a month ago till now are done "in my head"
Engine Flush, Nitro Lag Nullifier, the new 3G TurboCharger, KAK... I haven't seen them running with my own eyes as of yet LOL
Of course, V8 Alpha was done before that... I think this was done in May/July...
Oh and I forgot to thank you in the OP for assisting with the OCing at the time
Click to expand...
Click to collapse
Hehe, no worries about the OC, just a simple idea to implement!
At this point, it's pointless to get a new Milestone, the new GSII is supposed to release sometime soon on Telus
Sent from my Milestone using XDA Premium App
Keyboard?
I wonder if droid3/milestone3 will make it's way here
zeppelinrox said:
Keyboard?
I wonder if droid3/milestone3 will make it's way here
Click to expand...
Click to collapse
No keyboard, but it's rumored to have a 4.5" screen. The Droid 3/Milestone 3 is on Bell, so if you can buy it no term, you can just enter in the APN for Telus afterwards I guess!
Sent from my Milestone using XDA Premium App
V8 is working nicely!
Thx man!
Im using Gamming Mode
skadude66 said:
No keyboard, but it's rumored to have a 4.5" screen. The Droid 3/Milestone 3 is on Bell, so if you can buy it no term, you can just enter in the APN for Telus afterwards I guess!
Click to expand...
Click to collapse
When the time comes, I will definitely look into it
afonsolage said:
V8 is working nicely!
Thx man!
Im using Gamming Mode
Click to expand...
Click to collapse
Cool indeed
zeppelinrox said:
When the time comes, I will definitely look into it
Cool indeed
Click to expand...
Click to collapse
Some more info on the Samsung GS2 for Telus codenamed "Hercules" :http://mobilesyrup.com/2011/08/17/telus-samsung-galaxy-s-ii-hercules-surfaces-again/
I'm going to try out V8 Alpha tonight and let you know how it goes
Nice work zepp, I'll do some testing on my Evo 4G and post an update with my results! Glad to see you progressing! V8? What's next, V12?!
Thanks for testing guys...
It's pretty much the same as V6 update 1 if I remember correctly except for the added colours, 3g and overclocking.
Oh maybe you can test this command out...
Code:
busybox | head -1 | awk '{print $1" "$2}'
Going by this page it should spit out the busybox version that you're using
Also...
Code:
id | awk '{print $1}'
If you could post the exact output... that would be great
zeppelinrox said:
Thanks for testing guys...
It's pretty much the same as V6 update 1 if I remember correctly except for the added colours, 3g and overclocking.
Oh maybe you can test this command out...
Code:
busybox | head -1 | awk '{print $1" "$2}'
Going by this page it should spit out the busybox version that you're using
Click to expand...
Click to collapse
I'm getting an error saying that it is an unknown option. The switch for -1 should work with head, but it isn't working. When you type only busybox, head is one of the options, I think there might be something missing in the call for head.
Also, I don't know 100% if appending the " " in the awk will work. I'm pretty sure the , will interpret the fields with spaces, and that is not needed.
EDIT: Just invoking "Busybox" in an instance of Terminal Emulator will spit out a sort of help page, with the first line having the Busybox version number on it.
yeah going by that page...
busybox | head -1 by itself should work... and it doesn't?
Howabout....
busybox --help | head -1 | awk '{print $1" "$2}'
zeppelinrox said:
yeah going by that page...
busybox | head -1 by itself should work... and it doesn't?
Howabout....
busybox --help | head -1 | awk '{print $1" "$2}'
Click to expand...
Click to collapse
busybox | head -1 gives an unknown option error.
busybox --help is the same as just running busybox in Term Emulator.
I tried running id | awk '{print $1}' and it gave me "awk: applet not found".
EDIT: Running busybox --help | head -1 |awk '{print $1 " " $2}' gives me the applet not found error for awk and head.
can you possibly have an incomplete busybox or something?
How can it not find awk
zeppelinrox said:
can you possibly have an incomplete busybox or something?
How can it not find awk
Click to expand...
Click to collapse
I have no idea
I just ran the Busybox Installer, installed 1.18.5 and then I ran the commands, even after doing a su and it gave me the same applet error.
ah... try 1.18.2 or lower.... LOL
You lost your Milestone? Where did you ever find it?
zeppelinrox said:
ah... try 1.18.2 or lower.... LOL
Click to expand...
Click to collapse
BINGO! I installed Busybox v1.17.1 and doing
Code:
busybox | head -1
Spat out
Code:
BusyBox v1.17.1 (2010-08-12 23:44:34 CDT) multi-call binary.
EDIT: Everything is working fine right now.
Code:
busybox | head -1 | awk '{print $1" "$2}'
Working.
Code:
busybox | head -1 | awk '{print $1,$2}'
Same output as with " " in the awk call.
Hello.
Have you ever tried to port Rom's from model with wifi ot model with 3g? Which files need to copy to make modem work?
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
kimshooter said:
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
Click to expand...
Click to collapse
Never go full retard.
kimshooter said:
Buddy You need the hardware for it (Voice and Network)
its not possible in Nexus 7 WiFi model
so forget about porting
Click to expand...
Click to collapse
So I take all the ROMs that are available for both WiFi and 3G model are made with pure magic then ? Hmmm..
Sent from my C6603 using xda premium
farstar7s said:
Hello.
Have you ever tried to port Rom's from model with wifi ot model with 3g? Which files need to copy to make modem work?
Click to expand...
Click to collapse
I believe any of tge general gyides fie porting (which you can avail by searching) is also applicable here, even if its not, trying won't hurt as nothing more than a soft brick can occur, afaik, even of anything goes wrong
khaytsus said:
Never go full retard.
Click to expand...
Click to collapse
LOL.
farstar7s said:
Which files need to copy to make modem work?
Click to expand...
Click to collapse
It's a little more involved than just simple file copying as to get it working fully requires changes to the framework-res to enable telephony in the android layer. Below are the changes you make to enable telephony on a rom if you building from AOSP sources but you can use apktool or similar programs to mod an existing rom ( I think these settings are found in the arrays.xml )
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
WHY? Changes these settings enables the Mobile Networks Option in the Settings
Then you'd need to copy the following files from a Nexus3g Stock Rom, Generally you try to match the build ID number to your target when copy system file however it shouldn't make a difference in the case of the Nexus7 because it's all Jellybean.
Code:
/system/bin/rild
/system/bin/pppd ( if it doesn't exist )
/system/lib/librilxgold-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
WHY? the rild ( radio interface daemon and it's supporting libraries ) handle the requests to and from the baseband processor the vendor specific implementation is in this case found librilxgold-ril.so. the permissions files lets the Android UI access the Radio Interface Layer ( through the rild ). pppd - some ril implementations rely on pppd to establish the data connection.
Add or change the following settings in your build.prop file
Code:
rild.libpath=/system/lib/libxgold-ril.so
rild.libargs=-d /dev/ttyACM0
WHY? This is the settings that the ril daemon will use when it auto starts - the name of the vendor library and libargs. The -d switch is the name of the device node that all that juicy 3G data flows.
Make sure the build.prop and any files you change have the correct permission set. Thats 0644 for non exectuable ( everything except stuff in /system/bin ) and 0755 for executable ( rild and pppd ) on some system pppd needs the superuser stickybit setting ( 6755 ) but that doesn't look like the case maybe google are using some off that magic that @leminhnguyen0703 speaks of or parhaps the vendor ril doesn't rely on it in this case
DEBUGGING
Use adb logcat -b radio to see what the RIL Stack is upto as standard logcat doesn't include this information
I think that pretty much covers it.
Reference : Android Platform Development Kit - Radio Interface Layer
@leminhnguyen0703 Now where did I put my wand? LOL
Thnx
trevd said:
LOL.
It's a little more involved than just simple file copying as to get it working fully requires changes to the framework-res to enable telephony in the android layer. Below are the changes you make to enable telephony on a rom if you building from AOSP sources but you can use apktool or similar programs to mod an existing rom ( I think these settings are found in the arrays.xml )
Code:
<resources>
<string-array translatable="false" name="networkAttributes">
<item>"wifi,1,1,0,-1,true"</item>
<item>"mobile,0,0,1,-1,true"</item>
<item>"mobile_mms,2,0,2,60000,true"</item>
<item>"mobile_supl,3,0,2,60000,true"</item>
<item>"mobile_dun,4,0,5,60000,true"</item>
<item>"mobile_hipri,5,0,3,60000,true"</item>
<item>"bluetooth,7,7,0,-1,true"</item>
<item>"ethernet,9,9,9,-1,true"</item>
<item>"mobile_fota,10,0,2,60000,true"</item>
<item>"mobile_ims,11,0,2,-1,true"</item>
<item>"mobile_cbs,12,0,2,60000,true"</item>
<item>"wifi_p2p,13,1,0,-1,true"</item>
</string-array>
<string-array translatable="false" name="radioAttributes">
<item>"9,1"</item>
<item>"1,1"</item>
<item>"0,1"</item>
<item>"7,1"</item>
</string-array>
</resources>
WHY? Changes these settings enables the Mobile Networks Option in the Settings
Then you'd need to copy the following files from a Nexus3g Stock Rom, Generally you try to match the build ID number to your target when copy system file however it shouldn't make a difference in the case of the Nexus7 because it's all Jellybean.
Code:
/system/bin/rild
/system/bin/pppd ( if it doesn't exist )
/system/lib/librilxgold-ril.so
/system/etc/permissions/android.hardware.telephony.gsm.xml
/system/etc/permissions/android.hardware.telephony.cdma.xml
WHY? the rild ( radio interface daemon and it's supporting libraries ) handle the requests to and from the baseband processor the vendor specific implementation is in this case found librilxgold-ril.so. the permissions files lets the Android UI access the Radio Interface Layer ( through the rild ). pppd - some ril implementations rely on pppd to establish the data connection.
Add or change the following settings in your build.prop file
Code:
rild.libpath=/system/lib/libxgold-ril.so
rild.libargs=-d /dev/ttyACM0
WHY? This is the settings that the ril daemon will use when it auto starts - the name of the vendor library and libargs. The -d switch is the name of the device node that all that juicy 3G data flows.
Make sure the build.prop and any files you change have the correct permission set. Thats 0644 for non exectuable ( everything except stuff in /system/bin ) and 0755 for executable ( rild and pppd ) on some system pppd needs the superuser stickybit setting ( 6755 ) but that doesn't look like the case maybe google are using some off that magic that @leminhnguyen0703 speaks of or parhaps the vendor ril doesn't rely on it in this case
DEBUGGING
Use adb logcat -b radio to see what the RIL Stack is upto as standard logcat doesn't include this information
I think that pretty much covers it.
@leminhnguyen0703 Now where did I put my wand? LOL
Click to expand...
Click to collapse
Thank you. It show me right direction. I hope you won't get angry to me. I am actually Acer iconia a701's user. We have weak society. But acer iconia a700's auditory is bigger. There is same situation with 3g.
Now i get working Rom, Except icon of 3G,GSM and working Internet.
I don't get why all peoples thought dass there is no posibility to do it. It is easy enough if to know what to do. Thank you you helped me much.
farstar7s said:
Thank you. It show me right direction. I hope you won't get angry to me. I am actually Acer iconia a701's user. We have weak society. But acer iconia a700's auditory is bigger. There is same situation with 3g.
Now i get working Rom, Except icon of 3G,GSM and working Internet.
I don't get why all peoples thought dass there is no posibility to do it. It is easy enough if to know what to do. Thank you you helped me much.
Click to expand...
Click to collapse
Obviously there maybe be other hardware differences with the Acer in H/W but if you got a ported rom booting and just need the 3G going then you can use this method on pretty much every device provided you can source the RIL files etc, There also maybe some extra bits, like you need to make sure the modem device node has the correct permissions in ueventd.rc ( the N7 wifi model already has this set ), There's a couple of links in my sig regarding stuff I did to get Huawei Dongles working on various Devices. You might pickup some tips from there.
leminhnguyen0703 said:
So I take all the ROMs that are available for both WiFi and 3G model are made with pure magic then ? Hmmm..
Sent from my C6603 using xda premium
Click to expand...
Click to collapse
BURN THE WITCHES OF WHOM THAT PORT!
Sent from my HTC One using xda premium
COLOR="Red"]This thread will discontinue, Now I'm published my new mod's thread under Magisk, that mod includes Whole new ViPERFX app and many other mods and upcomings so From now everybody please follow this thread below:
[Module] ViPERFX
https://forum.xda-developers.com/apps/magisk/viperfx-t3667145[/COLOR][/SIZE][/B]
Introduction:
ViPER4Android is very popular audio mod around the world of Android and probably the best audio mod ever made. But there is so many complexity ViPER4Android couldn't go further through, so I wish "ViPER-FX" could be a project to let our beloved ViPER4Android step in advance. Original V4A details at ViPER4Android Official forum.
Modifications:
+ Based on ViPER4Android v2.5.0.5
+ New Material UI and Icon
+ App rotation enabled.
+ Default install as system app to prevent task kill.
in MIUI or some rom could be installed as user-app
for IRS compatibility [Experimental]
+ The zip edition includes apk.
Recommendation:
* Magisk Manager, Framework installed.
* Android 5.0+
* To update from ViPER-FX v4.0 (v4.0 only) first remove it.
How to install?
* Flash the zip using Magisk Manager or Custome recovery.
# Track this thread using the URL below.
URL: [url]http://forum.xda-developers.com/showthread.php?t=3535401[/URL]
Thanks To:
Code:
[user=4470081]@topjohnwu[/user] for Magisk Framework.
[user=3901724]@zhuhang[/user] and ViPER520 (Founders of ViPER4Android).
[user=4445176]@guitardedhero[/user] | [user=5704037]@repey6[/user] | [user=5210243]@exodius48[/user] | [user=6118476]@#mrk[/user]
for helping/support/testing.
...and those I forgot to mention.
I spend dedicated time, made pressure on brain and did hard work to make this perfect
If you like my post please hit Thanks and give a rate....
~~ Feel The power of ViPER-FX ~~
Contributors
metaspook
Version Information
Status: Stable
Current Stable Version: 4.1
Stable Release Date: 2017-01-13
The long waited finally come, will try this out.
the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
id=v4a
name=ViPER-FX
version=Base v2.5.0.5 | MKM v4.0
versionCode=3
author=ViPER’s Audio | Mod by Metaspook
description=ViPER-FX is a system wide audio enhancing software, modified edition of ViPER4Android.
support=https://www.androidfilehost.com/?w=files&flid=143525
donate=http://vipersaudio.com/blog/?page_id=95
Click to expand...
Click to collapse
@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.
crusader727 said:
the title is a bit misleading:
-this is not [Magisk], this is a [Module]
-it's not 100% clear if you packed the Magisk module or if you also offer a modded App (in thread description)
-it also has the same id as @topjohnwu 's module...
Click to expand...
Click to collapse
Got it... actually I had to make this thread in short time making this of thread n sort it as well as possible is a bit hard something could be missing, but this thread will be more informative, well sorted soon...
Thank you.
exodius48 said:
@metaspook
Can you delete V4A app inside "\system\priv-app\ViPERFX" in next release? Because if V4A app installed inside /system/ there will be no sound improvement by IRS. Tested on my device running MIUI rom, dunno on other rom.
I use sepaker & many times change the IRS, but no sound improvement.
Click to expand...
Click to collapse
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.
metaspook said:
Do u'v installed Magisk n flash the zip through it?
B'cz this is a whole new way to dealing with system.
If u did but after that also don't work let me know.
Click to expand...
Click to collapse
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
OK I'll release next update separately..
I can't tell whether or how this differs from the existing V4A module offered by topjohnwu.
Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
Code:
/data/magisk/sepolicy-inject --live -s mediaserver -t mediaserver_tmpfs -c file -p read,write,execute
/data/magisk/sepolicy-inject --live -s audioserver -t audioserver_tmpfs -c file -p read,write,execute
2. Why are the following folders blank?
Code:
system/etc
system/lib/soundfx
system/vendor/etc
oreo27 said:
Cool. I'd like to try this out. I just had some questions:
1. What do these commands do:
2. Why are the following folders blank?
Click to expand...
Click to collapse
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:
metaspook said:
1. It helps to keep Viper FX alive in SELinux enforcement.
2. Into these directories necessary files will be extracted or pulled from original /system.
Thanks to wanna know. :good:
Click to expand...
Click to collapse
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.
Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...
oreo27 said:
Oh. I didn't think to check in the update-binary. It feels like this is a complicated script for sure:
Code:
# Push files
unzip -oq $ZIP "system/*" -d $MODPATH
unzip -pq $MODPATH/system/priv-app/ViPERFX/ViPERFX.apk assets/libv4a_fx_jb_$DRVARCH.so > $MODPATH/system/lib/soundfx/libv4a_fx_ics.so
ui_print "[OK] Pushing files."
# Config files modification.
for X in /system/etc/audio_effects.conf /system/etc/htc_audio_effects.conf /system/vendor/etc/audio_effects.conf; do
cp -af $X $MODPATH$X
sed -i '/v4a_fx {/,/}/d' $MODPATH$X
sed -i '/v4a_standard_fx {/,/}/d' $MODPATH$X
sed -i 's/^libraries {/libraries {\n v4a_fx {\n path \/system\/lib\/soundfx\/libv4a_fx_ics.so\n }/g' $MODPATH$X
sed -i 's/^effects {/effects {\n v4a_standard_fx {\n library v4a_fx\n uuid 41d3c987-e6cf-11e3-a88a-11aba5d5c51b\n }/g' $MODPATH$X
done; ui_print "[OK] Config modification."
Does this mean that if I uninstall this mod, Viper is completely uninstalled without any changes present in my entire device? If so, it's a pretty good implementation.
Click to expand...
Click to collapse
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.
Didgeridoohan said:
Nice! Works just fine on my Nexus 6. Will this be submitted to the Magisk repo? Would be useful to have it in the manager...
Click to expand...
Click to collapse
Thanks... yes I wish also soon.
exodius48 said:
Yes bro, i already used magisk long time ago.
Recently compared with V4A original (installed as user app /data/app/) & V4A module by topjohnwu, my device can read IRS and has sound improvement.
I don't know this issue is MIUI related or not, but I always get that issue if V4A app installed as system app (/system/app or /system/priv-app).
Click to expand...
Click to collapse
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???
Is not working for me, IS activated on Magisk Modules Install,
But V4A say "Install/Update now?", Samsung S5 G900m, Is rooted using SuperSU 2.79, Latest Magisk Manager/Installer,
I Installed this V4A why magisk "Refuses" to open Modules download page "No Modules Found", And i have to download manually from internet. (SafetyNet says RED, Root and Magisk is green in Magisk Manager)
V4A is installed as System App, And SELINUX is Permissive,
I Try to change V4A to user APP, But not working;
metaspook said:
Actually I pushing the apk into the system cause if Viper install as user app in data, 3rd party or internal app killer kill it and Viper looses to output the effect even also when remove from recent list. but I have an idea if its just happens with your MIUI rom... can you give me your ROM's 'build.prop" file ???
Click to expand...
Click to collapse
Yes you're right. But on MIUI (especially MIUI 8 on my device) i can control it. We can lock app into taskbar and turn off MIUI optimization for selected app by turn off background restriction. Those will prevent MIUI kill running app.
build.prop file attached. :good:
metaspook said:
1. The code I wrote looks a bit complicated but its for to reduce the size of the module (you can see I didn't packed the driver separately, codes are extracts those from the apk) and for more task will be done in less lines.
2. Yes.. obviously that's why using Magisk framework is so useful. It wont change anything in /system while installing nor in uninstalling your /system would be intact.
Click to expand...
Click to collapse
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.
oreo27 said:
This is pretty good. I installed this and it's working great. Just a quick question, I don't suppose it can work on phone calls as well? I was looking to get my bluetooth volume increased.
Click to expand...
Click to collapse
Not sure about it... Test urself, look can work or not