yashsingh1/xdaforums huggingface dataset:
[HTC Vivid, Raider, Velocity] HeetMon:
Some have bad batteries.

Mine started doing the same thing. For a while I thought the battery life on Vivid was horrible compared to the Aria I had at the time. Then it progressed and one day finally quit completely and would not take a charge from any charger I had. So, being a techhead I decided to probe the battery with a multimeter and it showed very little voltage, so low I guess the charger wouldn't even recognize or try to charge it.

So what I did was take a battery charger I had for a walkie talkie radio and touched the leads to the battery for 3-5 seconds or so, put battery back in phone and it would then charge. I did this a few times until I could get to ATT store and the guy ordered a new one through warranty. Haven't had a problem with the Vivid since.
[HTC Vivid, Raider, Velocity] krekol:
Same Problem

Last night I pulled my battery at 21% after shutting the phone off to clear the memory. I put the battery back in and put it on the charger, I tried to turn the phone on and nothing. It is not showing that it is charging. I have four batteries for this phone and none of them will turn on the phone. I am at a loss here. The phone was working fine until i shut it down and removed the battery. Any ideas on what is causing this or any way to force it to turn on.
[HTC Vivid, Raider, Velocity] lowfatmilk:
That sounds like a royal pain.

Could it be the changer or its USB cable? Work some contact cleaner into the power button?
[HTC Vivid, Raider, Velocity] stuffed_tiger:
I'm having this same issue. I'm not sure if it's the battery, since the phone boots to bootloader just fine. But the battery won't charge when the phone is off (red light comes on for a second, then quits) and I can't get past the HTC screen booting to ROM or recovery. Where is a good place to buy a battery?
[HTC Vivid, Raider, Velocity] krekol:
Even if the power button was bad the phone should still charge a battery. I have a charger that will charge the batteries without the phone so I know the batteries are charged. I have several different chargers and none of them will show the phone charging. I even tried connecting it to my computer. The phone is dead, I guess I am going to have to crack it open and see if anything has come loose inside. I really like this phone and am going to hate loosing it. I paid a lot for this phone. That shinny penny I paid to get this phone was my favorite.
[HTC Vivid, Raider, Velocity] lowfatmilk:
Have you tried plugging the phone USB into a desktop and using that to try rebooting the phone into bootloader or recovery?

Hasoon2000's Vivid All-In-One Toolkit in the dev section can do that pretty simply. i used an earlier version of that to unlock the phone a year and a half ago.

i don't remember if the phone has to have debugging turned on for the desktop to feed it commands.

Even if this works i dunno whatall it'll prove.

i like this phone too a lot, and am sorry yours seem to be having hardware problems.
[HTC Vivid, Raider, Velocity] rignfool:
That sounds like you lost your boot image... try flashing a new one that you know works... and if it won't charge with power off... sounds like you have CWM installed... switch to twrp...
[HTC Vivid, Raider, Velocity] krekol:
The phone does not turn on at all so getting to the bootloader is impossible. It does nothing. Does not even charge a battery. .
[HTC Vivid, Raider, Velocity] lowfatmilk:
That's the definition of a bricked phone, was what i meant. No screen, no led, no button function, no sign of life, and from no explicable cause.

Android phones don't have real on-off switches that directly disconnects the phone from power. Its failure to manifest signs of life doesn't absolutely indicate irreversible hardware failure. There's a bit of a chance it's firmware.

Aside from the power button, Android phones can be controlled thru the USB port.
[HTC Vivid, Raider, Velocity] krekol:
I took your advise and plugged the phone into the computer and left it over night. This morning I rebooted the computer and the phone screen lit up. I got all excited and tried to use adb to reboot into bootloader, Of course the phone was not found. I took the phone off the cord and the screen shut off. I pushed the power button and the screen lit up. Let go of the power button and the screen goes off. I tried another usb cord and now the screen no longer lites up. Maybe there is hope for this phone.
[HTC Vivid, Raider, Velocity] rignfool:
If the screen lights up like that... there is power to it...

Sounds like you have dirt in your power button... or the button isn't making contact...

Time to disassemble and check the power button...
[HTC Vivid, Raider, Velocity] lowfatmilk:
Yeah, that part where the phone was seen by the desktop, and then not, can have something to do with the Windows drivers. Most of the folks on these forums know what's with this stuff better than me; i usually have to tell windows to stop the hardware, disconnect and reconnect the phone USB and start the connection up again, every time before i do one set of commands, like put the phone into bootloader and download a kernel image into it.

There's a Vivid unbricking project over in the dev subforum, you must've seen that. Whether or not you get your phone working again, i hope it'll be a productive journey for you.

i was perfectly happy just messing with apps until i bricked my tablet; that got me into all this device unlocking and rom burning and fun stuff. It's too bad the Vivid isn't simpler to hack.
[HTC Vivid, Raider, Velocity] mydos1:
my phone cant boot to desktop after i flash the kanel

my phone cant boot to desktop after i flash the kanel please can you help me
[HTC Vivid, Raider, Velocity] cmerlyn:
9 times out of 10, if the phone will not turn on at all it is the battery. For some reason, the Vivid will occasionally stop seeing the battery. I have fixed this on mine when that happened by using an external charger. That worked because my battery was actually OK, the Vivid just wouldn't charge it or even see it. Once it was charged it was fine. If your battery really is dead (sounds like it might be the case), get a new battery. There is a 2000 mHr battery on Amazon that is not too much worse than the original (when new).
[HTC Vivid, Raider, Velocity] Orizence:
I had the same issue once, it turns out that I fixed it using a external charger
[HTC Vivid, Raider, Velocity] 1zacster:
a thing that works for me fixing things that don't charge is forcing the batteries to hold a charge. Either A- manually connecting the wires to the battery for a few seconds, then charge it normally (over usb with it in the phone) B- get a high wattage charger (meaning around 1000-1500mw) and then plug it in an unplug it a lot (10-20-30 times) until it holds a charge normally while charging. This only works for batteries that aren't worn out and have been used beyond their minimum.
[HTC Vivid, Raider, Velocity] Gogy72:
That happened to me a couple of times. And what I found to work for me was to press and hold all four soft keys(at the bottom), both volume buttons and the power button all at the same time. After a few seconds the screen lit up and started charging. Hope that helps
[HTC Vivid, Raider, Velocity] positiveg:
Well guys faced something similar yesterday, wasn't fun i took out the battery after it went dead, and tried replacing it in the dark. I did it incorrectly and bent a pin contactor in the phone where the battery connects.

I spent hours wondering why it wouldn't charge cause the phone would go amber (orange) like it's charging then go green a steady green like the battery is full

and when you click the power button it would just go off

So if anyone wondering why their phone might not charge, check the battery pins inside the phone make sure they aren't bent. Oh and be careful fixing them if they are.

G
[HTC Vivid, Raider, Velocity] wilksy1:
I had the same problem my htc velocity/vivid had no power or led lightning at all.

I followed this tutorial and after a few goes i got the little orange light back.

1. Get your phone. Take out both battery and SD or sim card.

2. Get USB Cable, plug into computer.

3. Take your phone (naked) and plug in the USB cable.

4. Hold down the Volume up + down, while holding the volume buttons place battery (not SD card) back into the phone. NOTE ( In this step i held power button aswell which is a bit tricky but holding just the volume buttons didn't work.)

5. Keep holding on until Phone goes into USB mode (vibrates or something). You can stop holding buttons down. The computer may not recognize your phone. That's okay, doesn't have to. NOTE ( After i got the orange little light on the front to turn on i just let it charge for about an hour then turned it on while still plugged in,then disconnected the usb cable now it works fine, before the phone stopped working it was working fine so i don't know what the original problem was i didn't think it was completely dead so i brought a new battery and after that didn't work i couldn't find any really helpful info until this post so it might work for you to.

6. Try and see if there is a green blinking light on your phone. This is the sign of hope!!! If not try steps 3-5 again.

7. If so then take you phone, plug it into the wall charger.

8. Again, take battery out let it sit for about 2-3 or 5 minutes.

9. Now you can put both your SD card and battery, back into the phone. Your Phone should now have an orange blinking light. Your phone is charging again!!!

10. Give your phone time to charge, until blinking turns solid orange.

11. Now you can access you Bootloader, and recovery, and restore your Backups!
[Sprint Samsung Galaxy Note II] Killa357:
It seems my phone is stuck on ALJC. I flashed the stock recovery via Odin and did a temp unroot, downloaded the OTA update. The phone rebooted and went to the stock recovery and appeared to be installing the update. Upon reboot, my phone was back in rooted condition (not sure if this is normal for voodoo unroot or not). This has happened twice. The first time it happened I had not noticed it, but now that it has sent a second update request to me today, which I used the same method only to discover that it doesn't seem to work. Now when I request an update it tells me no update is available. Suggestions?
[Sprint Samsung Galaxy Note II] Killa357:
Ignore this thread, I said screw it and just did it all manually.
[MDA, XDA, 1010 General] Gene_uk:
Hi All,

I'm having a small problem with my XDA and the pocketpc2002 system.

there are certain files in my windows directory that are gorwing out of control. It has already taking up nearly half of all my internal memory and growing by about 50kb every day.

I dont know how to stop it from growing, nor can I delete them, as they are in the windows diretory and are locked. The files all begin with

"MsgQueueDataFileMicrosoft " and have the following after it...

Broadcast Message SMS Protocol (Receive Only)

Notification SMS Protocol (Receive Only)

Raw SMS Protocol (Receive Only)

Status Message SMS Protocol (Receive Only)

Text SMS Protocol

WCMP SMS Protocol

WDP SMS Protocol

As I said these files are taking up about 15MB of space at the moment and If I dont get rid of them soon, I will probably have a serious system crash.

I need someone to confirm the roles of these files, what their typical size should be, is the normal, and what to do to correct it.

A Hard reset is not what I am hoping for... please help..

Gene
[MDA, XDA, 1010 General] Tim C:
see the following link

http://www.ppcw.net/forum.php?forum=30&thread=272

posted by Arne Hess on ppcw.net for a full explanation

Regards

Tim
[MDA, XDA, 1010 General] Zviratko:
Well, the answer doesn't satisfact me, those files are not in ROM neither in RAMdisk, they seem to just be loaded in RAM as programs (they are dlls). I renamed one and restarted the phone, another one was created with the original name. The content never changes.

I wonder what they are here for...
[MDA, XDA, 1010 General] Gene_uk:
It doesnt satisfy me either...

I cant beleive anyone in Microsoft would develop apps to hog 15MB of storage memory.

I have a good mind to do a hard reset just to prove the point...

G
[MDA, XDA, 1010 General] Carlos:
According to MS, the file sizes reported are completely false and they do not take up that much space at all.
[Samsung Galaxy Exhibit 4G] yBrik:
Hello all, long time lurker, first time poster.

After drooling over the feature on the N4, I set out to get wireless charging on my humble Exhibit 2. At this point, I have installed the induction coil into the back of my phone, wired into VCC on the USB plug and the Sim card reader(Connected electrically to ground). I have verified 5v in the proper polarity is being supplied by the charger, but the thing isn't charging! I suspect this is similar to the fast charge issues several devices have, when the device will only pull current when certain pins are shorted or have a certain voltage across them. I'm considering a small leave-in plug with the proper wiring, but I also want to explore fast charging. I'm running Slimbean (the December release) and Demon's Blood v8, but fast charge doesn't seem t be enabling properly. Is the software enabling possible on our device? or should I try the hardware approach?

EDIT: the Fast Charge app from the Play Store is reporting my kernel doesn't support fast charging. Is there a kernel for our device that does/did? If not, could that be implemented, or is there a hardware limitation?
[Samsung Galaxy Exhibit 4G] afwolfpacked:
You can try rootbox 4.1.2. Look in rom control/performance settings/other settings. Enable fast charge there. See if the device works. Looking forward to results hope positive.
[Samsung Galaxy Exhibit 4G] yBrik:
No dice, none of the kernels support fast charge. Seems I've hit a snag unless one of our awesome devs can enable it...
[HTC Rezound] zkrp5108:
I have this weird issue where I am on Hboot version 2.27, but somehow my raids are out of date. I understand the process to update both but not one at a time. From what I remember you cannot run the RUU or is the same ph98img if you are already in the hboot your updating to. Does anyone know how to just update the radios? If you need more info check Stangs CM thread in the Q&A section of the forums it is the first question asked in that thread. Stang provided and answer but was not 100 percent sure if his solution was correct can anyone confirm our send me in the right direction. Thanks in advance
[HTC Rezound] feralicious:
I've never heard anything about not running an RUU that's the same hboot as your current one. A lot of people run it just to get back to stock.

I just ran the global RUU, flashed a custom ROM, then ran the same global RUU and reflashed the same custom ROM because for some reason after the first ROM flash my baseband info was showing up as "unknown" in my phone.

I'm s-on if that makes any difference, but my understanding of it is that it wouldn't.
[Android Q&A, Help & Troubleshooting] appro77:
Is there a hack to remove the message that pops up whenever my phone connects to my wifi network? I have the phone set to disconnect wifi when the screen goes off, so I always get the "Connected to wifi network xxxxxx" message when I wake my phone.

I know that there is a hack to remove the "Wifi Network Is Available" message but that is not what I am asking here. Any help is appreciated.
[Android Q&A, Help & Troubleshooting] ikjadoon:
Depending on your phone...http://xdaforums.com/showthread.php?t=1784615
[Verizon Samsung Galaxy S III] Gordon Ramsay:
I was hoping anyone here could relate to the problem my brother and I are having with pretty much all AOSP ROMs. Every time we install an AOSP ROM after even completely wiping everything except ext SD, after about an hour of run time to smoothness of the ROM goes away. The pull down is all choppy as well as scrolling the home screens. A reboot fixes it temporarily for around a minute or so and it goes back. We did find one AOSP nightly from the 15th that remained smooth but that was it.

If anyone has any ideas what could be causing this I would be eternally thankful. We have searched up and down and can't believe no one else is complaining of this. This is happening on both of our devices where pretty much the only similarity is that we use TWRP and update it regularly.

Thanks again for any advice you can provide.
[Verizon Samsung Galaxy S III] voltage526:
I've had this same exact problem. I believe you meant the AOKP build from the 15th as that was the one that has remained smooth (but had some other bugs) for me. Seems like nobody else is having this problem.
[Verizon Samsung Galaxy S III] jmxc23:
The reason people aren't complaining is because they haven't had that problem yet. The only thing I can tell you is when flashing ROMs make sure you completely wipe 2-3 times as for some reason with TWRP you have to do that to get some ROMs to work.
[Verizon Samsung Galaxy S III] voltage526:
Thank you for the wonderful insight. But in all seriousness I wonder what is causing it for us.
[Verizon Samsung Galaxy S III] jmxc23:
please read my edited post. I will also add that when flashing ROMs the results are very random even with the most stable of ROMs.
[Verizon Samsung Galaxy S III] voltage526:
Thank you. I wipe everything 2-3 times by habit though.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Yes I wipe 3x and then use zips that wipe again.
[Verizon Samsung Galaxy S III] jmxc23:
then you guys might have to switch CWM recovery as I flashed most of the AOSP ROMs with no problems.
[Verizon Samsung Galaxy S III] voltage526:
You really don't have any stuttering whatsoever with AOSP roms? Hmm.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
I would think though if it was TWRP wouldn't a lot more people be having this problem? I will try CWM though.
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Just wanted to update the thread. We have tried switching recoveries to CWM, also tried running the rom with absolutely nothing but Gapps. Same result after a few hours. This is on two completely separate devices, we can't be the only ones. Any additional advice would be really appreciated. This is driving us crazy!
[Verizon Samsung Galaxy S III] andrewk7750:
I get pretty bad lag on carbon rom, flashing with CWM. Any other aosp rom runs fine but carbon seems to not like my phone :p
[Verizon Samsung Galaxy S III] Gordon Ramsay:
Carbon was the worst so far for me as well.
[Verizon Samsung Galaxy S III] jmxc23:
That goes with the fact not everyone will have the same results when flashing ROMs.
[Android Q&A, Help & Troubleshooting] CommandoModz:
I always get this error. I just tried to download a light Google music app and I get this. Its not my first time for different apps either View attachment 1777593
[Samsung Galaxy Nexus] jimmyco2008:
I want to form a group of devs/general people, and I want us to get things done for the Galaxy Nexus.

From WebOS to Ubuntu to FirefoxOS, and even Android itself, arguably no other device (except maybe the Nexus 4) has the potential that the Galaxy Nexus has. I know there's a lot of you out there who don't really know anything about ROM development, you're far from calling yourself a developer, and I'm in the same boat, I put together a guide for installing WebOS on the Galaxy Nexus, but all I did was follow the original guide, figured out the gaps, and re-wrote it with the gaps filled in... I want to do more, I'd like to give credit to myself for a change.

I don't know much, but I want to learn... What I'm saying is, I have ambition but I lack skill.

In any case, if you're kind of just sitting around, perusing the forums, and you want to be a part of something really cool, chime in- even if you aren't a dev, because even the CyanogenMod team started off as a bunch of clueless noobs.

It'd be cool to have some experienced devs, some regular ROM flashers who know only how to flash ROMs, anyone who wants to contribute/learn in some way. I'd like to start off with Open WebOS (in case you haven't guessed), and I would call this the "WebOS A-Team", but I thought, why do we have to stop with WebOS?... I suppose we could, we'll see if anyone is even into this.

No one's heard from the WebOS Ports team in a while, and they aren't really focusing on the Galaxy Nexus, so I think we can certainly work with it.
[Samsung Galaxy Nexus] madd0g:
Like what ? Bored with the phone again ? Time for a new hobby perhaps.
[Samsung Galaxy Nexus] b1337:
Cant really be a newb and start a dev project or team...
[Samsung Galaxy Nexus] iLeopard:
OP Go check out the HTC HD2. Surprised as to how far it got.

$30 headset, fun toy to play with
[Samsung Galaxy Nexus] chefthomas99:
What's wrong with the great devs that we already have? They are the A-team.
[Samsung Galaxy Nexus] jimmyco2008:
Haters gonna hate... It's cool what they do, but none of them are bothering with WebOS AFAIK.

I'd like the GalNex to be the next HD2, that'd be cool.
[Samsung Galaxy Nexus] madd0g:
Maybe they're not bothering because they see it's not worth it. Unless you'll just assume they will magically craft drivers for it out of the blue.

It's not what you think it's "cool" but what the real world situation is.
[Samsung Galaxy Nexus] t1.8matt:
whaaa....????? you're making it seem like the only reason you want to do this is for YOUR benifit. i know jack about building roms, but i think if you want to start somewhere, learn how to build basics, like compile CM or AOKP and learn how to add your OWN mods to it. After that, learn some more, and after that, learn some more, then you can put together your all-star team and work on WebOS. Just my .2, take it as it is. Not being a dock, but you can't pull magic out of your behind when you don't know anything to begin with. There's a ton of talented people on here, if they could get WebOS going, they would, but obviously it's not that easy.
[Samsung Galaxy Nexus] ECOTOX:
Unless you learn to code and write you're own OS you will always be giving credit. I'm willing to help you some in regards to kernels as I don't like working in user space but you gotta learn the basics.

---------- Post added at 07:11 PM ---------- Previous post was at 07:09 PM ----------

The problem is Its dead, I love webOS but there isn't much to do on it these days
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] linnu5:
I just upgraded my Galaxy Note N7000 from 4.0.3 ICS to 4.1.2 JB (both stock roms), but when I try to restore my apps and data, Titanium says that the folder is empty and don't recognize my backup.

I restored my phone successfully many times between ICS roms, but now I'm getting this problem.

I've tried to re-install Titanium, tried to change the folder location, restart my phone, use stock and custom kernels, and I'm not able to restore my apps and data. When I wipe my phone and go back to stock ICS, Titanium recognize and restore all my data and apps without a problem.

What can I do?

Thanks
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
I think you made a mistake when selecting the backup folder. Try again.

In TB - Preferences - Backup folder location - Detect - Whole device - (after recognition) - Use the current folder - Restart TB.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] linnu5:
I've tried that. I even tried changing the folder name and back again.

The weird thing is that, if I go back to ICS, Titanium recognize my backups normally as soon as I install and open the app.

This bug is only on JB.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ThaiDai:
Move or Copy your Titanium Backup folder to a different place (example: from internal to external card) with a file explorer

And try again with the new folder location.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] incisivekeith:
I've very disappointed with some of the new JB features, as they just appear to be gimmicks. Smart Stay is one of them. Does Smart Stay work for you, indoors or outdoors?

4.1.2 JB LSZ Ultimate 5.2 ROM, KSO Modem, Phil's LSZ kernel, Carrier: AT&T (US)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] abhinav quietly brilliant:
Yeah it works.. But in low light it seems to be useless
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] squabbi:
Well it works for me fine. But as the poster above its useless in dark areas.