Anyone else not able to get the radio to work?
I plugged headphones in. It said FM turning on.
I go into the menu of the application, refresh local stations but nothing is found.
Tried different headphones, Rom, and in 2 different cities ( I commute, I didn't just go to test this! )
Any help ?
Sent from my HTC One using xda app-developers app
milestoneman said:
Anyone else not able to get the radio to work?
Click to expand...
Click to collapse
Works fine here (UK)
Whizzed through the spectrum, found a load of stations straight away.
Reception on mine is quite poor in comparison to my s2 and s3 have not found the solution yet
Sent from my iPad using Tapatalk HD
Mine still not working :'(
Contacting HTC must be a dud. Dang!
Sent from my HTC One using xda app-developers app
Weird. My FM radio works; but when I turn on the radio, my WiFi connection stops working.
I'm awaiting a replacement for other reasons (white plastic around the side of the phone is bulging, backlight leaking from home/back buttons), though. So I'll see how that one is, once it arrives.
M_Woody said:
Weird. My FM radio works; but when I turn on the radio, my WiFi connection stops working.
I'm awaiting a replacement for other reasons (white plastic around the side of the phone is bulging, backlight leaking from home/back buttons), though. So I'll see how that one is, once it arrives.
Click to expand...
Click to collapse
If by backlight leaking you mean the buttons light up then that is normal, its so you can see them when it gets dark. Try looking again in bright conditions
Related
Just posted this as a reply to a thread in 'Themes and Apps' but thought it belonged in 'General' so I've echoed it here. The Admin can feel free to remove the double posting, take away my birthday, etc. if I've broken the forum protocol
==========================
I connected my HDMI cable for the first time since upgrading/rooting ZV8 and I couldn't get the screen to mirror. This is something I've used/done quite a bit before the update and I never had an issue at home or in hotels while traveling. Now for some reason the screen doesn't seem to want to mirror.
After fooling around with it for a while, I'm starting to think the problem it could be tied to the G sensor position - when connected, I'll re-position the phone and when close to landscape/vertical the screen will mirro of a few seconds and then quit. Could someone with rooted ZV8 give this a try and let me know if they're having problems?
Here's what I've done/observed:
I've rebooted and re-tried
I've checked all the right boxes under settings - connectivity
I've toggled screen resolution - 480/720/Auto
The status bar properly reports when the cable is connected and indicates the screen is mirroring (but it's not)
Most times the sound will mirror and occassionally occassionally the screen will do so but only for a few seconds.
Tried this with HBOGo, Netflix, and just swiping across home screens
Sometimes the screen mirrors nothing and sometimes a blue screen.
I get this same issue on my Galaxy Note...I feel your pain man, no help anywhere.
Are you using stock or broken out? Have you tried using in portrait mode and let the video load into landscape..?. I know my hdmi port on my phone is a very loose connect and I have to have it standing on end to get it to work. Cant say anything about sounds working or not I use a LCD monitor with no sound capabilities so I plug speakers in. Haven't had any software related to hdmi issues while on broken out...
Sent from my VS910 4G Broken Out 2.0.1 powered by Mt using xda app-developers app
meabrams said:
Are you using stock or broken out? Have you tried using in portrait mode and let the video load into landscape..?. I know my hdmi port on my phone is a very loose connect and I have to have it standing on end to get it to work. Cant say anything about sounds working or not I use a LCD monitor with no sound capabilities so I plug speakers in. Haven't had any software related to hdmi issues while on broken out...
Sent from my VS910 4G Broken Out 2.0.1 powered by Mt using xda app-developers app
Click to expand...
Click to collapse
Problem turned out to be a damaged cable. i replaced my $2.00 HDMI cable form Amazon with another $2.00 HDMI cable from Amazon and it solved the problem. We'll see how long this one lasts . . .
does anyone experience proximity and ambiant light sensor issues mines wont work. first i thought it was broken and bought a new sensor replaced it and it still wont work. the headphone jack and speaker works ok but not the sensors anyone? I also tried the sensor reading apps to see if its working. proximity wont show anything and the light sensor gives me between 4700-5000 lux but wont change no matter what light condition any help i cant even make a phone call without headphones anymore
What kind of rom are you running?
If you replaced it then its not a hardware issue it software then
Sent from my GT-I9000 using xda app-developers app
well ı've been using pa v2.54 before and flashed lots of roms in this 3 months i even flashed official rom went stock but still no luck :/
Really strange even with a new sensor and stock rom isnt working maybe the socket isnt good maybe a problem with the motherboard i dont know i thought it might have been a rom problem maybe the people here had a similar issue and they might help i wish you luck and i hope you find a fix
Sent from my GT-I9000 using xda app-developers app
thanks if it was due to the socket im guessing that the speaker and the headphone jack would also not respond... but yeah its a minor issue but really annoying
So I realized if I unplug the sensors the reading will still continue bounce between 4500-5000 lux so im guessing its not an issue of the sensor itself there should be something else... Right?.. Please back me up can be it be caused by the drivers of the sensors ?
And i found this (last post) http://forum.xda-developers.com/showthread.php?t=1446005&nocache=1
Yes that picture in the last post could be it it could be a motherboard problem like that just be careful if you dont know what your doing
Sent from my GT-I9000 using xda app-developers app
All
I've been having a really annoying issue with my Note 3 and Google Maps: the dot-arrow that shows my position is pointing in the wrong direction. Yes it does track me per the gps location but the issue is that as I am driving instead of the screen moving from up to down, usually along the length-wise direction, it moves at an angle or across. The only option I have is to hit the location button so that I can always have the top be North. That's not as good as having the heading pointing to the location of travel. Now, I calibrated and recalibrated the compass with GPS Status App (turns around the axes and figure eights) which seems to have worked for some, I have restarted numerous times even after turning on/off location-based services. I have cleared the cache and the google maps data. I have reinstalled it. I have even checked the compass versus real settings - seems to be pointing in the right direction. I still have the same issue. This is very frustrating and disorienting when driving. Looks like a crab moving angled to sideways across the screen.
I am on the latest Stock KitKat 4.4.2 version and Maps 7.7.0.
So, does everyone have this issue? Does anyone think is is a unique configuration issue? Is this a google maps issue? Any thoughts on how to fix?
PS...other Map Apps seem work fine (but like to use Google Maps due to the excellent traffic option)
If other apps seem fine, it might be Google maps. I don't have that issue, but I use Google maps version 6.14 (the old style with location arrow). The note 3 is notorious for all of its gps issues, but if you have good signal and it doesn't cut out then all I can think of is that GMaps is the culprit.
Sent from my SAMSUNG-SM-N900A using Tapatalk
I noticed this issue too! I believe it has to do with being inside a vehicle. The metal may be interfering with the gps signal. If I sit in my car and hold my phone so it points north, the arrow points south. If I open the door and step out (while still pointing north) the arrow magically flips! I can fix it by doing figure 8's in the car, but what a pain!!
Well, I do agree it is a google maps issue. I wonder if I can install older version to check. It only recently happened to me. I do not think it is an in-car issue because I never had the issue before when I was navigating in the car. Will come back if I can side load an older version of gmaps.
By the way, this issue is all over the internet but none of the foxes suggested seem to work for me.
No luck in getting it fixed. Did back down to earlier version of 7 but still had the same issue. Driving me nuts.
navfree... can preload maps but just uses google search for most things. some things arent great but its getting better. ive had the same issue with google maps. its been super sporadic. not a deal breaker...
So excited when I started reading this thread, figured someone would have a solution...lol Had this problem ever since my GSII Skyrocket, the gps works great but the direction is always off in my car... Can't understand what the problem is. Done the calibration to no effect... Hopefully someone who knows how to fix will pop in and steer us in the right direction...lol
I'm also waiting for a fix for this..
Ever since 7.0 "update" its been like this. I tried everything but no luck.
I'm using Exynos Note 3.
I was using an HTC EVO 3D when I recieved thr 7.0 update. Before it was fine but after the update even my HTC started doing the arrow pointer bug, and its still happening on my Note 3 even after the yesterdays maps 8.0 update. So I'm thinking this is all Google's fault but nobody is admitting anything.
Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
wilowolf666 said:
Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Any solution that needs to be applied again after a reboot is not a solution at all (nothing against you, just frustrated at no solution).
I have the same issue as the OP, and GPS status app fixed it, but I lose the fix after a reboot. This is unacceptable and I don't think it's just a few of us experiencing this issue.
Could more people post and say whether they have this issue and if not, how they fixed it?
wilowolf666 said:
Hit *#0*# , then select sensor, little black compus will have red line in middle on bottom left of screen. Shake phone vigorously, line will turn green..... This will fix that issue;however, if you reboot phone, you will have to do this again.
Hope this helps someone.
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
The issue seems to be resolved by this. I only have to rotate the phone horizontally a couple of times after a reboot and pointers works just fine.
I broke my screen last week , it fell and was damaged, and the camera stopped working too. I fixed the screen, but the camera is still offline, tried to change the rom, but no changes., i am getting the "Error, camera not available". When i click on camera icon, it shows a black screen after some delay and then right away an error message pops up with "Error! Camera not available". When i load this from any application, such as snapchat or instagram, it crashes the application. Has anyone dealt with such issue before? Give me some hope, what could be wrong.
The camera was not working even before i replaced the screen. (The screen repair was good, i made sure nothing was touched that should'nt be touched.
The phone's proximity sensor seems to be a bit off too, the phone also vibrates ( like it received a text message) randomly.
Unrelated issue: the screen i install has a round ring that appears if i press the screen to hard at a certain spot. it's not too annoying but it is there.
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
electrash said:
Broken flat cable, broken camera. Physical damage.
Sent from my C6903 using XDA Free mobile app
Click to expand...
Click to collapse
Ah! what do you think , can it be saved DIY?
marksee said:
Ah! what do you think , can it be saved DIY?
Click to expand...
Click to collapse
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
electrash said:
Well i didnt opet Z1 before, so i dont know if you can only replace flat cable (if that is problem) or you must replace whole camera module.
Best bet is to give to service center, probably they will put new module on it, and its best in my opinion.
Click to expand...
Click to collapse
Most likely put a new module in there as the modules are machine made are probably solid.
Status Update
So i opened the phone again, and seems like i was able to fix the screen issue.
Issue of camera remains. I removed the camera from the socket, and disconnected its wire from the motherboard. When i accessed camera without wire connected, it straigth away went to "ERROR. Camera not available. Earlier, when wire was connected, it took about 5 seconds and then outputted the Error. Flash/ Front camera are still not accessible or usable even when front camera was plugged out.
Weird vibrations are felt randomly, i am still trying to pinpoint what causes them, but they have decreased significantly.
My question now is, will replacing the camera fix the camera issue? Or is there a deeper wire/motherboard issue here? What would be your next step to investigate it further. Also, can this be not a broken screen issue but a camera issue covered in warrantly?
Additional info: i have tried reinstalling ROM, flashed T-mobile's original ftf file, cleared camera cache, files etc. used 3rd party apps but no success.
#####SOLVED: SCREEN HAS WEIRD FLOATIES WHEN WE TOUCH AREA NEAR THEM
This is caused because of dust between the digitizer and the back of the phone. To fix this, simply open the phone up and remove any dust particles between the digitizer and the phone. Screen will work perfectly after that.
JustPlayingHard said:
Most likely put a new module in there as the modules are machine made are probably solid.
Click to expand...
Click to collapse
When you say module? you mean the camera with the connection wire ? or something more than that?
marksee said:
When you say module? you mean the camera with the connection wire ? or something more than that?
Click to expand...
Click to collapse
The camera with connection wire
Update: so bluetooth call recieving does not work, people call me, and if i pick it up, voice does not work over bluetooth anymore. music skips randomly too. My question was that will camera module replacement fix this? or is this a deeper issue, such as cable that connects the camera module? what will i need to replace .
I don't think that anybody here could answer your questions. You should take your phone tot a service center.
Sent from my C6903 using XDA Premium 4 mobile app
SOLVED it.
Fixed it! The issue was that the back camera module was malfunctioning. Because of that, phone chip that controls camera (also controls vibrations) was not functioning properly. I bought a used camera module from ebay, plugged it in and phone works perfectly now
Feel free to pm me if anyone else has questions about this, or need help dismantling phone. Xperia Z1s I AM BACK!!!
For the life of me I cannot use my N6 no-handed, even for just a moment. The 5-10 seconds I need to hold my phone up between my shoulder and my face to free both hands.......it never fails that I cause an issue with a live phone call. Obviously the larger screen (larger touch-sensitive area) and the screen being on for some reason during the call.......I always either put the phone call on hold, or even put the current call on hold and manage to dial one of my starred contacts. It is driving me up the damn wall. I am not a huge fan of the L phone interface (the starred favorites especially), I much prefer the KK layout.
Anyone else having as hard of a time as me? I'm wondering if the screen being off during the call would cure this. I guess I could manually cut it off when going to no-hands.......but figured it should do it on its own. Anyone care to either give me some suggestions, or even punch me for my ignorance and tell me what I am doing wrong?
Love everything about the phone, and also loving LiquidSmooth.......just hoping the development gets into high gear soon.
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
holeindalip said:
The screen is suppose to be off during calls, that's what the proximity sensor is for. Are you sure you are not hitting the power button while in call, i find it to be sensitive??If its not turning itself off when you put it up to your face, flash back to full stock. Still not working, then its probably a hardware issue???
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
I forgot to reply I had this issue while stock as well. I wasn't looking to 'fix' this issue with a different ROM either, I just like the capabilities and development done in the ROM's themselves. Can't say I didn't hope something would change though.....
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
wilson289 said:
I only experience this with my left hand, LOL. Right handed, no issues with the screen turning off.
Click to expand...
Click to collapse
Well that is certainly odd lol.....
Anyone else? Surely I'm not the only one....... :silly: