When Samsung service replaced my faulty screen, they introduced a new problem: from time to time, usually in the morning after the phone wasn't in use, I get lots of phantom presses on my menu button. The phone is unusable during this time. It will go away after a while, but sometimes it takes more than 10 minutes for the phantom presses to stop.
To make things worse, they upgraded my phone to knox-enabled bootloader, so I cannot return it again, because I already tripped my knox flag.
Has anyone had to deal with these phantom presses on their own? Is it likely to require a part replacement, or more like cleaning a contact under the screen?
I have never heard about this problem but maybe there's a program to disable the buttons, like miui has. (i know there's a program for remapping, so you may want to disable the button completely).
And i think you can actually get the knox stock status by downgrading to 4.1.2 and then officially upgrading to 4.3.
Sent from galaxy n7105
XDA sucks said:
I have never heard about this problem but maybe there's a program to disable the buttons, like miui has. (i know there's a program for remapping, so you may want to disable the button completely).
And i think you can actually get the knox stock status by downgrading to 4.1.2 and then officially upgrading to 4.3.
Sent from galaxy n7105
Click to expand...
Click to collapse
No. . His Knox is already tripped. . Even otherwise You cannot downgrade once in Knox bootloader mj9 and above to any version less than 4.3 without tripping Knox
And you have a weird username
Sent from my GT-N7100 using Tapatalk 2
Yeah, the username is so because they have already blocked 2 of my other accounts.
And about knox, I always hear people complaining that they can't downgrade to older rom, however I've never had that problem.
Maybe it's because I flashed custom 4.3 rom (knox free) on the beginning and then downgraded to 4.1.2
However I've found some deknoxing tool he may try to use and then he could try to get back to 4.1.2. (never used it myself)
Sent from galaxy n7105
That's because all the de knoxed 4.3 roms have mj5 or lower bootloader
Sent from my GT-N7100 using Tapatalk 2
Related
For the past 4 days my Note 2 has randomly rebooted at least once a day. I wasn't using the device for most of the reboots and just noticed that it rebooted because of battery drops. I don't really know what could be the cause since I don't remember changing anything recently. Is there any way I can diagnose this without root?
How about just flash stock rom? If you dont have lots of apps which you've used, then it should take care of problem without needing titanium backup which needs root. Just save ur data using kies and flash stock rom from sammy.
badbadtz.carlo said:
How about just flash stock rom? If you dont have lots of apps which you've used, then it should take care of problem without needing titanium backup which needs root. Just save ur data using kies and flash stock rom from sammy.
Click to expand...
Click to collapse
I'm actually currently on stock and unrooted. I was just wondering if there were ways to find out what caused the reboot such as logs and such? Or if there was an app I could install to keep track of what causes a forced reboot?
cesss said:
I'm actually currently on stock and unrooted. I was just wondering if there were ways to find out what caused the reboot such as logs and such? Or if there was an app I could install to keep track of what causes a forced reboot?
Click to expand...
Click to collapse
You could download alogcat from the marketplace, its free and will save a log of what's going on with your phone.
It might help find out why its happening
for me it happens cause the power button is so easy to press while phone is in pocket.
keep it pressed for some seconds by accident and phone reboots. even if screen is locked.
cesss said:
For the past 4 days my Note 2 has randomly rebooted at least once a day. I wasn't using the device for most of the reboots and just noticed that it rebooted because of battery drops. I don't really know what could be the cause since I don't remember changing anything recently. Is there any way I can diagnose this without root?
Click to expand...
Click to collapse
If your rooted run a logcat and that will tell you what happened right before the reboot, reboots are usually a Kernel Panic meaning something caused a big enough problem that it couldn't be recovered and crashed the core of Androids software "The Kernel".
As others have noted flashing a stock rom ideally via ODIN and then testing your phone may let you know if you had bad software or a hardware issue. Custom roms can have bugs that will cause kernel panic a stock rom should be 100% fine and reboot free
I find mine will sometimes reboot after copying something to the clipboard.
Sent from my GT-N7100 using xda premium
I had reboots on my previous unrooted HTC EVO. The problem was an app. I was able to diagnose the problem by looking at my install/update log. Basically, I uninstalled all apps back to the date I knew it was stable and waited to verify it was stable. Then added back one app only and waited. Repeat. About a week later, I added an app that caused a reboot within hours. I uninstalled it and the phone remained stable.
Here's where I found a chronological listing. If you have multiple devices, it will show all apps for all devices (tablets, vizio, phones,etc)
Google Play> My Android Apps> at the bottom My Orders & Settings.
This gives you a cronilogical listing of app installs and updates.
Mine turned out to be a call recorder app that I had put on the phone 4 weeks previous.
Seems like a Samsung issue:
http://androidforums.com/samsung-ga...-s3-crashing-when-copying-text-clipboard.html
I've got the same problem worth my note 2. At least I know I'm not alone.
Sent from my Galaxy Note 2 using Tapatalk 2
Bad SD cards are also a notorious source for spontaneous reboots. If you have one inserted, it should be easy enough to retract it for a while to test it. ..
Note'd too from my N7100...
I'm also experiencing this issue. I'm using 4.1.1 Brazilian stock ROM here.
Even before flashing CWM (yesterday) I as going through this problem. Most times it happens when the screen is off.
Maybe changing the stock Kernel to a custom one would solve this?
Upgraded to rooted [stock] MD4, and i would get times when my [stock] lock screen would not let me unlock, as if touch screen was not working.
I did a hard reset and still seem to be experiencing the issue. I can hold home to get past the lock screen but even when unlocked, touch screen wont work. A soft reset seems to resolve it so far, but I was wondering if its hardware or software. I am running stock, other than being rooted and the trouble only started when i upgraded to MD4. Never had any issues with any prior version.
A soft reset might solve the problem for a few minutes, then it happens again. I might just try downgrading my software :/
Is anyone else experiencing this issue?
m4zt3r said:
Upgraded to rooted [stock] MD4, and i would get times when my [stock] lock screen would not let me unlock, as if touch screen was not working.
I did a hard reset and still seem to be experiencing the issue. I can hold home to get past the lock screen but even when unlocked, touch screen wont work. A soft reset seems to resolve it so far, but I was wondering if its hardware or software. I am running stock, other than being rooted and the trouble only started when i upgraded to MD4. Never had any issues with any prior version.
A soft reset might solve the problem for a few minutes, then it happens again. I might just try downgrading my software :/
Is anyone else experiencing this issue?
Click to expand...
Click to collapse
Upgrading your software isn't going to make your touchscreen not work. Sounds more like a software issue.
Sent from my SPH-L710 using Tapatalk 2
You're right, but its weird because it only started when i upgraded to MD4, as if the software is causing touch screen issues. I guess I will re ODIN MD4 tonight and see if that helps, and if not ODIN a software downgrade and see if I am still experiencing the issue. So frustrating.
m4zt3r said:
You're right, but its weird because it only started when i upgraded to MD4, as if the software is causing touch screen issues. I guess I will re ODIN MD4 tonight and see if that helps, and if not ODIN a software downgrade and see if I am still experiencing the issue. So frustrating.
Click to expand...
Click to collapse
Not unless a bad download.. But still seems strange. If problem persist I'd take it up to sprint.
What happened to my GS3 is the LCD went out totally.
Sent from my SPH-L710 using Tapatalk 2
cbass15 said:
Upgrading your software isn't going to make your touchscreen not work. Sounds more like a software issue.
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Sometimes it can. Every now and again I will go to lock screen and it won't respond, but a click of the screen off and on fixes it. Not a big deal and happens MAYBE every few weeks.
----------------------------
Sprint Galaxy S3
Whiplashh ROM
Or using CM10, MIUI, OR Stock. Depends on the day.
Check it out. :trooper:
Whiplashh said:
Sometimes it can. Every now and again I will go to lock screen and it won't respond, but a click of the screen off and on fixes it. Not a big deal and happens MAYBE every few weeks.
----------------------------
Sprint Galaxy S3
Whiplashh ROM
Or using CM10, MIUI, OR Stock. Depends on the day.
Check it out. :trooper:
Click to expand...
Click to collapse
That's just a freeze up in the system. Not exactly a software issue.
Sent from my SPH-L710 using Tapatalk 2
Hey guys. I moved up from a Verizon Note 2 to a T-Mobile Note 3 two weeks ago (and switched carriers obviously).
Since then, it has happened that the phone gets stuck and then reboots.
Three times it's happened while scrolling in the 9Gag app, once while in the Play Store and once as I was unlocking the phone using a pattern an e-mail came in and the vibration got stuck for a while and then rebooted.
I've also noticed that if I have WiFi on, Skype logs in fine, if I leave the house so I go on 4G and then come back to WiFi, Skype refuses to see a connection unless I turn off WiFi or reboot the phone.
Then yesterday the entire phone was in landscape mode even though I had auto-rotate enabled, and whether I turned it off and back on, it stayed on landscape mode until I rebooted the phone.
My wife also has a T-Mobile Note 3, bought at the same time. For her it's rebooted only once so far while using Google Maps.
I've had S3, Sprint Note 2, Verizon Note 2, and my wife has had S3 and S4. Now we both got these Note 3s and man, this is way too glitchy. On the Note 2 I went over 2 months once without rebooting the phone. This one has rebooted itself 5-6 times in 2 weeks!
We're updated to KitKat 4.4.2 (OTA) and not rooted or modified in any way (yet). So I'm wondering if it's KitKat that is glitchy, since our phones before weren't on KitKat, or the Note 3s in general, or just my specific Note 3.
Would love any info on this. Thanks.
I would do a master reset. Worst case Odin stock rom. Avoid send in for refurbished one
Def don't root yet. Try and get phone stable first.
TWEAKED N3
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
EDIT: if you don't mind me doing the noob thing and just asking, what's the easiest way to get root? I don't particularly care about a customized rom, but definitely want system access to get rid of all this bloat and install my customized video ringtone program.
Max_Pain said:
If i'm going to wipe, I might as well root. I've rooted and modded all my devices to date. Just when I got to the Note 3 it seemed that things had become considerably harder than on the Note 2...so I chickened out.
Click to expand...
Click to collapse
It not harder it more steps and Odin is best. But if you have hardware issues on stock u need to know before root
TWEAKED N3
Yeah, doing it now. Going to go stock but rooted so I can have some control. Maybe later on i'll flash a custom rom when I have time to go through them and see which one suits my style.
Thanks.
I'd suggest doing a factory reset b4 anything, then if that dose not work, use odin and flash kit kat... then if ur issue persist, maybe contact samsung.
Sent from my SM-N900T using XDA Premium 4 mobile app
---------- Post added at 05:57 PM ---------- Previous post was at 05:56 PM ----------
Also one u have root, go to the play store and check out greenify. I swear by it. C:
Sent from my SM-N900T using XDA Premium 4 mobile app
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
Hibernating battery hogging apps and their associated services when they aren't being used.
Sent from my SM-N900T using Tapatalk
Max_Pain said:
I'm already rooted on stock deodex. Let's see how it goes.
What's Greenify for?
Click to expand...
Click to collapse
I be honest I don't use it and this kk really doesn't drain the battery like job did stock
TWEAKED N3
I haven't noticed any sort of glitches since I've had my N3. Even after putting the jedi ROM on it seems fine. As far as the battery goes, I know there are alot of complaints that kk has killed alot of the life out of it. I haven't noticed a difference in battery life either. It holds a charge all day and some. And greenify is to stop or freeze certain apps that run constantly in the background that could drain the battery. I personally didn't really like the app nor did I need it.
Sent from my SM-N900T using Tapatalk
Well, I went on a stock deodexed rom and got on lean kernel for a while... but it's still doing the stuck-and-reboot thing. It's always related to the touch screen, so i'm either scrolling or clicking to open an app or settings within an app. The phone gets momentarily stuck, then full reboot.
How long do I have to get it exchanged in store? I wonder if i'm within that time frame. It's definitely not normal and getting very annoying.
If i'm outside the time to get exchanged in store, what's my next best option?
I have to say that this experience with the Note III has been nothing short of disappointing and nothing like the two Note IIs I had before (different carriers for each, neither broke or gave any problems).
Here's an update for anyone who finds this and is in the same boat.
I had two issues: 1) the power button became so recessed that it's a hassle to turn on/off the screen, 2) the phone kept turning on and off, by the end almost constantly, without any obvious pattern beyond it getting stuck after me touching the screen (i.e. never just up and turned off while being idle).
Because of the recessed power button, T-Mobile shipped me a replacement phone. Should arrive tomorrow.
I still tried troubleshooting the rebooting issue. I think it came down to one or a couple of the following:
1 - Go Weather EX
2 - Freeza's CRT mod
3 - flashable 1% battery mod
4 - bootanimation.zip support flashable script
5 - something in the Deodexed version of the stock KitKat rom
In prepping to take the phone to T-Mobile, I did the return to stock thing with Odin, putting back stock kitkat odex non-rooted rom. The entire afternoon I got not a single reboot. Since I came back home with the phone, I restored a backup I had made before doing the Odin stuff. Back to rebooting.
So I thought, let's go back to the stock experience like I had earlier, and restore my apps through the play store and manually hunt it down.
Now i'm running the stock odexed kitkat rom, rooted, with lean kernel, with a whole bunch of stock apps frozen, and virtually all my apps and not a problem. I avoided 2-4 since those mess with the framework and I thought it could have something to do with it. I removed Go Weather EX because I experienced a reboot once while setting it up as a live wallpaper.
When the new phone arrives tomorrow I'll try to duplicate my current setup and hopefully won't have any more rebooting issues. I hope this helps anyone experiencing the same thing. I know it's kinda convoluted and not very concise, but then again this experience has been nothing short of annoying and confusing.
So i received a new phone in the mail from tmobile because i claimed that my last phone was lost. They sent me a Galaxy s4 with 4.3 pre installed (sadly) and I didn't care about tripping knox so i rooted and installed an i9505 rom. Now when i was on stock before i rooted i would get signal problems at my home unlike on my previous galaxy s4. Text messages wouldn't go through nor mms and sometimes i wouldn't have a data signal. But now i realize there are a lot of things wrong with this phone :
Vibration on the phone does not work at all nor keypad vibrations
The speaker where you place your ear for a call has a lot of static when on the phone and the volume is low even on max and with volume mods
the back facing speaker is low even with volume mods on high
the continuos bad reception it has
notifications that the sim card has been removed when it has not
So what I'm trying to ask is if i reflash stock 4.3 on it and set the flash counter back to 0 with triangle away, can i call customer service complain that the phone has all these problems and that knox was already broken when sent to me so I can get another galaxy s4 sent to me?
Just reflash 4.3 and see if it helps or even 4.4.2, Knox is already tripped.. And you don't have to reset anything because you can't reset the counter, and they won't ask you about the counter, all you can do is file a claim and hope they won't say anything about it
Sent from my SGH-M919 using Tapatalk
Did you flash a kernel?
Sent from my SGH-M919 using XDA Premium 4 mobile app
Tyler.Boston1 said:
...
Vibration on the phone does not work at all nor keypad vibrations
The speaker where you place your ear for a call has a lot of static when on the phone and the volume is low even on max and with volume mods
the back facing speaker is low even with volume mods on high
the continuos bad reception it has
notifications that the sim card has been removed when it has not
...
Click to expand...
Click to collapse
Reset flash counter using triangle away. Reflash 4.3 tar. Go into store and b*tch!
Don't ever mention knox. A lot of store reps have no idea what that even is or what even a bootloader is. As long as you can re-create the issues you mentioned at the store. They will gladly give you another one. Took me 3 Galaxy S3s referbished to finally get a good working one.
I've been getting these glitches/artifacts/tearing on any 4.4+ rom on my T-mobile S3.
It's like the status bar will glitch down to the bottom of the screen.
I'm currently on a 4.3 stock rom (ENC2), It's been rooted with the samsung toolkit and has knox disabled (at least according to the app).
I've tried most current d2lte roms, PA, spirit, ACIP...ect.) and they all have it.
I know for a fact I'm missing something. I just can't remember what it is for the life of me. I know it has something to do with the bootloader/binary. I seem to remember when 4.4.1 came out there was something with the bootloader we had to do and no matter what I search nothing is coming up with the correct solution.
I'm hoping someone could tell me what i'm missing because it seems painfully obvious and I'm missing it, . I really don't enjoy using TW.
We don't ever mess with the bootloader or other parts of the base firmware, so maybe you're thinking of a different device?
When did it start? What was the last thing you did (flash)? Tbh, to me it sounds like a hardware problem. Maybe a connector got loosened, or some moisture/water damage, or even heat damage could cause what you are describing. Especially if its happening on every ROM.
Flash the stock NC2 firmware via Odin and factory reset. If it still happens after that its almost certainly hardware related.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
Does it also happen with touchwiz?
So. I ran the knox removal thing from the samsung toolkit and now I don't see them on the latest CM nightly.
I have to test a few other roms but I don't know, it's somehow fixed, thank you for the responses.
Glad to hear it. Be careful with the toolkit though. It is not supported and has bricked devices.
Sent from my SAMSUNG-SGH-T999 using Tapatalk
After giving it a few days the issue came back.
I've tested this on a stock nc2 touchwiz as well as your (doc) latest likewise release with no issues with the screen or anything.
For the non touchwiz I tried aicp latest 4.4.4, the latest cm11, the latest aospa weekly and a 4.3 AOKP release (milestone2).
The glitch issue wasnt in the cm release for a day or so then showed up, all others showed up instantly.
I also emergency recovered via kies. Then rerooted. I'm also using the latest twrp
Here is a logcat of the ROM I'm currently on, the 4.3 AOKP. I wish I had more of an understanding of logcats so i knew if I posted the right section.
http://pastebin.com/UyZFHriB
I was curious so I booted up a nandroid of aicp and then restored a backup of the boot from likewise. Results were minimal glitching but no connectivity at all. APNs didn't load and WiFi is broken. I'll post a video shortly of the screen.
The only thing that jumps out on that logcat is where you have this kind repeated several times in a row:
09-18 13:35:38.752 W/ActivityManager( *761): Permission denied: checkComponentPermission() owningUid=10060
But I honestly don't know what its referring to. But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue. Display problems usually are to begin with, but almost any problem that persists across multiple ROMs and wipes can usually be blamed on a hardware malfunction.
Watch a disassembly video on youtube, then open it up and reseat all connectors. (Don't mess with the antenna. Its fragile and not related to the issue at hand.)
Sent from my SAMSUNG-SGH-T999 using Tapatalk
DocHoliday77 said:
But I will say that since it appears to be happening on every rom, even stock, it sounds more like a hardware issue.
Click to expand...
Click to collapse
That's the odd thing, On both 4.3 and 4.4.2 versions of touchwiz I don't get the glitching. Only on AOSP based roms. I could just go stick with a touchwiz based rom and be done with it but my personal preference is not using touchwiz. I'm just confused as to what is actually causing this.
I'm guessing it has to have something to do with the bootloader and baseband.
I think i did forget to mention this is a "refurbished" warranty replacement, i regret that I don't recall which specific version it had as stock, I'd guess it has to be enc2?
Here is a poor quality video to show whats happening, on the home screen you see the glitching where the status bar glitches down to the bottom. I tried to get it to do what it sometimes does in both the MLB app as well as the reddit app but it decided not to be as noticeable this time.
http://youtu.be/ZsZL1Okio-A (sorry about the added music )
Just a side question, I couldn't seem to find a definitive answer, but was it ok to downgrade within the 4.3 bootloaders? I thought I remember reading that as long as you don't go from 4.3 to 4.1.2 it was fine.
Soryy I misunderstood before about it happening on stock. Have you tried any different kernels? I'd suspect that before bootloader. But since it's a refurb, there's just no telling for sure.
Once on 4.3 you cannot downgrade your firmware at all. You can flash older roms, but that's it.
Sent from my SAMSUNG-SGH-T999 using Tapatalk