yashsingh1/xdaforums huggingface dataset:
[Fascinate General] Falcyn:
As everyone has said, this question is ridiculously premature to say the least.

But that said, to those saying "Honeycomb isn't for phones!": That's simply not true. Google execs have said Honeycomb will run on phones in the past, and they talked about how apps will run on both Honeycomb phones and tablets during today's event.

http://pocketnow.com/android/matias-duarte-gives-glimpse-of-android-honeycomb-on-phones

http://news.cnet.com/8301-30684_3-20030465-265.html
[Fascinate General] RacerXFD:
Seriously, this thread did nothing to aid in development. This belongs in general.

It just makes it harder for members to sort through to actual roms and development.

Whether or not honeycomb will come to this phone is up to the developers who will have to port it for this phone. If they are willing, you will have it. But requesting this will get you nothing.
[Fascinate General] cstrife999:
That's just an emulator. I would still think it's Tablet only. http://www.examiner.com/gadgets-in-san-jose/google-android-3-0-will-be-available-only-for-tablets

An emulator would have all possible options.
[G2 and Desire Z Q&A, Help & Troubleshooting] Minker17:
Anyone have any suggestions?

Thanks
[Captivate Q&A, Help & Troubleshooting] darkfalz:
So since the Galaxy S phones are more of less the same hardware-wise, (for example) can one flash a (T-Mo)Vibrant modem to a (AT&T)Captivate, and use it on T-Mo, or vice-versa?
[Captivate Q&A, Help & Troubleshooting] yokozuna82:
You can unlock the captivated to use it on t-mobile edge network but the 3g radio(hardware) on both devices are different so the answer would be no
[Captivate Q&A, Help & Troubleshooting] darkfalz:
What type of radio do both of the phone use? I can't seem to find a good detailed teardown for the Captivate. The Vibrant has this . And this one is either another Vibrant or the i9000.

If you look up the transceiver, it says it supports UMTS bands I-VI and VIII-X.

Wikipedia page on UMTS bands.

So the supported bands are 2100, 1900, 1800, 1700, 900, 850, 800.

AT&T uses 850 and 1900 for 3G. T-Mobile uses 1700 and 2100 for 3G.

So, if both of those teardowns I linked are Vibrants, then I still would like to find one for the Captivate. However, if one is the i9000, and the hardware is still the same, why would it not be the same in the Captivate, since the chip supports all the necessary bands?
[Captivate Q&A, Help & Troubleshooting] Kaik541:
the Captivate's hardware supports:

2G/GSM: 850, 900, 1800, 1900

3G/UMTS: 850, 1900, 2100

the Vibrant's hardware supports:

2G/GSM: 850, 900, 1800, 1900

3G/UMTS: 1700, 1900, 2100

AT&T uses:

2G/GSM: 850, 900, 1800, 1900

3G/UMTS: 850, 1900

T-Mobile uses:

2G/GSM: 850, 900, 1800, 1900

3G/UMTS: 1700, 2100

the modem.bin that you flash to the phone only controls software level access. flashing the modem.bin will not magically give you 3G access on TMO with the Captivate. Oddly, the Vibrant *does* support one of the 3G bands for AT&T (you can unlock the Vibrant, and get 3G on AT&T) but the same is not true of the Captivate with TMO. Unlocking the phone is different than flashing a modem, you can check the network unlock state with SGS tools, as I can't remember the dialer code. To use an AT&T phone on TMO, you must unlock it--either through the tools available here on XDA or calling AT&T and attempting to ask for an unlock code. But, at least with the Captivate, you will only manage to get EDGE speeds... changing the modem.bin will not alter this.
[Captivate Q&A, Help & Troubleshooting] darkfalz:
Ok, that helps. I'm not actually interested in using the Captivate on T-Mo, that was just an example. I talked to someone earlier today that has his Vibrant working on AT&T 3G, so I just figured that it went both ways.

I have yet to find a good, detailed teardown for the Captivate and am too lazy to disassemble mine...any idea as to what hardware it has, since it's not the same as the Vibrant/i9000 (which are the same according to those teardowns)?
[Captivate Q&A, Help & Troubleshooting] newter55:
You can have it disassembled in less than ten minutes.
[Captivate Q&A, Help & Troubleshooting] darkfalz:
Fiiiiiiiiiiiiiiiiiiiine, I'll do it myself. And will post my finding here.
[Galaxy S I9000 Q&A, Help & Troubleshooting] hari46:
I have got galaxy s with build FROYO.BOJP7, which file should i download in the CF-Root thread to root my phone?

Thanks
[Galaxy S I9000 Q&A, Help & Troubleshooting] astralmaze05:
u can use that or u can use superoneclick
[Galaxy S I9000 Q&A, Help & Troubleshooting] hari46:
i wont be able to use clockworkmod recovery with 3e recovery..i need to be in 2e recovery to flash updates or other ROM's
[Nook Color General] Rboy014:
I have loaded the 1.1 on my nook and now i cant log into my google account, no access to the market place. I'm not sure if i did something wrong when i load the file.. I use clockwork mod to load the file. does anyone know how to fix this problem?
[Nook Color General] jparness:
I was having a problem with the Market last night as well, right after I flashed the rooted 1.1 image. I rebooted with the microSD card removed. Then inserted the microSD and rebooted again and everything seems to be OK now. Others were reporting that the Market was down last night, so it may be that as well.
[Nook Color General] A. Nonymous:
Yeah, the market was having issues last night for some reason. Is it still having problems?
[Nook Color General] molivrock:
Looks like Google opened up a web market - what a game changer !!!!!!!

market.android.com

I can't do links yet
[Nook Color General] succulent:
Delete folders,

/data/data/com.android.vending and

/data/data/com.google.android.youtube

Clear data,

Gmail

Gmail storage

Market

Google Talk Storage

Youtube

Power off/Turn on and run the Market.
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
I've got one of the first HD2s that were sold. These have the issue, that the touchscreen is way too sensitive, which makes typing a real pain.

Using Windows Mobile this was adressed with a registry tweak, that set the sensitivity value lower - which did pretty much the trick.

The Android SD-builds seemed to benefit from this setting, since I had no troubles typing with those.

Now with NAND however, this problem is back. I really have a hard time, since the touchscreen goes mad again. Is there any way to apply the WM reg-tweak to Android with an equivalent setting?

Would be much appreciated!
[HD2 Android Q&A, Help & Troubleshooting and Genera] Ultimaex:
Do you also have that 'ghost' problem when you are outside and wind is blowing over your screen? :P
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
Nope, that I didn't experience (yet).

But there surely must be some parameter in the Android drivers, that controls the sensitivity and could be altered. I really hope one of the devs stumbeles over this thread.

It would be so much helpful (though I'm not complaining here. What they did to this point is outstanding already).
[HD2 Android Q&A, Help & Troubleshooting and Genera] nickluck:
That's exactly my problem. I had the same issue with WM that got solved via reg tweak. Hope the same can be done in Android, because it's annoying.

Actually, in WM, I saw several times button pressed without touching the screen.. :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
Yeah, and I see it again now with NAND. Starts driving me up the wall... :(
[HD2 Android Q&A, Help & Troubleshooting and Genera] eghbal:
Me too! Any solution?
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
Let's keep bumping this thread with all folks that have this issue. Best way to attract attention is a loaded thread. :D
[HD2 Android Q&A, Help & Troubleshooting and Genera] felipillo:
Try this:

Go to Settings -> Language & Keyboard -> Touch input -> Text Input -> Calibration Tool

Maybe this helps.

-----

Versuche es mal so:

Unter Einstellungen -> Sprache & Tastatur -> Touch Input -> Texteingabe -> Kalibrierungswerkzeug

Vielleicht hilft dir das. ;-)
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
Thanks, but I don't have "Touch Input" as an option. I'm on Gingerbread, maybe that's why.

However, I guess this option only optimizes the way, the keyboard interprets taps. Adjusting the center of each key to the way you are used to type. Know what I mean? It doesn't sound like an option that could really rid of the problem at hand.

I'm not only having issues typing, but also tapping on links in the browser without zooming in and the like. It's everywhere, since everything is about touching, isn't it? ;)
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
This problem plagued me in MAGLDR 1.2. Going to try 1.3 tonight and different builds to see if it's fixed. :/
[HD2 Android Q&A, Help & Troubleshooting and Genera] Meads:
Please report back.
[HD2 Android Q&A, Help & Troubleshooting and Genera] FreakyFerret:
Task 29

SPL to stock then back HSPL.

Magldr 1.13

Clockwork 1.3

Hyperdroid GBX v2.0 (the Feb 02, 2011 build)

Screen sensativity is okay with the "ghost hand" touch issue only during:

- When trying to select Ringtone

- When trying to type password in the browser for AppBrain authentication

I installed ADW.Launcher, and the touch screen stuff got a bit wonky in it too.
[HD2 Android Q&A, Help & Troubleshooting and Genera] leyley:
have the same problem... i thing its a hardware problem, i flashed to winmobile back an there is the same problem...
[Droid X General] wb1960:
I downloaded maderstcok 340 and updated. I then did a factory reset and re-rooted using z4. I then tried to download the gummyjar rom using rom manager. My droid x is now stuck,on boot up,the pic of flashing 4 android figures and saying gummyjar

I suppose I need to flash back but dont k now how and need to flash from the .340

Can anyone give me detailed instructions on how to fix my X and how to flash
[Droid X General] SysAdmin-X:
Try booting into moto recovery (hold down the menu button along with the power button, when the picture of the green android guy comes up, push the search button)

Do another wipe data/factory reset and reboot. If that doesnt work then you will need to sbf
[Droid X General] codythibeauuu:
Exact.

Wipe your data and you should be good to go. Same thing happened to me with GJ 2.0.
[Droid X General] smyers1012:
if none of this works and you really messed up your phone msg me on AIM: XxMMZxX . I have files to unbrick your phone on .340 guarunteed to work!!!!!
[Droid X General] SysAdmin-X:
Unless this guy ^^^^ works for Verizon or Moto and is holding out on the rest of the Android community... anyone can get access to the files to unbrick your phone. Check out mydroidworld for the 2.3.32 full sbf and the 2.3.34 system only sbf. If you need more help with sbf files, post back, and myself, or one of many other people are likely to help you out.

PS... to smeyers1012...unless you have "Secret files" please just offer the help in the forum... it makes it easier for everyone =) Thank you
[Droid X General] kdkinc:
If I'm reading this correctly ??

After reloading the Market programs, if you want to stick with the full "Maderstcok SBF".

You must do a full reboot BEFORE Rooting, Rom's, breathing, Or anything else.

IMHO kick the Rom manager to the side of the road , Again IMHO.

Then do what you wish.

When I use Maderstcok's SBF I bypass the market downloads so that I can then

get to the new Rom i,m really trying to get to.

Maderstcok SBf, full reboot, Root, Rom
[Droid X General] billymac122:
Wouldn't it be the home key and power, not the menu one?
[Droid X General] SysAdmin-X:
Yes. I may have mispoke. It is the home button
[Galaxy S I9000 General] themate1987:
If anyone is experiencing random restarts with darky's rom he/she should: long press power button> select recovery> wait> click delete(clear) cache >than click advanced> click clear dalvik cache >and when it's all done than restart adbd and reboot device
[Galaxy S I9000 General] paky79:
Hello,

I experienced with this ROM a strange issue: randomly with the phone in stand-by pressing the power button the phone is unable to switch on the screen and the only way to re-switch on the screen is a long press of power button in such a way that it is able to shutdown and reboot.

Has someone else experienced the same issue? Suggistions to fix it?

Thank you
[Galaxy S I9000 General] decouvrir:
better solution: don't use Darky's
[Galaxy S I9000 General] saphirrot:
best solution : read -> think -> dont hate !
[Galaxy S I9000 General] sempot:
you suck big time !
[Galaxy S I9000 General] themate1987:
what version do you use .... try updating
[Galaxy S I9000 General] paky79:
I'm on the 9.1!

Sorry, but I have searched and I read a lot but no answers to this problem have been found!
[Galaxy S I9000 General] ragin:
Has this been reported to Darkyy? And if so, what is his response?
[Galaxy S I9000 General] lljkpugna:
I've had a couple of random restarts on Darky's - I assumed it was due to the lagfix for some reason. But I've cleared the Dalvik Cache and will post back if that doesn't fix it!
[Galaxy S I9000 General] ragin:
Flash Darkyy's No-Wipe ^ flash Doc's No-Wipe. You will see the difference.
[Galaxy S I9000 General] g00ndu:
Shouldn't this be

"Has this been reported to the moderator?" This is the Development forum.....
[Galaxy S I9000 General] matsuru:
i experience this whenever i had my phone plug in over-night to recharge to full 100%. after i unplug and off the screen, it just wont wake up until i long press power button to restart it. then after that, everything seems fine until my next overnight recharge.
[Galaxy S I9000 General] Darkyy:
So, what's the difference?

@topic

Random reboots?

There are thousands of people running my ROM everday and don't have any issue like that.

The OP is indeed right - clearing caches might work.

You guys may have to wipe - don't worry, a new ROM which will do that 110% automatically is coming soon.
[Galaxy S I9000 General] numo:
Installed R4 yesterday (going from another custom ROM via resurrection and then the latest greatest with wiping) and already experienced some reboots. Last one was trying to copy a directory from a sdram to external SD. Next try was OK.

I am going to wipe the caches - I'll report if this does not fix it.
[Galaxy S I9000 General] MaXo64:
on 10.2, just use another Launcher. TwLauncher is the issue.
[Galaxy S I9000 General] knightdaemon:
I get random reboots when using Google Maps Navigation, it just freezes for 4-5 mins then reboots... sucks when driving...
[Galaxy S I9000 General] White Hawk:
Just adding my tuppence...

I wish to mention before I start that I am more than happy with all aspects of Darky's 10.2EE - it's a really snappy and slick-looking ROM.

I have had the ROM installed for about twelve hours now. I installed the ROM only after cleaning-down my SGS, removing anything and everything that was not stock, and formatting with prejudice...

...but I'm a little concerned about something. Three times today, the system has apparently rebooted, showing the boot animation.

I do not believe it is a standard reboot, however, as it is very quick. It is rather more like a quick reboot, where the ram is cleared and the front-end re-loads.

It has happened while I was restoring apps (app only, no data), while I was downloading game data (N.O.V.A 2 first launch) and one other time (I forget what I was doing).

I am running ADW Launcher EX, so I don't believe it has anything to do with TWLauncher, though I may be ill-informed to make such an assumption.

I imagine that restoring my apps and intensively downloading data might be putting my SGS under some stress, and while it does not reboot while running anything particularly CPU-intensive, it does appear to be occurring when moving large chunks of data around.

However rare this issue, I'd welcome sensible suggestions on what to look out for. I'm going to see if I can replicate the reboot while plugged into the log viewer - if anything useful comes of it, I will post the result.

Again, let me re-iterate that I am not complaining - this is an absolutely amazing ROM, and if it happens to perform a ten second reboot every now and again as a result of heavy downloading or data movement, I think I can live with it. Everything else lives up to the 'blazing fast' claim admirably, and there seem to be massive improvements to general performance in CPU-intensive apps too (I was previously running Tayatuma's FroYo ROM, and despite some glitchy behaviour, I was too lazy to get rid of it until now).
[Galaxy S I9000 General] SixHouse:
lol darky. thats funny

10
[Galaxy S I9000 General] spamtrash:
@Whie Hawk:

1. DO NOT use 10.2, if you can use 10.2.2 (you flashed recently, didn't you?);

2. you are on custom ROM. Therefore, it is ALWAYS better to install app from Market, than to restore it, as some "minor" differences can cause "big" issues;

3. I'm (personally) glad that you're not on the "blazing fast" stadium yet ;)

4. what I'm doing while switching ROM... is: I have all... "out of market" apk's on card, ready for install, while the Titanium is rather a list for me, not the resource. simply, when I finish flush, I check on titanium what I had, and then I reinstall it fresh from Market/SD card. BTW, Titanium is best for freeze/backup/restore while I'm on same ROM...

@Sixhouse: sorry, I couldn't understand... For a time being, looking on your posts, I presume that you are aiming to have 10.000 useless posts on XDA in different device's threads... Is it a homework in your primary school?
[Galaxy S I9000 General] got-petrol:
Best idea ever
[Galaxy S I9000 General] White Hawk:
With a name like decouvrir, I can only assume the poster of the 'better solution' comment is French. I can therefore excuse him for his ignorance and arrogance, but that doesn't mean the comment was any more helpful or constructive than surrendering to inferior numbers. Repeating the comment is also pathetic. It might serve all purposes better if those who wish to denigrate the work of the ROM builder might suggest alternatives and/or reasons why alternatives should be chosen. I didn't think I was visiting a forum populated by children. :P

_____

@spamtrash: thanks for taking the time to respond.

I shall find and install 10.2.2. I did flash recently. Very recently. Is this important? Am i running on borrowed time? Is my phone a dead brick walking? o.O

I did end up using the Market for most of the reloads in the end, as it happens. I used Titanium to restore skins, fonts, and relatively inconsequential bits and pieces, mostly. They seem to be working okay, so I think I can breathe easy. I reloaded the launcher, various widgets and major apps from the Market.

I am not sure I understand the 'stadium' comment. I am pleased to note that the phone is considerably more responsive and snappy (and stable; a few random reboots notwithstanding) than it has ever been... but that may have as much to do with the fact that I've gone from a chopped-up FroYo ROM to a Gingerbread one.

I got another reboot while waiting for a 500MB+ download for one of my games (installed from Market, initial run with phone-specific game data downloads). I wiped the cache and dalvik cache again after posting, and have managed to download a few more large chunks without issue. I might be jumping the gun...

On a side note, my battery is draining fast even after a strict calibration. I'm looking at whether swapping modem files is relevant to this, or if it's just because I'm keeping it busy (gotta get all those screens filled with junk again).

_____

Addendum: Nope, just got another quick reboot just after running a game and returning to the launcher. I am about to flash 10.2.2 instead.
[Galaxy S I9000 General] spamtrash:
Good idea to flash 10.2.2, it may be better for you.

The "stadium" emmm... I'm observing a lot of users, which 5 minutes after flashing are stating: it's blasting fast ;)

Hope it will be better for you, but just in case: have you tried to look after help on the Darky's dedicated forum yet?
[Galaxy S I9000 General] White Hawk:
So... since my last post, I have been breaking-in the 10.2.2 ROM. I am more than pleased with it - stable, reboot-free, and ever-so-slightly easier on the battery than the clunky FroYo-based ROM I was using before. Even with all the eye candy active, my phone had never been more responsive and glitch-free.

Cheers for the recommendation. With so many sources and disparate information repositories, I was not aware of a later version than the one I had installed. It is evidently more stable. :)

_____

I'm still confused by the pathetic "solution" message. As the original poster and the repetition troll have failed to come forward with an explanation as to why I should not consider using Darky's ROM, I can only assume that there is no substance to the assertion. I have been unable to find any serious problems reported for these ROMs that can't usually be filed under ID:10T errors. I must therefore conclude that until such a time as my SGS explodes, fails to boot, or attempts to take over the internet and usher in a digital apocalypse, I'm no better off with any other ROM.
[Hero, G2 Touch General] bassmonkey:
hi all. im getting that annoying 'sorry process com.htc.bgp has stopped working' crap every time it tries to sync facebook contacts. ive done tones of searching and tried removing and re adding the facebook account, clearing data/cache. it not a clash with google cos it does it even when im not logged in to google, ive tried official 1.5 rom - no problem there, accepted the first part of update -still no problem, accepted the 2.1 update - boom! it also does it on villain 12 now. have no idea why its just started doing it :mad: :confused:

anyone else having this issue at the mo?
[Hero, G2 Touch General] tfn:
HAve you tried updating the facebook app

found on google ( apparently you need to backup your contacts first

goto settings, applications, manage applications, all

then search "contacts storage", click on it, then choose "clear data".

after that the contact storage should work again, allthough you lost all data

in it...
[Hero, G2 Touch General] bassmonkey:
Hi, thanks 4 the reply. I have tried clearing contact storage with no luck :( when u say update Facebook do u mean Facebook 4 android (if so, yep, done that) or Facebook 4 sense (if so, how do I do that?)

This is really p***ing me off now :(
[Hero, G2 Touch General] Bantu85:
Hi there,

An interesting cause i read about is apostrophess in names. Apparently the contact sync messes up if you have an ' in your name.... others also recommend clearing "Calendar Storage".

I know that installing a a custom rom fixes all ;) (but adds its own problems :P)

Good luck!
[Hero, G2 Touch General] bassmonkey:
Hi. Yeah, that was the cause of a previous error but not this time. After a lot more searching and the help of a tech friend it seems that its a sql mismatch between sense n Facebook. Htcs response was basically 'turn it off n on again'! So basically I say **** you HTC and am now on custom, no-sense Rom n my next phone won't be HTC!
[Hero, G2 Touch General] Bantu85:
you made the right choice :)
[Hero, G2 Touch General] bassmonkey:
Seems so :) I do like the look of sense but I'm now on elelinux 2.2 special running its default kernel speeds and its over twice as fast as stock 2.1 (4.1mflops as opposed to 1.8) and nearly twice as fast as my gf's wildfire on stock 2.2 (she gets 2.2mflops) and with adw launcher to customize everything actually looks better than sense... screw you HTC :)
[Hero, G2 Touch Q&A, Help & Troubleshooting] brat.haneq:
hello everyone

I know that there are few people using gingerbread at the moment.

There is one thing I would like to ask - does colorize widget work with Gingerbread (ie. facebook widget). It's scrollable.

Perhaps someone is using it, and can tell me?

Cheers

brat.haneq

EDIT:

I just installed gingerbread rom from Elelinux. (0,3). and as I was afraid - in the stock launcher colorize widget doesn't work.
[Hero, G2 Touch Q&A, Help & Troubleshooting] zagielek:
You would have to use another launcher to get Colorize Widget going.

appbrain: