Database Develop

Install KERNELS WITH KEYPAD DRIVERS AS MODULES ????

I use the kernel : (source)
KERNELS WITH KEYPAD DRIVERS AS MODULES
Duckly's Kernel [Turbo Kernel] [27-3-2011]
Change Log:
**GPU Overclocked (PLL1 Overclocked From 768 To 960Mhz)
Compiled With GCC 4.4.3
Updated Source Code
Compiled With Performance Optimizations (-O2) Instead Of Small Size (-Os)
Added And Modified Battery Driver (From SP3DEV)
No Sleep Of Death
Compcache Driver Added
Tiwlan Wifi Driver Added
Updated Headset Driver (From SP3DEV)
Added compcache driver
Available RAM 200MB
Included Extra IPtable Modules For WiFi Tethering
No Key Freeze
Note:
Add line in startup "acpuclock.force_turbo=1 clock-wince.grp=0xa92"
I've replaced two file "modules-2.6.27.46.tar" and "zImage" in npkboot, but I do not understand the :
(Add line in startup "acpuclock.force_turbo=1 clock-wince.grp=0xa92").
I have to copy add this line anywhere in the file "Startup"? or should I replace this line instead of the "clock-wince.grp = 0xa92" located at the end of file "startup"

At your "startup" file in the npkboot folder, open it and add in acpuclock.force_turbo=1 clock-wince.grp=0xa92. If your startup file already have this command line then no need to add.

add to the problem is where, first, last, middle or where??
this is the file "startup" of me: http://www.mediafire.com/?ll1h96pr3wk7533
Help Me !!!

Replace your startup command with mine:
set ramsize 0x8000000
set ramaddr 0x10000000
set mtype 2006
set INITRD_OFFSET 0x608000
set KERNEL zImage
set initrd initrd.gz
set cmdline "rel_path=npkboot fbcon=rotate:2 ro.sf.hwrotation=180 lcd.density=240 msmvkeyb_toggle=off msmts_calib=0x0366.0x04b.0x0c8.0x038e clock-wince.grp=0xa92 acpuclock.oc_freq_khz=652000 pmem.extra=1 no_console_suspend physkeyboard=kovsq msmsdcc_1bit msmsdcc_fmax=14000000 hw3d.force=1 acpuclock.force_turbo=1 "
boot
Click to expand...
Click to collapse
Hopes it help..

after replacement is complete, copy 2 file "modules-2.6.27.46.tar" and "zImage in npkboot is completed, also be modified with Terminal Emulator ???? (I have to modify more by Terminal Emulator ???)
Ex :
su
mkdir /data/opt
cp /sdcard/autostart.sh /data/opt
chmod 755 /data/opt/autostart.sh
I can't understand ????

if you are using KERNELS WITH KEYPAD DRIVERS AS MODULES then no need to do that step, because using terminal method is for keyboard freeze problem. Your kernel should not have such problem.

but after I replace the 2 files in kernels AS DRIVERS WITH KEYPAD MODULES then start Android, the keyboard does not work. I use the Android Honeycomb Froyo V3
I do this :
- I download 2 file "modules-2.6.27.46.tar" and "zImage on,
- Replace them into the folder npkboot then run harset.exe
This is right ????

Yeap this is the correct way, I'm just curious about why your keyboard still does not work even though kernel as driver with keypad modules already installed.

I see you also use the X1 has a ROM like me, KERNELS WITH KEYPAD DRIVERS AS MODULES not you use?, please guide me how to install. Thankss.
I download this file: HERE then extract and replace them (2 files) into the folder npkboot then start Hartset.exe and Keyboard doesn't work
oh And when I use the kernel include in Honeycomb Froyo V3 6 / 7, then Terminal Emulator not turn up the virtual keyboard ???

I'm using Honeycomb Froyo V3 by Needo and using the turbo kernel ( keypad drivers not as modules ) included in the ROM, so far no keyboard freeze for me.
1. Did you try to lower your CPU speed like 614Mhz or 575Mhz??
2. Did you try this kernel? This kernel is posted by Needo to solve the keyboard freeze problem
3. Or you can try to reinstall the ROM by reformatting your SD card to 4 partition then install Honeycomb Froyo V3 again.
And yes, Terminal Emulator will not turn up the virtual keyboard and you must use the phone keyboard to type in commands, but for you I think it is impossible to do that..

but when I replace it with KERNELS WITH KEYPAD DRIVERS AS MODULES the virtual keyboard is turned on, the keyboard freezing error only happens occasionally one day / one time but instead KERNELS WITH KEYPAD DRIVERS AS MODULES then boot from the keyboard not working
I do not understand, I do to use kernels WITH KEYPAD MODULES AS DRIVERS?, I want to fix complete and use the keypad ?????
My CPU Clock : 600000 in Startup.txt

I can't promise that the keyboard will never freeze after you install the KERNELS WITH KEYPAD DRIVERS AS MODULES. If you are using Honeycomb Froyo by Needo, you can use the Fast Reboot app pre-installed in the ROM to activate back your keyboard, and try to lower the cpu speed to 575Mhz.

thank you very much for your enthusiasm, I want to ask why the kernel included in the ROM Honeycomb Froyo V3 is the virtual keyboard does not work?
And why I have set right all that as soon as the boot keyboard did not work?
Thanks You

h_pro9x said:
why the kernel included in the ROM Honeycomb Froyo V3 is the virtual keyboard does not work?
Click to expand...
Click to collapse
For this you should ask the developer, I'm just trying my best to answer your questions based on my knowledge, and welcome..

Thanks
Oh, by default the Honeycomb Froyo V3 button camera is not Home(it is Standby)?? So my X1!

Yes, Honeycomb Froyo V3 camera button is set as Standby ( turn off the screen ) by default

Xposed Internals & Requirement of Reboots

Is there any reason why de-/activating modules needs a reboot?
If I got it correctly, the modules are loaded in the XposedBridge on start-up of Zygote: github.com/rovo89/XposedBridge/blob/art/app/src/main/java/de/robv/android/xposed/XposedBridge.java#L105
However, can loadModules() be used dynamically, such that a reboot would be not necessary anymore when reinstalling modules?

If it were that simple, don't you think rovo89 and the other Xposed devs would have found a way to do that by now?
Hint: It's probably not as simple as that.

How to install Viper4android Fx on Moto X Android 6

Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!

Well mine has problem of installing the sound driver.
通过我的 XT1096 上的 Tapatalk发言

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
How did you install the viper4android via apk or you flashed from recovery?

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".

duongnv1996 said:
Hi guys, I could not run Viper4android application on my device (android 6) . I haved installed apk then install driver . But Not thing change in sound effect. I tried to search and did not find out any error?
I need some help to run app with effect sound when play music!
Thank inadvance!
Click to expand...
Click to collapse
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
KazuhiroYasei said:
In order to install ViPER4Android, you'll need your system to be properly rooted, BusyBox must be installed, and SELinux Mode must be "Permissive".
I recommend this BusyBox installer, and you can get SELinux Mode Changer from here.
Then, after everything is properly set up, you must also disable your ROM (e.g. CyanogenMod-based ROMs' AudioFX)and/or player (e.g. Poweramp's equalizer)'s built-in equalizer, and switch ViPER4Android's FX Compatible mode from "Normal" to "Compatible".
Click to expand...
Click to collapse
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.

brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.

KazuhiroYasei said:
Was this procedure required for V4A to work on your Victara? Mine worked in every ROM I tested (all Marshmallow-based) by following the steps you quoted.
Click to expand...
Click to collapse
Yes. I was only able to enjoy v4a after this procedure.

It's worth pointing out that V4A is going to F up your Moto Voice

Popping into this thread real quick to provide some info,
Using compatibility mode with V4A is bad news, causes extra battery drain and problems with some apps.
For every single rom and device I've used 5.0+ I've followed the same procedure to install V4A, without using compatibility mode, without having to delete a file every time, etc.
Flash the "lolliviper" zip attached to this OP.
Followed by the "Build.Prop-Tweaks" and "Soundfix-LibFiles" attached to this post.
You'll also need a way of setting selinux to permissive after every boot if you're using CM or something else with selinux set to enforced. Something like SELinuxModeChanger available here will work.
If you don't have busybox installed, V4A will tell you and help you install it.
The V4A version included in the "lolliviper" zip is not the newest , you'll need to "Check Update" via the 3 dot menu and install the latest apk.
After all this, install the driver via the V4A app, reboot, and you're golden.

Flipz77 said:
It's worth pointing out that V4A is going to F up your Moto Voice
Click to expand...
Click to collapse
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?

brunoperissotti said:
Didn't know that. I was only able to set v4a on a custom ROM, so that ship was long gone hahaha
it just stops working?
Click to expand...
Click to collapse
Actually it still "works" because it detects your launch phrase, but after that, half of the time it just hangs without hearing your command. Sometimes it'll randomly work, but it was too much of a botch to keep it that way. I've now resorted to Noozxoide Pro: it's still a system-wide mod with modes for headset, speaker and BT, but it's installed as a "standard" app, it doesn't mess with your system and it sounds boss!

I ran across this link on a similar search on the google machine, and it made V4A installation a breeze. No manual messing with kernel settings and whatnot: http://forum.xda-developers.com/android/software/viperaudio-viperatmos-3-8-sq-driver-t3289075
Battery life has been fine running this for about a week. I don't use Moto Voice so can't comment on that.

THANKS
brunoperissotti said:
I was able to make V4A work on my Moto X 2014 with a fix.
If you do not have Busybox or permissive SELinux, follow the instructions our mate's posted above:
After Busybox installed and SELinux on permissive, you flash the Viper zip and install the driver. Right after that you open a root enabled file manager and find system>vendor>etc. You'll see an audio_effects.conf.
(I suggest making a safe copy of this file).
Rename the original audio_effects.conf to audio_effects.bak.
Save and reboot. Now try using v4a again.
Click to expand...
Click to collapse
Thanks a lot, I was already discouraged, tried several versions of viper, on diferent roms, this was the only solution, but is necessary to remember that for this file to appear in the folder, you need to open the application and save a profile, even if empty, without it you can not find the file audio_effects

If u root ur device using magisk, u can install viper magisk module...it works fine on android 6.0 with selinux enforcing..
Sent from a Motobot

Issue with new Xposed Installer 3.1 (coming from DVDandroid's fork)

With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards

Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
If you have disabled the framework, restart your device and uninstall the modul which makes problems

Imagine, you have installed a whole bunch of modules and you need to find out which one is causing the trouble ...
The installer just shouldn't disable the enable/disable checkboxes in the modules list on purpose in case of a framework not installed state and everything is fine. At least it was implemented like this pre 3.0

Edgar_M said:
With the new installers modules can't be enabled/disabled when the framework is not active.
This is a problem if one has to run the Xposed uninstaller to get out of a bootloop and wants to disable single modules afterwards
Click to expand...
Click to collapse
There is a flashable file to disable all modules from recovery
Sent from my SCH-R220

Edgar_M said:
Hi mattzeller! Thanks for your contribution to that topic. But please read the original post once again. Then you will see, that you are missing the point with your post. Not a big deal - let's just try to keep the good quality of XDA alive
Click to expand...
Click to collapse
I fully understand your original post. If you are in a boot loop because of a specific module, disabling all of them will ensure you get out of a bootloop without removing Xposed completely so you can figure out which one it is via logcat. If it is Xposed itself causing the bootloop, it doesn't matter what modules are installed or activated.
Sent from my SCH-R220

[TOOL] Samsung Xposed Safe Mode script

Samsung Xposed Safe Mode script v1.0
What does it do?
This is an init.d script which emulates the xposed safe mode where you can press any button during boot, get a vibrate (to know it detected you), and it will disable all your xposed modules. To be used in case of bootloops because of incompatible modules.
This only disables all modules so that you can boot. It does NOT actually uninstall or disable xposed itself.
Why would I need this?
I talked with the developer of xposed for Samsung, wanam, and apparently, xposed safe mode was disabled for Samsung devices due to a Knox issue (if you disabled xposed, Knox will hate you and refuse to boot the phone). This is good, but if you have a bootloop, AND you're on a bootloader locked device, you have NO CHOICE but to wipe your data. Ouch!! That's a heavy penalty for accidentally installing one malfunctioning module!
Or maybe your phone still is bootloader unlocked, but you're running Samsung xposed and safemode is still disabled for you. Then you'd rather have xposed safemode back just for the ease of not having to go through recovery to fix things.
How does it work?
1. Press any of three buttons during boot (volume keys, or home button). You have 10 seconds from bootup to choose to do this.
2. System will give you 2 short vibrates to tell you it detected it.
3. Press any button 4 more times, each time will give you another short vibration.
4. One long vibration will signal to you that xposed has been disabled.
5. The script will automatically reboot your device in 6 seconds. This is because we can't disable xposed, so xposed will STILL load modules on this bootup, which means you'll still see the bootloop momentarily until you reboot.
Great! How do I install it?
This is an init.d script, so you need init.d support in your phone. Obviously, if you have a bootlocked device, you probably don't have init.d support. This is not a guide on how to get init.d support, but I'll offer you a few tips you can use to search yourself.
- install-recovery.sh, since it's called by init.rc during boot, can be hijacked in order to create an init.d system.
- If install-recovery didn't work, SuperSU also includes an su.d directory which is executed at a similar time. Just throw a script in there, or throw a script in there which enables use of the init.d folder (run-parts /system/etc/init.d).
Anyways, here's how you install it:
- Place the script you downloaded into
Code:
/system/etc/init.d
OR
Code:
/system/su.d
Give the script proper permissions for the folder it's in
- For su.d folder, it is root:root 0700 (rwx------)
- For init.d folder, it could be a variety of permissions. My init.d folder runs as a result of su.d, so I gave it same permissions as su.d. If yours doesn't, then you might want to try root:root 0755 (rwxr-xr-x)
- The important point here is to make sure it's at least root user and group, readable and executable, rwxr-xr-x
Will it work on my device?
It should work on any device really, if you follow the simple instructions. But I've only tested it on the ATT S4 (Lollipop 5.0.1), so I can't guarantee it will work on your device. Test it out and see if it works for you! It probably will!
You saved me!
I'm glad to hear that! I love to hear and see a thanks, so make sure to click the thanks button and maybe write a post too!
Bugs and problems
You know how to report bugs and issues. State all relevant information related to the problem; device, problem in clear detail, with reproducible steps, and anything else you might need.
Related custom xposed builds
Here are a list of Samsung custom xposed builds I know this "safe mode problem" to be present in. (Don't forget, this problem is likely to be in any and all Samsung xposed custom builds due to the nature of the Knox problem).
[UNOFFICIAL] Xposed for Samsung Lollipop by arter97
[UNOFFICIAL][5.0][v87.1][03 Dec] Xposed for Samsung Lollipop 5.0.x
[UNOFFICIAL][5.1/6][v87.1][28 Nov]Xposed for Samsung Lollipop/Marshmallow
Disclaimer: As usual, while I've made every attempt to make it perfect, there are no guarantee it will work for you. By using this, you agree not to hold me accountable in case something bad happens to you (or it didn't save your device)! Do your own testing to make sure it works before you actually need to use it in an emergency!

FAQ
It didn't vibrate
You probably have a different device which places the vibrator in a different location. I don't have your device, so maybe you'll need to help me debug and find where the vibrator is located at.
It didn't work!
What happened? Give me some detailed information about exactly what you did, what happened, and the device you're on!
Some possible problems to investigate are:
Does the script have correct user: owner and permissions?
Is your init.d or su.d system even working? Make sure it is first

Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.

wanam said:
Nice work!
It should help with incompatible modules leading to a bootloop, but it won't prevent Xposed from loading, the flag "/data/data/de.robv.android.xposed.installer/conf/disabled" is ignored on my Xposed version, done here for a reason, i got many bootloop reports in the past by people accidentally triggering safe mode by physical buttons, leading to Knox refusing to deal with modified binaries.
Fortunately it does not seem to be the same with TouchWiz 7.0, so i will bring it back later for Nougat.
Click to expand...
Click to collapse
Thank you!
It certainly will help a lot for disabling incompatible modules. Yes, although it doesn't technically disable xposed itself. It's really great that future versions aren't that way!
I actually thought of creating another script which utilizes back and menu key buttons to actually uninstall xposed from backups (an actual disable xposed script of sorts), but I thought it was too much.