yashsingh1/xdaforums huggingface dataset:
[Dell Streak 7] khaytsus:
I was going to ask this too, found this thread.. According to a few posts on google, it should work like the following.. Can someone try this and see? My DS7 is on Froyo, I keep saying I want to udpate it sometime, but for now it's working pretty good. I can get up to step 8 on Froyo but it won't do anything beyond pairing.. I've read that Honeycomb this should work..

on Tablet, go to settings>wireless & networks>tethering and portable hotspot and make sure that "Bluetooth Tethering" is UNCHECKED, this is NOT what we want

on Tablet, go to settings>wireless & networks> enable airplane mode (optional; for 3g tablets)

on Tablet, go to settings>wireless & networks> enable bluetooth

on your android phone, go to settings>wireless & networks (or equivalent)> enable bluetooth

Make sure that both devices are discoverable, so that they can see one another, should be in settings>wireless & networks>bluetooth settings

on Tablet, go to settings>wireless & networks>bluetooth settings>select your phone in order to pair it with your Tablet

a box should pop up on both devices, select Pair on both devices

on Tablet, once the pairing is complete (still inside bluetooth settings), select the phone, it should say paired but not connected underneath it

The two devices should connect, once connected there should be a wrench next to the connected device, clicking on this will show an option to tether, click this option if it is not automatically enabled

TA-DA, if it worked then in the bottom right hand corner of your Tablet should have two bluetooth icons, one should indicated that your bluetooth is turned on and the other should say bluetooth tethered, you are now using your phones internet data plan on your Tablet, aka not counting towards your Tablet's data plan
[Desire Q&A, Help & Troubleshooting] aekold46:
Hi!

I'm french so I'm sorry for my poor english.

Since one week I've a HTC desire which doesn't boot any more.

It stays on the htc logo with white screen.

I tried to go to the recovery but always this white screen.

So I tried to reinstall the recovery by fastboot using fastboot flash recovery recovery.img .

always the same error even with several different recoveries

I tried the PB99IMG_Bravo_Froyo_HTC_WWE_2.29.405.2_Radio_32.49.00.32U_5.11.05.27_release_151783_signed on the µSD ...

I tried RUU_Bravo_Froyo_HTC_WWE_2.29.405.5_Radio_32.49.00.32U_5.11.05.27_release_159811_signed.exe .... same problem.

Now,in the bootloader:

What do I have to do?

Here's a paste oh the fastboot oem boot

Using the exe RUU it's again s-off.... that's strange,isn't it?
[Desire Q&A, Help & Troubleshooting] aekold46:
up.

do I have tu erase the recovery with fastboot in order to re flash it?

i've already viewed the Bortak's guide but nothing worked
[Desire Q&A, Help & Troubleshooting] ikidntu:
I never need to erase anything before flash recovery.

You probably not S-OFF, try to boot into bootloader first by turn it on while holding back key, what do you see on that screen ?
[Desire Q&A, Help & Troubleshooting] aekold46:
so i've tried many things and.... it boots!

i've downgraded the alpharev hboot

then install recovery via fastboot

install hboot cm7

flash radio

and flash cm7 rom and wipe

thx to all the support provided by this forum!
[Desire Q&A, Help & Troubleshooting] lkj-17:
how do you do that?
[General Questions and Answers] Spartan Legionnaire:
I recently bought the Samsung Galaxy 551 i5510 smartphone, but when starting to use it, I noticed that there was a problem with the screen. It has a problem on the left of the screen, an narrow area that doesn't detects touch input, it like 1.5 cm wide, from top to bottom. I don't know what to do, I restarted the phone, used in horizontal form, the same area does not detect touch input. Thanks.
[myTouch 3G Slide General] zacxaroo:
Hi everyone,

This is my first post, my superuser upgraded yesterday and the app now says that my binary is out of date. It has an option to upgrade the latesest but it fails to do so every time I try. Has anyone else experienced this problem?
[myTouch 3G Slide General] jacewt:
Yep, I did. I am guessing you are not s-off, neither am I.

Go to rom manager and update from there. Go to download ROM, then get superuser, should be the third choice there. Then choose 3.0.2 efgh
[myTouch 3G Slide General] lordstein:
you have to go to the official page of superuser http://androidsu.com/superuser/

or download this file http://downloads.androidsu.com/superuser/su-3.0.2-efgh-signed.zip and after flash this zip with clockwordmod recovery and the problem will be resolved.

i resolved this problem with this metod.

sorry for my bad english
[myTouch 3G Slide General] zacxaroo:
Thanks so much, that notification that kept coming up was about to drive me crazy! :)

Sent by a rooted slide
[AT&T Samsung Galaxy S II SGH-I777] justabrake:
just curious since this has the NFC battery compared to the international SGS2 do we AT&T have to use battery's with NFC !

Also what if the international phone puts in an NFC battery will they have that built in automatically
[AT&T Samsung Galaxy S II SGH-I777] thelastjedi:
Just inserting the ATT battery will not give anyone the powers of NFC, if thats what you are asking. Apparently someone found four contact tips on the ATT version instead of three in the international, so that the NFC can talk to the rest of the phone. So there needs to be mechanisms like that in place. So, in short no they won't get NFC by putting in your battery.

But you can insert a replacement battery without NFC and it will just work fine but you wont have NFC (if ATT flips the software switch on, that is). Doesn't mean I encourage you to pop in any battery and test.

Experts can correct me on this.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Actually, no one confirmed the 3 vs 4. I know Infuse had 3 - I don't know what international has. I asked and no one provided the information.

Also international batteries will NOT work fine. They flake out as soon as you connect a charger or USB. connexion2005 spent hours trying to debug constant reboot loops and it turned out to be due to using an I9100 battery.
[AT&T Samsung Galaxy S II SGH-I777] justabrake:
I'm glad I asked because I bought 2 batteries 1 is a off Chinese brand i9199 and the other is a original samsung non NFC battery , I was going to buy the international galaxy but changed my mine and bought the AT&T phone

So your saying the off brand i9100 battery is no good ? just wondering how a battery could cause problems when it's only pushing juice,

I read about the NFC battery someone mentioned it has a chip inside so I guess that isn't true ! so it actually has a extra prong and so does the AT&T phone right!

I wasn't planning to use the i9100 brand battery all the time and charge it in a charger thought I would switch them out when out for the day , So would just using that battery cause problems ?
[AT&T Samsung Galaxy S II SGH-I777] jefferoniandcheese:
In case you still want the info Entropy, I just checked with my roommate's I9100 (I have an i777), and it also has 4 contact tips
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
The battery has an ID resistor (I think it's the pin between + and -) - if it's the wrong value, the charge circuitry will force a shutdown/reboot when charging.

Actually it's the kernel - but until I'm positive that there is NO risk resulting from removing this protection mechanism, I'm not doing it.
[AT&T Samsung Galaxy S II SGH-I777] agh1701:
The 4th contact is for a antenna in the battery.
[AT&T Samsung Galaxy S II SGH-I777] foxbat121:
This is not the first time Samsung did this. The original Galaxy S batteries are the same. You can't use the Verizon version's battery with rest of Galaxy S lines (AT&T, T-Mo and Sprint). If you do, you get the reboot.

After seeing the information from Verizon about about Galaxy Nexus battery, it seems the NFC chip, not just the antenna, is inside the battery.
[AT&T Samsung Galaxy S II SGH-I777] guilin:
I'm willing to try it if you are willing to create a special kernel.

I'm currently in Hong Kong and bought an i777 from one of the local small merchants. The phone worked in the store, but did not charge when I got it home. The battery does not say "Near Field Communications" on it, even though it looks like an authentic Samsung battery. So I am assuming that I have a genuine i777 (it says AT&T on the top and has the four buttons on the bottom), and a genuine I9100 battery. I am currently waiting for an NFC battery that I bought on Ebay. I also bought a local noname battery so that I can charge one while using the other. Both batteries have 4 terminals.

If anyone knows what the value of the ID resistor is, I'm also willing to try that route to get the phone to charge.

The phone came with MIUI 10/28 and everything else seems to work, including GPS, WiFi, etc. MIUI 12/2, 12/9, 12/16 (not US version) fix the charging problem, but then the phone audio doesn't work. I tried flashing all the i777 modems, but none fixed the audio problem. I was not able to flash the CM7 converted modems because CWM gave some error messages about "I777" (I think it said failed assertion).

I tried flashing Unnamed, Cognition and CM7, but they don't fix the battery problem, but the phone audio and everything else works.

I am a total noob so if I've used any incorrect terms, please forgive my noobness. The last two weeks have been quite an adventure, searching forums, learning about rooting, recovery, downloading ROMs and kernels and modems, etc. Actually, its been a lot of fun.
[AT&T Samsung Galaxy S II SGH-I777] tedkunich:
Most of these batteries will have four contacts, two for power and two for communication to the gas Guage within the battery pack (I2C interface). The few batteries out there with three contacts use a single wire interface, but they are essentially the same - there is a communication path into the cell to talk to the fuel Guage embedded in the pack. The nfc enabled batteries either extend the capabilities of the fuel guage or add an additional part, but in either case, the two functions share the same communication paths - there are no "resistors" to check or change, the ic(s) identify what capabilities they have to the host via the serial interface.

T
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
The ID resistor is buried deep within the battery, on the same board as its protection circuit.

Take the unit back to the store and explain that they did not give you a functional I777 - if this merchant were legitimate you should have received a properly matching battery with the unit.

WRONG.

Have you read the kernel source code for the fuel gauge driver? Probably not. I have. I've even fixed bugs in it.

Have you read the datasheet for the fuel gauge chipset's predecessor? (The current one does not have a publically available datasheet, but it's VERY close to the previous version used in the original GalaxyS series of phones) Can you even name the fuel gauge chipset without Googling?

Have you used an ohmmeter to measure the resistance of the ID pin? I have.

The fuel gauge chipset is in the phone itself, NOT in the battery for this device.

The phone checks for a legitimate battery by connecting a constant-current source (looks like around 0.3 mA) to the battery contact between the + and - terminals. It then measures the voltage of this terminal to see what the value is when the device is on AC or USB power, and powers off if it is outside of certain ranges. See sec_bat_check_vf_adc in drivers/power/sec_battery.c

I777 batteries are 4.7k ohms, and the device looks for a range between 1.1 and 1.8 volts on the vf terminal. I9100 update3 makes this stricter - 1.35 to 1.5 volts. I9100 batteries appear to have a 6k resistor approximately, the Vf check looks for a voltage between 2.0 and 2.1 volts.

I'm not sure what is on the terminal adjacent to the - terminal on the other side - this is likely NFC-related, it is not a bare antenna (extremely high resistance when powered off)

I've seen evidence that the NFC solution is distributed between the battery and the device - I9100 kernels have PN544 support, and at least one I9100 user has managed to get a successful PN544 firmware load. However without the battery side of things, their device doesn't work.
[AT&T Samsung Galaxy S II SGH-I777] axis01:
There is a thread in the "accessories" section that is devoted to batteries. Some seem to work well while others cause the bootloop.
[AT&T Samsung Galaxy S II SGH-I777] tedkunich:
Have not personally looked at the chipset that SAMSUNG uses, but the Texas Instrument line are in-pack gas gages with either I2C or hdq interfaces. The bq245xx series does both flavors of interface.

Are you an electrical engineer? I am, and have been designing this stuff for years - your 4.7k resistor is a pull up on the communication lines. Standard value per the I2C standard.

I have not seen too many designs where the gaging is outside of the pack, it it makes tracking pack changes and giving reasonably accurate results difficult if not impossible. Now, I have no insite into how SAMSUNG designed the hardware, but reading the source code will not give the full picture either. Fuel gaging is a dual discipline function - there is dedicated hardware to measure and track energy going into and out of the cell, and software must controll and track the data.

Peace,

T
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Yes, I am an electrical engineer.

And you clearly have not read the MAX17040 datasheet. Otherwise you would know that Maxim designs their fuel gauges not to depend on a coulomb counter function (current sensor) - which is why it does not require any calibration. Yes, it gives up some accuracy because of that, but the advantage is that the pack has no fuel gauge chip itself. We have a MAX17042, which is a close relative of the 17040. It does have current measurement capability, but this is not enabled in our device.

We don't actually have a MAX17042 or 17040 - we have a MAX8997 PMIC, the fuel gauge is embedded inside it but functionally equivalent to the MAX17042. Older devices have a MAX17040 equivalent built into the MAX8998 PMIC.

And tell me, how can a resistor between a terminal and GROUND be a pullUP resistor like you claim it is?

Don't you think it's a little odd that they're IDing the battery by taking ADC readings, when if that contact were for an I2C or one-wire bus, they could just embed a battery identification in whatever chip was in the battery so that it could be read digitally? Oh yeah, and I2C doesn't exactly work on a single wire like other Samsungs such as the Infuse would have to have, given that they have three-terminal batteries. How is it that they're reading an ADC that's part of the PMIC or CPU to identify the battery if that battery terminal is I2C or some sort of one-wire digital bus?
[AT&T Samsung Galaxy S II SGH-I777] guilin:
Thanks for all the great info. We did't try to exchange the unit because when we discovered that MIUI 12/2 and later fixed the battery charging problem, we knew that the problem could be fixed/circumvented in the kernel or ROM. My wife and I are retired Electrical Engineers and once we discovered the world of rooting, flashing, adb, CWM, ROMs, kernels, modems, we were addicted. We even rooted our Kindle Fire. If the phone had worked correctly when we bought it, we wouldn't be having all this fun.

Like they say, it's the journey, not the destination.

Thanks again (I already clicked the Thanks Meter).
[AT&T Samsung Galaxy S II SGH-I777] polobreaka:
so a battery boot loop depends on kernel and/or rom?

i bought the samsung 2000 mah non-nfc international version battery for my i777 thinking it should work no problem because i didnt care about having nfc. when i plug my phone in to charge, it causes a reboot loop. i am running task650 icsdout rom with entropy's latest kernel.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
There is code in the kernel that checks for a proper battery.

Until I know more about what subtle differences might exist between I777 and I9100 - I'm not disabling it.

I'll look into maybe making it a "use at your own risk" optional feature.
[AT&T Samsung Galaxy S II SGH-I777] FireRaider:
So after reading almost all of the threads on the 2000mAh battery this one was the deepest and most informative as far as why there are problems.

From what I have gleaned in my readings, the I9100 2000mAh battery can be used in the I777 as long as it is charged externally, and you don't care about the NFC ability. Correct?

And if you plug in the charger at any time with the I9000 battery the phone will reboot and continue in a bootloop?

And perhaps in the future with a kernel change we could use the I9000 2000mAh without the bootloop issue? Correct also?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
Correct. (As long as you replace all instances of I9000 with I9100 - I typo that a lot myself.)
[Xperia Arc Q&A, Help & Troubleshooting] YeeHaa_22:
This morning i got the .368 update (android 2.3.3), and when i want to type text messages, i get this huge white gap above my text (aobut 5 lines), which means i can't see what i typed previously. Also, the line 'Type your text here' has moved down one line.

Is there a way to fix this? Or do i just have to wait till the 2.3.4 update is available here in Belgium?
[Xperia Arc Q&A, Help & Troubleshooting] SXUsr:
Hi.

Can you post a screenshot to illustrate the issue.
[Xperia Arc Q&A, Help & Troubleshooting] YeeHaa_22:
Pic 1: The "Type your text here", on preview before typing any text has moved one line.

Pic 2: The empty space above my text when i reply to someone.

Pic 3: One empty line above my text when i type a new message.

Sorry for the poor quality of pictures, i didn't have anything better to make them.

Thx.
[Xperia Arc Q&A, Help & Troubleshooting] Poker gypsy:
That's the new update, nothing that you can do about it, well that I know of? I don't like it myself
[Xperia Arc Q&A, Help & Troubleshooting] SXUsr:
The screenshot feature. ;) But as said, that's normal.
[Xperia Arc Q&A, Help & Troubleshooting] SnEAkyy:
I have that too. It is really annoying, since you can't see what the message above it is. I wonder why they messed up that look
[Xperia Arc Q&A, Help & Troubleshooting] YeeHaa_22:
Well, doesn't really seem like they intended for this.. (seems like a mistake). Is this fixed in the 2.3.4 update?
[Xperia Arc Q&A, Help & Troubleshooting] Poker gypsy:
Nope maybe 235?236?46+666? Lol
[Xperia Arc Q&A, Help & Troubleshooting] YeeHaa_22:
Guess I'll have to live with it :mad:.. Thanks for the help though!
[Xperia Arc Q&A, Help & Troubleshooting] daveybaby:
You dont have to live with it. Just install an alternate SMS app, e.g. handcent or chomp.
[Defy General] pritesh_100_in:
The current situation with my Defy

was using a rooting 3.3.11 uk froyo version some thing happenned to my defy last night the battery wont charge any more

1 Major issues is Micro usb port isnt working tried to format the cell Via RSD LITE 4.9 in bootloader but windows detects the device as a UNKNOWN devices no RSd lite is not the way to bring back my phone

So All i need is a 2.2.2 SEa OFFIcal UPdate.zip to be flashed via Stock recovery or else plz guide me if there is any other way to recover my Defy

my Cell is in warrenty too but i rooted it and installed CM7 earlier and my M logo is replace with the google CM7 logo so plzz help help me with the logo restoration for the stock recovery
[Defy General] jassi32:
its not bricked as far as my knowledge .....

go to recovery wipe cache /data and wipe dalvik cache......

and go to bootloader and check rsd lite ...did it detected it ....use rsd lite 4.9.....

if dis doesn't work ....after above install a fresh nightly build of cm7 ....and then check ......

do this if you more than 70pc battery .....or you can try on luck.......

if battery dies out buy a universal charger to charge ....and then start over......

its hard to brick defy.....don't worry
[Defy General] pritesh_100_in:
okk.. thankz,.. i will try that 70% thing and connect it to my PC hope it detects the motorola flash interface Any other assistance will e helpfull too

Can any 1 giude me through for making update.zip ( which can work in stock recovery ) from a SBF/ nanroid backup SEa 2.2.2
[Defy General] jassi32:
Requirements

•	Get the SBF you want to flash

- Full SBF: No Nandroid backup needed, always keep CG versioning in mind.

- Fixed SBF: You might need a matching Nandroid Backup.

•	Get and Install RSD Lite v4.9: There are reports of other versions working, but this one is what I have used.

•	Get and Install Motorola Drivers [32bits] [64bits]

Now to Business:

To Flash full SBFs, this is the standard procedure:

•	Open RSD Lite: Click on [ … ] Button and select your .SBF (Remember to rename to a short name and put it on root of your PC) and click Open.

•	Boot your phone into Bootloader Mode (check last section if you don’t know how to do it).

•	Now connect your Defy to your PC

•	The START button on RSD Lite should be available now, click and wait.

For Fixed SBFs a slightly different method is needed, is basically the same but you need to Wipe Dalvik Cache and Data before flashing. Then after flashing you need to enter inmidiatly to Recovery and restore the matching Nandroid Backup. I won’t write a specific way to do it here, since most of this version require different steps (for Example CM7 or MIUI), so is better so check for the guide for your Custom ROM, or specific Android version.

How do I enter to the Recovery?!:

With the Phone off press VOLUME DOWN then, while still pressed, power up the phone and leave VOL key pressed until you see a Yellow triangle, once you see this you are in Recovery now press Vol Up and Vol Down at the same time (if you are in Froyo) and the menu will appear.

How do I enter to the Bootloader:

With the Phone off press VOLUME UP, then while still pressed power up the phone. Keep the Vol key pressed until a black screen with some white letters appear. This is the Bootloader.
[Vibrant Q&A, Help & Troubleshooting] Tengis:
I just bricked my Vibrant trying to install one rom through Odin. I sent it off to get repaired and should have it back tomorrow.

Which rom should I be attempting to install? I use to install maybe 3-5 roms every time I was going to change or "upgrade" but that gets old.
[Vibrant Q&A, Help & Troubleshooting] sahil04:
I'm not sure with the 2.2.1 or 2.3 roms but with 2.2 you can't go wrong with Project V or Bionix.
[Vibrant Q&A, Help & Troubleshooting] G1toVibrant:
I gave up on GPS a long time ago, If I need a GPS, I use my Garmin :) if I am that lost anyway, I will be way out of TMobile range...

NextGenV2 by team whiskey rocks for me with the Bullet Kernel

I have recently swtiched to Simply Stock 2.3.5 ( JVT ) it is wicked fast!! if you follow the directions.. use the BG Bootloaders.. and put them on with Odin 1.85.. format your mounts on each flash ( the cache, system and data) you will be a ok...
[Vibrant Q&A, Help & Troubleshooting] boystuff:
hmm well if you managed to brick via odin to the point of having to get a replacement then i don't recommend any of the 2.3 roms based on Samsung since they all require a GB Bootloader for CWR and rainbow fixing.

Froyo recommendations are the same as what the prior posters said. as far as Gingerbread goes i recommend Miui there are currently 3 flavors in the development sub forum Revamped, & Lithium by Nick and his Production 360 Group, and Stock Miui

my easy to follow install guide for CM7/Miui

https://docs.google.com/document/d/14xGkh3BuU1OYR6eYY0XAk6BoRHsQAPWEHeVSJ1HcioI/edit?hl=en_US
[Vibrant Q&A, Help & Troubleshooting] nevrlow:
bionix v and the bali 1.8.8 kernel and ur good to go.
[Vibrant Q&A, Help & Troubleshooting] N00B_IN_N33D:
Miui *stock* (based on Android 2.3.5) in my opinion is the best. It's very easily customizable and updated every week! All you have to do is open the updater app to update, no need to fiddle with CWR and no PC necessary... You should at least try it, i'm sure you won't regret it.

Sent from my SGH-T959 (Samsung Vibrant)