So, I have a MTK device, a chinese one.
I just finished my first ROM port. I expected to be problems.
The things I can´t solve:
-The sound (everything related to) -> yes, I tried to replace libaudio.primary.default.so
-The buttons (Power, Volume ones, and Camera).
If someone can, plesase help me.
popoNXN said:
So, I have a MTK device, a chinese one.
I just finished my first ROM port. I expected to be problems.
The things I can´t solve:
-The sound (everything related to) -> yes, I tried to replace libaudio.primary.default.so
-The buttons (Power, Volume ones, and Camera).
If someone can, plesase help me.
Click to expand...
Click to collapse
For the button mapping issue I would recommend pulling /system/usr/keylayout/yourdeviceslayout.kl from the stock ROM looking at the power, volume, and camera keys on that then changing the key layout file on the port ROM. For audio make sure you've included all the audio libraries needed others are likely needed besides libaudio double check the libs folder.
No way
shimp208 said:
For the button mapping issue I would recommend pulling /system/usr/keylayout/yourdeviceslayout.kl from the stock ROM looking at the power, volume, and camera keys on that then changing the key layout file on the port ROM. For audio make sure you've included all the audio libraries needed others are likely needed besides libaudio double check the libs folder.
Click to expand...
Click to collapse
So, I made another ROM including all the stock audio libraries, and what I got is a bootloop.
popoNXN said:
So, I made another ROM including all the stock audio libraries, and what I got is a bootloop.
Click to expand...
Click to collapse
Did the keyboard trick I suggested work for you? Check what audio libraries rely on the main audio library you were using before.
One step
shimp208 said:
Did the keyboard trick I suggested work for you? Check what audio libraries rely on the main audio library you were using before.
Click to expand...
Click to collapse
Yes, the keys are fixed now.
I tried replacing the libraries one per one, in some different sequences. Nothing worked.
Related
Apologies, that's the best way to discribe it.
I have searched the forums for this but it's difficult to find someone that has the same scenario as me. Am using lates Darkstone build with NRG light rom. Radio is 20.12 and I have the media folder (with all contents in the root of my SD card).
The problem is, is that I get sound - for a while, then it goes. When this happens and I make a call, there is no sound ringing sound the other end but it does ring apparently. They answer but obviously they dont hear and I am hearing nothing. This also happens with Mattc build.
I've tried radio rom 20.10 but the same issue happens.
Does anyone know of this issue and it's resolution. It is obviously rendering the build useless to me.
Thanks
have you tried to switch the zImage?
wilwilwel said:
have you tried to switch the zImage?
Click to expand...
Click to collapse
Thanks for responding. I dont really understamd the whole kernal zimage thing. I just trust what ever's in the Adroid folder. But I'll try anything!
How do I decide which zimage to try? And do I just copy and paste it over the one in the folder (obviously reinstalling Android again after)?
Thanks.
Hi,
I've installed CM7.2 on my RHOD but the layout of HW keyboard is wrong. How can I change it to us layout?
Cheers,
Tom
It should 'detect' your keyboard layout.
Do other NAND ROM's have this issue?
I'm not sure, only NAND I tried was the CM7.2
_eph said:
I'm not sure, only NAND I tried was the CM7.2
Click to expand...
Click to collapse
At least give OMGB a shot...
Although, IIRC CM7.2 from Mr. Walter detected my keyboard no problemo. I'm sure we can get the right one shoehorned in, I'm just curious if it happens to you on other ROM's.
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
You could try copying the keyboard map file from the rom that worked to the one that didn't.
_eph said:
Ok, I've tried OMGB. The layout of normal letters/numbers seems to be correct but the function keys seem to be broken. Fn types @, Ctrl lights up the FN led but doesn't act like Fn, arrows are wrong (up is left, right is up, left is down, down is left).
Any more ideas?
Thanks
Click to expand...
Click to collapse
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
wizardknight said:
You could try copying the keyboard map file from the rom that worked to the one that didn't.
Click to expand...
Click to collapse
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
_eph said:
CM & OMGB were the only android roms I tried. Keyboard didn't work properly with neither of them. I used haret with win6.5 rom before. Can I use keyboard map from win rom?
Click to expand...
Click to collapse
WM and Android are totally different. Haret and nand android will probably work ok though.
arrrghhh said:
You never even stated which RHOD you have... I kind of assumed "US" layout meant one of the US RHOD's, but it sounds like you have something different.
So which one is it?
Click to expand...
Click to collapse
I've got RHOD110 (got it in New Zealand).
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
_eph said:
I've got RHOD110 (got it in New Zealand).
Click to expand...
Click to collapse
wizardknight said:
The 100's have a awful time with issues, and you have an odd subset of that. No wonder you are having trouble.
You will probably have to make your own keyboard map.
Click to expand...
Click to collapse
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
arrrghhh said:
This ^^.
I think someone might've made a layout for F22's rootfs - you can poke around there and re-use it perhaps. Otherwise, you will have to make your own layout. There's really not many with the 110, at least not interested in this project... so the layout isn't solid. I think the 100 still has layout issues with the FN and CAPS key as well.
Click to expand...
Click to collapse
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
_eph said:
Can you please point me to correct direction regarding this? Where is that keyboard map located? How can I reuse it?
Thanks
Click to expand...
Click to collapse
http://www.kandroid.org/online-pdk/guide/keymaps_keyboard_input.html
arrrghhh said:
One nice thing about NAND, the files are easily edited before flashing.
For example, CM7.2.0-RC1-rhodium-GSM-kernel-3.3.6-201200523.zip\system\etc\keymaps\ is where the keymaps are.
I'm not sure which one your device is getting mapped to... and I'm also unsure of what you need to do to get yours detected properly. Sorry I can't really help more...
Click to expand...
Click to collapse
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
akk29 said:
I am having the same problem of an incorrect HW Keyboard layout on GBX0* + 3.4.17 kernel - update 11/7/12 using a UK Rhod 100. In system/usr/keylayout/ the qwerty.kl file is correct and can be editted and the changes persist after a reboot. I was able to map the end call key to home.
However the microp-keypad.kl file which contains the keymap for the HW keyboard is incorrect and matches the default layout in system/etc/keymaps/default. Any changes made to this file have no effect and after a reboot the files changes back to the default one. The files I need are in system/etc/keymaps/rhod100_uk. i have also tried editing the default layout files with no success. Again after a reboot they revert to the original files.
I had a similar problem with the CM7.2 NAND ROM. While using the 2.6.27 I was able the use the correct keyboard layout however after flashing a kernel update to 3.3.6 the keyboard layout was incorrect (and was the default layout).
I am unable to find any .kl files in the GBX0 zip and therefore I am unable to make any changes prior to flashing.
Thanks all those still developing for the Rhod.
Click to expand...
Click to collapse
GBX0* is a different rom than CM7.2, and will have many files in a different place. You would be better off making a new thread, or posting the the thread for that rom.
I see that this issue has now been tackled in the ROM development thread. I will download the new package. (Sorry I was unable to post in that thread)
Stock KK rom for my phone have a big problem in LK.BIN module, LCD driver is not choice correctly.
I opened the file with a binary editor and i can see there are 3 LCD driver included the correct driver for my display, but auto detection choice the wrong one, so only random lines appear on screen.
There is a way to modify LK.BIN to remove the wrong driver and leave only the correct one?
Or there is a way to force manual detection of display driver?
ilmira said:
Stock KK rom for my phone have a big problem in LK.BIN module, LCD driver is not choice correctly.
I opened the file with a binary editor and i can see there are 3 LCD driver included the correct driver for my display, but auto detection choice the wrong one, so only random lines appear on screen.
There is a way to modify LK.BIN to remove the wrong driver and leave only the correct one?
Or there is a way to force manual detection of display driver?
Click to expand...
Click to collapse
I would recommend taking a look at this article, which also deals with modifying the little kernel binary file. If you can figure out what lines are dealing with the other display drivers and comment them out or remove them, another resource would be this online dissembler that tells you what's going on in the code. As always make a backup of the unmodified file and be very careful as you could modify the file to the point where the phone won't boot or display anything at all.
thanks a lot for your answer, but there isn't any useful info in links you gave me.
what else i can try ?
ilmira said:
thanks a lot for your answer, but there isn't any useful info in links you gave me.
what else i can try ?
Click to expand...
Click to collapse
What is the model and manufacturer of your device?
shimp208 said:
What is the model and manufacturer of your device?
Click to expand...
Click to collapse
my device is a Mediatek based phone, model Doogee DG2014
No other ideas?
ilmira said:
No other ideas?
Click to expand...
Click to collapse
Sorry for the delay in getting back to you another idea would be going into the engineering device menu from the dial pad and seeing if you change things that way sometimes you can do it that way.
Are you sure there is an option to select LCD driver inside engineer mode menu ?
ilmira said:
Are you sure there is an option to select LCD driver inside engineer mode menu ?
Click to expand...
Click to collapse
Other people have mentioned similar options before on Mediatek based devices however sometimes not all engineering mode menu items can be used.
https://www.apkmirror.com/apk/lgelectronics/lg-camera/
I downloaded the new version of the LG camera from the above website, which could be installed normally, but couldn't be opened, there is an error message: unfortunately, the camera has stopped, however, I can open the front camera by long pressing the menu in the camera icon. The rear camera still can't work. How can I make the rear camera work normally?
I think that, although the package name is the same, the version 7 of the LG Camera has been taken from another phone. Of course there are many brilliant developers on XDA, but I don't think that making that app work is just a matter of bug fixing.
wuri said:
https://www.apkmirror.com/apk/lgelectronics/lg-camera/
I downloaded the new version of the LG camera from the above website, which could be installed normally, but couldn't be opened, there is an error message: unfortunately, the camera has stopped, however, I can open the front camera by long pressing the menu in the camera icon. The rear camera still can't work. How can I make the rear camera work normally?
Click to expand...
Click to collapse
it's to do with the camera_config file in system/etc.
if you have root, you can modify the file to get it working.
if you look at some ROMs avaliable, they have LG Camera 7 working, you may be able to use their files as a guide to modify your config to work.
jc9896 said:
it's to do with the camera_config file in system/etc.
if you have root, you can modify the file to get it working.
if you look at some ROMs avaliable, they have LG Camera 7 working, you may be able to use their files as a guide to modify your config to work.
Click to expand...
Click to collapse
Thank you, my mobile phone model is h868, cannot be rooted, it seems no way to solve.
wuri said:
Thank you, my mobile phone model is h868, cannot be rooted, it seems no way to solve.
Click to expand...
Click to collapse
[url]https://www.dropbox.com/s/ge8rqmfpy3nluh9/LG%20Camera%207.zip?dl=0[/URL]
try this out, not sure if it works. it does not replace your stock camera app, so you can still use that.
unzip and copy camera_config.xml to the root of your internal storage (/sdcard)
install the contained app normally, no root needed.
from my testing, everything works except cine mode, food mode and popout. Wide angle is a tiny bit odd. Manual video and Graphy features avaliable too.
Feel free to edit the config file to add or remove options.
Tested on a H860
jc9896 said:
[url]https://www.dropbox.com/s/ge8rqmfpy3nluh9/LG%20Camera%207.zip?dl=0[/URL]
try this out, not sure if it works. it does not replace your stock camera app, so you can still use that.
unzip and copy camera_config.xml to the root of your internal storage (/sdcard)
install the contained app normally, no root needed.
from my testing, everything works except cine mode, food mode and popout. Wide angle is a tiny bit odd. Manual video and Graphy features avaliable too.
Feel free to edit the config file to add or remove options.
Tested on a H860
Click to expand...
Click to collapse
I tried and it worked, it's amazing, but some features are still faulty, as follows: cine video, popout, food, panorama, 360panorama, flash jump-cut, and application will crash when click sticker in self-timer mode, and can not change photo storage to sd card, thanks for your job, you are very kind.
wuri said:
I tried and it worked, it's amazing, but some features are still faulty, as follows: cine video, popout, food, panorama, 360panorama, flash jump-cut, and application will crash when click sticker in self-timer mode, and can not change photo storage to sd card, thanks for your job, you are very kind.
Click to expand...
Click to collapse
some features are impossible without root as they require files in the system.
those features you mentioned require files not included with the G5.
jc9896 said:
some features are impossible without root as they require files in the system.
those features you mentioned require files not included with the G5.
Click to expand...
Click to collapse
I get it，thanks.
Hi there,
This is a copy paste of my post I made on reddit.
( https://www.reddit.com/r/Mi9T/comments/fcmplg/viper4android_profiles_for_mi_9t_k20_lets_share/ )
I've been messing around with V4A since yesterday and feel like we should share profiles and ressources, as I didn't find anything worth it for Mi 9t / k20 .
So here are my two cents and I hope you'll join in with yours.
First, ressources.
I downloaded an IRS pack (300+ samples) to use with the convoler option (put the files in /VIPER4ANDROID/KERNEL then load one within V4A). It changes everything. There are a lot of them on the net, just look for .irs files (impulse response sample). There's also an official link for this on the V4A xda lab page.
Here's the link to the one I used : https://forum.xda-developers.com/zenfone2/general/collection-convolver-samples-389-t3140299
Now, profiles (or is it presets ? ).
IMPORTANT EDIT : I use Ainur Narsil, the following profiles will probably sound a lot different if you don't ! I recommend that you do by the way (just be careful with the headset volume then, its max can kill a man !).
Here's my headphone profile, which I'm really happy with, I couldn't stop listening to music when I finished it. I used "basic" Iphone earphones while setting it up :
https://mega.nz/#!BnYiCayY!TbKgbA1Pn9gkth0S-Qu8j-KymR-Cn58R8iUQt1ddfdI
In case it wouldn't be saved within the .xml, it uses FRC - Sennheiser HD 595 (50% Correction).irs at 0% cross channel (included in archive).
Here's my speaker profile. I was satisfied with it yesterday but not that much now that I tasted the one above. I probably can't do as good with the phone speaker as with headphones but still. It looses in gain and has to be even further lowered because it otherwise saturates (distords ? - not sure about my english here). So there's definitly room for improvement here but still :
https://mega.nz/#!YvICnCwT!wMy5A1vrQ2UmHUDiA_oxqezvX7xX2n3z6b5o0AP 5aCs
This one uses Clear Bass +3 & ClearAudio+ 70.irs at 100% (included in the archive as well).
(Re)Edit : Here's my new speaker profile, I feel like it's the best I can do, and I'm quite happy with it, let's hope I still am tomorrow ! It uses Clear Bass +.irs at 16% cross channel (included in the archive of course). Enjoy !
https://mega.nz/#!pvoRQBRb!B4ew2eK1HZW49TJ9kQoZ_7v6o-2hWMi2rhBktCj2e14
That's it, I hope it will help and start an exchange thread.Please share yours if you feel like it... especially the speaker ones !
Cheers
Excellent, mate! Thanks for sharing!
Gonna test them asap
Good morning.
Any tutorial or video to install V4A and driver?
How do I install the zip file of your profile?
Thank you.
wahuka said:
Good morning.
Any tutorial or video to install V4A and driver?
How do I install the zip file of your profile?
Thank you.
Click to expand...
Click to collapse
Hi there, here is the guide I followed. Just as they say it's kind of a hit or miss, try again and if it doesn't work, try harder !
A note about it though, in my experience it seems to work better in the long term when one keeps AML activated in the end, so try to do that first, and again if doesn't work at first, insist for a bit, just in case.
*ah, sadly I'm a new user so I can't post links yet. The guide is on the website "the custom droid dot com" all attached , use the search engine on it and look for : "How to Install ViPER4Android on Android 10 Q (Fully Working)", you'll find it .
Now regarding presets archives, once everything is installed and working, unpack the archive in /Viper4Android , just use a file manager, the folder is not hidden or anything. It will paste kernel into kernel and presets into presets. Then, in V4A you just log press the speaker (or whatever) icon on the bottom and release, it will prompt the menu to load your presets.
Just so you get everything, the kernel folder contains those .irs files for the convolver option. The presets folder contains the presets files (right ? ) with all the tweaks settings.
I hope it helps.
Cheers !
wahuka said:
Good morning.
Any tutorial or video to install V4A and driver?
How do I install the zip file of your profile?
Thank you.
Click to expand...
Click to collapse
This works also for Mi 9T:
https://forum.xda-developers.com/k20-pro/themes/guide-viperfx-miui-11-android-10-t3994621
Thank you both.
I'm going to follow the tutorials to try.
I just installed Viper 2.7.1.0.apk, there's no need for flashing...
Sent from my Redmi K20 using XDA Labs
Actually, using combo V4A + Equilizer:
https://play.google.com/store/apps/details?id=music.basss.booster.effect.equalizer
In the Equilizer app using only equilizers, turned down Boosts, Virtualization and so (using V4A instead)
Hi, I have an issue with presets.
I have extracted the 2 zip but when I long press in Viper4android nothing appears.
What should I do ?
Anakill said:
Hi, I have an issue with presets.
I have extracted the 2 zip but when I long press in Viper4android nothing appears.
What should I do ?
Click to expand...
Click to collapse
There are three different actions, on short press, long press and mid-long press (you need that one). So lttle experiment with your finger
zgfg said:
There are three different actions, on short press, long press and mid-long press (you need that one). So lttle experiment with your finger
Click to expand...
Click to collapse
Actually, I've found the mid-long press but it only shows new preset
Anakill said:
Actually, I've found the mid-long press but it only shows new preset
Click to expand...
Click to collapse
It doesn't find Preset file
Hello my friend, thanks for sharing ...
I have a request, will there be sharing for bluetooth headset?
The model I use; Haylou GT1
zgfg said:
It doesn't find Preset file
Click to expand...
Click to collapse
Yes it doesn't.
PotentieL said:
Now regarding presets archives, once everything is installed and working, unpack the archive in /Viper4Android , just use a file manager, the folder is not hidden or anything. It will paste kernel into kernel and presets into presets...
Click to expand...
Click to collapse
Anakill said:
Yes it doesn't.
Click to expand...
Click to collapse
With Viper4AndroidFX v2.7.1.6, its settings apparently moved to (as on the screenshot):
Internal memory
/Android/data/com.pittvandewitt.viperfx/files
Anakill said:
Hi, I have an issue with presets.
I have extracted the 2 zip but when I long press in Viper4android nothing appears.
What should I do ?
Click to expand...
Click to collapse
Load The pre-configs with doble tap in the (¿Source of sound?) (Headphone, Speaker, Bt, etc)
Hi! Have any a good profile for BT headphones? (Air 2 se) I have a good volumen in poweramp but in youtube the max volumen its too low, thanks!
Enviado desde mi Mi 9T mediante Tapatalk
Hi all,
I would like to share my preset for the speaker of xiaomi 9T