Sond Problem With Ginger DX v.014 - XPERIA X8 Q&A, Help & Troubleshooting

I have installed GingerDx v.14 on my SE X8. I was playing an mp3 on the "built-in" player so I mounted the SD, the music stopped (Normal beacuse no source) but since then no sound come from the speaker, I checked every Sound configuration but nothing happens.
I tried to install/Restore another rom (GingerDX v013, Floyo, and the original one)
but still no sound from it.
NOw Trying SEUS,
HELP!!

I have the same problem...any solution ?

try make full wipe in CWM and again install ROM, if that not success use SEUS to get default ROM on your phone..

Solved!! at least my sound problem
With SEUS it's the same, so it's a hardware problem....
Don't worry the problem was in the internal speaker, so I changed it, and done.
but I'll have some opinion about the mod but i'll post them later.
Thanks

Related

No Sound in My Captivate

Hi Guys I lose my media sound and system sound yesterday suddenly at that moment I'm Running the Original Samsung /AT&T 2.1 ROM Root & Lagfix I try all the setting and nothing happens and I have tryied change the ROM,I flash CM7 after flash have sound after I start installing the App I found that My Captivate have No sound again still have the same problem, anyone any ideas? or help Please.

[Q] Serious problems with optimus 2x...

Hi .. am facing weird problems with my mobile.. It started of yesterday suddenly when i tried to unlock the device . I was using kang's RC1-80 + Etana's 28 march LOC kernel (default values- no undervolting or overclock)
1. doesn't wake after locked (major problem)
2. frequent hang ups
3. accelerometer not working
4. media playing too fast and no sound
I have tried different Roms - Kang's build of cyanogen(GB), Nova-HD, MIUI GB (with and without etana's kernel).
I have also tried raising the minimum frequency to 503mhz but of no avail.
Can you suggest some solution and help trace the problem.
You think maybe it's hardware?
Why not trying to return the phone to full stock with smartflash? If it's still acting weird can you still return it on warranty?
Thanks for the reply.. I tried flashing with smartflash to stock rom but still the same problem persists. I will be taking it to service centre then..
Best of luck to you mate.
Maybe if it starts suddenly it can be something unusually, sdcard, sim card, or try other kernels. Maybe problem with recovery (but stock rom should help).
Sent from Poland

[Q] No sound with F1 GalaxyNexus port and Semaphore kernel

Hey all,
I just decided to upgrade to ICS, and it looked like the F1 GalaxyNexus port for Capis was a good option. Flashing went great, but first the sdcard was mounted on the wrong place and I had no sound at all.
So I changed the kernel from Glitch to Semaphore, and the sdcard problem was fixed, but I still have no sound. Not from the speaker or headphones, and it doesn't matter whether it's a system sound or something else.
I've reflashed twice and still have the problem. Anyone have any ideas what I can try next? Thanks

Touchscreen bug, apparently software-caused

So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Cheshire-Cat said:
So, I was using MiniCM7 2.2.1 (kernel nAa-13) but it seemingly was too hard on my battery, therefore I decided to give a try to a few other ROMs in order to find out which provided the best battery life. So I tried a few on the same kernel and then flashed the Alfs v08a-CM7 kernel and the GingerZaraki ROM. Then the problem began.
As soon as it booted I noticed that the touchscreen was acting weird. I assumed it to be a GingerZaraki or Alfs bug so I flashed back to nAa-13 and MiniCM7 2.2.1, but it persisted, then I flashed nAa-ics-04 and MiniCM9 3.0.4, and finally stock 2.1 -- and it's still there. In all cases factory resets were done and the SD card was cleared as I've seen on other touchscreen bug threads.
I don't know what happened, or what to do. It is like, from time to time, an invisible finger repeatedly touched the right edge of the screen. That results on options being activated in portrait mode (in settings it can go down to third or fourth level in each of the "bursts") or the notification center being activated in landscape mode.
Any ideas?
Click to expand...
Click to collapse
try in stock rom/eclair about a week ,I think it is about nAa issue !!
just full wipe and flash stock rom..........using flash tools......or try using song update service........
binhari said:
just full wipe and flash stock rom..........using flash tools......or try using song update service........
Click to expand...
Click to collapse
I did, as I stated before. Still not working properly.
What I don't understand is how flashing a new kernel/ROM can break it in a way that not even flashing back stock Eclair solves the problem. I can only think of hardware failure but... it would be akin to a computer failing because you installed a different version of Windows.
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
illusionist.h1 said:
I am facing the same problem. Both GingerXperia v22 & 23 had the same problem as yours. Tried installing GingerXperia v25 but my phone then got stuck at the SE screen.
Posted a query here: forum[dot]xda-developers[dot]com/showthread.php?t=1837885
Used SEUS to install the default Sony version, but I am still facing the same touchscreen bug (random parts of the screen get selected even if I don't touch the screen and many times the screen does not respond even if I touch it).
I was happily using GingerDX till all of this started.
Please do post here if you find a way to solve this bug.
Click to expand...
Click to collapse
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Cheshire-Cat said:
It doesn't seem to be kernel-related then.
In my case it began when I flashed Alfs v08a and then GingerZaraki. I assumed that it had to do with Alfs as the touchscreen driver is in kernel space on Linux (and therefore Android) but seeing that you got the same while on stock kernel (I assume, as you really, really shouldn't try to unlock your bootloader as it's likely to result in a hard brick) it seems to be either ROM-related, or plain hardware failure.
In your case, did it start right after flashing GingerXperia? This is important as it would be too much of a coincidence if two phones failed in this way right after flashing a ROM and that wasn't the cause.
Click to expand...
Click to collapse
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
illusionist.h1 said:
This confuses me. This seems neither a hardware problem nor a software problem. Here is why:
1. Why this doesn't seem to be a hardware problem.
Because it started the moment I installed GingerXperia v22. Everything was fine when I used Stock Kernel as well as GingerDX. This to be caused by a hardware problem would be too much of a co-incidence for both our cases.
2. Why this doesn't seem to be software problem.
Because it persisted even after I installed different versions of GingerXperia (v23). I have now installed the Stock Kernel using the SEUS and the problem is still persisting. Moreover, I haven't unlocked the bootloader till now. So, how could be a software problem (ROM related) ?
Now, can someone explain me what could be the source of this problem ?
Click to expand...
Click to collapse
I don't know exactly how ROM flashing works -- I've seen a "backing up system files" message, and I think that there's a reason why the stock 2.1 image is about 200 MB while CM7 ROMs rarely exceed 100 MB. I guess that some files are kept. Maybe if one or more of those files (say, a driver) is replaced with an incompatible version... but then, flashing stock should solve it. Maybe someone can shed a bit more light on the subject?
Another possibility is software-caused hardware failure, where some kind of misconfiguration physically damages the hardware. It's very uncommon, but who knows.

Help sound problems after flashing!

Hi,
After flashing an ICS rom i got problems with the sound. I get sound at the Samsung logo but halfway the sound get clipped.
No sound on anything coming from the external speaker from there on. Internal speaker works fine on calls ect, and headset port
also works.
I have tried flashing pit file, gb bootloader and gb stock rom from samfirmware for my country non of these things fixed it.
Please help..
Best regards
Robert
babaloui said:
Hi,
After flashing an ICS rom i got problems with the sound. I get sound at the Samsung logo but halfway the sound get clipped.
No sound on anything coming from the external speaker from there on. Internal speaker works fine on calls ect, and headset port
also works.
I have tried flashing pit file, gb bootloader and gb stock rom from samfirmware for my country non of these things fixed it.
Please help..
Best regards
Robert
Click to expand...
Click to collapse
I would suggest that go back to GB, do a full wipe and then after reflash ICS. DO NOT DO A FULL IN ICS....

Categories

Resources