Related
Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Jonnibravo said:
Hi, I recently flashed my phone to cyanogens 3.6.8.1 all was well until yesterday when the phone screen displayed vertical lines like a grey color, the phone could receive calls but from t mobile customer service and it was booting up tho I couldn't see the screen. Then I took the sim card out and the screen returned to normal but was stuck in the splash screen. I reflashed and sometime the next day it happened again, this time I took out the sim card and it went back to normal
Any ideas
Click to expand...
Click to collapse
Could you post a log of this? Could you also provide some more details about your set-up (a2sd? swap? comcache? spl/recovery?) and how did you get to this point (did you wipe before flash? did you run any back-up apps, what were you doing when it happened?)
Once we have that info we should be able to figure it out.
I started out with th jesus freak rom then I decieded to flash the cyanogens 3.6.8.1, I had trouble with the market because I hadn't wiped first, I did that and all was well for at least 5 days. I created an ext2 partition for apps2sd but I'm not sure if that worked. Then on the Saturday 6 days later I put fotmob on my phone so I could keep an eye on the opening premiership season put the phone in my pocket whilst at the football and 2 hours later the phone screen was dead, nobody could call me tho I know the phone was operating and booting only t mobile manage to get through, I tried a reboot, then took the sim card out and the screen went back to normal but was stuck on the splash screen. I tried fixing file ext but came as error asomething about the super block being unreadable tried manually but didn't work, tried backup still stuck, reflashed worked fine for. 20 hours then it happened again this time I wasn't doing anything with the phone no programs other than the usual running in the background, this time I removed the sim card and the phone went back to normal again for about 4 hours then it happened again this time removing the sim didn't work.straight away but eventually it came good again.
Its now 11 15 and its running fine again. I have noticed that I now only have one ringtone (dream theme) and one notification tone and I'm getting a few force closes tho I not sure what they are I will report them if and when I see them
you need to get audio resources and unzip to the sd card all the ringers. search xda for audio resources
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Jonnibravo said:
The screen went dead again at 3pm this time after removing the sim card it stayed the same it was only after leaving the battery off it returned to normal again about 10 minutes later, I am also getting a vending core force close from time to time, please someone help me solve this issue.
P.s I've never actually seen the phone do this it happens when it is in my pocket when I get it out it happens also this time I have not installed any software and it is still happening
Click to expand...
Click to collapse
Because you lost your ringtones, it sounds like your SD card is acting funny, I would format it using this guide (make only 2 partitions for the time being, fat32 and ext3).
See if that works...May be complete reflash with wipe wouldn't be a bad idea neither.
That's all I can suggest at this point, I'll need to see a log to be anymore specific, but try this out, sounds like you've got nothing to loose
Good luck.
Thanks for your reply I am very greatful, I have tried a different sd card without setting up partitions and it still happens. I think the latter is true and a complete reflash is definately the thing to do.
I think this may be a hardware issue because as I mentioned it only happens when it has been in my pocket for a while, perhaps it is overheating or something.
I'll try a complete reflash and let you know if it happens again.
Wipe, re-flash, reformat your sd (or take it out altogether, just to rule it out see what happens... This is all I can tell you....
good luck
Hi guys, I have had a G1 for over a year now, and it has been rooted for that long. I began using cyanogen's mods since 4.1 or so, and they have been rock solid until recently, when I upgraded from 4.2.6 to 4.2.7. Ever since that upgrade, my phone has been "freezing" and rebooting at seemingly random intervals.
First, let me try to define what I mean by freezing: this usually occurs when the phone is put to sleep, and it just refuses to wake up. The screen remains black, however my notification LEDs continue to flash (if they were flashing before). Sometimes, the phone freezes while I am using it; buttons stop responding, and opening/closing the keyboard does not change orientation. The phone usually gradually slows down to a crawl before this type of display-on freeze happens. In both cases, I am able to restart the phone by pressing call+end+menu buttons.
For the restarts: these started happening recently, I'll guess after 4.2.9. This always happen while I am using the phone. It'll pause for a second, like it's frozen, then restart back to the G1 boot screen a few seconds later.
I have tried wiping, repartitioning my SD card from scratch, using the phone without any of my apps installed, etc. The only thing that seems to fix this is if I downgrade back to 4.2.6. I have tried to narrow this down to the best of my ability, but I still cannot figure out the cause. My question is, how can I begin to troubleshoot this? Is there a log or some way for me to see what is the last thing the phone tried to do before it froze/rebooted? Right now, I don't even know where to begin.
well for the phone freezing it MIGHT be too many apps running in the background and eating up CPU usage...download advanced task killer from the market, it allows you to close apps that run in the background.
as for the random reboots, i am almost certain it has to do with the rom you are on. there should be an app called "log collecter" in your app tray, it comes with the rom, try and get the logcat from it when your phone reboots, and send that logcat to cyanogen via the link he provides on his thread.
2 things that I can think about:
1. Wipe you dalvik-cache
if that does not fix it
2. This may be a good time to re-format the ext 2/3/4 partition of your card and do a complete wipe.
I have this exact problem, it first started with random sd card errors "removed sd card" with an sd card inserted, and now the black screen of death, I reformatted and repartitioned my 8gb transcend class 6 card and flashed latest cyanogen. Today I got the black screen again so I used nandroid and went back to cyan 4.0.4, I still got the black screen freeze running old rom but so far sd card is working so not sure what the cause is, bad sd card? I just got this card a month ago... or phone going bad?
yeah, i get the freeze, its usually when i am running multiple resource eating apps. Try advanced task killer for a convenient notification bar click away from closing apps.
I also get the other problem where it wont wake up! Seems like we are running into the same problems under the same ROM. When it doesnt wake up i usually wait a few seconds and try pressing other buttons than the menu button to wake it up when its not turning on. A combination of waiting 5 seconds and trying a different button usually wakes it up.
Hey guys, thanks for the logcat info.
The most frustrating part about this problem is that it is unpredictable; it just happens when it feel like it and is impossible for me to reproduce, therefore I cannot figure out the cause nor can I tell whether or not any changes I make have any effect.
I do have ATK, and I use it regularly. It still doesn't stop this from happening. In fact, I installed ATK in order to try to solve this, which means before this started occuring, I did not even have ATK installed nor did I have this problem.
Can anyone tell if there were any significant changes from cyanogens 4.2.6 to 4.2.7? I see the changelogs, but most of it doesn't really mean anything to me because I don't understand what its talking about.
Yeah I usually get the freeze after installing a new rom onto my htc dream 32a. I just take out the battery and put it back in. Then I reboot and have no problems after that.
try going back to previous rom you had and see if the problem still exists... could possibly be an issue with latest update for rom...
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
I would like to keep this short and sweet so...
Basically heres the low down: I got a G1 almost a year ago, got into Rooting/flashing 7 months ago. I noticed in the beginning almost every rom was giving me a problem, Freezing up, hanging for long periods of time, etc. I eventually found a very nice, stable rom thats been lasting me for about 6 months but as of late was being horrible. Force Closing everytime I got a text message, REALLY Hanging for long periods of time, freezing up. Etc.
So I finally got FED UP, and decide it was time for a change, so I grabbed MLIGN 3.3v having seen so many good reviews and what not, thinking it would be the remedy to my poison. I cried. So in short, here is whats going on:
1. It seems to only wanna cooperate when Plugged into the USB, which, isn't too practical.
2. When not plugged in, it is NOT sluggish, but when loading into apps I've noticed it will hang for quiet awhile or completely lock up to the point only popping out the battery will work.
3. I haven't noticed it yet, but on the old ROM it would randomly shut off during phone calls; which leads me too....
4. When ever I shut the screen off (by pushing endcall) it seems to freeze and lock up and eventually either SHUTOFF or REBOOT into a SHUTOFF of the phone and refuse to turn back on until it has been plugged into the USB, or enough time has passed for it to 'forgive me' and by that, I mean randomly work again.
5: Various other things I cant think of right now.
So, basically thats almost everything. Whenever its plugged into USB though, it works like a charm (for the most part).
Would a problem with my Battery be the case? Which, would be awkward but a possibility.
Or did I just do something wrong?
I made sure to factory wipe the phone twice, even 3 times on the last go, I updated the ENG.SPL and Radio every time I tried to reflash just to make sure.
I partitioned my SD Card for 32MB Swap; 512EXT2 (and 7xxEXT2 I forget what it was) and I also upgraded it to EXT3, which showed some improvement... I believe.
So, I just would like to have my phone working, in a peaceful, obedient manner xD.
Forgive me for the block of text, and all help will be appreciated. Thank you guys... I await sound advice
Try different ROM? See which one works best.
Like me, I found that SuperAosp is best suit for me (see my sig for DEV Site and Download, if you want to try it). It had been running fast and I had no issue, what so ever. Occasionally when I loaded apps that hogged the power usage it gets lags, but still good. FCs are at minimal to none (that's just because of the way I handle the apps). Once in a while I noticed that it reboot, when I tried to use the apps that hogged the memory (maybe that was the apps issue).
Only other thing I recommed is to download a different launcher, because the build-in ADW Launcher does not work too well in my opinion.
Another thing, if you wish to keep the ROM you had. I would suggest to change the partition size. (IE: Catch [128MB]/Ext 2 or EXT 3 [1024MB]/ FAT32[the rest]) Now I know other people might say that it's overkill, but to me my G1 performance it great.
I've tried multiple roms as of late, and the one I like the most does happen to be MLIGNs... everything seems to be working correctly for the most part with the exception of what I listed above... Now on the like, 23rd reboot most of the sluggishness that was there before is gone, and everything is pretty much being cooperative, with the exception of like the weather, which isn't updating properly but I can live with that. What I cant live with is the fact that this ROM when not plugged in, will freeze up when in the lock screen, a few minutes after it has darkened and gone black and wont respond at all. Or I'll unplug it and just do a test, swipe left, right for a good minute or two, go into apps and It'll just SHUT OFF. Maybe it really is the battery? I'm unsure. When I look at the battery it does look quiet bloated... I am unsure...
I'm gonna try to set it to what you recommended, and see if that works...
I don't think it's the battery.
Have you tried reformat/partion your SD card (be sure to backup your data first). See my last comment on sizes recommendation for each partition.
Also check on the swappiness setting.
Mhm... so I went back and followed everything you told me to do, including repartitioning to the exact file sizes you told me. (Also I'm guessing Cache meant Swap) So I set everything up and its really blazing fast and stable.... until I remove the USB cord. Then it shuts off, freezes at lock screen when the screen is dimmed to black, and will just randomly shut off while doing things (especially when trying to get into messages)
Also if it helps, I have a Class 2 8Gig SD card, and my Recovery is Ra 1.5.x(I forget.) I'm completely confused... I dunno what to do... I would really like this to just work and stop being a hassle D:
Hmmm, Try reading this thread, http://forum.xda-developers.com/showthread.php?t=1010932
See if it helps.
Nothing :/ Its okay... I'm gonna go play around with other roms, completely re do my phone, make sure everything is updated etc. Then go from there.
Thank you anyways, you were a big help, reguardless of my phones triumphing retardism
Hi guys,
So I've gone on the HTC website again and looked at the specs of my HTC HD7 (as I have done many times before, e.g. when I was finding out the official "spec" for GPS on the phone - related).
Anyway, it seems that HTC have recently made a change to the specs page, they have split the internal storage size spec - 8GB for Europe handsets, and 16GB for Asia. I am 99% certain this was not the case a few months ago, it used to just say 16GB.
I happen to have 2 HTC HD7s (one bought from O2, one purchased offline, both acquired within a few weeks of each other - around Feb/March time this year):
Both boxes have the same P/N as each other, and also same model barcodes (6HTGD7XN)
Both boxes have identical specifications printed on them, also identical packaging and contents
Only discernable difference between them is that the O2 handset has a silver kickstand bed and the other handset's kickstand bed is orange.
Frustratingly, my O2 phone started its dying process after the Mango update. It never misbehaved before. Slowly and intermittantly at first, I would get random reboots, giving me "Memory card not working" error screens, setting itself as incorrect time, and even wiped itself a few times (meaning I had to reconfigure everything from scratch). I searched all over the net, checked and tried all sorts of remedies suggested on forums, e.g. doing a full factory reset, uninstalling all the HTC apps, disabling location services, disabling 3G/data connections, etc. Also I hadn't played any music with it since the Mango update either, so it wasn't the music player for which some people reported problems.
Sometimes the phone could go 12-18 hours without so much as a hiccup, and other times it would crash and reboot within a minute of starting. My SIM card has a PIN on it, so I always knew if my phone had rebooted itself. On average I'd say it happened a 2-3 times a day, though some days it would happen 10+ times.
Keeping my data connection turned off and only using Wifi seemed to keep the crashes at bay for several days, at least until today. I'm a fairly tolerant guy, but today was the last straw.
I was playing a new game I downloaded (Jewel³) when travelling to work, when suddenly it crashed and rebooted just like it did so many times before. I rolled my eyes and waited so I could carry on with it until the next crash, except instead of the usual process of booting up and acting normal, it kept crashing and factory resetting itself, asking me to configure the phone for the first time after every single crash/boot. That was it, now it was well and truly buggered. I took it to the O2 shop and they have now taken it in for repair. I assumed the memory card somehow developed a hardware fault, though the timing of when these issues started happening seemed too coincidental with the Mango update.
This is where my spare HD7 comes in handy. I've barely touched it since taking it out of the box brand new about 8 months ago (was meaning to sell it but never got round to it). I threw in my SIM card and began the update process using Zune. All updates successful etc but then afterwards I suddenly noticed the bottom of the Zune window. I went into the phone "about" screen, yep, 8GB total capacity, even though the box says 16GB.
So what I'm thinking is this: does the Zune Mango update patch actually recognise I am in Europe and try to flash the phone into only utilising 8GB? Even if the memory card has a physical capacity limit of 16GB?
If that's what happened to my first phone, that certainly explains the random rebooting behavior and memory errors, as I probably had parts of my data occupying the space which the Mango patch told the phone to ignore.
Just a hypothesis, anyone here got a 16GB HD7 in Europe which had a lot of data on it pre-mango, and had any similar problems afterwards?
It would also be interesting to know if you fall under this category and haven't had ANY issues since mango. I would like to try getting to the bottom of this, as my searches on the net seem quite fruitless (this was the best thread I could find, though I couldn't reply as I'm not a WP7 developer)
Mango is more sensitive to SD card timing issues... Check out the how to upgrade your phone to 32G in the general section... I benchmarked the factory 16GB card, a 32GB card that wouldn't work (constant reboots) and a 4 year old 8GB card... all Sandisk Class 4.
the 8 and 32 are undeniably not going to work, the FACTORY card is marginal, and I have been getting occasional reboots since upgrading to Mango. If I downgrade to NoDo, the reboots cease.
Ah ha, very interesting, and that certainly explains a lot. I wonder if my "repaired" phone will still suffer the occasional crash like your 16GB did. Would be nice to see which make of memory card they use (assuming they will replace it), though I don't want to void my warranty doing it!