yashsingh1/xdaforums huggingface dataset:
[P3300, MDA Compact III General] dennisv9:
i have a p3300; no power lights when charger is connected; doesn't power on as well. battery is fully charged, battery and charger are both fine. but sometimes the p3300 powers on just fine; if i connect the ac charger then it also charges the battery. but it hangs in windows mobile 5 after some time (trackball and buttons and system does not respond anymore); after a soft reset no power/power lights or boot at all. then after some time and fiddling it might power on again and the cycle starts again.

i know it is a common problem; but is there a solution?

the backup battery (yes, there is one in it. the same as in the qtek 8310) gives me 0.20 volt. not sure how much it should be. but the backup battery in my qtek 8310 gives also 0.20 volt. not sure whether both are drained or that the voltage is normal.

will a drained backupbattery prevent it from booting up fine? or... hope to get it up running reliable again; great navigation phone with tomtom.

edited:

without the battery installed i get a red light flashing quickly if i put the 5volt charger on it; same if i connect an usb cable (connected to my computer);

if i have the battery installed; i do not get a red light flashing.

with the battery plugged in and the charger plugged in; i don't see any charging lights. but it does charges my battery; i started with 3.7 volt, and it is going up (now at 3.9 volt).

in both instances i cannot get it to power on/into bootloader mode.
[P3300, MDA Compact III General] R_AL_Sim:
i've got exactly the same issue

I was given this phone by my brother as its broken, i tend to get alot of his broken stuff :) anyway i stripped the phone down and found that the little battery inside had leaked so i did a little bit of hack wiring and bodged a 3.3 volt battery used in a PC to power the cmos chip well it seems to have sorted the problem apart from the fact there are two wires hanging out of the phone but i've also noticed this battery voltage has dropped to 2.6 v now and still dropping over the days i'm guessing i'm going to have to make it replaceable. :)

oh just for the record

my brother tried a replacement main battery on it originally and tried flashing it with a clean rom to try and fix it but it carried on hence passing it on to me
[P3300, MDA Compact III General] raving_nanza:
...

...to both of you...

buy a new battery..

leave it OFF while charging!!!

when the green led comes on (orange while charging... red flashing indicates battery is dead)

done.. turn it on..

batterys are cheep on ebay..

(if this dont work, pm me.. it could be something totaly differant but buying a new battery is the usual soloution for this common problem)
[Sable] vohuu:
All rom, What's rom best for Hp Ipaq 612c? :D
[Sable] mendel129:
my choice goes to keyx's roms :-)
[Sable] vohuu:
Please comment rom is best? :D
[Sable] Zemun_PFC:
http://xdaforums.com/showpost.php?p=3541058&postcount=4
[Sable] vohuu:
Why you use rom 35.1?
[Sable] Zemun_PFC:
you asked what is the best rom right? i forgot to change the signature.

there is no WM 6.5 rom without annoying "sms opening bug"
[Sable] vohuu:
Thanks! :D
[Droid Incredible Q&A, Help & Troubleshooting] jdmba:
Greets - I am looking for a decent MP3 and Video player in 1 app. Currently I am using Meridian, but the authors refusal to fix the bug where if you update ID3 or Album art, it not only refuses to note the changes, but then starts showing different MP3's album covers.

I have no requirements other than it needs to play Video and MP3's and NOT suffer from this bug.

Any thoughts?
[Droid Incredible Q&A, Help & Troubleshooting] abe01:
I used double twist all the time.
[Droid Incredible Q&A, Help & Troubleshooting] jdmba:
Any other suggestions

Thanks but the VERY FIRST review on the list says it suffers from the same problem I am trying to escape. Meridian would be VERY GOOD if the author bothered to fix the same bug.

Any other suggestions are appreciated.
[Droid Incredible Q&A, Help & Troubleshooting] compnird:
DoubleTwist!!!! You need no other.

Well, that and Slacker radio for internet tunes. Now f only I could use my Zune Pass on the Android... :(
[Droid Incredible Q&A, Help & Troubleshooting] compnird:
Well then try Mix Zing, it's in the marketplace. I would compare it to core player on WinMo... Have to pay to properly edit ID3 tags but it has some great features if you do.

I have not used it for video and don't even know if it is able.... but the basic player on the HTC is fine for videos that I play.
[Droid Incredible Q&A, Help & Troubleshooting] Boomh4u3r:
If doubletwist could read the internal storage,I'd use it. I have 6gbs of tunes and it finds the 2 i have on my sd card...lame
[Droid Incredible Q&A, Help & Troubleshooting] ihtfp69:
I use cubed because it has a cool interface and a variety of widgets. The real name in the market is ³.

http://www.appbrain.com/app/org.abrantix.rockon.rockonnggl
[Droid Incredible Q&A, Help & Troubleshooting] ZOMBII MATT:
For some reason Double twist doesnt read all of my music. it maybe reads 2 out of 14gb
[Droid Incredible Q&A, Help & Troubleshooting] jdmba:
Ugh

Doubletwist seems like a really bad idea, but it seems the answer to my question is THERE IS NONE. Let's home some developer can step up, make a player that can process updated ID3 and Album art, without getting all confused.

If anyone has any ideas, I would love to hear them
[Droid Incredible Q&A, Help & Troubleshooting] dkaile:
Use Rock Divx Player - best one around for snapdragon devices...
[Droid Incredible Q&A, Help & Troubleshooting] pules:
you might be interested in this

http://android.modaco.com/content/forum/311257/view-topic/

RockPlayerBase: The Android AVI, MKV, DIVX y RMVB player

It's something a lot of us avid Android fans have missed and now at last we have a multiu format media player!!! RockPlayerBase

At the moment it's in private beta testing phaseand so far the reports are fantastic. It requires > Android 2.1 and a decent processor

If you want to give it a try you can download it from the original SoyAndroide article here

The link is at the bottom of the article, marked Pruébalo (Spanish for try it out)

More details:

movie:

MKV

H264 High profile, 720×304 @ 405Kbps @ 24FPS

AAC, 44.1KHz

perfect quality

14 to 20 FPS

tv show:

AVI

DivX 5, 704×384 @ 1,097Kbps @ 24 FPS

MP3, 48KHz @ 128Kbps

perfect quality

22 – 24 FPS

anime:

MKV

H264 High profile, 848×480 @ 302Kbps @ 24FPS

AAC, 48KHz

lots of artifacts

no subs (ASS, Advanced Sub Station)

8 to 15 FPS

handbrake:

MP4

H264 Baseline profile, 800×448 @ 3,120Kbps @ 30 FPS

AAC, 44.1KHz @ 151 Kbps

perfect quality

13 to 16 FPS

Artbeats 720p HD Demo:

MP4

H264 Main profile, 1280×720 @ 5,994Kbps @ 30 FPS

AAC, 44.1KHz @ 66Kbps

perfect quality

3 to 6 FPS

Artbeats 1080p HD Demo:

MP4

H264 Main profile, 1920×1080 @ 10Mbps @ 30FPS

AAC, 44.1KHz @ 192Kbps

perfect quality

1 to 3 FPS
[Droid Incredible Q&A, Help & Troubleshooting] ankaka:
If you like iTunes then getting an Nano would be a good option since you don't seem too worried about extra features like a radio etc. If you can get the education discount then it will drop down to ~$320 which is great value.
[Droid Incredible Q&A, Help & Troubleshooting] POQbum:
?

I use doubletwist and all my songs have correct ID3 tags and album art.

I use separate programs to grab all the album art and ID3 tags.. but doubletwist doesn't scramble them or mix them up.
[Droid Incredible Q&A, Help & Troubleshooting] godsmacked4653:
Since this topic was started almost 18 months ago, I'm assuming the issue has been fixed in the apps by now. :)
[P3600 General] MoroMoretti:
I am trying to install russian keyboard in my Trinity (italian WM6.5) but some problem. I used instruction on other post on XDA but some problem with resolution. Somebody can help me?
[Hero CDMA Q&A, Help & Troubleshooting] bigfatdude:
Would it be possible to downgrade to the official shipped Sprint 1.56 ROM (RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe) from official 2.1 ROM using recovery-RA-heroc-v1.6.2? I know hboot was changed in the latest ROM and 1.56 RUU generates the dreaded 140 error, but would it be possible to extract rom.zip and flash it using RA?
[Hero CDMA Q&A, Help & Troubleshooting] mooniefresh13:
I noticed that Stk.apk is listed in system/app. If I'm not mistaken, isn't that for dual sim cards? Or am I wrong? Can it removed or does it serve a purpose?
[Hero CDMA Q&A, Help & Troubleshooting] thatguythatdid:
I'm not sure but what I do when I have a question like that is first nandroid. Next remove it and reboot. Then go through the quick motions of testing everything out to see if everything that I use is still working (mms, internet, music...etc). Maybe not the answer your looking for but it's something
[Hero CDMA Q&A, Help & Troubleshooting] Thatonedude:
i removed it. its still going strong since the rom was released.
[Android Software Development] smurf:
Hi there,

i made a "hello world" app. When i try to install it on my magic it says "com.example.helloandroid couldnt be installed on this phone".

Any help would be appreciated. Thank you...
[Android Software Development] tekmunki:
home > menu > settings > applications > uncheck unknown sources
[Nexus One Q&A, Help & Troubleshooting] lynxboy:
Hey Guys,

Ever since I first experienced this bug, it seems more and more people are coming forward explaining the same symptoms.

Connection drops, OS becomes unresponsive, freezes, and then you are greeted by the 'X' animation. After the phone reboots, it freezes once again and returns you to the 'X' animation and the process repeats until you pull the battery.

There seems to be no direct trigger as it can occur when on a call, when browsing or even when the phone is idle.

I've read through various threads on different forums in an attempt to reveal some kind of pattern, yet reports are coming from users on different ROMs with different kernels and different apps. I've created this thread in the hope that if people contribute their experiences, we can draw some kind of reasoning behind the development of the bug and offer some hope for resolving the issue in then future.

So guys, what are your experiences of the BLOD? What ROM were you running? What kernel were you running? Do you overclock, underclock or remain at stock? Anything you think may contribute to this annoying bug.

Thanks in advance.....
[Nexus One Q&A, Help & Troubleshooting] lynxboy:
Reserved for future use
[Nexus One Q&A, Help & Troubleshooting] lynxboy:
My experience began after updating to Kang-o-Rama 0.6 final (CM 5.0.6) after using Kings Desire Port aswell as using Paul's Desire ROM and Cyanogenmod previously. Originally it happened to me in the gym. While listening to music I recieved an SMS and the phone suddenly crashed and went into the BLOD. I had to pull my battery for it to stop. Since that occasion, I began to suffer the BLOD 3-5 times a day, sometimes when on a call and other times when the phone was idle. I tried wiping and reinstalling countless times, flashed stock Cyanogen and the later versions of K-o-R which would give my phone a slight reprieve ,however eventually the BLOD would hunt me down and return.

Eventually I believed it was a Cyanogenmod specific bug, especially after reading this thread,

http://forum.cyanogenmod.com/index.php?/topic/43-odd-crash/

Since I thought it was CM specific I went away and flashed Enom's ROM which again gave me a reprieve but only until I charged the phone at night. I awoke in the early house to find my phone rebooting away as I slept. This pattern continued for 3 nights until last night which was my first BLOD free night.

Now i'm not 100% sure as to what cured my looping last night but I flashed a new kernel yesterday (IR .33.5) and also on the advice of this thread,

http://www.google.co.uk/support/forum/p/android/thread?tid=2711ea74ef3d9aee&hl=en

I wondered whether the fact that I'd started using the stock alarm clock app could have triggered this so called 'notification bug'. I returned to using Gentle Alarm from the market and cancelled my stock Androdid alarm.

Right now i'm waiting to see how long I go without a BLOD before investigating if it was specifically the new kernel or changing the alarm which got me through the night. Will report back if anything changes.
[Nexus One Q&A, Help & Troubleshooting] wesbalmer:
I'm pretty sure this is a form of a kernel panic. I know Cyanogen had made some type of tweet or post regarding this. I'll try to find it and edit this post when done
[Nexus One Q&A, Help & Troubleshooting] lynxboy:
Cyanogen posted something regarding it being a system_server crash in the CM thread and that we needed logs of the event occuring before he could draw any conclusions. I managed to dump and adb logcat of the event while it was happening, although it was just a panic loop of which a segment was posted on the Cyanogenmod forum I posted above. Has anyone managed to capture a log of the BLOD as it starts? That would be a great help.
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
I got my N1 about 4 weeks ago and it worked OK until I flashed the Froyo radio. from that point on I could not get any rom to run in a stable way - my reboots happened 3 - 4 times a day and got to the point where I would get stuck in the boot loop. Pulling the battery did not always solve the problem although I found that if I kept the battery out for several minutes my chances of getting the phone to boot into either the ROM or recovery would be better.

I noticed at the same time that once the boot loop started I could not get into recovery until my phone had at least booted into the ROM successfully once.

Flashing back to the 4.04 radio reduced the random reboots to about once a day - usually at night after I had just plugged my phone in to charge. I was using the stock alarm app as a bedside clock.

After many days of frustration and the help from several people here at XDA, I finally came to conclusion that the problem must be hardware related and am returning my current device to HTC and am getting a new one.
[Nexus One Q&A, Help & Troubleshooting] nexusdue:
I don't have a boot loop but I definitely experience the initial stages of this problem on a stock (unrooted, locked) N1 (at&t).

50% of the time when the N1 loses the connection (e.g. due to going into a garage) it will not re-acquire the signal. Searching for networks will hang, putting the phone in flight mode and then disabling flight mode will still result in no signal.

The only way to get a cell signal back is rebooting the phone.

Usually, searching for a network and/or enabling and disabling flight mode will result in the phone turning black and then rebooting.
[Nexus One Q&A, Help & Troubleshooting] phrphz:
I have the problem, too.

Just a few notes:

didn't have it on stock rom and Cyanogen 5.0.6, nor an Enomther's 1.8.1, started with Enomther's 1.9.2

This is not really a reboot, because a real reboot always helps. Other than a reboot, it starts directly at the X animation, not with the unmoving X before.

Seems to be a kernel panic.

I currently suspect that the panic happens when the RAM is full, especially if there is one single process that uses up massive amounts of RAM (could be in the background, of course).

I yesterday found that Sytrant (periodically sets time using internet time server) has a memory leak, and on closer inspection today found that it queries an ad server every few seconds and thus switches from sleeping to running state every few seconds. Also, it spawns root processes when setting time, which might lead to the system not wanting to kill it.

So, here's my current suspection (I'm not at all sure if that's true!):

The reboot loop only happens when the system runs out of memory.

In this case, Android should normally kick out other programs: First apps that are not running anymore, but are still in memory, second background jobs, and third services.

I guess there's some error in the killing logic in newer Cyanogen kernels and others that use Cyanogen parts (or maybe even in the orginal code from Google).

This somehow leads to a state where the kernel has no memory left and can't kill a process, too. -> Kernel panic

Maybe this is more probable if there is one big memory hog the kernel doesn't want to kill (because it's a service, or maybe because it has children running as root).

So, everyone who has this problem, please get a process monitor or task manager where you can see how much memory an app uses. OSMonitor is a very good one, and it can also sort the processes by memory usage. Start it periodically to find out if a process is constantly growing.

If you found such a process: Is it one that requires root? Does it run as a service? (Unfortunately, OSMonitor can't tell you if a process runs as service, or at least I didn't find it if it can. :-) ES Task Manager can show that information, though, for example.)

Personally, I threw Sytrant off my phone now and will watch if that helps. I had reboot loops every two or three days, so I can't tell yet if it really will make a difference. I really hope so …

Edit: Of course, this theory does not really explain why the network drops before the boot loop starts. It could be, though, that the kernel tries to kill just anything to gain meomry, which might also be a system process that it responsible for the network. As the networks always seems to drop before the loop starts, maybe killing that process is what leads to the panic in the end.

Maybe, could … well, yes, this is just a theory. But at least it sounds good, doesn't it? ;-)
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
The more I read about this problem here and in other threads, the more I am convinced that my problem is probably not hardware related. My replacement phone arrives today but now I am wondering if I should return my original or not. Argg!

Is there a way we can all band together to try and get to the bottom of this problem? I am more than willing to do whatever testing those that know what to look for tells me to do.

Would one of the Guru's here be willing to guide us through a coordinated troubleshooting excersize?

Maybe we can start by trying to find out what we all have in common?

I have an AT&T/Rogers version of the N1.

I typically have the Facebook, Calendar Widgets on home screen.

Power Widget on 2nd screen

Use gmail but via the standard email client, not the gmail client.

Use the native alarm clock app in the dock at night

16GB ADATA MicroSD card.

I also install:

- ChompSMS (with icon widget on home screen)

- NewsRob (with Widget on home screen)

Did not get the reboots initially running the stock rom but they started the moment I installed paul's version of Froyo. I tried several of the other roms and had the same instability and BLOD's until I reverted back to stock and things stabalized again although I was still getting random reboots once a day or so.
[Nexus One Q&A, Help & Troubleshooting] phrphz:
While a hardware issue (especially RAM failure) could cause this issue, I don't think that it is the cause in most of the cases here. The fact that some don't experience it anymore after trying one or another software-related measure makes a hardware failure highly improbable, at least in their cases.

I won't rule that out, but until I tried everything else I can't conclude it must be a hardware faliure.

Please get OSMonitor and watch your processes. If after some days you still can't find a process using more than, say, 65 M, and still get the issue, you can be pretty sure that a memory leak isn't the problem for you.

The memory leak + killing bug guess is a good one and is quite probable. So let's check that first.
[Nexus One Q&A, Help & Troubleshooting] MSigler:
I think my FroYo rom problems are the same problems you guys are having. I think it's something with an app or an element of the OS or something.

http://xdaforums.com/showthread.php?t=703508

I get the exact same issue on a handful of roms. Everything starts to force close, then it goes into boot loop, but, as someone said, doesn't really fully reboot, it just starts at the boot screen.

I've also noticed when things get funky, plugging in the USB cable makes it immediately go into a boot loop.
[Nexus One Q&A, Help & Troubleshooting] cmarti:
I start having this problem after I install the Quadrant Standard program, I was using the Kang-o-rama - Froyo when this happened. But after going back to Paul's Froyo everything is working perfectly again.
[Nexus One Q&A, Help & Troubleshooting] MSigler:
I deleted quadrant, signed into market and all so it knew i uninstalled it, flashed a baked modaco R17, and it still boot looped on first reboot.
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
I suspect it is related to the 4.06 radio. My first boot loop started just after I installed the radio and before I updated the ROM itself.
[Nexus One Q&A, Help & Troubleshooting] MSigler:
That doesn't explain mine though. I get the boot loop on some roms but not others, with the same radio.
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
Which ROMS are safe for you - I will flash one of them tonight and see if it works on my device as well - maybe we can narrow it down to a specific ROM.

Would also appreciate a list of the apps you use - I am thinking we should set up our phones as close to identical as possible to begin with and then start adding things to see what causes it. Thoughts?
[Nexus One Q&A, Help & Troubleshooting] MSigler:
The only roms that screw up for me are modded froyo roms. LeoFroyo works fine for some reason, as does the stock FRF50. I'll screenshot my apps in a minute and post them.
[Nexus One Q&A, Help & Troubleshooting] nexusdue:
I have this on stock 2.1u1 EPE54B
[Nexus One Q&A, Help & Troubleshooting] tjsimmons:
I was getting some pretty random boot loops when running CM 5.0.7.1 and 4.04 radio. Noticed two things could (almost) cause it every time:

1) Not so much a cause, but Google Listen was running almost every time I went into a BLoD.

2) Something that WAS causing it.. I keep my phone on airplane mode at work with WiFi on, since I don't get a reception in the building. Reboot + turn off airplane mode when the phone is to that point = BLoD.

I actually flashed Kang-o-Rama and the 4.06 radio earlier, no problems now.
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
Did you flash the Froyo version with SP3?
[Nexus One Q&A, Help & Troubleshooting] GldRush98:
A custom rom introducing bugs. Shocking.
[Nexus One Q&A, Help & Troubleshooting] nexusdue:
Stock rom having serious bugs.

Pathetic.
[Nexus One Q&A, Help & Troubleshooting] tjsimmons:
I had SP2, flashed SP3 earlier. I haven't had any problems with this ROM.
[Nexus One Q&A, Help & Troubleshooting] DvTonder:
Flashing 4.06 with KOR090SP3 - will advise on what happens

Radio = Flashed OK

KOR090 = Flashed OK

SP3 = Flashed OK

First Boot = animation running a LONG time but OK

Initial config = OK

Install SIM card and Boot = OK

Set up Google account and sync start = CRASH!!!

Auto Reboot to boot animation = CRASH!!!

Hanging at X

Pulled Battery

Booting = Hanging at X

Pulled Battery again

Booting = OK

Lock screen for 10 seconds = CRASH!!!

Boot into Bootloader = OK

Clear Storage = OK

Booting = Hanging at X

Pulled Battery (3rd time)

Booting = Hanging at X

Several battery pulls later back at home screen, setup connection = CRASH!

BLOD!!!!

I give up!!!
[Nexus One Q&A, Help & Troubleshooting] djmcnz:
That's a shocking experience.

So, if you do NOT set up your Google account does it work okay? What happens if you use a NEW Google account on a fresh rom?

These boot loops are impossible to diagnose remotely without logs. What you need to do is replicate the bootloop, plug in your USB cable and use adb to output the log to a text file e.g:

adb logcat > mylog.txt

After it's looped a few times, stop the output (CTRL+C), sanitise the log to remove personal details and then post it back here.

Please try the new Google account and fix mismatched UID (in recovery) before collecting the log.

If a new Google account works, the problem is with your existing account and sync data. There seems to be no way users can fix this problem with the account... :eek: