However, my Folio says SD card is damaged!

To replicate the tet, I put a card with contents that was accepted by the Folio into the Panasonic TZ10 & snapped 2 pictures & 1 video.

When I plugged this (previously working) card back into the Folio, it reported SD card damaged!

Also, When I copied an .MOD file from a Canon SD card into the Folio's SD card with a notebook, the Folio happily allows me to rename it to .MPG. But with a card from the Canon, it barfs and says cannot rename file!

Is this normal?

Or have I got a lemon amongst lemons?

BTW, Youtube FC on my Folio. SkyFire 3.0 works but videos hangs at buffering screen (between 10~25%).

Really bummer here.

Some of the installed apps are force-closing even out of the box, indicating the base ROM image is badly configured. Archiving and re-installing these seems to improve responsiveness. Do not try and prevent apps from being auto-loaded using a startup manager. The problem is with the application installation, not that the apps are draining the system.

Fix

The procedure goes like this:

Install systempanel (you will need access to an android phone, an emulator, or search for the APK and install it). Other tools may work as well, but that is the one I am familiar with. SystemPanel will archive itself onto SD, from where you can copy it to the Folio, browse to where it is with the toshiba file manager and install it.

Load System panel, select 'menu, installer'. This will show you all of the installed applications. Make a list of them all, then work through the list doing the following:

• Select the app in the list to get more details.
  
• Select 'archive' and check it has backed up the app. Skip any which are copy protected and can't be backed up.
  
• Un-install the app.
  
• Re-install the app. Move onto the next.
  

This will require you to enter any setup information again for each app, and to re-configure things like the supplied keyboard app, but it will make sure that any directories and configuration required is installed properly.

Running apps full-screen

You can use the 'spare parts' app to change the 'compatibility mode' for old applications which do not run full-screen. You will find this option near the bottom of the list on the front page of spare parts. The tick-box needs to be not ticked. It is 10th item down on the menu, under 'general'. You do need to reboot after un-ticking the box. Oddly, spare parts will FC on a HTC desire, but can still be sideloaded on the folio from the desire.

When I use a spirit level app, it shows that the sensor is calibrated fine, but in games, the car, plane, or whatever, just heads to the right.

Is there anyone out there that can tell me why this might be? Is it down to the tegra 2 platform or something that can be fixed/calibrated sepatately?

I know that they're different machines, but the advent Vega seems to have a G-Sensor game mode option in settings that helps with some games. Any idea why we haven't even got one of those?

Thanks.

he fixed opengles 2.2 and had gapps working.

and for the brave ones, look for dexter_nlb's foliomodv0.1 over at xda

leave ur impressions after using the roms and donate to the guy if u find his work fruitful.

I was posting my findings in the Advent Vega thread so I though I'd transplant the info here and stop cluttering it up:

Well just got home with my folio 100

First thoughts:

1. Wow the display is _terrible_ the viewing angles are like 10deg vertical making portrait viewing really tough (like bad polarized 3d)

2. The supplied launcher is awful, installed ADWlauncher and it was smooth as butter

3. There is a _huge_ delay between pressing power and waking up the device, sometimes as long as 5 sec... weird

4. Google maps installed from the apk , I didn't expect that to work.

5. Every 3d app I've tried so far has flickered or crashed, not good at all.

6. Too many apps are using the market "call home" API and refuse to run when sideloaded even though I paid for them fair and square, boo to DRM.

7. Quadrant scores were better than my CM6 Nexus one

8. The battery pack is completely removable.. which is nice as I've had to remove it due to lockups.

9. USB host mode does work for Storage and keyboards (most of the time, I have had problems)

10. After a short while with the screen off it goes into "hibernate mode" and quite often fails to come back out, requiring a reboot. Annoyingly this kills adb even if you have debugging set to hold a wakelock.

11. Using mini-usb-client the device does not charge, it needs its own netbook-style brick :)

12. Bluetooth on the device does _not_ do HID, so no bluetooth keyboards or mice

Take a look at the GLbenchmark results

http://glbenchmark.com/phonedetails.jsp?be...tgroup=lowlevel

vs the iPad

http://glbenchmark.com/phonedetails.jsp?be...tgroup=lowlevel

Compares well, though the iPad had much better fill rate.

Additionally I finally got ADB working. I could see "FAILED BINDER TRANSACTION" rows in logcat when it was stuttering, so I'm not sure the folio was to blame.

Whoah. Oh I think something I generally use was _really_ bad for it. not sure on the details yet, but I just uninstalled a load of stuff and suddenly its buttery smooth again. (I _think_ is was "visual task switcher")

BTW, superoneclickroot seems to work :)

Ok I've pushed GoogleServicesFramework.apk and Vending.apk to system/app I now get the market icon and once executed it takes me to the account signup. however that fails after signup. I think the Folio is mis-reporting its MAC address and thus the check-in is failing

D/NativeCrypto( 1295): Freeing OpenSSL session

V/CheckinRequestBuilder( 1295): pre-froyo android id is 0

I/CheckinTask( 1295): Sending checkin request (32167 bytes)

E/CheckinTask( 1295): Checkin failed: https://android.clients.google.com/checkin (request #0)

E/CheckinTask( 1295): java.io.IOException: Rejected response from server: HTTP/1.1 400 invalid hardware identifier: "00.24.7E.70.B3.6A" is not a valid MAC address (expect 12 hex digits)

E/CheckinTask( 1295):   at com.google.android.gsf.checkin.CheckinTask.parseResponse(CheckinTask.java:298)

E/CheckinTask( 1295):   at com.google.android.gsf.checkin.CheckinTask.sendRequest(CheckinTask.java:246)

E/CheckinTask( 1295):   at com.google.android.gsf.checkin.CheckinTask.doInBackground(CheckinTask.java:146)

Does the Folio use hdpi or mdpi graphics? (if you have adb shell access then 'getprop ro.sf.lcd_density' might be the easiest way to answer that - if it returns 240 it's hdpi, 160=mdpi). Just wondering if the pixels are so far apart on a 10inch screen does it fall under the mdpi category.

[ro.secure]: [1]

[ro.allow.mock.location]: [0]

[ro.debuggable]: [0]

[persist.service.adb.enable]: [1]

[persist.tegra.dpy5.mode.width]: [1920]

[persist.tegra.dpy5.mode.height]: [1080]

[EXTERNAL_STORAGE_MOUNT]: [/storage]

[ro.factorytest]: [0]

[ro.serialno]: []

[ro.bootmode]: [unknown]

[ro.baseband]: [unknown]

[ro.carrier]: [unknown]

[ro.bootloader]: [unknown]

[ro.hardware]: [tegra]

[ro.revision]: [0]

[ro.build.id]: [TOSHIBA_FOLIO_AND_A]

[ro.build.display.id]: [TOSHIBA_FOLIO_AND_A.5.0026]

[ro.build.version.incremental]: [5.0026]

[ro.build.version.sdk]: [8]

[ro.build.version.codename]: [REL]

[ro.build.version.release]: [2.2]

[ro.build.date]: [Thu Sep 30 15:21:11 JST 2010]

[ro.build.date.utc]: [1285827671]

[ro.build.type]: [user]

[ro.build.user]: [android]

[ro.build.host]: [git.pc.ome.toshiba.co.jp]

[ro.build.tags]: [test-keys]

[ro.product.model]: [TOSHIBA_FOLIO_AND_A]

[ro.product.brand]: [TOSHIBA]

[ro.product.name]: [TOSHIBA_FOLIO_AND_A]

[ro.product.device]: [TOSHIBA_FOLIO_AND_A]

[ro.product.board]: []

[ro.product.cpu.abi]: [armeabi-v7a]

[ro.product.cpu.abi2]: [armeabi]

[ro.product.manufacturer]: [TOSHIBA]

[ro.product.locale.language]: [en]

[ro.product.locale.region]: [US]

[ro.wifi.channels]: []

[ro.board.platform]: [tegra]

[ro.build.product]: [TOSHIBA_FOLIO_AND_A]

[ro.build.description]: [TOSHIBA_FOLIO_AND_A-user 2.2 TOSHIBA_FOLIO_AND_A 5.0026 test-keys]

[ro.build.fingerprint]: [TOSHIBA/TOSHIBA_FOLIO_AND_A/:2.2/TOSHIBA_FOLIO_AND_A/5.0026:user/test-keys]

[ro.kernel.android.gps]: [ttyACM2]

[ro.kernel.android.gps_ctl]: [ttyACM0]

[ro.config.notification_sound]: [OnTheHunt.ogg]

[ro.config.alarm_alert]: [Alarm_Classic.ogg]

[ro.config.sync]: [no]

[ro.media.dec.vid.wmv.enabled]: [1]

[ro.media.dec.aud.wma.enabled]: [1]

[ro.media.enc.hprof.file.format]: [3gp]

[ro.media.enc.hprof.aud.hz]: [44100]

[ro.media.enc.hprof.aud.ch]: [2]

[ro.media.enc.hprof.codec.aud]: [aac]

[ro.media.enc.hprof.aud.bps]: [128000]

[ro.browser.useragent]: [1]

[persist.service.mount.umsauto]: [1]

[net.bt.name]: [Android]

[net.change]: [net.dnschange]

[dalvik.vm.stack-trace-file]: [/data/anr/traces.txt]

[persist.tegra.nvlog.level]: [4]

[persist.sys.isHdmiPluged]: [false]

[persist.sys.timezone]: [Europe/London]

[persist.sys.language]: [en]

[persist.sys.country]: [GB]

[persist.sys.localevar]: []

[persist.sys.wifi_flag]: [false]

[ro.FOREGROUND_APP_ADJ]: [0]

[ro.VISIBLE_APP_ADJ]: [1]

[ro.SECONDARY_SERVER_ADJ]: [2]

[ro.BACKUP_APP_ADJ]: [2]

[ro.HOME_APP_ADJ]: [4]

[ro.HIDDEN_APP_MIN_ADJ]: [7]

[ro.CONTENT_PROVIDER_ADJ]: [14]

[ro.EMPTY_APP_ADJ]: [15]

[ro.FOREGROUND_APP_MEM]: [1536]

[ro.VISIBLE_APP_MEM]: [2048]

[ro.SECONDARY_SERVER_MEM]: [4096]

[ro.BACKUP_APP_MEM]: [4096]

[ro.HOME_APP_MEM]: [4096]

[ro.HIDDEN_APP_MEM]: [5120]

[ro.CONTENT_PROVIDER_MEM]: [5632]

[ro.EMPTY_APP_MEM]: [6144]

[net.tcp.buffersize.default]: [4096,87380,110208,4096,16384,110208]

[net.tcp.buffersize.wifi]: [4095,87380,110208,4096,16384,110208]

[net.tcp.buffersize.umts]: [4094,87380,110208,4096,16384,110208]

[net.tcp.buffersize.edge]: [4093,26280,35040,4096,16384,35040]

[net.tcp.buffersize.gprs]: [4092,8760,11680,4096,8760,11680]

[init.svc.console]: [running]

[init.svc.mmcblk0p8]: [stopped]

[init.svc.servicemanager]: [running]

[init.svc.vold]: [running]

[init.svc.netd]: [running]

[init.svc.debuggerd]: [running]

[init.svc.zygote]: [running]

[init.svc.media]: [running]

[init.svc.dbus]: [running]

[init.svc.installd]: [running]

[init.svc.keystore]: [running]

[init.svc.tosfb]: [running]

[init.svc.tupdate]: [running]

[init.svc.nvrm_daemon]: [running]

[init.svc.wlan_tool]: [stopped]

[init.svc.postinit]: [stopped]

[init.svc.ak8975]: [running]

[init.svc.eventd]: [running]

[wifi.interface]: [wlan0]

[init.svc.adbd]: [running]

[wlan.driver.apmode]: [unloaded]

[init.svc.bootanim]: [stopped]

[WIFI_MODULE_TYPE]: [1]

[hw.keyboards.65536.devname]: [qwerty]

[net.hostname]: [android_9774d56d682e549c]

[hw.keyboards.65538.devname]: [nvec cir]

[hw.keyboards.65540.devname]: [qwerty]

[wlan.driver.status]: [unloaded]

[hw.keyboards.65541.devname]: [nvec keyboard]

[hw.keyboards.65543.devname]: [tegra-kbc]

[hw.keyboards.65544.devname]: []

[dev.bootcomplete]: [1]

[init.svc.wpa_supplicant]: [stopped]

[gsm.sim.operator.numeric]: []

[gsm.sim.operator.alpha]: []

[gsm.sim.operator.iso-country]: []

[gsm.sim.state]: [UNKNOWN]

[gsm.current.phone-type]: [1]

[gsm.operator.alpha]: []

[gsm.operator.numeric]: []

[gsm.operator.iso-country]: []

[gsm.operator.isroaming]: [false]

[ro.runtime.firstboot]: [1288855778298]

[net.dnschange]: [22]

[dhcp.wlan0.result]: [failed]

[init.svc.dhcpcd]: [stopped]

[dhcp.wlan0.pid]: [5719]

[dhcp.wlan0.reason]: [STOP]

[dhcp.wlan0.dns1]: []

[net.dns1]: [192.168.43.1]

[dhcp.wlan0.dns2]: []

[net.dns2]: []

[dhcp.wlan0.dns3]: []

[net.dns3]: []

[dhcp.wlan0.dns4]: []

[net.dns4]: []

[dhcp.wlan0.ipaddress]: [192.168.43.185]

[dhcp.wlan0.gateway]: [192.168.43.1]

[dhcp.wlan0.mask]: [255.255.255.0]

[dhcp.wlan0.leasetime]: [3600]

[dhcp.wlan0.server]: [192.168.43.1]

[sys.settings_secure_version]: [7]

[hw.keyboards.65545.devname]: []

[hw.keyboards.65546.devname]: []

[hw.keyboards.131080.devname]: []

[hw.keyboards.196616.devname]: []

[hw.keyboards.262152.devname]: []

[hw.keyboards.327688.devname]: []

[hw.keyboards.393224.devname]: []

[hw.keyboards.458760.devname]: []

[init.svc.bluetoothd]: [stopped]

[init.svc.opush]: [stopped]

[init.svc.hciattach]: [stopped]

[sys.settings_system_version]: [2]

[hw.keyboards.524296.devname]: []

[hw.keyboards.589832.devname]: []

[hw.keyboards.655368.devname]: []

[hw.keyboards.720904.devname]: []

[hw.keyboards.786440.devname]: []

[hw.keyboards.851976.devname]: []

[hw.keyboards.917512.devname]: []

[hw.keyboards.983048.devname]: []

[hw.keyboards.1048584.devname]: []

[hw.keyboards.1114120.devname]: [usb_keyboard_102_en_us]

/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

/KeyguardViewMediator( 1026): pokeWakelock(5000)

/KeyguardViewMediator( 1026): pokeWakelock(5000)

/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

/WindowManager( 1026): Key dispatching timed out sending to Keyguard

/WindowManager( 1026): Previous dispatch state: null

/WindowManager( 1026): Current dispatch state: {{null to Window{4a809e50 Keyguard paused=false} @ 1288870649940 lw=Window{4a809e50 Keyguard paused=false} lb=android.view.ViewRoot$W@4a6e7150 fin

false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a809e50 Keyguard paused=false}}}

/WindowManager( 1026): No window to dispatch pointer action 1

/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

/WindowManager( 1026): Key dispatching timed out sending to Keyguard

/WindowManager( 1026): Previous dispatch state: null

/WindowManager( 1026): Current dispatch state: {{null to Window{4a809e50 Keyguard paused=false} @ 1288870654944 lw=Window{4a809e50 Keyguard paused=false} lb=android.view.ViewRoot$W@4a6e7150 fin

false gfw=true ed=true tts=0 wf=false fp=false mcf=Window{4a809e50 Keyguard paused=false}}}

W/WindowManager( 1026): No window to dispatch pointer action 1

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/Process ( 1026): Sending signal. PID: 1026 SIG: 3

I/dalvikvm( 1026): threadid=3: reacting to signal 3

I/dalvikvm( 1026): Wrote stack traces to '/data/anr/traces.txt'

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/wpa_supplicant( 1170): CTRL-EVENT-SCAN-RESULTS

I/Process ( 1026): Sending signal. PID: 1026 SIG: 3

I/dalvikvm( 1026): threadid=3: reacting to signal 3

I/dalvikvm( 1026): Wrote stack traces to '/data/anr/traces.txt'

I/Process ( 1026): Sending signal. PID: 1120 SIG: 3

I/dalvikvm( 1120): threadid=3: reacting to signal 3

I/dalvikvm( 1120): Wrote stack traces to '/data/anr/traces.txt'

I/Watchdog_N( 1026): dumpKernelStacks

E/Watchdog_N( 1026): Unable to open stack of tid 1026 : 13 (Permission denied)

E/Watchdog_N( 1026): Unable to open stack of tid 1027 : 13 (Permission denied)

...

E/Watchdog_N( 1026): Unable to open stack of tid 1276 : 13 (Permission denied)

E/Watchdog_N( 1026): Unable to open stack of tid 1278 : 13 (Permission denied)

D/dalvikvm( 1026): GC_FOR_MALLOC freed 13505 objects / 1393888 bytes in 63ms

I/dalvikvm( 1026): Jit: resizing JitTable from 4096 to 8192

I/Process ( 1026): Sending signal. PID: 1026 SIG: 9

W/Watchdog( 1026): *** WATCHDOG KILLING SYSTEM PROCESS: null

D/		(  923): NVRM_DAEMON(478): forcibly killing queue fd 31

D/		(  923): NVRM_DAEMON(478): forcibly killing queue fd 36

D/		(  923): NVRM_DAEMON(478): forcibly killing queue fd 34

D/		(  923): NVRM_DAEMON(478): forcibly killing queue fd 33

E/installd(  919): eof

E/installd(  919): failed to read size

I/installd(  919): closing connection

I/ServiceManager(  912): service 'network_management' died

It would be nice if owners could post what apps and roms ( probaly/hopefully many will be available in the near future) they are using on their folio and how the experience is with the device.