Database Users

Recommendations please Help

I just got the eris on the 20th of july. I had heard that HTC was really good but I have started running in to problems.
I rooted and I am using evil eris rom 3.0. I noticed yesterday that the awake button started not working after further investigation I noticed I could tap on the side and it would wake up.
Also just noticed today that was getting pretty hot and using the battery significantly. only lasted 5 hours.
I am considering returning the phone as I have 30 days.
Anyone have any Ideas

Search through the forums for specific problems you are having, then trouble shoot. Have you reflashed the ROM? Tried any others? Did you do a nandroid backup, if so have you tried a restore? The phone could be complicated so if you don't want to put in the effort id recommend returning it.
Sent from my Eris using XDA App

Did you ask your question in the Evil Eris thread ? Maybe others running the same ROM are having similar issues.

yeah, I tried two other roms for a short time I liked this one the best. At first I didnt have any problems.
Are you suggesting i wipe this flash then reflash it again.
Also are you suggesting I restore the original.
Ive been searching just Havent found anything yet.
I really would like some input on if you guys think I should work through this with the phone. Are these phones reliable and such I dont mind tweaking it a little to get it right. But I dont want to have constant problems

HTC does make great phones. However, you shouldn't base your opinion of the phone off of hacking into it and modifying it (especially being a less-than-a-week-old first-time HTC owner who hasn't done a lot of footwork to troubleshoot the issues).

Yes you should wipe and reflash the rom and see if that does anything. If that doesnt help, do a restore (supposing you did a back up). Also a lot of these roms are over clocked so the phone can get hot from using it a lot especially if its on the charger.
Since you rooted your phone, you have void your warranty. Basically if verizon decides to check the software builds and whatnot and discovers you have rooted, you might not get another phone. There are threads on how to unroot your phone, so I suggest doing that before you return it if you decide to.
Also I might suggest sense able 3.1 very stable rom
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype

orkillakilla said:
Yes you should wipe and reflash the rom and see if that does anything. If that doesnt help, do a restore (supposing you did a back up). Also a lot of these roms are over clocked so the phone can get hot from using it a lot especially if its on the charger.
Since you rooted your phone, you have void your warranty. Basically if verizon decides to check the software builds and whatnot and discovers you have rooted, you might not get another phone. There are threads on how to unroot your phone, so I suggest doing that before you return it if you decide to.
Also I might suggest sense able 3.1 very stable rom
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype
Click to expand...
Click to collapse
Hey bud thanks for the positive feedback. Your help is greatly appreciated.
I do really like the phone. You know all that power in such a small package. Thats the reason for these forums I believe so that we can help eachother.
Ill try that and see what happens.

I really hated my eris until i started using froyo based roms.. They are a bit buggy especially the camera but well worth the effort even if just for battery life. I went from 15-20% lose an hour to 5-8% unless i use alot of data.. then its more like 10-12%.
Sent from my FroyoEris using XDA App

lukaro said:
I really hated my eris until i started using froyo based roms.. They are a bit buggy especially the camera but well worth the effort even if just for battery life. I went from 15-20% lose an hour to 5-8% unless i use alot of data.. then its more like 10-12%.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Froyo rules. CyanogenTazz v2 is blazing fast, smooth,and responsive.

tophunterz said:
Hey bud thanks for the positive feedback. Your help is greatly appreciated.
I do really like the phone. You know all that power in such a small package. Thats the reason for these forums I believe so that we can help eachother.
Ill try that and see what happens.
Click to expand...
Click to collapse
No problem. I'm no developer by any means so I just try to help others from my own experience. My way of contributing
Sent from my leaked rooted HTC Droid Eris with Sense-Able 3.1 using Swype

Bingo
I loaded Sense-able and it seems to be working well so far.
Thanks for the help I'm sure Ill need some down the road

EVO 0004 w/ hboot 2.02 Rom issues

My phone is rooted and I have been having issues with roms. Anyone else having problems?
This is a brand new replacement phone and I am considering taking it back. To get another one.
Thoughts suggestions? Anyone else having similar issues?
Issues:
Keyboard vibration feedback works sometimes. Mostly doesn't.
When rebooting from recovery using the reboot command it hangs on the white screen sometimes. Have to yank the battery and then power it up again.
General instability in the roms I have flashed. Reboots, force closes, and CPU running full steam ahead on some of them. Also flashing some like ripride on fresh 3.4 just results in boot loops.
Sent from my PC36100 using XDA App

You may want to flash airbourne 3.4 with stock kernel I have not had those issues with that combo
Sent from my PC36100 using XDA App

Airborne ? I suppose that is a Rom? I may go back to the stock RUU and return the the phone. Why should I have to put up with a defect? I am running OMJ latest Rom with riptide9 v11. It does have some stuff I don't want on there but it is stable.
Sent from my PC36100 using XDA App

Yea it is a rom from virus I dont have anythose defects it is something to do with hardware 04 but stock htc kernels usually fix all those issue
Sent from my PC36100 using XDA App

Really the big issue is the feed back for the keyboard. It doesn't work most of the time. I haven't had an EVO for almost 3 weeks before getting this one, 20 days go black tie insurance, but I definitely can tell a difference. I am flashing the RUU here in like 5 mins and then I should be able to tell. Oh were you meaning the stock kernel or completely stock?
Sent from my PC36100 using XDA App

If you got it back from Best Buy broken, then why the heck aren't you complaining up a storm and making them FIX it? Honestly, I will never understand why people use BB's crap insurance over Sprint's TEP.

I no longer have that insurance. I do have a brand new phone with a flaw from best buy. If you get a brand new phone you can opt into getting Sprint to cover it.
You don't understand why? Because Best Buy is misleading and I came from ATT who did not offer anything like Sprint does. As soon as I walked into the sprint store to ask about my old phone I knew I made a mistake in my choice. When I heard an employee telling someone they replaced their screen. I have never seen Sprint advertise this kind of service. I thought it was something of the past and didn't realize Sprint had repair centers and to the extent the repairs they would conduct.
I went to best buy and got turned away. They told me to come tomorrow when their manager is there. In fact I had to pay extra tax to get my replacement which was complete bs. I called Sprint and I spoke to one of there management guys. He told me to go to best buy and if they would not give me a new phone to call them without leaving the store.
Sent from my PC36100 using XDA App

Went to best buy again today. Got turned away again. Literally was told that they did me a favor replacing the phone in the first place.
Called the store and spike to the gm. He was pretty understanding and hooked ne up. Now I have a phone that works.
Sent from my PC36100 using XDA App

I agree, always deal with sprint for repairs. Stock kernel 11 or above is better for all around functions (camera, 4g) ziggy kernels are best performance. Just trial and error with diff rom/kernel combo is the best advice. till you find the one that works best for you
Sent from my PC36100 using XDA App

[Q] Is there a fix I can't find?

I have just switched over to verizon from AT&T a couple of days ago. It was an impulse decision as I was only in the Verizon store with my girlfriend to get a her a new phone. I was showing the sales guy my pimped out Samsung Captivate and explaining to him him how easily these things can be manipulated and how much I loved my Cappy. Thats the last thing I remember. I woke up to find I had switched my service (3 lines) over to Verizon and I was now the owner of a Droid X.
I loved my Captivate and had no thoughts of ever switching but they had a promotion going on that blew my AT&T plan out of the water so financially it was a good decision. But I am beginning to wonder if I haven't made a mistake.
Out of the box, the DX is rebooting pretty often. I had planned on getting on here when I got home to find the latest and greatest ROM anyway so I didn't worry about it too much.
I am currently running Liberty 1.0 as my first flash. That is of course after flashing .340 which I read may or may not fix the rebooting issue. I am liking the ROM but the random reboots still persist. Its beginning to get too much to bare as I have yet to have one phone conversation that isn't interrupted by the phone powering down by itself.
I have searched for any word of a fix for this but I haven't found any definitive answers other than to do a factory reset. I have done that several times, as well as reflashing .340 and Liberty to no avail.
Before I take 3 phones back to Verizon and crawl back to AT&T and beg for forgiveness does anyone have a definitive solution for this?
Its worth mentioning that I bought my daughter a DX as well to replace her Cappy (she is NOT happy BTW), and it does the same thing. It is still stock out of the box.
Thanks in advance for any replies.

I have a Dx and haven't had this reboot issue, however, my sister traded in her iPhone for an x on my advice and now she's having the same issue you are. I was going to have her flash to liberty and do a system restore but obviously that hasn't worked for you. Hopefully someone will have an answer to this problem
Sent from my DROIDX using XDA App

Send the phones back to Verizon, that is not normal.

In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.

Sbf to stock and reflash liberty. Or take it back a get a new phone.
Sent from my DROIDX using XDA App

Ben's said:
In my opinion, not to say you don't know what you are doing which I am sure you are, I know you are well aware of the risks of flashing roms.
I hear more people having issues with Droid Xs that have been re-ROMed, flashed, themed, etc, then I do people with stock DXs that are rooted and cleaned up of bloat.
While my DX might not be clean out the box, it's still in prestine shape, rooted and even flashed to Cricket. I have never had a single issue with it unless I am bricking it or messing with it myself.
A lot of times, people mistake the phone as the issue. These were $600 phones when released, still are (give and take a few bucks lol). I doubt the issue is hardware. Send it back to VZW or try the Full SBF 320 using RSD Lite. It's been the talk of the town.
Could be that there's a bad batch of DXs going around that have just been released? None the less, VZW can get you replacement DXs over night practially.
Click to expand...
Click to collapse
Ben you are right about people messing up phones by flashing. But generally taking them back to stock will fix any issues that have risen from tinkering.
My issue is that mine did it out of the box. My daughters did as well.
Funny thing is just this morning I updated my daughters with the .340 update and it seems to have stopped. Its been quiet now for about the last 30 minutes. I reflashed .340 on mine at the same time and it has rebooted about 4 times while I type this message. Maybe my daughters is fixed, but mine is definitely not right.
Thanks for the comments.

My sisters phone is also doing this bone stock. It doesn't always reboot sometimes it locks up and she has to pull the battery. She's taken it into the Verizon store and they reset it to stock (not sure exactly what they did). That didn't fix it so she took it back to exchange it and they told her " that's normal, sometimes you have to pull the battery." So they wouldn't exchange it.
Sent from my DROIDX using XDA App

Sadly this is has been a small issue with the DX, it's been posted many times. Mine did it when I first got it back in August and at first I was blaming Handcent on the reboots. Then for some reason it just stopped and I have never seen it reboot on it's own. Was it the update to 2.2 or removing Handcent? I've reinstall Handcent since so I honestly I don't know. Side note I still blame Handcent on the phones lag because when I uninstall it the screen redraws and the lag goes away.
Anyway there is a great big long thread on this at the Moto DX forums and Matt's (forum admin) advice was to return the phone for a new one. I would arm myself with a printed copy of the thread in case Verizon wants to throw a fit.
For the record I just dig this phone. I'm stock, rooted with just bloat frozen. It's been a great phone after the teething problems were solved.
fasthair

[Q] <Issue><Please Help> Droid X at Bootloader Screen

I tried installing the Gingerbread update, and when I installed both Parts 1 & 2, then rebooted, my phone only goes to the bootloader screen. Tried using RDS and that, and couldn't find my phone. So I'm stuck.
My phone boots now with a red Moto logo and then goes to the error screen.
My question is, what will Verizon say when they see it? I'm going to take it there later today. I'm under insurance but hacking voids that I believe.
What should I say to get it replaced at no cost?
I was going to say that I put it down, and then when I checked it later it was off, and then when I tried to boot it, this happened, saying I didn't hack it, maybe someone else got it.
Would that work?
Speedy answers would be great.
Thank you so much.

DO NOT TAKE IT TO VERIZON.
Look at the stickies, there is a thread about fixing your phone. You need to find the stock firmware and flash it with RSD.
Sent from my DROIDX using XDA Premium App

Also, the "I put it down" excuse will only work if you get a retard. Anyone who knows about Android will know what you did
Sent from my DROIDX using XDA Premium App

Did you install the Motorola drivers before attempting an SBF, just Google "Motorola drivers".

Well I have funny news for you guys.
I actually saw your messages after I got back..but thank you for your time.
But the guy...bought the story. He said I was probably recieving a bad update, and was able to fix the phone.
The guy was awesome though, after, he could tell it had ben rooted, and said, "yeah just know that root won't work on Gingerbread", which he installed for me.
So problem solved.
The extent of how lucky I was is amazing.

Well good deal. I'm glad he was cool. You can root, you just have to sbf back to froyo first
Sent from my DROIDX using XDA Premium App

If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.

salsabettis said:
If you mess up your phone when you are messing with it, you are responsible for fixing it. Not Verizon.
Click to expand...
Click to collapse
Not sure why you're posting this now.
And I think i'm gonna stay away from rooting right now.

If you do ever decide you want root get the bootable linux cd with the automated scripts to sbf with. It is totally painless.
My DroidX Thrives on the DarkSlide!!

Droid X Gingerbread Cellular Disconnect

Has anyone else here had issues with the Droid X having cellular network disconnect issues?
What I mean by this is that the 3G stops all together, you cannot make outbound calls or SMS messages. The 3G icon goes away, yet I can see bars on the antenna strength meter.
The only way to fix this is to reboot the phone, even putting in airplane mode doesn't work. It happens about every 1.5 to 2 days on this phone. I've factory reset it, gotten a replacement phone, etc.. Nothing works and it all started with the Gingerbread update.
I'm not the only one I can tell you that, many others on the moto forum are having it too.. https://supportforums.motorola.com/thread/52111
I have an ADB logcat that I could send to some folks smarter than me if someone wants to look..

http://androidforums.com/droid-x-support-troubleshooting/354058-loss-data-voice-connection.html
Another forum posting I've found..
Glad to see there are more people with the issue.. Now its getting Motorola to listen....

There must be something unique that you are doing. I burn about 2200 min a month of cell time, and I've had no issues.

Yeah that happens to me, I sbf back to froyo, and now I'm on liberty rom, no more cell disconnect
Sent from my DROIDX using XDA App

I'm to the point where I want to get away from Motorola all together.. This phone has always been quirky, now its just totally unreliable. I have an HTC incredible (CM7) and have 0 issues with this, so I know its not a cell reliability issue in my area.
I can tell you that I ran CM7 for a few days on the DX with no issues at all. However CM7 has a few other annoyances that the wife didn't want to deal with.
I'm working with Verizon and it sounds like they're to the point of offering up a different phone..

I was having a similar issue. Spent countless minutes on tech support with vzw, countless resets, even sent me a replacement phone and had the same issue. Determined it was google voice at fault. Had to do a factory reset from the moto bootloader (not from settings/privacy), and it finally solved the issue.
If you're using google voice, try getting rid of it, and disconnecting it from your phone.
Sent from my DROIDX using XDA App

Well, I don't use GV, but had it on my phone...
I've uninstalled, and rebooted (not factory wipe)...
I'll see how it goes...

I asked in the moto forum and one user responded so far saying that they have the issue but don't have google voice installed..

I had the same problem with OTA Gingerbread. Cyanogenmod 7 fixed all my problems. No lie.
Sent from my DROIDX using XDA Premium App

Hi,I'm now having these issues and more since gingerbread. Sad thing is, I had NO issues with this phone while on froyo. Verizon wants to do a complete factory reset, but that means i'd lose everything on the phone. I have it all backed up, but it takes a while to set up the damn thing the way I have it. I feel if tat what Verizon recommends, they should help set it back up.
Sent from my SCH-I800 using XDA Premium App

After dealing with the issue with Verizon they agreed to let me swap the phone out for a different phone. The only rule was no 4G or no iPhone. Right now we settled on the HTC Incredible 2. I have the original Incredible, while the HTC software isn't perfect, but at least I haven't had these issues..
Bye bye Motorola.. Another plus, if this HTC has issues, as least I can run CM7 easily now..

I had(?) the same problem
history:
before upgrading to 2.3.3 my Droid X was on Froyo and rooted. In fine noob fashion I deleted bloatware during that time without backing it up so when I attempted to updated to Gingerbread I was **** blocked.
The resolution was to SBF the phone back to stock Froyo then upgread to Gingerbread, it worked like a champ... sorta
I kept noticing that the phone was really sluggish on reboots, it also kept dropping the network connection, mostly when I moved out of a wifi hotspot, the 3G wouldn't connect, not until I rebooted. I tried a few things, uninstalled misc programs blah blah blah, some of it seemed to have worked temporarily but nothing was permanent.
So, yesterday, I did a Factory Data Reset, actually had to do it 3x's since the first 2 times somehow goofed the market so that it wouldn't download and install . But 3rd time was the winner and now everything seems resolved, no more whacked out loss data connections and faster reboots!
so my suggestion - Factory Data Reset

I totally agree. Vzw tier 1 tech support can be a waste of time. After taking 30 minutes to tell me to turn on wifi, one guy told me to right click on the settings menu. I told him it was a touch screen, does that mean I have to use my right hand?
Sent from my DROIDX using XDA App

I have the same problem on rooted OTA gingerbread. My solution for the time being is to setup tasker to reboot the phone at 3am everyday. If i go back to froyo the problems go away. I posted about this a while ago. It doesn't fix the problem it just masks it but I start with a fresh phone every morning.

I have the issue too, it started right after Gingerbread.
It was *really* bad until I re-activated my phone but it still happens almost every 48 hours.
As best as I can tell, it is most likely to happen when wifi is on and you have a weak cdma/3g signal.
I'm glad to hear that CM7 seems to clear it up. Between hardware instability, the compass quality being degraded and the ever imposing presence of Blur, I'm thinking I'll never again own a phone with a locked bootloader if I can help it.

I also setup tasker to reboot my phone at 3am every night. Did this several weeks ago and I've not had a network access issue since. Not a great solution but if you got root it does seem to make the problem go away.

Hey, let me know what you think of it. I thought about grabbing one cheap and using it until a good 4G & dual core comes out.
Not sure I could go with the smaller screen though.
Sent from my DROIDX using XDA Premium App

I have this issue on an unlocked dev dx which has slightly older hardware than the current DX's but I'm glad to hear I'm not the only one with the issue. I'm going to experiment with some different radio versions, because this didn't happen with all the different leaked GB radios. It wasn't until I think the 588 build that it started for me.

+1
I have had this issue ever since GB dropped for it. I am on my third X since GB. The first one smoked a memory card and battery. So I got a like new phone and all the fixings. Then the second one was also having the data issue and the camera took a **** (shutter was stuck closed). All of these have also not only rebooted randomly from day 1 with GB. Go to make a call phone reboots, send a text phone reboots. I thought it also was apps and heard about Google Voice causing it. So when I got this third one I only setup apps that it came with and nothing else. not even 2 days into having it the same **** was there. Less frequent but still there. They are going to get screamed at until I get a new device.

Switch to cm7. I love it.
Sent from my DROIDX using XDA Premium App