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.
i switched from galaxy to xperia range, so I am new to this area, I noticed few threads people asking to downgrade, so that's why I have following question:
i have currently installed 14.2.A.1.136 stock version ... and getting a notification of OTA update to 14.3.A.0.681?
any issues on 681 like getting hot, unstable etc?
The update do not respond the same for everybody. Maybe you will like it like don't. If you will update just wipe everything to make a clean installation, then if you are unhappy or you face some problems then you can revert to 4.3. There is no perfect firmware nowhere.
infra4800 said:
i switched from galaxy to xperia range, so I am new to this area, I noticed few threads people asking to downgrade, so that's why I have following question:
i have currently installed 14.2.A.1.136 stock version ... and getting a notification of OTA update to 14.3.A.0.681?
any issues on 681 like getting hot, unstable etc?
Click to expand...
Click to collapse
It's strange you're not getting the OTA update to .757...
The best way is to see for yourself, try it out and if you don't like it, use Flashtool (or PC Companion?) to downgrade.
I personally like .681 because of Kitkat There was a few issues on my device (Xperia Z1), such as unable to change the lockscreen wallpaper, but that was fixed by fresh-installing the firmware, not upgrading. As for performance, that's device specific. On my Z1 it runs pretty good except for random lag on the home screen, but I corrected this by using a different Home launcher. My phone did get a tad bit hotter with my .681, but hardly noticeable.
.681 is pretty stable IMO, I recommend trying it. But again, it's solely based on opinions.
thanks guys, I do not see much that I am missing by not going to 4.4 kitkat.
phone works fine now.
I was hoping to see replies saying that something that I am missing by not upgrading ... something significant...
only sometimes when I press camera button to start camera from locked sleep phone, it doesn't work... i have to use power button once to make the camera button work.
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
That is happening on every 4.4 I think. It was on CM10.1, CM10.2 too.
Lag on calling screen
Klaas68 said:
Because of the very laggy behaviour of my I9070 after the official upgrade to JB, I decided to go for KitKat after reading good reviews about it.
All this is pretty new for me, but I succesfully rooted the phone, installed the ClockWorkMod recovery tool and flashed to Android 4.4.4.
The build number according to the settings menu is: carbon-janice-userdebug 4.4.4 KTU84P 3a697bce2f test-keys
Overall the performance is excellent and the nasty lags in the youtube app are completely gone so I can finally watch movies again Also I am pleased about the look and feel of KitKat.
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
krazzykuldeep said:
It happsens in all roms even in CM too
but now after 4.4.3 in carbon rom it has almost stopped....
Reflash your rom and try it
I use the same
hit the THANKS button if it helped you
Click to expand...
Click to collapse
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Klaas68 said:
I use Carbon rom 4.4.4, to be exactly the ROM-file CarbonKK_janice-4.4.4-20140627.zip
AFAIK this is still the most recent version. Maybe the problem was even worse with the previous builds.
But I did not have this problem with the, otherwise pretty laggy official JB upgrade from Samsung.... lets hope for a new update from Carbon that gets rid of the issue.
Click to expand...
Click to collapse
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
krazzykuldeep said:
Hmm
Have not downloaded this version bcos the mega downloader gets stuck all the time
if the problem exists then why dont you try the AOSP rom
Off course it does not provide with all the features but its quite stable and we definately have gravitybox or many other apps for the additional features
Click to expand...
Click to collapse
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Klaas68 said:
I will definately consider this, I have not a very clear view on the differences between the different ROMS and tend to get lost in the flood of information on this site and others... I am not interested in lots of features but just want a fast, lag-free phone with the normal features: email, gmail, whatsapp, youtube, Google maps etc. If AOSP is more stable than Carbon, I will surely try it.
Click to expand...
Click to collapse
I installed the AOSP rom and it seems stable and maybe the call delay issue is better, still have to test it more.
I do however miss some nice functions which were present of the Carbon ROM:
- separate lockscreen background
- disabling the annoying Google Now bar on the homepages
- some fine tuning in icon colors
- kliing an app by long-press the back button
- defining hotkeys e.g. for the camera
and some more..
Is there maybe some package to install to add functions like this to the AOSP ?
Klaas68 said:
...
Click to expand...
Click to collapse
Use Xposed module for all what you need. Gravity Box or others module..
R_a_z_v_a_n said:
Use Xposed module for all what you need. Gravity Box or others module..
Click to expand...
Click to collapse
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Klaas68 said:
Unfortunately the AOSP-4.4.4 ROM (build 20140620) is on second thoughts not working for me.
Though the install of the ROM and GApps went fine, I discovered that I had no internet when leaving my home with Wifi, and it appears that I had no connection with my provider and the icon always showed the R of "roaming".
Even after a new fresh install without the GApps the problem persists. The setting "Mobile data" appeared to be torned off, and ehen setting it to on, the triangle with exclamation mark and the (translated) message "The data connection has been broken because you left your home network while data roaming was turned off" (hope my translation makes sense).
So accessing my 3G network appears to be impossible and tham makes the build unusable for me. I installed the Carbon Janice 4.4.4 again and everything worked fine.
With the pa_gapps-mini.4.4.4 the system is up and running again and the incoming call delay is still somewhat of an issue but no show stopper. So for now I go that way...
Click to expand...
Click to collapse
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
shut_down said:
Check if you have set up APN, on some ROMs it is not possible to be set automatically by provider. So you need to fill it manually. And you must do factory reset on ROM change to avoid those kind of problems too.
Click to expand...
Click to collapse
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Klaas68 said:
Do you mean a factoery reset just after installing the ROM and Gapps? I think indeed I have not done that.
For now it is working fine with Carbon but I will definately remember your tips for a next flash
Click to expand...
Click to collapse
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
shut_down said:
Yes, factory reset before or after (just need to to it when you change ROM) install of a new ROM. Unless you just doing update to new version of the same ROM. Then you do wipe cache and dalvik cache.
Click to expand...
Click to collapse
OK I did those 3 steps before flashing the new ROM. Sometimes I even had to do it twoce because the ROM did not install and raised a error 7 or so...
I think it was more a problem with the APN configuration and never before needed to do this manually...
Updating from 4.4.2 to 4.4.4
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
harsh3793 said:
Hello friends,
I am new on XDA forums.
I am currently using Carbon rom 4.4.2.
If i want to update it to 4.4.4 then will i lose my all Apps, games etc currently on my phone or not.
Thanks in Advance
Click to expand...
Click to collapse
If you dirty flash (just wipe cache/dalvik and install) the new version, you want loose your apps etc.
But I would recommend to do a clean flash (factory reset and format system), but before backup your apps with Titanium. After installing the new version you can restore your apps and data.
But anyway, before wiping/installing anything do a nandroid backup. So if anything went wrong, you can go back in just a minute.
solution ?
Klaas68 said:
The problem is that when receiving an incoming call, it appears that the caller does not hear my voice during the first 5 seconds or so. Mostly this is the time that I say "hello <my name> speaking" but this is not heared by the caller. Now I am forced to wait those few seconds before saying my name. I tested it with my other home phone line and this unwanted behaviour does seem to be persistent.
It is pretty annoying and really a flaw to this otherwise great update. Any ideas how to fix this?
Click to expand...
Click to collapse
Has anyone solved this problem ? I have this problem with every rom that i've tried. I'm losing patience with android phone.
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Wysłane z Light-fonika 1-2 ....
...
MikiGry said:
@ian2189
Dont blame google for samsung mistakes. It isnt android problem couz my friend is using sII and there isnt any problem. Our phone is not an flagship like s 5 or nexus 5 so it has problems.
But this dealy is usefull sometimes.
For example if u want to unsware the call and u are stressed u can take a deep breath before u hear voice for other side
Click to expand...
Click to collapse
I am stressed when receiving an incoming call and caller don't hear me. I wait from mobile phone calling without problems.
I just wanted to know if there is a ROM without this problem or if anyone have solution.:cyclops:
@ian2189
This is our phones problem. 99% of the users (me too) were expiring this since gingerbread 2.3.6 . So i think there isnt a solution. I now why it is happening but it is unfixnable.
Wysłane z mojego nexusowego tablecika.....
Yeah... I even bought another phone because of this...
Hi all,
I had my One M7 Sprint for several years, i got an issue that it freeze while i'm using and reboot, then there is no longer appear the status bar. Beside that i got camera issue as well, open the camera app and it quit intermediately after that.
So strange that if i flash back to Jelly Bean or Kitkat, my phone worked again with no camera. The camera seem like cause by hardware issue. Sometime worked, sometime didn't.
Have anyone advise me about this issue?
Thank you!
boomlord said:
Hi all,
I had my One M7 Sprint for several years, i got an issue that it freeze while i'm using and reboot, then there is no longer appear the status bar. Beside that i got camera issue as well, open the camera app and it quit intermediately after that.
So strange that if i flash back to Jelly Bean or Kitkat, my phone worked again with no camera. The camera seem like cause by hardware issue. Sometime worked, sometime didn't.
Have anyone advise me about this issue?
Thank you!
Click to expand...
Click to collapse
Never heard of that, but if you want to really test the hardware, the best thing to do would be to run the RUU and then test it running pure stock. If you still have the issue, then I'd say it's most likely hardware, if not, then you'll be able to use the phone normally. Worth a shot I think.
I don't know if this has been answered anywhere and I am sincerely sorry if it has been.
I am faced with a peculiar problem with my 18K Mi Mix. The phone came with 8.2.5.0. When no updates were forthcoming I decided to root and install a custom ROM. Everything went fine and the phone booted up and I installed my apps. I was using 7.8.31 version of the Beta ROM. However I was faced with a problem of a crackling or static like noise in the background while making calls. The speakerphone and headphone or Bluetooth headset has no problems. Only the call speaker. So I imagined it to be a hardware problem and went back to stock. To my surprise, the problem vanished in stock ROM and any ROM based on Android 6.0. It is only present in Android 7.0. So I guess it might have something to do with the Android 7 ROMs themselves.
Has anybody here faced such issues. If you have kindly help me. I am kinda addicted to the 7.0 ROMs and wish to stay on them if I can get rid of this issue. I was using the Global stable ROM earlier.
Thanks for any help.
shantanil said:
I don't know if this has been answered anywhere and I am sincerely sorry if it has been.
I am faced with a peculiar problem with my 18K Mi Mix. The phone came with 8.2.5.0. When no updates were forthcoming I decided to root and install a custom ROM. Everything went fine and the phone booted up and I installed my apps. I was using 7.8.31 version of the Beta ROM. However I was faced with a problem of a crackling or static like noise in the background while making calls. The speakerphone and headphone or Bluetooth headset has no problems. Only the call speaker. So I imagined it to be a hardware problem and went back to stock. To my surprise, the problem vanished in stock ROM and any ROM based on Android 6.0. It is only present in Android 7.0. So I guess it might have something to do with the Android 7 ROMs themselves.
Has anybody here faced such issues. If you have kindly help me. I am kinda addicted to the 7.0 ROMs and wish to stay on them if I can get rid of this issue. I was using the Global stable ROM earlier.
Thanks for any help.
Click to expand...
Click to collapse
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
james1089 said:
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
Click to expand...
Click to collapse
Thanks. Will give it a try.
Finally cracked the problem. As I had suspected, this is a software flaw. The whole issue was being caused by the proximity sensor. The moment I turned the proximity sensor off all problems have vanished. Have replicated the problem a number of times, so am pretty sure that is the cause. Thanks everyone for your help and suggestions.
you don't fix the problem we need the sensor
fred1311 said:
you don't fix the problem we need the sensor
Click to expand...
Click to collapse
You do need the sensor.
But since the problem is not happening with any of the stable version ROMs (I have tried Global stable 8.2.5 and China Stable 8.5.4), I am very sure its not related to hardware. So for the time being I am more than happy keeping the proximity sensor off and using Nougat 7.0 on my Mix. I am pretty sure this has something to do with drivers or firmware and will be taken care of, once the stable versions of 7.0 are released.
james1089 said:
Well you've already done the hard work so may as well stick RR rom on the phone. All problems have been ironed out and think you will be happy, I went back to miui awhile ago had crackling in calls although mainly on Bluetooth.
Click to expand...
Click to collapse
Even my Redmi Note 4 has that cracking or scattering sound when bluetooth calls are made. I found temporary solution that is Turn off the WiFi. Looking for permanent solution.