yashsingh1/xdaforums huggingface dataset:
[EVO 4G Q&A, Help & Troubleshooting] jaejudah:
I got mine in eBay. Came with 2 ext. batteries & covers for $19.99

Sent from my SWAGGED OUT EVO
[EVO 4G Q&A, Help & Troubleshooting] dblkspecial:
Amazon. 2 ext batteries included for around 15
[EVO 4G Q&A, Help & Troubleshooting] BrImStOnE UnLeAsHeD:
http://www.amazon.com/gp/offer-list...rd_t=201&pf_rd_p=486539851&pf_rd_i=B003X26RTK
[Galaxy Tab General] Soundchasr:
I currently have a rooted Tab. If I update to GB will it screw up anything (other than unrooting)?

Original Samsung Galaxy Tab from Verizon gets Gingerbread update

Posted: 3 hours ago, by Alan F.Categories: Samsung, Android, TabletsBookmark

Share this page:Discuss2

Remember the original 7 inch Samsung Galaxy Tab? Verizon has given new blood to the ol' boy with a firmware update that gives the device a Gingerbread transfusion. The tablet was launched with Froyo installed and the update from Verizon adds some new features as well as Gingerbread functionality.

Android 2.3.5 is now on Verizon's Samsung Galaxy Tab

Besides receiving Android 2.3.5, the Verizon sold Samsung Galaxy Tab will also have improved word selection and copy functionality, improved security for the PIN method as when using the PIN on the device, you will no longer be asked to enter a symbol as a numeric entry and a "View Data Plan" icon will be available to let you adjust your plan. At the same time, a feature from Verizon Data Service gives you a real-time peek at the amount of data you have consumed for the month to make sure you don't go over your contracted amount.

Other new features coming with the OTA update are a download manager app, the ability to use the front-facing camera to record video, more accurate portrait and landscape re-sizing of widgets, support for Verizon's pre-paid service, and perhaps most importantly the update brings some security patches from Google.

Once you've allowed the update to proceed to the end, let us know what you think of the changes by dropping a comment in the box below!
[Galaxy Tab General] jason62082:
Please look at the search results when you post a new thread.

http://xdaforums.com/showthread.php?t=1328633
[Galaxy Tab General] Soundchasr:
Please delete.
[Galaxy Tab General] jpleez:
This thread was created first. So please look at the time stamps when responding in a thread.
[Galaxy Tab General] jason62082:
If you're going to call me out, at least be right....
[Android Software Development] swm5126:
To clear up some confusion and so I don't have to answer too many PMs, I'm going to add some details about how to get this to work.

First of all, grab mxt224.c, Kconfig, and Makefile from drivers/input/touchscreen/, and place them in your build folder in the same place.

Then do the same with mxt224.h, which is under include/linux/input/.

Go to arch/arm/mach-msm and grab my board-incrediblec.c. Compare it to whatever yours is (i.e. board-supersonic.c).

You'll need to change the name of the power init function for the touchscreen, and do something similar with the config data that I added to my init file. Make sure you scroll alllll the way down until you find the section about virtual keys. Make sure you change the name of "virtualkeys.atmel-touchscreen" to "virtualkeys.mxt224_ts_input" (I think thats correct, I'll check in a bit and correct if I'm wrong).

A note about the config data section for initializing the touchscreen:

I took the values from the original struct that was there from HTC, for my touchscreen revision. Normally, there are multiple hardware revisions of the touchscreen it seems, and upon booting, the kernel checks which one you have, and picks the correct one. I took this out since I was only trying to get it to work on my phone. Now that I know it works, I'm going to go back and readd the code to check the rev so it'll get the right config data.

This also means there's a good chance you need to copy the values from the original HTC init functions and put them into the struct I made. It can be a pain in the ass kind of, but it'll ensure your touchscreen works correctly. I want to note that mine worked fine with the actual Samsung values, but was kind of wonky.

Also, you'll have to edit your .config if you already have one. Go in there and put a big ol # in front of the line about atmel-touchscreen or whatever and save it. When you make your build it'll tell you about a great new driver that it found (surprise!) and ask if you want to enable it. Say yes, obviously. The first part is only important if you already have a .config or if your config wants to use atmel.c by default. Cause you don't. You ARENT using the HTC driver anymore. You want to use mxt224!

Sorry for being confusing, I'm not always the best at explaining things :(
[Android Software Development] swm5126:
Hey guys, I see this has about a thousand views. I'm not demanding a response but I'm curious if anyone else was able to get this working. If you did, please post!
[Android Software Development] twistedumbrella:
After porting the driver on Thunderbolt, I do get a log of the init, but there is no getevent data and it is currently unresponsive. I think it is related to my specific functions and the way they are translated, but in theory it does recognize the new driver.
[Android Software Development] swm5126:
Interesting...

Would you mind posting a logcat (from cold boot) and a dmesg dump?

Also, are you using the kernel on ICS or some other ROM? I found it helpful to test my kernel changes in CM7 until I got it working, only because I was more sure of what would work.

I'm actually trying to tweak the original HTC driver now to use the newer i2c_master_send method, which is proving somewhat difficult. It actually works using i2c_master_send instead of i2c_message, but its god awfully slow. I'm chalking that up to the ridiculous amount of i2c_writes (only 1 byte each!) the HTC driver wants to do individually to modify touch settings on the fly. I'm trying to see if there's a better way to do this and group them together to make less writes on the bus. The Samsung driver seems to do this pretty well...
[Android Software Development] twistedumbrella:
I really think HTC takes everything 1 byte at a time. Look at how many devices they have released and they are still using almost the same size battery they had in the G1. Anyway, back to the topic at hand.

For anyone else, here are the commands to get those files if you need to post them:

adb shell logcat -d > logcat.txt
adb shell dmesg > dmesg.txt

And mine are included with this post. I didn't try running it on CM7 because my daily driver is a Sense ROM. Even I don't understand why I run Sense when I use SPB launcher and disable most of the Sense features anyway.
[Android Software Development] OdiemanSAM:
I am working on porting it to the G2 but am having problems getting it to init. got the kernel to build, and boot but no joy with the ts... let me get the logcat and i will post

http://www.mediafire.com/?jpt3estxqxs4i - logcat and dmesg
[Android Software Development] Deleted member 4123551:
Is there any way to just edit the kernel and ROM instead of using the Source Code?
[Android Software Development] swm5126:
Looks like the touchscreen never actually gets to power on for some reason...probably something in your board init file I would think, but I'm not sure. Wish I had more devices to test this out on. If you can, I'd try the latest CM7 for the Tbolt, and grab the kernel from whoever maintains it and build that one and see if it works, since that's how I had success so far.

Sounds like you have about the same issue as twisted does. Try CM7 and adding it to the current kernel for your device, unless that's what you've already done.
[Android Software Development] OdiemanSAM:
I'm on CM7 and not sure what ts i have... the desire z/g2???? anyone... I tried changing it to the synaptics i2c rmi and the init file to synaptics_i2c_rmi_ts_input... is that right???

EDIT: I found it... it is synaptics-rmi-touchscreen
[Android Software Development] swm5126:
Well you have the Atmel maXTouch, just like the Incredible and many other HTC phones. You shouldn't need to change any files other than your board init file and adding the mxt224.c/.h to their respective directories. It's a little more than renaming functions in the board init file, by the way. And it should be mxt224_ts_input. The synaptics stuff doesn't relate to our phones, only the Nexus One, Desire, and maybe earlier models.
[Android Software Development] swm5126:
Uhh... well we are editing the kernel. That's what we're doing. You can't edit much of anything at all in a kernel once it's built, that's why I modified the source.
[Android Software Development] twistedumbrella:
I grabbed CM7 just after making that post. The kernel built for CM7 is a port from other devices, modified to work. The version I am using is a newer replacement CM7 kernel made from the source for the Tbolt. I am pretty sure the same results happened with the CM "port" kernel that was being tested.

I remember hearing about the issue when they ported gingerbread. Let me see if I can find the info.
[Android Software Development] OdiemanSAM:
ok so my init file is board-vision.c???? right??? what else do i need to change??? besides the virtualkeys.mxt224_ stuff????
[Android Software Development] swm5126:
I'd like to help out but you'll have to give me until later tonight or tomorrow. I'd like to see if I can get the HTC driver working in ICS with some changes, thus eliminating the confusion of getting the Samsung driver to work people seem to be having.

If its not possible to fix the HTC driver I'll post a step by step guide on how to apply what I've done with the Samsung driver to a kernel.
[Android Software Development] swm5126:
Ok. I actually just compiled the Tbolt kernel for someone else, I don't have the download link handy but I'll post it here in a few hours.
[Android Software Development] twistedumbrella:
Lol. **** you. Bust my *** and you just sneeze and make the thing. Haha. Thanks. I am curious what the difference was that I didn't catch. I will have to post my board c file if you want to take a glance at it, but the driver file should be exactly the same because I was comparing Incredible to Tbolt and the atmel config and such were word for work. The big difference was the init method. Everything else matched up.
[Android Software Development] swm5126:
Yeah didn't mean to make you do work for nothing, I had just done it for someone on a whim using a different source than you were using and I'm not sure if it worked or not yet.

He said it was working under CM7 for sure though, he just PMed me.

http://www.mediafire.com/?avcb4ev5k31indm
[Android Software Development] twistedumbrella:
I'll have to try it out against my setup. It is good I did it either way because I am sure more changes will be needed down the road. I just couldn't help giving you a hard time :)
[Android Software Development] twistedumbrella:
Didn't seem to work in ICS. No getevent data, and no touch response. Making sure I properly added in the zimage just in case, but it should be right.
[Android Software Development] swm5126:
Try it without any idc files if you have them in there, or any kcm or kl files for the touchscreen, a couple things I did seemed to break the touchscreen completely in ICS.

Can you send the logcat and dmesg log or post it?
[Android Software Development] twistedumbrella:
Dumped all idc, kcm, and kl files and here are the logs.

Looks the same as the kernel I was testing before...
[Android Software Development] swm5126:
Yeah it does, which is good. By that I mean its at least behaving the same. From the dmesg log, it looks like the touchscreen turns on and then immediately off. I'll take a look at the board init code in a bit and see if I can pin it down.
[Android Software Development] spaco22:
am no dev, but here to give Kudos to you all putting in your time

cheers
[Android Software Development] twistedumbrella:
That is the exact issue that post I read addressed. I am feverishly digging for it lol

Only problem is it may not be a kernel edit with what they recommend doing:

http://osdir.com/ml/android-porting/2011-01/msg00044.html
[Android Software Development] twistedumbrella:
I attempted to mod the power function to eliminate the integer check (which in theory should force it to always read as on if my logic is correct) and that didn't make a difference. I am trying again with a more drastic method of forcing it.
[Android Software Development] swm5126:
Thinking about that, I remember seeing warnings about the battery code whenever I compile for the Inc.

Take a look...

board-incrediblec.c

static struct htc_battery_platform_data htc_battery_pdev_data = {
/*	.gpio_mbat_in = INCREDIBLEC_GPIO_MBAT_IN,*/
/*	.gpio_mchg_en_n = INCREDIBLEC_GPIO_MCHG_EN_N,*/
/*	.gpio_iset = INCREDIBLEC_GPIO_ISET,*/
.guage_driver = GUAGE_MODEM,
.m2a_cable_detect = 1,
.charger = SWITCH_CHARGER,
};

board-mecha.c

static struct htc_battery_platform_data htc_battery_pdev_data = {
.guage_driver = GUAGE_MODEM,
.charger = SWITCH_CHARGER,
.m2a_cable_detect = 1,
.int_data.chg_int = MSM_GPIO_TO_INT(PM8058_GPIO_PM_TO_SYS(MECHA_GPIO_CHG_INT)),
};

Notice something commented out??
[Android Software Development] twistedumbrella:
Looks like it might be similar enough to the last line of the Mecha, but I am still refreshing my memory on C. It's only been about 3 years lol.

What I did was force all answers in the mxt power function to have the same result as on. I was also thinking I should double check my variables to make sure I was calling the right things. I will post it shortly
[Android Software Development] swm5126:
Nevermind, looking at the battery file it just looks like yours is giving the kernel the interrupt address to stop charging or something in the case of an overvoltage :/
[Android Software Development] twistedumbrella:
Nevermind. Placebo effect. Looks like it didn't do anything.

Just caught this line: <4>[ 11.778686] [lcm]mecha_init_panelpanel_type=9

Any relevance?
[Android Software Development] swm5126:
Interesting. I see what you're getting at. I'll admit I was a little lost on the power management thing earlier, but it looks like the Inc doesn't have one(a HW PM unit that is).
[Android Software Development] twistedumbrella:
Another long shot, but based on the way the other functions are configured I figured it was worth a try:

static int mxt224_power(int on)
{
printk(KERN_INFO "Atmel mxt224 interface (%d)\n", on);
if (on) {
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 0);
msleep(5);
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_GPIO_TP_UP_INT_N), 1);
msleep(5);
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 1);
msleep(40);
} else {
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_GPIO_TP_UP_INT_N), 0);
msleep(2);
}
return 0;
}
[Android Software Development] OdiemanSAM:
gonna get back to workin this afternoon, noticed this yesturday reading through all that code and tried this myself but changed a lot of other things too that threw hundreds of warnings and errors. i think mxt224.h and c need to be looked at too but i will read through later.
[Android Software Development] twistedumbrella:
Read through both mxt files, compared the atmel ones to the Incredible to make sure the same changes were relevant. Outside a few slightly more descriptive log messages, the atmel files were identical. This points to the same driver files being correct. What I am working on is making placeholder values for those two extra variables the Incredible has, which seem to match the values used by other drivers to kick start the enable process.
[Android Software Development] twistedumbrella:
Mecha:

static int mecha_ts_power(int on)
{
pr_info("%s: power %d\n", __func__, on);

if (on == 1) {
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 1);
} else if (on == 2) {
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 0);
msleep(5);
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 1);
msleep(40);
}

return 0;
}

Incredible:

static int mxt224_power(int on)
{
printk(KERN_INFO "Atmel mxt224 interface (%d)\n", on);
if (on) {
gpio_set_value(INCREDIBLEC_GPIO_TP_RST, 0);
msleep(5);
gpio_set_value(INCREDIBLEC_GPIO_TP_EN, 1);
msleep(5);
gpio_set_value(INCREDIBLEC_GPIO_TP_RST, 1);
msleep(40);
} else {
gpio_set_value(INCREDIBLEC_GPIO_TP_EN, 0);
msleep(2);
}
return 0;
}

So I searched for "INCREDIBLEC_GPIO_TP_EN" and ended up with:

gpio_direction_output(INCREDIBLEC_GPIO_TP_EN, 0);

but in mecha, that is:

gpio_direction_output(36, 0);

So, to fill in those missing values, I am currently attempting:

static int mxt224_power(int on)
{
printk(KERN_INFO "Atmel mxt224 interface (%d)\n", on);
if (on) {
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 0);
msleep(5);
gpio_set_value(36, 1);
msleep(5);
gpio_set_value(PM8058_GPIO_PM_TO_SYS(MECHA_TP_RSTz), 1);
msleep(40);
} else {
gpio_set_value(36, 0);
msleep(2);
}
return 0;
}
[Android Software Development] swm5126:
Ok. Well.

http://xdaforums.com/showthread.php?p=19047963
[Android Software Development] twistedumbrella:
Yeah, well my idea was good too haha

SOAB! I had the mxt driver set to module... WTF!
[Android Software Development] swm5126:
Didn't mean to say it wasn't! :) I'm just shocked that it was so simple that's all :(
[Android Software Development] twistedumbrella:
Well either way it is good you found it or I would have never even noticed that I set the mxt224 driver to M and missed the second select to *

I can't believe I was oblivious to that. Of course it never launched. It was missing the module... wow. I feel dumb, lol.
[Android Software Development] OdiemanSAM:
Me too... i feel very dumb. Thanks guys, building the G2 version now. LETS HOPE VISION NATION!!!
[Android Software Development] DroidRC1:
Anybody working on a Sensation build?
[Galaxy Note GT-N7000 General] Techvir:
Today i got Gnote and realised that it has the same touch screen sensitivity issue as galaxy s2. Minor issue but an issue

If u dont understand by what i mean

http://www.youtube.com/watch?v=sRXcBcpSD1w

Here is the orignal thread.

http://xdaforums.com/showthread.php?t=1161262

I did not do anything

Just download the app from there and run it.

It solved for me.
[Galaxy Note GT-N7000 General] Niuseek:
Does it work for S-pen writing some memos as well? It would be serious improvement if that's the case.
[Galaxy Note GT-N7000 General] Techvir:
mmmm.. WIll have to test that out.
[Galaxy Note GT-N7000 General] kersh:
S-pen doesn't have that problem

And the patch doesn't work in the note.
[Galaxy Note GT-N7000 General] Sharpshooterrr:
Are there others who are experiencing this problem on their Note?
[Galaxy Note GT-N7000 General] aussiebum:
No. I've been doing pinch-zoom's in Gallery (which was where I noticed it from the SGS2) and don't notice any delays in finger recognition.
[Galaxy Note GT-N7000 General] Sharpshooterrr:
Alright that's good to hear. The problem might not affect all handsets.
[Galaxy Note GT-N7000 General] ephestione:
Confirm the problem is there and even the app doesn't solve this, but I didn't really notice. S-pen in SMemo doesn't seem to be affected, but reducing to 0 the hyst still gives the "sticky" behaviour, which maye, or may not, be a con depending on the various uses.
[Galaxy Note GT-N7000 General] mfractal:
so the way to confirm the problem if i understand correctly is to install the mentioned app and test for jumps in coordinates ?
[Galaxy Note GT-N7000 General] djbattlecry:
Gnote

I have had my Gnote for 25 days, my device is way to sensative in certain areas of the screen with the S-pen only. i can hold my S-pen 10mm away from the screen and it will activate the apps or words. it gets annoying when im on a rush taking notes, it sometimes quadruple clicks on apps, i stop using my S-pen and get my screen dirty with natural oil smudges. Kinda Lame. Any way i am going to AT&T today to test a different S-Pen, or switch Devices.... Does anyone like the White GNote Vs. Black/ or blue?
[Wing, P4350 Herald Upgrading] Ursuletz22:
Hi,I`m new user on this forum so if I posted wrong please excuse me.

My problem is that i`ve got a herald with italian language,and I tried to flash a new rom on it and while flashing something got wrong and now it`s stuck in bootloader and appears IPL 1.08.0001 and SPL 1.08.0001.Can you please help me?I`ve searched the internet for 6 hours and i`ve found nothing.:(please help me:o
[Wing, P4350 Herald Upgrading] Hakim Rahman:
try to flash rom again with official rom ~ ftp://xda:xda@ftp.xda-developers.com/Uploads/Herald/Official%20WM6%20roms/
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
Hi All,

I tried to flash my friends i9100 (it had arabic 2.3.4 firmware, but i didn't write down the exact firmware number), to I9100JPKI1 2.3.5 1 file update. But it gave "FAIL" result in ODIN. After that phone got stuck on Download screen. I removed battery and restarted the phone. And after it got stuck on the following screen (pic at the end of post)

I tried to flash it again by odin but it's not flashing (Attached pic of ODIN after unsuccessful flash below). Any ideas how to restore the phone?
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
it seems connectivity problem. Have you tried another USB or another USB cable?
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
Yes, tried different cables on different computers. The phone is booting with this phone-warning triangle-computer logo immediately. Even samsung logo is not coming before it.
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
Are you able to access recovery mode? If yes, try to do a full wipe.

EDIT: Try to Kill all process of Kies, and see if Odin recognize your phone
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
No, it's stuck on this screen. i can't put it in Download mode. Even if i start it: Volume Down+Home+Power this screen is coming.

ODIN can't recognize the phone.
[Galaxy S II Q&A, Help & Troubleshooting] meranto:
Ouch, I see repartition and a PIT file, that usually means the phone is really dead; a job for the service centre.

Which guide did you use?
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
Maybe some file are corrupted. Try to follow these steps:

[READ THIS] Got a Boot Loop? Don't post a New Thread!

[ROM+Guide]Official i9100 Firmwares KG, KH1/2/3/4, KI1/2/3/4/8, KJ1/2 Download
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
On the first flashing (after which it became like this) i didn't do repartitioning and didn't use PIT file. Just selected PDA file.
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
I didn't see that...maybe only service center can do this job
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
I tried to follow following guide: http://xdaforums.com/showthread.php?t=1108499.

Did

1) Turn off your phone. Unplug it from your computer etc

2) Hold down home, power, and volume UP. This will enter recovery mode. If you are using CF-Root, you'll get CWM recovery. If not, you get stock recovery. It doesn't matter which appears.

BUT phone is not going into recovery mode.
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
I think that you need to leave the phone to Service Center.
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
The thing is that the phone was bought in another country, so there is no warranty in my country for it. That's why i'm searching for solution myself.
[Galaxy S II Q&A, Help & Troubleshooting] marcelotorres:
I had a problem weeks ago with my phone too. Tried a lot of things and nothing fix the problem. But when i was losing hope, i found the solution by myself.

My problem was only IMEI number and i recovered it. I think that your best choice is read a lot before take some decision. And the most recommended choice is leave the phone to Service center.

Good luck!
[Galaxy S II Q&A, Help & Troubleshooting] limon11:
Maybe JIG will be useful to put the phone into DOWNLOAD mode?

P.S. : I am keeping going to Service Centre options as a last resort.