Database Users

[Q] What's wrong with this MyTouch 4G?

A buddy's girlfriend just picked this phone up and she had me check it out and show her the ropes (I own an Epic 4g and came from a Hero) and I just couldn't get over how incredibly slow it was. It installed and opened apps slowly, it changed screens slowly, I honestly thought it was a 500Mhz phone until I looked it up. Now, I know these custom UI skins have a tendency to drag down performance, but my Hero never ran like this and neither does the Evo which is a similarly spec'd phone with the "same" software. Its so bad at this point even she's fed up with it and the only Android phone she's had before is the Vortex which is a 600Mhz device.
Now, I know that this phone is capable of more given its hardware and I'm going to get right to hacking it up for her and getting CM6 or 7 (nice btw, I wish we had CM7 going on the Epic) but is the stock software it comes with supposed to be this bad or is this an atypical experience that if I were to do a factory restore (via RUU or w/e file type they chose to load software with) would fix it?

Definitely unusual, my gf has a stock that she abuses, installing everything she finds and never uninstalling or rebooting and her phone still runs smooth. Might happen to have an app misbehaving...

Thanks, I've worked many an HTC phone and hers is a disaster. I can't imagine what app could have been misbehaving, but I assume it'll stop once I wipe everything and load some vanilla Android goodness. I'll admit, I'm more excited to mess around with CM7 than I am to root around in her stock phone to find whatever's causing the problem.

I'm still running stock on my MT4G, and it's quick as can be. Been using it a month or so and virtually no lag.

My stock mt4g wasn't slow either. But definitely root it. Much faster
Sent from my HTC Glacier using Tapatalk

nick34609 said:
My stock mt4g wasn't slow either. But definitely root it. Much faster
Sent from my HTC Glacier using Tapatalk
Click to expand...
Click to collapse
Lol, yeah I'm sure performance would be even better after rooting and optimizing, but I'm not there yet. I had my MT3G for like 6 months before I got bored and decided to root, after which I tried about 20 different roms. I'm sure I'll follow a similar pattern with this phone - in a few months I'll get bored and root to start switching things up. But still enjoying the stock experience as it offers everything I had to root the MT3G for. Plus rooting after running stock for a while will really make it feel like getting a new phone without actually having to buy one

I just bought one as well on the 12th of Feb and it's VERY slow. Annoying. I DID run a Quadrant standard test on it and it scored about 1660 which is nice. No matter how many factory resets I do, it doesn't change the crappy smothered OS.
My stock EVO was very fast. Other MT4G's I've worked with are able to be rooted and are very snappy STOCK. This one is slow and giving me a headache.
I am unable to root it with any method available. I can't find Visionary 11, which supposedly is the problem...
I'm waiting for another method to come out. I've tried about 4 different methods...

Install iced glacier rom on it and maybe faux's kernel and you're done. It should be smooth as butter. I don't know how tthat stock is slow but I've played with a buddies stock phone and its still quick. No lag. Definitely a app misbehaving
Sent from my HTC Glacier using XDA App

If wiping does not fix it, then I would say there is a hardware issue. It should not be slow at all.

Yeah. Took me about a week before I decided lol.
Sent from my HTC Glacier using Tapatalk

RootaToota said:
I just bought one as well on the 12th of Feb and it's VERY slow. Annoying. I DID run a Quadrant standard test on it and it scored about 1660 which is nice. No matter how many factory resets I do, it doesn't change the crappy smothered OS.
My stock EVO was very fast. Other MT4G's I've worked with are able to be rooted and are very snappy STOCK. This one is slow and giving me a headache.
I am unable to root it with any method available. I can't find Visionary 11, which supposedly is the problem...
I'm waiting for another method to come out. I've tried about 4 different methods...
Click to expand...
Click to collapse
It seems like a factory reset wouldn't fix any core issue, since there isn't an image kept on the phone's memory. It just wipes all of your user data and returns the phone to an original state, but if the original state is in some way corrupted you would have to flash a known good image of the stock ROM to correct any problems. You can find good post-OTA PD15IMG.zip files on these forums.

Misbehaving apps or hardware problems are not the only reason for slow down.
If you have your phone syncing a ton (facebook, twitter, Qik, weather, stocks) it will appear slow as it becomes sluggish during the sync process.

$pitacular1 said:
Misbehaving apps or hardware problems are not the only reason for slow down.
If you have your phone syncing a ton (facebook, twitter, Qik, weather, stocks) it will appear slow as it becomes sluggish during the sync process.
Click to expand...
Click to collapse
You should be able to run 7 screen full of active push widgets and full syncs without the type of lag he is describing.
He said he thought it was a 550MHz phone until he looked up the specs. There's got to be some rogue program controlling things. Check out the running apps / services and also check the battery usage.
Finally, if a wipe doesn't fix it, send 'er back!

RootaToota said:
I just bought one as well on the 12th of Feb and it's VERY slow. Annoying. I DID run a Quadrant standard test on it and it scored about 1660 which is nice. No matter how many factory resets I do, it doesn't change the crappy smothered OS.
My stock EVO was very fast. Other MT4G's I've worked with are able to be rooted and are very snappy STOCK. This one is slow and giving me a headache.
I am unable to root it with any method available. I can't find Visionary 11, which supposedly is the problem...
I'm waiting for another method to come out. I've tried about 4 different methods...
Click to expand...
Click to collapse
Here is Visionary R11

Making the Leap - Stock - > Cyanogen: Let's discuss

Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!

DownloaderZ said:
Hi Guys,
I've been with Android since truly day 1.
I lived with my G1 for a long time and together we endured lots of roms. Cyanogen is what most always ran on my G1. Finally, after all the bugs, slow downs and issues, I got a nexus 1 and kept it stock. It's been an amazingly unfrustrating experience and I truly fear any cooked roms.
I do however, have some gripes with stock android. One of the biggest is the lack of permissions controls in apps.
Today, I read that cyanogen is implementing permissions blocking at the app level on the nightly builds. I am VERY intrigued and want to give this a go.
http://www.androidpolice.com/2011/0...port-for-revoking-and-faking-app-permissions/
So to everyone, how stable is cyan compared to stock 2.3.4? Is it still the same old buggy, bloated, incomplete rom as it was, or have they been able to keep it light, stable and full of extra features?
Please let me and the other readers know!
Thanks!
Click to expand...
Click to collapse
I love it right now.. before it was bloated and totally incomplete and now they got it working pretty darn good you asked at a good time! but for some users.. still causing issues. For some like myself it is perfect right now absolutely no problems I took a while to stick with GB because of all the problems with CM7 I had an htc magic which was pretty similar to the dream and I understand most the problems you probably faced. I've tried a bajillion cooked rooms myself and ever since I moved to the nexus one I just stick with a few (I tried so many on the magic it was my first android and wasted so much time -_-) I would suggest you give this one a try it still has extra features but most of which I find useful

It makes it noticeably snappier and battery life is better. 99% win (wireless LAN reception is a bit worse). I went from stock 2.3.4 to CM7 and am kicking myself for not doing it 16 months ago lol. Maybe there were issues with cooked Roms earlier but the n1 is a mature platform and I haven't noticed any major issues with cyanogen 7.03, of course YMMV
Sent from my GT-P1000 using Tapatalk

I have been running the nightlies for weeks and they have been very stable for me. I have not had any significant problems and really like using them. #85 put the permissions blocking in yesterday and I tried it with a few apps. Seems to work fine. I liked stock rom, but personally could not do without trackball wake and lots of other wonderful features in cm.

Once you go custom you wont ever go back to stock.
Make sure you understand how to flash a custom recovery and how to get to it first.

he said he had cm on his hero so he must now about custom roms..
i think it is currently very stable and good apart from the wonk issue.

CM7 Nightlies have been gold for me. Except couple bootloops. I'm on #83 now with data throttle removed. I love my Dinc
Sent from my ADR6300 using XDA App

I have been running CM7 since shortly after the official Froyo was released from Google. I had to send my phone back for the powerbutton and so I rooted it right before and tried out one of the CM6 nightlies. It was amazing. The features in every subsequent version have only built on the quality of CyanogenMod. I have been a nightly user ever since (although I only flash nightlies every week or so).
It has been extremely stable for me and I have converted a few friends (most recently a friend with the Desire HD) and they don't know how they dealt with the stock crap for so long.
So in short, give it a shot. Do a nandroid beforehand if you are worried, as then you can go right back if you don't like it.

You can only control the permissions on cm7 nightlies. That feature isn't available in the stable release I believe.
Sent from my Xoom using XDA Premium App

cyanogen 7 starting at nightly #74 has introduced some new bug fixes which greatly improve standby battery life, so that now idle current with screen off is 3-4mA. its so good now, that you can leave your phone unplugged over night for 8 hours and only lose like 3% battery. and this is WITH wifi and email accounts turned on and syncing.
this makes the nexus one like a brand new phone and turned it into a proper normal device in the sense that you can now rely on superb battery life. you know that when you arent using it and the screen is off, when you come back to it you will have the same battery percentage as when you left it.
its a no brainer to use the nightly just because of this alone.

Ever since the 2.3.4, I've been happy with the battery life and fixes with the GPS. Currently my uptime is 190+ hours without the usual sluggish response that requires a restart.
Running CM7 I found more random issues from the call quality being distorted and random reboots, to other random bugs that I need something stable.
Sent from my Nexus One

i often go 550 hours between reboots on cyanogen.

I don't know how anyone is stable with GB.

Whether it's a Gingerbread ROM, or just pre-rooted GB Motorola ROM, I am not stable. I get random freezes sometimes, but more often I just can't turn the screen on. It turns on, but is completely black (but you can tell it's on) and I have to do a battery pull. Liberty GB (all versions) do this as well. No GB ROM in existence is stable. I go back to .340 stock Froyo SBF or back to some other Froyo-based ROM, everything is fine. The problem never happens once.
HOW ARE YOU GUYS HAVING STABLE GINGERBREAD ON THE DX?
Ugh. Rant over. If it was a hardware problem, it'd happen at least occasionally on Froyo.
My next phone is so going to be an HTC or Samsung.

Absolutely no problems at all using Apex 2.0 RC2. Gingerbread AOSP.

No problems on prerooted GB. I was having that issue with rooted Froyo towards the end before I upgraded. It would mainly happen when I used Maps and as far as I could tell it was the GPS screwing up because when I turned off GPS my phone worked fine. I have yet to turn on GPS on GB, food for thought.
Sent from my DROIDX using XDA App

Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86

try cyanogen its pretty fukin awesome. only bugs so far are vieo camera and hdmi. other than that its fast n stable...
Sent from my DROIDX using the XDA mobile application powered by Tapatalk

Cyph' said:
Same exact problem as OP mentioned. Especially common after docking/undocking from PC (even if it's only charge only mode). I think GB and the Moto Driver pack are not happy. I'm running win7 ult. x64... not sure if you're on the same; but I noticed I didn't have the problem on my old work PC w/ XP x86
Click to expand...
Click to collapse
I don't think it's Win7 64bit causing the issue, I'm running it at home and work and I haven't had any issues connecting or disconnecting my phone. I would really recommend SBF'ing back to Froyo, clearing data and cache a few times, and starting with a fresh ROM. And if you have TB backing up any system data, don't restore that, just apps + data.

I love how people say they will switch to a different device manufacturer as if they expect that device to be 100% flawless.
I use prerooted GB .588 and I don't have any freezes and the random reboots stopped after I did a factory reset.

I,ve been running 596 deodexed since the first day it came out with no issues. Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Sent from my DROIDX using XDA Premium App

.596 rooted deodexed. Perfectly stable. Are you overclocked?
The only time mine froze was when I went from having it underclocked at 800 MHz to overclocking at 1.4 GHz. But I expected that to happen lol
Sent from my DROIDX using XDA App

Liberty is working great for me. I have had one freeze up since may.
Sent from my Xoom using XDA Premium App

My Verizon Droid X works great with GB. Even pushed it with Netflix and Hulu. I burn about 2200 min a month of cell time on avg. No issues.

I am running the latest DarkSlideX on my DX. It's flashed on top of TBH's 2-part 596. It's fast, stable, and has pretty good battery life, too. I had a reboot issue the first day with it, but a couple reboots and it hasn't hiccuped in over a week.
My DroidX Thrives on the DarkSlide!!

I have had about 1 of the problems you've discribed: The lockscreen blackout but that only happened once.
The problem is that you are probably deleting necessary files with Titanium backup. The crappy thing about GB is that half of the apps on the system that moto puts in there are interconnected with everything else so if you kill one app it'll make your phone die. I have never had the random freezing; but If I were you I'd delete WInzip if you have it on your phone. This is the main reason for a lot of my gingerbread issues. I now use ProPlayer: you can either get it free somewhere online, or off the market[place for like 3 bucks.
Everything is now working great.

Massgainer said:
Since the vast majority of ppl seem ok with GB, it's most likely ue (user error) with following directions.
Click to expand...
Click to collapse
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.

You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.

BBJohnnyT said:
You probably did this, but many aren't aware of it. Any time you do a SBF or ROM install, do a factory reset as well. More often than not, it clears up strange behavior like this. I had lots of problems with my GB upgrade until I remembered to do this. Since then, GB has been running flawlessly for the past few weeks.
Click to expand...
Click to collapse
After SBF'ing, I've always had to (so far) wipe data and cache to stop it from bootlooping anyways, which is basically the same thing as doing a factory reset.

Roland Deschain said:
I completely agree with your logic, but it's not user error. I'm a tier 3 tech for 10 years and user error is abundant and seemingly always the cause of problems that you can't duplicate on your side of things. However, I was flashing ROMs to smartphones years before Android even existed. (I also SBF my phone from a headless Ubuntu server sitting under my desk that I'm SSH'd into, if that helps convince you that I know what I'm doing.) I'm intimately familiar with the process on a variety of devices. I clear data, cache & dalvik cache 7 times each just to be sure whenever I SBF or install a new ROM, or even update to a newer version.
I don't use backup apps of any kind like Titanium Backup specifically because they can cause problems, I do "fresh installs" every time. I may have some hardware issue only being brought to light in Gingerbread, which seems unlikely but anything is possible. No matter how many times I SBF back to .340 stock or .340 stock then flash Liberty 2.0.1, (which is still Froyo-based) it's rock solid, but any GB ROM, before long I've got the screen turning on to a blank black screen when I hit the power button and it takes 1-10 reboots before the problem goes away for a while.
Really annoying. Guess I'll just have to stick with Froyo until I decide to buy a new phone. Bleh.
Click to expand...
Click to collapse
Nothing to add, just wanted to say "Hile, Gunslinger!" (just finished the audiobook version of DT 7).

[Q] Random reboots on CM-based roms

The past several days, I have been noticing random rebooting on both Official CM 10.1, and PAC-rom, which is CM based. The way it usually goes is: while interacting with the phone, the display will totally freeze for several seconds, then reboot.
Anyone else noticed this lately?

Mushroom. said:
The past several days, I have been noticing random rebooting on both Official CM 10.1, and PAC-rom, which is CM based. The way it usually goes is: while interacting with the phone, the display will totally freeze for several seconds, then reboot.
Anyone else noticed this lately?
Click to expand...
Click to collapse
They're both a work in progress and it's not unknown to get some rr's. They'll get better as the devs work on them. Keep trying the updates.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

CM is always a work in progress, then something better comes out, and dev for CM suddenly drops waaay off. Atrix 4G with CM7 had the same problem; endless reboots when i tried to play music, random stuff would work/not work with every update, and everything kept changing. I got sick of it pretty quickly, and i wont run CM anything again.

I've found I only get rrs when using KT's kernel and the ktoonservativeq governor. Using AOKP, CM, and Slim Bean on their stock ROMs, I have zero rrs and I've TRIED to reproduce all the conditions that cause them. What I've found is it appears to be tied into the GPU rendering as I get these rrs when either scrolling through long pages on Tapatalk or Twitter or using the AOSP camera. Haven't reproduced using any other process yet and it doesn't always happen at the same time or place (ie x seconds after boot or crossing x post).
Sent from my SGH-I337 using Tapatalk 4 Beta

Does this happen on a brand spanking new, untouched, stock copy of the rom your running?
Which is CM10.
These kind of problems are the exact reason I jumped off the aosp bandwagon. One thing after another. Just not worth it to me.

Nexus 6p MHC19I high RAM usage?

Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.

Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...

Alex338 said:
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Click to expand...
Click to collapse
That's so odd for someone on the bleeding edge to have issues. Give it time

do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs

dontbeweakvato said:
That's so odd for someone on the bleeding edge to have issues. Give it time
Click to expand...
Click to collapse
I'm impatient. They've had a whole day to work out the bugs
Pain-N-Panic said:
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Click to expand...
Click to collapse
Yeah Feb factory image was basically perfect for me. I don't use Bluetooth much so didn't have any of those issues. I had no issues flashing, but like I said I'm stock with no root, so no twrp to worry about. And yes we buy these phones to experiment!
Update: Had the phone completely freeze on me. First it lagged like crazy and wouldn't respond to touch, then screen went blank. Had to hold down power until finally it shut off. Seems to be fine after a reboot. I definitely never had anything like that happen since I got the phone. Hopefully it was some random one off bug!

quantumqweef said:
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
Yep I'm aware of all that. Like I said, not really a complaint, more of an observation.