yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] kong:
Some follow up on the issue: To be honest I didn't even notice the glitch until @syntax_gosong mentioned it. But ever since I knew it's there, it's been quite annoying. So I spent a few hours yesterday trying to fix it and here's the result :D

Before and after screenshots:
[Samsung Captivate Glide] jayjayjoker2:
It seems as if I get no signal on my phone I have to reboot to get service again what is causing this

-sent from my insanely awesome captivate glide-
[Samsung Captivate Glide] Lookin4Trouble:
Don't know if you may have seen any of my other posts in this section, I had a problem with 2G/3G connectivity when I first got my i927. After poking around a bit, it looked like the SIM card was just a hair loose in its little metal cage. I took a piece of clear tape and stuck it in place, haven't had any issues since. Let me know if you see the same thing?

HTH

L4T
[Samsung Captivate Glide] jayjayjoker2:
So far so good I will report if it does it again another problem is that when I turn off my phone and charge it when I turn it on it shows the samsung logo then goes away and I have to turn it on again

-sent from my insanely awesome captivate glide-
[Samsung Captivate Glide] Lookin4Trouble:
Any chance you're accidentally hitting the Vol+ button when you press power to turn it on? sounds exactly like ODIN mode to me...

HTH

L4T
[Samsung Captivate Glide] jayjayjoker2:
There is a pssibility I'm going to check up on that but the tape thing worked haven't had a problem since so

-sent from my insanely awesome captivate glide-
[Samsung Captivate Glide] mariol66:
I kept losing data recently running osimood, went to network settings and changed carrier option from gsm/hspa to hspa only, I haven't disconnected yet
[Samsung Captivate Glide] stone81:
hey all i just got 2 of these babies from the states. im from belfast UK and have found that the signal on both are really bad all the time 1 or 2 bars at the most every other phone i have had was fine for me and im in a good area for O2 which is my network provider. now i know u could flash kernals for htc's that would change that but could this be done with the samsung cap glide ?

any help would be great im only getting the hang of the glide, its been rooted custom kernal and rom all installed so in not so much of a noob and very quick to pick up thinks
[Samsung Captivate Glide] knv8:
i have the same problem, signal would cut out and only way to get it back is pull the battery. i had the att service center update me to ics and a new sim yesterday, see how it goes.
[Motorola Triumph] Android311:
Hello all, I've been with virgin mobile for about 2 years now and I've owned the LG otimus v and HTC wildfire s, I currently own HTC wildfire s and I'm not liking it, I'm thinking of buying the triumph. So my question is how do you like the triumph? What is the good and the bad? Should I buy the triumph or wait for new virgin mobile phones to come out? I ask here cause members here no phones more then regualr internet reviews so I want to ask the people that no this phone in and out

NookColor Cyanogenmod 7.1 "Overclocked"
[Motorola Triumph] ajore22:
Well, I have to say I have a love/hate thing going on with my MT.

I would say my biggest disappointment is battery life. I know Android doesn't get great life, but out of the box, this thing will last maybe 5 hours in your pocket. I use juice defender and can get about 15 hours in 1 charge with medium-light use.

Reception is a little spotty sometimes, I get about 80-95dbm everywhere I go. When I had my OV I would get 75-85dbm.

One thing I really do like about it though is I have never had any major issues with software. Hardly anything ever FC'd on me.

And the screen size and resolution is pretty nice, nothing to really jaw dropping, but way better than the OV.

Overall, I am happy I made the switch. Aside from my displeasure with Virgin Mobile, this is a pretty decent phone.

If you have any more questions, I'll be happy to try to answer them.
[Motorola Triumph] marc12868:
Well I have the MT, although I switched to T-mo, because where I am VM service isn't the greatest. So I have a MT4GS, so my opinions might be b bit biased because of that although I have had the triumph longer...

Good: Fairly fast processor, flash support, led flash on camera, gorilla glass screen, 4.1" screen, HDMI out support, lots of dev support, virtually unbricakble, can record in "720p".

Bad: ****ty touchscreen that barely recognizes 2 touches, VM speeds aren't that great (at least for me), blue tinted screen (at least on mine and other people have complained about it), regular lcd screen, capacitive buttons, no dedicated camera keys, speakers aren't that great, screen will sometimes be whitewashed or graphically screwed up (turn screen off and on and its fixed), Touchscreen ignores touches at times, rebranded, the 720p capture isn't that great mainly this and pictures are because of a POS camera sensor.

It may seem like there are lots of bads, but they really aren't that major if you don't play a whole lot of games, because this touchscreen is not made for that. Its ultimately up to you to choose. VM may or may not come out with a phone anytime soon that has equal or better specs than the MT, so if you want to wait you can, but the MT isn't all that bad. I've had mine for a few months and rooted it, installed custom roms, etc. My main problem is where I live I get horrible service on my phone and with T-mo I get a near perfect signal and 4G! Its definitely a upgrade from the OV (I used to own one), the wildfire its an upgrade in some aspects I haven't owned it so I could only tell you on paper its better.
[Motorola Triumph] Android311:
Great info both of you, thanks to you two my mind has been made up and I will get the triumph, perhaps when the price will go down a bit, I just bought the wildfire s so I'm gonna wait a bit, but hopefully soon I will be over in this part of xda :)

NookColor Cyanogenmod 7.1 "Overclocked"
[Motorola Triumph] marc12868:
Or even better. On android forums where its more active :D
[Motorola Triumph] Android311:
great ill look over there :)
[Motorola Triumph] jaaydogg:
Ok well those guys aren't wrong, but my Triumph has all the issue's that many people have reported maybe it's because i bought it when it first came out. Anyway my Triumph has crap reception but theres an app for that lol, also some roms make my phone hot as hell & the battery charging sucks, sometimes it won't charge & i have to go through all this bull**** to get it to charge again. On the other hand i would never go back to the Samsung Intercept this phone is a beast when set up right so i guess it's a love hate relationship for me & the Motorola Triumph.
[Motorola Triumph] Android311:
O I see, I'm sure its way better then my wildfire s....god I hate my wildfire s, Idk y virgin mobile would even allow this to be sold to there customers
[Motorola Triumph] jaaydogg:
that bad huh ? To be honest i think it might be my phone my wife has one & hers seems to be good, so i guess it's a crap shoot on if you get a good one or a bad one.:D
[Motorola Triumph] Android311:
That's true! The virgin mobile HTC wildfire s has a diffrent design back door so you can't buy extended batterys and hard to find nice cases, all the good stuff is on the gsm phones (tmobile) phone feels cheap, i can't stand sense roms bad battery life to small lol and it goes on.... :p
[Motorola Triumph] Android311:
HTC wildfire s vs LG optimus v, I'd chose the optimus v
[Motorola Triumph] jaaydogg:
Good to know about the HTC wildfire though, i was gonna get my mom one but i think i'll pass on that. Don't wanna deal with another UNDER CONSTRUCTION phone all the time LOL.
[Motorola Triumph] marc12868:
What phone of VM's isn't under construction? I think the only solid android phone they had was the OV all the others seem to have some major problems at times.
[Motorola Triumph] jaaydogg:
My motorola triumph, the samsung intercept i had it seems most of VM's phones have problems.
[Motorola Triumph] marc12868:
Yea seems like it. The only phone I didn't have any problems with (besides VM's network being slow as hell), was my rumor touch. Then when the OV cam out I didn't have any major problems. The MT doesn't have major problems on my end, but it does have a lot of minor problems that shouldn't be there. Not to mention a touchscreen that barely recognizes 2 touches on both the MT and the OV. That's one thing I hated about them.
[Motorola Triumph] jaaydogg:
Have you removed the crappy stock screen protector ? Not the peel off one that's on it right out the box. Did this to mine & had Ghost Armor put on it & now the touch response it fantastic.
[Motorola Triumph] marc12868:
Yea I did. I put a zagg invisible shield over it, but now since its not my main phone anymore I took it off so I just use it with the glass.
[Motorola Triumph] jaaydogg:
And it still has touch issue's huh ? I guess add it to the list of BS this phone can provide us LOL. On the other hand i had zagg protector on my triumph too, Ghost Armor is better & guaranteed for life.
[Motorola Triumph] Android311:
Ya I was thinking about selling my wildfire s to go back to the optimus v, although I don't like the wildfire s but that's only my opinion, I'm not telling any one not to buy it but just my thoughts of why I don't like it, but if some want to try the wildfire s give it a shot :)
[Motorola Triumph] marc12868:
zagg is garaunteed for life too. And its a hardware issue. The digitizer is a pos either that or the phone just can't track the fingers either way if you put both fingers together on the same horizontal area the axis snap together tel you move further apart. Get a visual touch test app and you'll see what I mean.
[Motorola Triumph] jaaydogg:
mine dosen't have that issue thank god
[Motorola Triumph] marc12868:
What do you mean it doesn't? Get "multitouch visible test" and put 2 fingers on the screen and try moving them around. I'll make a video to show you what I mean if you want.
[Motorola Triumph] jaaydogg:
Are you talking about using two fingers sliding them in opposite directions to enlarge the screen picture ? If not then show me what your talking about.

---------- Post added at 10:00 PM ---------- Previous post was at 09:55 PM ----------

Ok just downloaded the app it seems to work fine on my Triumph, maybe I don't know what to look for but i can move both of them dots at the same time ?
[Motorola Triumph] marc12868:
I'll make a video showing what I mean exactly...
[Motorola Triumph] jaaydogg:
ok sounds good, is this video gonna make me hate this phone even more ? lol
[Motorola Triumph] Android311:
Lol its still better then the wildfire s :p
[Motorola Triumph] marc12868:
Here http://www.youtube.com/watch?v=-8h5OK1jcIE&feature=plcp&context=C3283d8bUDOEgsToPDskIcf1G4zbLv6vwfmLDYgtXT

This is what I mean. The axis stick together and snap when you get too close.

I even just move one finger and the other point moves... That's how bad it is.
[Motorola Triumph] jaaydogg:
Well you were right about this. Break it down to me one more time if you would, what's the problem with our phones, you say it's a hardware issue ? What exactly is the issue ?
[Motorola Triumph] marc12868:
Well its either the phone doesn't have the right hardware to track to fingers at the same time (either the digitizer doesn't support it or the cpu can't recognizes it or something), or it could be a software issue, but I don't think its software since no matter what rom or kernel you have you will have the same issue. Compared to my MT4GS I can have 4 fingers on the screen and can independently track them with no problems. So my guess would be in theory maybe a better digitizer could be put in place to solve it, but I am not completely sure (kinda like synaptics took an HP touchpad and put their digitizer on it that can track 10 fingers). So the problem is it can't track 2 fingers at the same time independently, or it can barely track them and only to an extent.
[XPERIA X8 Themes and Apps] UAL4588:
http://xdaforums.com/showthread.php?t=1357056

PDroid. Does Anyone use this? I'm not sure if the patch will work on the X8 so I'm hesitating to install the patch.
[Galaxy Tab Accessories] thekenderman:
Is this charger rated properly to be used on the tab?
[Galaxy Tab Accessories] thekenderman:
Rated 5v 2A....
[Barnes & Noble Nook Tablet] Indirect:
Alright, I know alot of people follow development actively but I figured I would create and (semi)maintain a timeline including links, etc. All for the benefit of people. This will include problems, releases, etc of major developments. Nothing minor or silly like a few small tweaks. Anyway, let's begin.

Root was found: for 1.4.0

Bootloader was cracked: also CWM was developed, CM9 development starts

CM9 development progress shown ^ see previous link

Root through sdcard found: 1.4.1 and any other versions (since it's made to boot off sdcard first)

CM7 development starts: Goncezilla, CelticWebSolutions and Indirect start (Indirect drops out of the team but helps with fixes and solutions.)

CM7 "beta" released: by Celtic and Goncezilla

CM7 "beta" was found to brick tablets: by formatting the x-loader instead of the sdcard (fix is contained in the link.) (found by indirect {unfortunately} but also fixed by indirect)
[Barnes & Noble Nook Tablet] jonceramic:
1.4.1 SD method confusion

Hey Indirect,

First of all, congrats on the successful debricking. Second of all, thanks for all the work, etc. I would help if I knew how to code, etc. But, I don't (and I'm an Android noob), so I'm grateful.

But third, it seems like the 1.4.1 SD method thread has gotten a bit out of hand from a week ago. There are confusions as to what image is what, and as to how to enable sideloading if you were using 1.4.1, and to if the "n" button fails or not.

Any chance you might go back to that thread and straighten it all out for us lowly beggars, too scared to dive in?

Also, since I'm a complete newb, I'd love a "so you screwed up" mini tutorial on how to use SWM to recover what you just did (I think that's what swm is for?). I've tried searching, but haven't found anything.

Anyway, again, I really appreciate what you're working on and that you make it available for everyone.

Thanks,

Jon
[Barnes & Noble Nook Tablet] daedricgeek:
I am guessing you meant CWM -ClockWorkMod ... just toto indirects thread on the developers forum http://xdaforums.com/showthread.php?t=1482519
[Samsung Galaxy Nexus] Stadsport:
Is it just me, or does entering text (say, on forums) totally suck in the ICS browser? This is my first Android device so I can't speak of earlier versions, but its painfully bad here. Not only is it extremely laggy, even in portrait mode, but if you try to move the cursor through large blocks of text, it often jumps around, disappears, and generally refuses to cooperate. Earlier I resorted to copying my entire message into an email just so I could correct a single word, because the cursor absolutely refused to let me select anywhere near it. I've tried a variety of browsers and keyboards and none of them really solve this at all.

I understand there's software like Tapatalk to alleviate this, but that's not he point. Not every forum has Tapatalk support, and it doesn't really solve the issue of text entry in the browser anyway.

Anyone running 4.0.4 want to chime in and let us know if these issues have been addressed since 4.0.3? Thanks...
[Samsung Galaxy Nexus] rjax:
Not just you, but I don't know if we're some of the few or the many...

I'm stock (rooted) 4.0.2 CDMA and I hoped it had just been a problem with the 3rd-party keyboard I was using. Seemed to get a little better with the stock keyboard, but not nearly better enough. I'm also hoping this is fixed in the 4.0.4 update.
[Samsung Galaxy Nexus] volsey:
Text entry all over the place is horrible. I had to turn off spelling correction or else I'd get massive stutters in portrait mode in the Messaging and Gmail app.

This disappointed me cause it takes away the red squiggly under misspelled words that I was looking forward to.

But specifically talking about the browser, I too notice large amount of lag and stuttering. Maybe even moreso than my 2 year old Nexus One. I also find the little blue anchor used to move the cursor WAY too small, especially for such a large screen. This combination results in an awful time searching using the browser. Stock, 4.0.1. btw. Pretty sad that a phone like this has such fundamental flaws (small but still important). Here's to hoping 4.0.4 fixes this!
[Samsung Galaxy Nexus] z06mike:
I can't tell how it was on 4.0.2 or 3 but I'm on 4.0.4 now and text entry is great! I just tested it right now to see how it was and had no problems. Try Opera mobile to see if it alleviates your woes.
[Samsung Galaxy Nexus] Stadsport:
Flashed 4.0.4 earlier, seems exactly the same. Actually the whole rom performs about the same to me as a 4.0.3 ROM with some performance tweaks. But I didn't play with it much. I did test the text entry in the browser and found no improvement over 4.0.3.

I tried multiple browsers including Opera. Honestly opera is so laggy and jerky to scroll that I didn't even make it to my forum to test text entry before I uninstalled it. I would be miserable replacing the ics browser with that, even despite the text entry problems.

Firefox and nighlty don't exhibit the same problems as the stock browser, but have their own set of quirks and bugs that make text entry equally stupid. Webkit browsers like Dolphin and ICS Browser+ also behave exactly the same as the stock browser.

I also tried a different keyboard to try to alleviate the lag. It helped but not enough to make me use it full time.

tl;dr stock has some serious issues, and so far 3rd party stuff is worse (in my opinion).
[Samsung Galaxy Nexus] David Horn:
I don't understand why the browser seems to think that we don't need predictive text when replying to posts in the XDA forums. I know there's Tapatalk, but I like the browser.
[Samsung Galaxy Nexus] RogerPodacter:
It was my understanding that auto correct was added back in the browser in 4.0.3, no? Not sure about the jump-around bug though, google really needs to fix that.
[Samsung Galaxy Nexus] Stadsport:
It absolutely was fixed, but in doing so the keyboard became extremely laggy. :/

Edit: By the way, I forgot to mention another bug with text entry in the browser. When you're zoomed in and typing, the zoom doesn't follow the cursor correctly. You will often start typing off screen before it "catches up" and jumps to the next line.
[Samsung Galaxy Nexus] skynet11:
Preaching to the choir...

Terminators run on Android :cool:
[Samsung Galaxy Nexus] adrynalyne:
I have predictive text.
[Samsung Galaxy Nexus] nhizzat:
not encountering these issues on any of the forums i frequent.
[Samsung Galaxy Nexus] Stadsport:
The lag is present pretty much anywhere on 4.0.3's browser. There's not much lag in 4.0.2, but there's also no predictive text/spell check in most (read:not ALL) forms on sites.

The cursor bug is only present in large blocks of text.
[Samsung Galaxy Nexus] thequinox:
I've had these issues on every android device be ever had. It just sucks a web text entry boxes.
[Samsung Galaxy Nexus] Stadsport:
Just wanted to throw this out there. All of these problems are non-existant on the new Chrome Beta. Its the first browser I like enough to take me away from the stock Browser :)

But I really like the stock browser's icon. Nothing Nova couldn't solve!
[General Questions and Answers] I Am Marino:
I made a folder on my C: drive named "Android" and it contains the SDK, fastboot, adb, images, etc that I need to use fastboot and such on my Rezound.

If I want to use these tools on another computer, can I just copy the whole folder my my C drive and just copy them to another computer and get right into it right there and then?

Or do I have to reinstall them all from scratch?
[General Questions and Answers] juzz86:
You'll need to reinstall the Android SDK (and by default Java JDK) on each computer. ADB, Fastboot rely only on the Android SDK. They will work just fine after you reinstall the SDK. Your ROMs, Radios, .zips etc. can all just be copied across :)
[General Questions and Answers] I Am Marino:
So just reinstall the SDK and Java, then i can drag and drop the rest?

-Sent from my Rezound-
[General Questions and Answers] juzz86:
Roger that :)
[General Questions and Answers] I Am Marino:
Thanks man.

-Sent from my Rezound-
[Samsung Galaxy Nexus] a1exus:
is there a way to make it work on galaxy nexus? i bought this game was hoping to really enjoy it on my phone but it's not working (at least for me)
[Samsung Galaxy Nexus] asb123:
works fine for me. At what point does it not work
[Samsung Galaxy Nexus] a1exus:
Really??? Why won't it work for me??
[Samsung Galaxy Nexus] phaze one:
I have issues with multitouch but supposedly people on 4.04 have said the update solves the problem. What issues are you having?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] a1exus:
Are you guys using stock 4.0.2?
[Samsung Galaxy Nexus] asb123:
I am on 4.0.3 AOKP now and also had it running on stock 4.0.1

I did run into multitouch issues (not always though)

Since the latest market update it should work, make sure it the app is updated to 1.3
[Samsung Galaxy Nexus] clarkey1269:
works fine for me as well.

only problem i had was when i flashed a different kernel the game would start and the screen would just go blank but after a wipe was perfect :D
[Samsung Galaxy Nexus] a1exus:
I take it back it works now...awesome!
[Samsung Galaxy Nexus] a1exus:
Can't wait for 4.0.4
[Galaxy S II Q&A, Help & Troubleshooting] despot55:
my samsung sgs2 can't boot on startup after update

always hang..someone plz give me the solution..

plzzzzzzzzz:(
[Galaxy S II Q&A, Help & Troubleshooting] MistahBungle:
Boot loop thread.
[XPERIA X8 General] Mayank77:
What are the list of available ICS ROMS for our Xperia X8 ?

Out of these which is the most stable ICS ROM for daily use ?

Also , when is the stable version of ICS for X8 likely to come ?
[XPERIA X8 General] Mayank77:
Well , yes I am a new member. I wasn't sure where to post this thread. I intended this to be a thread of general discussions of latest ICS ROMS trending around for X8.

But , I marked it as a question.

Sorry for wrong placement of this thread :(
[Samsung Galaxy Mini] jrandroid:
http://hotfile.com/dl/145455059/c180343/GT-S5570L_SAM_S5570LWMKPM_S5570LSAMKP6_S5570LWMKPM.zip.html

Password: sampro.pl

Please press thanks ------------------------------>

Source: Sampro
[Samsung Galaxy Mini] jrandroid:
Upon flashing the firmware this is what i got..

Version: 2.3.5

PDA: S5570WKS7

Phone: S5570WKS2

CSC: S5570OXXKS2

My source: Sammobile / Firmware

--------------------------------------------------------------------------

Link above was updated.

Got the correct link pasted above.

Source: Sampro.pl
[Samsung Galaxy Mini] Przekret:
PDA: S5570LWMKPM

Phone: S5570LWMKPM

CSC: S5570LSAMKP6

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=GINGERBREAD.WMKPM
ro.build.version.incremental=WMKPM
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Wed Nov 23 12:32:13 KST 2011
ro.build.date.utc=1322019133
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-73
ro.build.tags=release-keys
ro.product.brand=samsung
ro.product.model=GT-S5570L
ro.product.name=GT-S5570L
ro.product.device=GT-S5570L
ro.product.board=GT-S5570L
# ro.build.product is obsolete; use ro.product.device
ro.build.product=GT-S5570L
ro.product.cpu.abi=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=GT-S5570L-user 2.3.6 GINGERBREAD WMKPM release-keys
ro.build.fingerprint=samsung/GT-S5570L/GT-S5570L:2.3.6/GINGERBREAD/WMKPM:user/release-keys
# Samsung Specific Properties
ro.build.PDA=S5570LWMKPM
ro.build.hidden_ver=S5570LWMKPM
ro.build.changelist=754025
ro.build.buildtag=jenkins-HUDSON_LATIN_GINGERBREAD_TASS_MR-347
# end build properties

Download:

http://hotfile.com/dl/145455059/c180343/GT-S5570L_SAM_S5570LWMKPM_S5570LSAMKP6_S5570LWMKPM.zip.html