Develop Bugs

Updated 24.11- Galaxy Nexus Volume problem is hardware related...but fixable by soft?

Well, as you can see from the video below, the guy set the highest volume, then place the smartphone near the Galaxy Nexus and the Galaxy Nexus respond to it. This is CLEARLY hardware issues. This could be the real reason Verzion still haven't release the Galaxy Nexus yet.
www.youtube.com/watch?v=BIFRYY25fDo
Thanks dnlsmy.
www.youtube.com/watch?v=y_mO_K7OYR0
Update 1
Google "We are aware of the volume issue and have developed a fix. We will update devices as soon as possible."(and you holding it wrong xDD) jk
Update 2: Lee Johnston explain of "volumegate" issue
Let's talk about the Google Nexus "volumegate" issue.
Today Google said that they have fixed the problem in software, and that a fix is coming.
I see many people saying this is a bunch of BS, but in reality they just have no idea how complex electronic circuits and software interact.
I'm a Systems Engineer and also a Developer. I deal with things like this every day.
What we have here is indeed a hardware issue, in that the radio interference is coming in through the radio hardware.
However things like this can be fix fairly easily in software. It's called debounce.
When you monitor an electronic input like the buttons on a phone there is always noise and flutter even when you just press the button. If testing by Google has shown that they just need to turn up the debounce time (the time which an input must exceed for it to be determined to be a genuine press) then it will more than likely just work and no one will ever see ti again.
Like I said I deal with this kind of thing every day, it's not a big deal as long as your debounce time is not excessive. But noise happens down on the order of 1 to 40 ms, real inputs when you press a button last from 100 or 200ms if you tap the button, up to seconds if you hold it down.
This is nothing like Apple and the iPhone 4 antennae problems that could not be fixed in software. I'm sure everyone will see in due time, the problem will be fixed, and the dust will blow over.
And people will be saying "wow, I was wrong, Google rocks
Cheers,
Lee
Finally, Where is the GSM HSPA+ 32GB version of Galaxy Nexus??????!!!

Yeah, and for further proof, he does it in the bootloader screen of the GNex
http://www.youtube.com/watch?v=y_mO_K7OYR0
This seems like it's a hardware fault entirely.

I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.

TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.

TiltedAz said:
I wasn't sure what the test was but it looked inconclusive to me. Almost looks random.
Click to expand...
Click to collapse
well you're mistaken then. the test is not inconclusive at all.

martonikaj said:
He has an incoming call on the other device. When it touches the side of the Galaxy Nexus it causes the volume to erratically go down/up. It just shows that the radios are effecting the volume.
This would fit with people saying its happening when the phone is in 2G networks.
Click to expand...
Click to collapse
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.

TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
no software patch can fix this. the phone has inadequate RF shielding.

My bionic which I know is a different device does something similar. When I put it next to my corded work phone and the bionic switches to 4g it causes the speaker on my work phone to male a distortion noise even when it is hung up. So I can see where the radios cause some sort of interference on these 4g phones
Sent from my DROID BIONIC using Tapatalk

TiltedAz said:
Ok, gotcha.
Still could be software and even if it were hardware a little software patch could resolve it.
Click to expand...
Click to collapse
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0

Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App

Would that have anything to do with the nfc chip?

DammitCubs said:
Does this affect certain frequencies. It seems like the signals are affected in the US. Only UK signals?
Sent from my SPH-D710 using XDA App
Click to expand...
Click to collapse
please read this post
---------- Post added at 08:24 PM ---------- Previous post was at 08:23 PM ----------
dadsterflip said:
Would that have anything to do with the nfc chip?
Click to expand...
Click to collapse
it has nothing to do with the NFC chip or aerial

I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.

chandlerweb said:
I was able to replicate the second video demo by setting the gNexus to 2G only, wifi off and making a call from a HTC Desire a few millimetres away. I appreciate this is an uncommon scenario but others who experience it in daily use so it must be an internal radio that is affecting other parts of the internals.
Click to expand...
Click to collapse
yes, exactly - the internal radio on the Galaxy Nexus is causing the problem. that is why those of us who have been affected by this hardware defect have been so vocal about it.

vash1053 said:
Sadly no. The phone was shown to be affected even whilst in the bootloader-- a place unaffected by the OS software and everything that it contains.
Edit: Here is the video of it being affected at the bootloader: http://www.youtube.com/watch?v=y_mO_K7OYR0
Click to expand...
Click to collapse
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.

This is why I effing hate Samsung they always screw something up... Looks like the g-nex us going to be a big failure.. Hint hint goggle you should of stick with HTC to make your nexus line phones

Danrarbc said:
Does the bootloader also have a linux kernel or is it lower-level than that? If there is a kernel there is a remote possibility the issue is there. A kernel update in the OS also might make it possible to filter out the RF interference by analyzing what's going in (although that's not too likely).
Either way, the phone needs a hardware rev to improve shielding.
Click to expand...
Click to collapse
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.

oscillik said:
the bootloader is akin to a BIOS on a computer. it is very low level.
it needs a hardware fix.
Click to expand...
Click to collapse
Yeah, figured it was. And trying to work around it by analyzing radio signals to detect if it is a real button press or interference would be very hard too, they're going to have to do something about the phones already sold - this is a huge issue.

This is indeed bad. I guess this makes my decision easier about getting one from Hantec. Hopefully the Verizon version doen't have this issue since it uses different frequencies however, this may be the reason they haven't released it yet.

Nexus exchange?
The fact that Samsung have begun replying to peoples comments on their UK Facebook page asking for an email to be sent to technical support including their home address suggest they intend to replace the phone. It`s a great phone and it should never have happened but it`s how Samsung/Google deal with it.
For those who haven’t read the Facebook comment from Samsung :
Samsung UK Hi *, to ensure we investigate thoroughly could you please send the following details to [email protected]: Serial Number, IMEI number, date of purchase, place of purchase, details of issue
your name, address and phone number. We will get in touch as soon as we have more information.

T989 GPS Problems, Multiple Devices

I have two SGSII phones on T-Mobile. I just came from Sprint where I had a SGSII as well. I have had T-Mobile for 2.5 weeks and have traveled twice since then and both times were a distance of 800 miles or so. During this time I needed the GPS as expected and had countless problems.
The problems are very inconsistent and numerous to mention them all...
The generalization of it would be problems locking on to the Sats. In addition to that the GPS also has problems fully functioning when there is a Data loss. It seems to handle a loss of data differently then my Sprint SGSII did.
I am often having inaccurate locating, being off several hundred yards.
Sometimes it will lose the GPS signal altogether, and when I check the GPS app it shows 20-30 SATS visible and 0 connections etc.
With all this said again the Sprint version performs very differently, something is off. Also since I have two of these I was able to test better, and the results are almost identical. There were times that the performance was worse on one then the other as well.
Just to add, I have tried several different ROMS hoping the performance would be better with no luck. I also have tried the aGPS patch that is on here, however I believe that is more successful with the international SGSII and the ATT one.
I encourage anyone experiencing GPS issues with this phone to please post here. I also encourage any DEVS that read this or experience this issue to please check it out for us.
Thanks for taking the time out to read this or participate. Also when you post please include which color you have and roughly when you purchased the phone.

For me navigation is one of the most attractive features of a smartphone. So far my experience was very good with the T-mobile SGS SII. I am using stock firmware with removed bloatware, primarily CarrierIQ, social networks and Samsung media services.
I've found that T-mobile version can use Glonass satellites along with the US GPS giving it higher accuracy and faster lock.
Recently on my ocean trip I've used Navionics US east application in offline mode and it worked as fast and accurate as Google maps. That app is using preloaded maps without online data assistance.
In my experience Google maps worked in Europe as well as in the US.
This phone has drastically better GPS performance compare to the Samsung Vibrant.
It might be that success is dependent on a particular application because all of them do position data interpretation in its own way.
For clear comparison it might be useful to mention what apps were used for testing.

Glad I'm not the only one.
For whatever reason, the AGPS patch completely destroyed my GPS and its ability to lock to anything, so I had to hard wipe my phone after. Tried every single version the OP had in that thread.
As much as I love this phone, the HTC phones of last year had far better GPS.
Sent from my SAMSUNG-SGH-T989

The only time I EVER have GPS problems is when my phone is left on WiFi with the GPS off, or if my GPS icon doesn't start flashing when GPS is requested. Flicking GPS off then on fixes that.
If left on WiFi and GPS tries to locate me, it will never lock on.

For those that "dont have problems", how long does it take to lock and do you ever have issues where accuracy goes down for no reason?
Also if you have posted please post the color of the phone. As silly as it seems, I have heard that the white model has different issues. The only way I can think that would matter would be a batch manufacturing issue. Either way the info would help. Also a general timeframe of when you purchased the phone could help as well. Thanks!

DeeXii said:
For those that "dont have problems", how long does it take to lock and do you ever have issues where accuracy goes down for no reason?
Also if you have posted please post the color of the phone. As silly as it seems, I have heard that the white model has different issues. The only way I can think that would matter would be a batch manufacturing issue. Either way the info would help. Also a general timeframe of when you purchased the phone could help as well. Thanks!
Click to expand...
Click to collapse
Locks in under 5 secs usually to 20ft or less. with or without wifi but on Juggs 5.0 & Stock
Titanium, Sept 2011 manufacture date.
i'm really shocked to hear about GPS issues on this phone.. my GPS has been solid since day one.

AUTX_buckeye said:
Locks in under 5 secs usually to 20ft or less. with or without wifi but on Juggs 5.0 & Stock
Titanium, Sept 2011 manufacture date.
i'm really shocked to hear about GPS issues on this phone.. my GPS has been solid since day one.
Click to expand...
Click to collapse
Well that's hope for me. The Sprint one I just had was solid as I mentioned prior.

well my gps on stock had no problems, un juggs no problems, i was having problems on darkside with no locks at all, but yesterday i installed the agps patch on darkside rom and im now having locks pretty much instantly so my guess is that it might have something to do with kernel or build or something.
to be honest if your in stock i wouldnt flash the agps patch, i would only do it on a custom rom that is having gps issues.

pb3000 said:
well my gps on stock had no problems, un juggs no problems, i was having problems on darkside with no locks at all, but yesterday i installed the agps patch on darkside rom and im now having locks pretty much instantly so my guess is that it might have something to do with kernel or build or something.
to be honest if your in stock i wouldnt flash the agps patch, i would only do it on a custom rom that is having gps issues.
Click to expand...
Click to collapse
Again what color phone do you have and when did you purchase it?

DeeXii said:
Again what color phone do you have and when did you purchase it?
Click to expand...
Click to collapse
white december 23

Try going to accessory greeks and check out the wireless Bluetooth receiver they have in stock for 99.99$ it's NMEa, I have three globalsat bt-359 genuine and it was very cheap and it responds very slow on my s2 andI wind up missing turns, but it should work anywhere you get clear sky, except the Sahara and a few other treacherous Arizona and Nevada stress areas probably buying one of the ones on accessory greeks retail do a custom tailor job. Happy trails.
Sent from my SGH-T989 using xda premium

My phone is black if it can help you
In regards to how fast I can tell that it locks in 5 to 20 sec with accuracy up to 9 feet.
In my experience the best results I had with the stock T-mobile ROM.
T_mobile is also the carrier that makes use of Glonass navigation satellites, not sure that others do the same. Typically I can see more than 21 satellites of both systems.
I would suggest to look closely at the software running on your phone.
Samsung included test software allowing to check signal to noise ratio and locking speed of raw hardware. If you find SN better in the range 22-34 and reasonable lock time your phone is fine.

Try flashing this, it may help.
http://forum.xda-developers.com/showthread.php?t=1476962
Sent from my SGH-T989
Edit: nvm... I realized that you already tried this

DeeXii said:
I have two SGSII phones on T-Mobile. I just came from Sprint where I had a SGSII as well. I have had T-Mobile for 2.5 weeks and have traveled twice since then and both times were a distance of 800 miles or so. During this time I needed the GPS as expected and had countless problems.
The problems are very inconsistent and numerous to mention them all...
The generalization of it would be problems locking on to the Sats. In addition to that the GPS also has problems fully functioning when there is a Data loss. It seems to handle a loss of data differently then my Sprint SGSII did.
I am often having inaccurate locating, being off several hundred yards.
Sometimes it will lose the GPS signal altogether, and when I check the GPS app it shows 20-30 SATS visible and 0 connections etc.
With all this said again the Sprint version performs very differently, something is off. Also since I have two of these I was able to test better, and the results are almost identical. There were times that the performance was worse on one then the other as well.
Just to add, I have tried several different ROMS hoping the performance would be better with no luck. I also have tried the aGPS patch that is on here, however I believe that is more successful with the international SGSII and the ATT one.
I encourage anyone experiencing GPS issues with this phone to please post here. I also encourage any DEVS that read this or experience this issue to please check it out for us.
Thanks for taking the time out to read this or participate. Also when you post please include which color you have and roughly when you purchased the phone.
Click to expand...
Click to collapse
I have similar problems as you especially with inaccuracy and sudden loss of GPS signal In GPS Status I see, the error being as large as 150-200m in the beginning. It narrows down, gradually in a minute however its still is as large 15-30m. Sometimes its down to 3-4m from there. Sometimes it doesn't lock at all as it sees no satellite or sees them but unable to lock. It is very very unreliable as you have said.
I have Titanium version of t989 which I'm guessing is couple of months old. I got it from eBay recently. Also i'm not using any case at the moment as according to some people it limits it range.
For comparisons sake, I had HTC amaze short while back and it would lock down in 5-15secs at same place with error usually within 4-8m.
I tried aGPS patch but i don't see any improvements with it. Additionally it sometimes make the GPS act weird, like GPS status will show it locked on 1 satellite, if I open up google maps, my location had error of couple of 1000s miles, lol. I was being shown in CA (I'm in mass)
@For people having more issues with aGPS patch, no need to hard reset, it simply updates GPS.conf. You can restore your original gps.conf from my earlier post using root explorer. Its present in /systems/etc folder
First I thought it is GPS driver implementation problem with this phone but
could it be, in our phones the GPS antenna is damaged as it doesn't make any sense as most people have excellent gps performance ?

I purchased a black SGS T989 in March. I have zero GPS issues, usually lock in <5s to 4-8m. I find the spectrum of different experiences with GPS on this phone interesting, I use my phone as a daily driver (quite literally, it's my GPS too!).

Just sharing my experience, I am currently running the ICS Perfection Rom. And I was/am having GPS problems until today. I downloaded the app faster fix off of the play market and did a quick reboot>ran the app> then full restart. And now I get a pretty solid lock around 10-14 satellites.
Just sharing my 2cents. I think the problem has to do with the NTP. If that makes sense.
Sent from my ICED up Samsung Galaxy S2.

no issues on my black one, only really use GPS Status for ~2-5 min at a time , locks on to 10+ sats in ~10 sec max. While driving down highway mainly, if it makes a difference , using Darkside 2.3 and whatever kernel it came with

Guys I had similar issues with GPS until I narrowed it down by doing various experiments with different ROMs/ back to stock/ hardware etc. It turned out to be my CASE!!! I had bought this case with shiny metallic coating on the inside and it was causing the issue. With the case off I get a lock in less than 5 seconds...Hope this helps.

On AOKP M6, locks in a few seconds, accurate to between 10 to 20 meters, I've seen it as accurate to 6 meters!
Sent from AOKP Goodness :-D

I may be skewing from the main topic but hear me out. I owned an SII for about 5 months before switching to the Galaxy Nexus however still have two Tmo SGSIIs in the same household. When I had my SII I would in fact encounter the aforementioned GPS issues. They were completely sporadic which made the GPS feature highly unreliable. Spending some time with the GN I have not encountered any GPS issues, GPS locks within seconds and no loss of connection. I was curious as to why my SIIs GPS was very fickle so I did some simple, field tests if you will. They consisted of the placing of the phone in certain positions while driving for example. I found that with my SII, I had to constantly keep the phone in my hand or close to windows or the dashboard, otherwise the GPS connection would simply drop. The same if placed upside down, the accuracy radius increased dramatically ( distance-wise). However on the GN the signal remains strong in situations where the SII would lose GPS connection. To say that those affected by this issue have a hardware defect would be inconclusive but I do feel as though its not software defect.
Sent from my Galaxy Nexus using Tapatalk 2

For those with data drop issues. Read this.

Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!

this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device

Thanks for the input, can you please supply me the official Google or Samsung news that this is a bug by Samsung and we should RMA it.

gaming09 said:
this is a radio issue specific to quality control by samsung. issue has been addressed method of fix is to call in for replacement device
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=26009296#post26009296
I found your post and sorry to say but I don't buy it. Google has already stated they know about the problem with data drops, I posted the actual thread tracking the issue. I suggest that others post there too and say they have the problem. More posts = more attention. There is absolutely nothing there saying Samsung is at fault. But please, I am open to any ticket or comment from Samsung acknowledging that my phone is a lemon.

Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA

noticed the problem the first time i accessed the play pen. i have had my phone for only a few hours.

I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.

Flukester69 said:
I just spoke with a Samsung rep over their Live Chat line on their site. They have no such issue with radio's for the Nexus model. No recall and no news announcements about this issue. She said to me that they are unaware of any problems of data drop with the phone, she apologized for the problems and suggested that I contact Google about the problem. I wanted to confirm after that guy responded here about RMA'ing the phone. Did not make any sense and there are LOTS of people with the problem. It all started with 4.0.4. I imagine we will see a fix for this issue soon. Like I said, more people who post they have the issue the faster it will get resolved.
Click to expand...
Click to collapse
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.

Has anyone tried this? I will give it a go when I get off work....
Edit.sorry wrong link
http://forum.xda-developers.com/showpost.php?p=24545086&postcount=73
Sent from my Galaxy Nexus using Tapatalk 2

Smokeey said:
Qualcomm makes the radio in the Nexus. Don't see how Samsung is at fault at all.
Not to mention, Google chose it and closely monitors development.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Actually, Samsung has branded the CDMA radio, and VIA makes the LTE radio. Not sure who does the GSM one.
It might have licensed Qualcomm tech in it, but they arent Qualcomm radios.

Zepius said:
lots of people is relative. usually people with problems scream the largest, but what is the % of those people in relation to the total number of phones sold.
samsung/google are the only ones that know that magic number.
Click to expand...
Click to collapse
the problem is pretty rampant and probably more so for GSM users. I doubt Samsung can tell you how many GSM vs CDMA user there are. I don't just frequent this site, I frequent dozens of others sites and the problem is reported on all sites. That tells me MANY people are having the problem. I'd like to keep this thread on topic rather than detract from the problem at hand. Thanks.

Flukester69 said:
Go here and see the issue. http://code.google.com/p/android/is...s Owner Summary Stars&groupby=&sort=&id=28133
I don't believe this is the fault of any ROM but actually a problem with Android/Google. So post in this thread and maybe when Google wakes up one day they will fix the issue. It killed me to see they rate the issue as Medium and not critical or at least Major!
Click to expand...
Click to collapse
You know this article was addressed in IMM76I, right?

adrynalyne said:
You know this article was addressed in IMM76I, right?
Click to expand...
Click to collapse
All I know that I'm on 76I and still getting massive signal drops. Very frustrating. Tried dozens of different ROMS, kernels, radios, clock speeds, etc.
Sent from my Galaxy Nexus using XDA

What if you go back to 4.0.2?

Have the same issue as those that are complaining about the data drop issue.
1, after upgraded to stock 4.0.4, the reported issue starts happening.
2, I tried custom ROM, AOKP. Same issue.
3, I reverted back to 4.0.2 stock. The issue does not persist.
4, I upgraded back to 4.0.4 stock. The issue exist.
5, I flashed AOKP again and installed GetRIL from Google Play. Downgraded the RIL to 4.0.3. Issue seems to be resolved.
For about a month now, I haven't noticed data drop issue. Seems to be a valid workaround for the time being until Google fix the bug.
I'm on:
- GNex Maguro Yakuju, UK version.
- T-Mobile US
- LA area
Hope this helps.

adrynalyne said:
What if you go back to 4.0.2?
Click to expand...
Click to collapse
Its to my belief that prior versions whether it be 4.0.2 or .3 does not have this issue. I think its mainly the fact that we no longer cannot change our settings under the *#*#4636#*#* to GSM auto from WCDMA which I believe is partly at fault here.
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA

chlehqls said:
Correct me if I'm wrong. I really want to be able to change it to GSM auto since it still forces HSPA+ even in bad signal areas instead of reverting to edge.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal

Wow, a lot of people posted in that thread. I wonder if Google even reads that stuff or even cares.

I've suffered data drops since 4.0.1... tried lots of roms and kernels, but it keeps happening. GSM, Orange network, Madrid.
Sent from my Galaxy Nexus using XDA

gbalerdi said:
I believe it's the opposite> GSM auto will revert to EDGE sooner. WCDMA preferred will try to stick to 3G even with very low signal
Click to expand...
Click to collapse
Yeah that's what I meant, my sentence came out wrong since I was rapidly typing on the phone. Where I commute, I have pockets of low HSPA+ signals and currently it refuses to go to edge because of the changes on 4.0.4..
Sent from my Galaxy Nexus using XDA

[Q] Signal Booster

I live in a "dead zone" in a valley. The k3 modem works the best but in my basement there is almost no chance for signal. Is there a script that could be written to boost my signal strength wen necessary? In an ideal world with a toggle. I'm usually charging in this area so battery isn't a concern. I need to study tasker or similar I think for that type of option. Forgive me if that is the wrong idea. I use KT kernel and don't understand all of ktweaker settings and there is so many. I don't know if one will control this option. Ive seen threads about antenna and hardware to install I just didn't know if more power directed toward signal would help. Thanks for any input.

Bubba Fett said:
I live in a "dead zone" in a valley. The k3 modem works the best but in my basement there is almost no chance for signal. Is there a script that could be written to boost my signal strength wen necessary? In an ideal world with a toggle. I'm usually charging in this area so battery isn't a concern. I need to study tasker or similar I think for that type of option. Forgive me if that is the wrong idea. I use KT kernel and don't understand all of ktweaker settings and there is so many. I don't know if one will control this option. Ive seen threads about antenna and hardware to install I just didn't know if more power directed toward signal would help. Thanks for any input.
Click to expand...
Click to collapse
hmmm.. not sure about codes that can boost strength. If there is, please sticky this.. haha
I live in a dead zone as well. There are a few solutions (costing lots of course)
You can look into a device called zboost. Google it and see if its right for you or not.
Hope this helps!

Bubba Fett said:
I live in a "dead zone" in a valley. The k3 modem works the best but in my basement there is almost no chance for signal. Is there a script that could be written to boost my signal strength wen necessary? In an ideal world with a toggle. I'm usually charging in this area so battery isn't a concern. I need to study tasker or similar I think for that type of option. Forgive me if that is the wrong idea. I use KT kernel and don't understand all of ktweaker settings and there is so many. I don't know if one will control this option. Ive seen threads about antenna and hardware to install I just didn't know if more power directed toward signal would help. Thanks for any input.
Click to expand...
Click to collapse
Signal isn't fixed by code. Its fixed by your provider putting up more towers. Only thing you can fix is the signal picture to make it show more bars when you actually have little to no picture. But that would just be a false read and you would still have no signal.
Sent from my SGH-I747 using xda premium

Cell phones are optimized based on how much "power" they can utilize to search for a signal, and how much they should be use after a lock and sustained signal has been established. The more the power phone uses, the more hotter it would become, and the more radiation it would emit.
This is what you see as SAR rating on your phone.
The max power used is normally limited at hardware level too (to the best of my knowledge).
Just giving my 2 cents here

Thanks guys. I was hopeful. Att is the ONLY carrier that will even kinda work. Not like I like I live in the boonies either. Maybe they will add a tower someday. Thanks again.

I had to purchase a 5W booster to fix my issues (my provider paid for it or else i could cancel my contract)

Need some info regarding WiFi on Nougat 7.1

Hey people.
I was thinking of buying a second hand Nexus 5X.
Found and offer with the 16GB version, tempered glass, Dbrand case and full accessories.
The seller says it is running Android 7.1.1 and WiFi doesn't work (it turns on, but doesn't find networks) due to driver problems.
Before committing to anything I'd like to know if this problem is actually real, and not just a hardware issue on that particular device, and if there is any workaround or fix yet.
I'm gonna put a custom ROM on it anyway, but I wanna be sure that this issue won't cause problems across ROMs.

Pwnycorn said:
Hey people.
I was thinking of buying a second hand Nexus 5X.
Found and offer with the 16GB version, tempered glass, Dbrand case and full accessories.
The seller says it is running Android 7.1.1 and WiFi doesn't work (it turns on, but doesn't find networks) due to driver problems.
Before committing to anything I'd like to know if this problem is actually real, and not just a hardware issue on that particular device, and if there is any workaround or fix yet.
I'm gonna put a custom ROM on it anyway, but I wanna be sure that this issue won't cause problems across ROMs.
Click to expand...
Click to collapse
I guess this is a hardware issue specific to that device. Do you know if this was tested on different routers, i.e. work WiFi vs. publicly accessible college WiFi vs. home WiFi? I haven't noticed widespread WiFi reports on our forum. On Nougat 7.0+, some people initially had issues with specific WiFi. On Marshmallow 6.0, it helped to enable "Legacy DHCP" in Developer Options however this has been removed in Nougat 7.0+.
FYI, make sure the seller removes their account while booted in Android prior to performing a factory reset. Android 6.0+ introduced Factory Reset Protection which requires signing into the previous account on the phone if a factory reset is performed while still signed into that account. Failure to do so means you will be locked out of the device upon arrival and people have already fallen victim to this. There is no help provided on XDA to circumvent this security feature built into Android 6.0 and newer.
Sent from my Nexus 5X using Tapatalk

SlimSnoopOS said:
I guess this is a hardware issue specific to that device. Do you know if this was tested on different routers, i.e. work WiFi vs. publicly accessible college WiFi vs. home WiFi? I haven't noticed widespread WiFi reports on our forum. On Nougat 7.0+, some people initially had issues with specific WiFi. On Marshmallow 6.0, it helped to enable "Legacy DHCP" in Developer Options however this has been removed in Nougat 7.0+.
FYI, make sure the seller removes their account while booted in Android prior to performing a factory reset. Android 6.0+ introduced Factory Reset Protection which requires signing into the previous account on the phone if a factory reset is performed while still signed into that account. Failure to do so means you will be locked out of the device upon arrival and people have already fallen victim to this. There is no help provided on XDA to circumvent this security feature built into Android 6.0 and newer.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
There isn't much info in his description of the device and I have not talked to him yet.
He mentioned looking through the Google support forums. So I assume that's how he figured it must be software problem.
But I'm starting have second thoughts on this. The reason being the various reports of 5Xs going into bootloops due to some hardware issue.
Thanks for the reply.

OP, why not (and, you should) ask the seller/previous owner to factory restore or clean flash a stock ROM, whether it's 6.x or 7.x - assuming s/he knew what to do/done it - assumed it's out of warranty too ??
If that's all in working order, WiFi should not be an issue - you can then root and/or unlock the bootloader, etc. and choose your own OEM or custom Rom.
Running PureNexus on Nougat 7.0 (security level to Nov. 2016) on mine and I don't have any WiFi issues whatsoever.
Good luck but it doesn't feel right - keep looking, no matter how attractive the price/bundle can be. Is this seller a local source, eBay and have you look at Swappa offering for competitive comparison ?

WiFi works on the 7.1 beta.

Fcks work
7.1.1 work for some days
It's not hardware is software
Sent from my Nexus 5X using XDA-Developers mobile app

FYI:
WiFi of my Nexus 5X does not work on stock 7.1.1 rom.
But it works on stock 6.0.1 rom.

I haven't noticed any Wi-Fi problems on 7.1.1. But bear in mind Wi-Fi is a very tricky technology, there's literally tens of external factors which make Wi-Fi association and signal quality vary. Also, Android switches the Wi-Fi antenna to various (power saving) modes depending on battery level etc.
Not to mention some really stupid "problems" like the seller is an inexperienced person who doesn't know how to setup a router or that he could be testing it in, say, Facebook app which just happened to be unresponsive.