I've been running Liquidsmooth for the past 48 hours or so. Love the battery life, the overall functionality and stability. Great work! Much better on the whole than other ICS ROMS I've tried.
I've seen only three issues after doing my full wipe and flash of Liquid smooth.
1) Occasional system.UI stops. Oddly enough they seem related to the quick torch setting. Not a show stopper.
2) Liquid options, enabling JIT compiler for Dalvik does not actually set the check box. Again, not a Show stopper.
3) When on a call today, I received another incoming call. During this time, I was no longer able to hear the current call. Rejecting the inbound let me hear the current call again. That one is a bit odd as I've not encountered that behavior before with any other ICS ROM. I was using my bluetooth headset at the time, so not sure if there's a Bluetooth issue that shows up during a call waiting event.
If anyone else can confirm these issues that'd be good to know, as I didn't see mention of them in the dev thread.
Related
I've seen people complain of similar issues, but no solutions when searching. Regardless of if I call them, or I'm the one being called 30-50% of the time they won't be able to hear my voice. It's been consistent regardless of ROM (Stock, Cyan, Enom).
It may be a hardware defect (I had one of the earlier phones) but programs such as Shazam and Hertz, which use the mic to collect nearby sounds, work flawlessly and 100% of the time.
Has there been a proposed solution to this problem?
are you accidentally pressing the mute button?
No, mute's not pressed when I look at the screen and nothing changes if I toggle mute on/off.
Are you running a non-stock kernel?
This is also a new google feature. If your voice is that bad sounding, the nexus one cancels the other person from hearing it. This also happend to one of my friends that sounds like hes high half the time.
lol, harsh.
i've had the same problem before on cyan and today again for the first time on enom.
rebooting normally fixes it but i have no idea what causes it.
Do you use a task killer? I think this may have something to do with it, killing an app that phone calls require but I guess it would have the smarts to re-open it if it actually required it.
Same thing happens to me- I would shift position and move my hand and it will start working again. Super annoying.... i returned my phone and got a new one, and it is still happening. Arghhhh
Hello fellas,
I just installed ICS from this link
The sound works fine when playing music or notifications or whatever I do.
But when I'm making or receiving a call, my sound doesnt work. My phone doesnt ring or hear it ring when making a call and nor can they hear me at all.
The only way I can make a phone call is through bluetooth which makes me think that the speaker on the phone isnt configured correctly.
If the ROM is the issue which rom do you recommend for my DROID 3?
Thanks for your help!
This is known issue people are experience with CM9, Gummy, and AOKP. MotoBlur + Android 4.0.4 is based of AOKP inheriting its issues. Usually a restart or two fixes the issue, but it is somewhat random. I believe the issue involves bluetooth but I guess no one really knows. I heard toggling bluetooth sometimes fixes it as well.
However you say it doesn't even ring, I have never had it not ring. But have experienced the rest.
Tried that
I've tried restarting several times, doing it again as I type.
When I've also tried to toggle bluetooth off during a call but it didnt work.
Should I reinstall the ROM?
Ok so I deleted all data and cache.
Re-installed the ROM again and it turns out that bluetooth is messing with my in-call sound. My phone rings now (by default there was no ringtone selected) but when I toggle bluetooth on I cannot hear anyone or anyone hear me.
Band aid: Keep bluetooth turned off until it gets fixed.
Thanks for your help Senate9690.
Is there a different rom out there for Droid 3?
About that band-aid
I run into a the no sound on calls as well. I'm running ICS and have always left the Bluetooth off. For me it seems to happen occasionally after I interrupt music/audio playback by removing the wired headphones from the jack or incoming call.
Just flushing the cache and rebooting letting the cache rebuild seems to fix it without the need to a re flash or factory reset. It is good to hear I'm not the only one experiencing the issue.
I ran into that issue with cm9 (selfkang) as well. Usually just toggling bluetooth off did the trick, and when it didn't, rebooting always worked. The sound issues were only in-call related, and notifications/ringtones worked just fine. I switched to Axiom and aside from the know in-call issues, toggling bt off works perfectly without rebooting.
In my opinion, Axiom is an excellent rom. My only drawback is the amount of battery sucked dry when the screen is on/keyboard out, however under very minimal use it has lasted well into the next day. Hash's original cm9 has prevailed as the battery king in my ICS D3 testing, but Axiom has made me a happy camper. I didn't spend much time with Gummy or the original AOKP though. That's the beauty in rom choices; different strokes for different folks
Sent from my XT862 using XDA
magedassad said:
Hello fellas,
I just installed ICS from this link
The sound works fine when playing music or notifications or whatever I do.
But when I'm making or receiving a call, my sound doesnt work. My phone doesnt ring or hear it ring when making a call and nor can they hear me at all.
The only way I can make a phone call is through bluetooth which makes me think that the speaker on the phone isnt configured correctly.
If the ROM is the issue which rom do you recommend for my DROID 3?
Thanks for your help!
Click to expand...
Click to collapse
A lot of Android phones are having this issue. Try this app and see if it works. The Pro version lets you route sound during phone calls too!
http://play.google.com/store/apps/details?id=com.woodslink.android.wiredheadphoneroutingfix
Bluetooth Share?
Hi,
This is my first post, but I have encountered an issue similar to this before. I work for a company that makes Bluetooth headsets, primarily for truckers, and this is a fairly often related experience. I would describe it as "dead air" on a phone call. Often, if the headset supports it, the A2DP stream will be fine. I don't know why, or where we found this from, but we have found that often if a user goes into their application settings, to "All" apps, there will be an app there titled "Bluetooth Share". Sometimes there is more than one, but only one with show an amount of data. Going into this, clearing that data, then restarting the phone has been reported to help resolve this issue.
Try it, and see what happens. Not just Motorola phones do this either, but it seems to be associated with Android 4.0.x and up.
Thanks,
Alex.
I belive this rom has a bug where the speaker/earpiece doesn't work if Bluetooth is on.
Sent from my XT860 using xda premium
Make sure bluetooth is off
I am a new G2 owner (and frankly a new and inexperienced Android user), and have been noticing some small, but annoying, issues with any KitKat 4.4.2 ROM that I flash to my Verizon G2. I'm wondering if anyone knows of why they exist, possible workarounds, or any general solutions/explanations. So far, I have tried a CM11 nightly from last weekend, and an AOKP nightly from yesterday.
Most of the issues exist during a phone call, and still occur even when I have full bars of LTE service.
For one, speakerphone volume is pitiful. With the volume maxed, I can still barely hear people speak. Non-speakerphone volume is fine.
Secondly, the facial sensor does not seem to function at all. When I end a call, or pull the phone away from my face mid-call, the screen stays black and I have to double-tap the screen to turn it back on.
Thirdly, I get this weird "tapping" noise through the earpiece (not the speaker) of the phone when I'm on a call. It is definitely a sound that is on the phone, although I havent been able to find the file for it...it's almost like the sound the OTA makes when you tap-on or tap-off, or like a bubble popping (anyone know the Facebook Messenger notification sound? Very similar). I havent been able to pinpoint what causes the sound to play...no combination of moving the phone around or pulling it away from/putting it back towards my face prompts it or makes it stop...it just happens. It is not constant, but over the course of a 30 minute phone call, I will hear it at least a dozen times. It usually plays two successive sounds. People I'm talking to do not hear it...only me.
Are these just issues we have to live with? At first I thought it was CM11, but after getting the same exact issues with AOKP...I'm wondering what the deal is?
All are known and being worked on. They are minor bugs that most users can deal with or find work arounds
-VZW LG G2 VS980
Let's try this again.
I've got the N6 and so far it's great but one of the things that I absolutely hate about it is the Ascending Ringtone "feature" that either Google or Motorola has put on this phone. I'm one of those wacky people that likes to actually hear my phone ring, or alarm tone, or text notification at the volume that I set manually, rather than have the phone start the tone whisper quiet and then go up in volume.
I've heard of a custom ROM or two that have removed this feature (or at least made it OPTIONAL) but in my own personal experience, custom ROMs have always been too buggy for my taste. I wasn't exactly planning on rooting this phone, but I may just have to do that for a custom ROM that turns the ascending ring feature off or removes it all together. Sorry for the ramble, but I suppose my question is this: Is there a Custom ROM out there that is essentially a stock ROM - with absolutely nothing changed except for this? Is changing this feature something that someone like myself could accomplish by compiling a ROM on his own? I have no experience with this, only experience with flashing downloaded custom ROMs.
I don't mind stock 5.0.1, I just want to get rid of that ringtone issue. I've tried the "Disable Increasing Ring" app, but it has not helped.
To be clear: just flashing a custom ROM or editing an mp3 to a different volume is NOT what I'm looking to do, as this 'feature' is affecting all sorts of notifications, and not just the ringtone.
Thanks for any help, or helpful suggestions.
I agree, I can't stand the decreased to increased volume when I get a call or notification.
The funny thing is that it doesn't happen all the time for me. I wonder if it's a bug with the phone hardware or possibly software.
On my Nexus 6, it only affects the ring (call) signals. The notification sounds aren't affected at all.
Still very annoying, since we can't make this choice ourselves. I'd hate to need to flash another
ROM, due solely to this crap! Too bad the "Disable Increasing Ring" app doesn't work on N6.
It worked flawlessly on my old Note II. I wish the dev would extend the functionality for us.
bump.
I've been looking for a fix for this for a while as well. This is, quite possibly, the worst "feature" Google ever added to their ROMs. It makes it sound like the phone is broken and it's beyond annoying.
Yeah I agree, this ''feature'' should have been optional just like the encryption should have been optional too....
Let's keep our fingers crossed that Google adresses
this crap within reasonable time. It's a pain in the b...
I thought I was the only one who thought this was ridiculous. You've already missed like 2-3 rings and wasted time left to answer the call, sometimes. I can't wait for more "official" custom ROMs.
bump.
Yes. This "feature" sucks. Hope it goes away or becomes optional.
I have the same issue and can't find any option to disable this.
Hope google will make this optional the increasing ringtone.
EDIT: Btw this "issue" is present on custom ROM's aswell i think.
I really hate it also...can someone please kill it
Just tried cyanogenmod 12 (nightly 20150126) and it's there also. In this case it is even worse because CM's built in increasing ringtone feature does not work very well maybe because of the default N6 behavior.
bump.
Wondering about this also.
I was researching this issue for couple days and I found just few custom roms that fix this issue.
1) MeanPop rom. It's a bit outdated (based on 5.1.0), but works like a charm and very near to the original stock (personally tested and as I understood all sounds are just starting playing with a delay)
2) Benzo rom (based on Euphoria rom). Haven't tried it, but people say all sounds work perfectly (it looks like its highly customized rom)
3) Euphoria rom (Personally tested - fast, stable, customizable). For some people it didn't work and I found suggestion to flash first franco kernel and then the rom. That's what I did and everything works perfectly like it should be.
Couldn't find any other roms or mods. Programs like "Disable Increasing Ring" don't work, but maybe it will with custom kernel - haven't tried.
I'm running latest Euphoria ROM with the increasing ringtone already disabled but still it plays the ascending ringtone for some reason. Anyways my simple fix was I used Nero Soundtrax and added a 2 second delay to the beginning of the mp3 file I used as my ringtone and it sounds perfect no more ascending ringtone.
I didn't notice this on the chroma rom, but after flashing stock 6.0.1, this issue appeared.
I don't think it is a hardware bug. For me, other notifications are fine. Ring and alarm are the two that are problematic.
It's super ****ty that it affects alarms. It's at least 7 seconds after a timer reaches 0 until I start hearing it beep. Wtf... I mean 7 seconds isn't a huge deal in anything that I'm timing but WHY make it affect alarms?
Maybe I'm missing the point here, particularly with the last two posts. I have 6.0.1 MMB29S from January 4th 2016, and it has separate volume controls for Alarms & Timers in clock settings - "Gradually increase volume" - both allowing a certain number of seconds for the increase, including zero seconds, which I would take to be "off", right...?
I haven't tested this yet, since it's an option I didn't notice until I looked just now, but have the last two posters seen and tried it?
i hate this feature too.
来自我的 Nexus 6 上的 Tapatalk
Just enrolled my Pixel 7 in the android 13 beta program. So far so good. Anyone else using the beta? What are your thoughts?
All good here, also.
Running just fine, as usual.
Since i haven't seen any value added i decided to roll back to latest stock. Oh my...it's just 500 mb and it takes literally ages to install..
It's fine. Nothing to write home about.
I just installed it about a 1/2 hour ago. Mainly for the battery stats to show since last charge like it used to, but mostly for the Clear Calling. I make a lot of calls, and from early impressions from other users, it makes the already great call quality that much better.
Update on my call experience. With Clear Call enabled the caller sounded very muffled, and faded in and out. During the call I turned off Clear Call, and they instantly sounded like they were right next to me. I also tested it on myself by calling my voicemail. With it enabled I sounded a bit off/muddled. With it disabled I was very clear. I'm not sure what's going on because it supposed to be the opposite. Maybe it's just for loud/noisy area calls? All my test calls were in a quiet room.