yashsingh1/xdaforums huggingface dataset:
[G1 Q&A, Help & Troubleshooting] Sleeps17:
Yep, that's exactly how it works. First off, are you using T-Mobile USA?

Remember to NEVER flash DangerSPL on a 1.x, 4.x, or 6.x radio!!

The following are compatible radios that you can safely flash before you flash DangerSPL:

2.22.23.02 (T-Mobile USA)

3.22.26.17 (Rogers CA)

3.22.20.17 (Orange UK)

2.22.19.26I (Non-US)

CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA
[G1 Q&A, Help & Troubleshooting] newbieforever:
using a T-Mobile G1 outside the U.S. ;)

ok, since i can't update radio as it stands, here's my plan.

1. reboot to recovery mode

2. flash HardSPL

3. flash radio

(... if radio update successful)

4. flash DangerSPL

5. flash CyanogenMod6

6. do the funky chicken!

sounds good?
[G1 Q&A, Help & Troubleshooting] Sleeps17:
Yes, but I don't think that will make a difference. You should be able to flash the radio successfully on a stock HBOOT. I've never had problems flashing the radio before, so I don't know. But sure, you can update the HBOOT to HardSPL, but I don't think it'll make any difference.

CyanogenMod V6.0.0 Stable / HBOOT-1.33.2005 / Radio 2.22.23.02 T-Mobile USA
[G1 Q&A, Help & Troubleshooting] machine*head*:
exact same problem

Having the exact same problem. I have literally spent 2 days trying to do this.

Trying to do the whole CMwiki procedure, unlockr procedure, and various others.

Luckily I didn't brick it.

But I am in the same boat, now matter what I try, after flashing the radio via

recovery amon-ra 1.7 I check on fastbook and it is still 1.22 version of radio.

I have the stock Hboot, etc....

Has anyone had luck with fastboot / adb flashing the radio??

Thanks for any help.
[G1 Q&A, Help & Troubleshooting] ezterry:
Flash HBOOT 1.33.2003:

http://xdaforums.com/showpost.php?p=6510019&postcount=76

Once 1.33.2003 is installed you can install 1.33.2005 via fastboot as on the post I linked to .. or skip directly to the newer 2708+ radios/SPLs with extra ram:

http://xdaforums.com/showthread.php?t=831139
[G1 Q&A, Help & Troubleshooting] ldrifta:
ok guys hopefully i can solve this problem.. i never had this issue but have had slight problems almost like so here was my solution....

Stage 1 un-rooting (very simple)

1. download update.zip and DREAIMG.nbh files here...

DREAIMG.nbh http://www.4shared.com/file/9izdCbvo/DREAIMG.html

update.zip http://www.4shared.com/file/ePnmmoxA/update.html

2. boot into recovery mode and do complete wipe of everything, also repartition your sd card set 0mb swap and 0mb ext..

3. then either use usb mounting through recovery or power off and place sd card in comp to copy files over.. than put back in phone and boot in recovery.

4. flash update.zip

5. power on in boot loader and flash DREAIMG.nbh

6. reboot and do normal setup just to make sure you are 1.0 firmware

Stage 2 Re-Root device..

1. download update.zip, flashrec, recovery.img, radio and spl files here...

1.5 update http://www.4shared.com/file/EyiKXmTd/update.html

flashrec http://www.4shared.com/file/ABXfQQ1H/flashrec-113-20091107-2.html

radio 2.22.23.02 http://www.4shared.com/file/jGTeRvfs/G1-radio-2_22_23_02.html

SPL http://www.4shared.com/file/nJkB58Qf/Latest_G1_SPL.html

recovery http://www.4shared.com/file/zCVPjMUz/recovery-RA-dream-v170-cyan.html

2. place files on your sd card than boot into recovery

3. flash update.zip (gets you to firmware 1.5)

4. now boot up normal and go to settings, check in applications and check unknown sources and usb debugging.

5. go to market and download "oi file manager" open app and select the flashrec file

6. when finished select open, then press backup recovery, then type in the box sdcard/recovery-RA-dream-v1.0.7-cyan.img then select flash recovery image.

7. when finished power off phone then boot into recovery.. wipe data factory reset, then flash the radio.zip press home+back to complete installation

8. wipe data again, now flash spl.zip, press home+back to complete..

9. now partition sd card.. i use 128mb swap and 1024mb ext4...

Stage 3 advanced rooting

1. download danger spl, fr boot, super wipe, radio and hboot files here...

fr boot http://www.4shared.com/file/gjRmpuh7/FR-boot-v157-CustomMTD_S.html

hboot (0.33.0013d) http://www.4shared.com/file/tfbsSTys/hboot0013d-signed.html

superwipe http://www.4shared.com/file/qm3gl7fQ/Ohsaka-SuperWipe_v2.html

radio (2.22.28.25) http://www.4shared.com/file/tMqoIX3p/update_2222825_S.html

2. place files on root of sd card

3. boot into revovery wipe data cache all that good stuff than flash the spl.zip let finish...

4. flash superwipe, power off than rebbot to recovery then do manual wipe of everything data, cache, battery, sd partition.. then repair sd..

5. flash the fr boot file, then go to console and type reboot recovery

6. flash radio file, let it finish then flash the hboot file.. power off than power on in fastboot mode (camera+power) and check phone stats.. should be on latest radio and hboot and s-on than you are free to flash roms from here...
[Touch2 ROM Development] xad_sandra:
Yes, I did last nyt... and now I can't use my HTC touch 2... How can I put it back in English again???:(:confused:
[Touch2 ROM Development] touchbaz:
what is the program you use for installing arabic language? added-value? or a cab file like arabizer?
[Touch2 ROM Development] xad_sandra:
it is value added installed and it said... arabic localization...
[Vibrant General] wbexpress:
I recently (this evening) installed Clockwork Recovery and some other assorted apps, and all of a sudden I can't turn off my screen with the power button. I do have "No-Lock" installed but I did not change any settings and I don't believe it has anything to do with the functioning of the power button to turn the screen on or off. When I long press the "Phone Options" menu still does come up. Has anybody had this happen? Is there an obvious setting I am missing? Thanks to all.
[HD2 Android Q&A, Help & Troubleshooting and Genera] S3BAZ10:
HD2 Screen "active" while in sleep. may be reason why battery dies so fast. (video)

i have noticed that the screen is active while supposely it is on "sleep" i noticed this only on light as you see the video. i was cleaning my HD2 and saw that. i think this may be the reason why battery may discharge so fast and phone may over heat. devs. please look into this. i am on energy july 14 21911 titanium, froyo build. latest zimage.

take a look: http://www.youtube.com/watch?v=g7akMTC8KTA
[HD2 Android Q&A, Help & Troubleshooting and Genera] Shushunmire:
Huh, the latest zImage fixed that particular problem for me.

Energy Rom - Cookie's Build.
[HD2 Android Q&A, Help & Troubleshooting and Genera] S3BAZ10:
hmm idk then, i overwrite it and see if it still presist. may you share your zimage? just incase its diff. thanks.
[HD2 Android Q&A, Help & Troubleshooting and Genera] numeria:
The latest zImage the PANEL_ON_OFF 7/25 doesn't work for me. It gives me the SOD.
[HD2 Android Q&A, Help & Troubleshooting and Genera] asphaltkiller:
same for me
[HD2 Android Q&A, Help & Troubleshooting and Genera] S3BAZ10:
yup same here.
[HD2 Android Q&A, Help & Troubleshooting and Genera] sea_man:
sleep & wake up work for me whit the zimage PANEL_ON_OFF 7/25

Edit: also i don't have any back-light while the HD2 are in sleep mode.
[HD2 Android Q&A, Help & Troubleshooting and Genera] numeria:
Must be nice. =/
[HD2 Android Q&A, Help & Troubleshooting and Genera] 23207:
The latest zimage works for me. No SOD for me so far.
[HD2 Android Q&A, Help & Troubleshooting and Genera] criszz:
same here , im very happy
[HD2 Android Q&A, Help & Troubleshooting and Genera] kibicer:
The latest (July 25) zImage also works for me, no problem at all. I am running Desire V5 build.

An overnight battery discharge was 40% in 7.5 hours.
[HD2 Android Q&A, Help & Troubleshooting and Genera] myself11:
Do you notice less battery drain with the new zImage?
[HD2 Android Q&A, Help & Troubleshooting and Genera] marios96:
Actually, the first couple of times you turn the screen back on, it takes a few seconds to show the lock screen...
[HD2 Android Q&A, Help & Troubleshooting and Genera] mystik610:
Ditto. TMOUSA, Latest Energy ROM
[HD2 Android Q&A, Help & Troubleshooting and Genera] narta:
Guys I only had 8% discharge in 8 hours last night only phone funtction working (WiFi/data off). FroYo V1 with latest zImage from Cotulla. I think that you have to manually set screen brightness. We had the same problem in the ported Desire builds and that was the culprit
[HD2 Android Q&A, Help & Troubleshooting and Genera] numeria:
I'm using the same exact one.
[HD2 Android Q&A, Help & Troubleshooting and Genera] kibicer:
What radio and ROM are you using?
[HD2 Android Q&A, Help & Troubleshooting and Genera] bazgee:
So does anyone know why some of us are having SOD and others are not with latest zimage ???
[HD2 Android Q&A, Help & Troubleshooting and Genera] ATomCZ:
I tested latest ON/OFF PANEL zImage with Desire v5 and Froyo Sense PR1. With desire works fine, only android freeze for short time sometimes (maybe too often), but still works. But with Froyo Sense PR1 don't, it freeze completely. And I think that booth Androids works most slow. Froyo is unustable, too much slow, but it was slow also with older version of zImage. I thinked that Froyo will be faster.
[HD2 Android Q&A, Help & Troubleshooting and Genera] rustydraft:
Ditto..... I have SOD with new zimage. energy rom, desire v5.
[HD2 Android Q&A, Help & Troubleshooting and Genera] narta:
It seems its related to the panel your device is running

try to help the devs guys

download the SDK, hook up your phone, run cmd (in windows), navigate to the tools folder of the SDK and type

adb shell (you will see a #)

dmesg | grep panel

and copy paste the outcome here
[HD2 Android Q&A, Help & Troubleshooting and Genera] NRGZ28:
Seems Cotulla is on it. SHARP panels (TMOUS models) will have the SOD problems. I think Cotulla already fixed it.. just waiting for him to release a new ZImage...
[HD2 Android Q&A, Help & Troubleshooting and Genera] S3BAZ10:
do you know around what time hel be releasing it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] kibicer:
I've been running Desire v5 with the latest zImage for last 24 hours, not a single problem so far.
[HD2 Android Q&A, Help & Troubleshooting and Genera] RuffRap:
i use the latest zimage and desire v5, stock ROM 1.66 GER.

discharge in ca. 6 hours ´round 10% at all. no crashes, sod or something.
[HD2 Android Q&A, Help & Troubleshooting and Genera] tgerbracht:
Heh, learn not to ask. My guess would be in the next day or so if history serves.
[HD2 Android Q&A, Help & Troubleshooting and Genera] schmao:
I have a TMOUS HD2 with an Energy ROM. SOD dissapeared when I used Not the latest Z-image but the one the came out right before it. Try it and see.
[HD2 Android Q&A, Help & Troubleshooting and Genera] fi3ry_icy:
using the 3 aug zImage...

still having SODs when others dun..

my phone was purchased in may this year in singapore... any1 have any idea if it is one of those phone with sharp lcd or is it only Tmous models which have them?
[HD2 Android Q&A, Help & Troubleshooting and Genera] drwolfford:
I just loaded the newest version of dan's froyo and everything works except I hear the robot voice every now and then and I used to get the SOD until I activated screen lock.
[HD2 General] GLO:
Hi,

I am looking for feedback from other HD2 users who use their HD2 to increase their productivity.

Im currently using Energy Roms with the following:

Nuevasync (syncs Google Calendars with Outlook and my wifes HD2, sharing same calendar)

Im looking for a Over the Air tasks/To Do list that will sync with Outlook also.

so that i can do the same thing ie sync with outlook and subsequently mny wifes Handset.

I read alot that many people like Pocket Informant but how does that interact with Outlook mobile and HTC Sense.

Thanks for your input.
[General Questions and Answers] Stryder3:
Hey guys, I just recently rooted my phone and installed the newest Cyanogen ROM.

But I have a problem.. Whenever I try to install apps to the internal memory on my phone it will crash and reboot before it installs...

Also when I try to copy apps to my phone from SD card it says 'Memory full' but I still have 170MB's of internal memory available.

When I use the Terminal Emulator on my phone to 'fix_permissions' it says Permission denied for each one..

I have manage to use the ROM manager to do Fix Permissions, but it didn't fix the problem.

Could this be I have somehow lost root?

Or would it be something went wrong with the ROM installation? :confused:

Thanks.
[Vibrant General] iunlock:
SHOULD I USE A TASK KILLER?

The tips&tricks thread (nice by the way) answered;

"Absolutely not. You have the best OS and one of the best spec'd phones ever. You would be doing more harm than good. If you do have one, uninstall, reboot and let me know what you think!"

I don't get it. You'll be doing more harm than good? Right now I'm using Advanced Task Killer along with Auto Task Killer and it has definitely made a difference in my battery life.

Why would you NOT want to have these apps?

I'm confused LOL :confused:
[Vibrant General] iceman1251:
I don't use one at all. I don't see the need for one on this phone...
[Vibrant General] iunlock:
It surprised me when I did see all the programs running ... would it not be of a benefit to close those for the sake of the battery? I found this to be very true and it was a noticeable with my battery.

I'm just trying to figure out why that other guy would say to uninstall it. Reasons...
[Vibrant General] ArcticWolf91:
I was using one for reasons of speed, but I stopped using it and I honestly did not notice a difference in performance or battery life. So for me, I will no longer be using a task killer. I simply don't see the need.
[Vibrant General] speoples20:
In the time of low spec'd Android phones it was need. But with phones with fast processors and lots of ram its not really needed any more. Some people have said it even slows down the phone.
[Vibrant General] djunio:
Task killers are a waste of time for any phone that has 256 RAM and up.
[Vibrant General] s15274n:
I'll let others chime in, but the reason I put that in the sticky is because I listen to those who know more than me... and EVERYONE who is in the know with android (developers and google) suggest task killers do more harm than good. I did not intend to come off harshly in the sticky, but I don't want those new to android thinking this is something they need to do.... when in fact, it could cause a lot of problems and they would not even be aware it was the cause.

Hope that helps, a little...
[Vibrant General] S4X:
OK, like the OP, i do not get this claim that Killers do more harm.

Suppose you started a game which took 50-100K of your valuable RAM. Even if you have 500K of it, not much is actually left for apps. Even if you quit playing the game or other memory hungry app, it often still hangs in memory. Eventually you will have several pages of different apps which you've used over last days

What's wrong is with kicking them from there? How can this be harmful? That's sounds like a nonsense.

Don''t you all know also that unused memory is switched off by power management to save the battery?
[Vibrant General] s15274n:
Hahaa... okay, you are correct. Google and the ROM chefs are all wrong. Android is not capable of killing off apps when they are no longer needed. Everyone, rush to the market and immediately start killing off every app the second you close it. Especially the system apps you never use.

Alright, enough sarcasm (didnt mean to sound rude). Like I said in the sticky and above, I am only quoting those MUCH more knowledgeable on the subject. I will admit I purchased a task killer 2 years ago... and I hate seeing it under "Downloads" in the market as "Purchased" now. If you feel the need to kill off apps, so be it. But for those new to Android (and those who are very familiar), it is mine (and others) opinions, especially on the Vibrant, to not use a task killer.

Even Google at Google I/O 2010 told app developers to no longer add "Quit" or "Close" into their apps, as they were NOT needed.

This thread helped me. I have cleaned up the Sticky with more input. Here is a good article from a few months ago that sums it up well (also now in the sticky):

http://androinica.com/2010/05/07/go...-imply-task-killermanager-apps-are-pointless/

To the OP, thanks... this did help me and I'm certain a lot of others were probably put off by my vagueness. Do you think this makes it better now? Anything else needed you think?
[Vibrant General] iunlock:
I really appreciate your dedication and yes it did help me built onto my knowledge base. As I always tell people, "If you don't know what you don't know then YOU DON'T HAVE A CHOICE, however, if you do know than YOU THEN HAVE A CHOICE."
[Vibrant General] heygrl:
I really think using AutoKiller is a better method to controlling what you have running in the background.
[Vibrant General] dan0zone:
Finally someone to educate the masses ... time to get them off this task/app killer *CrAcK*

Dan0zonE
[Vibrant General] SykesAT:
As said previously. Maybe worth using them on a G1 but not on any recent phone.

For those who do think it worth running them. How quickly do new apps open? Lets say you kill 30 apps, how long before 30 new apps are running? 20mins? If it's such a huge drain on resources why has google not fixed this issue, its been around since the first retail offering G1 with android 1.1? In fact, as previously pointed out google does not recommend even using task killers. I would say using a task killer to kill the apps is a far bigger drain (cpu, battery) that allowing android to as it was intended.

Android is not like windows. Android will shut down and make available what is needed. It does not need any help.
[Vibrant General] techpreneur:
They cause more problems than good. Task killers slowed my phone down more.
[Vibrant General] masterotaku:
The problem with task killers is two fold.

First you have to really grasp what you are killing. Many apps and services are interdependant so killing the wrong app or process can result in apps dead-ending, or worse locking up and taking all the cpu task time (which will make battery use worse).

Second, everyone's phones are different. We may all run an identical build of 2.1 on our Vibrants, but I'd wager each of us is running a different set of 3rd party applications, so anecdotal statements that "task killers work" don't necessarily mean anything, other than for you specifically.

Here's the bottom line. So long as you do not have a buggy app taking ridiculous amounts of cpu time your battery life is solely dependant on what you are doing with and have installed on the phone. The Android Service UI does an excellent job of handling task management, providing those 3rd party tasks are behaving. Apps on the market do not go through an orwellian level of scrutiny like on the Apple App Store, and many (if not most) are currently in a constant state of development owing to the explosive growth of our smartphone platform.

And one additional tip thanks to the Vibrants styling. As the phone is incredibly thin, it's quite easy to feel when the cpu is a crankin! If after you've locked your phone for 10 minutes or so the upper middle back is warm? You probably have sleep issues with an app or apps. :)

In essence welcome to beta testing, even if you didn't realize it. And welcome to the consequences of an open platform. :)

Use the built in battery stats, market apps like spare parts, and you can likely discover what 3rd party apps you may have that are giving your battery grief. The level of detail you can gain from the built in stats in 2.1 are excellent and immensely useful, providing you use them.

In my experience apps and widgets that routinely poll for data and interrupt the phone's sleep process are the main culprit you can control. And the OS's built in battery usage statistics can really tell you what is going on.

Some apps may look cool and do great things, but if they're interrupting the sleep process or eating entirely too much cpu when they are active, you're probably best off trying one of the gazillion alternatives to that app available on the market.
[Vibrant General] adamparker17:
I flash my occasional ROM, but am not a developer of any sort. this post has been great insight into my many attempts to "protect" my phone from the running apps. I did start to notice that advanced task killer was asking me to shut down system processes that I would never know what they do. Now obviously I can see the third party apps and scrolling widgets that needed to be closed when I finally let my device sit, but after uninstalling ATK I have found that my device is actually running more smoothly.

FYI - a simple battery pull at the end of the day has been my best medicine.

thanks for the discussion guys!:D
[Vibrant General] AVonGauss:
I hope that was meant as a jest.
[Vibrant General] kizer:
Never used one on my G1 from the day I bought it an I was one of the early adopters, and now to the Vibrant.

I've always had awesome battery usage and I just use my phone. I've never used a task killer in my PC so I don't see how this is any different.

Task killers are IMHO a waste of space and money if they charge.
[Vibrant General] s15274n:
This is one if the best threads on XDA about task killers. I will make a point and link it in the sticky thread also. Really encouraged by the Vibrant forums.
[Vibrant General] couped:
From what I have heard, tasks when you first load a rom need to run to configure. If you keep closing them they will keep trying to run to do what they need to. So, it actually slows you down.
[Vibrant General] DKYang:
Download System Panel and see how many of the apps are actually active. I had one other task manager and it said a lot of the apps are running, but when I opened System Panel, most of them were just cached or on standby and not using much of the battery. I only use System Panel to monitor, but they have options to kills apps if you want to.
[Vibrant General] iunlock:
Appreciate it and thanks to all for their input. :D
[Vibrant General] iunlock:
Thanks for the great info. I uninstalled my Automatic Task Killer and I do notice that the phone is much snappier.
[Vibrant General] S4X:
:) Wow, not just stopped using but uninstalled.

I am sure you WILL return it back.

The Google requeirement not to exit apps like we usually do, is coming from the fact that cellphone must be ultimately simple to use, the OS will be serving even total mental retards and the phone apps must decide everything for them. Apps have to slow down almost to zero being in background.

That's in theory. In practice, they still will suck the resources. And with 100th of them (not switched down in say 3-6 months) as RAM approaches 1 GB you will notice the difference.

If you will not exit or kill them they will not be just hanging in memory and collecting the dust there. Even not in foreground, on low priority, they are still multitasking and interrupting processor. Swapped to flash to free some RAM they will even more slow other tasks, processes and services.

You think all 100% app developers are smart and care about your cell battery life when apps are not in foreground? I'm not so sure. We do not have Steve Jobs to police them. The only what we have is task killers
[Vibrant General] kolyan:
so what about 1500+ positive reviews (mostly positive) on Autokiller ? some devs even include this in their roms.

I know that 2.2 manages tasks differently and therefore has 0 use for task killers (dont know about Autokiller because its actually different from others), BUT I think 2.1 still takes some advantages from killers.

the key notes are 2.2 and 2.1 are VERY different in managing apps. and What makes Autokiller so different from other task killers (looking at all positive reviews)