Related
My 2.1 powered Hero is having a few speed problems, and one of them is that when my phone is ringing, the vibrator continues shortly after I've picked up. Quite annoying for both me and the caller. One time it didn't stop, not even after I hung up again, I had to shut down then phone completely!
So does anyone have suggestions how to fix this? I guess its a lag problem because the phone feels slow other times aswell, for example now when typing.
The problem is my phone's not even filled up with Apps etc, and I use an appkiller. Also the problem is there almost right after I reboot the phone.
I use the original HTC Rom running android 2.1. Have replaced sense with launcherpro though regarding the homecreens and appdrawer.
Sent from my HTC Hero using XDA App
bjoernbertelsen said:
My 2.1 powered Hero is having a few speed problems, and one of them is that when my phone is ringing, the vibrator continues shortly after I've picked up. Quite annoying for both me and the caller. One time it didn't stop, not even after I hung up again, I had to shut down then phone completely!
So does anyone have suggestions how to fix this? I guess its a lag problem because the phone feels slow other times aswell, for example now when typing.
The problem is my phone's not even filled up with Apps etc, and I use an appkiller. Also the problem is there almost right after I reboot the phone.
I use the original HTC Rom running android 2.1. Have replaced sense with launcherpro though regarding the homecreens and appdrawer.
Click to expand...
Click to collapse
It sounds like a typical Sense UI issue...very laggy. Easiest solution is to root your phone, and install another ROM. CM6 is great, and it will get you up to FroYo (2.2). The lag will be gone, and your phone will work much better.
I was kind of hoping that wasn't necessary, but maybe I'll give it a try. Any link to the easiest way to install a custom rom? Don't know how to although I've read a lot of confusing guides a while ago.
Sent from my HTC Hero using XDA App
BTW is there a way to remove/disable sense on my hero and go so stock android with launcher Pro, WITHOUT rooting and flashing a custom rom? So its easy to go back to sense if I think stock android is too ugly?
Sent from my HTC Hero using XDA App
You dont NEED any kind of killer. Get rid of your junk apps, just delete them all. Disable all the vibrate options for everything(may not be necessary) and reboot. Run some tests. Is there a process popping that you think causes it? Delete its source.
bjoernbertelsen said:
I was kind of hoping that wasn't necessary, but maybe I'll give it a try.
Click to expand...
Click to collapse
You won't regret it one bit Trust me...
bjoernbertelsen said:
Any link to the easiest way to install a custom rom?
Click to expand...
Click to collapse
CM6 is my favorite. Here's the link http://forum.xda-developers.com/showthread.php?t=755795
Root - Do a Nandroid backup in case you ever want to go back - Wipe Data - Flash - Enjoy
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
Your search method must be flawed, as this is a known & frequently discussed issue.
timmyjoe42 said:
The audio both from the speaker and headphones only seems to work after a reboot. I have no idea when it stops functioning.
This was a problem from day 1 with the free elephant kid book using the Read To Me function. I just had it happen with the music player, both the native one and MortPlayer. I had originally assumed it was a glitch with the book.
If a reboot fixes the problem, it's a software issue, right? Why did a search here not produce any similar threads? If I'm alone here, then it's a hardware issue and I'll need to unroot and return it, right?
Click to expand...
Click to collapse
It's defective. Get a new one.
Thanks for the reply.
Now to unroot...
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
When you get your hands on the new one, before you leave the store do this. After power on & such, try the audio (V0l + -). Works? Put to sleep for >10sec. Wake & test audio. No-work? Reboot, (Long power press) Try sleep/wake sequence again. If it works you are golden, now check a few other things & go home & root it! If it fails the test, don't let the Nook Genius tell you that you should let it charge for at least 4 hrs. before testing. The three that I have received had between 50% & 90% charge OOB. That's plenty for it to work properly, assuming the battery level meter is accurate. Put together your own checklist based on info on this forum. Crossword to test edges of screen, kbd. when charging from wall adapter etc.
Good luck, when you get a good one they are solid!
kev
trumpet444 said:
Mine had the same exact problem. Audio usually stopped working after the screen went to sleep for the first time after a reboot. I recently flashed the 900mhz "screamer" overclock kernel and I've yet to have an audio problem since then. As much sense as that does or doesn't make, it seemed to fix the problem for me. Its worth a try. Hope it works for you (if you haven't already unrooted and returned by now)
Sent from my Droid using XDA App
Click to expand...
Click to collapse
Interesting! That would support the thinking that this issue is related to timing & initializing the audio codec or something related. Hardware specs may be skewed just enough for it to not work when waking up. That's actually encouraging! Means that all those with this problem may see a F/W fix if they don't want to re-clock it.
Cheers,
kev
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
timmyjoe42 said:
Well, I unrooted and restored it to factory new using the 9 reboot method. This brought the device back to 1.0.0. I then went back to the store. The manager came out, took the device, and said "it needed 1.0.1 to fix the problem. Let me load it for you." I was thinking, "whatever dude. It had 1.0.1 on it and it still had the issue." But the guy was super nice and ran off with the device to some back office. He came back while it was installing 1.0.1 and it's working fine now. I kept trying to get it to recreate the problem with no luck. (So it actually is good luck.)
I'm assuming the 1.0.1 software update didn't install properly the first time.
I could have done all that myself without going to the store.
Click to expand...
Click to collapse
That's interesting. I had the audio/sleep problem with 1.0.0 & exchanged it for another 1.0.0 that worked fine. ?????
All,
We don't have an ICS Bugs thread going on. I wanted to check with some of the people here on XDA to see if they are experiencing what I am. Currently on .213, but most of these bugs I've seen since the begining. Oh, I'm also in Canada running on 3G HSPA+. I'm stock, but rooted with safestrap installed.
1) When placing a phone call, the phone hangs up immediately (you here the disconnected beep), then retries the phone call a few seconds later (it always succeeds). I have tried this on a freshly wiped phone and found the same experience. I have also tried disabling the Assisted Dialing, but have found ikt's the same thing
2) When using Google Chrome, if there is a input box, most of the time my keyboard won't appear (I'm using Swype as my default keyboard)
3) Phone runs hot sometimes, and when it's running hot it slows down to a halt. Usually happens after a day or two without a restart
4) My photo doesn't appear in the text messaging app (worked in AOKP/CM9 on my D3, as well as it works on my gf's Nexus S)
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
podspi said:
The only bug I noticed was that it initially booted up in global mode, and wouldn't connect to 4G/CDMA. Switching it to CDM+LTE fixed the issue and I haven't seen a bug since (213).:good:
Click to expand...
Click to collapse
Is your chrome working properly? Specifically the bug I mentioned in the OP...?
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
podspi said:
I didn't comment on that because I use Opera
Just tried the Chrome Beta now just to see, and I can confirm I am seeing the same behavior. I use Swiftkey, so it isn't a Swype-specific bug either.
What exactly is the difference between Chrome and the built-in browser? Aren't they both Webkit-based? Why is Google bothering to work on both?
Click to expand...
Click to collapse
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
I'm in the US also running .213
I haven't noticed any bugs, its working fine for me. I do not use chrome beta so I can't comment on that. The stock is not too bad, I don't use it much anyways.
Sent from my DROID4 using xda app-developers app
danifunker said:
Chrome is way faster at many things since it users hardware acceleration for video. Does text input work properly on opera?
Sent from my XT894 running ICS
Click to expand...
Click to collapse
Text entry works fine in both the stock browser and Opera. BTW, Opera also has hardware acceleration, which is why it never worked in any of the Frankbuilds of ICS based off the GB kernel ... So you can have your teh snappy and type with it too :laugh:
I'm on the 212 build and i can't screencap using power + volume down.
Is this fixed in 213 or am i just doing it wrong?
Also on 212 i can't control the default google music app or winamp from my bluetooth headset when the screen is off. I could do this before with the same version of the winamp app when i was back on gingerbread. I tried upgrading winamp, but that did nothing. Is there any change in 213?
Thanks ahead of time
Edit: just tried it and the volume down + power combo worked. Lol
One question, possible thought to ponder.
Are the bugs being described here really bugs of Android 4 or are they bugs in the individual app itself not being fully compatible with Android 4 yet?
Do similar bugs happen on a non-motorola device with android 4?
I'm considering flashing one of the leaks, so I'm trying to understand how you are sure these are ics bugs before I make the leap and run into issues.
Thanks.
Apologies if this constitutes hijacking the thread, if it does let me know and I"ll edit it to delete the question.
I was able to figure out bug #4, I had to login with my Google+ account again, since the update yesterday everything seems to be working fine.
Bugs 1 through 3 still exist, although I've switched off Global mode for now and put it to GSM only, it seems like the phone runs a lot cooler in this mode.
Even after updating Chrome to the final version, I'm still experiencing that text input bug. Maybe it's a Motorola issue... Can't wait for the next version of the leak!
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
podspi said:
I have tasker reboot my phone every morning at 6am. The phone doesn't need to be rebooted every day, but it ensures that it is fresh and ready to go every morning :laugh:
Nothing more annoying than trying to do something with your phone and having to reboot it because it is slow for whatever reason.
Click to expand...
Click to collapse
for this reason I think there will be other leaks, ICS is supposed to handle killing processes much better than GB, however the settings seem to not be aggressive enough in 213.
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
podspi said:
Probably there will be, though I likely won't update again for a while. Don't feel like losing all that data...
Click to expand...
Click to collapse
I don't know, just had a random reboot after watching a youtube video in firefox, most likely memory related, not sure who's fault though, Motorola or Firefox. gotta root and use system tuner to change memory mgmt states.
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
That is a great idea. Though there hasn't been another leak since 213, so
Notification Bar Sticking/Wont Pull Down
I am on 212 currently, and I have noticed in 208 and 212 something that has happened only twice so far. Today, I just tried to check my notifications, and the bar will not pull down.
After a reboot it works fine, and it has only happened 2 times in the past couple weeks since the leaks first appeared.
Obviously it is a minor glitch, but just thought I'd throw it out there in case anyone else has seen it and overlooked it. :cyclops:
danifunker said:
You could just do what I do: once you have root install safestrap and then take a backup of your phone before flashing the upgrade.
Once you're all done upgrading, re-root and re-install safestrap, then do an advanced restore and only restore the data. Voilla, all your apps are back.
Click to expand...
Click to collapse
I have heard of a few others using this method successfully. If you are not using safestrap or just don't want to go this route take a look at the post link in my signature. It's a modified version of the original Droid 4 Utility and includes a script to jump from one ICS leak to another without losing data. It also flashes the GB files and the Kernel (boot.img) in one script, thus making it easier to go from one leak to another.
Regarding bugs, my wife got a razr yesterday. It wouldn't pull down the ICS update, so I just sideloaded it. We both run some of the same apps. So this gave me a chance to do side by side comparisons.The issue with some of the icons being small in the left top of the status seems to be a app issue. The chrome issue isn't present on the razr, of course there isn't a physical keyboard. Otherwise my 213 ICS seems to run great.
I found a new bug, it looks like GSM call forwarding doesn't work properly... at least it doesn't with my SIM card, I'm on Rogers in Canada.
Does Verizon support call forwarding? Does it work on there?
I have noticed in Chrome that pressing shift and then one of the symbol keys (like @) will only work if you hold the shift key.
More importantly I don't get notifications of app updates from google play. Check to see if you have any apps that need updating. Superuser had a update on July 1, dropbox yesterday and voodoo rootkeeper on June 28, I think. Anyone else?
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
vwmaniacx said:
I'm running TD 9.1, and prior was on 8.0. Tried both stock kernel, and a few other ones with no luck. At first when the sounds starts playing, the left speaker works fine, then with in a sec, it will fad to almost nothing. Is this something someone else has encountered? For all I know it has been like this since day one.. But I don't believe so.
Edit: I have also tried clean installs. i have not tried other roms yet.
Double edit: My xda search is not working, but google did for me. Found one other person having somewhat the same issue, but it was never answered. I hate to bump an old tread like that, after i have posted mine already.
[Q] HTC One speaker problem - One speaker turning off / mono sound
Click to expand...
Click to collapse
I have the exact same issue. Tried million ROMs, sound patches and tricks but nothing change. The easiest way to see the difference between the two speakers is to run the Audio Test using HTC Function Test by dialing *#*#3424#*#*
Finally, I managed to get S-Off and now I'm going to get back to 100% stock flashing RUU_M7_UL_JB_50_BrightstarUS_WWE_1.29.1540.3.exe, I'll do the test again and update the post.
EDIT: I'm full stock and it didn't fix it I guess I have to send it back...
BTW, what did you do? Did you fixed yours?
Running Sinless 5.1.5 now with elemental, everything works 100%. I guess for some reason my phone just didn't like TD, we all know they have a personality of there own..
Sorry for the long wait before response, I don't pay attention very well.
It appears that some of us have been dealing with a very annoying issue with the mic not working in calls, Google Now, video recording, or any other voice based service (utter!, etc.). Oddly enough, it works fine, and then suddenly stops working completely until a reboot.
No errors appear, or popups, it just doesn't work, as if the microphone hardware is not even attached. It is certainly a software issue, but not too sure what is causing it. There is another older thread that covers microphone problems, but is not related to this new issue caused by something wrong in Sense 6.
Temp fix 1: Boot the phone into safe mode.
Temp fix 2: Reboot, but not guaranteed to work for very long.
If we all share our settings, we might be able to pinpoint what is causing this issue.
- ViperOne 6.1
- ElementalX 14.1
- TWRP 2.6.3.3
- Radio 4A.25.3263.21_10.38x.1157.04L
- ProjectERA v15.2
- Viperdark 6.1.1
- Launcher: Google Experience
- Xposed with a few modules *Ruled Out*
EDIT: I think I figured it out. It is the caused by the IntenseBlast addon in ProjectEra. Flashing this should fix your issue: IntenseBLAST_UNINSTALL.zip.
I will test this out for a few days and see if the problem persists after uninstalling IntenseBlast.
EDIT 2: I reflashed IntenseBlast to test my luck, and... my mic seems to be working fine. I'm guessing now that countless reboots fixed the issue, and it was simply a coincidence that the time I uninstalled IntenseBlast... the microphone decided to work. As of now, there is no known solution, but you can try rebooting your device a few times.
EDIT 3: A full factory reset and reflash solved my problem completely.
EDIT 4: The problem was discovered to be Project ERA. However, v18 is said to fix the issue, so try that build than any older release.
Okay, I've only had the issue on ViperOne 6.x.x, and always had ERA, and Kangaroo kernel. Twrp 2.7.0.0. No xposed.
I know they changed the mics in later m7 builds. Would this be related?
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Okay, I've only had the issue on ViperOne 6.x.x, and always had ERA, and Kangaroo kernel. Twrp 2.7.0.0. No xposed.
I know they changed the mics in later m7 builds. Would this be related?
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Agreed. I updated my OP. I believe ERA is conflicting with Sense 6, more specifically, the IntenseBlast addon.
BuffMcBigHuge said:
Agreed. I updated my OP. I believe ERA is conflicting with Sense 6, more specifically, the IntenseBlast addon.
Click to expand...
Click to collapse
Not entirely sure that's it, as I had the issue both with and without intense blast, and on different versions of ERA, which didn't cause issues on other ROMs, or earlier ViperOne releases.
Sent from my HTC One using XDA Premium 4 mobile app
Has this issue been spoken about in the Viper M8 thread? I ask because since with our M7 devices and the Sense 6 is a port, could this be causing the spotty mic problems?
I have not been subject to this issue... Yet.
As far as some people not being affected at all and others may be a combination of the port and assembly plants. HTC had assembly plants in different countries and the parts come from different manufacturers.
I'm glad you started this thread cuz I'd like to find the answer & help other users too.
(I'm not a dev, just a user passing forward what I've learned)
ghostryder12 said:
Has this issue been spoken about in the Viper M8 thread? I ask because since with our M7 devices and the Sense 6 is a port, could this be causing the spotty mic problems?
I have not been subject to this issue... Yet.
As far as some people not being affected at all and others may be a combination of the port and assembly plants. HTC had assembly plants in different countries and the parts come from different manufacturers.
(I'm not a dev, just a user passing forward what I've learned)
Click to expand...
Click to collapse
I wonder if it might be related to the microphones, as htc only used the super good hdr microphones on the earlier builds, and switched to an inferior type after.
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Not entirely sure that's it, as I had the issue both with and without intense blast, and on different versions of ERA, which didn't cause issues on other ROMs, or earlier ViperOne releases.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm assuming that the requirements for the spotty microphone are a Sense 6-based ROM (i.e. ViperOne 6.x) and IntenseBlast installed. Could also be related to the microphone hardware.
There are also a few levels of IntenseBlast, I believe the Maximium and Ultimate Edition are the culprits, since the original edition has been shown to work. I'm guessing (I'm no dev, just a tester), that the addon disables the microphone due to power requirements to the speakers. Undervolting wouldn't help, but could be certainly related a short or cut off of power to the microphone hardware. That is why a reboot temporarily fixes the issue until it starts again. The mic seems to work fine by booting into SafeMode, further demonstrating how a mod on boot is causing the issue. However, I'm not entirely sure how IntenseBlast works, but I'm sure it contains a boot level script that doesn't run in SafeMode.
All I know is that uninstalling it fixed my problem so far. If I get it back, I would be sure to update this thread. Thanks for the insight everyone.
Edit: I tried out my luck and reflashed IntenseBlast Maximum edition... and my mic seems to be working fine. Seems that uninstalling it the first time coincidentally caused my microphone to work fine after reboot. I guess we can rule out IntenseBlast... and say that this problem is completely random... and is fully restored by rebooting the device countless times... until it cuts out again.
Have you found a solution?
I'm having the same issue and it's really driving me crazy.
Is it possible that the problem is caused by HTC Speak mod from Venom team?
rockwentz said:
Have you found a solution?
I'm having the same issue and it's really driving me crazy.
Is it possible that the problem is caused by HTC Speak mod from Venom team?
Click to expand...
Click to collapse
Not currently.
It won't be the speak mod, as I don't use it, and had the issue.
Sent from my HTC One using XDA Premium 4 mobile app
myrigon said:
Not currently.
It won't be the speak mod, as I don't use it, and had the issue.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I went ahead, backed up my user apps with titanium backup, wiped my data, and reflashed ViperOne 6.1. Haven't seen the problem since.
Sent from my HTC One using Tapatalk
BuffMcBigHuge said:
I went ahead, backed up my user apps with titanium backup, wiped my data, and reflashed ViperOne 6.1. Haven't seen the problem since.
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
i have the same settings as your's in the 1st post , im suffering now from this issue but what i noticed in my phone is that when i reboot the mic works as i open voice recorder and record and it works but when i use any app which access the mic like phone , viber the mic stops working
Nightf0x_007 said:
i have the same settings as your's in the 1st post , im suffering now from this issue but what i noticed in my phone is that when i reboot the mic works as i open voice recorder and record and it works but when i use any app which access the mic like phone , viber the mic stops working
Click to expand...
Click to collapse
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
BuffMcBigHuge said:
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
Click to expand...
Click to collapse
no i wiped system and data partitions , then clean installed 6.1
BuffMcBigHuge said:
Yes, that seemed to be the issue. When using the mic for the first time in any app that requires it, it works, but then any subsequent apps will not be able to access the mic thereafter.
A full factory reset and reflash is suitable to fix the issue. Did you dirty flash from 5.8.0?
Click to expand...
Click to collapse
reflashed rom , restored my apps and mods again this issue appeared i have feeling it is concerned with either xposed modules or the kernel
now wiping and reinstalling again for the 2nd time
Nightf0x_007 said:
reflashed rom , restored my apps and mods again this issue appeared i have feeling it is concerned with either xposed modules or the kernel
now wiping and reinstalling again for the 2nd time
Click to expand...
Click to collapse
Weird. What xposed modules are you using?
BuffMcBigHuge said:
Weird. What xposed modules are you using?
Click to expand...
Click to collapse
gravitybox , subsense of elementalx kernel , ice cube of ice cave xperia apps mod , halo floating window , fix for halo floating window , mutliwindow sidebar , sense 6 toolbox , expanded notifications + few other modules but not enabled
Reflashed rom and the mic is working properly for a week so far.
Perhaps the problem is from Project era; because I only flashed it along with IntenseBlast and HTC speak when I had the problem.
Xposed is not the culprit. I was using none of those mods when I had the problem.
Sent from my HTC One using Tapatalk
yes , i confirm it now zeroinfinity project era soundmod is causing this problem at least on my phone
wiped my device , reinstalled rom, kernel, mods, app, xposed mods., all have no issues but last thing i flashed is the soundmod which caused my mic to stop working , hopefully just before i flashed the soundmod i backed up my device just restored and everything now works
i will inform zeroinfinity cause i really need his soundmod:fingers-crossed:
Nightf0x_007 said:
gravitybox , subsense of elementalx kernel , ice cube of ice cave xperia apps mod , halo floating window , fix for halo floating window , mutliwindow sidebar , sense 6 toolbox , expanded notifications + few other modules but not enabled
Click to expand...
Click to collapse
Nightf0x_007 said:
yes , i confirm it now zeroinfinity project era soundmod is causing this problem at least on my phone
wiped my device , reinstalled rom, kernel, mods, app, xposed mods., all have no issues but last thing i flashed is the soundmod which caused my mic to stop working , hopefully just before i flashed the soundmod i backed up my device just restored and everything now works
i will inform zeroinfinity cause i really need his soundmod:fingers-crossed:
Click to expand...
Click to collapse
Holy S*** ... you have a Frankenstein phone ...how do you ever figure it out when things aren't working