yashsingh1/xdaforums huggingface dataset:
[myTouch 3G, Magic General] luismrosa:
i had my htc mytouch 3g very well but y decided to run it the ruu given in tha thread http://xdaforums.com/showthread.php?t=659403 (this one 46) [xda-ftp] [4shared] 2.10.531.4 T-Mobile USA DRD35) then i got my android unrooted and i can by passed the activator screen them i decide update whit this one (47) T-MOBILE OTA UPDATE from 2.10.531.4 DRD35 to FRG83D [4shared])

i run it from theandroid system recovery after that i didnt see the bootscreen just the logo of mytouch 3g and reboot it alone agiain and again not system well later i decide to rooted whit the nhb given here (http://wiki.cyanogenmod.com/wiki/HTC_Magic_(32B):_Rooting) not work tells me Main version is older

so the question is is my phone already a crab or it can be fix ? pls help whit that
[myTouch 3G, Magic General] 5[Strogino]:
At first, need SPL-info:

Turn phone off

Then turn on by pressing and holding Back + Power (it's a fastboot-mode)

Write first 5 rows (all symbols are important)

p.s. if your phone is bootlooping - to get into fastboot-mode you need turn off - remove battery, wait a few minutes and place back...
[myTouch 3G, Magic General] luismrosa:
ok thanks for the rapid respond this is my spl-info:

SAPPHIRE PVT 32B SHIP S-ON G

HBOOT-1.33.0013 (SAPP30000)

CPLD-10

RADIO-2.22.28.25

OCT 21 2009,22:33:27
[myTouch 3G, Magic General] 5[Strogino]:
After some investigations in PM solution is:

Flash 3.12.531.1 because it is stock ROM for T-mobile mytouch 3g

Owner in this problem flashed wrong rom (2.10.531.4 - it is for T-mobile mytouch 3g v1.2; this phone has different hardware and official roms than old mt3g)
[HD2 Android Q&A, Help & Troubleshooting and Genera] tainle:
I cannot the zip rom file show up in the directory. what is the reason for recovery not seeing it?
[HD2 Android Q&A, Help & Troubleshooting and Genera] hacimurat71:
If you follow the steps correctly in Recovery, then you should see the whole directory listed of you SD card. If you don't see this, probably your SD card is defect. Try with another card.

Good luck.
[HD2 Android Q&A, Help & Troubleshooting and Genera] freakin.ro:
what have u tried anyway?
[HD2 Android Q&A, Help & Troubleshooting and Genera] tainle:
I did nvflash for second time but some problem. this 16gb sd that i am using was an old sd from my hd2, i did a partition and extension in the recovery during the time i use the hd2. so i wonder if that affect it?

so far i didn't take any steps beside 1: redid the nvflash, i choose the internal sd and nand option.

i got to the step install rom from sd card, that was where i don't see the rom in the root directory. i only see certain folders in the recovery that are in my sd, still not al lthe folders that was in the root though. so i tried to put some rom zip file in those folder that visible in recovery but i still cannot see it.

so they are couple things i did but it not a solution. what should i do?

thanks
[HD2 Android Q&A, Help & Troubleshooting and Genera] tainle:
okay i realized i nvflash with internal option so i though i should put the rom into internal and it work. all these time the recovery was viewing internal sd the 5GB
[Motorola Droid Bionic] darkkterror:
I've had a DROID Bionic since just about when it came out (I got it on Sept. 15th) and recently I've had reason to suspect that my Bionic has reception issues. At work I mostly end up on 3G, getting 4G occasionally. I didn't think much of this at first, thinking that perhaps the 4G signal in the area wasn't that strong. I now think otherwise.

Since I got my Bionic, three other employees at my work all got Verizon 4G phones. Two of them have the Thunderbolt and one has the DROID Charge. From asking them and looking at their phones, they seem to have a 4G connection the majority of the time while my Bionic is stuck on 3G. They get consistent, steady 4G while my phone switches back and forth between 3G and 4G, mostly ending up on 3G.

This discovery prompted me to check Verizon's coverage map. According to it, my work is very, VERY clearly in a Verizon 4G LTE coverage area (not the LTE extended coverage, but full LTE coverage). That seems confirmed by the fact that the Thunderbolts and the Charge here are almost always on 4G. This has be worried that my poor little Bionic is having some issues.

Anyway, to cut the exposition here and get to the point, I was wondering if anyone else has noticed poor 4G reception on the Bionic. I'm curious to see if perhaps I just have a bad phone or if the Bionic, in general, is poor in the reception department. I have tried toggling airplane modes and rebooting the phone. That helps me get back on 4G momentarily, but I end up back on 3G shortly thereafter.
[Motorola Droid Bionic] bigeddthemonk:
In the same boat

I work in Pittsburgh and mine wont hold a steady signal either, unless I set in on this metal canberra by the radio in my room. Kinda weird really.
[Samsung Galaxy Nexus] touchaponk:
As I've noticed that most (if not all) Android phones I've ever tried have been suffering from the "non-fluid" issue. The homescreen and apps experience might be fast but they're not fluid like ones found on iOS or Windows Phone and I'm guessing that it's because previous Android phones doesn't have the 2D gpu acceleration. ICS has added the feature and I'd like to ask those owner out there if the experience is now as fluid as iOS or WP7? watching video review doesnt help because videos are formatted into 30fps. Even GS2 doesn't appear to be fluid (aka I dont think it's running at 60fps)
[Samsung Galaxy Nexus] Chrono_Tata:
The home screen and app launcher are very fluid if you have a static wallpaper. With a live wallpaper there is considerable slow down. Some wallpapers are less CPU intensive than others though.
[Samsung Galaxy Nexus] dnlsmy:
Android's fluidity is actually due to more than just Hardware acceleration. Most Gingerbread phones come out of the box very quick (Nexus S) and really glide without any apps installed. Hardware [was] acceleration is a big problem, as you were throwing efficiency out the window in order to run on everything. Now with it HW Acceleration, the slickness of the OS has multiplied exponentially giving you an experience on par with iOS (Joshua Topolsky, The Verge)

Now, here comes the real problem, apps. Android apps have the most freedom in the developer sense, and are also the most lax on what is allowed in the market. While iOS dev kit requires a stringent agreement and agreement to an app review process before getting your license, Google's Android Market is nothing like that. If you can pony up $25 (a requirement only recently), you can publish whatever the hell you have made, no matter how ugly, useless, or inefficient it is. Google's toolbox for Devs is great, even greater in terms of options in app making, but enforces no standards or required templates. This is why iOS apps all have the same look and feel while Android's app range from great to complete ****. This makes a lot of sense though as Android started late in the game, so they needed to bring up the app numbers, no matter how many were ugly soundboards or battery hog games.

With ICS, Google is taking a step in the right direction by offering the HOLO hook for developers, which will allow apps to be "prettied up" for ICS instantly. Also, more efficient protocols have been added to keep battery life and smoothness up, such as a revised Garbage Collector (actually, I think they removed it entirely) and allowed apps to share information with each other. The Garbage Collection is what make your phone lag, as it is recycling the unused code on the apps you're running in the background. The new location hook allows apps to now constantly turn on your GPS to pull your location, as they can simply request it from other apps if they don't need the most up-to-date info or if you just recently used your location on another app. The OS should be as fast as any other on the stock level, and as soon as the Apps become ICS friendly and more efficient, Android will truly have people falling in love with it:p
[Samsung Galaxy Nexus] rikbrown:
This is particularly annoying. My last Android (Nexus One) was pretty smooth on almost all live wallpapers - certainly on the stock ones. The Galaxy Nexus lags like hell (slow juttery screen swiping) on all of them except one of them. Very, very disappointing and hope it gets fixed somehow.
[Samsung Galaxy Nexus] touchaponk:
Live Wallpaper

Thank you everyone, I'm now ordering one for myself and hopefully there won't be a let down on the UI experience!

Strange, I owned Nexus One too and live wallpaper (stock one) isn't running at acceptable frame rate at all....it's laggy and sluggish (i changed from iPhone 3G and that might explain why)

May be you can try changing live wallpaper on Galaxy Nexus cuz the one u'r using might not be that optimized?

PS. One more question, how u guys find the battery life?
[Samsung Galaxy Nexus] blunden:
No, they most certainly did not remove the garbage collector but they implemented a more modern algoritm for it and it now makes sure to run on a different CPU core as to not take CPU cycles from the app. A garbage collector is part of the Java platform and could never just be removed since that would result in constant memory leaks that would result in a crash as soon as you filled up all the memory.
[Samsung Galaxy Nexus] scott.deagan:
When will the stuttering laggy UI experience be addressed?

I'm tired of all the mis-information. There's a pattern: Google is about to release a new handset, they don't show the handset scrolling in any of their ads, or if they do, it's super-imposed. A handful of 'mainstream' bloggers praise the handset calling it quick and responsive and lag free. You buy into it, buy the handset, and the basic UI is anything but CONSISTENTLY fluid and responsive.

I stupidly bought the Galaxy Nexus, really wish I hadn't. Here's just one example of the issue: I have an SMS thread with a mere 27 SMS messages between a friend and myself. When I scroll the up or down the thread, it's embarrassingly choppy (stuttery - don't know what word to use for it). It's extremely unpleasant, and completely ruins the end-user experience.

What annoys me is that Romain Guy closed Android Issue 6914, claiming that it was implemented in ICS. Now ICS is here, and the Android phone is still plagued with the stutters and non-fluidness Android is renowned for. Thankfully someone else has opened a new issue (Android Issue 20278), and hopefully this time Google will FULLY address the issue.

Understandably, it annoys some people more than others. Any user who has experienced a mobile UI that is buttery smooth and fluid (free from 'jitters' and 'stutters'), and where a page or menu sticks to your finger like a magnet when you scroll, would not be able to put up with what Samsung and Google have produced. It's what the kids today would call an 'epic fail'.

---------- Post added at 10:17 PM ---------- Previous post was at 10:11 PM ----------

I'm tired of all the mis-information. There's a pattern: Google around about to release a new handset, they don't show the handset scrolling in any of their ads, or if they do, it's super-imposed. A handful of 'mainstream' bloggers praise the handset calling it quick and responsive and lag free. You buy into it, buy the handset, and the basic UI is anything but CONSISTENTLY fluid and responsive.

I stupidly bought the Galaxy Nexus, really wish I hadn't. Here's just one example of the issue: I have an SMS thread with a mere 27 SMS messages between a friend and myself. When I scroll the up or down the thread, it's embarrassingly choppy (stuttery - don't know what word to use for it). It's extremely unpleasant, and completely ruins the end-user experience.

Understandably, it annoys some people more than others. Any user who has experienced a mobile UI that is buttery smooth and fluid (free from 'jitters' and 'stutters'), and where a page or menu sticks to your finger like a magnet when you scroll, would not be able to put up with what Samsung and Google have produced. It's what the kids today would call an 'epic fail'.
[Samsung Galaxy Nexus] [hfm]:
I find this to be untrue, the experience for me has been really good so far. Not perfect but its close. They have come a long way, it'll only get better.

And if you think any of the ads including apple are using true device operation in their advertising you are fooling yourself.
[Samsung Galaxy Nexus] serialtoon:
Can one of you guys post some video footage of said lag? I just ordered a Galaxy Nexus and can still cancel it. Thanks!
[Samsung Galaxy Nexus] player911:
Yea there is an iPhone YouTube video performing the exact same steps they show in the commercials and it takes a LOT longer in real life.

Oh well.

G2x - 2.3.7 CM7

Transformer - 3.2 Revolver OC/UV
[Samsung Galaxy Nexus] Nexcellent:
Not something worth canceling your order for, it's barely noticeable.
[Samsung Galaxy Nexus] serialtoon:
Its the main reason i left Android. Hoping that one day they will use GPU rendering to assist with UI fluidity. If that is present, its enough for me to cancel an order. Ive been a long time Android enthusiast, but the UI sloppiness is what has kept me from keeping an Android phone for too long.
[Samsung Galaxy Nexus] Spybreak:
As a fellow UI lag hater I can tell you it's still there in some places. The problem is, although the base of ICS supports and uses GPU acceleration, 3rd party apps dont yet, and even if you "force" it in the developer settings, it isn't compatible with some apps, and will sometimes cause crashes.

That said, it is ages ahead of Gingerbread, but still not as smooth and fluid as iOS and WP7; not even the GPU accelerated parts.
[Samsung Galaxy Nexus] Andrmgic:
ICS is a big improvement over gingerbread in terms of fluidity.. but it's not on the same level as iOS and WP 7 yet.

UI lag is one of the things I always hated about Android.. and I feel better about ICS than previous versions.. but they still need to improve it if they want to be on the same level as Apple and Microsoft.
[Samsung Galaxy Nexus] alias3800:
FWIW, I bought the phone having read in several reviews that the phone still suffered (albeit much less) from the usual android-lag. It now compares favorably to iOS and the windows mobile platform, just doesn't match or pass them in fluidity and smoothness.

In my experience, many aspects of the UI are "buttery-smooth" and whatever else reviewers usually say. However, there are still a good amount of moments where lag and hangups are present. The difference is, I'm ok with that. I've accepted the phone for it's plusses, despite it's minuses.

To be clear though, it does lag and hang from time to time. Rebooting once a day helps and I believe forcing GPU rendering under developer settings generally helps.

Sent from my GNex
[Samsung Galaxy Nexus] gogol:
Dont forget that Andoid does much more in the background and foreground compare to iOS or WP7.

Think multitasking, customization, widgets, etc.

It is understandable Android cannot be as smooth as those iOS and WP7.

And for me, it is more than good enough. I wont ditch Android because it might lag a little bit, because the advantages are much more valuable.

---------- Post added at 11:58 AM ---------- Previous post was at 11:48 AM ----------

Here, this just in ... a thorough explanation from Google Developer about Android graphics:

https://plus.google.com/u/0/105051985738280261832/posts/2FXDCz8x93s

I copied the text here:
[Samsung Galaxy Nexus] Evostance:
you saying iOS has no stutter lag..

My iPad stutters all the time. Its no where close to smooth!
[Samsung Galaxy Nexus] Shodney:
There was some suggestion in this thread that any acceleration is currently software based only, and that the hardware acceleration has yet to be enabled.

I don't know how accurate that is, and there doesn't seem to be a definite answer in that thread.

Perhaps in the 4.1 update? :D
[Samsung Galaxy Nexus] jadaress1:
+1
[Eee Pad Transformer Themes and Apps] TomTcom:
Is it possible on the Email app to do an alias for the Exchange account setup? My usernae and email address are obviously different but the app keeps telling me my username and password are bad. Am I missing any type of option?
[Eee Pad Transformer Themes and Apps] TomTcom:
As an example, K9 mail recognized alias and it worked but the program was very slow and unreliable for anything on Exchange in my opinion.
[HTC Rezound] Marcismo55:
I'm plain so the black and smoked covers look really nice. Thanks for the review!
[HTC Rezound] jayochs:
agreed, i like those the best...but i'm starting to really like the clear argyle...it makes the phone just stand out and look awesome, and those green/blue andy ones are SO cool haha
[HTC Rezound] dmeadows013:
Damn. Beat me to it. I'll be posting my review of the red case later.

Sent from my blazing fast HTC Rezound with 4G LTE
[HTC Rezound] joelmic:
Great review
[HTC Rezound] zetsumeikuro:
Do you know if the phone w/ the case on will still fit into the media dock? Thanks!
[HTC Rezound] jayochs:
Hmm I doubt it will...I remember the Inc didn't
[HTC Rezound] krstnsn:
Do we know the demensions? The car dock will fit cases 1-2mm.

In pictures these don't look any bigger than the vzw ones that supposedly fit.
[HTC Rezound] FSRBIKER:
I have the clear Androidify version i bought from Amazon, the fit is perfect and it is very thin so using the dock certainly is possible. This tpu case is probably half the thickness of others I have used, cant wait to pick them up for the Galaxy Nexus when its released.
[HTC Rezound] Evo4gLI:
I also bought the clear Androidify one, and it will be here on Tuesday, so I'll post something up about it then.
[HTC Rezound] jayochs:
yeah the clear andy one looks awesome, i wish i had one of them to try! i'm using the clear argyle one right now
[HTC Rezound] sheba611:
I bought 3 Andy cases

I have the aqua, red and smoke cases. The aqua case is on the phone now and looks great. Really stands out if you like cases that do. The only thing I would change is to have the volume buttons cut out. The buttons are too hard to press thru the case.
[HTC Rezound] jayochs:
yeah, i felt the same way..i may try to cut them out on one of mine to see if it's actually better than the buttons being in there
[HTC Rezound] jayochs:
oh, FYI:

the easiest way to do this (there's a little trick) is to push the volume button towards the BOTTOM of the vol down one, and right towards the TOP of the vol up. if you try to push towards the middle or insides of hte button, it's impossible..but doing it with your thumb, a bit of your nail, towards those positions makes it so much easier!
[HTC Rezound] FSRBIKER:
Hard Volume Key Solution:

Its a simple fix, take a sharp blade and make a 1/3" slice on either side of the upper volume button tpu material and then do the same for the lower volume button. Be careful you do not cut completely through and make one long slit.

My volume buttons are simple to use now, I use Widget Locker with Easy Wake mode and now can wake the phone using the volume keys. I also use Screen Off and Lock app and set long press of the search key to put the phone to sleep. This will help to save HTC's issue with volume buttons failing, it is a different design then the Tbolt but better safe then sorry.

These are great thin cases and I am ordering them for my Galaxy Nexus phones as well.
[HTC Rezound] jayochs:
sorry, but that confused the hell out of me...can you explain more into depth, or show pics or something? lol
[HTC Rezound] feralicious:
I'm very curious to know if the red is a deep blood red or more of a tomato red. If I go red I want a deep blood red.
[HTC Rezound] FSRBIKER:
If you take the case off and look at the volume key area you can see a line completely around the keys, this is the line you will follow to cut. Now starting at the top on either side of the upper volume key area make a slice with a very sharp blade(xacto knife is perfect) 1/3" down, now starting at the bottom on either side of the lower key area make a slice 1/3" up. This allows the tpu material to flex quite a bit more and use of the volume keys is greatly improved. Take your time so you dont make the cuts too long as you would rather them not connect.

Hope that helps clarify it for you.
[HTC Rezound] Evo4gLI:
I just got this case today, and it fits really well. I like it a lot, but I'm going to have to try out that fix for the volume button, because it is really hard to press. Other than that, the case is really great.
[HTC Rezound] jayochs:
i'm gonna try the volume fix myself, i'll report back!
[HTC Rezound] dpiddy14:
I really like your review of the cruzerLite cases. I wish the volume button was cut out all the way though. I guess you could cut it out but its not the same as if its made that way. I actually purchased the black HTC TPU case from htcpedia.com. It has the volume button cut out which makes it way easy to actually find and press the buttons and is very similar to the CruzerLite. The HTC case though seems to wrap the screen just a little too far. I hit the case with my finger on the top and bottom all the time( playing angry birds and what not). It seems the cruzerlite actually doesn't wrap as far according to your pictures. If both these cases would combine it would be the perfect case.

http://shop.htcpedia.com/htc-rezound-tpu-cases.html
[HTC Rezound] jayochs:
when i spoke with the owner, he wanted my input about the power and vol buttons..he said he started cutting out teh power buttons because people said they were too hard to press. i'll show him the thread and tell him that maybe he should check out cutting out teh volume buttons as well! :)
[HTC Rezound] jayochs:
I actually just did the cut method to mine and I notice no difference...oh well haha naybe i did it wrong Idk
[HTC Rezound] jayochs:
actually, it is a bit easier to push, but you still generally have to use the tip of your thumb, like your thumbnail. now that it's cut, i can actually FEEL the button being pushed in, whereas before i couldn't. maybe i'll cut some more to get more flexibility
[HTC Rezound] joelmic:
Thanks, I may start making cases with the volume button cutout.
[HTC Rezound] tbgreen89:
Just received mine today. I ordered the clear android one. Very nice case. Although the volume buttons are almost impossible to press. Good quality though. Will definitely buy again.
[HTC Rezound] jayochs:
Tb, read about the xacto knife cutting thing. Mine has gotten a little easier to push but id really like to see what Joel can do about cutting out the volume button.
[HTC Rezound] awmobjects:
I'm waiting for the red, clear and smoke Andys to arrive...buy2get3 from Amazon
[HTC Rezound] tbgreen89:
I think I will cut it out completely. Other than that I'm really liking this case. I wanna order the red and green one. I should have bought the 3 pack deal.
[HTC Rezound] jayochs:
Lemmie know how cutting it out all the way helps. I'm thinking of it but Idk if I wanna ruin them yet lol
[HTC Rezound] Evo4gLI:
I cut the volume buttons out completely, and it's much easier to press the buttons, although still not perfect....It does take a while though, as you have to cut them out, then shave the hole down (I used an Exacto knife) until you can press the buttons easily. I went slow so I didn't ruin the case, but apparently not slow enough, considering I sliced my thumb open with the knife. The case came out unharmed though.
[HTC Rezound] jayochs:
DAMN. how'd you do it? throw it in a vice or something to hold it, or in your hand?

i'm thinking after you cut out the volume buttons, you hvae to cut AROUND that area to make it big enough to fit your thumb in their, much like how if you notice the power button isn't cutout for the just the button, it's cut out AROUND it so you can fit in there.
[HTC Rezound] Evo4gLI:
Nope, held it in my hand, and put it on my desk too, hence how I sliced myself lol. What I did was cut out the buttons, then put the phone back in the case to check. Then I shaved the hole a little bigger, and checked again. Put the phone back in, you get the idea. Eventually I got it so I can use it the way I want. Takes about half hour if you want to do it right. Better to take your time than ruin the case.