My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Related
I found the solution to the problem described below. It was ROM Manager that was sabotaging me, for whatever reason. I went into CWM manually, wiped everything obsessively 3 times like I've seen other people describe, installed 1.6, and it worked perfectly. Too early to say how it actually runs for me but I least I've got it fully installed!
PROBLEM:
I started from stock rooted S-off ROM and installed Das BAMF 1.5, wiping everything as recommended. Under Settings/About Phone/Software information, the baseband, kernel, build number etc were all correct. Things ran OK, although battery life was pretty bad. But there were a number of anomalies. The Verizon bloatware still seems to be present. The location reticule is still present in the notification area. Etc.
Today I installed 1.6 over 1.5, again wiping everything even though it is said not to be essential. I did the install through ROM Manager. Everything proceeded as expected, the boot animation screen shows BAMF 1.6, all the About Phone information is correct for 1.6. But again, the location reticule is still present; signal strength indicator is 4 bars instead of 6, Verizon bloatware still present.
I know the real action is in the development thread but I still need a few more posts before reaching that exalted status. Anybody else seen/solved an issue like this? Any help is appreciated and if some kind moderator feels led to move this to the other thread, all the better!
[EDIT] A couple other anomalies are the extended Power Options and Reboot menu options shown in the 3rd and 4th screenshots at the beginning of the Das BAMF 1.6.1 development thread-- I don't have those. On the other hand, I do have BAMF Toolbox, Call Recorder, and other expected apps included with the ROM.
Thanks very much.
I'm having the exact same results. Frustrating!
Are you installing with ROM Manager, or directly from CWM?
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Here's the thing I don't get. What's the fricking point of wiping 3 times?
If wiping == formatting a partition, then what good does it do to do it 3 times? None that I can imagine.
If wiping == deleting everything in a directory tree, then again, what point is it to wipe 3 times? What is accomplished on the second and third time that isn't on the first?
Just my opinion. I've never had a problem with wiping just once.
johnkc1975 said:
Having the exact same issue and I installed with ROM manager. Should I reinstall 1.6 manually in CWR? I JUST rooted my phone a week ago and I think I may have flashed it 20X already, lol! I also have weird caller ID issues, it says CDMA call waiting when I miss a call, and Call waiting when I have a voicmail. If flashing it manually will fix these issues, I'll do it again!
Click to expand...
Click to collapse
I would try hbooting the unsigned stock RUU. Then try flashing the rom of your choice through Cwm not rom manager. This should start you back at scratch with s off along with clearing up any bugs you can't seem to get rid of.
I had the same problem. Don't use Rom Manager for this Rom. Do it manually and everything will be like it should.
Ditto to that. All my unfruitful efforts were due to initiating the process via ROM Manager. Doing it all via CWR did the trick.
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
lilhaiti said:
Lately (since yesterday) I have been having a weird problem. Every time I restart my phone, it resets. By resetting I mean my it looks like a fresh install. All my apps are still there but launcherpro has the fresh install look and GAPPS is asking me to install stuff. I have also been getting a lot of FC's with these restarts. I have tried going back to a earlier NANDROID and it seems to do the same thing...going ever further back now to see if it still does it. Has anyone seen anything like this before?
Click to expand...
Click to collapse
You flash anything or change anything with a2sd etc, before this started happening?
It's not doing it on an older NANDROID (from 4/22).
I flashed Drowning 7-6 ad then noticed it. But since my last restart before that, I've installed a lot of stuff. I will try it for a while on this NANDROID and see if it does it again after updating my apps, too many changes to rebuild from here...
Basically what happened was I flashed the Kernel (7-6) and restarted, things were fine...but then (per Drownings advice) I restarted again, and then all hell broke loose. I recovered my last NANDROID but experienced the same thing with just a restart, so now I am on an earlier NANDROID and tried a restart and all went well..Like I said I will try to update my apps when I get home (damn ATT data caps) and see what happens then...
OK...several restarts after installing updates, and everything seems normal it's definitely got something to do with either drowning 7-5 or 7-6, or n75 and/or n76.
Right now with the NANDROID I am running n42 with drowning 7 with aufs enabled (as was with the newer ROMS)
I also run DT A2SD with apps and dalvic on SD.
I will try to upgrade to n76 and drowning 7-7 in a few and see how that works out...
n76 and Drowning 7-7 has been good so far...I think the problem is solved...there was definitely something wrong with my setup that was common to the later NANDROID...thank god I saved some NANDROIDS
Wasn't there some kind of known issue with 7.6? I don't remember the details, but I seem to recall that there was some reason why I didn't flash it at the time (aside from general laziness).
Did a fresh install of n76 with S2E and Drowning 7-7, all is running smooth again and I have restarted a dozen times with no issue. After flashing over top of ROM's for the last few months there was probably some trash getting in the way, so I decided to clean house.
So I got an Evo 3D GSM a few days ago and upon installing a custom ROM on it, the phone worked perfectly up until the first reboot. At which point it began to reboot frequently so I reverted back to stock and it was fine. I then tried another ROM though from the same developer and once again it was fine up until the first reboot and then again it became unstable.
At this point I know it could just be that I used 2 different Sense 3.5 ROMs from Shooter that's been causing the problem but unless that's a known issue which I couldn't seem to find, I'd rather not install another ROM just to test this out.
Basically I'm wondering if I could be doing something wrong, I installed it through ClockworkMod Recovery which never gave me problems on my Nexus One. Also if I'm going to test if it's just an issue with the ROMs, can anyone suggest a stable and relatively customizible ROM?
Are you doing a clean install, full wipe?
Also, are you loading apps and settings back into the phone from Titanium or the like?
Ya when I attempted to do it non-clean it was unstable off the bat. The last time I basically wiped everything. I have been using Titanium Backup to restore apps but I also used it on stock(I backed up from my Nexus originally) and it hasn't given me any problems there.
Try flashing the rom first again and this time don't use tb to restore data to apps. I've seen and read quite a few times that tb can cause all kind of weird problems when restoring data+apps. Try just restoring just the apps and see if the issue still remains.
#Root-Hack\Mod*Always_
""Shooter on Deck""
I went through the apps I don't need first and removed the backups, I never did restore data, just apps. MikRunny seems to be running stable so problem solved though I still don't know if it was ROM related or just an app screwing with it.
if you flashed a new ROM, it was probably the ROM since it is working now, seeing as how you didn't restore any of your data. logically, that sounds right to me.
cobraboy85 said:
if you flashed a new ROM, it was probably the ROM since it is working now, seeing as how you didn't restore any of your data. logically, that sounds right to me.
Click to expand...
Click to collapse
Well I had tried two different ROMs before and never restored Data, kinda strange but it appears to be fine now so I'm not complaining.
Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
beholder121 said:
Hello guys,
I gave my friend my EVO 3D (CDMA, Sprint) a few months ago when I upgraded to a new phone. Ever since she called Sprint to activate the phone (at the time running SOS M 2.6 ROM) she had nothing but problems. She also didn't have the Google Services packet working for some reason (all Google Apps worked fine with me, even thought hangouts was new I didn't use it on the Evo). After a while I tried to install Cyanogen on it and it failed (it won't boot and get stuck on a loop), eventually resorting to Venom, which is what she has now.
The phone is so slow it takes the keyboard 10-15 seconds to respond between button-pressing. Swipe is obviously impossible, and the phone sometimes gets stuck on boot. The whole thing is sluggish as hell. I'm not sure what going on, the phone was perfectly fine, and now after 3 ROM it's a piece of crap.
I am going to have the phone tomorrow again and I have permission to wipe it clean and try again. What I need is a ROM that has 4.0 if possible, but what's more important for me is that the thing would work smoothly. Having the 3D camera would also be nice. What ROMs would you recommend? Something that should work for sure? Anyone else have issues with Hangouts maybe?
Thanks, all suggestions welcome.
Click to expand...
Click to collapse
All right bro, so it's good that your phone isn't bricked, and it is just slow, so that's the first good part. I'll give you a couple of steps to help your EPIC (because 3D is epic) phone get into the fastest zone possible.
STEP 1) Flash a well-built, not in beta stages, stable rom like NegaLite-BluRom (/showthread.php?t=1745093)
STEP 2) Flash a stable, overclocked (for you) kernel. The best options are Mirage and ButteredToast. Those are the best and most common. DON'T FLASH THIS KERNEL WITH RECOVERY. Install Flash Image GUI apk on your rom (if you can't install it because of huge lag, try the adb method-check out a list of adb commands)
STEP 3) After flashing and rebooting, install an CPU manager of your choice (CPU Master is free)
STEP 4) Overlcock your phone to your need (this is probably your problem
STEP 5) Enjoy your lag-free phone.
*********************Additional Info:
NegaLite supports 3D (just check out its awesome 3D boot animation)
Its IceCream Sandwhich
It can be flashed with S-ON using 4EXT (install this before installing the ROM)
If possible with you lag, backup all your data and contacts using Titanium Backup (save you some time later)
Hi. i own an HTC EVO V 4G (Virgin Mobile). i used the Search function but sadly didnt found exactly what i needed.
a month or so after activating the phone, i decided to Root, S-off, Flash Recovery, bootloader and a custom Rom. However, its been a while now, that when i do a fresh install i get some inconsistency problems. for example, my first Rom was Harmonia, but later on i switched to MidnightRom. there the problems started to show up. the Sense version was working fine, but then i wanted to try out the Jellybean version. and when i did (after wiping everything, of course) some apps were not working. PlayStore wouldnt let me download anything, Tethering was not working, when using "reboot" the phone would get in a bootloop, which would only go away by removing the battery. and 3D games (Shadowgun, Temple Run, etc.) were graphically laggy. more like, unplayable. the image was distorted to the point it was impossible to see what was going on. messed around with fixing permissions, deleting Cache and Dalvik, re-flashing, and the problem was still there. i tried with other Jellybean Roms (both 4.1 and 4.2) and noticed that the problems were still there. anyways, after deciding to live with the problems (running Wild For the Night). months later i decide to flash MidnightRom again and i see that all the problems are magically gone. to this day ive been running only 4.1+ Roms and i dont have many issues whatsoever. BUT. i tried a Senseless Stock-based Rom the other day (started to miss 3D camera) and it ran well, but the overall behavior of the phone was laggy. it would take longer than usual to do anything. took me about 5 re-flashes to get rid of all the problems. then just yesterday i tried a few other Roms. some worked, though DU was really laggy, and the icons would switch places by themselves at times. as i saw the problem was not going away with re-flashing, fixing permissions and whatnot, i decide to restore to my most stable Flashed Rom.
just to clarify, here is what i do every time im about to flash a new ROM:
Wipe everything except SD card
Wipe Cache and Dalvik
Flash.
Reboot
after i flashed, if something went wrong, or if im flashing something ontop:
Wipe Cache and Dalvik
Fix permissions
Reboot
so question is, is this normal? does this has to do with the phone switching from ICS to JB? or am i doing something wrong?
also, just curious... is there a way one could, say, by some weird reason be "half S-off"? because although my bootloader says S-Off, and i have been able to flash many things, i remember that when doing the Wire thing i experienced many errors, and the thing said it was successful by itself a few seconds later while i wasnt doing anything.
and also, which is the best and most stable Hboot version i could use?
My HBoot version is 1.04.2000 (PG8610000)
Radio is 1.09.00.0706
My Recovery is 4EXT latest version
Thanks in advance