Database Users

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.

Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?

lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...

The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...

I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.

BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...

I wonder if it found one of those radios and did something with it?

For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.

hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.

lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Black screen on wakeup? Please help.

Ok so I'm having issues with a black screen on wakeup. The phone's still on and it's sleeping but hitting the power button won't bring up the lockscreen, so I have to pull the battery and restart the phone.
I'm on DK28 and I was running Mammon's Bonzai ROM. I thought the issue was ROM related so I flashed the previous version of it, but same issues. Continuing to think it was ROM related I flashed Nebula ROM. Same thing.
Could this be caused by LauncherPro? It's the only constant between all the ROMs I've flashed because it's one of the first things I load up. Could it be any other apps that I have loaded on the phone?
Any help would be much appreciated.

So I uninstalled LauncherPro but it seems I'm having the same issue.
I'm out of ideas.

it's got to be a dk28 bug because I was having that problem as well from a fresh dk28 install. It also happens sometimes on the roms i mess around with. (dk28)

I've done some playing around and come to see that I can turn the screen on and off as many times as I want when I first load up. The issue doesn't begin until gmail backs up all my apps and I set up my phone the way I like to have it. So I know it's definitely application related.
I'm starting to have an inkling that it's being caused by Taskkiller. I remember someone posting something about not using task killers with Froyo but I can't recall where or the reasons why. I'll try not running task killer for a while and see if this might be the cause.... if this doesn't fix it I have no idea what to do...

Problem with touch-screen not functioning?

Hey guys,
So I loaded RubiX a while back and after getting everything all fancied up the way I wanted it my phone decided that it doesn't like when I touch it (touch-screen stopped responding, the hard keys still worked fine, but I have to serious hold screen-keys down to make anything happen).
I thought this problem was just something in the ROM that my phone didn't like, or a bad setting I changed, so I tried out Liberty ROM (which, by the way, is AWESOME). After getting everything completely made for the Liberty ROM, the exact same thing happened.
In a fit of frustration I decided to start from scratch, root and deodex, then load all my fun settings (like the de-throttle and imoseyon's memory changes) and it all started doing it again. Is there something I don't know about the way the screen works?
Another interesting fact: While I was trying to figure this problem out with my phone (stock with root/deodex and imoseyon's changes) I unplugged it from charging on my comp and now it's running pretty smoothly again... I've been having this problem all day, restarting and clearing cache / loading different ROMs and running restores didn't do anything... this is really strange!
Any idea what this is / has anyone experienced it before. I was just about to call Verizon and reset my phone to stock to get an exchange.

Try running a ROM stock and see what happens. Could be an app...

zehk,
I've tried every combination, including running to stock...
What I know now is that it only happens when phone is charging from a computer... The touchscreen goes completely brain-dead...
Any ideas?

I've had a problem when charging my phone from USB before. Someone said it was the drivers on my PC... might try a newer or older version depending on what you have.

That's an odd problem. Seeing how you have tried to troubleshoot your issue, trying the PC Drivers might indeed help as suggested by zehkaiser.
I would recommend downloading Motorola'as MotoConnect. It's the only driver I use for any Motorola device I hookup to my computer. You can download it here. Hope that helps and if not, sounds like you will have to do a .340 SBF with RSD Lite or the maderstcok zip 340 and return your phone for a new one.

nope
It's not the drivers either, I've now realized that it's happening when I plug into the wall too. I thought that might be due to using an old palm charger, since it's slighty higher amperage, but it turns out the standard moto charger still causes this problem...

My DX does exactly the same thing after unplugging. Any ideas?

Reboots, can't call, no sound!

My nexus 6p has worked fine for months however I woke up yesterday morning to find it would not play a video on YouTube. Continuing to use it I noticed the following symptoms:
Wont play videos of any kind (youtube, Facebook etc)
Speakers do not work at all
phone hangs and will not connect during incoming or outgoing calls. The call may connect after several minutes of the screen hanging on the blue calling screen however speakers don't work anyway.
Phone restarts itself randomly
I have tried a hard reset from recovery, wiped cache, booted to safe mode etc with no change.
The phone is bone stock and has not been rooted.
Any suggestions?

At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.

Same problem here.
teh roxxorz said:
At this point I'd try rooting and just flashing stock ROM, don't install anything and see where it goes. If it survives, then maybe it was a rogue app, but that's a lot for an app to do - so it could be a hardware issue.
Click to expand...
Click to collapse
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.

Yakksiek said:
I've got the same problem, but it happens only on stock, when I've got Chroma installed, everything is fine. One time it happened under Chroma. I don't know what causes it. Reinstalling factory images or even 7.0 doesn't help. Custom kernels didn't bring any improvement either.
Maybe there are some music drivers or something.
Click to expand...
Click to collapse
It could be a driver thing. Didn't look like a device issue, as it'd be constant. I would go back to stock and note when it happens and then flash a custom ROM and repeat the steps, to perform a controlled test. While doing so, take logcats so Beans / others can review them.

Gone to the service becuase even on a custom ROM I couldn't get any sound. They said that it was a hardware problem (I don't agree but we will see).

Random Reboot Help

So I have spent a lot of timing trying to figure out the lag on this phone after a bad experience recently with a custom ROM I changed my approach. I went back to the latest stock odexed ROM and I decided not to install xposed as unfortunately I have noticed it has added lag to my system after installing it multiple times.
However now that I have everything setup the way I want the phone is finally buttery smooth without any dirty hacks but now I am getting random reboots. I don't even know how to troubleshoot this problem I thought some apps might be to blame so I tried disabling a few but that didn't help. Worst part it that it is truly random no one situation seems to cause it. It will even happen when I am not even interacting with the phone at all for several hours.
I am rooted. Tried systemless but when I told TWRP not to write to system it would not honor this setting when flashing and always installed in system mode so I had to install a modified boot image. I'm not sure if that could potentially be the cause of my issue but I am really getting annoyed with this. I am just confused about the best way to try and troubleshoot this issue. Any advice is welcome

I too have a similar issue. My phone randomly shuts down(not reboot) whenever using any random app. Sometimes i get a battery indication of 0% and sometime it just shuts down. Very frequently aswell.

Are you getting anything in last_kmsg? When kernels crash they're supposed to write to it, but it doesn't seem to be there after 100% of crashes.
Check it with:
Code:
cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Or by using an app like syslog.

Hmm with the command im getting "no such file or directory" and syslog is telling me i dont have root access or the commands failed.. hmm

tainger said:
Hmm with the command im getting "no such file or directory" and syslog is telling me i dont have root access or the commands failed.. hmm
Click to expand...
Click to collapse
Sorry. It's not always there even after a crash.

Welp now my phone does not power on / charge. I believe my phone has bricked itself or somehow the battery connection is loose. What are the chances that this is hardware related and the connector is Loose or disconnected?

You tried a different charger?

Yep, I've tried a few(0.8 amp, 2amp, computer) None seem to work and the phone doesnt get warm from charging.
I've seen that if you physically disconnect the battery connector and reattach it will fix some software issues. But i dont want to break apart my bamboo back