yashsingh1/xdaforums huggingface dataset:
[Streak 5 General] Thremix:
NO I just got the phone today, :) I read the PDF and went in to fastboot, ran the command to install clockwork and then I boot in to recovery, but nothing, just dell stock....

Now I'm getting frustrated... If I can just get streakmod or clockwork on here I would be a happy guy lol for now, this phone cant hold a candle to the speed of the inspire, from what I have seen on youtube 1.0.9 flys! I want that rom...
[Streak 5 General] Thremix:
OK I got it, I am doing a nandroid backup.... it's taking some time... more time than I like.. it also keeps blinking? how long does it take?

OK phone looks like it is stuck, I'm not sure what to do.... but it's been about 15 minutes now. and the phone is new, so it's not like it has a lot to backup....
[Streak 5 General] Thremix:
OH, and clockwork is upside down lol..
[Streak 5 General] eSZee:
Nandroid should not take more than 5 minutes.

Posted with StreakZilla, using XDA App.
[Xoom General] Mshanahan:
I have a Wifi only Xoom running android 3.1.

I'm connected to my internet. Tried rebooting xoom & Router

Today when I connected only the browser seems to work. Tried many different websites all load fine.

Any time I try to access the internet via another application it shows no internet access. Android Market just keeps saying no internet connection.... Ive tried 3 different apps besides the market. Nothing....

Any idea's ?

Is there a option in the settings that would disable app internet connections ???
[Xoom General] chbennett:
I have the same problem, and I have not found a solution to the issue. I notice that some apps can find the internet just fine (Beautiful Widgets), while apps like CNN say I must connect to a network. *Despite the fact I am on a super fast WiFi network*
[Xoom General] blackte4:
backup all your files(music,movies,etc) and restore it back to factory. What happen was the update didn't take 100%. I had problem but everything is great after a factory reset.
[Nexus One General] dweebs0r:
I thought I would post a thread listing the Paypal address for those who would like to donate to the developer who helped bring about a fix for the dreaded wonk.

I think this guy deserves a couple bucks thrown his way by most of us who use and enjoy ASOP based firmwares.

The last couple of cyanogenmod nightlies have had ZERO wonk.

Lets keep in mind that this issue was starred with Google a couple of times and we couldnt get Google to even recognize that a problem exists!

The problem was so bad that cyanogen was releasing roms marked as stable that still had the wonk because it was an ASOP bug...

Anyway, send this dude a couple of bucks if you can. All of us running a N1 with ASOP based firmwares are benefiting from the wonk fix.

His paypal address is: jordanp@gmail.com

Thanks!

-Dweebs
[Nexus One General] dweebs0r:
Ok, I just sent the guy $10 USD. Its not much but every little bit helps.
[Nexus One General] GldRush98:
Umm what?

Google acknowledged the issue and even fixed it, which is probably why it is working in CM roms now.
[Nexus One General] Devastatin:
Dunno if the email is the right guy, but it was fixed independently of asop.
[Nexus One General] Chosen_on184:
Two different forms of wonk ..

One is the call delay bug

The other is the black screen bug

I "think" he found the issue for the call delay

Not sure about status of black screen bug

Google said the delay bug was not across all devices and only specific to Nexus so they closed the report. Last time i heard about it

Again i might have my bugs mixed up but ehhh
[Nexus One General] dweebs0r:
http://xdaforums.com/showthread.php?t=1080147

This is the thread where you can see the results of the guys work. All I know for sure is that for several iterations of Cyanogenmod there was a "call delay". People would call me and not be able to hear me for several seconds. Very annoying bug. I resorted to using a CM Froyo build for a while and then a rooted OTA build of Gingerbread. It was acknowledged as an ASOP bug but wasnt present in the OTA builds of Gingerbread. This guy took the time and tracked the issue down and repaired it with a simple patch.

@Devastatin: The email is the right developer if you follow the above link you can see the name of the guy who I contacted via PM.

@GldRush98: You may have never seen this bug because I remember you commenting in a thread where you stated you only used OTA builds and not "janky custom builds like Cyanogenmod" which I am sure ruffled a few feathers.

But regardless it was a very real problem and there were a couple of threads in which people were asked to "star the issue" on Google forums. The first starred thread was closed, Google said it was hardware specific on the N1 and didnt address it. I dont know what happened with the second thread.

If you guys dont want to donate to the guy, nobody is forcing you. I just felt like the guy deserved some props for fixing an issue that noone else was addressing.

-D
[Nexus One General] jyxent:
I'm not actively soliciting donations, but if anyone wants to donate to me, I appreciate it. I just thought I'd post here to confirm my identity.

My changes to cyanogenmod are listed here:

http://review.cyanogenmod.com/#dashboard,1030

The a1026 suspend commit deals with the wonk, the call delay commit is obvious. If you click any of the commits, you'll see my email address there, as well.
[Nexus One General] bassmadrigal:
The other fixes were for a CM related issue due to merging of 2.3.3 with 2.3.4 which broke receiving MMS from certain other phones. All bugs were a major source of complaints on both the xda nightly thread (along with Fitsnugly's Gigglebread build) and the CM nightly thread with who knows how many countless other threads in both forums.

And AFAIK, google has not fixed the call-delay bug (the wonk didn't exist on the stock ROM) from everything I have read. It still existed on various 2.3.4 builds that I tested.

jyxent fixed some of the major bugs that were plauging N1 users (and who knows how much sleep cyanogen lost due to the wonk). If I can come up with some money on this next paycheck, he will be getting some... Until then, I will just sing his praises :D
[Nexus One General] dweebs0r:
Gonna give this thread a final bump in the hope that the N1 users out there will show this guy some love.

I realize fixing broken code and releasing it to the community is in the spirit of open source software but every once in a while I like to give credit where credit is due. My N1 is perfect (again)!!
[Nexus One General] Estimated Prophet Hawk:
I'm on CM7.0.3 and am still having to use dewonkificator because of phone delays. Is this for real or is someone trying to get some free $$?
[Nexus One General] RogerPodacter:
It's for real, and also seems to have side effect of greatly increasing battery life as well. Bit the fix is only in the nightlies which is why you don't have it.
[Nexus One General] dweebs0r:
You could apply the fix to the stable firmware. The dewonkificator was just a band-aid as this actually corrects the bug.

And the guys not trying to make any money off the code, it's freely available. I just think he deserves a few bucks for fixing a huge problem with our phones.
[Nexus One General] Muzikant:
I believe that this was truly fixed for most devices and the developer who solved it deserves the credit for it, but I'm sorry to say that I'm also still experiencing that call delay occasionally on my N1 running CM 7.0.3...

Edit: just after posting I saw the comment that this is only available on the nightly builds... thought this was already included in 7.0.3. Anyone has a clue on when it will be included on the stable versions ?
[Nexus One General] Babydollll:
I would think it would be included in 7.1 (or the next stable release (candidate) but I'm most likely wrong.

Oh, and the call delay exists in stock OTA builds. My husband has an N1 that is completely stock and not rooted, He has the call delay bug.

I didn't write that. ;) Prove it!!!
[Nexus One General] Ertavarez:
this patch can be applied to another ROM like stock GB 2.3.4?
[Nexus One General] m2xtreme:
I'll wait for the next stable CM

If the next stable CM has fixed the call delay, wonk, and has better battery life you can be sure I'll be sending out some donations! I flamed on the google thread about this issue; it was clearly an AOSP bug because I experienced it on CM *and* vanilla AOSP. I'm looking forward to the upgrade back to gingerbread but until CM drops another stable I'll be rocking Froyo :)
[Nexus One General] dweebs0r:
This problem is completely fixed in the latest nightly builds. You can apply the fix to the 7.03 build by pushing over the fixed libaudio.so file. Step by step directions are available here if you are uncomfortable using adb, search the forum. I attached the corrected file to this post. The fix was made by jyxent and he deserves the credit for fixing this problem.
[Nexus One General] Galloway:
Just so everyone is clear...the call delay bug is not just AOSP. I had it right from the get go in OTA 2.3.3 and it continued to 2.3.4. I am now using an AOSP build and don't have it :). I may have the MMS bug though as I can't receive certain MMS pics from certain phones/carriers. Have not narrowed down the exact issue yet.
[Nexus One General] baseballfanz:
CM7.0.3 is ancient compare to the latest nightly.:D
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
I have had the tablet and the dock battery's drain all the way while connected and with the tablet turned off. I do have the latest firmware for the tablet and the dock.

Has anyone else had this issue?

:confused:
[Eee Pad Transformer Q&A, Help & Troubleshooting] Gary13579:
The battery dock still has draining issues, even while off. I'm not sure why your tablet drained as well -- perhaps the dock started to charge it and tablet turned on due to it? or maybe the tablet started to charge the dock while it was draining and ended up both being dead.
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
yeah Im really not sure what happened but I do know when I went to turn on the tablet it started up and only had about 13% battery left when it was fully charged when I turned it off.
[Eee Pad Transformer Q&A, Help & Troubleshooting] frosty5689:
Check your wireless disconnect policies, if its set to Never then that might explain why.

Sent from my Transformer TF101
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
Im not sure where to check that.
[Eee Pad Transformer Q&A, Help & Troubleshooting] FrayAdjacent:
OFF as in you held the power button until it asked if you wanted to shut off, or SLEEP, as in just tapped the power button (or lock button on the keyboard)?

The Lock key on the keyboard, or just tapping the power button puts the unit in SLEEP, which is not really sleeping, it just turns off the screen and depending on your wireless power policy, WiFi may still be on. Apps still run. Stuff still communicates with the interwebs.
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
off as in i held the power button and hit shut down.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Tera Tike:
Mine is doing it as well. Did a complete shutdown yesterday after fully charging both the pad and dock. Just turned it on and the dock is blinking orange. I also had the WiFi disabled. Even when you do a shutdown it seems something is not shutting down.

-M
[Eee Pad Transformer Q&A, Help & Troubleshooting] oicu812:
ASUS never said that they fix the dock battery drain issue while tablet is docked and powered off. Have they?
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
im not sure. At least i know its not just me.

I hope they push the update where we can see the battery live for the dock soon.
[Eee Pad Transformer Q&A, Help & Troubleshooting] gadgetfann:
Mine is doing the same thing. Keyboard was charged when I closed the lid and then blinking 6 to 8 hrs later. Wasn't doing this with firmware .12 with the keyboard battery indicator. I really hope they bring back some of the .12 features soon.
[Eee Pad Transformer Q&A, Help & Troubleshooting] friedgoldmole:
My keyboard dock no longer seems to hold much if any charge, I left it charging yesterday until the keyboard dock light stopped flashing and stays on steady (I assume that means its full) and now 4 hours later the keyboard dock light is flashing and no longer charging the tablet.
[Eee Pad Transformer Q&A, Help & Troubleshooting] skunkape:
if i recall, this is a known issue with the dock. When not in use, it will still drain the battery. If plugged into the tablet at the time, im pretty sure the tablet will drain also. I think asus is aware and i thought i saw somewhere that there will be a fix once 3.1 is out, that will put the dock into a very low power state when not in use.

so i guess we will see once 3.1 is out
[Eee Pad Transformer Q&A, Help & Troubleshooting] ssj4vegita2002:
I believe only Solid Green is full.
[Eee Pad Transformer Q&A, Help & Troubleshooting] friedgoldmole:
Interesting I've only when seen a solid orange light, perhaps that just means charging, will try again tonight.
[Eee Pad Transformer Q&A, Help & Troubleshooting] bleclair:
Same issue. Had a fully charged dock and a partially charged Transformer.

Was very pleased to see the tablet start to charge when I docked it, and not so pleased when I got up in the morning and both were dead.
[Eee Pad Transformer Q&A, Help & Troubleshooting] checkbox111:
Leave it turned on then :D
[Eee Pad Transformer Q&A, Help & Troubleshooting] Jojobou:
Just for the record, I have the same issue. Dock battery drains really quickly when turned off and in sleep mode.
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
that might be a good idea it might not drain as fast!
[Eee Pad Transformer Q&A, Help & Troubleshooting] diecast17:
Does it help if I leave the tablet and the dock disconnected when turned off?:confused:
[Eee Pad Transformer Q&A, Help & Troubleshooting] guyvertje:
I'm 'glad' I found this thread. At least I know I'm not the only one. I got my TF 1,5 week ago. I don't have the keyboard dock but was unpleasantly surprised to see the battery life drain almost completely after leaving the TF fully charged for a few days.

Has Asus officially acknowledged this as a issue?
[Eee Pad Transformer Q&A, Help & Troubleshooting] Tera Tike:
Yes, Asus has acknowledge this issue and a few others. I have been told by one of their Techs that they will be releasing a new update sometime within the next couple of weeks if not sooner.

-M
[Eee Pad Transformer Q&A, Help & Troubleshooting] the_gunner:
I have not been shutting my TF down when not in use. Just putting it to sleep or letting it auto-sleep. I usually have it docked and connected to wifi when it's at home. I just close the 'lid' when I'm not using it. I've been getting pretty good battery life, and the dock seems to be retaining it's battery power as it should when not in use.

I'm starting to think it actually is better to just leave the TF on all the time, instead of doing a shutdown.
[Eee Pad Transformer Q&A, Help & Troubleshooting] dimebagslash:
Also having the same problem. My prime came with latest software though . And the dock had 40% battery... shouldn't it have been drained as i presume it would have been tested at the factory... the only thing i can think of was the position of the holder for the dock. Doubt it makes a difference but its the only thing i can think of so im going to try it tomorrow.

Jay
[Eee Pad Transformer Q&A, Help & Troubleshooting] Droid_Junky:
Same issue here. I though my wife had been using it while I was at work. Hopefully they release a fix!
[Eee Pad Transformer Q&A, Help & Troubleshooting] dgraziotin:
Another victim of the "dock drain while off" here. Only the dock drains, from about 60% to total empty in less than 3 hours. I am really happy about this device, in any case.
[Eee Pad Transformer Q&A, Help & Troubleshooting] thepatman:
How To Fix The Dock Drain Issue

RMA the dock. It's that simple. I just did it. Before, if the dock was connected, both the dock and the tablet would be fully flat in 36 hours (from fully charged). Now, with a hardware change from Asus, I'm 36-40 hours in and the dock is down to 65%, the tablet is 99%, no keyboard wakeup with trackpad or keypress.

In short, all problems resolved. Email them and say "I have the keyboard dock drain issue" and they will give you an address to email to get an RMA number. Your cost to send it back, they pay for the return - cost me $11 via FedEx, but I live 4 hours from a service center, so YMMV. They turned it around in 2-3 days.

Hope that helps - no software update will fix it. It's a chipset mismatch.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Droid_Junky:
Submitted my issue about two weeks ago. Finally got an email with the RMA form this morning.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Droid_Junky:
So it is now May 15th. After several attempts to get an actually RMA I spend $27 to ship it back. Finally got it yesterday. No indication that any repair has been made. Problem still exist. Battery drain occurs even when the tablet is turned off. I will never buy another ASUS product.
[Eee Pad Transformer Q&A, Help & Troubleshooting] hoang51:
Just for the record, I also have this dock battery drain issue when the tablet is connected to the dock and the tablet is off (not sleep). Only workaround I found was to disconnect the tablet and the dock so that the dock battery does not drain. The ICS firmware update (.27, Android 4.0.3) never fixed the issue by the way. Warranty is beyond over at this point in time...
[G2 and Desire Z General] teh5abiking:
Hello Everyone,

I'm well aware of the damage that a task manager can do to an Android phone, as well as the changes in the Android SDK for Android 2.2 and later which makes most of the task managers on the Android Market obsolete, but one thing caught my attention, this app called Autokiller Memory Optimiser.

According to some posts I've read on some of the forums, Autokiller justs tweaks Android's minfree values so that Android can kill tasks more efficiently or something like that.

Is this true or should I steer clear of this app?

And did I post this in the right sub-forum?
[G2 and Desire Z General] deliriousDroid:
I used a few different auto memory apps and have always found that my phone seems slower with them, uses more battery and I have less memory. So I just let android take care of me

Sent from my 'SilverBullet' HTCDesireZ running CM7
[G2 and Desire Z General] gbarayah:
The only 'task killer type' application that I have used is Watchdog Lite.

I use it to monitor rogue applications that use excess system resources while running in the background.

It does use some system resources to do the monitoring but its nice to know when a background app is going out of control and hogging resources.
[G2 and Desire Z General] redpoint73:
Android manages memory on its own, task killers are a waste of time. Unless you have a specific problem you need to troubleshoot with a poorly written app hogging app for no good reason (as mentioned above), I would not bother with them. Task killers waste resources, and can cause more issues then they solve.

http://lifehacker.com/5650894/android-task-killers-explained-what-they-do-and-why-you-shouldnt-use-them

Someone posted recently that a task killer was making his G2 power off randomly. He uninstalled the task killer, and the problem vanished.
[G2 and Desire Z General] xsteven77x:
The app that the op is posting about isn't a task killer. It modifies the system values/thresholds for when to kill stuff and flush memory and all that happy crap I don't really understand. I am guessing it would depend on the rom and how the dev have the values set to begin with. Just a guess tho.
[G2 and Desire Z General] infamousjax:
if you have an automatic task killer in gingerbread you're an idiot.
[G2 and Desire Z General] redpoint73:
In addition to tweaking the system values, it includes a process/service manager, same as any other task killer.

Besides, any app that claims to improve battery life and performance by freeing up memory is immediately suspect. Having memory free affects neither in Android.
[G2 and Desire Z General] xsteven77x:
Its not an auto task killer and its a supplemental part of the app. I used to use that app and never even looked touched or saw the taskiller part. Just saying. Its not its main use or strength and not really advertised as such!
[G2 and Desire Z General] Ace42:
They don't seem to know much about the very much :(, it is actually quite helpful on tweaking the android's "built-in" killer. It is not a task killer, the author of the app is a member of XDA and you should check out his work. A task killer is nice too, since many apps like Camera, gallery, maps, browser, etc are not kicked out until memory is "extremely" low. The G2 has what, 300-340MB free on a clean boot? After you open a couple of apps that will go to low 200's or high 100's. You may notice a difference in performance or maybe more battery drain from those apps staying open. I've used android since the G1 and can tell you that you dont want certain intensive apps to stay alive. But, this is just my opinion, not trying to attack anyone at all.

P.S. Here's a link to the app dev

http://xdaforums.com/showthread.php?p=5861010
[G2 and Desire Z General] redpoint73:
I don't see it as an attack, your opinion is welcome. Although from what I have read (link I supplied above), Android does not benefit from having memory free, as having free memory does not improve performance and battery life.
[Touch CDMA Android Development] andrewmp:
As my touch screen begins to select different areas randomly, I am eBaying a new digitizer for my 5 year-old HTC touch and wondering - who else is left using this as their primary device on Bell in Canada?
[Touch CDMA Android Development] Richard Langlois:
My Wife and I are still on Bell Vogue. A white and blue-grey one.
[Touch CDMA Android Development] andrewmp:
Nice! What are you running?
[Touch CDMA Android Development] theppler:
Mine is still chugging away running Fat Free Froyo. The 3 year contract is done in a month which is when I will lose my 1000min/month free long distance. Hopefully soon after that, the Samsung Galaxy S2 will be released in Canada. It will suck to have to start paying for data, but whatever I guess.
[Touch CDMA Android Development] WnG88:
Wife and I are still on vogue with Bell. Running Fat Free Froyo, not sure which version. For a while I kept 12 since I thought it was the most stable (with 10-04-10 .25 kernel ), can't remember what I have now anymore. Looking for a better combo, because I want apps to SD, camera, and USB mount. Such a combo doesn't seem to exist.
[Touch CDMA Android Development] margosmark:
i am still sticking with my vouge... for now
[Touch CDMA Android Development] leoleotheiii:
ME! I'm on fat free froyo as well, been waiting for another release of scoots 2.3, still have 5 month left on the contract
[Touch CDMA Android Development] min1968:
me. Using Super Froyo.

Bell prepaid. I cannot find any other plan better than mine: pay $11.3 every month, get unlimited data, unlimited msg (through Heywire), voicemail, CID, and still $7 remain can be used for prepaid voice call
[Touch CDMA Android Development] evader69:
My ex-wife and I are still on a family plan with two touches running fat free froyo. This phone is awesome! For the price for unlimited data I'm not planning to switch any time soon. (I even put up with the ex wife.. that's how good it is!!)
[Touch CDMA Android Development] andrewmp:
I'm on my 2nd HTC Touch. Currently I'm waiting for the digitizer to come in, the touch screen has become very sporadic. I'm using the Cyagenmod 7.0.2 build right now
[Touch CDMA Android Development] ericbond:
me! im still running the vogue as hard as the day i got it
[Touch CDMA Android Development] andrewmp:
My digitizer just came in, can't wait to get it up this weekend. I've been off FourSquare for weeks and it's killing me!