yashsingh1/xdaforums huggingface dataset:
[Android Software Development] Wozgetsrdone:
I have the file but what & how should I begin Have unbuntu & all that updated still need help where do i go from here
[Android Software Development] Runawaycoder:
You could start by taking a look at the wiki on cyanogenmod.com, assuming that you weren't referring to the droid x or droid 2
[G2 and Desire Z General] ALAMO695:
hey guys could someone please mirror the visionary app r11 because it seems like paul's page is down
[G2 and Desire Z General] D_Rob:
R11 or the new on R12? I have R10 up on the forums here.
[G2 and Desire Z General] T.P.:
http://android.modaco.com/content/h...722/10-nov-r12-test-visionary-one-click-root/
[Nexus One General] boogieboogie:
Hey guys,

I wanted the nexus one ever since it first got announced. unforunately for the first month and a half it was exclusive with tmo bands. Come around March, i heard the ATT version was released and i told myself i was gonna get it. I put up my iphone 3gs and to my surprise, nobody bit. they were all trying to trade their iphones for the nexus one att version, just like i was.

fast forward to last week, i bought a htc desire (telus, so it works with att) from a friend. It was a awesome phone, but the nexus one bug was still inside me. Everytime i would see comparison videos against the desire, i would tell myself how pretty and attractive the nexus one is. I couldnt take it anymore, so i went on ebay, searched all day today, and than right when i thought all hope was lost, one ad popped up. "never used, refurbished by HTC Nexus One ATT". I did the BIN which was 425 with 15 dollar shipping. Now selling the desire for 550ish. My question is, with tech advancing so fast these days, did i make a good investment in buying a mint att nexus one for a whopping 425? or should i have waited for the dual core phones from samsung.

be brutally honest guys. and btw, the nexus one is going to share primary phone duties with my iphone 4.
[Nexus One General] worker1:
I think it's worth it. The N1 is amazing.
[Nexus One General] ksc6000:
I agree. The N1 is still the best all rounder phone (notification lights, great GPS receiver, perfect size). Unless you play very graphic intensive games on your phone...you'll be just fine without a dual-core processor. I just feel sorry for your poor iPhone 4..you're gonna be so mad at the little things it can't do like long kinetic scrolling in the browser, lack of configurable color LED notifications, flash in the browser, ability to change to different notification sounds....
[Nexus One General] DarkDvr:
In my opinion, currently, there is not a single phone that, in overall quality, surpasses the nexus one.

It's just "pure" - no UI additions, no craziness. Just solid, beautiful phone. Oh, and it just feels so good to the touch.

There are phones that has advantages over it here and there.. but overall, N1 is still the king of the hill for me.
[Nexus One General] hexix:
It sounds like you made a little money selling the desire and getting the N1 so I guess it wasn't dumb. I personally think the desire is a bit cooler looking than the nexus so I would have kept that. They're basically exactly the same, right?

I really like my nexus one. Recently the battery life has even become better on the stock rom. However if someone was about to buy it now I would tell them not to bother. The touch screen sucks — it can only detect two points and gets confused doing that, it also gets messed up when the phone warms up in my car dock. The screen is also nearly impossible to see in bright daylight.

Not sure what android phone I'd prefer though. Wish there was a galaxy s with an HTC body.
[Nexus One General] chromiumcloud:
Remember that all the leaked Sammy devices are for T-MOBILE.

AT&T is in the process of switching bed partners from Apple to Microsoft. I count us AT&T users lucky that we got an AT&T banded N1 to begin with. Regardless of what the person with incredibly large hands may say about the Dell phones, the N1 is the best Android phone on AT&T and will be for some time until the next Dev phone makes its way (fingers crossed) to AT&T bands.

Until then, enjoy the BEST custom roms ever made right here at XDA. This phone gets better ever month, and next month when the customized gingerbread roms appear, it will be better again.
[Nexus One General] ronniecarlough:
I totally agree my friend :)
[Nexus One General] peliROJO:
Not worth it, IMHO. Once you get it, post back and let us know how you like it, and if YOU feel you got your money's worth.
[Nexus One General] Lamar720:
I think its not worth it. Don't get me wrong it's the best phone I have ever had. All the Sidekicks (1,2,3 and lx etc.), from there to g1 (great classic) and a N900 with a few other phones.

I traded my N900 and got an nexus plus $200 bucks. best deal ever !!!!!!!

I would not sale my nexus it's is the best phone out to me. Perfect build, and feel. Googles baby you just can't beat that.

AND THE BEST COMMUNITY FOR ANY PHONE KNOWN TO MAN.

A CLASSIC THAT NEVER DIES ..... CHUCK NORRIS LOL. j/k

But, if your not happy with your choice there always someone with that same burning feeling you had to get one that will pay 500+.
[myTouch 3G, Magic General] vtmn215:
I tried to use SuperOneClick to root my phone and it seemed to work. The program came back saying I successfully rooted my phone.

I then went to ClockworkMod to install cyanogen and clicked on the appropriate boxes to begin the download process for cyanogen 6.0 stable mod and ran it.

My phone rebooted and started to run some scripts.

Now, the phone just reboots to the green mytouch screen and continues to loop like that and I have no idea what to do.

I can get into fastboot on the mt3g and when I do, my pc makes the sound that states that the phone is connected but when I try to get into the mytouch, using adb, my pc cant access it but when I plug up my G2, I can see the serial number and such showing that it is connected.

I tried to follow the fastboot driver installation page but it didn't seem to work.

Bottom line is I would really enjoy a functional MT3G in either the regular form or cyanogen (which is why im in this predicament now :))

For the the record,

I was running 1.6 but got the OTA update for 2.2 before I ended up blowing up my phone.

Thanks for reading this and any aid would be greatly appreciated.

UPDATED:

I found something called SAPPIMG.NBH that allowed me load Android 1.5 onto my phone. I now am back to a functioning device but still, I am super stuck on trying to get cyanogen onto my device. Any helpful hints? From what you read above, did I miss something?

Thanks again. :)
[myTouch 3G, Magic General] vtmn215:
... Sadness... I have been bashing my face against this mt3g and haven't been able to get cyanogenmod on this phone for the life of me. I have tried all of the builds from 5.08 up to RC1 of 6.10 and I just get the infinite loop at the cyanogen boot up screen. I even tried to flash 2.23.XXXX radio to see if it gets past the boot loop and it does not. Anybody have any insights into my issue?

Thanks,
[myTouch 3G, Magic General] housry23:
You must go into recovery mode(boot up by holding down home + power). That will get you to Clockworkmod recovery(I am assuming since you said you downloaded using Clockwork app). From there you need to wipe cache, and anything else you can wipe. Then try installing Cyanogenmod after that. Without wiping the there is not enough space to install and it causes a bootloop.
[myTouch 3G, Magic General] jaypr9:
I'm in the same boat, I'm stuck in a boot loop and I cannot get any ROM to fully load in. I'm using clockwork recovery Radio 2.22 32B.

I tried wiping everything but that still doesnt seem to work. I noticed when I try wiping Davlik cache I dont see any message on the bottom. I thought it would normally give me some sort of message stating that it is wiping davlik or something so maybe it isnt actually wiping it?

Is there some other way to make sure davlik is wiped? Or something else I can do. I just want the phone to boot up at this point. I can get into recovery but thats it.

I know I shouldve done a backup but dumb me was such in a rush I completely forgot, I know im a idiot...
[myTouch 3G, Magic General] jaypr9:
Het I found that same .img file and also reverted back to 1.5 then just went up to 2.2 not sure what was wrong but Rom I put on just went into a boot loop. Maybe it was clockwork recovery.
[myTouch 3G, Magic General] vtmn215:
the padawan becomes the master... Sort of...

The problem is that you cannot go directly to 2.2 from 1.5. You have to do the incremental upgrades that take you from 1.5 to 1.6 then 1.6 to 2.2
[G2 and Desire Z General] ok11:
I have the Bell Desire Z that I unlocked to use on Fido and many people are complaining to me that whenever they call me, it goes straight to voicemail. It doesn't happen everytime, but its happening like 25% of the time. Anyone else experiencing something similar? Is this a network issue or is it the phone? What can i do to fix it?

Update: A friend of mine also has this phone and is on Bell. He too is experiencing the same issue. Guess it's something with the phone, right?
[G2 and Desire Z General] B73C:
We (wifey and I) are having the other issue where where we can't even dial out.

It's hit and miss, but sometimes it takes half a dozen tries to get a number to ring.

We just had our SIMs replaced today, and had our profiles reset but the problem continues.

I guess a hardware replacement is the next step, as the wife is fed up at having to dial a number over and over to get through. "What if it's an emergency?"

My phone is unlocked as well and I've used 3 different SIMs in 3 different countries but it only happens here in Canada.

We'll go back to our place of purchase next week and see if a hardware replacement fixes the problem, then will report back here.
[G2 and Desire Z General] Susido:
I'm using an unlocked Bell Desire Z on Telus and I have had one call that went to voicemail without the phone ever showing that it received the call. And it did not inform me of the voicemail either. Hasn't happened recently but I'm still a little leary.

B73C, you're fortunate if you get to hardware exchange your unlocked phone at your place of purchase in Canada. I've always been told in no uncertain terms that once a phone is unlocked, you're on your own. But I think that HTC still has to warranty it.
[G2 and Desire Z General] JPHCCFC:
What is your network signal strength my unlocked desire z has poor reception on fido! I'm hoping a new radio rom will fix it. My signal strength is around 100 SBM and below 10 asu
[G2 and Desire Z General] zedix79:
I'm also on Fido with an unlocked Desire Z from Bell, but never experienced any of these issues... sorry to hear that!
[G2 and Desire Z General] ok11:
My signal strength is -93dBm 10asu with the numbers changing constantly up and down a few digits.

I hope there's a fix for this.
[G2 and Desire Z General] JPHCCFC:
Im hoping there will be a new radio rom out soon that woll fix the poor network strength issue.
[Epic 4G General] kd7zdj:
o basically a while ago i rooted my phone and for about three weeks it has been working just dandy. Though rom manager wasnt allowing me to boot into recovery like it should. Me being the explorative person i am read all the forums i could and one said to just reinstall the CWMod file again via Odin... And THIS is where the problems begin. It appeared to work fine but when Odin rebooted my phone it keeps alternating between the standard SAMSUNG(samsungmobile.c o m) and a very "old" looking basic samsung.... over and over and over. O and did i say...AND OVER? again. It will boot into download mode but not into recovery mode.

My question to you android savants is: "what the heck did i do?" AND "how the heck do i fix it???"

Thanks
[Epic 4G General] mesaexplorerbc1:
If you can get into download mode (holding 1 while turning on the phone), I would use odin to flash the phone back to stock. Since this username is new, I can't post links, but at the end of xda-developers (dot) com add this /showthread.php?t=794138 and that will take you to the instructions you can use to flash back to stock.
[EVO 4G Q&A, Help & Troubleshooting] dpearman:
Hey all,

I've got an ego, have had it since July and love it. I finally have come to terms that I really should root it and get a cleaner, faster running ROM on it. My question is, what is the easiest, simplest way to get the level of root necessary to install custom roms? I've searched several sites and they all seem to be fragmented, does someone know of some step by step guide, or does anyone have any history or experience with simple root? I've heard of unrevoked, but some mixed reviews. I guess I just haven't had the guts to jump in and do it, till now, I want a cleaner running phone! Any help is appreciated.

Thanks,

Devin
[EVO 4G Q&A, Help & Troubleshooting] HiddenKnight:
What firmware version are you running? Settings > about phone 3.xx.xxx.x

Should look similar to this

blasted this post with my limited edition evo!
[Droid Incredible General] sonar_chris:
Just like the title says, Rom Manager things my Dinc is a Fascinate. I am currently running Cyanogenmod 6.1 RC2 and Rom Manager is baked in, I've tried deleting the updates but when I go into download rom, I get only Fascinate roms. Any ideas on how to fix this one?
[Droid Incredible General] smtom:
Are you using an SD card from elesewhere?

Try uninstalling ROM Manager and reinstalling - you may get the device selection screen, at which point you choose Incredible rather than Fascinate.

Absent that, with the device on, unmount the SD and power down the device. Then take SD out, copy entire contents to PC so you'll have them, and format the SD card to FAT32. Put SD back in device, d/l ROM manager to get the device selection menu.

Then you can copy files back to SD card from your PC.

Please post whether this (or something other) works.
[Droid Incredible General] sonar_chris:
Thanks a lot.

I uninstalled ROM Manager and put a different (blank) micro SD card in the phone then reinstalled ROM Manager, this did the trick. The SD card I was using came out of a fascinate and that was causing the issue. Thanks again.
[Captivate General] Tzu2050:
Edit:

SOLVED

Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.

Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).

---------------Original Post-----------------------

As I type, my Samsung Captivate appears to be possessed with an obsession with clicking the search button all by itself, at random times. I've searched around the forums and have yet to find a solution that works for me.

I'm running Cognition 2.4

The phone is about 1 week old, with the problem starting at about 5 days.

I replaced the phone initially because it would shut down randomly. Now this one seems to have yet another malfunction :confused:

EDIT: Also note that the problem began shortly after cleaning my screen with a slight amount of monitor cleaning fluid and microfiber cloth. Whether this is coincedental or not, I don't know.

Does anyone know what might be causing this, or know how I would go about disabling the search button altogether?
[Captivate General] snorkle:
i had the same problem, its kinda just went away for me haha
[Captivate General] Tzu2050:
Hmm, I also hope it goes away as mysteriously has it appeared if a solution is not found.
[Captivate General] Tzu2050:
I'm trying to make changes to "system/usr/keylayout/melfas-touchkey.kl" with "droid explorer", but every time I change the file, delete it, or replace it, the file always seems to revert back. Once I figure out how to do this, the problem should be temporarily fixed.

EDIT: My current theory for what causes this is that it occurs due to an electrical short after the screen has been exposed to liquid of some kind. If you look closely, there are thin cracks around the glass of the screen. Whether these cracks are water-permeable or not, I don't know. But due to the nature of this problem coming about randomly, and disappearing randomly for various owners, it would explain the effect of drying. I read someone say that he had this problem on two different phones, so maybe he cleaned both of them in such a way that affected the navigation buttons?

If anyone else can contribute to this theory, please do!

EDIT 2: The frequency of search button activation has increased significantly since the first symptoms appeared. I highly doubt this is software related. There is a apparently an issue with the circuit for that specific button. Considering that my cleaning of the screen was the only possible event that could have impacted the circuit, I am now leaning towards that prospect. There doesn't seem to be an easy way to completely dismantle the Captivate and let it dry.

EDIT 3: I'll focus a fan on the phone over night, then focus a blow dryer on it in the morning.
[Captivate General] ricethief:
Had the same problem, it was like that since the first day I got it 07/18. It got worse for a period and now it mysteriously doesn't seem to have the problem anymore. No clue what it is from.
[Captivate General] Tzu2050:
SOLVED

Problem: Water or some liquid mixture with water and other conductive chemicals can leak through the outer edges of the glass screen, causing electrical shorts on any of the navigation buttons. Thus avoid applying direct pressure with damp cloth along the perimeter of the screen.

Solution: Place the phone in a ventilated area as long as needed. In a severe case, this could take a very long time (a blow drier may expedite the process), so you may want to seek instructions on how to dismantle some of the phone components to allow drying, or disable the search key temporarily, or send the phone in for repair(last resort).
[Captivate General] mr.jaguar:
you might also try putting it in a ziplock bag with rice in it. (the rice will absorb the water)
[Captivate General] nitin1009:
Has the proposed solution worked for anyone?

Hi,

I am wondering if the proposed solution worked for anyone? What do you exactly do? Leave the phone in the sun for it to dry out. With combination of blow dryer?

With the battery out? I've had this phone since August and I initally thought it was a software issue. After couple of hard resets, roots and upgrade to 2.2 the problem still persists.

Any suggestions? Should I try all combinations? Rice Ziplock bag?
[Captivate General] meadhros:
Just as a note. Used to have a lot of random search loads. Along with the moisture thing...a lot of us right handers contact the corner and it does need a direct tap of button to trigger as touch screen. If you notice the settings button never randomly pop up. Additionally, from wrar and use the plastic can gain some flexibility. Must my two cents to help avoid letting ATT screw up their phone.
[Captivate General] meadhros:
And in no case...let best but put a screen protector on for you....that will take days to dry...
[Captivate General] Twicebak3d:
I've had that issue in the past, on stock Eclair, and it was an easy fix for me. All I did was flash a custom ROM. I can't say that I tried it on stock 2.2, but an Odin didn't help, so I went custom and it disappeared.
[Captivate General] brianray14:
WOW! Thought i was alone.. I also have the phantom button activation problem... but it's not the search button, it's the home button and back button. I know for a fact my phone has not been exposed to moisture. I noticed it after i flashed an OC'd kernel. I tried every OC/UV setting in the voltage control APP thinking it had something to do with the increased MHZ, but the problem didn't go away. I have since flashed a variety of custom roms and regular non OC'd kernels, but the problem still is present. I saw someone post a little while back about the same issue and that they sent their phone in and at&t replaced something having to do with "LIB." The submitter didn't have any idea whether the "LIB" was related to software of hardware. I'm considering sending my phone in, but i hate the idea of being without my phone for 2-3 weeks. If anyone stumbles upon a fix, please do share.
[Captivate General] sf1120:
Try a gingerbread rom.I've had the same problem,back and home key.No matter which froyo rom I run,it would act up randomly at times.I dont spend enough time on eclair to be sure that it does it,but I've been running GR-9 for two days,has not happened once.Coincidence?Maybe....Now running GR-11 for the second day,so far so good.
[Captivate General] crystalhand:
I agree with the op that the cause is water/moisture in the phone. I have had it on all android versions I have used. And the fact that that it comes and goes is strong evidence in my opinion
[Captivate General] Spurt_n_squirt:
It might be moisture in some cases, but....

Post getting old, but new to me! My random search problem is definitely not moisture related(unless high humidity outside is considered a problem for a cappy). My phone stays dry, I even clean it with a lint-less cloth, so water isn't the issue(its in a otterbox). I read some post on other sites that show the only fix is either allowing samsung to work on it, or get a refurb from att. I think this problem is also related to all those wrong contact sent messages to, which has happened to me several times with some embarresing happenings ;). I updated to gb 2.3.5 and problem still exist, plus I use handcent for messaging, and I havn't sent a mis-message yet.
[Captivate General] Captain Zero:
There's another thread on this (search 'crazy back button' and my tests on many roms indicates that it has to with the blk app that mods the buttons. Many roms come packed with versions of it.

No longer sent from my BlackBerry.
[Captivate General] dreamliner77:
Add me to the list with this problem. At first I thought it was an old screen protector. I changed that out last light but I cleaned the screen first by spraying it with LCD cleaner :eek: I guess I'll have to wait for it to dry a bit more. I've also been playing with recent Glitch kernels with BLN issues so I can't figure it out!
[Captivate General] dreamliner77:
Well I got the BLN issues sorted. Still can't figure out the search button. There's got to be some way to disable it completely
[Captivate General] Espaa Valorum:
I get this problem at random times when using Google Maps / Navigate, while the phone is in the car dock. At random times, the search will just pop up. No idea why :(
[Captivate General] They Drew First Blood:
While using the phone in the rain one day, the touchscreen pretty much became inoperable once there were multiple droplets on the screen. Luckily I did not have any seepage under the glass, though.

I also concur with meadhros- I've found that when gripping the phone in my right hand, the edge of the pad of my palm at the base of my thumb sometimes sets off the search, since it wraps around the edge of the glass slightly.