Related
I wonder if I have found a reason why GPS was not offered in the past year..
Since playing with the new radio and OS ROMs, the internal GPS on my phone has been consistently flawless. Indoor (wood frame house) and outdoor 5~30s lock ons to 3-8 satellites out of a visible 10.
A few weeks ago I got my dad the same Telus phone and this evening moved it also to the latest radio and DCD's 2.2.1. BUT, it can only perceive a maximum of 7 satellites and retain a much weaker and extremely intermittent lock to 1-3 satellites. When first activated with visualGPS, the signal strength and satellite recognition seems to be stronger for the first 5-10 seconds but then quickly drops off to rather poor levels. If the app is shut-down, I wait ~15 seconds and restart it then it returns with the same weakening performance model. This is all the while with my phone (identical ROMs) is close by but providing exceptional reception.
In the other thread concerning GPS performance there are some people complaining about the apparent "worthlessness" of the internal GPS. Possibly they aren't doing anything wrong but lost out on a crapshoot for a GPS viable Titan.
Checking in the EPST (reliable and significant? I'm still learning..), the hardware version of my phone is 0003 and the PRI Version (?) 1.15_010. In the next few days I'll head back to my Dad's to see if his phone states anything different.
GPS is working great on my Telus P4000 with the 2.2.3 ROM. Little jumpy in steel-and-concrete buildings and among the downtown buildings, but it's got a lock everywhere I've tried it.
Soundy106 said:
GPS is working great on my Telus P4000 with the 2.2.3 ROM. Little jumpy in steel-and-concrete buildings and among the downtown buildings, but it's got a lock everywhere I've tried it.
Click to expand...
Click to collapse
Yes, most seem to work well. But I think this is the first opportunity to test one of the phones with apparent weak GPS issues side-by-side with another that's working fine and has an identical (sprite backup image) software configuration.
After the ROM update, as mine, my dad's phone was updated on the Telus network via *228032. It was also left outside for 30 minutes to see if it could better survey and lock on to the satellites. I can't think of any software or settings discrepancies between the two that could cause such a difference in performance.
Tomorrow or Wednesday I'll again try out quickGPS and check if his EPST states any different hardware revision.
It's appears to be definite that my dad's Titan is subpar compared to mine with the internal GPS. It's EPST hardware revisons are identical to mine, so there is no visible difference between the phone.
I just again tried quickGPS with no difference in reception.
Keystone said:
It's appears to be definite that my dad's Titan is subpar compared to mine with the internal GPS. It's EPST hardware revisons are identical to mine, so there is no visible difference between the phone.
I just again tried quickGPS with no difference in reception.
Click to expand...
Click to collapse
please remember that this is still a "BETA" rom. it is not publicly released, or supported by ANYONE. with that in mind, it could get better with time, and when they finally release the public rom, test it again.
I was wondering the same thing if something was changed internally along the line.
I have hardware rev. 03, and my GPS blows.
fallingup said:
please remember that this is still a "BETA" rom. it is not publicly released, or supported by ANYONE. with that in mind, it could get better with time, and when they finally release the public rom, test it again.
Click to expand...
Click to collapse
Yes, and it is unlikely to be the cause of these discrepancies. With identical software setups between the Titans, I have left the hardware to be the lone differentiation. Could later software revisions resolve this hardware dilemma? Possibly, but with that mostly out of our hands and into the OEMs (I'm an old & jaded Toshiba e740 user....), I wouldn't put much hope in getting much more than what we are.
I started this thread because in the GPS FAQ thread some were expressing frustration at being unable to achieve the same GPS performance that was widely expected. With this side by-side comparison it may be comforting (though sad.... )to see that people may not be at fault for setting up the software on their phones. Myself and others were treating the GPS failures as though user error was at fault. After playing with my dad's Titan it is now clear to me that not all Titans are equal, and as such that may explain why the GPS abilities of the phone did not make it active to market. None of us bought these phones with a GPS guarantee.
jsmz, both mine and my dad's phones are hardware revision 0003. Without practical testing I don't think there is an obvious way to distinguish which phone will perform so radically different with its internal GPS. I have no inclination to tear them open..
i have hardware version 0003 and mine works fine...it gets me within ~10ft
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware. Just about all of these units are chipset based and the features each unit has depends on how much of that chipset is used.
The fact that it is possible at all to turn on the GPS would seem to suggest it's not a hardware issue at all as far as chipset capability...
More likely just a individual manufacturing defect of that particular unit...
Could even be a bad soldering job...common with SMT boards.
Asphyx said:
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware. Just about all of these units are chipset based and the features each unit has depends on how much of that chipset is used.
The fact that it is possible at all to turn on the GPS would seem to suggest it's not a hardware issue at all as far as chipset capability...
More likely just a individual manufacturing defect of that particular unit...
Could even be a bad soldering job...common with SMT boards.
Click to expand...
Click to collapse
I was thinking the same thing - the difference from one mass-produced unit to the next shouldn't be that substantial, and a bad/loose/iffy antenna or antenna connection is the most likely culprit.
Give it a good whack on the table and see if that smartens it up
Soundy106 said:
Give it a good whack on the table and see if that smartens it up
Click to expand...
Click to collapse
Just did that, didn't really help My gps really sucks takes at least 10 minutes to get a lock for the first time even outside with cleas sky. And even when I do get a lock using gmaps, it can be off by a whole New York City block, sometimes more. Too bad i can't just go to the sprint repair center and demand a replacement phone Maybe after the official release i will, who knows? But thank to this thread I don't feel so stupid anymore. I always thought i was doing something wrong, and after reading pretty much everything on gps here and installing quickGPS, i am quite sure it's not because of me.. But if anyone knows anything else i should try please feel free to tell me. Thanks
Asphyx said:
My guess is if there are any deficiencies from one unit to the other it would most likely be in the Antenna not the actual hardware.
Click to expand...
Click to collapse
Well as per forum posts the apparent hardware (chip revision, manufacturing flaw, etc...) discrepancy between units does not seem to be very isolated and it is best for all of us to be aware of this before banging our heads against the wall to get an afflicted unit operating.
My GPS works so well I was able to get a sustained lock at 35000 FT on a recent plane ride. That was cool, to see speed at 627KM/hour.
I have a friend that is also having GPS issues, so it appears to be fairly widespread.
having gone through 9 (yes, nine) telus P4000 units, i'm certain they are plagued with inconsistencies... getting on telus' case won't do much either except get you refurb after refurb if you're past the initial 14 days.
Lutzik - You mention off by a NYC Block...
Are you trying to use this in NYC?
I will point out that the height of buildings do block your unit from seeing enough satellites to get a fast and quick lock and whats more is you will also get reflections off the buildings that can hurt your accuracy if the conditions are right.
Remember GPS operates and locates you by noting the delay time it takes a signal to get from one of the satellite to you. It calculates the time it took the signal to get to you to determine how far away from that sat you are. By doing that for three sats minimum it triangulates your position...
Not a big problem with AGPS enabled navigators since the cell towers help ensure you have enough signal sources to throw out the errant data.
Sorry that did go a bit off topic...
I think the real issue is the beta radio driver. when a stable release is finally made I bet most everyone's sat lock and transmission issues will go away.
Asphyx said:
I think the real issue is the beta radio driver. when a stable release is finally made I bet most everyone's sat lock and transmission issues will go away.
Click to expand...
Click to collapse
It is possible to think that but beyond guessing we lack information to assume so while we have recorded cases of the erratic performance between devices with the identical software.
If a future software release resolves the problem then that further reaffirms a hardware discrepency between units. Yet we haven't seen a diffinitive answer that the units do have different gpsOne or other chipset revisions that require a software resolution while others units do not. As a few people are having GPS issues it may come down to the afformentioned quality control, manufacturing/design changes, etc..
It's cheaper to release a unit to retail without a potentially flawed feature than to advertise what may be broke and swallow a recall. I do think that we may be seeing why these phones were not sold as GPS enabled PPCs.
Hello everyone. This is my first post on XDA. I've been lurking for a month or two, and have decided that XDA is the place to be!
I've had my Bolt since April, and like many others I am very frustrated with it. The OTA back in May/June, the one that caused all the random resets, made me start exploring and discovering this thing called 'rooting'. Back then I felt that rooting was a risk I didn't want to take, yet. It reminded me a lot of my Dish Network days, where keeping up with ECM's was an ongoing hell, and I just didn't want to go back there. The OTA after that fixed the resets, and bought some time while I researched rooting.
For the most part, it seems like most of the problems are software related, and the hardware is just being held hostage by crappy coding. BUT, it also seems like most every TBolt owner is on their third device because of hardware issues. I don't want to trade up for a less-than-new device. I did go through an authorized reseller, and bought a year-long, no questions asked warranty, so I can play that card if needed.
My dilemma is that I am ready to root, but if I have bad hardware, I want to return an un-screwed with device. I know that I can unroot, but it would be my luck that it wouldn't go well. And believe me that I considered modding it just to see if it is the hardware or not.
ISSUES: I have various quirky things going on that are obvious software problems, like texts going to the wrong people, butt-dialing (once), CPU lock-ups, erratic scrolling (browsers mostly), software lags, etc.. I think the touch screen, though hardware, is controlled through SenseUI, which has really contributed to my wanting to go with AOSP. The biggest issue I have is with the data connection. I've read a lot of threads on this that have ended in numerous solutions. The most common culprits seem to be the SIM card and the battery cover (idiot design btw). Regardless of whether I am in a good coverage area or not, I have the classic ... 3G..1X..3G..nothing..1X..1X..1X..nothing..3G..nothing..1X..etc. This was really terrible before one of the OTA's, after which it seemed to settle down. I've also experimented with the modem settings, and also the radio settings. CDMA auto PRL works best. Still unsure about the modem settings. Currently I have CDMA only for preferred mode, Enable for Rev A., and Disabled for 1X diversity. I still experiment with these settings, but don't really see much difference. A detailed guide to those settings would be really kick-ass. One day, my phone wouldn't let me make or receive voice calls. Somehow, a setting changed that set it for EVDO only, really strange.
I use Easy-Tether, and have recently been using a Wilson dual-band repeater/amp. I have also found a most excellent app called RF Signal Tracker, which gives me separate RF meters for voice and data, and also shows the state of the SIM card when toggling Airplane mode. I live a little bit out of the city, so I know that serving towers might be causing some headache. With the Wilson, both meters are around -72dbm, which is decent. In town, without the Wilson, it's a little better, around -66dbm. I will stare at this this thing and watch the EVDO meter bottom out at -120dbm and then bounce back. Sometimes it will stay on 1X (for hours probably if I let it), requiring a reboot (or airplane toggle, it varies). Sometimes, while using ET, the signal strength will be awesome, but I get connection errors like it's not even hooked up, or I'll be typing a lengthy post and when submitting I'll get a Connection_Reset error. Sometimes the throughput will blaze (even while streaming), sometimes I'm reaching for a hammer. I have also found that "It works...if i use it," meaning that a data session might start out crappy, but will stabilize. There are times when the data connection is crappy, and rebooting the phone will fix it. And of course, there are many days with no issues at all.
With a hundred different combinations, I can find no rhyme or reason why this handset cannot maintain a data connection with consistency. I'm leaning toward software, but I still can't tell. Others with this problem had their SIM card replaced, which worked, but maybe it was just the battery cover. Is there a fool-proof test I can do that will troubleshoot this? Another possibility might be Big Red Brother compelling me to buy a Nexus.
And: 2.2.1
BB: 1.39.00.0627r
K: 2.6.32.21-g0606a3a
Build: 1.70.605.0
Pete said:
Hello everyone. This is my first post on XDA. I've been lurking for a month or two, and have decided that XDA is the place to be!
I've had my Bolt since April, and like many others I am very frustrated with it. The OTA back in May/June, the one that caused all the random resets, made me start exploring and discovering this thing called 'rooting'. Back then I felt that rooting was a risk I didn't want to take, yet. It reminded me a lot of my Dish Network days, where keeping up with ECM's was an ongoing hell, and I just didn't want to go back there. The OTA after that fixed the resets, and bought some time while I researched rooting.
For the most part, it seems like most of the problems are software related, and the hardware is just being held hostage by crappy coding. BUT, it also seems like most every TBolt owner is on their third device because of hardware issues. I don't want to trade up for a less-than-new device. I did go through an authorized reseller, and bought a year-long, no questions asked warranty, so I can play that card if needed.
My dilemma is that I am ready to root, but if I have bad hardware, I want to return an un-screwed with device. I know that I can unroot, but it would be my luck that it wouldn't go well. And believe me that I considered modding it just to see if it is the hardware or not.
ISSUES: I have various quirky things going on that are obvious software problems, like texts going to the wrong people, butt-dialing (once), CPU lock-ups, erratic scrolling (browsers mostly), software lags, etc.. I think the touch screen, though hardware, is controlled through SenseUI, which has really contributed to my wanting to go with AOSP. The biggest issue I have is with the data connection. I've read a lot of threads on this that have ended in numerous solutions. The most common culprits seem to be the SIM card and the battery cover (idiot design btw). Regardless of whether I am in a good coverage area or not, I have the classic ... 3G..1X..3G..nothing..1X..1X..1X..nothing..3G..nothing..1X..etc. This was really terrible before one of the OTA's, after which it seemed to settle down. I've also experimented with the modem settings, and also the radio settings. CDMA auto PRL works best. Still unsure about the modem settings. Currently I have CDMA only for preferred mode, Enable for Rev A., and Disabled for 1X diversity. I still experiment with these settings, but don't really see much difference. A detailed guide to those settings would be really kick-ass. One day, my phone wouldn't let me make or receive voice calls. Somehow, a setting changed that set it for EVDO only, really strange.
I use Easy-Tether, and have recently been using a Wilson dual-band repeater/amp. I have also found a most excellent app called RF Signal Tracker, which gives me separate RF meters for voice and data, and also shows the state of the SIM card when toggling Airplane mode. I live a little bit out of the city, so I know that serving towers might be causing some headache. With the Wilson, both meters are around -72dbm, which is decent. In town, without the Wilson, it's a little better, around -66dbm. I will stare at this this thing and watch the EVDO meter bottom out at -120dbm and then bounce back. Sometimes it will stay on 1X (for hours probably if I let it), requiring a reboot (or airplane toggle, it varies). Sometimes, while using ET, the signal strength will be awesome, but I get connection errors like it's not even hooked up, or I'll be typing a lengthy post and when submitting I'll get a Connection_Reset error. Sometimes the throughput will blaze (even while streaming), sometimes I'm reaching for a hammer. I have also found that "It works...if i use it," meaning that a data session might start out crappy, but will stabilize. There are times when the data connection is crappy, and rebooting the phone will fix it. And of course, there are many days with no issues at all.
With a hundred different combinations, I can find no rhyme or reason why this handset cannot maintain a data connection with consistency. I'm leaning toward software, but I still can't tell. Others with this problem had their SIM card replaced, which worked, but maybe it was just the battery cover. Is there a fool-proof test I can do that will troubleshoot this? Another possibility might be Big Red Brother compelling me to buy a Nexus.
And: 2.2.1
BB: 1.39.00.0627r
K: 2.6.32.21-g0606a3a
Build: 1.70.605.0
Click to expand...
Click to collapse
You need to research cellular technology. All the signal amps in the world aren't going to make for a stable lte signal unless they're smart enough to unpack the packets and lie about transmission data. That said, pretty much all your issues sound software related. Some of what you call hardware problems cannot be randomly duplicated by hardware failure or even accurately diagnosed without some knowledge and experience. Restoring to stock is easy and quite reliable. Some do it once or twice a week. I have guides in my thread.
Thank you for the response. I confirmed that it was software. I took it to the reseller and found out that even though I took two OTAs this year, the radio never updated, and was still on the original from the release. I'm at 2.3.4 now, with a stable radio. Feeling like I'll take that plunge, now that I know the hardware is good.
BB: 1.48.00.0906w_1, 0.01.78.0906w_2
K: 2.6.35.10
Build: 2.11.605.5
The last half year have riddled various forums with the now infamous Samsung HW/SW bug that is most often causing an extremely unpleasant echo in the other end of a conversation. However, this bug appears in many variants due to the multiple causes of many interacting smaller problems.
In my own quest of finding the root of the problem and scanning the web for a potential solution (not involving send my phone off), I decided to share my findings, very well aware of the shortcomings of my limited research. So please let me know of any current (or future) solution to this, or if I have missed anything important.
Internally there are 2 microphones and 2 speakers. Unfortunately the way these are situated, aligned and and isolated, together with the sound transmission throughout the phone chassis and the complicated sound and digital noise reduction (NR) settings, are the cause of these problems.
All this can best be seen in the iFixit's teardown guide:
http://www.ifixit.com/Teardown/Samsung-Galaxy-S-II-Teardown/5861/1
or in the "S2 screen replacement photo tutorial":
http://forum.xda-developers.com/showthread.php?t=1253969
or in the schematic blow-apart diagram in the official "Samsung-GT-i9100-service-manual". (Google that!)
My Conclusion:
After performing a limited number of tests, on my own, I have concluded that this problem should in ANY case be resolvable by a fix in the phone firmware/software. Obviously the phone is working without a case, and (usually) perfectly when turning off NR (noise reduction) and/or turning down the volume. Others report fiddling with the internal rubber enclosure of the microphones and/or speakers. In either case, it would be very interesting to know the details of your phone's SW and HW configuration as many reports differences in behavior after flashing new/old phone software. It is very likely the problem occurs as a combination of "PHONE/PDA" software, the lower USB charge-port HW and the upper speaker/microphone insulation. In other words the NR algorithm need to be changed or better tuned for various environments. We can only hope Samsung fixes this in their next updates... But very unlikely as they are much more interested in making new phones and selling more of them. And if they did fix it, they probably wouldn't tell anyone since if they ever did admit to any wrong doing, they'd have to replace/repair probably at least tens of thousands of phones!
Problem (Simple Description):
A number of small assembly line variations is causing the internal noise reduction software to misbehave. (Remember the "butterfly effect"!)
Problem (Technical Description):
The problem consists of (at least) 3 smaller problems working together.
1. The lower playback speaker is always on (!) and is causing feedback to the lower microphone when using a protective cover. Thus explaining the greater echo at higher volumes and less external noise, when using a rubber cover.
2. The SGS2 plastic casing transmits sound around the entire phone. Thus both speakers (lower and upper) are transmitting sound to both the lower normal microphone and the upper noise cancelling microphone. These need to be isolated.
So when covering the upper noise reduction microphone you are getting better feedback (more "noise") from both upper AND lower speakers, than from outside and thus (usually) improving call quality by reducing the echo effect, but when there is no case-cover and a noisy environment, you may end up increasing the echo, by covering it up!
3. BUT not all phones have echo, thus there is also a NR settings or algorithm problem that should or may be resolved by a firmware/phone/PDA update. In addition, and making things even more complicated, different phones have slightly different hardware on the PCB of the USB charge-port...
Who to Blame?
1. Samsung Hardware engineers who must have been sleeping in their "Acoustics and Wave Propagation" classes.
2. Samsung (?) Software engineers who never took a course in "Feedback and Control Theory".
3. Samsung HW design director(s) who
a) didn't make (1) and (2) work closely enough together on the SGS-2.
b) never though of putting a rubber case on the phone! 4. Samsung Assembly line Quality Control manager(s) who didn't check for minor design flaws.
- check (open up) every 100 or so phones, if problem check ALL previous 100 and estimate problem!
- stop assembly line and talk to the management about solution ..
..
oo. The casual SGS2 owner who just wanted to protect his new investment with a rubber/plastic cover.
Some Known Solutions:
Service Center Solutions:
1. Improperly placed internal speaker cushion:
http://androidforums.com/samsung-ga...ice-echo-anyone-else-getting.html#post3000051
2. Replace the UI Board; Part No: GH59-10949A
http://androidforums.com/samsung-ga...ice-echo-anyone-else-getting.html#post3269199
http://www.scribd.com/doc/56542824/5/Cellular-phone-Exploded-View
http://giga-tel.com/item-10095-samsung-i9100-ui-board.html
3. Attach layers of soft electrically and noise insulating tape (e.g. medical-tape) over the back-side of the upper speaker, earphone jack and microphone. On the inside of you phone. See instructions in Hebrew (!) below:
http://iandroid.co.il/forum/topic56552.html
DIY Home Fixes (various success):
4. Put some tape over the top NR hole, which is next to the 3.5mm head-phone jack. (This fix messes up the speakerphone functionality!)
5. Put some tape over the hole just above volume-rocker
6. Lower volume
7. Manually disable NR during call: ("HOME" button)
8. Factory Reset (This will wipe your data/contacts and probably only lasts until next reboot!)
9. Try to flash a different phone ROM/Firmware/Kernel/Baseband etc. (Seem like it's mostly Gingerbread 2.3.4 phones being affected.)
10. Perhaps by changing some settings in the hidden "Service Mode" menus (???)
11. Open your phone and
a) make the bottom small microphone hole in the case bigger and
b) cut some of the rubber from the lower microphone cover.
See: "Fix for low microphone volume":
http://forum.xda-developers.com/showthread.php?t=1127103
http://forum.xda-developers.com/showpost.php?p=20022525&postcount=10312. Attempt the above Service Center operations by yourself!
NOTE: It's highly recommended to do only ONE AT THE TIME!
Currently Recommended Solution:
A) WITH stock phone/firmware AND warranty; ask for a new phone and test it!
B) WITHOUT stock phone/firmware OR WITHOUT warranty; Try 11b!
List of Firmwares WITHOUT echo: (PDA/Phone/CSC)
"Polish Stock ROM"
"Many Indian firmwares don't have DNR (KE8 or KF3) activated"
I9100XWKE7 (2.3.3)
KI4/KI1/KH2 (XEU) Echo with DNR OFF (default) NO ech with DNR ON!
KD6/KE7/KD1 (XEU) 'same'
[ If you have/find other firmware solutions, please add them to this thread! ]
Service Mode Settings
Entering Service Mode: *#197328640# OR *#*#197328640#*#* [dial]
See: http://forum.xda-developers.com/showpost.php?p=14692752&postcount=30
These settings are probably ending up in the various audio setting files in: /system/etc/audio (which are only accessible in a rooted phone.)
Potential (Rooted) System Hacks
Tweak/check the files present in: /system/etc/audio
OR perhaps write some Tasker script; see:
http://forum.xda-developers.com/showpost.php?p=19339706&postcount=125
Some custom ROMs come with NR tweaks that allow you to permanently turn ON/OFF DNR:
VillainROM (VRTweaks)
DarkyROM
Revolution 2.7.1
[Could someone confirm & provide a links to these?]
Apparently there are other ways in which you can directly hack the Phone.apk package, under certain conditions. Thus at least in theory it should be possible to directly toggle NR in memory, which could indeed be useful. Here is one variation of the APK hack:
In the Phone.apk package, find the ../res/values/bools.xml file. Edit and recompile after changing the line: "<bool name="has_in_call_noise_suppression">true</bool>".
See: "[HOWTO] disable NoiseSuppression by default, to enlarge mic volume":
http://forum.xda-developers.com/showthread.php?t=1251922&highlight=volume
and start reading from this post:
http://forum.xda-developers.com/showpost.php?p=18932990&postcount=107
Some additional info for hacking Phone.apk:
http://forum.xda-developers.com/showthread.php?t=1332137&page=3
Do you have a contribution or solution?
So if you want to contribute to the solution and permanent fix of this (or any other comments), please post the following info, as well.
1. Baseband (aka. "Phone") version
2. Kernel version
3. Build number
4. The USB-charge-port PCB version (if known)
5. Your particulars when it works and when it doesn't
6. Details on how you fixed the problem, if you did!
To find info use these codes on the dial pad:
Firmware Version: *#1234#
Hardware Version: *#2222#
Both Versions: *#8999*8376263#
That way we may hope to find and fix the problem ourselves!
Some of this I already mentioned here:
http://forum.xda-developers.com/showpost.php?p=20142257&postcount=99
http://forum.xda-developers.com/showpost.php?p=20143129&postcount=28
http://androidforums.com/samsung-galaxy-s2-international/357910-voice-echo-anyone-else-getting.html
Also try to search the "Samsung Galaxy S2 Q&A" forum for "Echo Noise Reduction".
http://forum.xda-developers.com/search.php?searchid=104855328&pp=25
Thanks and I hope this helps!
...
UPDATE: 2012-01-30
Apparently there have been many reports of very happy people doing their own SGS2 surgery following the thread:
http://forum.xda-developers.com/showthread.php?t=1441510
This is essentially equivalent to the solution in number #3 above!
+1 for the effort, about time someone did an all-in-one topic about this rather common issue.
I've had the same problem and noticed it the day I bought my phone, a friend called and immediately complained about the echo. I did a quick Google search and found out that it's a rather common problem and caused by most case types, removing the case or disabling NR did indeed fix my problem.
Anyway, I have tried many fixes, including VillianTweaks/LeoMar's fix, turns out those only remove the ability to turn NR on/off, but it was still turned on by default. This fix however was the only one that actually worked:
http://forum.xda-developers.com/showthread.php?t=1332137
The fix above had a minor drawback though, the first call after reboot always had NR enabled by default. I wanted a set and forget solution to permanently disable NR so I learned a bit about deodexing/decompiling and managed to get rid of it for good, you can check the fix in here:
http://forum.xda-developers.com/showthread.php?t=1372718
Wow
E:V:A said:
After performing a limited number of tests, on my own, I have concluded that this problem should in ANY case be resolvable by a fix in the phone firmware/software. Obviously the phone is working without a case, and (usually) perfectly when turning off NR (noise reduction) and/or turning down the volume.
Click to expand...
Click to collapse
I'd disagree. I heard a slight echo also without the case (I called from a land phone to hear it myself). Lots of SGS2s work fine with cases, with NR on. Killing NR should not be considered the solution.
I've opened the phone and inserted two thin layers of white medical tape over the ear speaker (much less tape than in that hebrew sample). The original echo gone completely, with and without case. But now the other party hears a very slight echo of me. I don't consider tape a solution either. Perhaps the speaker is not mounted properly (sticks out too much)?
I was wondering about the position of the cushion, don't understand what that guy meant precisely. Mine looked a bit squashed by the case, maybe too firm contact?
> 1. The lower playback speaker is always on (!)
Are you sure? It could be transmission via the case? I guess the add-on cases increase the transmission.
> 3. BUT not all phones have echo, thus there is also a NR settings or algorithm problem that should or may be resolved by a firmware/phone/PDA update.
I'm not sure the NR algorithm can be fixed so that it can work with a faulty phone.
> Service Center Solutions:
Add 4. Replace old SIM card
I'm using stock 2.3.4 I9100XXKI1
2.6.35.7-I9100XWKI4-CL575468
[email protected] #2
FTA HW REV1.5
Baseband: KI4
ROM: MIUI 1.12.2
Kernel: Siyah 2.4.2
Everybody I talked to used to tell me that my voice echoed pretty bad. Then I switched to the KI4 modem and the issue was resolved. Maybe someone with this echo problem could try the KI4 modem and report back.
Sent from my GT-I9100
@bazzag: Thanks for VillainTweaks info, I'll scratch that until further notice.
@_sem_: Essentially I agree that killing NR is not a proper solution, as it is just a remedy for a sickness, which would return in a very noisy environment when NR may be needed. But given that this will probably never get properly fixed, it seem to be the best option we have for now. ALSO:
a) In the 1st § you say you called your own phone and found echo, then in the 2nd § you said: "But now the other party hears a very slight echo of me." these seem the same to me, or did you mean that now you hear echo when using your mobile to call someone else?
b) > 1. The lower playback speaker is always on (!)
Actually I am not sure about this as I live in very noisy environment, but everyone standing next to me, during phone calls, say then can hear everything the other person is saying!
c) > Service Center Solutions: Add 4. Replace old SIM card
Now THIS is a shocker! Why on earth would upgrading the SIM card have anything to do with this? Where did you see and hear about this solution?
d) We have the exact same stock SW/HW!@iHoneyBadger: Yes! Could someone provide a link for (easy/noob) instructions on: (1) where to find/download the KI4 Baseband files and (2) how to easily install only Baseband?
@E:V:A
> Essentially I agree that killing NR is not a proper solution, as it is just a remedy for a sickness, which would return in a very noisy environment when NR may be needed. But given that this will probably never get properly fixed, it seem to be the best option we have for now.
I think the best option is the service center if you have stock ROM. You may need to convince them first, best by showing another SGS2 that works fine with your case. But that'd take much more time for me than inserting that tape did.
It really isn't difficult. Except that I'd feel a bit better knowing the exact problem better. It may be possible that the change was just due to taking the phone apart and back, not the due to the tape. I'm too lazy to do it five times trying this and that I'd ask the next one who tries this to check if the speaker can perhaps be pushed a fraction of a mm deeper into its seat, so that the speaker would have less or no contact with the (removed) back of the case. I think this could be better than tape.
> a) In the 1st § you say you called your own phone and found echo, then in the 2nd § you said: "But now the other party hears a very slight echo of me." these seem the same to me, or did you mean that now you hear echo when using your mobile to call someone else?
This echo is on the level of the previous echo without case - barely noticable if you're listening carefully, but no longer an issue really. And, those phones that do not have the problem don't have any tape inside
b) > 1. The lower playback speaker is always on (!)
> Actually I am not sure about this as I live in very noisy environment, but everyone standing next to me, during phone calls, say then can hear everything the other person is saying!
I think this could also be caused by the case conducting the sound. It must also be emitting some around. I've also read some folks got improvements by cutting ugly large holes in gel cases at the back - that'd probably decrease conduction.
> c) > Service Center Solutions: Add 4. Replace old SIM card
Now THIS is a shocker! Why on earth would upgrading the SIM card have anything to do with this? Where did you see and hear about this solution?
I think it was a german forum android-hilfe
/samsung-galaxy-s2-i9100-forum/144551-probleme-beim-anrufen-echo.html
/samsung-galaxy-s2-i9100-forum/174469-echo-problem-sgs2.html
@E:V:A
It's in the modem thread in the original development section.
Here's a link to the CWM flashable zip...
http://www.multiupload.com/0FTG1P9MK4
Edit: It's just the modem. Let us know if it helped.
Sent from my GT-i9100
Your modem did NOT work for me :-(
put k14 modem on my phone
so i just added the modem as of now doesnt seem to be any noticeable echos. I will use it for a day with a case and see what happens.
Just tried to install the zip on power up of the phone....it starts but I just get a signature verification failed error. The progress bar hangs and when I go back to the root menu in recovery the error message is present in red.
Am I doing something wrong?
I had also the echo problem and also the other person could not hear me well... After changing my modem firmware to BOKJ1. This is a custom made firmware for Greece Cosmote... My voice is now loud and clear.
But I have also made a change to the stock dialer at KK5 deodexed ROM (Omega v9) so that the phone starts with noise reduction off.. but you can enable it from the menu during call.
Please see my post..
http://forum.xda-developers.com/showthread.php?t=1388058
iHoneyBadger said:
It's in the modem thread in the original development section.
Here's a link to...
Edit: It's just the modem. Let us know if it helped.
Click to expand...
Click to collapse
Thanks! I will flash a complete new ROM (with a different Modem) in few days, when I get some more time off. I'll get back to you on the results.
talexop said:
...
After changing my modem firmware to BOKJ1. This is a custom made firmware for Greece Cosmote... My voice is now loud and clear.
But I have also made a change to the stock dialer at KK5 deodexed ROM (Omega v9)
...
Click to expand...
Click to collapse
Please see my response at:
http://forum.xda-developers.com/showpost.php?p=20306528&postcount=11
This does not seem like stock...
a) Where did your Phone.apk come from?
b) What did you do?
c) How does it compare (diff) to a real stock,lets say the 2.3.4 (XWKI4 / XXKI1)?
Could someone test this?
E:V:A said:
Please see my response at:
http://forum.xda-developers.com/showpost.php?p=20306528&postcount=11
This does not seem like stock...
a) Where did your Phone.apk come from?
b) What did you do?
c) How does it compare (diff) to a real stock,lets say the 2.3.4 (XWKI4 / XXKI1)?
Could someone test this?
Click to expand...
Click to collapse
Please see my responce. I hope I made it clear for you. I have tried a patch nobody else did and to tell you the truth I cannot uderstant why they did not! My patch is way to easy and leaves the user choise to reenable noise reduction.
Also all the other patches did not work for me. The one I made worka fine.
http://forum.xda-developers.com/showthread.php?p=20320415
Sent from my GT-I9100 using Tapatalk
I don't know for u guys but with last KK5 Roms my sound is terrible.
When i speak with people sounds as i call out of the box
Can't find f'in solution....
BuzzFuzz said:
I don't know for u guys but with last KK5 Roms my sound is terrible.
When i speak with people sounds as i call out of the box
Can't find f'in solution....
Click to expand...
Click to collapse
First of you should try to change your modem firmware... This did the best work for me. You should try the one you had before... If that one was ok... Also you can try my dialer which works for KK5..
Sent from my GT-I9100 using Tapatalk
Used my phone without my tough mate case and have worried about dropping my phone all day! Really wish i could sort this myself, why can i not install this modem zip?! Echo def gone without case no complaints at all. It doesn't feel right without a case! If someone could help me install this modem id be eternally grateful!
sent from t'internet
Dear all, i was testing the loud speaker (you know, speaking with speaker on) and unfortunately no one can hear me. When i disable it everything is ok. I made a hard reset, but nothing changed. Do you have any alternatives??
Thanx
Hmmmmphh....back to a service centre for my phone then! This is a fundamental flaw with the phone. Problem still occurs without a case if the top of the phone moves too close to my head!
Hello - Dear XDA Developers Community,
First up... I'm a NOOB! (thought I'd get that out of the way first & foremost).
2nd - Please no suggestions I get my money back (already pursuing that option)
I've had a fairly modest history with Android devices, culminating in my most recent purchase a used Samsung Galaxy SII (18 months old) off eBay from a private seller. Unfortunately, from the minute I switched it on I expereinced chronic problems in achieving a reliable & consistent signal for voice & data. I'm in the UK on a PAYG & 3 are my network provider.
Upon switching the S II on with my old SIM inserted & going through some initial config (google account, SMS configuration settings, etc). I experienced intermittent signal loss for both voice & data. sporadically my phone would have no service or 1 bar (voice only!!). Expecting this to be a transient network issue I switched my SIM back into my old phone (Samsung Galaxy Ace) which gave me a consistent 3G signal. Now alarmed, I called 3 Customer services & we went through a rather lengthy trouble shooting session on the phone (multiple reboots, manually entering network details, restoring factory settings, etc). None of this worked and the 3 guy recommended I upgrade to the latest Samsung approved firmware in the hope that would perhaps fix the problem. I successfully update the firmware (details below) but the problem remained the same....
Current Android Level :-
Android Version : 4.1.2
Baseband Version: I9100NELS1
Kernel Version 3.0.31-889555
I perfomed the same tests at my house with identical results. Galaxy Ace with same SIM had decent, reliable & consistent 3G signal whereas my S2 with the same SIM struggled to achieve 1 bar at best (not even 3G or HDSPA - just a very weak voice signal). I called 3 customer services again who advised following all the action taken (and in light of both locations - B98 9AY & CV11 6GH having no coverage or network problems) the problem is definitely with the handset & there's nothing they can do.
So, I went for a stroll...... Amazingly in other areas I can achieve a good signal with high speed data transfer rates on HDSPA+ (up to 8 meg according to speedtest app). Unfortunately, in the two locations I spend the vast majority of my time (Office & Home) the phone is rarely anything other than a glorified WiFi enabled device.
I also remembered I had a GiffGaff SIM so gave this a try as well. The singal was also patchy at best and I didn't even get anything approaching a data strength reception. I checked on the o2 coverage checker which informed my location should easily be able to pick up a good voice & data signal. All of which strengthens my suspicions the problem is with the handset itself.
I've spent many hours trawling the Internet for solutions and can't see too many instances that closely match the symptoms I'm experiencing. I've downloaded the OpenSignal app - which is of limited use for me. At the moment I'm thinking this will have one of three root causes (at the moment I'm sulking and thinking it's option 1).
1) The Samsung Galaxy S II receiver is simply crap and there's nothing I can do
2) The Samsung Galaxy S II receiver is defective or inefficient at a hardware level (could send off to have it fixed)
3) There's some problem with the drivers/firmware for the receiver that will require a custom ROM upgrade to fix.
I'm open to the idea of rooting & installing a custom ROM to fix this, but only want to go down this route if it's pretty certain to have a positive outcome for this problem.
Thanks for taking the time to read this & look forward to your replies.
Kind Regards,
BrokenSparrow.
try the nordic 4.1.2 rom download HERE link from sammobile.com. flash it and see if it helps other than that you could try different modem files.. there is as thread about it around here some were....... HERE give that a go and see what happens gotta be worth the shot before righting off the whole phone... GOOD LUCK
That's tells me it's most likely down to the particular equipment your carrier is using in the cells close to where you use the phone the most (when it doesn't work). If it were a hardware issue, you'd either have the problem intermittently everywhere or all the time/everywhere. Tho that doesn't completely rule out a hardware issue; I'm just saying, on balance & on the evidence you've offered, that's my theory.
What I'd do in your situation phone-wise is to go back to ICS stock - rooted (not 4.0.4) & flash a bunch of different modems (rooting your phone/having CWM rather than stock recovery will make this process relatively simple) & see if you find one that improves your connectivity where you use the phone most. Unfortunately, modems are black boxes & largely undocumented (publicly at least), so people have found out through trial & error which modems seem to work well with which carriers/in which countries (and sometimes even in certain areas; that variation in equipment carriers use in different base stations).
A good place to start is try all the modems bundled with stock roms released by your carrier. Reasoning being you'd hoped your carrier would have thoroughly tested every facet of a rom before releasing it, and that the modem bundled with it would work with their network most of the time/in most places.
If you still didn't have any joy once you've done that (not very many to try given your carrier has probably only released a handful or roms, so it wouldn't take you long), then you could search here & look at what modems other people had tried with your carrier & try those, then you could start trying any/every modem you can get your hands on (there's dozens; relax, if one doesn't work, the worst thing that can happen to your phone is you'll have no connectivity with that particular modem, which you remedy by going back to one you know works).
If you'd done all that & still had the same problem, I'd be sending it back to seller & frankly, given the problems you've had from the get-go, you may want to consider that sooner rather than later unless you have the stomach to try a lot of stuff that has no guarantee of fixing your problem. You could also have a phone tech take a look at it either before or after you start your own troubleshooting, but if it were me, I'd be returning it given you have no real way of knowing it's history.
brokensparrow said:
So, I went for a stroll...... Amazingly in other areas I can achieve a good signal with high speed data transfer rates on HDSPA+ (up to 8 meg according to speedtest app). Unfortunately, in the two locations I spend the vast majority of my time (Office & Home) the phone is rarely anything other than a glorified WiFi enabled device.
Click to expand...
Click to collapse
Root and updae RIL (and SIM)
brokensparrow said:
I'm open to the idea of rooting & installing a custom ROM to fix this, but only want to go down this route if it's pretty certain to have a positive outcome for this problem.
Thanks for taking the time to read this & look forward to your replies.
Click to expand...
Click to collapse
Root the handset (http://forum.xda-developers.com/showthread.php?t=1826497 (thanks pelpa87)) and look into updating the RIL (Radio Interface Layer) / BaseBand (free app available form Play called GetRIL (thanx to SIBBOR) will assist in updating RIL) BaseBand tends to be updates with ROM (so poss update ROM too).
Also, people forget that the SIM card is a micro controller, with its own software, memory and (big pinch of salt here) processor, using a new(er) SIM / USIM card will help improve signal.
All,
Many thanks for your advice so far. I've done the following
- Rooted the phone
- Gone back to ICS 4.0.4 and tried various modems from links provided
- Tried JellyBAM, NordicOS & SlimBean with a combination of different modems
- Ran the GetIRL utility and matched up with Baseband version
I get similar results from all of these steps & the common denominator appears to be the modem. I experience slightly improved reception using NEL3 and XXG3. These improvements are marginal, but do at least give me a voice only connection in the afforementioned locations (but interestingly only on Orange/3 - which I guess is 3's failsafe network).
Also, discovered Samsung warranty for all smart phones is 24 months.... As this handset is only 18 months old it may be eligible for repair as the small print on the warranty statement declares the warranty entitlement can be transferred to different end users. This does represent me with a slightly different problem however! I've been messing around with the phone rather a lot (more than enough to void the warranty). So, before I send it off I need to make it as close to the stock version of Android as I can. These are the things I can think of....
- Install latest stock Firmware via Kies (think this should unroot and put me back on a stock kernel)
- Remove all the zip files used for "tinkering" from the internal SD card
- Also noticed several times there a utility that shows you exactly how many times custom ROM's have been put on the device - so this is something I'm anxious to remove as well. Any other points or advice on how to conceal my "tinkering" from Samsung?
Thanks & Regards,
Graham.
-
Triangle away to reset the rom counter otherwise your there. Triangle away is on xda here some were but you'll have to go search fir it as I dont have a link or computer to hand just now. Good luck.
LSJ Powered Time Machine.
---------- Post added at 06:33 PM ---------- Previous post was at 06:23 PM ----------
FOUND IT... http://forum.xda-developers.com/showthread.php?p=22462960
LSJ Powered Time Machine.
It's possible that the previous owner replaced the USB flex cable/board with the newer version, which requires a resistor to be de-soldered otherwise it will have extremely poor reception. The previous owner might not have stumbled upon this fix, and thought he'd just get his money back by selling it. Check LittleCanon's post and pictures on page 2 of this thread: http://forum.xda-developers.com/showthread.php?t=1611409 and compare the pictures to your usb flex cable/board. It's a very simple & easy fix if that's the case. I replaced the usb flex cable/board on my i777 and had the same exact issue until I de-soldered that resistor, now it works perfectly.
So I've been using my phone a few weeks now. The first handset I exchanged as it had a stuck pixel near the centre of the screen. The replacement was ok, the screen isn't perfect, but it's definitely acceptable.
I feel really split on the phone. On the one hand, I really like the hardware. The phone is well constructed, feels solid, no glass back. A headphone jack is a big plus. The camera is fine for the price and more. Also, I do like many aspects of EMUI as it utilizes similar customizations to LG.
However, the phone is starting to annoy me on a regular basis. Most notably issues with notifications, widgets and Bluetooth. All things that appear to dog Huawei/Honor phones to one degree or another. Thing is I rely on those three day in, day out.
I'm not fussed about gaming ability or adding filters to photos. I just want the (Android) basics done right. Not too much to ask is it.
The question is how long do I wait to see if they sort any of these issues. Sure, I could email or Facebook message them, but I'm certain the reply will involve clearing the cache, resetting the phone etc. If I send it in for 'repair' I doubt it would come back any different.
As firmware updates appear to be a lower priority than many OEMs I'm not hopeful. As the phone has been out a few months now in a number of territories I would have expected some dedicated ROM development by now. Perhaps that was a little optimistic.
Rooting looks like a necessity in the short term. Just to see if I can fix the notifications and widgets.
Longer term, well due to my lack of faith I'm going to keep an eye on the market. Last year I tried both the G6 and the 5T. The former was returned because the screen was uneven, with a dark patch in the middle. Also, I just didn't like it enough. The 5T, while perfect in many ways, gave me headaches. Whether that was a PWM or OLED thing I couldn't say. I don't suffer using PWM laptop screens, so it I guess it was the vibrancy or something else. Anyway, OLED screens are off my list. Shame as I really like using my Samsung Tab A which is a standard LED and would buy a Samsung phone if they hadn't had all switched screen tech now.
I kinda hope I can find solutions to the phone's issues. Simply because I don't think I'll find a better 'bang for my buck'. Just a question on how long I'm prepared to give it.
So, what exactly are your issues with notifications, widgets, and bluetooth?
I guess he is saying about battery consumption notification coming if any apps uses too much battery. That is problem of Android Oreo. Not the fone
freeza said:
So, what exactly are your issues with notifications, widgets, and bluetooth?
Click to expand...
Click to collapse
I leapt on this thread previously, so I've outlined the issues previously. However, I'll provide more detail here.
Notifications - Initially a proportion of notifications were not coming through. This appeared to be sorted by taking the apps in question out of automatic control. However, clearly some notifications get delayed, This is most noticeable when the phone has entered the 'doze' zone as I like to call it. If the phone is left idle for a long period, then little or no app notifications will appear. So you'll find first thing in the morning a bunch of stuff coming through when you start using the phone.
Then theres's the sounds, I've found unless the app has a specific option to select the notification sound, you'll just get the phone's default one i.e. Whatever you've chosen. This is a problem with things such as Sky or BBC Breaking News alerts. Both apps have dedicated sound alerts, neither provide the ability to choose. So this means it's impossible to audibly tell what an alert is, unless you can specify the alert sound in-app. A nuisance when you are busy or out and about.
I have tried to resolve this by installing the app NotifiCon. The app provides notification sound customisation on an app by app basis. While it initially appeared to work, there was a problem. While it was fine when the phone was unlocked and being used, the selected alert would be heard. When locked, only the phone's default sound would play. That is until you unlock the phone, then you'd get the one you specified in the app! Not quite what you'd want. I do need to get back to the dev to report my findings. He might be able to resolve it. However, I should have to be seeking third-party solutions to a very basic function.
Widgets - EMUI based phones appear to have a real issue with scrollable widgets. In my checking on the net, I've read countless reports on XDA, other forums and Facebook. Again, I've found my news apps to be the worst affected. Widgets either don't function or get stuck. The only workaround is to use Nova launcher and flip the phone into landscape which supposedly indirectly forces them to update. Even that is somewhat hit or miss. I feel sorry for those that rely on a calendar and other widgets that provide time-sensitive functions. Once again, this is basic functionality.
Bluetooth - I stream a good couple of hours a day. I use Android music server software Muzecast and listen to a number of podcasts. So I want Bluetooth to be a smooth as possible. Alas, I've found, like the OP in the thread I mentioned above, there's something not right with View 10. Speakers will randomly lose the ability to play/pause and, if the speaker supports it, skip tracks etc. Note - volume control isn't affected. From my experience, I cannot pinpoint what causes this. Again, this might not be too much of a bind if your speaker is next to you on the desk. However, I can see this would be a huge problem with headphones or in-car.
The second problem, I've noticed a CD skip like sound affecting playback. It's not frequent but you will spot it. Also, the sound can get garbled for a second, this is quite jarring when it happens.
Finally, the connection is hit and miss. My main go-to portable speaker has trouble hooking up with the phone. Often it will mean toggling Bluetooth off and on in the settings. This contrasts with my soundbar which works first time, every time. However, this creates another issue. If I'm playing music on my portable speaker and the phone is in range of the soundbar, it automatically switches to the later! Umm. . . That's surely not right, since there's no setting to prioritize which device playback should be through. It was so frustrating that I unpaired the soundbar and if I want to listen with it I use an old tablet instead.
So there you go. I'm certain these are in the main cross-device issues which are down to EMUI. The specific Bluetooth problems may be a quirk of the View 10, but for the rest, you can find plenty of evidence across the web. Huawei appears to be paying lip service or just ignoring them while quickly bringing the next handset to market. Disappointing.
Edit:
ben cherian said:
I guess he is saying about battery consumption notification coming if any apps uses too much battery. That is problem of Android Oreo. Not the fone
Click to expand...
Click to collapse
No, I'm not, as you'll see from above.
Do one thing. Go to Settings-> Battery -> Launch and select the apps manually that you require for notification. Monitor and provide the results to us.
tomtapatalk84 said:
Do one thing. Go to Settings-> Battery -> Launch and select the apps manually that you require for notification. Monitor and provide the results to us.
Click to expand...
Click to collapse
Was the first thing I did. Solved a lack of notifications but has zero effect on the delayed.
While I was checking on the status of the exchanged phone with my retailer (John Lewis in the UK), they let me know I actually had a 35 day return window if I wasn't happy. Something I wasn't aware of.
So after having a long conversation with one of their tech guys (who actually knew his stuff!), I did some further research.. Now I'm even more certain that these are EMUI problems across the board.
Indeed, if I'd spent top dollar on a flagship Huawei unit I'd be extremely annoyed. but TBH I'm just disappointed. Decent hardware and tons of potential hobbled by over zealous battery/power management and some suspect wireless chips.
Having read today about Huawei removing bootloader unlocking for new devices, just confirms I've made the right decision in returning the View 10. Seems like they won't fix problems and in the future they won't let you fix them yourselves. That's a very poor move.
Best of luck to those sticking with their brands.