Database Users

mytouch 3g slide restart itself occasionally after root

I didn't test the device before I rooted it. Now even since I rooted the phone, it reboot itself occasionally when using eugene's legend2slide and SlideM rom. Anyone else have similar problem? I also want to mention that I installed DroidFontsfallback.ttf to the /system/fonts/ after I rooted the phone or using those custom roms. Could the font be the cause of the problem?

.
noticed the same problem i dont know what it is

I have noticed this as well. I went from stock -> ENG -> Legend2Slide -> ENG -> SlideMERoot2. I forget when I think I first started noticing the reboots the second time I had the engineering ROM on - but - I didn't keep the engineering ROM on the first time for more than a few minutes, and I only kept Legend2Slide on for about an hour, so I may just have not had it running long enough to reboot itself those times.

Mine is also rebooting randomly.
Last time it was when i changed it to the camera it lagged for a second and then just restarted.

Move posts to Android Dev thread
Don't remember seeing a "Bug" thread, so maybe start a new Bug thread for things that happen after root. Just a suggestion. Thanks.

Same deal here. Its been doing it for a while I just haven't posted anything about it. I'm rooted but on the stock rom and get the reboots every once in a while. Yesterday it did it twice but not today. If I remember correctly I was listening to music and when I stopped the song and hit home that's when it rebooted. Maybe something to do with low memory I'm not sure though as I didn't see the available memory before it rebooted.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Have you guys thought about going back to stock and checking on this to see if it is the phone? If it is return it to t-mobile and get a new one. I have flashed all the available roms and this has not happened to me at all.

Sup fellas
I doubt it is the phone itself. I have had mine running on the standard OS since I got it. I don't want to root unless the froyo update we receive is crap. I'm bearing the pain of not being able to save apps to SD until froyo comes out as an update for the phone. If no luck, then root.
As for reboots, none here. I have had the memory maxed out with widgets on 7 home screens with GDE running, phone running wireless GPS and bluetooth all at the same time and it did not crash nor reboot.
I think there must be some conflict that is in the adk install somewhere. It seems that this is a standard problem after rooting the 2.1 Slide MT3G.

HTC Aria touch screen being very unresponsive

So today while in class at college, my phone was acting very funky. I noticed that touch screen response was going crazy (Even the capacitive buttons were freaking out). Pushing on the screen would type randomly, bring the notification bar down, etc. Pushing on the capacitive buttons would usually do nothing, vibrate, or do the exact opposite it is suppose to do. I can usually alleviate the issue by turning the screen off and turning it back on, but it will only be responsive for a very short time.
So, I was thinking there was something wrong with my install of the CM 6.1.1 ROM, so I flashed the Liberated Aria FR008 ROM and... it does the same. So then I load the CM 7 (18 nightly) and it seems fine with it happening every now and then, but I don't want to use CM7 (Albeit great, it's sluggish and isn't up to what I want to use as my daily driver).
I've treated my Aria with care ever since I got it after my transfer from Alltel. I'm usually able to fix my own problems, but this one has me stumped. Any ideas as to why it's freaking out?

CM7 is now up to nightly 39 and there was a big improvement in speed/performance from 34 and later.

I have 34 loaded right now (Just found it in my Dropbox folder); however, the touch screen is still very sensitive.

I've been having very similar problems with my Aria recently; unresponsive, misreads where my finger is, Swype goes nuts, but a quick lock/unlock will correct it for a little while. I thought it was just that my cracked screen was finally giving up. Now I'm downloading CM7 build 39 to see if it's something else.
EDIT: The CM7 build didn't help my problem. I'm upgrading to an Inpsire 4G tomorrow, but I might try a few more things first or while I'm rooting it.

So I found my backup of the stock ROM and flashed it back on there. Still getting the same issue.
I upgraded the stock ROM to the "latest" AT&T version and I'm taking it into AT&T tomorrow.

perhaps its an isolated defect on your phone. hopefully your hardware is still under warranty, but alas we already flashed. maybe you can get a technician to look at it.

Took it into the store and the guy said it's "shot". I'll be able to replace it under warranty.
I should be fine. I'm still confused about how the touch screen became unresponsive, and like I said... I'm usually able to figure this stuff out (Going to college for computer engineering).

[Q] So i got TF101 Refurb from Newegg..

(Item: N82E16834230172)
.. & I'm just not sure if i should return it or if these issues are pretty much whats expected.
I have not upgraded to ICS from HC
Problems so far:
1. Re-booted twice on first day i had it. I'd been using it all day (installing/using apps etc) - I used it all day 2 days after that w/out issue.
2. Re-booted last night? Not sure exactly but there were no apps suspended in the bg from the night before (~8 hours before) - i had quite a few in the bg
3. 2 out of 3 times so far if i "shut down" *the power button will not power it back on* - i have to plug it into the wall/power for it to turn back on
They aren't the worst issues..yet? I don't know.. I'm pretty happy with HC at the moment & will probly avoid ICS upgrade for a bit.
Stick with it?

#3 is not supposed to happen.
#1 and #2, it depends on exactly which version of the Honeycomb firmwares you are running. Honeycomb 3.2.1 didn't do those for me, but the versions pre-3.2.1 had occasional incidents.

It's 3.2.1

We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.

ssl123 said:
We can assume that you know that you have to hold the button down for three seconds to power it on when it's completely off. Therefore, I would see about swapping it because #3 sounds like a major problem.
Click to expand...
Click to collapse
Yeah i just shut it down again and it would not come on until plugging into the wall. Problem seems pretty consistent. Ugh i really don't want to have to go through this.
QUESTION: how can i pretty much wipe this device of the apps/personal info i've entered into it before sending it back?
QUESTION: Try ICS then if i'm gonna ship it back anyways?

To wipe the device, you run "Factory Reset Data" in the Settings.
Sure, might as well try out ICS if you're curious.

Sometimes when mine gets a random reboot/shutdown I have to hold the power button down for about 10 seconds to turn it on. Try this if you haven't already.

yeah the power button issue may be it not being totally shut off, so when you hold power you are shutting it down instead of starting it. happened to me a few times so figured it was worth a mention.

Thanks for the suggestions guys. Although it's a bit inconsistent on whether or not i have to hold it down for 3 seconds or 10+ one way or another (after a struggle) it does appear to consistently come up. Emphasis on struggle though.

Have you tried any custom roms yet? I personally seem to have a more stable tablet when using a custom rom due to the various tweaks and fixes.

Just install ICS - such a relief from Honeycomb!

No_u said:
Just install ICS - such a relief from Honeycomb!
Click to expand...
Click to collapse
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh

bgl said:
This thing decided to re-boot randomly again. So i decided to upgrade to ICS (4.0.3) - nearing last ditch efforts.
Problems came up right away:
1. Browser having strange connectivity issues? I have Wifi Analyzer and watching the scrolling graph i don't see any dropping or problems with the connection itself. So i'm not sure what the situation is but sometimes it just doesn't want to load pages - I can't fully say if Dolphin has the same problems or not.
2. Screen tearing. Fairly frequently there's a diagonal tear occurring across the screen, when switching around in/out of apps.
3. The shutdown issue. This problem is at best the same, if not worse. So in hopes of shrugging off the other issues i did a "shut down" and i seriously battled with the power button and never got it to come back up w/out plugging into into the wall.
- What's interesting is how it always comes up RIGHT AWAY once it's plugged into the wall. I tried and tried and tried again with holding the power button 3-10-20-30+ seconds random intervals nothing worked. Hard to express the amount of times & different timings i tried.
So i'm gonna give it a whirl like this for a while and see.. i might end up doing a factory reset .. if problems persist after that it's going back to newegg
Edit: i just tried to play a youtube video and it stopped trying to cache 1/4th through it.. then i pulled up Aljazeea live and it's echoing/choking/stalling .. these problems didn't exist prior. Also, i noticed another streaming (scanner radio) app not doing so well earlier too... heh
Click to expand...
Click to collapse
Do a factory reset already and test it without installing any apps. You need to find out whether the problem is with hardware or software.
There's a good chance that it's a hardware problem since you got it refurbished. Maybe it was broken already and Asus didn't completely fix it.

Do yourself a favor. Root it and install the latest CM9 build. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.

Headcase_Fargone said:
Do yourself a favor. Root it and install a custom rom. I was having all kinds of reboot and sleep issues with the stock ROM, mainly the ICS one but a few issues with HC as well. CM9 has been rock solid for me so far.
Click to expand...
Click to collapse
Fixed it for you
CM9 might not suit him, so instead he should try out several roms until he finds one hes satisfied with
Telling him to install a specific rom is fine, but it doesnt really help him out.
That said, since you brought up "rock solid", Team EOS build 19 has been really rock solid for me. Currently 202h uptime and counting.

Wow i didn't think things could get much worse but they did.
I decided to do a factory reset because generally things hadn't improved. Initially after the reset things were "OK" ("better" @ 1st but short lived)
Then a while later..
It appears the connectivity of the wireless has completely died. It will connect to wireless fine but is incapable of anything beyond that. No web pages, no connectivity/data transfer in any apps.
I did another factory reset, installed nothing, imported nothing, signed into nothing.. same issue.
Even though i have 2 other netbooks right here w/no issues at all, i tried resetting the AP multiple times. No diff.
Just before the wifi dying it was acting like it was before the reset, where things would randomly fail to stay connected, videos wouldn't fully cache, web pages wouldn't fully load etc. (general connectivity problems that didn't exist in HC, but have in ICS since update)
I think ICS was really the nail in the coffin for this thing.

[Q] Samsung Tech got my phone worse

I think they got my phone worse, I'm planning on take it back to Samsung but first I want the opinion of you guys since I've learned so much in XDA and they are so much "pros" in here.
I would like to know if there is something I can do? Is there something I should say to them? and mostly ... Should I ask for a full refund for the new $330 main board that DID NOT fixed the problem or they did well?
The beginning :
- I bought a N900W8 in september 2013, since the very beginning it had a multitouch problem, when XY from a finger aligned with the XY from another finger, one of them would disappear, it wasn't such a problem for me since the odds to trigger the bug wasn't that much and I had warranty.
- Kitkat was out and I couldn't help myself and updated it to the mexican leak, since it was "Knox-trigger free" and "downgreadable" I was still planning to take it to warranty if the problem with the touchscreen persists.
- Everything was fine and it didn't had the problem anymore, kitkat was amazing, rooted it, installed X-Note, my phone was great. Months passed, I updated it with the canadian Kitkat NB7 and more months passed.
- So, it's september 2014, I was reading reddit on my phone and it started to lag bad, like unusable bad.
Diagnostic :
- Later I notice it's not lag, it's a delay with the touchscreen. If I used any voice assistant app It would work perfectly but if I touched anything on any spot, it would take like 30 sec to recognize or it would act like I was long pressing it or double tapping, same thing with the pen and the physical buttons (volume, home, power). I spend nearly 20min tapping everywhere on TWRP recovery mode and there was no delay, the physical buttons worked perfectly too. EDIT: every time I installed or re-installed a ROM every tap/physical worked perfectly when selecting (next, next, choose apps, etc). the delays started after booting the OS.
What I did :
- Clean up the phone, check RAM (max was 10% still had 15~45sec delay), Format, Hard Reset, Reinstalled Kernel, Reinstalled ROM, Downgrade ROM, tried another Kernel, another ROM, 3 more ROMs, 2 more Kernels, flashed everything stock, tried stock with custom kernel.. NOTHING. The only thing I couldn't do was to flash Jellybean back because I updated to NB7.
- Took it directly to Samsung (Knox was still 0x0 but there is NO 4.4 update in my country yet so warranty wouldn't cover it) the guy said it was too weird, I took care of my phone so much, he though I bought it 1 week ago not 1 year lol.
What SAMSUNG did :
- After a week they told me it was the main board / motherboard, charged almost $330 for a new one.
- Went to pick it up, the guy turn it on and handle it to me, I even couldn't choose the language because the delay was there. He immediately called someone on the phone, and told me he has to take a video when the problem occurs, but when he inserted the battery back my phone started to work perfectly, almost 45min later was still good so he told me to go back if something happens again. My Scover didn't work, they told me it's "normal" for the Scovers to broke (it did worked before taking it to repair).
- 3 days later I decided to install 4.4 again, but this time I was not going to update it so I could downgrade to 4.3, long story short, I flashed 15 times and downgrade it 16 times because everytime I was on Kitkat the incredibly annoying delay cames back and it fixes when I flash JB back.
New problems :
- The problem persists on kitkat dissapears on jellybean, I haven't tried the updated firmwares, just the leaked mexican one since I needed to downgrade android.
- Scover makes my phone flashes like I'm open it and closing it.
- Every re-boot the half botton of the screen and the volume/home buttons, back and menu, won't work, the power button shows a black screen with the options on the top. I have to pull the battery or shutdown- turn it on in order to solve the problem.
Thank you for reading !

Freeze on charge

I recently rooted and unlocked the bootloader on my Razr M and installed a nightly build of CyanogenMod (I like to live on the edge, I guess.) The first week or so with it was going great, no issues as far as I could tell.
Then I installed a social application that requires GPS location. I noticed that the first time after enabling this the phone would freeze when plugged in to charge. It would freeze to the point where hitting the wake up button wouldn't even activate the screen. Not always, but it has happened on several occasions. So now whenever I charge it (daily), I have to force reboot (hold down Up, Down, Power in that order.) Sometimes it'll even go through the process of "Optimizing Apps" as if they were all just installed.
Firstly, has anyone else experienced this? And if so, is there an "easy" workaround? I can't quite pinpoint how to reproduce the bug, though I've got 3 different Cleaning applications installed that are used daily. That in mind, it's unlikely this is a memory leak bug.
Second, if there's no "easy" workaround, when can one expect the next Stable build of CyanogenMod, if ever? Is it still in development? I see that the last Stable release for this phone was in 2013. It seems like I'll have to downgrade to an earlier build, but just want some input before I do it.
Thanks much in advance

Sounds like an issue with the app, not the ROM. You said yourself that the issues started AFTER installing that app. So, delete that app and report back. Also, a lot of those cleaner apps out there will just bork your phone if you're not careful.
Sent from my Nexus 5