Database Info

[Q] Low microphone?

Hey!
I have been having issues with my microphone on my LG G2X - I have it rooted, and it's running Miui - not sure what version... I have completely wiped and gone factory, but when I talk everyone can't hear me..... I bought it from a friend - who said he had problems - but it seemed to fix itself out..... Not sure what I can do.
Does anyone know how to increase the volume for a microphone? Or how to take it apart and fix it manually?

calebcoverdale said:
Hey!
I have been having issues with my microphone on my LG G2X - I have it rooted, and it's running Miui - not sure what version... I have completely wiped and gone factory, but when I talk everyone can't hear me..... I bought it from a friend - who said he had problems - but it seemed to fix itself out..... Not sure what I can do.
Does anyone know how to increase the volume for a microphone? Or how to take it apart and fix it manually?
Click to expand...
Click to collapse
Is it related to the ROM? Or have you tried other Roms? I know that the latest Nightlies of CM7 have that issue, but the stable release of CM7 doesn't.

Jufjufjuf said:
Is it related to the ROM? Or have you tried other Roms? I know that the latest Nightlies of CM7 have that issue, but the stable release of CM7 doesn't.
Click to expand...
Click to collapse
That really seems to depend on the phone, also. I've flashed every single nightly since the 40s, and when the 'microphone issue' started popping up I made it a point to test my mic volume to a minimum of 5 other phones every nightly....and it's never been a problem on my handset. Not once...
Not saying the problem doesn't exist, it just doesn't seem to be present on all devices..

I had the same prob on cm7 around nightly 174 or 175. Try pushing the latest stable release of cm7.. i bet it'll be all set.

JaiaV said:
That really seems to depend on the phone, also. I've flashed every single nightly since the 40s, and when the 'microphone issue' started popping up I made it a point to test my mic volume to a minimum of 5 other phones every nightly....and it's never been a problem on my handset. Not once...
Not saying the problem doesn't exist, it just doesn't seem to be present on all devices..
Click to expand...
Click to collapse
I totally agree, my phone has it where as my parents' doesn't. Wonder what could be the issue.

It's a known issue on some MIUI builds, some have suggested replacing files (for example: http://forums.miuiandroid.com/showthread.php?10200-Low-mic-problem) or playing around with mute/unmute (for example: http://www.galnetmiui.co.uk/landing/forums/showthread.php/2352-Low-Microphone-Volume). I haven't experienced the problem myself on recent builds from Whitehawx.

Bottom buttons don't stay "always on "

When I'm stock the option will work but as soon as I flash a kernel they wont stay on. Any help appreciated.
Sent from my SAMSUNG-SGH-I727 using XDA

inspire me said:
When I'm stock the option will work but as soon as I flash a kernel they wont stay on. Any help appreciated.
Sent from my SAMSUNG-SGH-I727 using XDA
Click to expand...
Click to collapse
Do a little reading in the UCLA3 upgrade and kernel threads. You will find it is a problem with the UCLA3 Kernel(s) that has not been resolved as of yet. Some seem to have the problem and others claim that they do not.

It's not Kurnel or Radio/Modem, if you go to Settings/Display/Touch Key Light Duration/ and choose Always ON and it does not stay on, IT MEANS ROM PROBLEM!

odeccacccp said:
It's not Kurnel or Radio/Modem, if you go to Settings/Display/Touch Key Light Duration/ and choose Always ON and it does not stay on, IT MEANS ROM PROBLEM!
Click to expand...
Click to collapse
wrong bud, means kernel problem

icenight89 said:
wrong bud, means kernel problem
Click to expand...
Click to collapse
I am learning, but logically it is the ROM and actually I've just flashed what he is saying with the ROM I use and no problem.

odeccacccp said:
I am learning, but logically it is the ROM and actually I've just flashed what he is saying with the ROM I use and no problem.
Click to expand...
Click to collapse
Again, just because your phone is not having the issue does not mean everyone's phone is not. These phones act differently for different people. It IS a known problem that SOME people experience with the UCLA3 KERNEL. I have posted before that I have tried the stock ROM as well as the one I am on now (Alien) and others have posted while using different ROMS and the problem always comes from the UCLA3 kernels.
If you are one of the people that don't have a problem...that's great...but don't try to tell others that they are wrong about something just because it isn't happening to you, that just doesn't help the situation.
Take some time to read through the forum(s) and you will see what really is a problem -vs- what people make into a problem because they are not doing something correct. The "touchlight" always on problem started the day of the last OTA update (for many people) and has continued. I am still hoping a fix will be found for those of us that have this problem with the UCLA3 kernels.
It is more than likely a problem with the lights driver in the new kernel, but until an actual MOD has the problem it might be difficult to create a fix for it. My theory is that "maybe" the old lights driver(s) can be added to replace the lights drivers in the newwer UCLA3 kernel and maybe that would work...but its just a theory.

scott14719 said:
Again, just because your phone is not having the issue does not mean everyone's phone is not. These phones act differently for different people. It IS a known problem that SOME people experience with the UCLA3 KERNEL. I have posted before that I have tried the stock ROM as well as the one I am on now (Alien) and others have posted while using different ROMS and the problem always comes from the UCLA3 kernels.
If you are one of the people that don't have a problem...that's great...but don't try to tell others that they are wrong about something just because it isn't happening to you, that just doesn't help the situation.
Take some time to read through the forum(s) and you will see what really is a problem -vs- what people make into a problem because they are not doing something correct. The "touchlight" always on problem started the day of the last OTA update (for many people) and has continued. I am still hoping a fix will be found for those of us that have this problem with the UCLA3 kernels.
It is more than likely a problem with the lights driver in the new kernel, but until an actual MOD has the problem it might be difficult to create a fix for it. My theory is that "maybe" the old lights driver(s) can be added to replace the lights drivers in the newwer UCLA3 kernel and maybe that would work...but its just a theory.
Click to expand...
Click to collapse
you said/wrote what I was too lazy to lol. Yup, because he's new (technically he joined first but ur more active), he doesn't know this was an existing problem.. He'll learn as he goes along

scott14719 said:
Again, just because your phone is not having the issue does not mean everyone's phone is not. These phones act differently for different people. It IS a known problem that SOME people experience with the UCLA3 KERNEL. I have posted before that I have tried the stock ROM as well as the one I am on now (Alien) and others have posted while using different ROMS and the problem always comes from the UCLA3 kernels.
If you are one of the people that don't have a problem...that's great...but don't try to tell others that they are wrong about something just because it isn't happening to you, that just doesn't help the situation.
Take some time to read through the forum(s) and you will see what really is a problem -vs- what people make into a problem because they are not doing something correct. The "touchlight" always on problem started the day of the last OTA update (for many people) and has continued. I am still hoping a fix will be found for those of us that have this problem with the UCLA3 kernels.
It is more than likely a problem with the lights driver in the new kernel, but until an actual MOD has the problem it might be difficult to create a fix for it. My theory is that "maybe" the old lights driver(s) can be added to replace the lights drivers in the newwer UCLA3 kernel and maybe that would work...but its just a theory.
Click to expand...
Click to collapse
Tltr lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk

Same Issue here, I have it set to "Always On" and they come on as they please. I hope they can fix it soon!

Which ICS Roms have the SMS delay fix?

I recently flashed my first rom, going from stock 2.3.3 to Fallout 4.4.0. I always had the sms delay issues on 2.3.3, since flashing Fallout 4.4.0 I've still got the issue, but I also have text messages going missing as well.
Do any of the ICS custom roms have the SMS delay fix built in? Or is there a way to apply the fix to any rom I use?
Thanks

I've never had any issue with text messages going missing or any delay issues, either on stock or (currently) on CM9.
Are you sure it isn't a hardware issue with your particular phone instead of software?

It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.

FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
I do vaguely remember something to do with this issue, but I think it was solved by an HTC update a long time ago. I can't imagine that any current ROM has this issue - it was a base software fix, not an add-on fix AFAIK.
If you are getting this now then I suspect it is something other than the ROM causing the problem.

FlexiPack said:
It is a noted issue with some Desire S handsets. Why it's only some I don't know. There are a lot of users with this issue - link. It's also been discussed here on XDA.
Click to expand...
Click to collapse
That link also points to the software update that brought the Android version up to 2.3.5 as fixing the issue, why didn't you upgrade to 2.3.5? I still think it has something to do with your hardware and the fact it is only some would make me think that even more.

I presumed that any rom after 2.3.5 would have the fix but it was still happening on the ICS rom I tried. Today I have flashed 2.3.5 (version 2.10.401.9). I've still got sms delay
It's looking like it's not a software issue but I don't understand how it could be a hardware issue. Surely a hardware fault would mean they either do come through or don't, not the occasional delay or one going missing. So far my phone doesn't seem to have dropped signal when idle, so it 'may' have fixed something at least!

If my memory serves me correctly then the issue was related to the radio that came with the 1.47 update many moons ago
Sywepd form my DsereiS

That's interesting. Perhaps I could update to a custom rom and change the radio. So far the delays have been very short and none have gone missing so it's definitely better than before. I'd hate to be stuck on gingerbread though.

Jellybean (CM/AOKP/Virtuous) Maps/Photoshpere Bug (Report Here)

Hello,
I have the following problem:
I experience visual artifacts when using two-finger rotate in Google Maps, also Photoshpere is really acting up... the images flicker...
Not all devices have it, as a matter of fact there are few of them (reported). Let's try to collect as much data as we can in order to find the cause of this and maybe a fix. I'll start.
HTC One S
Color: Gradient Blue
HBOOT:1.14.0002
Radio:1.06es.50.02.31
Jun 11 2012, 14:36:28
It's recommended to attach a logcat with the problem.
The problem allways happen when try to rotate Gmaps with two fingers, and photoshpere gets crazy especially after taking 1st photo.
It seems like an accelerometer problem, but accelerometer utilities seems to report the sensors working fine, so maybe a GPU driver problem.
C'mon guys, let's get this fixed

For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?

Darknites said:
For the flicker have you tried changing debug.composition.type=dyn to debug.composition.type=gpu? I also had the same issue with that camera but only tried it when it come out, have you tried other packs that have it?
Click to expand...
Click to collapse
I've tried many packs... i will try those and report back. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.

adi4motion said:
I've tried many packs... i will try those and report bach. The thing that scares me is that this happens on Virtuous Rom also (which is almost stock build with HTC jb libs), and this may mean that i will never have fully working jb not either from HTC.
Click to expand...
Click to collapse
What you get both issues on Virtuous? that can't be good.

Darknites said:
What you get both issues on Virtuous? that can't be good.
Click to expand...
Click to collapse
yes... that's also what i'm afraid of...

Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.

PcFish said:
Keep in mind the camera is for 4.2, not 4.1, and I doubt we'd ever get stock camera on official Sense.
Click to expand...
Click to collapse
ok, that's not a problem, i can live without photoshpere, but the fact is Google Maps also have this problem and I need GMaps...
I know that at least 3 others reported this problem (and i'm sure that are many others who didn't test for it) I wonder where are they now...
I started this thread hoping that if other users reported it, the devs would try to solve this, but i think i'll just have to wait for HTC to give us JB and see if i still have the problem (but I am really concerned that I might have it). What's wrong with this One series? so many bugs (and not minor): cases chipping, helicoptering bug, sound issues, performance issues (one x), this problem....

I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers

wheeliemonster said:
I reported in another thread that I have this problem and I do, when using photosphere, I've seen it, although if I keep my movements nice and slow and steady, it seems to hold together.
I haven't seen any problem in Google Maps though, what happens to you in there?
Cheers
Click to expand...
Click to collapse
when i rotate the map with two fingers i get visual artifacts

I have the same problem on photospere, on maps I have no graphical problems, but the magnet sensor seams to change it's direction sometimes. Had this on CM10, and now on 4.1 Sense+.
Edit: I mean I have the orientation problem on photosphere. My screen does not flicker.

I have this same exact problem with an HTC One XL. I have not found a fix for it.
I've tried flashing every flavor of jellybean there is. It oddly seems to not happen if I use a sense version of jellybean. But I hate sense and want vanilla android.
AOKP, AOSP, modded, unmodded, doesn't matter. I get this annoying graphics glitch when I try to scroll around using maps or photosphere.
I hope it's not purely hardware related, and that there's an easy software fix for it.

[Q] Various potential hardware/sensor related issues

Hey guys,
I have a VZW HTC One M8 with the following version details:
Cyanogenmod 11-20141112-snapshot-m12-m8
Unlocked bootloader
M8_WLV PVT SHIP S-OFF
CID-VZW__001
HBOOT-3.16.0.0000
RADIO-0.89.20.0222
OPENDSP-V26.2.2-00538-M8974.0106
OS-
eMMC-boot
This phone came to me with a clean Cyanogenmod install on it. I wiped it anyway to be sure. I have an S3 that I've been running CM11 on up until I got this phone so I'm no stranger to Cyanogenmod.
My issues appear to be randomly occurring and I cannot seem to pin down what is causing it or when it actually happens. Here are the various issues I'm seeing:
1. Screen fails to reorient when being turn - this happens system wide, even the home screen fails to reorient. Perhaps a problem reading the gyro sensor?
2. Lux values get stuck, usually at 45. Ambient light sensor?
3. Double tap to wake stops working - need to use the sleep/wake button to turn the screen on. Can still double tap the status bar to turn the screen off
4. Incorrect battery reporting - The battery appears to drain normally and at a consistent pace, however if the phone is shutoff or rebooted I will sometime see a huge drop when the phone boots back up.
I have a screenshot from the phone this afternoon but cannot post it (attachments fail to upload on this forum). I can probably PM it to you though.
I noticed if the phone gets to 5%, sometimes ~15% it will just turn off because the battery has actually died but the OS thinks differently.
The first 3 issues fix themselves after reboot.
Oh and I've noticed that the profiles feature doesn't work properly. If the ring mode is set to vibrate on the work profile, it will stay in vibrate even when it switches back to the default profile which is set to ring mode. The phone will not let me set custom notification sounds with Profiles enabled either. Example: Hangouts uses the notification sound as set by the default in Settings. I cannot change this. I can turn off Profiles and I can change the notification tone on Hangouts all day long.
Not quite sure what I should be looking at here so any guidance or suggestions would be much appreciated. Let me know if you need any more details.

You answered the question yourself in the second sentence of your post.

beaups said:
You answered the question yourself in the second sentence of your post.
Click to expand...
Click to collapse
beaups,
Was really hoping for a more descript answer. Can you please elaborate?

cstokes86 said:
beaups,
Was really hoping for a more descript answer. Can you please elaborate?
Click to expand...
Click to collapse
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.

beaups said:
You are running cm. Probably known cm bugs or possibly you need different firmware. Either way, there's no such thing as a hardware problem until it exists on stock software.
Click to expand...
Click to collapse
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.

cstokes86 said:
I forgot to mention in my original post:
I already searched around for the various issues I'm having but was not able to find any mentioning of them in any known issues lists. Was hoping to see if any devs on here had suggestions on things to try.
Click to expand...
Click to collapse
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA

beaups said:
Search better. This took me less than 5 minutes:
http://forum.xda-developers.com/showpost.php?p=56813202&postcount=3167
http://forum.xda-developers.com/showpost.php?p=56733227&postcount=3140
http://forum.xda-developers.com/showpost.php?p=56719654&postcount=3130
and many, many more all in that thread, which happens to be the CM thread for your phone.
Oh, and welcome to XDA
Click to expand...
Click to collapse
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.

cstokes86 said:
Thanks for those links. I was looking in the official known problem lists for Cynogenmod for these issues to see if they actually confirmed anything. I will look at possibly installing a nightly and testing with that, but I'm a bit reluctant to go that route since this is my daily driver.
Click to expand...
Click to collapse
If you are looking for stability, flash a sense based ROM. Its just the way it is.

beaups said:
If you are looking for stability, flash a sense based ROM. Its just the way it is.
Click to expand...
Click to collapse
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?

cstokes86 said:
^ Can't disagree with that, but I loathe the bloatware and manufacturer UI and skins they put on their devices, not to mention the freedom and functionality I lose out on by going back to a more or less stock experience. If I want stock non-CM, I'll just flash 5.0 GPE and see how that goes, but I've already tested with that as well and missed the functionality that CM brings. :/
Win/Lose.
Do you think the firmware (not the ROM/OS) is highly out of date and should be updated by now?
Click to expand...
Click to collapse
Yes you should update that firmware. There's an emmc controller firmware update amongst other things included you should have. Have you tried gpe or stock with some of the xposed modules now available?