Hello folks,
I'm from Germany and after searching a lot in this forum and via google now I try my luck here by asking directly.
My phone:
Sony Xperia XZ1 Compact
branded by German Provider Vodafone
Model G8441
Android 9
Build 47.2.A.11.228
TWRP installed: Sony Xperia XZ1 Compact (lilac)
My problem is the (as I know now) well-known microphone gain which makes it impossible to use the device for telephoning. The gain is much too high so the one I call can't understand a word I say. Using a headset telephoning works well with good sound quality.
So I tried to edit the mixer_paths.xml, which is in /vendor/etc on my phone. To do so I installed TWRP to get temporary root rights in recovery mode and did the following (as described in many other posts I found so far):
start the device in recovery mode with TWRP
copy /vendor/etc/mixer_paths.xml to the sdcard
edit mixer_paths.xml on pc
copy it back to /vendor/etc
set permissions to chmod 0644
reboot
All that worked, BUT if I restart the device as user and look in /vendor/etc there is always the original file from 2019-09-03, 21:40. Starting again with TWRP in /vendor/etc I see the before edited mixer_paths.xml.
It seems as if the system uses different parts of the memory depending on the way I start the device, to pretend the user from editing system files in recovery mode.
Is there any solution to this problem? Maybe I did something wrong?
Every hint is highly apreciated!
As nothing worked I decided to root the phone with Magisk. Works like a charme, I can edit the mixer_paths.xml while the system is running.
Unfortunately the problem I wanted to solve by editing mixer_paths.xml is still there, but that doesn't fit in this thread.
o_brien said:
Como nada funcionó, decidí rootear el teléfono con Magisk. Funciona de maravilla, puedo editar el archivo mixer_paths.xml mientras el sistema se está ejecutando.
Desafortunadamente, el problema que quería resolver editando mixer_paths.xml todavía está ahí, pero eso no encaja en este hilo.
Click to expand...
Click to collapse
Me pasa lo mismo, creo que hay módulos magisk para no tener que estar editando el mixer_paths.xlm cada vez que reinicies, https://github.com/reiryuki/Mic-Fix-Magisk-Module prueba con este módulo y dime qué tal te fue
o_brien said:
Hello folks,
I'm from Germany and after searching a lot in this forum and via google now I try my luck here by asking directly.
My phone:
Sony Xperia XZ1 Compact
branded by German Provider Vodafone
Model G8441
Android 9
Build 47.2.A.11.228
TWRP installed: Sony Xperia XZ1 Compact (lilac)
My problem is the (as I know now) well-known microphone gain which makes it impossible to use the device for telephoning. The gain is much too high so the one I call can't understand a word I say. Using a headset telephoning works well with good sound quality.
So I tried to edit the mixer_paths.xml, which is in /vendor/etc on my phone. To do so I installed TWRP to get temporary root rights in recovery mode and did the following (as described in many other posts I found so far):
start the device in recovery mode with TWRP
copy /vendor/etc/mixer_paths.xml to the sdcard
edit mixer_paths.xml on pc
copy it back to /vendor/etc
set permissions to chmod 0644
reboot
All that worked, BUT if I restart the device as user and look in /vendor/etc there is always the original file from 2019-09-03, 21:40. Starting again with TWRP in /vendor/etc I see the before edited mixer_paths.xml.
It seems as if the system uses different parts of the memory depending on the way I start the device, to pretend the user from editing system files in recovery mode.
Is there any solution to this problem? Maybe I did something wrong?
Every hint is highly apreciated!
Click to expand...
Click to collapse
Hello. Can you please share your mixer_paths files from the stock firmware (Build 47.2.A.11.228)?
Related
I'm a chinese person, I got a Treo 750v from HongKong, I use [DesktopUpdaterEN release 1.16.exe] to update my mobile, but got something wrong, now my mobile OS can't start, It stuck at the blue screen with a text [Windows Mobile].
I tried the miniSD card method
1. Format the miniSD card to Fat32, and unpack the [DesktopUpdaterEN release 1.16.exe] file. Take the file inside [ CHEEIMG_FW.nbh] rename it as [CHEEIMG.nbh] , and copy the file to the miniSD card
2. Press both the media key (the one below the volume rocker) and the reset button.
3. Get the rainbow screen and then a grey screen , but different from other person , it stuck at red text at the top of the screen that says '00068002' and below it says 'Loading...' , and 2 second later it return to the rainbow screen .
Did anybody find the mothed to solve the problem?
respuesta
i hope do you spek spanish. a mi me paso lo mismo, pero lo soluciones, instalando la vercion wm6 de ATT, y me va de maravilla. aqui mismo en el for hay links si no ve a esta:r http://depositfiles.com/ru/files/1336491
danmali said:
I'm a chinese person, I got a Treo 750v from HongKong, I use [DesktopUpdaterEN release 1.16.exe] to update my mobile, but got something wrong, now my mobile OS can't start, It stuck at the blue screen with a text [Windows Mobile].
I tried the miniSD card method
1. Format the miniSD card to Fat32, and unpack the [DesktopUpdaterEN release 1.16.exe] file. Take the file inside [ CHEEIMG_FW.nbh] rename it as [CHEEIMG.nbh] , and copy the file to the miniSD card
2. Press both the media key (the one below the volume rocker) and the reset button.
3. Get the rainbow screen and then a grey screen , but different from other person , it stuck at red text at the top of the screen that says '00068002' and below it says 'Loading...' , and 2 second later it return to the rainbow screen .
Did anybody find the mothed to solve the problem?
Click to expand...
Click to collapse
Danman, did you find a solution to your problem?
If so, after your English installation, can you still write in Chinese in your phone?
Hello. I had a problem with the Samsung
Galaxy S advance. I do not detect the
computer. You Yeah but I get error 43 and it
makes me uknow device (I tried it on several
computers) I have the kies and the drivers
installed. The phone in download mode or the
recovery takes neither. I tried several cables
and only loaded but the pc does not detect it.
Neither the odin. The baseband is ublk1 tried
restarting reinstalled drivers, etc.. Any
solution?
Hola. Tenía un problema con el Samsung Galaxy S advance. No me lo detecta la computadora. Va si pero me da error 43 y me pone uknow device (lo probé en varias computadoras) tengo el kies y los drivers instalados. El celular en modo descarga o con el recovery tampoco lo toma. Probé varios cables y solamente cargan pero la pc no lo detecta. Tampoco el odin. La baseband es ublk1 probé reiniciando reinstalado controladores, etc. Alguna solución?
Picasso Lg said:
Hello. I had a problem with the Samsung
Galaxy S advance. I do not detect the
computer. You Yeah but I get error 43 and it
makes me uknow device (I tried it on several
computers) I have the kies and the drivers
installed. The phone in download mode or the
recovery takes neither. I tried several cables
and only loaded but the pc does not detect it.
Neither the odin. The baseband is ublk1 tried
restarting reinstalled drivers, etc.. Any
solution?
Hola. Tenía un problema con el Samsung Galaxy S advance. No me lo detecta la computadora. Va si pero me da error 43 y me pone uknow device (lo probé en varias computadoras) tengo el kies y los drivers instalados. El celular en modo descarga o con el recovery tampoco lo toma. Probé varios cables y solamente cargan pero la pc no lo detecta. Tampoco el odin. La baseband es ublk1 probé reiniciando reinstalado controladores, etc. Alguna solución?
Click to expand...
Click to collapse
try look at the micro usb pin below your phone,maybe the problems is there ..
or try other pc/laptop. if other pc/laptop detect ur device then the problems is in ur pc .
lawong said:
try look at the micro usb pin below your phone,maybe the problems is there ..
or try other pc/laptop. if other pc/laptop detect ur device then the problems is in ur pc .
Click to expand...
Click to collapse
I tried it on several pc. The strange thing is 2 things over the load cell. and the other that the pc does not recognize it.
Besides brush pass to pin usb what else I can do?
I tried a thousand things but I can not connect via USB.
I tried rebooting with the cable set
Restart without cable since then connect
Download Mode
Wipes in recovery
Format internal SD
Give them a external SD
From factory profile reestablish the cell
1.4.8 drivers installed.
Then I tried with 1.5.6
Kies installed (touch troubleshooting, wifi kies walk.)
Odin
Various cables (4)
Several PC (3 or 4 can not remember win 7 and xp)
The unknown device pc tells me Error 43
and does not work in any way.
I tried usb debugging also
from mass storage connections put me says no usb connected.
The load cell with usb connected to the computer to perfection
And load connected to the charger too.
Android 2.3.6
Baseband UBLK1
HELP PLEASE!!
Picasso Lg said:
I tried a thousand things but I can not connect via USB.
I tried rebooting with the cable set
Restart without cable since then connect
Download Mode
Wipes in recovery
Format internal SD
Give them a external SD
From factory profile reestablish the cell
1.4.8 drivers installed.
Then I tried with 1.5.6
Kies installed (touch troubleshooting, wifi kies walk.)
Odin
Various cables (4)
Several PC (3 or 4 can not remember win 7 and xp)
The unknown device pc tells me Error 43
and does not work in any way.
I tried usb debugging also
from mass storage connections put me says no usb connected.
The load cell with usb connected to the computer to perfection
And load connected to the charger too.
Android 2.3.6
Baseband UBLK1
HELP PLEASE!!
Click to expand...
Click to collapse
Try this:
1. Unplug the USB cable
2. On the cell phone, dial the following number: *#7284#
Once the last # is hit, the PhoneUtil application is launched. Choose USB -> Modem and then USB -> PDA mode.
The good mode should be PDA. Even if the mode is PDA, switch to Modem and then back to PDA.
3. Plug the USB cable.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you tried all that, maybe it is some hardware problem with USB port on your phone.
same problem
Picasso Lg said:
I tried a thousand things but I can not connect via USB.
I tried rebooting with the cable set
Restart without cable since then connect
Download Mode
Wipes in recovery
Format internal SD
Give them a external SD
From factory profile reestablish the cell
1.4.8 drivers installed.
Then I tried with 1.5.6
Kies installed (touch troubleshooting, wifi kies walk.)
Odin
Various cables (4)
Several PC (3 or 4 can not remember win 7 and xp)
The unknown device pc tells me Error 43
and does not work in any way.
I tried usb debugging also
from mass storage connections put me says no usb connected.
The load cell with usb connected to the computer to perfection
And load connected to the charger too.
Android 2.3.6
Baseband UBLK1
HELP PLEASE!!
Click to expand...
Click to collapse
did you get the solution ???
Have you tried disable USB Debugging? My experience was that, after I flashed a ROM, the USB Debugging was enabled, causing me unable to connect to my PC.
So what I did was the followings: (assuming your PC USB slot is fine and also a working USB cable)
-Disable USB debugging and reconnect the cable
Then, it works like charm.
Hi guys,Android file transfer it doesn't work any more after the upgrade of my Mac to el Capitan. Adb command as well. Someone has any idea how to solve it? Cheers.
Sent from my Nexus 6 using XDA Free mobile app
Android File Transfer works fine and so does adb. You have to disable something Apple has added to El Capitan that blocked adb from working as it should.
Here is how I installed ADB on El Capitan:
https://github.com/corbindavenport/nexus-tools/wiki/Fix-for-Mac-OS-X-10.11-(El-Capitan)
follow it really carefully!
I will. Cheers!
Sent from my Nexus 6 using XDA Free mobile app
...theres nothing there at that link.
Yeah, I found a wiki to run at that link. I don't have the brain capacity or patience to follow instructions like that at length. I'm hoping there is an easy fix. It doesn't work on Mavericks either.
AFT has worked flawlessly on both Mavericks and El Capitan for me.
Honestly dont know what I did (aside from flash the latest Cataclysm ROM) and everything is working. I can adb and use Android File Transfer with El Capitan and Marshmallow
Guys, I had almost the same problem. I was using AFP on 5.1.1 with El Capitan, and everything was great. But then the Marshmallow came. And AFP stops working. I only had the "your device is locked" error. I've killed a night to figure it out – the device was charging only, no MTP protocol. So, here is the solution, that may helps to someone of you: you need to enable developer settings, and allow USB debugging. After that, when you have your Nexus connected to Mac, swipe down the notification bar and tap on message "Charging via USB". Then choose "File Transfer (MTP).
Thats it, AFP will works correctly.
Gbaaqty said:
Why not try Coolmuster Android File Transfer app.Coolmuster Android File Transfer enables you transfer contacts ,messages ,documents, music, pictures, videos to computer .It allow add, delete and export contacts, text messages, photos, videos, music, call logs, apps, and so on. What’s more, you can send text messages from computer to mobile phone.You can easy to install and uninstall apps on your computer.
Click to expand...
Click to collapse
Probably because I don't see anything about a Mac on the site you're pimping.
Also a pretty crappy Chinese to English translation with misspellings.
Honestly dont know what I did (aside from flash the latest Cataclysm ROM) and everything is working. I can adb and use Android File Transfer with El Capitan and Marshmallow
Click to expand...
Click to collapse
It works on my mac but it lags much. Any alternative to it on mac?
It only works on my Mac with my phone in twrp recovery. Weird. But works well there.
I tried installing Android-X86 on my Teclast X98 Air 3G (C5J8 - 64GB Z3735F) tablet.. and surprisingly enough, it works! (Though not without bugs).
I believe if we apply the correct fixes for baytrail platform, we could get Android 5.1 and even 6.0! I would do that myself, though being new to android building (always used custom roms, neve cooked them) an helping hand or two would be appreciated
You will need:
An usb Stick (2 are recommended)
USB OTG Hub
USB Keyboard (And mouse)
Rufus
GParted Live ISO (I used amd64 iso)
Android-x86 dd image (.img, x86_64)
Working brain
Now let's go down to the business, the install process is as follows:
Use rufus to burn GParted live iso on your usb stick #1, ISO mode, MBR for UEFI Partition scheme.
Attach your usb hub with GParted USB stick, keyboard and mouse to the tablet. Enter the bios and from "Boot override" menu, choose your USB stick.
Boot to GParted live, choosing any option from its bootmenu.
Once booted, use GParted to create a 201MB FAT32 partition labeled "EFI", and a big enough ext4 partition for the system (I used whole disk), commit the changes and power off the tablet.
Burn Android-x86 img to your USB stick #2 (Or #1, we won't really need it anymore), DD Image mode.
Boot to your usb stick, same way as you did in step 2
Install Android-x86 to the ext4 partition, when asked to install Grub and EFI Grub 2 say "Yes", i choose to install system in R/W, but you can choose to keep it read only if you wish.
Boot to your android-x86 Installation
What does not work:
Power button (Perhaps wrong GPIO pin in the driver?)
Audio
Bluetooth
Micro SD slot
Screen is upside-down and does not go off, it dims instead.
3D Acceleration (I believe, Antutu 3D Bench makes the tablet reboot when started)
YouTube playback does not work (Continuous reloading of the stream)
Camera (Couldn't test)
Touchscreen (My digitizer is broken so i couldn't test, but it's been reported as not working by @Maxximo88 )
3G (Couldn't test!)
Perhaps, other things i didn't test.
As i got it, most of these problems are from wrong device configuration. I will try syncing and building an android-x86 image with the correct drivers and configuration as soon as i have some spare time, what we now have looks like an interesting starting point. And knowing Android-x86 has joined forces with RemixOS, there are chances we could even be able to build RemixOS 2.0!
Useful stuff:
Android Device Tree
Update:
The same process can be used to install android-x86 6.0 Marshmallow. Same working hardware and procedure, so i'll be using that as a base.
I dumped some logs (lsmod, dmesg etc) you can find them in the attachments.
Yep, ok that's a good start!
Hope someone could help you to get a fully working release!
@mirek190 are you still go for one more ROM?
Great I hope some developer can get us an fully working rom! What do you say @mirek190?
hello i can to install android x86 in my teclast x80 plus ??? it all work ??? mp please ???
Kryogen said:
I tried installing Android-X86 on my Teclast X98 Air 3G (C5J8 - 64GB Z3735F) tablet.. and surprisingly enough, it works! (Though not without bugs).
I believe if we apply the correct fixes for baytrail platform, we could get Android 5.1 and even 6.0! I would do that myself, though being new to android building (always used custom roms, neve cooked them) an helping hand or two would be appreciated
You will need:
An usb Stick (2 are recommended)
USB OTG Hub
USB Keyboard (And mouse)
Rufus
GParted Live ISO (I used amd64 iso)
Android-x86 dd image (.img, x86_64)
Working brain
Now let's go down to the business, the install process is as follows:
Use rufus to burn GParted live iso on your usb stick #1, ISO mode, MBR for UEFI Partition scheme.
Attach your usb hub with GParted USB stick, keyboard and mouse to the tablet. Enter the bios and from "Boot override" menu, choose your USB stick.
Boot to GParted live, choosing any option from its bootmenu.
Once booted, use GParted to create a 201MB FAT32 partition labeled "EFI", and a big enough ext4 partition for the system (I used whole disk), commit the changes and power off the tablet.
Burn Android-x86 img to your USB stick #2 (Or #1, we won't really need it anymore), DD Image mode.
Boot to your usb stick, same way as you did in step 2
Install Android-x86 to the ext4 partition, when asked to install Grub and EFI Grub 2 say "Yes", i choose to install system in R/W, but you can choose to keep it read only if you wish.
Boot to your android-x86 Installation
What does not work:
Power button (Perhaps wrong GPIO pin in the driver?)
Audio
Bluetooth
Micro SD slot
Screen is upside-down and does not go off, it dims instead.
3D Acceleration (I believe, Antutu 3D Bench makes the tablet reboot when started)
YouTube playback does not work (Continuous reloading of the stream)
Camera (Couldn't test)
Touchscreen (My digitizer is broken so i couldn't test, but it's been reported as not working by @Maxximo88 )
3G (Couldn't test!)
Perhaps, other things i didn't test.
As i got it, most of these problems are from wrong device configuration. I will try syncing and building an android-x86 image with the correct drivers and configuration as soon as i have some spare time, what we now have looks like an interesting starting point. And knowing Android-x86 has joined forces with RemixOS, there are chances we could even be able to build RemixOS 2.0!
Useful stuff:
Android Device Tree
Update:
The same process can be used to install android-x86 6.0 Marshmallow. Same working hardware and procedure, so i'll be using that as a base.
I dumped some logs (lsmod, dmesg etc) you can find them in the attachments.
Click to expand...
Click to collapse
Hello mate, have u try to update the new version, Android O on it?
Any updates?
Thanks.
Phoenixos 2.0
Salut
Installation de Phoenix os 2.0 sur une tablette
Teclast x98 air 3g tuto video en 4 partie.
1
présentation sur la tablette de la version Phoenix os 1
https://youtu.be/LWYU3eIp-Zk
2
vidéo explicite de l'installation sur un Pipo X7 les manipulations a faires sont exactement les mêmes.
https://youtu.be/NUCsSkbooqw
3 et 4
mise a jour vers Phoenix os 2.0 Android nougat 7.1
https://youtu.be/W0kz9LUXdiA
https://youtu.be/fYpLOBjnYxM
:RÉ[COLOR="Silver"
Salut ,
est ce que le son et le tactile fonctionne ?
Merci
Hello, I have a problem with Leeco Le 2 x527 when I connect it to the PC via USB. The terminal is recognized, I can see the folders, but when I try to transfer a file, nothing happens. Any idea?