yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] Evo4sickness:
I

I understand this and I have a live to and this problem is messing woth my phone.

Ok yes Iam sure they are backed up using Amon Ra as I was able restore my stock sense rom and the Cm7 rom I made s day after installing it. My problem is this I troes to make a new nandriod because I was going to do the gps fix this was 3 days ago. When I went to fill in the boxes is when I made the mistake of Xing the ext sd when did this is when I had the opps something went wrong check your recovery log.

Ok so far Iam sure you can now understand the proplem and where Iam. Next I tried to look in recovery without seeing anything in the cache/recovery log. So the only thing I have done is swith sd cards to see if that would change anything. I have my main Sd card wich is the 8gig and a second 2 gig sd card with my two nandroids that O mentioned above and work properly. So I just have to find a way to erase the error from Amon ra. Some people are suggesting to format the 2 gig and than try again. I just cant put the files on my computer right now because my usb ports are gone. And I tried to do the.transfer with a ftp app but it was takingover two hours and at one point looked like it had stopped. So goimg to try to go the.fedex store to put.the nandriods on.the comp and format the sd card and see if that works. Just want some more suggestionsbecause other people have had this prpblem and not have to start feom scratch.
[EVO 4G Q&A, Help & Troubleshooting] Evo4sickness:
Do you have any way I can get this error taken off without reinstalling everything and starting fron scractch. Have you ever herd of this error being caused by a sd card not being read correctly.
[EVO 4G Q&A, Help & Troubleshooting] dougjamal:
No sir, I do not. Sorry. I wish I was able to actually see your device firsthand so I could offer better assistance, but that not possible and there is nothing else I can think of that could possibly solve your dilemma without starting from scratch.

posting & replying via the XDA Premium app.
[EVO 4G Q&A, Help & Troubleshooting] plainjane:
Have you tried switching to ClockworkMod?

Either try switching and then see if you can make a backup, or download Amon Ra again (don't use the same one you have, get a new copy) and reflash. If you cannot backup with ClockworkMod, you know that it isn't a recovery problem... most likely, anyway.

Before you do that, go into recovery and move the recovery log to the SD card. I believe it's under "other", but it could be somewhere else. Do that, then try reflashing a fresh copy of Amon Ra or ClockworkMod.

ClockworkMod: http://db.tt/9sksyTK

Amon Ra: http://db.tt/WP0beNa
[EVO 4G Q&A, Help & Troubleshooting] dougjamal:
Great suggestion....;)

posting & replying via the XDA Premium app.
[EVO 4G Q&A, Help & Troubleshooting] Evo4sickness:
Ok I finally wad able to fix my problem. Theres asll was a member at andriod forums that finally told me how to aftually perform the task of getting the log file. And not just telling where it suppose to be once you do the process. And was finally able to get the log. Nobody told me thst after getting the error is wheb yougl go to the front of Amon ra and go to other so you can send the log file to the sd card. And it turns out thats it was of space.
[EVO 4G Q&A, Help & Troubleshooting] plainjane:
I said that a couple of posts back, should've said it earlier... but when you said you checked the log file I assumed you had already done that. Oh well, glad you go it figured out.
[EVO 4G Q&A, Help & Troubleshooting] Evo4sickness:
Yeah thanks just wasnt really explained well in this thread.
[Fascinate General] preymond:
Heres my situation:

I installed the froyo rom without installing the new CWM first. So i tried renaming the new cwm and replacing it with update.zip to no success, and never reverted back to the old one. Now i decided to revert back to stock, install the new CWM, and than flash the froyo rom. But something went wrong.

I flashed odin stock-i500-vzw-system.tar.md5, and upon reboot it sounds the vzw sound, but stays in the samsung bootup screen, and it won't go into recovery because my update.zip is broken.

My odin for some reason fails every time i try to flash the old recovery, or the old kernels, it only wants to flash system.tar.

Thats as detailed as i can get it for now, any help would be great.
[Fascinate General] zander78:
look around for some different stock odin files. i had a hard time with flashing cwm files as my phone just wouldnt accept them for some reason.
[Fascinate General] preymond:
i'm gonna try adrenalyn's system.tar, kernel and CWM DI01 package, see if this works. keep fingers crossed
[HD2 Android Themes and Apps] andrewf403:
Hello!

Would anyone, please, upload new Google Maps 5.1 apk? Here in Ukraine I cannot see Google apps in Market.
[HD2 Android Themes and Apps] karendar:
Give me a minute, I'm currently downloading...

If you want you can just use MarketEnabler and set it to a US carrier... Then download it from there. Cuz I'm having market issues!
[HD2 Android Themes and Apps] justwonder:
Here you go
[HD2 Android Themes and Apps] controlpete:
Any changelog?

A possibility to change a guidance voice would be nice.
[HD2 Android Themes and Apps] andrewf403:
Thank you!

Main changes - Google Check-in for Latitude. Something like Foursquare, but from Google.
[HD2 Android Themes and Apps] nadram:
Oh thank you so much

I've been itching to get my hands on that since I read about it... 20 minutes ago? :P

Awesomness
[HD2 Android Themes and Apps] mbdroid:
@justwonder, thank you:)
[HD2 Android Themes and Apps] s_saiyen:
Thank you

Thank you so much
[HD2 Android Themes and Apps] rickytr23:
thkz for the app:D
[HD2 Android Themes and Apps] tcblues:
Thanks a lot!!!

I've installed it and when I clicked on "About" says 5.1, great!! but... no check-in option available, it looks like Latitude is not updated :(

Any idea?
[HD2 Android Themes and Apps] uid95353:
same behaviour for me too
[HD2 Android Themes and Apps] vincie76:
Shukran (thank you)
[HD2 Android Themes and Apps] drigy:
Jap, I dont have check in option neither. Does it only support certain countries? Could be.
[HD2 Android Themes and Apps] jucosorin:
Thanks for the app

Thak you for the app! Same problem here also. I am not able to check-in.

Can u tell us what u do in order to check-in?

10x
[HD2 Android Themes and Apps] goal139:
guys, try this
[HD2 Android Themes and Apps] inspiron78:
Thank you so much
[HD2 Android Themes and Apps] akos.szekacs:
thank you very much
[HD2 Android Themes and Apps] exnavi:
Great mate.. ive been searching for years.
[HD2 Android Themes and Apps] chrisgestapo:
Couldn't find it on the market. Thank you!
[HD2 Android Themes and Apps] mumtaz64:
thank you :)
[HD2 Android Themes and Apps] ceftelos:
Thanks a lot!!!
[HD2 Android Themes and Apps] tdizzle404:
how do you enable 3D maps?
[HD2 Android Themes and Apps] tcblues:
hey, anybody knows when checkins will be available in Iceland?
[HD2 Android Themes and Apps] waqarhussain22:
thanks dude
[HD2 Android Themes and Apps] xvip87:
good

Google Maps 5.1 is good :)
[HD2 Android Themes and Apps] almwhob:
can i have arabic maps ??
[HD2 Android Themes and Apps] jaymact:
thanks too
[Vibrant General] musikalharmony:
then musikalharmony is my g mail or go to my youtube page musikalharmony or twitter musikalharmony ill be glad to help any one with rooting flashing roms themes ect...
[Captivate Q&A, Help & Troubleshooting] PizzaAmerican23:
this was my previous thread about this phone:

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

the phone wouldnt get recognized by a computer no matter what. Different computers, cables, drivers, modes, etc.

So finally i decided to just do a factory reset on the phone, and hopefully that would fix it. Well now it boots up into the ATT screen, shows the samsung S screen, and then just stays black.

I had to make a JIG for my other phone, so i used that to put it in download mode, and planned on flashing back to JF6 through odin. My computer still won't recognize it, so i cant flash to anything. Am i screwed? any idead on what to do?
[Captivate Q&A, Help & Troubleshooting] diablo009:
What is the build number of this phone? U can find the build number under the battery.
[Captivate Q&A, Help & Troubleshooting] PizzaAmerican23:
not the s/n right?

i see a 1007 rev 0.4
[Vega General] strictlysocial:
Quick question. On my Galaxy S, you can bring up a task menu of previously used apps by holding down the home button. Is there any way of doing this on the Vega without the home button?
[Vega General] O_G:
Button Savior

Quick answer:p. Use button savior its a great app (available on the market) Adds the missing buttons as on-screen buttons. Long press that Home on-screen button and the recent apps pop up.
[Vega General] strictlysocial:
Thanks. Works great
[Gen8 General] melax:
Here are all Archos Gen8 firmwares you can download. If needed..

http://www.arctablet.com/assets/archos-firmware/
[Gen8 General] gbohm:
oh great tip bookmarked ;-)

thank you

btw :is the thank button comming to the xda app any time soon?
[Gen8 General] sdho:
thx, I was having problem downloading from archos site...
[Focus General] squarejp:
I own both Samsung Captivate and Focus, both devices have SUPER AMOLED screen. Both devices have burn-in problem after months of usage.

Captivate:

I could see the notification bar on top of the screen with the fuzzy clock and battery indicator burn-in to the screen with very pale color especially very noticeable with a white screen! I also saw AT&T stores had these demo units experiencing the exact problem! I then called up Samsung to replace the Super AMOLED screen. Now it's fine but very annoying.

Samsung Focus:

I just got mine in Dec and didn't use a lot on that device. There is a very good reason why WP7 has to hide those status indicators on top to prevent Super AMOLED screen burn-in problem. I also checked out the demo units in AT&T stores, all of the Focus had Windows Phone 7 logo burn-in to the screen at the top left corner due to the static logo constantly playing on the demo mode.

In conclusion:

SUPER AMOLED screen's quality life-time is still short compare to LCDs. Given about 2 months of usage, 8 hours a day with static image such as notification bars for example, burn-in issue is inevitable! In real-life daily usage, give it about 2.6 hrs a day, your screen will be burnt after 6 months.

NEVER USE SUPER AMOLED SCREEN WITH STATIC IMAGE!
[Focus General] wildbilll:
On my phone the screen isn't on for very long periods. Even when I am talking on it if near my face the screen is off.

How does this compare to your experience?

Does a phone in demo mode have the screen on constantly?
[Focus General] foxbat121:
The only reson OLED isn't so widely used is because of its limited life span (especially on blue color). From what I read in the past, it is very difficult to get blue channel pixels pass 2,000 hours of life span. Not sure if AMOLED or SAMOLED made any advancement in this area. So, the precautions should always be taken. Let your phone screen on 8-hour a day is not a good approach. That's why there is a setting to let phone go into sleep and turn off the display.

My Captivate has been working flawless since August 2010 with zero image retention or burn in.
[Focus General] squarejp:
How many hours per day do you keep your screen turned on? I would give that minimum 480 hrs with static image to experience burn-in. No need to wait 2000 hrs of life-time in Blue Channel in AMOLED.

The life-time of the entire Super AMOLED is here and I'm also being conservative: 480Hrs to start to get burn-in issue using AT&T store demo units as reference.
[Focus General] squarejp:
I use skype and bluetooth headsets alot, so screen shut down may not happen at all until i manually shut off the screen. Moreover, using GPS navigation will definitely cause burn-in problem with static images such as the miles, eta, notification bar, clock, battery indicator, etc.

Android is just not a good OS for Super AMOLED. WP7 on the other hand is for Super AMOLED.
[Focus General] foxbat121:
I'd estimate less than 30 minutes total per day (only counts screen on time). So, 480 hrs should let me use my phone for 960 days, or way beyond my tolerance for an *old* phone.

If I'm sitting in a meeting broswing internet or reading news using some apps, almost all of them are full screen and won't necessary have static images on the fixed locations.

Turn the brightness down (I use auto brightness setting) and don't let the screen on for extended period. You will be fine.
[Focus General] foxbat121:
I have to agree. The metro color schem (black in most of the screen) is the best way to reduce AMOLED battery usage and lower the potential burn-in risk.
[Focus General] AllTheWay:
I have both devices and neither or them display image retention. What method or program are you using to test this?

I downloaded a flashlight app on the captivate and on the Focus so I could turn the whole screen white. I also adjusted it to other color,s still see no burned in images.

I've had my Captivate and Focus since day one when they were first released by AT&T.
[Focus General] squarejp:
Go to any AT&T cooperate stores to check out all the burn-in screens. For captivate I use screen test. It cycles from white, black, green, red, blue, and other pallets. I can garauntee you that all Super AMOLED screens are the same given static images and keep the screen turned on such as notification bar, full battery notification, GPS app.

If you don't have any burn-in problems that means you haven't used the screen long enough even you got your devices since launch.
[Focus General] foxbat121:
The key here is to keep the screen-on time as short as possible. For normal usage, it will be fine. Will it have burn in 2 or 3 years down the road? Sure, but I probably have to dig it out from the bottom of my drawer to check it out by then. I'd rather enjoy my sharp crispy and colorful SAMOLED for 2 years than worry about burn-in and settle for murky, low contrast and washed out color of the LCD screen for 2 years.

Store demos are the worse case senario.
[Focus General] squarejp:
Very true! But still people really need to beware of their SUPER AMOLED screen. But for gamers...... make sure don't allow a static screen staying on for too long.
[Focus General] jmerrey:
Well, I was reading an email yesterday on my focus and noticed that the smiley message icon was like a little ghost in the background. I also noticed the circle/arrow icon. I use orange on black mainly. I moved the tiles around a bit, we'll see if it goes away.
[Focus General] manu81:
and disappeared?
[Focus General] jmerrey:
No, it did not go away. It's only visible on white screens, but it is definitely there. I guess I'm going to drop by the at&t store to see if it's a warranty issue, but I highly doubt it. My guess is I'm stuck with it. Since I use the black theme it's not a huge issue, but when I switch to the white theme it looks pretty awful.
[Focus General] DaFlake:
Why beware? Image Persistance can happen on any screen that is left running static for long periods of time. In most of the AT&T stores that I have been in the demo units are set to stay up and running for which I can only assume is to attract people. This will cause the image persistance that you are talking about. These phones screens also get used a lot more than your personal cell will.

Use your phone and don't worry about something that may or may not happen. In two years or less you will likely have a new one anyway.
[Focus General] Rayan:
Hilarious!

This reminds me of the times where projector tvs and lately plasma tvs exhibit the same not-suitable-for-gaming problem! LOL

That's one of the reasons I got the Motorola Atrix with its LCD screen!

My previous smartphone was a Nexus One and even though it didn't exhibit ghosting problems, I always tried to use it as little as possible and used the screen on its dimmest setting.

Now I can leave the screen on at full brightness for hours (like for GPS driving for instance) without any remorse! :)
[Focus General] day2die:
I have the the imprint of Internet Explorer Mobile's chome burned onto my screen.

1+ hour of continuing browsing daily.
[Focus General] D79_:
Im a high internet user and txtin user etc.. and on my old galaxy s i had the qwerty keyboard burnt onto my screen and not i have my galaxy s2 i can see the same thing startin to happen. For me if this isnt sorted by the time i get another phone in say a yr n half, as much as i adore my amoled screens im defo not goin down that rd again, wat a shame they cnt sort this out, and they r makin thousands of phones and tablets with these screens, so not cool samsung
[Focus General] foxbat121:
They have been trying very hard in the past decade or so. The main problem is the blue channel pixels' life span. Most companies have ditched their effort and move to other technologies. That's the main reason why there is no consumer TVs made of the OLED screens other than the $4000 Sony 14" OLED tv.

Unless there is a scientific breakthrough, this situation will remain for years to come.
[Focus General] Scipio Magnus:
Has anyone dealt with Samsung Tech support on this issue I just got off the phone with them and they wanted me to do a Hard reset. I tried to explain that this was a physical issue, but they still wanted to follow their script.

Now they have sent me a label to send it off but want me to remove my SD card. It ismy understanding that this card is bonded to the phone and cannot be used in a replacement phone if they send me one. I am going to call them back ut based on my previous conversation I am not holding out hope that anyone there will know what I am talking about.
[Focus General] dmw_4814:
It is my understanding that your MicroSD card, if it came from another WP7 device, should be able to be used in any other WP7 device. It just cannot be used in anything else unless you reformat it with a Nokia phone running the Symbian operating system (I also heard a digital camera can reformat it, but I'm not sure about that) because WP7 devices encrypt it with some sort of password protection that renders it useless in anything else (this is done to protect your data from prying eyes, should someone get a hold of it).

Put it in your replacement phone and do a hard reset when powering it up. You should be O.K. then.

Someone correct me on this info if I'm wrong.

Dennis
[Focus General] jeremyshaw:
If you look at the pentile layout, it all makes sense now, LOL.
[Legend General] relomega:
I currently have a HTC legend and it is from Bell mobility, I want to use it on the T- mobile network. Everything works except for the mobile 3g internet and picture messaging. I did the setup in the settings/ wireless networks but the 3g part of it still seems to not want to work. I was wondering if there is a flash available? Any help would be greatly appreciated! :D
[Legend General] marclh1992:
I'm pretty sure T-mobile uses different bands than the phone supports, AT&T will work with 3G though.
[Legend General] relomega:
Ahhhhh, don't tell me I have to go back to At&t????
[Legend General] marclh1992:
Unless you can live on EDGE only...

Sent from my S-OFF Bell Canada HTC Legend.
[Legend General] relomega:
Well what about a radio update? Could I update the radio on the legend and gain access the the 3G network?
[Legend General] marclh1992:
The hardware will only let you on certain frequencies, T-Mobile does not use those frequencies. You cannot change those frequencies with a radio update.

Sent from my S-OFF Bell Canada HTC Legend.
[Nexus S Q&A, Help & Troubleshooting] risegeek:
Hey all,

I've tried on multiple occasions now to overclock my phone, using both the Trinity & Netarchy (1.1) kernel, everytime I have done so however it will put me into a bootloop, sometimes not getting past the nexus boot animation or lock screen, I'm sure that I'm doing everything right :(

1. Wipe data/cache

2. Flash ROM (I've tried Stock, Bionic, CM & Modaco, which I use currently.)

3. Boot

4. Flash kernel

5. Boot

I've no idea what's going on, I've just about given up, perhaps I've been handed a crappy piece of silicon, should have returned it before it was too late :)

Any help appreciated anyways, peacee.
[Nexus S Q&A, Help & Troubleshooting] Xandlinger:
Instead of flashing the ROM and then immediately applying the kernel, let the phone completely reboot. Then go back into recovery and flash the new kernel. Should work.
[Nexus S Q&A, Help & Troubleshooting] risegeek:
I've tried this already dude, probably should of mentioned it in my steps :( cheers anyhows
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Which variations of the Trinity and Netarchy kernels have you tried and for which rom?
[Nexus S Q&A, Help & Troubleshooting] risegeek:
I've tried Trinity 1.2 > 1.4 on Modaco, Bionix & Cyanogen platforms

I've tried Netarchy 1.1 > Modaco & Cyanogen (1.0 was actually working but following the thread it wasn't actually applying the overclock :rolleyes:)
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Have you tried Netarchy 1.2 yet? I've had a lot of issues with CM7, including kernels. Sometimes I would have to just flash the kernel 3 times and then it would work. Now I'm using MoDaCo and it is infinitely more stable. I've noticed the trinity kernels tend to be a little more volatile and hit or miss than the Netarchy one seems to be. If it is really of grave concern to you, if you live in an area where a return would be easily possible and if you are within your return period, return it and try a different slice of silicon ;)
[Nexus S Q&A, Help & Troubleshooting] risegeek:
I've actually had this phone since release date, sadly I am out of the return period, I don't really mind all that much, this phone has been amazing ;) coming from a constantly slow and crashing iPhone 3G.

I've just downloaded the new kernel from Netarchy, it seems to address stability issues regarding voltage, which I think it might be. I'll flash it and update this post in a second.

EDIT: Hasn't helped :( seems to be looping at the Google screen now.
[Nexus S Q&A, Help & Troubleshooting] sanketrino:
Same thing is happening to me. I've had my phone since launch date and I can't seem to get it to overclock more than 1.3ghz (which is very unstable). It's so frustrating when people are posting pictures of 4000+ score on quadrant and I get a bootloop instead. I really hope they can tweak it so that people like us can run at these higher frequencies.
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
What the heck? I keep hitting edit but it keeps quoting =( please delete.
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Have you tried Netarchy's kernel? A link to his thread is in my sig and it works great for me. It will boot you to 1GHz then using SetCPU (which can be attained for free on XDA, legally, just search for it. The Dev posted it) you can up the clock speed. You should take note however that the Nexus S is damned fast stock. I typically run my phone at 1.2GHz unless I want to show off to my friends and then I bump it up hehe

EDIT: Thank you also for not posting a new thread about this :) Its nice to see people using the search function!
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Blah please delete.
[Nexus S Q&A, Help & Troubleshooting] sanketrino:
I'm using netarchy's kernel right now at 1.3ghz but as soon as i go to 1.4ghz it crashes which is slightly annoying. 1.3ghz is much more stable now though.
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Odd...for my own testing purposes I've been running at 1.4GHz (testing battery life vs other clock speeds) since yesterday and haven't had a single crash. What ROM are you using?
[Nexus S Q&A, Help & Troubleshooting] sanketrino:
I'm using modaco r10 and correction to my earlier post, 1.3ghz on netarchy's kernel isn't much better than trinity. Ran Nfs shift for 5 seconds and it rebooted.
[Nexus S Q&A, Help & Troubleshooting] kenvan19:
Hmm, I used his 1.1v kernel on MoDaCo but never the new kernel so I can't speak to its stability.