iCan provides "official" upgrade to their Flytouch II clone

sharpe351

Member
Jul 2, 2011
337
8
Unfortunately, NONE of the firmware/updates do anything to affect the Wi-Fi issues reported by all of the infoTMIC powered devices. There is ongoing work to create custom images to address the issues since a timely update is not expected from infoTMIC. All of the suppliers are reliant on infoTMIC fixing the issues and it's becoming obvious they're all struggling with infoTMIC to provide an "official" update. Many users are reporting returning their tablets only to get a refurbished one with the same or worse issues. Also reported that many if not all of the "fixes" may or may not work given your environment (router, B/G/N, encryption, distance). Those of us with fairly stable Wi-Fi count ourselves as lucky because there are so many reports of user complaints. Only advice is to keep trying to different Wi-Fi configurations until an "official" or custom update is released.

Indeed. Mine has gotten better since I replaced the Router. I guess I fall into the fairly stable category. I have a method that works and I use it. Its just aggravating to have to fart with it all the time. I suspected the U0 was the fault but I wasn't completely sure. Thanks for the info.

Sent from a rooted SuperPAD clone with Android 2.2 :p
 

sharpe351

Member
Jul 2, 2011
337
8
Is there a way to pull the U0 off my machine so it may be decifered and used to help others with their devices? Mine seems to have a pretty high update number for the uboot nand file. Do you think this would help?

Sent from a rooted SuperPAD clone with Android 2.2 :p
 

leeb

Member
Jul 16, 2011
463
21
Pre-update (waiting to hear if camera and other things work).
Model number: SAWEE Pad
Firmware version: 2.1-update1 V2.2:#3245
Baseband version: unknown
Kernel version: 2.6.32.9 infotm-sqa@infotm-sqa-desktop #57
Build number: ERE27

But iCan shows at least two models on their website (variances associated with the Home key is all I can see), associated with this update, so presumably care has to be taken there as well.

Trying Micro$haft's "Virtual PC" to see if I can run the update from 32bit WinXP inside 64bit Win7...

[EDIT: NOte the update to the first post...]

Your specs are exactly what I had before I started... so Im downloading the Ican upgrade...
Will come back here and report on details of success (or lack thereof).

:D
 
Last edited:

cfrockit

Senior Member
Dec 26, 2010
627
191
build.prop - V2655 - ICANV2655.ius
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF85B
ro.build.display.id=FRF85B
ro.build.version.incremental=[B]eng.leo.20110311.204810[/B]
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=[B]2011年 03月 11日 星期五 20:52:43 CST[/B]
ro.build.date.utc=1299847963
ro.build.type=user
ro.build.user=leo
ro.build.host=leo-desktop
ro.build.tags=test-keys
ro.product.model=[B]wwe10[/B]
ro.product.brand=generic
ro.product.name=wwe10
ro.product.device=wwe10
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=imap210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wwe10
# Do not try to parse ro.build.description or .fingerprint
[B]ro.build.description=wwe10-user 2.2 FRF85B eng.leo.20110311.204810 test-keys
ro.build.fingerprint=generic/wwe10/wwe10/:2.2/FRF85B/eng.leo.20110311.204810:user/test-keys[/B]
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
persist.app2sd.enabled=0
persist.keyguard.pattern.spec=2
persist.sys.language=en
persist.sys.country=US
ro.suspend.unloadWifiDriver=true
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Note: No ro.versioncode listed.
 

sharpe351

Member
Jul 2, 2011
337
8
build.prop from my #3925 (factory installed)

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF85B
ro.build.display.id=FRF85B
ro.build.version.incremental=eng.infotm-sqa.20110402.142351
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=2011年 04月 02日 星期六 14:26:11 CST
ro.build.date.utc=1301725571
ro.build.type=user
ro.build.user=infotm-sqa
ro.build.host=infotm-sqa-desktop
ro.build.tags=test-keys
ro.product.model=SAWEE10
ro.product.brand=generic
ro.product.name=SAWEE10
ro.product.device=wwe10
ro.product.board=
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=imap210
# ro.build.product is obsolete; use ro.product.device
ro.build.product=wwe10
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=SAWEE10-user 2.2 FRF85B eng.infotm-sqa.20110402.142351 test-keys
ro.build.fingerprint=generic/SAWEE10/wwe10/:2.2/FRF85B/eng.infotm-sqa.20110402.142351:user/test-keys
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.versioncode=20
ro.debuggable=0
persist.service.adb.enable=0
persist.app2sd.enabled=0
persist.keyguard.pattern.spec=2
persist.sys.language=en
persist.sys.country=US
ro.suspend.unloadWifiDriver=true
persist.launcher.def.desktop=1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Looks like mine was done at their factory.

Sent from a rooted SuperPAD clone with Android 2.2 :p
 

leeb

Member
Jul 16, 2011
463
21
Well, I have attempted this ICan install, attempted to reload the WWE10 install, and it still claims to be disco, with the same behaviors mentioned before (the SD card relocations as well as WiFi)...

Each and every time it processed thru the 'screen adjustment test' behavior clear up to the touch alignment adjustment procedure.

Internally...

I found that the end of the WiFi switch has BROKEN OFF.... which is why the slide button seemed so loose.
Will have to check the book to remember which is on... L or R.

In any event, there was no change in anything except the Kindle, etc that I had installed.... of course.
Other have claimed that the online update reverts back to 2.1 which would be nice if the Wifi works again...
HOWEVER,
The online update wont connect WITHOUT wifi... catch-22 yet again!

Will continue to play and read... hopefully some improvement will come to pass!

:D
 

dlzc

Member
Feb 10, 2011
71
8
...
I found that the end of the WiFi switch has BROKEN OFF.... which is why the slide button seemed so loose.
Will have to check the book to remember which is on... L or R.
...
:D

Towards the power button is ON.
 

leeb

Member
Jul 16, 2011
463
21
Towards the power button is ON.

Unfortunately, must disagree... at least on mine, I had to push it to the RIGHT (toward the SPEAKER) to make it work.
With a safety-pin! :eek:

But it DOES WORK NOW, running a 3925 (Infopad10) with only a couple of issues...
:D
 
Last edited:

sharpe351

Member
Jul 2, 2011
337
8
Unfortunately, must disagree... at least on mine, I had to push it to the RIGHT (toward the SPEAKER) to make it work.
With a saftey-pin! :eek:

But it DOES WORK NOW, running a 3925 (Infopad10) with only a couple of issues...
:D

DON'T KEEP ME IN SUSPENSE!!!! How is it, what issues.... please be more specific. I'm glad you got it straightened out.

Sent from a rooted SuperPAD clone with Android 2.2 :p
 

leeb

Member
Jul 16, 2011
463
21
(Copied from the 3656 thread...)

As of last nite I have a nearly-completely-WORKING copy on my pad...
It claims to be INFOPAD10 (FROM the icanv2655.ius)
Android 2.2 v2.1#3925 (FRF85B)

and I have only a couple if issues with it... one minor, one not.

Firstly, It DOES NOW recognize that SD1 and SD2 are DIFFERENT from LOCAL... YAY!!!
(Tho it shows folders for SDCARD1 and SDCARD2 IN local... whatever!)

The WiFi issue WAS IN FACT the switch in the wrong position, or so I must assume... once the saftey-pin moved it TO THE RIGHT it worked. YAY!!!
(YOU may want to try this BEFORE changing anything... perhaps it is a 'software switch' and not a 'mechanical power' switch... IT IS POSSIBLE that the 'on/off' positions got 'reversed'... just a thought!)

The camera does not seem to work. I dont care. Ill likely NEVER need it anyway. Havent yet, anyway! :rolleyes:

What DOES affect me is that the Kindle app is 'broken'... When I attempt to recover my books from the cloud, it faults out saying 'interrupted'. No reading for me... :(

For whatever reason the AUTO ROTATE is messed up... if I have it ON, the screen (while in landscape) will rotate LEFT to that portrait mode... so Ive disabled the AUTO ROTATE for the time being.... wonder if that's affecting Kindle. Will find out.

Havent attempted to get majhongg back yet... Did get the 'radio' and a bunch of other goodies. Happy Camper I am! :D
 
Last edited:

leeb

Member
Jul 16, 2011
463
21
The Kindle issue was apparently 'their problem'... it cleared up last nite and works fine since.

Thoughts...

Where is the info kept for the rotation? Surely it is a value passed to a register or somesuch and could be readjusted to be right.
Or, if nothing else, I can find the sensor and ROTATE IT.... physically .... by hand. :p

I dont really MIND turning it 'manually' (bwo the rotate button)... its just that I have to go thru 3 'ninties' to get where Im going... (usually landscape to 90dg clockwise)
:D
 
Last edited:

leeb

Member
Jul 16, 2011
463
21
Nice. Glad to hear its working. May flash the os only tonight.

I am 'somewhat seriously' considering trying to take the U0/u-boot BACK to the 'good one'... (587 or something)...
THEN see if that clears up the camera (and possibly rotation) issue(s)...

Scary thoughts goin' on here! :eek:
:D
 

sharpe351

Member
Jul 2, 2011
337
8
I am 'somewhat seriously' considering trying to take the U0/u-boot BACK to the 'good one'... (587 or something)...
THEN see if that clears up the camera (and possibly rotation) issue(s)...

Scary thoughts goin' on here! :eek:
:D

I wouldn't worry too much. The ROM itself is so screwy that it could be anything causing your issues.

Sent from a disparaged guy with a SuperPAD...another happy customer.
 

vampire365

Member
Mar 12, 2011
9
0
My camera works fine. Got v3 of Android market up and running. Can't seem to get the YouTube app working, though as well as playing vids in the browser.
 
Top