yashsingh1/xdaforums huggingface dataset:
[Barnes & Noble Nook Tablet] succulent:
Wow, this thing really work. This should be on frontpage of XDA. Thanks mik_os, kuzma!

My instructions.

WARNING!!!

Updating your Nook Tablet touchscreen firmware required new multi-touch driver in the kernel.

If you run stock OS/cm7/cm9/10, it will mess up your touchscreen without the new multi-touch driver in the kernel.

You will need a new kernel with the new multi-touch driver.

I am providing the SDCard boot version of Chris's cm10-acclaim-0.06.1.

http://www.mediafire.com/?9m7evrr50a4mecz

Here's a flashable boot.img with the new multi-touch driver for chrmhoffmann's CM10 "Jelly Bean" 0.06.1 internal.

I haven't test the file because I run CM10 on SDCard and not internal.

Just beware, if you are using TWRP (I haven't use it, but cwm with touch based also required new kernel)

You need to update your touchscreen firmware before flashing the new boot.img with cwm.

http://www.mediafire.com/?689faxgu45wet6q

Don't do this if you do not know what you are doing. It will cripple your device.

Place 'ft5406-sc3052-1024X768.bin' into /system/etc/firmware and /system/lib/firmware (I know it belong to one of the two locations)

Copy updatefw.sh to your SDCard.

Open terminal.

Type:

~: su

~: cd sdcard

~: sh updatefw.sh

Notice "VENDORID=", if it's just "VENDORID=" or "VENDORID=00", you need to repeat "sh updatefw.sh" until it's "VENDORID=0xCD" (Might require 7-20 times).

Notice "TPFWVER=" changes from "TPFWVER=13" or "TPFWVER=14" to "TPFWVER=0B".

updatefw.sh

#!/bin/sh
echo Starting
WINTEKPANEL=1
FILENAME="ft5406-sc3052-1024X768.bin"
NEWFWVER=0B

echo "0xa8" > /sys/bus/i2c/devices/2-0038/wmreg

FWID=`cat /sys/bus/i2c/devices/2-0038/wmval`
echo "FWID=$FWID"

VENDORID=`cat /sys/bus/i2c/devices/2-0038/vendorid`
echo "VENDORID=$VENDORID"

if [ "$VENDORID" = '' ]; then
echo "VendorID error!"
exit 0
fi

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`
echo "TPFWVER=$TPFWVER"

echo "Update firmware using $FILENAME from version $TPFWVER"
echo "$FILENAME" > /sys/bus/i2c/devices/2-0038/fwupdate
cat /sys/bus/i2c/devices/2-0038/calibrate
cat /sys/bus/i2c/devices/2-0038/storecalibrateflash

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`

if [ "$TPFWVER" = "$NEWFWVER" ]; then
echo "Update to $TPFWVER success!"
else
echo "Update fail! Try again!"
exit 1
fi
[Barnes & Noble Nook Tablet] nashdude:
Not brave enough to update my kernel on my lonesome, but I'm definitely excited about where this might lead :)
[Barnes & Noble Nook Tablet] succulent:
[FONT=&quot]I tried to use the driver with 2.6.x kernel and CM7 boot[/FONT][FONT=&quot]ed[/FONT][FONT=&quot] with lighted-black screen. I use logcat and can see things are running in the background, but the screen isn't [/FONT][FONT=&quot]displaying anything[/FONT][FONT=&quot].

I updated the firmware in CM7[/FONT][FONT=&quot] and s[/FONT][FONT=&quot]o far, I have zero luck downgrading to previous firmware in CM7 and CM10. I even changed the script to have a while loop to make updating the firmware easier.

[/FONT]

[FONT=&quot][/FONT][FONT=&quot][/FONT]

[FONT=&quot]I was thinking of ways to impleme[/FONT][FONT=&quot]nt the firmware when you install rom. All I can come up with is have the firmware installed with the rom and the script run on init. The hard part is that you need a loop in the script and there’s a potential infinite loop if the firmware doesn’t get updated.[/FONT]

[FONT=&quot]

[/FONT]

[FONT=&quot]My advice to people who want to try this is once you update the firmware, you might be stuck with CM9/CM10. No more stock OS or CM7 so think carefully. The firmware allow[/FONT][FONT=&quot]ed[/FONT][FONT=&quot] up to 5[/FONT][FONT=&quot] [/FONT][FONT=&quot]touches and it's awesome but there are sacrifices.[/FONT][FONT=&quot] This will create problem with dual-booting.[/FONT]
[Barnes & Noble Nook Tablet] Vector2nds:
Will this driver work on 25/10 rom or is specifically made for Chris 6.1?
[Barnes & Noble Nook Tablet] Kuzma30:
If you update kernel for 25/10 ROM, then yes it will work
[Barnes & Noble Nook Tablet] ShinnAsuka:
so this multi touch driver works for any cm10 rom? and you need to do the updatefw.sh first before flashing the newboot.img if you are doing this for internal/emmc?

awesome progress on this device!
[Barnes & Noble Nook Tablet] Demetris:
Of course you have to flash the firmware first.
[Barnes & Noble Nook Tablet] ShinnAsuka:
will you be including this multi touch driver in your next update of the roms you released?
[Barnes & Noble Nook Tablet] Demetris:
All ROMs will be updated to be 5 touch firmware enabled.
[Barnes & Noble Nook Tablet] ShinnAsuka:
well i shall be patient then. thanks for the reply!
[Barnes & Noble Nook Tablet] ryan.nguyentran:
I use This ROM

And then

Place 'ft5406-sc3052-1024X768.bin' into /system/etc/firmware and /system/lib/firmware (I know it belong to one of the two locations)

Copy updatefw.sh to your SDCard.

Open terminal.

Type:

~: su

~: cd sdcard

~: sh updatefw.sh

Result

Starting

FWID=0x79

VENDORID=0xCD

TPFWVER=13

Update firmware using ft5406-sc3052-1024X768.bin from version 13

6 6 6 6 7 5 4 6 7 4 8 6 9 5 6 6

Update fail! Try again!

:(
[Barnes & Noble Nook Tablet] Demetris:
Go here for an easy ride :)

http://xdaforums.com/showthread.php?t=1966894
[Barnes & Noble Nook Tablet] ShinnAsuka:
shouldn't this firmware upgrade work with any cm10 rom? or would it just be safer to use it with chris's cm10 releases?
[Barnes & Noble Nook Tablet] Demetris:
Eeprom firmware updating in cm10 branch is broken.
[Barnes & Noble Nook Tablet] chrmhoffmann:
Unresponsiveness in games fixed?

Hi all,

Does this new driver and FW fix the unresponsive games issue (aka "Temple Run" bug)?

Rgds,

Chris

PS: Install Temple Run game and see that it doesn't react to touchscreen interactions.
[Barnes & Noble Nook Tablet] tonyp23:
Indeed it does! :D
[Barnes & Noble Nook Tablet] chrmhoffmann:
Is it the FW or the new driver that fixes this, or both?

Chris
[Barnes & Noble Nook Tablet] tonyp23:
Combination. When using the new driver with old FW, you get a mirrored touchscreen. As soon as you flash the new FW, works beautifully.
[Barnes & Noble Nook Tablet] mik_os:
Driver.

It can be configured in board-acclaim.c so you can use new driver with old firmware. And I think it will be possible to detect firmware and set correct mirroring flags in runtime. I'll work in this way at weekend.
[Barnes & Noble Nook Tablet] chrmhoffmann:
Hi,

i am not able to flash new firmware...

<6>[ 195.088470] ft5x06_perform_fw_upgrade() - Step 1: Reset the CTPM

<6>[ 195.095275] ft5x06_enter_fwupdate_mode() - Step 1: Reset the CTPM

<6>[ 195.204986] ft5x06_enter_fwupdate_mode() - Step 2: Put the CTPM in Firmware Upgrade mode

<6>[ 195.228698] ft5x06_perform_fw_upgrade() - Step 3: Read the CTPM ID

<3>[ 195.259948] ft5x06_perform_fw_upgrade() - ERROR: Invalid CPTM ID. Expected 0x7903, got 0x0000.

<6>[ 195.269653] ft5x06_perform_fw_upgrade() - Step 8: Reset the CTPM

<7>[ 195.276367] ft5x06_reset_panel_via_gpio() - Toggling GPIO 39 to reset the Touch Panel...

<6>[ 195.657257] ft5x06_perform_fw_upgrade() - FIRMWARE UPDATE COMPLETE - Update Failed

<3>[ 195.665832] ft5x06_fwupdate_store() - ERROR: Could not update the firmware using 'ft5406-sc3052-1024X768.bin'

I tried quite a few times with kernel 3.0.31+....

Chris
[Barnes & Noble Nook Tablet] slgooding:
I was finally able to flash the firmware using the instructions in the second post here: http://xdaforums.com/showthread.php?p=33563513#post33563513

It took about 7 attempts.

On a different topic, I noticed that the new firmware still has the pixel delay during swipes. I have to swipe 8 or so pixels before it actually picks up the movement. This makes it impossible to do any effective stylus writing, etc.

Are there any plans to get rid of this pixel delay? For me that is a much bigger deal than 5 touches.

Thanks!
[Barnes & Noble Nook Tablet] tonyp23:
AFAIK, no one has been able to flash on one of the CM10 Kernels. To get around this, we've been flashing a CM9 kernel (from your 0.05.3.1 CM9 build) and then update the FW. Then re-flashing the CM10 kernel.
[Barnes & Noble Nook Tablet] Vector2nds:
I need new reading glasses.

Ok, I tried the "[ROM][WIP]CM10 with SGT7 cpuidle and 5-Touch ONLY + firmware update instructions" and it works with the "cm-10-20121031-UNOFFICIAL-acclaim.zip" rom after the cm9 "Touch Firmware Update ROM.zip". Tested already with multi-touch free app. My understanding is that this is a firmware update so if I was to wipe clean and install 25/10 back on then it would function normally. Sadly I thought this was the case until read read the bold lettering in the "[ROM][WIP]CM10 with SGT7 cpuidle and 5-Touch ONLY + firmware update instructions" saying "This will only work with an updated touch firmware. Please see second post for information on how to proceed with that.

Once you upgrade the firmware, until we find a solution to downgrade, you are on that firmware which means you have to use a 5-touch enabled ROM":crying: Couldn't even select reboot on 25/10. I'll wait till 7/11 rom come out with enable 5-Touch and go get a slirpy for now.:silly:
[Barnes & Noble Nook Tablet] mik_os:
Downgrading is simple like upgrading. But only with old kernel. You can use this boot.img. This kernel work for me, upgrading firmwares works from first try. Until we fix current kernel you can use this one.
[Barnes & Noble Nook Tablet] mik_os:
Finished with firmware detection in runtime: https://github.com/Kuzma30/kernel3NookTablet/commit/fc3e3e2bc3673f76688af1cd9b1b0fe31e0b7fb6

It's comfort to use new driver on all firmwares now.
[Barnes & Noble Nook Tablet] Zippy Dufus:
So, if I build a new ROM from scratch with your's and Kuzma30's new (Nov 4) commits, will I be getting this new driver?

Any danger here? :cowboy:

--- Update ---

Built a new ROM and it is working well except for that pesky SDcard unmount bug during deep sleep when WIFI is left on.

I'm not using the new multitouch driver yet. One finger is good enough for me to check my email.
[Barnes & Noble Nook Tablet] succulent:
I have finalized two CM9 builds (based on Chris's cm9) with auto firmware update/restore. All you have to do is flash the rom and run it once. The firmware will update/restore by itself. You will know if the firmware is updated when android load to the home screen and the touchscreen isn’t working. At that point you have to hold the power button until the device power off. Then you can flash a 5-touchs firmware rom. Conversely, you will know the firmware have restored when the touchscreen is mirrored.

cm-9-20120815-acclaim-updatefw.zip

http://www.mediafire.com/?7fol53zr6wasbww

cm-9-20120815-acclaim-restorefw.zip

http://www.mediafire.com/?qtovu99xqrajfq9

I’ve included both updatefw.sh and restorefw.sh script in the rom as well as the firmwares. You can run the script from either rom if you want. Scripts are located in /system/bin/updatefw.sh and /system/bin/restorefw.sh.

updated updatefw.sh

#!/bin/sh
echo Starting

WINTEKPANEL=1
FILENAME="ft5406-sc3052-1024X768.bin"
NEWFWVER="0B"
VARX=1

echo "0x00" > /sys/bus/i2c/devices/2-0038/wmreg

FWID=`cat /sys/bus/i2c/devices/2-0038/wmval`
echo "FWID=$FWID"

VENDORID=`cat /sys/bus/i2c/devices/2-0038/vendorid`
echo "VENDORID=$VENDORID"

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`
echo "TPFWVER=$TPFWVER"

echo "Update firmware using $FILENAME from version $TPFWVER"
while
do
if [ "$TPFWVER" = "$NEWFWVER" ]; then
echo "Firmware updated!"
exit
else
echo "Firmware failed to update! $VARX"
if [ "$VARX" = "20" ]; then
exit
fi
fi
echo "$FILENAME" > /sys/bus/i2c/devices/2-0038/fwupdate

cat /sys/bus/i2c/devices/2-0038/calibrate
cat /sys/bus/i2c/devices/2-0038/storecalibrateflash

VENDORID=`cat /sys/bus/i2c/devices/2-0038/vendorid`
echo "VENDORID=$VENDORID"

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`
echo "TPFWVER=$TPFWVER"

VARX=$((VARX+1))
done
exit

restorefw.sh

#!/bin/sh
echo Starting

WINTEKPANEL=1
FILENAME="FTS0019U700_Ver14_app.bin"
NEWFWVER="14"
VARX=1

echo "0x00" > /sys/bus/i2c/devices/2-0038/wmreg

FWID=`cat /sys/bus/i2c/devices/2-0038/wmval`
echo "FWID=$FWID"

VENDORID=`cat /sys/bus/i2c/devices/2-0038/vendorid`
echo "VENDORID=$VENDORID"

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`
echo "TPFWVER=$TPFWVER"

echo "Update firmware using $FILENAME from version $TPFWVER"
while
do
if [ "$TPFWVER" = "$NEWFWVER" ]; then
echo "Firmware updated!"
exit
else
echo "Firmware failed to update! $VARX"
if [ "$VARX" = "20" ]; then
exit
fi
fi
echo "$FILENAME" > /sys/bus/i2c/devices/2-0038/fwupdate

cat /sys/bus/i2c/devices/2-0038/calibrate
cat /sys/bus/i2c/devices/2-0038/storecalibrateflash

VENDORID=`cat /sys/bus/i2c/devices/2-0038/vendorid`
echo "VENDORID=$VENDORID"

TPFWVER=`cat /sys/bus/i2c/devices/2-0038/tpfwver`
echo "TPFWVER=$TPFWVER"

VARX=$((VARX+1))
done
exit
[Barnes & Noble Nook Tablet] chrmhoffmann:
choppy scrolling

Hi,

does the new fw/driver also fix the "choppy" scrolling issue? E.g. in web browser, it seems to always scroll a few lines at a time?

Rgds,

Chris
[Barnes & Noble Nook Tablet] C64assembly:
Hi Chris! I don't notice the choppy scrolling issue in the SGT7 5 finger touch variants.

Regards, Bruce.
[Barnes & Noble Nook Tablet] mik_os:
Yes, it does. Thats was the firmware issue. At this firmware accuracy is 1px.
[Barnes & Noble Nook Tablet] Demetris:
Yes
[Barnes & Noble Nook Tablet] Kuzma30:
driver issues or JB option

But when you make first touch you need move 5-8 px to start scrolling,

(After the first contact to Screen need to hold your finger about 5-8 pixels, the image began to move. This situation not only in the browser, but in the graph editor, too. When the "Show pressed" and "Show Touch" system "catches" the slightest movement)
[Barnes & Noble Nook Tablet] mik_os:
Это специфика определения направления скролинга: скроллинг не начнется до тех пор пока в горизонтальном или вертикальном направлении палец не будет сдвинуть на определенное расстояние. Иначе будет много срабатываний в ложных направлениях. Это только в приложениях где важно направление.
[Barnes & Noble Nook Tablet] AvRS:
Sorry guys not to be a pain but as per the rules, if you're going to write in other languages a full English translation must be also added for the benefit of all.

Thanks

AvRS
[Barnes & Noble Nook Tablet] Demetris:
Kuzma:

(After the first contact to Screen need to hold your finger about 5-8 pixels, the image began to move. This situation not only in the browser, but in the graph editor, too. When the "Show pressed" and "Show Touch" system "catches" the slightest movement)

Answer By Mik_os:

This specificity determining direction scrolling: scrolling does not begin until the horizontal or vertical direction finger will not move a certain distance. Otherwise there will be a lot of positives in the wrong direction. It is only in applications where it is important direction.
[Barnes & Noble Nook Tablet] chrmhoffmann:
It works really well now. Thank you.

Chris
[Barnes & Noble Nook Tablet] plantucha:
Most of development for nook tablet is done by Europeans. Rebellos -Poland, Kuzma and mikos - Ukraine, demetris - greece, webceltic - welsh. BN don't even sell nook tablet in Europe. You can be happy they actually post anything in English and on xda. Use Google translate if you must.
[Barnes & Noble Nook Tablet] hungmung:
Actually it's an xda rule that anything in other languages must have a translation it's not just him making a request.

Sent via moon rays...
[Barnes & Noble Nook Tablet] succulent:
It's just easier to implement.

I have another idea that require cyanoboot to boot into internal altboot (recovery.img disguised as altboot.img located on the rom partition) and then flash a zip that run the update/restore script. That recovery image would required the kernel that allowed firmware updating/restoring but I don't have it.
[Barnes & Noble Nook Tablet] skyward01:
Can I install this with TWRP, or does it need to be CWM? The reason I ask is I'm not sure how to touch screen mod will affect touch recoveries? Thanks.

Sent from my Galaxy SIII
[Barnes & Noble Nook Tablet] spcagigas:
You can install Succulent's firmwareupdate ROM from TWRP, but after that TWRP won't work. I found out the hard way/dumb way...

Also, TWRP doesn't like flashing a new recovery over itself... The easiest thing to do is to flash CWM6+ to emmc using an SD-based recovery image, then use that to install Succulent's firmware, followed by your preferred 5-touch enabled ROM...
[Barnes & Noble Nook Tablet] Kuzma30:
Ahtung!

10 point multi-touch working on NT.

https://github.com/Kuzma30/kernel3NookTablet/commit/9da5fade51895577cf09414021d148a72caa9572
[Barnes & Noble Nook Tablet] mik_os:
And I am working at android application for 1-click touch firmware flashing. It is almost ready :)
[Barnes & Noble Nook Tablet] succulent:
Tested the new driver. It fixed the ShadowGun problem. :good:
[Barnes & Noble Nook Tablet] comat0se:
Awesome work everyone... I now have 10 touch on my NT.
[Barnes & Noble Nook Tablet] jotekman:
Hi. I have a small problem. I have the 5 touch firmware, but I am soft-bricked and need to reset the tablet... from the beginning. I would think that if I begin the regular restore process, I would be permanently bricked because I couldn't use the touchscreen, so I will have to restore the firmware first. The only way to do this would be, I would guess, and SD bootable version of the Restore CM9.

Is this possible? I have been searching, but I cannot figure out a way to do it. Could someone point me in the right direction with steps on how to make that SD bootable? Or, if it is more complicated, perhaps (I cringe to ask) let me know if it is possible to build one?

With the proliferation of the new firmware, this issue may come up more and more often, so it might be a good idea to have.......

Please let me know though..... would a complete restore with (i think it was his) adamoutlers repartitioning stock sd card work? I think no, but I may be wrong. I couldn't imagine that the restore would also flash the touchscreen firmware....

Also, I found a CM10 SD version, which I haven't tried yet, but is it possible to just take the flasher app and use it with that?

If so, where can I find the app (looked and read all posts, but missed it somehow.)

I appreciate any help someone can give me.
[Barnes & Noble Nook Tablet] digixmax:
The simplest way is to download the CM10 SD image from http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/ and burn it to SD, then boot up from the card, once inside CM10 you'll find the app to flash the touchscreen FW back to 2-touch.

The much more tedious (but now unnecessary) way is to make a bootable CM9 SD from scratch using cm-9-20120815-acclaim-restorefw.zip from the same site. (I had to do this because the first alternative didn't exist at the time I had this same problem you do).
[Barnes & Noble Nook Tablet] Sovik62:
Touch problem!

There are two plate-like MX913DC. With one all right. The other, before it was found the firmware, flash a different firmware on selection. Touch screen is rotated on the x axis. Is there a way to upload the firmware from a working touchscreen tablet. Maybe it will help a lot.
[Barnes & Noble Nook Tablet] Sovik62:
Touch problem!

I've tried all the methods. The problem probably is that it only works on the platform of the A10. I have a platform A13. Motherboard KB901v3. Touchscreen chip FT5406EE8. I am glad that the second tablet fully working. We need a tool to download a working version of the firmware from its touchscreen.
[Barnes & Noble Nook Tablet] Kuzma30:
There is no tools for downloading firmware from device.
[Barnes & Noble Nook Tablet] Pepe.II:
Hello, one little question for multitouch driver developers.

Is possible to compile 10point touch driver with 2.6 (cm7.2) kernel?

My nook is switched to 10point and i need sometimes boot to CM7.2 from sd card. Flashing back to original 2point firmware and back and again and again is little bit uncomfortable.

I will be grateful for any help.

Thanks
[Barnes & Noble Nook Tablet] Narga:
I don't know why it's happened. Since 2 days ago, I can't touch to a dead zone alongside of top screen. I've flashed 2 touch and 5 touch firmware but it's cannot recover. I installed Nook screen recalibrate from Play Store then running and the results is the same.

I'm running CM 10.1 07 May build (installed from the first released of that Rom)

Is my Nook screen dead or the problem is firmware?

The size of deadline just about 2/3 inches with full width of top screen and has 1/5 inch from the edge
[Barnes & Noble Nook Tablet] ndnghia:
Me too, I met this issue two months ago. Try to flash to stock 1.4.2 but it still happen. 5 touchs didn't work too. It can only recognize up to 4 touchs.
[Barnes & Noble Nook Tablet] Narga:
Thanks, I like your reply. That's mean the problem is firmware. I'm searching about that now
[Barnes & Noble Nook Tablet] Narga:
I've used an app to test the surface screen then it is telling me that the surface size is 1024x546, the screen is perfectly without any dead pixel, wrong color or another problem.

I guess the problem is software?
[Barnes & Noble Nook Tablet] daedricgeek:
I had a similar problem since about a month after flashing 10 touch. The lower 1/5 of my screen is not responsive to touch. And I get only 4 touch.

Tried flashing back to 2 touch (didn't work) and again 10 touch (still doesn't work).

Tried several ROM's since then - cm10 - sgt7 , CM 10, 10.1, PAC, aokp.

Currently using pac with smart rotate apk as a workaround.
[Barnes & Noble Nook Tablet] Narga:
I've total reflash and format all the partition with Ubuntu SD card in sticky topic then reflash stock rom and other but this issue stull the same. I don't think reflash ROM will change touch firmware.

Plz help us or tell us how to change the firmware
[Barnes & Noble Nook Tablet] ndnghia:
Which app did you use to test?

I need to check my screen too.
[Barnes & Noble Nook Tablet] Narga:
You can try Display Tester on Play Store. Here is mine
[Barnes & Noble Nook Tablet] KOBOL:
hello. i have irulu al006 i flash new firmware on it and touch stop working. i see on board, touch ic is ft5202

lsmod

mxc622x 4708 1 - Live 0xbf097000

mecs 3776 1 - Live 0xbf093000

rtl8150 8910 0 - Live 0xbf08c000

mcs7830 6557 0 - Live 0xbf086000

qf9700 8513 0 - Live 0xbf07f000

asix 22500 0 - Live 0xbf074000

usbnet 23745 3 mcs7830,qf9700,asix, Live 0xbf068000

sun4i_csi0 26905 0 - Live 0xbf05d000

gc0308 14208 1 - Live 0xbf055000

videobuf_dma_contig 5659 1 sun4i_csi0, Live 0xbf050000

videobuf_core 18067 2 sun4i_csi0,videobuf_dma_contig, Live 0xbf046000

mali 130019 4 - Live 0xbf019000

ump 41954 9 mali, Live 0xbf008000

goodix_touch 12453 0 - Live 0xbf000000

if i make insmod command

insmod /system/vendor/modules/ft5x_ts.ko

insmod: init_module '/system/vendor/modules/ft5x_ts.ko' failed (Operation not pe

rmitted)
[Samsung Epic 4G Touch] kenfly:
Who's got the best 3g speed with their modem. I'm on the new modem that is with the leaked Sprint build of ics signal is better but internet is dragging balls.
[Samsung Epic 4G Touch] rwilco12:
I've had the most luck with EL29 modem.
[Samsung Epic 4G Touch] kenfly:
I am on el26. I'll try that. I just wanted to see if someone actually tested Al of them to see what differences there are.
[Samsung Epic 4G Touch] dw3bb10:
Im partial to EK02 right now.
[Samsung Epic 4G Touch] rwilco12:
Yeah I've run pretty much all of them (with the exceptions of FD19 and FD26). I had some decent ratings on FB27, FC05 and FD10 but EL29 always gave me the best.
[Samsung Epic 4G Touch] brysg2:
I've had the best of luck on EL29 as well. Which isn't saying much however as the speeds are still MEH for me.
[Samsung Epic 4G Touch] frankquattrone:
People will tell you every phone is different and you have to try them all but I really don't see how that could possibly be the case. There would have to be some serious quality control issues in Samsung's production line for that to happen. All of that said, I did try a whole bunch of them (EL29, FB, FC, FD) in one sitting to try to get as close to an apples to apples comparison as possible. EL29 came out the winner for me too.