Galaxy TAB A 9.7
This tablet was accidentally slightly bend in the middle, screen cracked, I replaced it and everything seemed to work as it should, except now there is almost no mobile signal - it shows crossed circle and sometimes 1 or 2 bars, and LTE doesn't work. LTE has worked, but for a few seconds then it doesn't work again, it usually might work a few seconds after restarting, but rarely when continually on.
I can't visit the secret mobile data menu (*#*463..), because it shows 'no signal', so I can't troubleshoot this in any way.
I had reinstalled OS, upgraded to newest stock android
Rechecked antenna cables, they all seem intact, the motherboard is not cracked
installed a few 4g test apps which are mostly useless crap, couldn't find any app that would show any kind of useful logs or anything like that
WiFi and GPS still works.
Is this fixable?
Related
Hi, I've seen this around a bit and just wanted a little bit more information, if any one has it.
Basically, a few weeks ago, I had a random shutdown, and had to do the 30 sec+ powerhold to boot it back up (NOT NORMAL FOR MY DEVICE USUALLY AROUND 3/5 Seconds ! )
I only knew to do that because of XDA so +1 there people !
Then, a couple of nights ago, was browsing around Chrome etc, and BOOM first CRASH EVER ! with my nexus devices, and to be honest, I thought crashes were a thing of the past/desktop laptop specific, as my HOX has never crashed. I WAS GUTTED
So I did the power thing, and it booted.
Again last night, another crash and shutdown, then 30 sec + power hold to boot again.
Basically, I want to know is this a sign of a deteriating device? Is there a known cause? Should I be worried?
Is there anything specific I could have on my tablet causing it?
I have over 10GB space still left on my 16GB device, as I'm rather a ****** when it comes to filling devices (i tend not to download much, other than REALLY useful apps TO ME ! like XDA, Flipboard and a few random games.
Any information would deeply be appreciated.
Anyone?
I had this for a while, and discovered the cause was that I'd disconnected the ground pin on my Wifi antenna in order to stop low screen brightness flicker. Removing the bit of tape stopped the reboots.
If you haven't done this mod, then I'd suggest it may be to do with weak wifi signal? Maybe the spring pins aren't making solid contact with the antenna?
adstraylight said:
I had this for a while, and discovered the cause was that I'd disconnected the ground pin on my Wifi antenna in order to stop low screen brightness flicker. Removing the bit of tape stopped the reboots.
If you haven't done this mod, then I'd suggest it may be to do with weak wifi signal? Maybe the spring pins aren't making solid contact with the antenna?
Click to expand...
Click to collapse
Nah I havent even touched my Nexus 7 in that way.
Its not been opened or tampered with
And if your being serious about a dodgey wifi antenna spring within the Nexus 7 im gonna end up killing someone, as my HOX has the Wifi antenna fault to.!!!
Can I just ask, how would a weak wifi signal cause the unit to crash and reboot?
THANKS!
It was just a thought based on my experience of effectively semi disabling the antenna, I've no specific knowledge to tie a crash to wifi signal strength, so pure conjecture.
Perhaps an intermittent connection confuses the logic and crashes the device?
adstraylight said:
It was just a thought based on my experience of effectively semi disabling the antenna, I've no specific knowledge to tie a crash to wifi signal strength, so pure conjecture.
Perhaps an intermittent connection confuses the logic and crashes the device?
Click to expand...
Click to collapse
Hi, dya know mate I've just thought of something and you could be on to something, not necessarily a weak signal, but Im sure its network based, as the second time round (cant remember what I was doing first time) I was switching between browsers, Incognito etc.(Opera/Google)
This started happening to my N7 starting a few days ago. I wasn't necessarily using Chrome but was on the Play Store updating apps or on Bacon Reader and it would crash and reboot.
I haven't opened up my N7 but have rooted.
I see this all the time
I'm seeing this on both my Nexus 7, and my Galaxy Nexus. A friend of mine is seeing it on her phone as well (I forget the model, but different than mine and also running Jellybean).
It seems to happen when I have poor wifi (e.g. the wifi meter on the N7 switches from blue to grey). The typical behavior is that some app mostly locks up. At first, the soft menu buttons still give feedback that they've been pushed, but don't do anything. The device can usually be turned off with a tap of the power button, but won't come back on again with a second tap.
After a delay, the device will display the multicolored "X" that indicates it's rebooting.
This happens 2 - 6 times per day on each of my devices right now. It's *very* frustrating.
I've been thinking of doing a factor reset to see if that helps, but haven't yet.
Any other suggestions?
Hello,
ok, I gave up on moving APPs to external SD on ICS 4.0.3...
Here is my new issue in a nutshell....
I updated to ICS 4.0.3 with no problems and everything worked fine for months. Within the last month, the tablet has developed a random problem, usually 30-90 seconds after it boots, where it may or may not freeze up (i.e. the screen is unresponsive) and I have to turn it oss and reboot and hope it doesn't happen again.
Sometimes this happens one or two times in a row and then its fine, sometimes it will happen five times or more, and then the next boot it is fine, sometimes it works fine on the first boot.
I have removed all kinds of apps and media to make sure I have lots of room and curently have about 5G free. but that didn't fix the issue.
I looked into the GPS txt files being left behind and made sure they are removed regularly, but that doesn't help the issue.
I used a Device Info APP to display what is going on when this happens, and while it doesn't show any APP or process I can see as the culprit, the CPU is being maxed at 100%?
It also seems to have "something" to do with the WiFi, as when it "locks up" the WiFi icon in the tray goes away and when I go to settings it seems stuck trying to turn off the WiFi. But at other times then the WiFi is working fine?!
Also, sometimes if I let it go to sleep for too long, when I wake it up this will happen..
SO... anyone got a clue what this could be?!
Hi all,
Having a problem here.
Had my N9005 for about 18 months, never really had any problems with it - or rather, never really required anything of it which might manifest any problems.
I've always used Stock ROM's, soft-rooted.
Never triggered KNOX.
I'm currently running Stock Lollipop (latest Switzerland Open). Everything I'm about to elaborate is also the same using Stock Lollipop (latest UK Open).
I'm rooted on Lollipop using the method compiled by The TAMAS on XDADEV.
I root because my phone is work-critical, and so I use Titanium Backup to keep my data/calls/APN/SMS backed up and to make restoring easy, as well as to disable stock bloatware etc.
The problem may have pre-existed in pre-Lollipop ROM's, but the sequence of changes which caused it to be manifested included my need to update to Lollipop, about 5/6 months back.
THE PROBLEM - First and foremost, the damn phone reboots randomly. I become aware of it because it will vibrate for startup and play the Samsung startup tone and splash screen before booting to normal functionality. It can do this day or night, maybe 3-4 times a day. I have no error messages or warnings, it's done it while in my hand, while plugged in charging, while out and about, in the car, on wifi, on data. MOST times it reboots. SOME times it just shuts off and I don't realise it's off until I go to use it, or get a call on a second phone to ask why I'm not responding to calls or messages.
When it reboots itself, if I go to the Samsung Battery control panel pane and take a look at the battery chart it will show a gap which is longer than the time it took to reboot, and a shift in the battery meter level.
But, that's not the only possible symptom or problem with the phone.
I've noticed also that my WIFI does a lot of crapping out, or slowing to a crawl, even on my home AP. I've reset AP's, reset networks, reset the phone, forgotten and then reattached the AP in WiFi Settings. So I downloaded the Ookla Speedtest App, to see this issue in black and white, and sure enough, even though any other Android or iOS or Windows or OSX device in my place can connect via Wireless AP to my fibre connection and get great consistent throughput, the Note 3 can often appear crippled...
At it's best, it responds to ping quickly on the Speedtest app, and leaps up to the 30-40Mbps range with consistency for download, and up to 17-20Mbps for upload. This is the least I would expect it to do, my target standard.
At it's worst (which can be 'most of the time') it responds slowly to ping, and either struggles to get over 250Kbps download and maybe a crazy Meg or two for upload, consistently, a slow grind; or it may oscillate extremely wildly between slow and high speeds before eventually settling to unacceptably low transfer rates.
Up to press, I've been trying to chase these problems in isolation, believing them to be unconnected.
No success.
I've reflashed several times. I've Factory Reset. I've wiped data and cache. I've reinstalled and restored from Titanium. I've reinstalled and restored nothing but my SMS's and Call Logs. I've reduced my installed apps to bare minimums. I've tried it with a MicroSD installed, and without. I've bought another battery and replaced it. I've tried it in its case and without its case.
Then I started thinking that the problems were all the same thing, and stemming from the same root.
It suddenly occurred to me that my use of the phone changed significantly at the same time as I moved to Lollipop.
I need to be on Lollipop because apps and hardware that are critical to me are Lollipop dependent.
All at the same time, I began using a Moto360, a Bluetooth Receipt Printer and a Bluetooth Credit Card Reader, all of which are deficient in functionality or in some way hamstrung by not using Lollipop.
So I had gone from occasional BT user (maybe PlayerPro plus a BT link to headphones or my stereo occasionally; when needed, BT speakerphone in car) who usually turned BT off manually to preserve battery life, to a constantly connected BT user...
So I went back to Speedtest app, and tried to test the WIFI connection again. Sure enough, it was pitiful. Then I simply disabled BT on the N9005 and ran the test again, and had full 'through the roof' speed ratings.
I've tried this back and forth hundreds of times now, and it is predictable and established. BT is somehow crippling WIFI on my N9005.
I've tried running the phone on either wifi or data only, with BT off, and had a couple of days use at a time without any restarts. Put BT back on permanently, and the restarts resume within hours.
I'll be honest, I've even been cursing and swearing at my BT devices, because BT sometimes struggles to even maintain a continuous connection. I get vibrations all the time on my Moto360 indicating that the phone, which is on my person, has disconnected from the watch again, perhaps just for moments, sometimes for minutes, resulting in the watch eating battery life, trying to get reconnected.
I'm convinced now that all these things are related, and the problem lies somewhere in the interaction between BT and WIFI in my N9005.
It seems likely that I never noticed the problem before because I never required continuous BT connection before the point where I installed Lollipop.
Downgrading the ROM isn't an option. Leaving BT off isn't an option (nor should they have to be, on an 18 month old £600 smartphone).
Does anyone else have experience of this? Has anyone else had problems that they now suspect might be this same problem? Does anyone understand what's going on hardware/software wise, or have experience of a solution to these issues?
I'd appreciate your input urgently, even if only to affirm that I need to go to the inconvenience of temporarily buying another phone to replace this, while I send this away for a warranty repair.
Is this even a recognised hardware fault, or would I just get back an identical unit which is crippled from being able to perform as I expect it?
Please help.
a lot of time i can't make calls or receive calls till restart my device, i have android 7.1.2 with Nexus 4. is there any solution for this issue
is it happen because Android version or there are other workaround to solve it
Same here. When the battery gets low or after returning from a low coverage area, the network signal randomly keeps disconnecting. On 7.1.2 lineage.
Similar issue here. The PIN screen appears at random times because of service loss. After entering the PIN the screen reappears after ~20 seconds. Sometimes it finds a connection, sometimes I can re-enter the PIN endlessly without success.
Did a wipe and installed the latest stock firmware but the issue remained, so it must be a hardware fault.
I disassembled the phone, removed the mainboard to have access and clean all contacts - especially the antenna and the ones in the SIM tray - and checked the flex cable connectors. The service is good right now and as a bonus the power button works well again. Let's see how it continues.
Title explains it all, but for some reason, my dad's note 4 has a strip along the middle of the screen where the touch screen stops working, but if the phone is powered down then back on, it's fine. The part of the screen comes back to life. What on earth could be causing that?
On a side note, it randomly looses cellular network connectivity, but connects to wifi just fine, we can't figure out what's happening with that. It'll show bars are connected, but it's unable to receive or send calls or texts for a while.
Anyone know any solutions to these problems?
some app running might be causing an issue
raul6 said:
some app running might be causing an issue
Click to expand...
Click to collapse
Boot your device into safe mode and see if it operates normally. If it does then start deleting apps from your device starting with the latest one you installed.