Database Info

Virtuous v0.8.1 (Vision) Troubleshoot! Help please! :)

Hello everyone, I successfully managed to Perma-Root my T-Mobile G2 as of this morning.
When I first installed this ROM (Virtuous v0.8.1) I really had high hopes for it, however when I first installed the room via clockwork reboot, I just clicked for a backup of my Stock OS - no clearing of data or cache files.
Upon the completion of the ROM my phone promptly rebooted. The whole process of rebooting took alone 5 minutes (at least) and I started to get weary seeing has how my phone stayed on the home HTC Screen (Boot-up Screen) for quite a while. And just before I was thinking of pulling the battery because it seemed as if my phone froze, it launched. However in doing so, everything appeared extremely laggy.
Everything was force-closing, constantly, even after I said to force close the program. It made it absolutely daunting, and I wondered what the hell did I do my phone! It was extremely irritating to navigate back to ROM Manager and hopefully be able to restore my phone back to normal. Eventually I ended up rebooting my phone to it's original status, and decided perhaps it was just all the previous apps and data on my phone causing all the aforementioned complications.
However I felt as if I should try again with Vision (Or what I believe to be the Desire Z Rom for my G2) and decided to clear all data on my phone when prompted - as well backing up my data for a second time.
In doing so, the restart process went smoothly as before. Then came the reboot/loading of my phone, and the screen didn't appear nearly as long. So there was a sigh* of relief there for me. My phone loaded and every thing appeared to working just fine and dandy - albeit with the expense of virtually all my phone data (Besides data that was obviously kept on my SD Card). Thus I was getting quite content with Sense and I actually kept it. Since I was extremely tired as I installed Sense/Rooted my phone very early in the morning (and since it's winter break for me, my sleep schedule has seemingly reversed) I decided to go and sleep.
Waking back up now, I decide to test some things, and ensure everything was going well. I sent a couple texts out, browsed the web, watched YouTube, and everything appeared to check out as running the way it should - except text messaging.
I was completely baffled as to why no one was replying my texts - I thought well maybe since it's New Years Eve people must be busy etc. No Harm done there right?
So I decided to pass it off, only to realize that hours later I receive several responses from the people that I've texted/new text massages from other friends. Yet they're hours behind!!!!!
Anybody know what's up with that? It's basically impossible for me to hold a conversation via text message on my phone now as messages are greatly delayed. I never had this problem with my Phone using the Stock OS of my G2, yet as soon as I install Sense this problem arises (and apparently it's Android 2.2.1) I could have sworn my G2 originally was 2.2.2? I'm sorry I'm just barely starting to get in the whole process ROMs/Rooting my phone, and getting more interested in Android.
Is there a specific Desire Z allocated ROM Designed for the G2? If so can someone please point me towards it? The description for the Virtuous Rom read to me that it was a Desire Z Port - so I thought I was downloading the correct thing.
However I'm sure if I'm having this problem, other people might have come across this problem? I mean it's no biggy for me to reflash back to Stock, and pretend everything is the same way it was - but I'm really taking a liking to Sense, and I want to see if there are at least alternatives - or perhaps I just installed the wrong ROM.
Thank you for your time!

Help analyzing ramdump.log

I have not been having these ramdump.log (essentially random rebooting) for some time, and whilst i've noticed that some apps seem to cause this process, I have not installed anything new for a while, other than updates to existing apps.
I have once again started to get these upto 3 times per night when the device is in deep sleep. Interestingly, each morning when I turn on the device, wireless internet is switched off (option unchecked), and I have to go into the settings and re-enable it.
Someone previously suggested that maybe it's faulty RAM in my TF? But how would I know that is not just a random guess? Also, my partner also has a TF, hers is the B70 (one of the lucky ones that are able to be rooted), and she gets ramdump.log on the same ROM (Prime with stock kerne), so it's perhaps less unlikely that both tablets have bad RAM? My TF is a B50.
Appreciate if anyone can help identify the issue from these 2 ramdump.log (I had 3 during the night!)
Thanks!
http://db.tt/0PB5lILB
http://db.tt/DDBzVKO9

I've been having the same problem for the longest time, and it always comes and goes at random. It seems to be a common problem that gets resolved with an RMA, but given the inconsistency of the problem between ROM updates, and the fact that I seldom see RAM go bad I refuse to mail it in before doing a proper memtest (which for now I am not sure if there is an option for that).
It seems to me that the transformer just has a very picky kernel.
Currently on Prime 2.0.7, been having this issue since I first started using it at 1.9.1. Wipes temporarily alleviated the problem, except for one time that I used the wrong kernel.

I'm the same... Some days nothing, then others 3 within an hour! I found an application for stress testing, and I'm running it overnight.
http://www.appbrain.com/app/com.into.stability
Been going for an hour now with no issues with cores or memory, so maybe it's just some kernels don't like some devices? It's really annoying.

[Q] But really...what's with all the random reboots?

Hi all...first time poster, long time reader. (Mostly because someone has usually solved my problem for me six months in advance.)
My Inspire has been rebooting at random for about the last six months. The rate varies from once every couple of days to once every couple of hourse. Most of the existing answers are "replace the battery." I think that makes sense in cases where phones reboot while under strain (watching a video, during a call, etc.) because higher current draw would pull down voltage if a battery is failing. Not in my case, though. About 80% of the time that I notice a reboot, the phone is either in a pocket or on the desk.
For a few days I thought that I had solved it by removing the Facebook app. I had noticed a correlation between using Facebook at the phone restarting, and not using Facebook really did seem to make a difference for about a week. (Upon further investigation, that seems to hold across different ROMS. This has been happening with the stock rom, Ice Cold Sandwitch, and JellyTime.) But it isn't 100% better. I currently get about one reset every two days that I notice, and probably more that I don't notice.
That leaves me wondering, what could be going on? Is my hardware borked? Should I try flashing a different radio? I have had this phone for about 22 months and it would be nice to hold onto it a little while longer. Otherwise it has been a reasonably decent device.
-Tim

ZircularLogic said:
Hi all...first time poster, long time reader. (Mostly because someone has usually solved my problem for me six months in advance.)
My Inspire has been rebooting at random for about the last six months. The rate varies from once every couple of days to once every couple of hourse. Most of the existing answers are "replace the battery." I think that makes sense in cases where phones reboot while under strain (watching a video, during a call, etc.) because higher current draw would pull down voltage if a battery is failing. Not in my case, though. About 80% of the time that I notice a reboot, the phone is either in a pocket or on the desk.
For a few days I thought that I had solved it by removing the Facebook app. I had noticed a correlation between using Facebook at the phone restarting, and not using Facebook really did seem to make a difference for about a week. (Upon further investigation, that seems to hold across different ROMS. This has been happening with the stock rom, Ice Cold Sandwitch, and JellyTime.) But it isn't 100% better. I currently get about one reset every two days that I notice, and probably more that I don't notice.
That leaves me wondering, what could be going on? Is my hardware borked? Should I try flashing a different radio? I have had this phone for about 22 months and it would be nice to hold onto it a little while longer. Otherwise it has been a reasonably decent device.
-Tim
Click to expand...
Click to collapse
Tim, random reboots can occur due to lack of memory. See if your internal memory is almost full. In that case, try deleting some apps or sending a couple to he sdcard. Take into consideration, that not all apps work fine from the sdcard, so just send the ones you like less...BTW, are you rooted or just stock?

glevitan said:
Tim, random reboots can occur due to lack of memory. See if your internal memory is almost full. In that case, try deleting some apps or sending a couple to he sdcard. Take into consideration, that not all apps work fine from the sdcard, so just send the ones you like less...BTW, are you rooted or just stock?
Click to expand...
Click to collapse
That's an explanation I had not found. Internal storage looks OK in my case, with 701MB currently available out of 1.13GB. If it matters, the SD card currently shows 3.86GB avaliable out of 7.39GB. (I have tried with and without the SD card, and it doesn't seem to matter.) Maybe I should increase the free memory setting?
To answer your question, the phone is currently rooted and running IceColdSandwich 8.8 AOKP. If anything it reboots less frequently in the current configuration than it did on the stock ROM. I have not tried any Jellybean ROMs for more than a day at a time, so I'm not sure if that would be better.

ZircularLogic said:
That's an explanation I had not found. Internal storage looks OK in my case, with 701MB currently available out of 1.13GB. If it matters, the SD card currently shows 3.86GB avaliable out of 7.39GB. (I have tried with and without the SD card, and it doesn't seem to matter.) Maybe I should increase the free memory setting?
To answer your question, the phone is currently rooted and running IceColdSandwich 8.8 AOKP. If anything it reboots less frequently in the current configuration than it did on the stock ROM. I have not tried any Jellybean ROMs for more than a day at a time, so I'm not sure if that would be better.
Click to expand...
Click to collapse
Sounds to me like your hardware is bad. I have had my Inspire 4g for two years and the only issues I have had was maybe three apps force closing. I have never had the phone its self freeze or reboot. I have tried all kinds of ROMS and right now I have 4 regulars I stay with and alternated monthly. I Use Energy, Revolution, Smart Droid Red venom edition, and JB 10.1. All those ROMS are stable and cause no issues as you have described.
So from a tech view if I had your issues and it happens with all ROMS then that leaves only the hardware to be at fault.

unable to start camera

so prior to being on venom 4.2, i was on venom 3.xx. i had no problems prior.
i flash 4.2, and had no problems related to the camera not working. i had other problems though, after reflashing 4.2 those problems went away, but now a new problem came up.
after a restart, i can use the camera maybe once, or take one photo. after that, the screen through the camera will be frozen on screen. i can still take pictures, but it will only be off what is on the screen. after closing the camera, or force closing it,upon trying to open the camera app again, it barely loads, then force closes automatically and i get an "unable to start camera" bubble on screen. i can see only the grid outline of the camera, off center and such very briefly ontop of my wallpaper.
i can do a reset on my phone, and resume taking pictures, sometimes i am fine to continue, other times its the same problem. this is a very common recurring problem for me.
looking at my apps, i see 2 cameras installed, one is the new 5.0, and the other is the old 4.xx camera. i have frozen the 4.xx camera before through titanium, and it doesnt fix it. should i uninstall the 4.xx camera altogether?
subsequent reflashing of this rom doesnt fix this issue. and i dont know what else to do rather than reflashing the rom from a blank slate. previous reflashings have been on top of the current rom.
i would rather not have to start new as this phone has crappy amoint of space, and i cannot back up all my apps and settings.
i dont know if it is kernel related. prior to 4.2 i was using elemental x, after 4.2 i switched to beastmode since i wasnt soff.
is there perhaps a way i can manually start the camera through root browser?

If you've got both versions of camera in your app drawer I'm guessing you dirty flashed the ROM, which has most likely caused your problems. Clean flash the ROM and see if it fixes your issue. This is why I'm totally against dirty flashing anything.
I don't understand how you don't have space to back up your apps, I have a backup of every app I've ever used and still have tons of space left over. The fact that you mention backing up settings troubles me, restoring system settings after flashing a new ROM will more than likely cause problems for you.
When you're flashing a ROM don't do it the lazy way, do it the right way, perform a full wipe (cache/dalvik cache/factory reset/system) and start clean. It only takes a few minutes to setup your ROM from scratch. Restore your apps but don't restore any system data.
Sent from my Evita

thanks for the reply.
as suggested, I did a complete reset. wiped the caches, factory reset, and system reset.
installed from scratch. But i am still having the camera issue?
now its just not loading at all. black screen, then close. no error message. and no unable to start message.
could it perhaps be a hardware issue at this point?
without restoring anything, under apps, I still see two instances of the camera app. one at 5.1, and one at 4.2.2. can anyone confirm this is normal?
the only thing out of the ordinary, within the past few months, my phone has been getting crazy hot at times. specifically right below the lens of the rear camera. I was getting this heat from charging, or even certain apps. Definitely attribute that to the age of the phone. as apps that ran smooth when the phone was new, no longer are so.
I dont know if the heat can cause hardware damage?
also, not sure how relevant this is in the context of my situation. but apps that use the camera do not work either when the camera is needed, such as snapchat and instagram.

Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita

timmaaa said:
Since the clean flash did you at least end up with only the more recent version of the camera in your app drawer? You could be looking at some kind of hardware malfunction, or even a problem with the ImageSense proprietary chip that is utilised to operate the camera. The fact that the camera works sometimes would suggest that all is not lost. Have you tried flashing an aosp ROM to see if anything changes? I'd suggest trying that, and if that doesn't work you should try running an RUU to see if a completely stock setup will help.
The phone heating up near the camera lens isn't abnormal for this device. The amount that it heats up can change significantly depending on the ROM/kernel that you're running. You should definitely try not to use CPU intensive apps while the device is charging.
Sent from my Evita
Click to expand...
Click to collapse
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.

chinaman_chong said:
no, the clean flash still left both cameras in my "manage apps", i have never seen two camera icons in my app drawer.
as of right now, i cannot get the camera to run in any way. even with a reboot. The only reason I really did the clean reflash, was because the camera wasnt working at all today. I did a bit more digging around, and it seems like this is a fairly common problem for the one x. there seems to be quite a few people, even on stock roms, that cannot seem to remedy this. and a few have chalked it up to a hardware problem, some have been confirmed, and others not so much.
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite. Thank you for all your help timmaaa!
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
There's nothing wrong with this phone. Given the right amount of knowledge and care the thing doesn't skip a beat. Even though there is no such thing as a soft brick (a phone is either bricked or it isn't), whatever it is that people experience in those so called "soft brick" instances is caused by user error 99% of the time. I've seen it time and time again.
Any phone available on the market can experience any amount of issues if it isn't handled correctly. You got unlucky and your camera is most likely shot, but any other problem you've encountered comes with the territory of flashing unofficial firmware and software, it isn't anything wrong with the device itself. These are possibilities you need to be comfortable with if you're going to modify your device.

Yea, I assumed there were gonna be risks when I rooted my phone. Dont know if any of the issues I had were related to rooting or not.
The soft brick scare I had was due to a flash that went wrong for no apparent reason.
another update on my phone. I noticed my front facing camera has no issues whatsoever. unluckily for me, I cannot even access my camera, to toggle to the front facing camera to even attempt to check it out. Instagram also does not allow me to switch either, it just gives me an error saying it cannot connect to a camera, then closes. snapchat's rear facing camera is just a black screen for me, but it doesnt force close, so I am able to toggle to the front camera, and it works just fine.
is there a setting or something I can modify, for now, so the front facing camera is the default?
my brother's one x recently went out this year too. I am gonna try to salvage his camera, and see if it will fix my problem.
I have not taken apart this phone yet, is the camera soldered or held in with connectors?

Have you tried an RUU yet like I previously suggested?
Sent from my Evita

chinaman_chong said:
I really dislike flashing this phone. ive encountered so many hiccups and scares(mainly a few soft bricks here and there). I really prefer the "if its not broken, it doesnt need fixing approach" here, granted my camera is shot.
one of the reflashes today was giving me wifi errors with wifi not even turning on. I really want to avoid potentially more problems, unless a fix is deemed more definite.
Click to expand...
Click to collapse
If a couple hiccups and scares are too much for your, then it might be that modding phones is not for you. These types of things happen time to time to even those experienced with flashing ROMs. Occasional setbacks and troubleshooting is just part of the game. If that is too much for you, than don't play.
As timmaaa already mentioned, failure to boot is not the phone's fault; and its almost always a matter of user error and not following the procedures properly.
chinaman_chong said:
im just in need of a new phone now. so many problems, and so many things the phone can no longer do effectively. random reboots, overheating, battery life, even the charging rate. this phone has become crap. Ive always hated the lack of expandable memory. I really dont know why I didnt choose a different phone over this at the time.
i really like the htc one, but i feel like many of the nuisances in the one X will follow over.
Click to expand...
Click to collapse
Random software errors like random rebooting, overheating, etc. are often easily remedied with the proper steps. They are likely not issue with the phone itself, but rather a result of improper steps while flashing the ROMs. I've flashed many ROMs on this device, and have never suffered any such issues that I couldn't solve easily.
As for your other complaints about the phone (lack of expandable memory, why you didn't choose another phone), I don't know why you even posted them, as they are not constructive. Those still on this forum are mostly here because we love the phone and remain loyal to it. Your comments aren't going to help your issue, and will only annoy fans of the device. Better to keep such comments to yourself.
If you hate the phone so much, go buy another one and be done with it. But crying about it isn't going to solve anything.
I would suggest you follow timmaaa's advice, and flash the appropriate RUU to "start over". S-off is highly recommended before RUU, as running certain RUUs with S-on and SuperCID will brick the phone.

I have the same device and the same problem.
It doesn't depends of firmware or kernel or camera app..
I thought it's hardware problem but it is not. Because i was changing the camera module and it doesn't helps((
Don't know what to do with this issue(

Nexus 5 - wifi stuck on 'turning on WiFi'

Hi everyone.
First off, I'd like to say that I don't like opening new threads, and I always read up on my problem first, but I'm simply at my wit's end.
The problem is fairly common (not only on nexus 5 phones), and something a lot of you forum guys have encountered and tried to help with, with more or less success.
Basically, my WiFi doesn't work, it shows 'turning on WiFi' most of the time, and sometimes (fairly rarely), has a couple of hours where it reboots to no end, but I'm thinking that's a power button that sticks. It usually fixes itself after I gently but firmly stroke it (lol) and doesn't happen again for weeks. The WiFi issue started randomly, totally out of the blue, and never happened before to any of my phones (it might have started a couple of days after the last OTA security update, but I can't say for sure). The phone was a 100% stock 16gb Nexus 5.
What I've tried (some steps even multiple times, with different variations):
- removing the sim card
- switching airplane mode on/off
- factory reset (3 times in total think)
- wiping cache
- reflashing stock ROM
- reflashing stock everything
- flashing TWRP and rooting, and manually changing/removing either the .macaddr and .btaddr files, or changing/removing their respective folders
- playing with ownership of those files
- flashing CM, flashing a custom kernel and flashing Paranoid Android
- all in all, i've wiped and rebooted the device like 50 times
Honestly, I don't know what I've missed, I've been at it for days, and I'd be very grateful if someone would point out an oversight.
Also, what's weird, my bluetooth didn't work too, but after i tinkered with .btaddr and .macaddr, it now works perfectly, no matter what I throw at it. This is what gives me hope that I still can resolve this issue without paying for a new motherboard/phone.
Thanks in advance, guys, you've been truly helpful so far.

A defective wifi chip could be the cause of the problem and, in my experience, is not that uncommon. I have come across two n5 and two Samsung s4 phones that work perfectly except the wifi either won't turn on or tries to turn on for about 10 minutes.
I tried different modems, bootloaders, and roms without any success.

Yeah, sadly, that's what I'm thinking too. I had some hope because bluetooth works, but not anymore. I've kinda already made my peace that I'm gonna have to spend +$200 on a repair or $400 on a new phone. I'm just thinking if anyone knows something that helps that I haven't tried yet, please come forward, possibly before I take it to a service centre :laugh:

Maybe look for a used N5 with a smashed screen and working motherboard?