Hey guys!
The other day, I picked up an Atrix, mainly to use as an mp3 player so my S3's battery wouldn't drain as much during the day.
So, I took the steps any good android-user would go through. I unlocked the bootloader, rooted, and had Clockworkmod all set up.
This is within 30 minutes of having the phone. During the first while of tinkering with it, I noticed some strange things. There's really too many to list, but I'll try.
The phone at times is completely unresponsive. At seemingly random intervals, the Atrix would freeze, and randomly start selecting things.
For example, whilst using the keyboard, it would stream out random lines of text, like yyyyzzyyzyyzyyzyyyxyyxyyzy. Thinking that it was just a fluke with the rom , I carried on.
Often, the only time I can accurately and reliably select something is immediately after turning the screen off and back on again. And sometimes, that doesn't work either.
Also, there seems to be a 4-5 second latency from pressing the screen, to the device registering it.
Again, at random intervals, the image displayed on the screen begins to shake, and becomes unresponsive. I really wish I could record it happening.
There's also a host of other problems. The wifi hasn't ever worked, and the phone flat out refuses to flash some gapps packages.
So, my Atrix is basically a non-functioning, shivering, nightmare of a phone to work with. None of these issues have been caused by flashing different roms, and I have never touched any of the sbf files.
No matter what I try, it is just unusable. Every thing I have tried has failed, and this phone is out of warranty, so replacement is out of the question. So, is there anything I can do to fix this issue? I really, really need help.
Thanks in advance guys!!
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Newbleeto said:
I think we need to know what ROM (ROMS?) you are using. Is the bug recurrent? Have you thoroughly wiped cache, dalvik and did a factory reset before flashing? Are you sure you are flashing the proper Google apps for the ROM you are trying to use? And finally, are you sure your bootloader is unlocked? Does it say unlocked when booting and can you get to clockwork mod?
Those problems might be hardware, but I've experienced some of them myself from bad flashes, or corrupt pds partition, so software is far more likely. Give a little more info and I'll try to help.
Also, does Bluetooth work?
And what do you mean " refuses to flash"? What happens?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Hey! Well, I started on the stock ota 2.3.6
Yes, the bootloader is unlocked, cwm is the recovery, and I can get into it. Before flashing, I did wipe dalvik, cache, and factory reset.
The roms I've installed are in this order:
Stock ota 2.3.6, Cyanogenmod 7 2013/1/1 nightly, TopSmart's final release 1.3 rom, and AOKP 4.1.2 from October 17.
The roms flash just fine,and I always use the correct gapps. The problems have persisted through everything I have tried.
Bluetooth does not work, and neither does anything that requires a radio. (Data, calls, wifi, etc)
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
affiatic said:
Is this a new or used atrix. if it was bought used perhaps has a hardware problem that the seller neglected to tell you about
Click to expand...
Click to collapse
I got it used, but it was still in the box, and even had the plastic screen that says "Don't text and drive" on it. The phone had literally never been booted up.
I think I figured out the problem, and will try to post a video of it.
The touchscreen just freaks out when being used. I found this out through the pointer location in the dev tools in Cyanogenmod 7
I'm on cm10 and random touches happen to me. I just lock and unlock the screen to fix. Only happens to me on cyanogen roms.
Sent using tapatalk
Could it be a foreign phone? that would explain the radio not working. The screen breaking and ghost touches sound like the leaked rom/kernel, was it happening with all the roms you installed?
Related
Hi guys,
Lately I've been having problems with the WiFi and BT.
I know it has been like that for a while but I only noticed it yesterday.
The BT on the phone doesnt work - when I try to turn in on it just doesnt... I press the button and it stays the same way.
The WiFi doesnt work - when I try turning it on it says ERROR. and stays like that... not on and not of.
And not only that, another thing is that my phone started crushing A LOT.
I have no idea what's going on... it can crash at any moment without worning... not always coming back (sometimes I have to pull the battery out).
it can happen after 1 minute or after 3 hours...
the 2 things that changed on the phone lately are:
1. swiched from neutrino 2.8EE to 2.9EE.
2. I was in a vecation and when I tried to charge the battery it got only upto 82%. didn't cross it no matter how long it was in...(it was like that for a week).
I have to phone for like a year and a half.
help? anybody?
This is a known problem and it's been reported countless times already. Unfortunately the most likely reason is that your wifi/bt chip is fried. This is a hardware issue (more specifically, a design flaw) and there is no workaround. It has affected many others and they are just as pissed off about it as I'm sure you are. Some even say all Atrixes will sooner or later end up this way because of this design flaw.
Not sure about the crashing, but it could be related to broken wifi/bt.
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
rain91x said:
Hi
I have same problem. I have Atrix 4G from UK Tmobile, with stock froyo. I flashed the stock 2.3.4 with RSD successfully, and i unl*cked the carrier.
Then i noticed, that Wifi don't work good. I don't know turn on: Wifi (error). The other problem, that the finger print scanner isnt work...
These actions do not help: factory reset, unlock BL, custom ROM (i tested Nottachtrix, any ICS ROM, stock froyo), erase all at fastboot, full wipe with CWM...
I am sure, that it is a software bug! (before flash 2.3.4 and carrier unlck, phone works fine...)
Some solutions? (I think, if we restore back to stock, the problem is solve) How can i make a fully reset, which is stronger than RSD flash stock sbf?
edit: http://forum.xda-developers.com/showthread.php?p=13754274#post13754274
or
http://forum.xda-developers.com/showthread.php?t=1035139
Click to expand...
Click to collapse
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Alonleibo said:
looks promising... did you try it?
I donnot if I can even try it... the first step is "close WiFi"... and I can't. it doesnt go off and doesnt go on... just stays on "Error".
should I just except the fact that I have to get a new phone?
should I send it to Motorola?
Click to expand...
Click to collapse
I try it later, but i dont know now SD card. I hope, that it is a correctable bug.
edit: i tryd it, but still not good. Other solutions?
I have the same problem (wifi error, bt does not open). I guess it is a hardware problem but when I installed TopSmart rom (coming from Neutrino) they worked for 10 minutes then they crashed again. If it is a software problem (but i dont think so) there must be the answer that everyone's looking for. I hope it ends up as a software problem.
Sent from my Motorola Atrix 4G
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
It is frequent bug on Android phones. (wifi - error)
https://www.google.hu/#hl=hu&gs_nf=1&tok=EBl1OHx7E49rfa9s8zPj_A&cp=13&gs_id=1f&xhr=t&q=android+wifi+error&pf=p&output=search&sclient=psy-ab&oq=android+wifi+&gs_l=&pbx=1&bav=on.2,or.r_gc.r_pw.r_cp.r_qf.&fp=aee7b1a090091e6a&biw=1680&bih=949
MdX MaxX said:
It's most certainly a hardware problem. Clearly the WiFi chip in this phone just dies. This is also why your phone is crashing. You'll just have to leave WiFi off (if you can get to the switch before the phone crashes).
This issue started a couple months ago for me, and today I managed to accidentally flip the WiFi switch on again, sending my phone into an endless cycle of crashing and rebooting. I had to factory reset and re-flash CM10 about three times just to get it to stop rebooting repeatedly (which sucks because I didn't have a recent TiBu backup...). You might have to do this as well if your phone doesn't stop crashing.
I'd say just get a new phone. Don't send it in to Moto because even if you're in warranty they'll likely send you back a unit with a permanently locked bootloader, which isn't worth it.
Click to expand...
Click to collapse
I did turn it off... eventually.
but my phone still crashes... at the same frequency...
*added alogcat files of 2 of the crashes... if anybody can understand it...
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Well, assuming you did complete wipes and factory resets as you flashed each Rom, I'd say you eliminated software.
Did you leave the phone somewhere that let it overheat? Or used a non-OEM charger? Or overclocked it?
majicmazo said:
Well, I was running rootbox for i717 and everything was working fine for a month, Then suddenly out of no where for no reason at all my phone got super laggy, apps started crashing, and my sound stopped working, I mean completely not through the headset not through the speaker nothing!!! So my first thought was something was wrong with the rom, so I tried a factory data reset, I tried re-installing it, I tried 3 other roms, cynagenmod10, Jellybeer and xylon, Finally I did the farthest restore to my stock gingerbread rom, and still the problem priests, in fact its getting worse, I don't know what to do at this point I am completely out of ideas. Could this be a hardware issue? its the only conclusion I can come up with, but its still strange, because if it was just my speaker I would understand hardware issue, but my speaker, my earpiece, my headset, and Apps crashing, super Lag, I can barley even get my keyboard to pop-up then it dispersers. What is going on!!! Please help me oh great devs.
Click to expand...
Click to collapse
Your best bet is to go to RootzWiki where the dev work is done for those ROMs .. And post this in the threads... I myself am running root box .... Go there .. XDA doesn't support these roms anymore so that's where you need to go
Sent from my SGH-I717 using xda app-developers app
did you do the 3 wipe procedures when installing the firmware?
there is more than just 3 wipes you can do .....depending on a dirty flash or a clean install or a complete wipe and clean install...you also have android secure ...internal ....external
Sorry for the delayed response
Well, yes I did always do the 3 wipe method, I did the complete wipe as well, and I saw no need to talk to the rootbox dev, (whos name im terrified of mentioning on xda in fear of getting banned lol) because I tried other roms from other devs and the problem still persisted, then I went to the stock rom and still had the problem, then I unrooted the phone and did one last complete wipe, re-installed the stock gingerbread rom, and still had the issue, so finally i gave up and got in contact with the guy on ebay who sold me the phone, and luckily he was more then willing to give me a replacement, then I got the note2 and was (still am) busy trying to sell this one, so I really just forgot I had this post up until I logged in right now so that is why the long delay, Thanks for your help guys but in the end im still pretty sure it was a hardware issue, but since Its back in the hands of the seller and I have new one we will never know for sure
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
flyinjoe13 said:
I don't see mention of it very often so I have to assume it's just me, but I have a terrible time with the radio getting borked out of the blue when I run any of the CM10 based ROMs. It will work fine for a few days, but out of nowhere, one I day I will turn the phone on and the radio will be messed up again. For example, this morning I installed the latest CM10.2 stable release. All was working fine... data, phone, etc. I got the ROM setup with all my apps and decided to make a backup. After doing the backup in recovery and rebooting, the radio no longer worked. So obviously I did something in recovery to screw it up.
Does anyone have any clue as to what I could be doing to cause this to happen so often? I want to run a CM Rom, but having to reset the radio once or twice a week is getting tiresome.
Thanks. For now i'll just reset the radio again and go back to stock and hope someone has some suggestions.
Click to expand...
Click to collapse
There are some versions that lose connectivity/data connection but it's not a borked radio. Most of the time you can restore a working system by just turning off data for a minute and then turning it back on.
I am in the process of downloading the "stable" release from 2013-12-11, but my current nightly of 2013-12-10 hasn't had any hiccups.
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
flyinjoe13 said:
I wish it was that simple for me. I can typically get data to work again when it goes out by doing what you said, but the ability to make phone calls never comes back unless I do the whole restore radio procedure. When I look at my phone info, it has my phone number listed as all zeros. It's a pain.
Thanks for responding...
Click to expand...
Click to collapse
Ahhh, the 000-000-0000 number. Seriously, pull the battery. Don't shutdown, just pull it out, reseat, and turn on.
BTW, I installed the stable version yesterday and haven't had any problems. Flawless install, all of my apps still work and I didn't lose any data.
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Have you tried running the latest RUU then flashing recovery and restoring? That seemed to solve a random reboot issue I was having, although I've never had radio issues. I have dirtyracun s-off, so it was pretty quick and easy.
flyinjoe13 said:
If that is all I needed to do, then I feel like a complete dummy. I guess I will reload the stable version again tomorrow and see what happens. Thanks for the info.
EDIT: I've come to the conclusion that i'm just not going to be able to run a CM10 based ROM. I have tried everything I can think of and/or read about on these forums and no matter what, I lose my ability to make calls using any of the CM10 ROMs. I know it's me because everyone else seems to run them fine, but I can't. It's a real bummer because I hate the stock ROM. I just don't know what to try anymore. I tried setting all the network settings as described in the directions (although I can't find the options for RIUU\SIM and NV mode anywhere). I triple wiped everything before flashing, I tried all the different CM10 ROMs and nightlys, I tried flashing with and without the sim card installed, etc. and nothing works. I get the 4G network, but my MEID ad phone number keep coming up as all zeros. It's very frustrating because the only reason I bought the phone off Ebay was to be able to run a CM rom.
I only have one thing left to try and I don't even know if it's worth it. Verizon sent me 2 4G sim cards by mistake so I have a spare sim card. I'm thinking of activating it and swapping out the old one in the hopes that it's a sim card issue. Although the current sim card works fine with the stock ROM so I doubt that's the problem but I don't know what else to try. Boy switching around to different ROMs sure was a lot easier with my old Dinc and Dinc2.
Click to expand...
Click to collapse
Do you have system select as automatic or home only? I have that issue when automatic is selected.
Sent from my ADR6425LVW using Tapatalk
I tried both automatic and home with same results. At some point i'll give it another try, but for now i'm going to stick with the Venom ROM because i'm getting tired of having to reset the radio. Some cold winter weekend day when i'm stuck in the house, i'll give it another shot.
Hello,
I'm somewhat new to the rooting world of Android but when I got my Note 2 last year the first thing I did was root it and unlock the bootloader, and kept that through the 4.1.2 (if I recall correctly) update. I knew I wasn't getting 4.2 and jumping straight to 4.3 as was Verizon's plan. I waited patiently and forgot about it entirely, so a couple of days ago I found the stock rooted deodex rom located here. I thought I had made the correct decision, it seemed to be for my phone, it flashed with no issues (both the rom and firmware) and runs fine except for one flaw which has proven to be a pain due to it cancelling my alarm every morning.
Whenever the lock screen comes up, the phone things a touch happens right in the middle of the screen. Nothing's there, but it doesn't matter what happens, I push the power button, plug its charger into it, it will always send out that one little ripple and as a result it cancels my alarm. I looked through the thread, I appear to be the only one with this issue.
Any recommendations?
Wow no wonder Ive been late to work all week. Phones doing the same thing.
Sent from my SCH-I605 using Tapatalk
As an update from my fiddling about this morning, it seems to only happen when the lock screen is set to the Swipe method. If set to a pattern, pin, anything else, this error doesn't occur. A temporary workaround at best, as this no longer allows me to access multiple lock screen widgets.
Wow man.. since my last post I wiped and am running a new rom, kernel, everything.. still doing it ?
Sent from my SCH-I605 using Tapatalk
I believe I've narrowed it down to a few possibilities, between it being the new ripple/ink effects on the lock screen or something to do with the multiple widgets. I can't believe we're the only ones dealing with this. Does anyone have any insight if even a complete reset, rom flash and kernel swap hasn't fixed it?
As another update, I appear to have been mistaken. While delayed slightly, the end result is no matter what, the alarm eventually silences itself after a few seconds, unknown why.
I had the same thing happen using n3bula (4.3) rom. Alarm would turn itself off. Didn't really have time to mess with it so I went back to beans 22 (4.1.2). If you figure anything out, let us know
Sent From My Sticky Note, Too?
As another update from yet more fiddling. I tested it this morning as it would normally be, hooked up to my computer charging, with my bluetooth headset on but also sitting on its charger. The alarm cut out even with pin set as the lock screen. When removed from the cable connecting it my computer and my headset on my ear, it didn't. Going to test further.
So, as yet another update, I believe I found the problem, a reply from prior posters experiencing the same thing would be helpful to see if it was the same issue. I have one of the original sony android smartwatches that connects through Bluetooth. On a hunch, I disabled Bluetooth on my phone before going to bed a few nights and wouldn't you know it, no problems. Did it again with the watch off and just the headset connected, again, no issues. Seems the watch is a bit too dated or butts heads with the MJ9 firmware driving the Bluetooth module.
So as to follow up. In my situation specifically, my music player is Poweramp and I noticed whenever my headset is connected and my alarm is going, it immediately tries to take over and start playing music, I think that's what caused my alarm to go silent. My headset is the Plantronics Voyager Legend, my smartwatch is the original Sony Smartwatch, I don't know if the combination of the three are relevant to the others in this thread having the problem.
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
ForcePhenomenon said:
Also. It appears to happen on 4.3 regardless. I've gone back after a clean wipe and used the stock 4.3 Samsung Verizon OTA rom, n3bula, and jelly beans and all of them produced the same problem when bluetooth was enabled with my watch and headset connected and poweramp installed.
Click to expand...
Click to collapse
when you wipe do you also format internal sd?
MunkinDrunky said:
when you wipe do you also format internal sd?
Click to expand...
Click to collapse
Correct, thought I'd noted that when I said clean wipe. I wiped internal storage, cache, everything you should when flashing a new rom, going to the point of doing it multiple times and even dirty flashing a few times to see if that would fix the problem (as it did fix some issues going on with n3bula and they actually recommend doing it.) But, nothing of the sort happened.
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
MunkinDrunky said:
Ok. I just can't belive that problem is persisting. Must be the radio? Did you say you flashed one of your backups, where any of them prior to the firmware update? That is if any have the radio backed up too. You could flash the zips for any of the older radios.
Click to expand...
Click to collapse
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
ForcePhenomenon said:
Why would it be the radio's fault. It has zero problems transmitting whatsoever, zero problems pairing, nothing. It just seems that as soon as any sound output comes from the phone, Poweramp immediately wants to kick on and start streaming music to my headset.
And no, I didn't flash one of my backups. Prior to all this when my Note was still 4.1.2 it had no problems. I suppose it 'could' be something with the MJ9 firmware but why would it only affect this certain circumstance?
Click to expand...
Click to collapse
have no idea but since it was a variable in this situation I thought to try to rule it out for certain.
Okay, Now I know I am not the only one with this problem. Also, I know I am one of the FEW people who have this problem.
Story:
I bought the Note the other day from someone, they claimed that the note was stuck in a boot loop. I purchased it, Did a factory restore etc. The phone came on and was working perfectly. THEN the battery died, now I understand what she means by stuck in boot loop.
What happens:
Phone turns on
Starts up
Freezes after about 2 minutes
Reboots & Repeats
Now there have been a couple times I can get it to stay on for about 12 hours then it will just freeze and reboot. I have tried factory firmware restore, I have rooted, I have tried custom Roms, I have unrooted, I have done stock rom. The battery is NOT bad, it holds a charge perfectly well, the Power button is NOT stuck. I have no idea what else I can do, I have tried just about everything and looked all over this site for the past 2 days trying to figure out info on this problem, but so few people are having it that it is basically just looked past.
Any help is MUCH appreciated and I will be very grateful if this issue can be resolved.
Have you tried removing the battery / changing the battery / using a different usb/charging cable/ac-dc adapter? Then clear the cache and dalvik cache and reboot. If you can get it to stay on for 12 hours I doubt that you have a serious problem.
Power button perhaps?
http://forum.xda-developers.com/showthread.php?t=2792746
http://forum.xda-developers.com/showthread.php?t=1744395
http://forum.xda-developers.com/showthread.php?t=2596832
http://forum.xda-developers.com/showthread.php?t=2595555
http://forum.xda-developers.com/showthread.php?t=2547025
http://forum.xda-developers.com/showthread.php?t=2522688
http://forum.xda-developers.com/showthread.php?t=1854944
Not sure about power button on this one. It wouldnt freeze, it would just reboot.
I question software on it. If you can get it running long enough to find out what it is running.
I might question more, is it running OS for the right device or possibly was it a clean flash?
Sounds like its running an older 4.2 JB rom......notorious for random reboots. Could be a rom that just may not work on you phone. Mine could run all except Carbon Rom. Dont know why, just couldnt. No biggie, plenty out there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app