Related
hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
I have had this problem before and unfortunately am having it again. Only solution I have ever found for this is a hard reset and then reinstalling all your apps. If you try to restore from a backup from Sprite Backup, for instance, the problem remains. This would lead me to believe that it's a setting or a registry issue somewhere but I haven't been able to locate exactly what would be causing it and don't know enough about programming in WM to write something to figure it out.
Not a great answer but there it is.
db
MegaHz said:
hello,
unfortunately i cannot turn on the bluetooth from comm manager, it turns on and after 1 second is off again.
any solution for this problem?
thanks.
Click to expand...
Click to collapse
Hi, I have a Uk version of the touch cruise and I have the same problem. I just did a hard reset but the problem remains. Turning bluetooth on is impossible. It just try's to turn it on and shuts it off immediately.
Maybe it has something to do with GPRS? I am always connected to the internet. I tried to disconnect but then bluetooth still doesn't work. Can anyone help? Thnx!
No one has a clue?
I had this prob with bluetooth and wifi following the use of wmwifirouter- after hard reset and no wmwifi all goes well...
On a French SFR rom
any other idea?
Same problem... beginning to wish I'd gone all Apple and bought an iPhone. Anyway.... To trun it on, I had to go to Comm Manager>Settings>Bluetooth>Mode>Turn on Bluetooth. That worked despite the Comm Manager still showing Bluetooth as "off".
It only connects 1/2 the time to my headset or handsfree in the car
Otherwise, the phone crashes only once a day! Great! Thanks!
ok, great to see more people having the same problem but i hope that someone has a sollution...
When I try to turn bluetooth on in the communications settings i get a message saying there is a hardware error! :S
Ohw btw, I'm not using any router programs or other and my WIFI works fine.
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
any news on this?
No news, I don't want to try for a different rom because i don't think it will change anything. It just seems like its a faulty device which is a real shame. I've already contacted the place where i bought it and see if i can get a new one.
I also have problems with my microphone during calls, photo camera does often not work and the touchpad reacts very slowly to my touches. Very annoying!!!!
Yup, am returning mine to HTC aswell. Not even sure I want it back. WiFi stopped working too, and then it stopped receiving text messages, and everyone said they couldn't hear me when I called them. Great
Some of you guys got a bad device, there are thousands out there working properly.
If some of you guys flashed a newer Radio, the one form the test-ROM, then this is your problem.
And some of you guys have a quite gay branded ROM (slow responsiveness of touchpad). The original HTC ROM on the FTP and even more so a cooked ROM would solve alot of your problems. But be aware, flashing without having a backup ready is going to void your warranty if you want to exchange it having a custom/non-original ROM on the device.
What's up Schaggo
I am experiencing the same problem these gentlemen are mentioning and my ROM is not gay or lesbian. It is the original one.
TC is my 7th HTC device and I can see the quality of the ROMs decreasing a lot on every new device. I feel like HTC needs a real competitor to move up its arse quicker.
All I can say is that it really annoys me to hard reset this [email protected] everytime I "accidentally" use a native feature called Flight Mode. By bluetooth seems to fly away and never get back.
Lots of time the GPRS settings have to be reconfigured too. Some people I know have problems with GMail IMAP4 accounts when sending messages after some time. I never had this problem on my Kaiser neither on my Niki.
The lack of a video driver really is an egg on our faces, because I can't believe my ole Qtek 9100 responds quicker than these "all the bells and whistles" Qualcomm 7200 super-duper geared up devices.
So, if you feel like not contributing, please do not mess around.
Your signature tells me you are a wise man, but your comments show me otherway.
-Feaps
PB of BT still there with custom rom
MegaHz said:
has anybody of you having this problem tried to change to another rom?
if yes? did this worked?
Click to expand...
Click to collapse
Hi
I've tried many custom rom and the PB continue. "PB with the hardware oh BT".
Hard reset doent change anything.
my initial rom (SFR France) was working
custom rom (blackwidow + Bepe 058) are buging...
nedd some help !
Thanks alot for that input feaps. I guess I have to clarify a little bit.
My answer was supposed to be pointing in different directions. The first and general information I tried to contribute was, that it is not a common Polaris problem to have a broken Bluetooth unit. Which doesn't help at all to ppl affected, but it should tell them, that they probably got a bad device and should exchange it first before blameing htc in general and shouting for an iPhone.
It only was partially directed at specific persons. At madinga for example: did you try hardresetting your device? It could be a corruption in your system which causes all those problems. I doubt it though, if you suffer the loss of so many functions at the same time I suspect the mainboard to be broken. But nonetheless, hardreset it, see if its working, BEFORE you put your backup back on the device again since that could restore the corruption. If it doesnt work, exchange your unit, I hope you'll get a working one back.
My second line was directed at all people which have overwritten their original Radio with the 1.58.25.14 originating from the HTC Test ROM which can be found on the ftp server. The Bluetooth part of that Radio is flawed and leads to the problems described in this thread. I quite nicely pointed that out and told people where to have a look before shouting around. I do know that because I tried it myself and couldnt get my Bluetooth devices working. Once I flashed the original Radio back, my BT problems were gone.
And my third line - in which I may chose the wrong words, 'gay' for example - holds information targeted at people with for example the branded french SFR ROM or the original HTC french ROM. The SFR ROM is just horribly branded and if you go through the threads here you'll find people complaining about problems which then turn out to be related to the ROM. The french HTC ROM is flawed as well, it has severe problems with the volume control. I don't exactly remember what it was, but it's a flawed ROM, thats for sure. The German o2 ROM isnt flawless either, I know that because I originally had that ROM. Once I flashed my orbit 2 with the original HTC WWE ROM, I found it to be working alot better and smoother than with the o2 ROM originally provided. And this is where my last line comes into play: if you suffer problems related to your currently flashed ROM, they could be diminished by flashing an alternative ROM. But if your device is broken, and I personally and strongly believe that everybody fooling around in this forum should be intelligent enough and able to determine the sense of my words, eg. if he/she suffers a ROM problem or if the device just simply is dead and take appropriate actions.
And now to your contribution feaps. I feel personally attacked by your words. Thats why I defended my words in all the paragraphs above. Trust me, I've had enough mobile devices of all sorts to know what it means to get a not working once. Its frustrating and makes you want to throw it out of the window. And being able to see the quality decrease over time is just another drop on a hot stone. I agree. But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think? As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices. And recommending to flash the original HTC ROM, which should be/is the base for everything floating around, breaking your devices, is a serious input to everybody.
Edit: I forgot to add, pointed at nooms, there are cooked ROMs out there which stupidly have the new, flawed Radio baked in. Which Radio are you on? Try Start > Settings > Tab System > Device Information > Tab Version. Are you inadvertedly still on Radio 1.58.25.14 or back to (original) 1.58.21.23?
Hi everyone,
I agree with Schaggo completely. Most of the time problems have something to do with the software on the device. But I a not a tweaker like most of you guys, i've just bought my first (and hopefully not last) HTC phone. If i have problems of some kind, all i can do is reset the thing. A hard reset if necessary. I've done that many times. I can't change the software that comes standard and i don't think i should be the one who has to do that. Shouldnt HTC be doing that??
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
You're right
schaggo said:
(...)
My answer was supposed to be pointing in different directions.
(...)
And now to your contribution feaps. I feel personally attacked by your words.
(...)
But be honest, if your BT unit works and stopps working once you engage a software based function, the problem is software related, dont you think?
(...)
As for the GPRS settings, I cant tell. Since I use a free ROM which has the wizard built in (o2 removed it from their ROM) I didnt switch my SIM and the configuration worked, automatically and every single time. And I do use IMAP as well on my personal E-Mail account. Until now I didnt run across any problems, so I cant give you any feedback on that either.
(...)
So rethink again if I mess around or not or if I actually try to contribute and help the freshmen, coming into this forum and flashing whatever they find and breaking their devices.
Click to expand...
Click to collapse
Well put. Sorry for being rude, but I keep seeing people offending others day after day in this forum that used to be high level; but that doesn't mean I should act the same way.
I totally misread you and please accept my apologies.
My ROM is: 1.25.405.1 WWE
ROM Date: 12/11/07
Radio Version: 1.58.21.23
Protocol Version: 25.65.30.04H
One thing I could notice is that HTC has a flaw in the Flush HKCU to Permanent Memory While Shutting Down. Some keys are not written.
One example is the MagiCall (an app I use) registration key. The software maker had to write a flush app for doing that. Another example is the Start>Settings>System>Error reporting. No matter what you chose, after a power cycle or a soft reset, it always go back to "Disable...".
I have, also, already tested the device after the hard reset with no extra apps on it. Same lame behavior on BT...
So, SW QA levels are really dropping fast on new HTC models. That is pretty bad.
But anyway, I have an open case with HTC and if I find something contributive I will toch base with this thread.
Once again, sorry for being rude.
Best,
-Feaps
Furio83 said:
Anyway, Bluetooth keeps saying it has an hardware error. My radio version is a standard 1.58.21.23 but isnt finding any radiostations here in holland. Is it also broken? (sorry, i know, its a bit off topic)
Click to expand...
Click to collapse
Then I guess you most probably got a bad unit. I guess the only solution at this time is an exchange.
The Radio-Firmware doesnt control the FM Radio btw The Radio-Firmware controls connections to the providers network, Wireless LAN and Bluetooth. But the FM Radio seems to be really bad in the Polaris, a lot of ppl I know complain about it.
feaps said:
please accept my apologies.
Click to expand...
Click to collapse
No problem dude! There is no need for such an excessive appology. We are in a Forum and people have different oppinions and I think its totally acceptable to shout at each other. I just wanted to express that I'm not in accord regarding your judgement of my post. But thanks a lot, I seriously really appreciate it!
Yes, your device seems pretty standard to me and the scenario you described logically made me think of a software error. But this seems very unlikely now. I'm out of ideas for the moment then, I guess you have to return or exchange it too.
You are perfectly right about the dropping SW QA though. You can notice the registry glitch in other areas as well: backlight timer always reset to 30 sec, and there are more settings all over the place which don't get saved properly.
Again, no problem, everybody lets be cool
Bluetooth doesn't turn on
I have the same problem. Did anyone find a solution?
Also camera fails to initialize, touch pad is sometimes very slow for initial reaction. I have NO added programs beyond manafacturer originals and have tried a number of hard resets. Doesn't help.
Jeremy
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
crunchybutternut said:
I have been using YouMail's service on my phones for quite some time and was excited to see there was an app for Android, but after 2+ months of use (and several versions of the .apk, including the most recent Beta) I am still experiencing 100% awake time when the app is running.
If I kill it my phone will immedietly because to sleep normally. But each time I receive a phone call or open the app it will keep the phone from sleeping again.
I have been in contact with their support (which is how I received the Beta version) and have been sending Dumps their way, but was wondering if anyone else is experiencing this issue.
Info: Running Fresh 1.1 on a newly 1.56 RUU'ed hero.
Click to expand...
Click to collapse
I stopped using the app because of this. I tried contacting support and was brushed off. I love the app but not the lack letting my phone sleep.
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
crunchybutternut said:
I am working with a developer of the app to fix the problem and have tested several versions. Will keep you updated of the progress.
Click to expand...
Click to collapse
That would be great. Thanks for helping him out with this as I would love to use the app.
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Kcarpenter said:
I don't mean to thread jack this, but.
Whats the difference in YouMail and our Sprint Visual Voice Mail? I have never used youMail.
Click to expand...
Click to collapse
YouMail http://www.youmail.com/home/index.do is a service that replaces Sprint's (or any other provider) voice mail service with their own. It allows you to set custom "smart" greetings for each caller in your contacts, among other things. Check out the site for more info.
Here is the latest response from the developer I have been working with.
Hi [Name],
I did some more research and can confirm that I see the same behavior as you when I run the YouMail app ('active' @ 100%)
I'm not exactly sure what the cause is, as the application is indeed going to sleep when it has nothing to do. The problem also seems to be quite widespread, affecting what seems to be "most" applications that loiter around in the background doing nothing for most of the time.
Since you use 'Spare Parts' you should notice that in there is a way of viewing the 'Partial Wake Lock' usage of a given application. According to the Android developer documentation this is the ONLY way an application can keep the phone "awake" other than 'prodding' it every 30 seconds or so (and you'd notice that 'coz the screen would never go off).
As long as that "Partial Wake Lock" value is low (and it should be unless you're constantly hitting "Menu -> Poll") it means the application is indeed behaving correctly.
All I can offer is that we develop a new feature into the app so that you can tell it to automatically exit when all of the automatic polling settings are disabled - that way the phone would literally shut down the app "sometime" after you back out of the message list. Do you think that's worth it? Or should we wait for HTC/T-Mobile to fix the root cause of the problem?
Doug
Click to expand...
Click to collapse
And my response:
Do you mind if I share some of our conversation with a community forum? It might help get others involved and more feedback for you to use in further development.
As far as other apps loitering in the background, my understanding is that Android (using the same process as other Linux distros) keeps recently used applications in RAM to make them more quickly accessible to the user, and will clear them as the RAM is needed by other apps.
I have seen this issue in the past with other apps (i.e. the HTC messaging app locking the dialer and maintaining 100% awake time) but has all been resolved by updates to the apps themselves.
Click to expand...
Click to collapse
Lastly, his response:
Feel free, I don't think I said anything bad
I we get enough requests from "the community" I'll be given time to add the 'exit when done' option (basically it'll become a "dumb" app that only checks for messages when you start it up instead of waking up every so often to check [like after you miss a call])
And yes, Android is a little stranger than normal in that it tends to leave applications running for an unspecified time after you "close" them. (basically until it needs to run something else, or it runs out of memory, or .....)
The YouMail app is a little different in that it runs as a background service and schedules the phone to wake it up whenever "events of interest" occur (you get a TXT, your phone rings, it needs to poll, etc) - so even if the OS does close the app because you logged onto "hugebitmaps.com" and the phone ran out of memory, it'll start it up again as soon as it can.
I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something
Doug
Click to expand...
Click to collapse
I can post more of the conversation history if it would help. Anyone have any ideas what might be causing this beyond coding issues?
If anyone wants to send their YouMail log for inspection just enter this code in the dialer *#*#963867#*#* (*#*#YMDUMP#*#*) and it will let you send an email with the log's text.
Tried in 2.1 beta
"I suspect the HERO OS is not allowing the phone to sleep, even though the application is literally doing nothing. I don't recall this problem on my trusty G1 when it had Android 1.5, so maybe some of HTC's customizations have broken something "
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Hi, Doug from YouMail here.
Just noticed my words and thought I'd give an update - although not much good news.
I basically spent the last 2 days completely reworking the YouMail app's back end code so that anything and everything that could possibly be shut down when it isn't actually doing anything is indeed shut down.
When it came time to test it out -- 100% awake time again (although I stand by my earlier comments that "its not just us").
If I run the same app on a HTC G1 the phone will last a good 2 days (maybe more) without battery issues. If I uninstall the app the difference is minor.
This information, added to all the discussion on the Sprint forums about how the HTC "extras" that this phone comes bundled with have caused the same problem leads me to think that there is something in the Hero that's not behaving properly.
I see other comments like "It does the same on my <insert phone model here>" - well, we don't have unlimited resources, so if you can put the small amount of effort in to dial the 'dump' code mentioned above (*#*#963867#*#*) then maybe we can start to find a pattern here (maybe it's all the Android 1.5 based devices for example).
I'd also like to thank crunchybutternut for all of his assistance and time in trying to sort this issue out.
Doug
superman.namrepus said:
I also tried using this app on the 2.1 ROM that Flipz and company have been working on, and had the same issue. I do not know enough programing to determine if this is a problem with OS or the app. I can only give you my experience and try other stuff out to see what the results are. I hope this helps.
Kevin
Click to expand...
Click to collapse
If I can get in touch with someone who has access to the "guts" of the device and that can help me determine whats going wrong then that would be great. Neither the Android developer list nor the HTC forums are particularly helpful when it comes to tricky problems.
Bump
Anyone have some insight on this?
Ok - If someone working on one of these custom builds is prepared to lend a little assistance I'm willing to put a custom build on my phone and try to debug this a little deeper. However, with the number of hours that I get to work on this app.... and all the "fun" blocks that Google have been putting in our way w.r.t Android 2.x, I may not get much more time to work this problem.
That being said, I'm going to try experimenting with a new test app that just adds (one at a time) the raw features of the YouMail app in the hope that a single change triggers this wonderful problem you guys have. If that's the case then I'll put on my Sherlock Holmes hat and try to work around whatever is causing it.
Doug
Any news ?
soundmind said:
Any news ?
Click to expand...
Click to collapse
Got this from ymDoug:
No progress as yet - not seen anything from xda folks either.
I've made *massive* changes to ensure the app is shutting down absolutely everything it can when it has nothing to do - still no joy.
I've even gone through a lot of the Android source code and can't find anything that would indicate I'm doing anything wrong. There is one debugging method I'd dearly love to call inside the Google Android code (it dumps out a list of who is keeping the phone awake at any point in time) but the method is only accessible to (a) Google, and (b) People who cook their own ROMs. The official Android people are doing their usual stand-up job of ignoring the difficult questions
I am still making the odd change here and there, and my test app doesn't seem to be having the same problems (of course)
Regardless, there will be an updated version on the web site in the next day or so - I'll need to ensure my changes haven't completely screwed things up
Click to expand...
Click to collapse
Doug has made some changes, does not seem to completely resolve the sleep issue though.
Here's the link to the change log:
http://forums.youmail.com/forums/viewtopic.php?f=12&t=18
Click to expand...
Click to collapse
FYI: The version in the market is several revisions behind.
Hello, i need some serious help over here
What's the problem:
I own a galaxy 3 since June, a week ago i started noticing the internal mic wasn't working on some incoming calls.
Details:
First of all the problem began for no apparent reason (the phone works fine otherwise and no major updates / new apps were installed)
This started happening on the official froyo ROM which was an excuse for me to flash the Kyrillos 9.4 ROM (wiped all data / formatted sd card in the process). The problem still occurs on Kyrillos 9.4 ROM suggesting that this is not a ROM issue
I thought it was a hardware issue but the caller can hear me perfectly if i connect the headset or use the speaker Also the internal mic works fine on some incoming calls and ALL outgoing ones!
Upon further investigation i came upon 2 threads on other forums (unfortunately i can't post the urls as i am a new user, if needed pm me or search google for "Microphone not working on incoming calls") which point out that the same problem incurs on HTCs and XPERIAs. Also it happens on replacement phones (original unit shipped back after this problem), on different providers, on official and custom ROMs, on clean phones (only the stock apps installed).
This seems to happen when the phone is idle for a set period of time (unconfirmed). Fast Reboot app / manual reboot / removing battery don't fix this, however making an outgoing call seems to enable the internal mic temporarily (even if the outgoing call never connects)
When this happens apart from the mic not working on incoming calls it becomes also unresponsive for other apps (Tape-a-Talk, Skype, Soundhound etc.)
Conclusion:
It seems to me that there is bug in froyo that keeps the incoming call code from activating the microphone or perhaps there is a conflict of sorts that keeps the microphone blocked. It is highly unprobable i think that the microphone would randomly start to fail on different android phones in the exact same way, so this shouldn't be a hardware issue.
Question:
Does anyone know/guess or can produce a possible solution for this? If not, could you please suggest further testing steps to help reproduce 100% this problem in an attempt to solve it?
Any help would be greatly appreciated as this is a pain in the neck for me (and others i guess?!)
PS: Excuse the thread form, i 'm really bored of writing / reading long posts
PS 2: This is my first post, hello xda community!
samsung vibrant
I have the same problem. I flashed the phone from android 2.1 TO cyanogen 2.3 and from it TO ice cream. I had this problem even to cyanogen and only in incoming call,never in other situation.
Googling I found same information but no solution. Anyone here knows something?
Anyway I found a stupid solution....try switching to 2g( I know that it's not a solution but...). It works for me!
that's ridiculous! how can network state have anything to do with the microphone of the device? can this be related to service providers maybe a more techish member could tell us.
anyway i am on 2g already as i don't have a usim card and this happens even if data network mode is deactivated. glad you found a way out but is it really a solution? i mean you have to ditch 3g for the phone to be actually a phone...
Since we seem to be the only ones among so many to be having this problem i am seriously thinking of taking back the phone for a replacement and hope for the best...
just an update, i lost functionallity of the microphone completely earlier today. That is with outgoing / incoming calls and any app i can think of, so i thought i 'd try changing the network data setting to 3g only since i was already on 2g...
WOW!!! that had an instant effect,it works seamlessly now,didn't even have to reboot.fingers crossed it will last.
that is one nasty and very strange bug. Please any of the developers could you take a closer look at this?
much appreciated
Sent from my GT-I5800 using XDA App
Hello,
Did Samsung ever fix the low level volume fluctuation problem through the headphone connection on the 7.0+? Listening to lower level music files at lower volumes resulted in the volume jumping up and down slightly. The problem occurs regardless of whatever music player app is used. The files play fine on the Samsung Galaxy 5.0 player and other devices.
Thanks!
Update: It's not fixed.
This thread is the only reference I could find to this issue anywhere. Is it documented more fully somewhere else? Is Samsung aware of it and planning to fix it? Any references or other help would be greatly appreciated.
I've had my 7.0 Plus for about a week, and yesterday was the first time I tried listening to some classical music favorites featuring very soft choral passages. I couldn't. The volume surges every couple of seconds during soft passages. It sounds as if some demented engineer thought it would be a good idea to add an automatic volume equalizer to make sure the music never gets too soft. No. Very bad idea.
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Sun_Cat said:
Until I found this thread, I thought I had a defective device or was losing my hearing. I'm glad that neither is the case. Again, please post links to further info about the issue. TIA.
Click to expand...
Click to collapse
I've had the same problem with 6210 from day one. Other than album art being screwed up, it's the only real annoying problem I've had with the box.
The problem may be in the default player. I use poweramp and don't experience that
Sent from my DROID BIONIC using XDA
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Sun_Cat said:
It's not just the default player. I've experienced it in the Rhapsody app too. Also see the OP, which says regardless of app and also strongly imples that the issue has been discussed before.
Click to expand...
Click to collapse
I hear it using TuneIn Radio. Hoping for a fix with ICS.
UPDATE
I've found two earlier references to the issue:
A review on Amazon from last November (reviewer says he's notified Samsung)
A post by this thread's OP, also from November (like me, he thought it sounded like Automatic Gain Control; unlike me, he remembered the right name for that feature )
Again, any more references, especially from Samsung, would be appreciated.
ETA: I found one on the Samsung support page (search for the string "How can I stop the volume" and click on the text to open the answer). It was answered, not by Samsung but by an anonymous user, who said "Sorry charlie, but you've got a headphone jack with a malfunctioning sensor. Sorry!"
I suppose that's a plausible explanation, but against it is the Amazon reviewer, who said he had the same problem with two different units. And then there's me and the OP here.
redsmear said:
The problem may be in the default player. I use poweramp and don't experience that
Click to expand...
Click to collapse
I installed Poweramp. Nice app, but it doesn't help with this problem at all.
To hear the problem you have to be playing music with sustained passages that are very soft. With most pop, rock, and jazz it won't be noticeable. That's probably why the issue isn't more widely reported.
Try this video in your YouTube app. If your Tab Plus is behaving like mine, you'll hear several volume surges during the first 20 seconds or so. ETA: Crap! I can't post outside links. Here's the last part of the YouTube URL, after the slash: watch?v=6-i1ESIRKdA.
One more clue
And I found one more indirect clue in the Samsung Troubleshooting Guide under the heading GT-P6210 Volume Drops When Headphones Are Plugged In:
The volume on your Tablet will drop 75% when you plug in your headphones. This is a preventive measure for acoustic shock to your ears. The volume can be increased after the headphones are connected.
Click to expand...
Click to collapse
Obviously this proves nothing about the issue we're discussing, but it is suggestive because it tells us that something in the firmware is deliberately designed to mess with the headphone volume.
Aha, so it's not just me who noticed this "feature" then
For anyone who is experiencing this issue and wants to let Samsung know about it in one place, I've started a public thread on their Facebook support wall. You'll have to imagine the first part of the usual Facebook URL since I can't post links. Here's the last part, after the slash: samsungsupport/posts/10150588609036213
Nothing from Samsung Support on Facebook since yesterday morning. One other person has posted there (thanks, Mark, if you're reading this). It would be nice if a few others would chime in.
I'll chime back in. I'm glad somebody else has finally noticed! The problem also exists with the Verizon SCH-i810 (Tab 7.7) but, perhaps, to a lesser degree.
I strongly suspect the (Yamaha?) driver and/or its configuration -- see the original post from November that shows the (configuration?) files. I suspect that file may hold the key to the problem. Problem is, I have no idea what the numbers actually mean and didn't find any documentation for those numbers (data sheets, etc.). I did attempt at the time to tweak a few numbers using my "best guess" by comparing the entries for rx-speaker vs. rx-headphone vs. rx-headset. but no discernible effect was heard.
No prizes for guessing who was raising such a fuss in November.
The "Sorry Charlie" answer is incorrect and I flagged it as such.
UPDATE: I found the 7.0+ /etc/audio files and I have the 7.7 /etc/audio files. There are some differences in the numbers and the 7.7 audio files (LVVEFS) have some comments (!!!) in them so maybe I can track down pertinent parameters.
Anyone else have an opinion or another idea? Is this a waste of time?
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Sun_Cat said:
Thanks again to everyone who posted here. If you've been watching the Samsung wall on Facebook where I posted last week you've noticed that they haven't responded at all except to ask one simple question, which I answered immediately. Since then, crickets.
If you're experiencing this issue and you feel comfortable saying so in public, please add your comment to the post on Facebook. Maybe we can guilt them into responding.
Thanks.
Click to expand...
Click to collapse
They just answered about 1/2 an hour ago. They provide a link and ask us to go to the Samsung Service Facebook page and fill out a support form. Might as well. Keep the pressure up on someone over there.
Agreed. I just submitted their form with full details. We'll see whether they follow through.
A hint to anyone posting there: Samsung appears to be great at stalling by asking follow-up questions. Include as many pertinent details as possible in the initial post, such as model, wi-fi or data-enabled, serial number, firmware, streaming or stored music sources, which apps, etc., etc., and so forth.
Well, at least they're responding, but I'm not sure it's helping. This morning they replied to my original Facebook post:
We can suggest checking to see if the same problem occurs in a different set of headphones or speakers. If the problem persists we will suggest servicing your Tab.
Click to expand...
Click to collapse
I've already checked with different headphones (not speakers; I've already told them several times that it's a headphones-only issue!), so I already know that the problem isn't due to one set of headphones.
This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.) I'm reluctant to send it in for service. The problem is subtle enough that someone lacking a trained musician's ear is likely to just say it's fixed and send it back. We already know that the fellow who mentioned this issue in his Amazon review got a second unit exhibiting the same defect.
Also, I have not heard from Samsung directly in response to submitting the official support form the other day, so I can't now tell whether or not this latest comment on the wall is coordinated with that other support request.
Does anyone have any advice? Has anyone here dealt successfully with Samsung support in the past, on any issue at all? How did you do it?
Sun_Cat said:
...This gives me zero confidence that they actually understand the issue. (Except that it's possible -- though in my view unlikely -- that it is a defective headphone jack.)
Click to expand...
Click to collapse
I agree. I don't believe it's a headphone jack issue either. I'm going to wait until ICS comes out and then decide what to do if it's still an issue.
I've tried adjusting some numbers in the .txt files -- no change yet. Maybe I'm adjusting the wrong file. Who knows?
I'm surprised there aren't more complaints. It's easy to identify. Headphones, earphones -- doesn't matter. The problem exists with Samsung's earphones. They can't run away from that one. Doesn't the 7.0+ come with four audio files? I can't recall if the problem could be reproduced with those files, because the problem needs periods of relative silence to get into the "AGC" mode. I think the Samsung support is in typical "denial mode". Problem? What problem? Let's go through all the permutations of user error or workaround before considering that there is a problem. It's a matter of problem ownership -- and Samsung isn't owning it.
The questions I would ask are: "Have you tried reproducing the problem?" "Do you know how to reproduce the problem?" "Who has the capability to reproduce the problem, if you can't".
Yes! Just found the Samsung music files, going to try to reproduce with all Samsung supplied software and equipment.
UPDATE: Reproduced the problem on Galaxy Tab 7.7 with all Samsung supplied files/software/equipment:
MATERIAL:
1. Samsung supplied "Music Player", no EQ
2. Samsung supplied music file "Silky whisper.mp3"
3. Samsung supplied earphones, white with button and mic (I think it's pretty generic to Samsung)
Steps:
1. Start Music Player.
2. Make certain volume is all the way down and the sound is muted (slash through speaker)
3. Press the volume up button once, twice (once to unmute and one step higher)
4. Play music file. Note how the piano cuts in and out throughout the song, especially during the opening of the instrumental.
I suspect that Samsung is going to hand this issue off to Yamaha. The constant in this matter is the Yamaha-sourced audio chip/driver/library/configuration/firmware.
Here are some files to compare from /etc/audio (I added the model to the name):
TonyBigs said:
It's a matter of problem ownership -- and Samsung isn't owning it.
Click to expand...
Click to collapse
Agreed. That's why my first question to them on Facebook was "Are you aware of the problem?" No way will I send my GT7+ to them for service until they take that step.
I'll try your steps later today and see if I get the same result. Maybe we can gang up on them.
I have one additional datum since last week. I've tried to reproduce it on Bluetooth headphones, and the problem does not show up. It's only there with plugged-in headphones.
I suppose this could be interpreted as evidence slightly inclining toward the "defective headphone jack" theory. But I still don't think so. If anything, I think it could be related to the Self Aware Volume Ghost on the Galaxy Nexus, which Samsung apparently did acknowledge. Except the Nexus bug was much more obvious since the volume control indicator actually appeared on the screen and changed.
I am starting this thread to be a place for Terrain owners to come for the latest info on how to root and flash their phones. The Terrain is one of the best "rugged" phones on the market, but it has been abandoned by it's manufacturer, leaving owners to find their own solutions to problems and upgrades. This is actually a good thing price wise as you can now buy a brand new Terrain for less then $85. The Terrain has about as of hardware specs as any other ruggedized smartphone on the market currently, but at one third or a 1/4 of the cost. This makes this phone a huge attraction to anyone who is looking for a rugged waterproof phone on a budget and is why this guide is essential for users.
The NEC Terrain still has plenty of life left and this is why we need to come together and find solutions for it. Please feel free to post you success stories in rooting and flashing your terrain to this thread for the benefit of all. Hopefully, will be able to form a complete guide from all the information that get's posted here.
Thanks.
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
gamerka said:
Hi!
I myself just today recieved this phone, and it would be great at least to debloat it.
Previous threads on XDA, just for reference:
NEC Terrain: ADB/CDC Serial Driver, 3e Recovery Password, and Root
[Q] Rooting NEC Terrain
[Q] Unlocking of NEC Terrain SIM/Root
Click to expand...
Click to collapse
Thanks for the post and the links. It appreas that much of the information on these links are still a work in progress. Hopefully this work will continue and we can create a How To guide from this.
For those that may be interested. You can buy the NEC Terrain Unlock on Amazon for $79.99. Here is the link.
http://www.amazon.com/NEC-Terrain-UNLOCKED-WaterProof-DustProof/dp/B00KZPI04S/ref=sr_1_1?s=wireless&ie=UTF8&qid=1405614968&sr=1-1&keywords=nec+terrain
For full specs on this great phone you can go here.
http://www.gsmarena.com/nec_terrain-5553.php
Well, I almost bricked it few days ago. :good:
I read a thread about a patch to unlock GSM in CDMA phones and saw there a code to enter some hidden menu. I entered that menu and messed a little with band settings (wanted to get LTE to work with my operator). Next thing I know Terrain stopped receiving any GSM signal and for next hour I tried to fix it. Factory reset got me 2G signal and that's all.
It turned out that the only way to fully fix it is to re-flash firmware or radio module and as we know that can't be done.
Well, this is not about unlocking or flashing, but it is a solution to another problem I and many other have been having with the predictive text bar blocking critical function keys from being accessed. The predictive txt bar is a function of the Adaptxt keyboard app and disabling it does remove that bar, but the keyboard also loses all special character function, upper case letters and numbers. After trying more then a dozen keyboard apps to replace adaptxt, I found one that works and brings back all keyboard functions without the stupid predictive text bar. It is called TouchPal.
https://play.google.com/store/apps/details?id=com.cootek.smartinputv5&hl=en
Forgive me for this slight OT-posting, but it's not that easy to find people with this device - let alone an unlocked one. I'm located in Germany and the device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI. The PC can connect to the phone, however the connection in Windows 7 always is shown as being limited (no internet access), while internet on the phone works fine.
GMail - as well as some other functions of google also rarely sync and basically just do so on request, while they sync just fine when being connected to Wifi. And no, background data are not restricted in the settings.
Has anyone experienced something similar?
laserdrome said:
device runs just fine - except for the fact that Tethering does not work - neither USB nor WIFI.
Click to expand...
Click to collapse
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
iDomino said:
I have the same problem! After few minutes of "thinking" phone reports "There is a temporary nework problem... bla, bla, bla"
Is there any suggestions how to fix it?
Click to expand...
Click to collapse
Well actually I know that message as well. For me changing the APN helped. You could also try to restart the phone. I just remember I also had this problem sometimes. But like I said - even without that particular message I would not get tethering to work.
iDomino: Do you also experience the problem with syncing that I had?
That's funny, actually I haven't noticed syncing problems untill I read your posts. I myself have all the same problems that you mention.
Even more of that, Terrain has some silly feature that TURNS OFF WI-FI if it thinks that that hotspot has no internet connection. It is massively annoying and can drain all your data traffic. The only solution that I found is to install the app "Smart Wi-Fi Toggler", it constantly turns wi-fi on if terrain turns it off, but only in places where I turned wi-fi on myself (like home and work).
It's a pity the phone has so many flaws and due to its tight security and the locked down NEC mobile devision no one can do anything about it. I wonder if this just affects the users who use an unlocked phone outside the US or if people in the US have similar problems. I have tried contacting NEC about this - actually about providing us with some kind of unlock mechanism - but all I got was this:
"Dear Sir,
Thank you for inquiry.
We, however, regret to inform you that our phone is not available about your request.
If you have any issue, would you try to contact the company or shop where you have purchased this model, who might be of help to you.
Thanks and Best Regards,
Fujii /NEC"
By the way, I discovered a new bug: When Roaming the actually used Network-Provider is not shown and I also didn't find a way to choose one...
Do you also experience the problem with syncing that I had?
Click to expand...
Click to collapse
I had some sync problems and I don't know working methods to fix it.
First time I solved it this way:
turning off apps sync -> open Gmail app -> it will show notification offering to enable synchronization -> use it -> sync works.
But this solution worked just once. (
Other time sync turns on by itself after one day disabled.
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Battery life
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
iDomino said:
P.S. My Nec reboots while connecting via USB to ubuntu laptop.
Click to expand...
Click to collapse
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
FFDA said:
Can someone tell me how your Terrains battery hold up charge? Because mine discharges completely in about 10 hours (without using phone at all). I think it's wakelock problem.
Does it crashes once or infinite loop begins? I had infinite loop problem while connecting NEC Terrain to Ubuntu, Linux Mint, Debian or CentOS. Removing "ModemManager" package solved it.
Click to expand...
Click to collapse
My phone works about 25-30 hours (30 min. calls, 5-10 sms, 30 min. messaging, 2 hours e-mail, internet & other applications. No video/gaming/music at all).
Infinite loop. Removing "modemmanager" helps! Thank you! :laugh:
Also got spontaneous rebooting after installing FTP Client made by Zifero. :silly: Removing app solved the problem.
Dreaming about root and working wi-fi tethering.
Who have usb driver of nec terrain? I need it, thanks
zolahn said:
Who have usb driver of nec terrain? I need it, thanks
Click to expand...
Click to collapse
Maybe this topic will help.
Cpu-z shows only 665MB RAM on device... Where are another 335MB???
Lets continue discussion in one thread!
http://forum.xda-developers.com/showthread.php?p=59514154#post59514154
I created a GitHub repo to collect information, also on how to disable apps (since thats as good as it gets for now).
Another Terrain user here!
Hi guys!
i am Kharl
i am another Nec Terrain user here!
due my lifestyle, i needed a phone which could gives me reliability and power under ANY circunstance, that could be done by any rugged phone, BUT i needed querty keyboard, fm radio, gps, gyroscope, accelerometer, loud speakers, that could work worldwide and touchscreen... the only one with those features was the Terrain... and with the extra, that it is amazingly cool, i dont know opther but i find this phone really cute, very sober and elegant design.
well, i live outside USA so, for me, to work it couldnt be locked to ATT, so i was able to get one unlocked.
my phone has almost all the problems you mentioned, althught i am still happy with it and i am not going to change it because its problems does nto interfere a lot with me, BUT of course id like to get those problems sovled.
trying to solve the problem i bough three of thes phones and all the three had the same problems
the first one was by mistake, locked to att, but it had the same problems, random restart and locked hotspot, i sold it, i got a second one, works with any sim, everything fines, but with the same problem, random restart and no hotspot, i bought a third one to see if the problem was with my particular phone... and n luck the same problems.
it has some other minors problems, like no stereo audio recording despite it has two mics and IT STATES IT CAN record in stereo, but thats not a problem, i can deal with that, and sometimes the people at the other side (while in a call) says my voice sounds like from within a box (lack of trebble or too much bass) and when i press the check too much to the phone boddy there is also clarity sound problem.... but thats ok....
regarding the two main problems
random reboot and hotspot
many of us suspect what the cause is
for the random reboot many could think it is a installe app which is causing it... NO, because it does it at factory state, to solve that i dotn think root is needed, there is a certain factory process that is causin to reboot, the reboot is VERY random, could doit threee times in a day or could happen only three times in a week, what i have notice is that it happe lessoften in cold weather.
the hotspot problem IT IS cause because att locked that function, even when the phone is ulocked, that part remain locked because ATT.
what about you guys?
u can try hard reset for begging