Search results

I run handcent on my stock Google bought gnex on tmobile. Running the latest version on 4.2.1 and it works for me. Sometimes the message won't send from the app so I have to switch to the stock mms app though.

Return/Exchange the device. My 2nd unit did this and it's not normal. Sent from my Nexus 7 using Tapatalk 2

That's an awesome build. I currently have my galaxy nexus mounted to my dash and Run torque and a bluetooth OBD2 Dongle. Nothing like having a digital boost gauge and A/F gauge! I personally think the N7 is too big to mount in my 2011 wrx, but to each their own. None the less your build is clean!

Yup positive. The 2nd and 3rd units, both jacks worked fine. The 1st unit was just faulty. Tried 3 different headphones all if the same results. Even had a co-worker that was flying with me try his and the same results. If you jiggled it enough and held it half way out it would cut in and out of...

That is their usual policy. However, they do make special exceptions. I randomly purchased a unit in store on 7/14. I did not realize until 7/18 that the headphone jack was faulty and would only play from 1 side of the ear bud. I was on a plane so I wasn't able to exchange my unit until 7/29...

I have the same issue of the sound only coming out of 1 side on the headphones. I've tested multiple headphones on different units and it's the nexus 7 which I will be exchanging this coming Sunday.

Just got my update. I've been doing the "trick" of clearing the service frame work since yesterday. Literally an hour last night. Everything must be done in batches because I tried it for 20 minutes at lunch, gave up and tried it 1 more time. Sure enough I got the update notification. My friend...

70 with swype and 65 with swift 3. Swift had more errors then swype.

Just read about it via tmonews on an off subject about HTC One S. So Glad I waited...now to play the waiting game to see when it arrives...:p Not bad considering I bought the nexus one when it came out and got the Galaxy Nexus for $450 after taxes and shipping!

Use this. I just rooted my stock 2.3.6 nexus using this method. Takes less then a minute once everything is downloaded. Just make sure to extract all the files into the same location as the adb.exe file. Usually its in android/platform-tools. Good luck and let us know if you have any questions...

This whole time I made the BIGGEST FACEPALM mistake possible. Thanks to your last post I figured it out and was rooted within a minute. Thank You so much bassmadrigal for putting up with my noob questions.

Had some luck. I am now able to get C:\android\platform-tools>adb devices List of devices attached HTXXXXXXXXXXXXXX device But when I run the script it still says the same thing. The actual runme file is also in the same folder C:\android\platform-tools When I run in command prompt or click...

When I type in adb devices I get the same message as before 'adb' is not recognizes as an internal or external command, operable program or batch file. I found this video and followed the same steps but was unable to find the device via the command prompt, but it shows under my device...

Every time I plug in my phone it shows it as a removable G drive. Guessing my computer recognizes my phone as just a memory drive and not a phone? ---------- Post added at 01:48 AM ---------- Previous post was at 01:46 AM ---------- Just tried this with the same results. Appreciate the...

Totally new to rooting any device but I've followed the instructions to a T. Phone is a 100% stock Tmobile USA nexus one running 2.3.6 build GRK39F. I've downloaded Android SDK and updated the phone driver. Under: Control Panel = > Device Manager=> Android Phone => It shows Android...

+1. Especially when showing friends pictures and you look like an idiot when it doesn't zoom in when you pinch!

I'm in the same boat as well. I am consistently hovering around 21-22 mb free. With all the recent updates, it eats up all my memory. Freaking flash is still 12 mb, google maps is 9.7 mb, music 7.7 etc. Half the google apps I don't even use such as books 4.3 mb and goggles 3.8 mb. I have to...

How much data do you use a month?

Thats a good question if they did anything to it. As I said, it was more of a preemptive send in. The power button was probably ok and unresponsive once every 10 pushes or so. They took off my CM screen protector so I don't know if they decided to change out the screen or not. I did notice...

My warranty ended on March 2nd so I decided to send my N1 for a preemptive warranty work on the known power button issue. My phone wasn't really showing any symptoms of the issue but every 10 or so pushes on the power button would result in not turning on the screen. It was sent out on March...

Yeah my track ball doesn't light up anymore either. Guessing there will be an update for this soon.

It sure has. I remember this time last year I still was on my G1 drooling at the thought of a 1 ghz processor. Amazing how the N1 set the bar and was an industry changer in 2010. I can only imagine what 2011 brings us. :confused:

There are 2 versions of the Nexus 1 that are out. One that works with tmobile 3g and one that works with at&t 3g. If you use the tmobile version with at&t you will only be able to get EDGE. How long have you had your N1? Did you buy it new or used? Who is your provider?

Just wanted to give everyone a heads up there is a new swype update out. Version:2.15.56.14870.t100

You can set the max size limit on Handcent. Settings > Send message settings > Maximum MMS size I have noticed that people on AT&T can only receive mms at 500k or less (I'm sending pics from Tmobile).

Me and a buddy just got the update around 8pm PST (Seattle area) around the same time. Both of us are completely stock.

After a few hours of using it, I switched back to my tough case. I just can't get over how "under protected" the phone feels. I did however use the Seido case when I had to wear a suit earlier this week. I like having my phone on my belt in those cases. For 10$ its a nice option to have. Now if...

Thanks for the heads up on the case. I went to my local best buy and they did not have it on display. I had to ask one of the cellphone associates to get it for me out of the back. Their SKU is: 9943421 for $9.99 regular price $34.99. I've been using the Case-Mate tough case exclusively since I...

Just got the OTA around 1 PM PST in Seattle. It is installing as I type. Took about 6 minutes on the animated splash screen before it fully booted up. Went from completely stock Tmobile FRF91 to FRG83

Just cleared mine running frf 91 and I cleared up around 1200+ files and around 117+ mb. I noticed that there is a slight change in time. What usually took around 15+ seconds for the picture to be viewed after being taken has now cut down to 4 seconds. IE: Take pic, click on the icon in the...

I've never had this issue on 2.2 until I updated to frf91. Glad to see I'm not the only one.

I too chose LP over ADW. To me, LP is more intuitive. I gave ADW a few good hours to play around but just couldn't get use to it. I have my bottom 5 dock incons all customized in LP and use all 3 docks. That was the main drawback for ADW. I also noticed that it was a bit sluggish compared to LP...

The video has already been posted several times. It is a great video none the less!

Well if you open it you will void the warranty...I'm sure it was cheaper for you to buy your own parts then to do a claim on it, but with doing your own repairs you void your warranty.

X1512424246346 ....I want that game too...:p

So this means it is safe to do even though you are not reinstalling an update?

I just got this update to work for me as well. I got sick of waiting for the OTA. Previously I had installed the stock FRF50 T-Mobile update manually from the "leaked version". I saw all the issues people were having with the 7X and the 83 issues so I decided to play it out and wait. Since so...

I'm using this one for my n1 that also has a case-mate tough case on it. http://www.seattlesportsco.com/productcart/pc/viewPrd.asp?idproduct=1081&idcategory=10 The fit is tight, but it takes around 30 seconds or so to shimmy the sucker in. I use this setup when I go biking with my n1 in my bag.

I was a little past Tukwilla south of Seattle WA, and I got a speed of 4631 kbps download and 598 kbps upload! Holly smokes was I impressed! I only wish I could get those speeds 10 miles south of that location at home. :p

Well looks like it fixed itself after several restarts.thanks for the information.

Looks like I owe you a tenner. Wonder what app I can find to edit that setting?

I am running the stock 2.2 froyo on my tmobile N1. I just had my sim card replaced today and now on the stock messaging app, it no longer shows my picture. It now shows a grey square. Anyone have an idea on how to get my picture back? I tried looking at my google settings online with no...

I had similar issues and called tmobile support. I was first linked to Google support. They went through the similar process as described by in the first page. (#*#*4636*#*# select USA band etc). While I was on hold, they called t mobile tech support and had them reset network connection and...

I'm in seattle right now and tested at 1.7 down and 1.4 up. I'm in a building so I will try again when I'm outside. Way faster then at my house where I get .6 down and.3 up .:rolleyes:

Thats the same version that was released a few weeks back.

Glad it finally came to Seattle! Too bad I'm about 20 miles south of Seattle and it doesn't reach my area.:rolleyes:

Did you uninstall both the old installer and the program? Then download the new installer and apk? I recall that this process should be followed for the new version to work.

Thanks for the heads up. I did not receive the email yet but downloaded it anyways. It seems much faster so far. I guess we will see how well they did after a few days of testing.:o

We aren't. I've seen this same issue posted on multiple forums.

I have the text issue with my phone as well. There are two fixes that work for me. You can either restart your phone or you can turn it on/off airplane mode. I wish there was a permanent fix for this issue, hopefully the "official" 2.2 update will fix it.