yashsingh1/xdaforums huggingface dataset:
[Folio 100 Android Development] ma1999:
The unresponisitivnes is random and hangs on for a while (minutes). When it happens its often after a cold boot. I have not had it reappear during the same session (until reboot that is) but I often reboot :)

It feels really random, sometimes days goes without problems, sometimes

I get it twice a day.

The problem has been been with all 1.2/1.3 mods atleast.

So yes, I fully understand its hard to find out the problem.
[Folio 100 Android Development] gohanSS:
Do u mean if somebody used titanium backup to restore full apps and their data or to restore system settings?

Sent trom foliomod 1.3d
[Folio 100 Android Development] kakkio:
unresponssive touchscreen after 1.3d - my experience

after 2 day of "1.3d"

no

unresponssive touchscreen issue found.
[Folio 100 Android Development] uc370:
1.3d and no touch problem; but i had it with the past built.pro for google earth... installed autokiller and perfect

I have problem tethering with winmo, connect adhoc, but no internet, has poor signal being 1 cm away... any ideas
[Folio 100 Android Development] Dexter_nlb:
lol, thought "rockplayer" was a music app :-)

thanks, ill check it out with my latest build here.. check tomorrow for a more complete and improved build :-) (its ready, but im tired)
[Folio 100 Android Development] ommx:
waiting for your good news Dexter_nlb, and will try everything out on your new ROM, thank you
[Folio 100 Android Development] Dexter_nlb:
well, seems not perfect at all, native player works quite well too for MP4 files..

secondly, try out the YXPLAYER as well, it got much better mpg/avi support than this rockplayer.. but mkv's seems to be worse here, and no hw support although mentioned..
[Folio 100 Android Development] Mark Chia:
Seems only Rockplayer can do.mkv format.
[Folio 100 Android Development] mddsd:
There's a bunch of players that can handle MKV, but none of them can handle 720p on the Folio.

- Vplayer Beta

- YXPlayer

- RockPlayer

One intresting thing is that the Folio can play H264 1080p in MOV format with the builtin player in the Gallery and the Toshiba Media Player.

So there is very competent hardware in the Folio. But none of the above players can play MKV in 720p... It would be great if there was a videoplayer that can handle this without hanving to reencode everything to MOV.

Archos 70/101 seem to have solve this problem by allowing their player to handle MKV(720p) and use hardware acceleration.

Also CoreCodec are developing a videoplayer for android, but I don't think they will release this anytime soon. :(
[Folio 100 Android Development] stilgar1337:
I noticed that Dolphin Browser force closes after a while. Is this normal? The stock browser works fine...

also, i haven't installed flash, so it's not a compatibility issue.

Can we have a link to the correct flash version in the first post? I forgot where i found it when i installed it in the stock firmware, and it could help new users...
[Folio 100 Android Development] stilgar1337:
I just noticed this... If it's true, get ready for a donation, this would solve the most serious issue i have with the tablet!

Crossing my fingers...

(also: i tried installing angry birds without the sd card inserted, and now it doesn't disappear when i reboot the tablet. Nice.)
[Folio 100 Android Development] tshoulihane:
This comes down to Tegra having a multitude of dedicated processors (7 I think) which are available for specialised tasks, and Nvidia being quite secretive about how any of their accelerators work. Exactly the same reason as the generic flash player not working at all on the folio.

There is no shortage of tegra tablets, so better support will come (although maybe not in free players)
[Folio 100 Android Development] pandersen:
Hi Dexter,

Thanks for a fantastic job. Is the easiest way to get your future paths and updates through this forum, or will you upload the same updates to your website? Will my apk be deletet when upgrade to the new mod? Thanks again, Your are amazing!
[Folio 100 Android Development] james00000007:
Thanks for all your hard work! I think this must be the smallest development community in the world! I had ago go with your first rom last night as I cant wait any longer for Toshiba. I had several issues with the andriod.phone process crashing and the tablet was unusable. I also had a problem where I manged to drag a widget down into the center/bottom area of the home screen and I couldnt drag it into the bin for love or money.

I'll have a go a the new rom, when its up. I'm really sad that Toshiba havent even given us any sort of comms via there toshiba folio update email service. Its amazing that the Advent guys are actually on the forums and listening and updating their build on the release day, while we are still in the dark. If your out there Toshiba make it special!
[Folio 100 Android Development] Dexter_nlb:
I dont think they have no good arguments or response to give to you, so they try to make it better, fully aware of the poor build they released.

But hardware does seem nice somehow if you leave out hdmi option which is not 1080p..

Well i think i take it back, seems Wifi has its own mind on pushing for "activate" screen here(also on v02), so i guess the hard choice is to accept it, as even my milestone with 100% proper android firmware also does the same.

But of course, Wifi is enabled on the phone too..

Its probably a kind of android bug, which no ones seems to mention in the right place. But thanks, ill follow the path to improve no matter what.
[Folio 100 Android Development] Dexter_nlb:
Request: a beta tester in the next 4-6 hrs who can test v0.2?

Hi do anyone have a chance to beta test the new 0.2 before i post it public?

please PM me directly and ill provide you with more information.

STOPPED! i got many responses now! thanks to all
[Folio 100 Android Development] stilgar1337:
Really? I also have a Milestone (2.1 stock firmware) and i never had this issue... Anyway, hopefully this screen-on problem can be fixed soon.
[Folio 100 Android Development] Dexter_nlb:
i guess im unlucky then because on froyo2.2 with 2 of the mods (MIUI and FroyoSense), those does have this similar issue but maybe depends on how you configure clients and wifi all together..so maybe 2.1 would do it too.
[Folio 100 Android Development] ommx:
i'm happy to help out, just PM you,... let me know what i can do ,
[Folio 100 Android Development] stilgar1337:
Interesting...

However, i noticed that if you set the folio in airplane mode, disable background data (settings->accounts and sync) and kill the processes of the apps that might request a data update (like news and weather) the screen turns on less often. Also, if the folio is put in standby while no program is running, it's less likely to have this issue.

There is a program on the marketplace that i will try later tonight, it's called wireless killer, it might be able to help... I'll post the results asap
[Folio 100 Android Development] ommx:
Now I'm posting with the new beta ROM, will provide you with all feedback via PM
[Folio 100 Android Development] stilgar1337:
ommx does the screen turns on during stand by with the new rom?
[Folio 100 Android Development] ommx:
Nope, i been testing it for awhile now, i even set the wifi setting to be never sleep, but i'll try to let it stand by for more than 20mins ,

will keep up date
[Folio 100 Android Development] stilgar1337:
Sounds good! Please let me know, i'm really looking forward to this
[Folio 100 Android Development] rodemkay:
This means sometimes i have some lags of 5-10 seconds. But as i sayed its useable and okay.

When i´m browsing (xscope) i couldn´t scroll sometimes. When i change orientation or i push the menu button it works again and i can scroll through the site. Its not very often but happens sometimes.
[Folio 100 Android Development] Maremagnum:
Ok i just updated from 1.2x to 1.3d, and i noticed almost instantly the touch issues (didn't have in 1.2x).

However i'm not sure if it is a screen driver/soft going zombie and not responding, or another thing, because although when this happen i'm not able to scroll at all i'm still able to click, but i need to leave the finger on the screen for even 2s to work (i mean 2s for the soft to notice that i'm clicking), it's like the touch accuracy & sensibility being greatly reduced, not like a real crash or freeze, weird.

Also is not a global system issue, because while being in some apps this issue does not appear (for example inside google maps, touch works perfectly, never hangs) and just when i close the app and go to the desktop it appears.

So my first bet goes for an app compatibility issue, i still have to test with the old screen driver, just in case..

I have to check further, but at a first glance it seems that without apps in execution the issue does not appear

PD: this issue is more likely to happen soon after boot, and more often, once the system is up and busy for some time the issue seems to appear less frequently (to even not appear again until next boot), but it's just my appreciation
[Folio 100 Android Development] GrigAdri:
Hi Dexter,

First, I want to thank you and all of the others for the excellent job you guys are doing.

I also I have experienced unreponssive screen issue, first on 1.3c and soon after the install of the 1.3d.

Today, a day after the 1.3d install and scren cleaning, the unreponssive screen issue is gone...

On the 1.3c mod, at the begining, all was just fine. After a while I've started to install some applications and games from Market and at a certin point the unresponssive issue apeared. Unfortunely I can not recall when.

I wish I may be able give you guys a hand...

REGARDS,

Adrian
[Folio 100 Android Development] frklk:
unresponsive touchscreen

I know that seem silly, but try to handle the folio with only one hand in the middle of bottom side and not with two hands in the corners... in my case the screen restart to respond fast.

Can anybody confirm?

Bye frk
[Folio 100 Android Development] jvegar:
both (patch and image)

when i start the device,some times the unresponsivites make me to off and another work proprerly
[Folio 100 Android Development] Trumpfz:
I had the unresponsive Touchscreen with 1.3b.

Games were running fine and fast, but you just couldn't control them smooth with the touchscreen. You really had to wait few secs until the screen responded again. It happened right after flashing so even the first setup with select timezone it didn't work smooth.

I went back to 1.2 and the problem disappeared.

Reinstalled 1.3 again and got the same Touchscreen problem again. I made that trick with switching off GPS with that App mentioned few pages earlier in this thread. Since then I had no problems with the screen any more.

I'm still at 1.3c. That trick was called a placebo, but I don't careas long my Folio is running smooth. :D
[Folio 100 Android Development] tweyer:
v1.3d works fine for me - first release without hangs

Hi

I am currently on v1.3d without the responsiveness-patch. After using it since its release, including several reboots and standby cycles, I have not seen the "freeze" issue.

Up to v1.3c, I had touchscreen-freezes (the touchscreen and buttons do not respond, just the physical hardware-buttons - only leaving the option to turn the Folio off) quite often.

Using v1.3c with GPS turned off with the "Android Assistant" APP eased the situation. I did not use it a lot, since v.1.3d came out soon after I turned GPS off.

I moved to v1.3d by patching my existing v1.3c, without a factory reset, so I can rule out application misbehaviour fairly confident.

To me, v1.3d works like a charm. The Folio is incredibly smooth, responsive and snappy.

The only issue left - for me - is the enormous battery-drain during operation and especially during stand-by. The stand-by is of course due to the well-known frequent device-wakeups.

"Jumping menu" does not happen with me, if I initialize the four keys once with FolioButtons after boot.

Regards

tweyer
[Folio 100 Android Development] Linmad:
unresponsive screen

Hi everyone,

Maybe i say something stupid but i had the screen problem and i turn it off and clean the screen with a humid cloth and after turning on now it goes perfect. Maybe screen is much sensitive and dirt and greese makes it feel you are pushing the screen in many places.

Hope it helps
[Folio 100 Android Development] Maremagnum:
I'm not sure about what i have done, but the touch issue seems gone.

I have rebooted several times and haven't been able to replicate the problem again, everything seems to be working as it should..

Maybe it's just temporal, but seems stable now, anyways this is what i remember to have done since the system install, maybe something fixed the problem:

Set launcher pro as default launcher.

Make sure gps is disabled by enabling & disabling again.

Install android assistant from market, set timeout to 10min (i think)

Remove fring, evernote, social and note widgets.

Uninstall toshiba market, toshiba updater, toshiba online info.

Disable account & apps synchro, disable wifi (ip) location.

Remove opera, since it does not work well (at least for me) and firefox 4 works way better.

Probably something else more, if the issue reappears i'll tell.
[Folio 100 Android Development] shpitz:
Problem of the screen response in 13d back to the version 13C and the problem disappeared.
[Folio 100 Android Development] alv002:
"not enough space on device"

Hello!

Simple question, yesterday I tried to install del 1.3d (full version 150mb posted on this thread). I could´t because in the recovery menu, the android robot had an exclamation mark on top, I pressed the home button and the system said that I couldn´t because "not enough space on device". I run factory reset, as always before and after applying each patch. Why is this happening? and how do i solve this?
[Folio 100 Android Development] myghimh:
i saw that b4, i think what i did was the wipe the cache... got option list right?
[Folio 100 Android Development] metuskale:
a linux will do..

and you simply mount the "system.img" on your linux with:

mount -oloop system.img /mymountpoint

the boot.img/recovery.img require mkbootimg here, you find lots on google on that one..[/QUOTE]

I have looked for mkbootimg and i have found that is used to repack the image, my problem is that in cannot mount it or split so at the moment i dont want to repack.

how do you do to mount/extract (at the moment i am using ubuntu)
[Folio 100 Android Development] shpitz:
hi dexter,

I have a request that serve All those who suffer MENU crazy button .

Is it possible to prepare application you can setting ON/OFF the MENU button

Most of the time useless button.

sometimes button jump after 10 minutes, sometimes after an hour

Usually I fix the problem by changing the settings with FolioButtons 1.1.

If you could add to FolioButtons on/off operation for menu Buttons was the best.

All else works Excellent with version 13C
[Folio 100 Android Development] colossus77:
For those who have the problem with a touchscreen.

I have version 1.3c installed by the factory reset before and after installation.

I have never installed the 1.4D and got the same problem with touch-freeze.

Thanks again to Dexter for his work
[Folio 100 Android Development] Butchi:
Hi I think it is the other way around. A capacitive screen reacts to a change in capacitance if you get close or touch the screen (no conductivity). To prove the point. I left the protective screen that came with the new pad on the LCD screen and it works without a problem (including the 4 buttons on the side).

BTW I am running foliomod 1.3c and the screen every now and then freezes. Not often enough to describe the exact situation when it freezes.

Butch
[Folio 100 Android Development] cloriente:
Problem: My Folio doesn't rotate

Hi friends,

After having installated Dexter's Mod 1.3d my Folio doesn't rotate anymore. I don't know if it is a common issue, but I know that it did before. I don't know when has it happened because I have transfered quickly from 1.3 to 1.3b-c-d. I'd be very pleased if someone could help me with this problem. It is very annoying specially now that I've got the specifid Toshiba cover for the Folio which invites to take it vertically.

Thanks to all and specially to Dexter.
[Folio 100 Android Development] Kostia:
Same here, 1.3c works ok, except from some rare crazy back-button issues
[Folio 100 Android Development] Dexter_nlb:
the screen refresh trick was posted yesterday in Viewsonic Gtab section to test it and hear their response.. so far only 1 reported what he think is slower reaction time from touchscreen but the others has not commented it..

for those experiencing what you feel is "unresponsive" touchscreen, install the test patch posted some pages back..

the conclusion and i dont think it needs more comments on this matter, is to rollback the device driver in the testpatch and you're fine for those having that issue.

furthermore it has been noted now, that a tablet is held differently by users, and i believe that part of the problem with sensitivity is increased by the framerate, so people holding it close to the black borders, might experience this.

but thats just a story and theory since not all users experience it.
[Folio 100 Android Development] Maxell:
hi dexter,

sorry but I can not ... : (

I upgrade to the 1.2 toshiba edition but I did not finish the installation

(triangle with exclamation point)

the same if you load any tool type or update(update-boot-recovery.zip ,storage.zip)

I always restart "0 GB disk space"

I do not know what to do ...

help me please: (
[Folio 100 Android Development] dacasamir:
Factory reset wil help.
[Folio 100 Android Development] radi8:
Stock ROM (dez/2010) rooted

First of all I would like to thank you Dexter_nlb , Weeds2000 and everyone else for the excellent work done so far in this ROM.

However, for my present needs, battery life is really important, so I have to switch back to stock ROM.

What would really help me would be to have the new updated stock ROM (dez/2010) rooted. Tried to do it myself for several days, but I couldnt.

I dont know if its too much trouble or if it would take too long but is it possible for you to post it on your first post ( or somewhere else) for those interested?

Thank a lot for your help!
[Folio 100 Android Development] costeph:
It solved the problem for me! I had the problem on each boot, and now it s ok with the patch. Thanks
[Folio 100 Android Development] Dexter_nlb:
here's a little help, and you do some legwork too..

Take official stock dec. release, and copy my FolioMod "boot.img" into the official release zip file, and flash it..

I think it should work fine, and you got a root'd shell. test and let me know..
[Folio 100 Android Development] touch444719:
Hello everyone,

Big thank you for the job that you provided dexter !

I just have a small question : is there a version without pre-installed program planned ?

Well done for the job anyway.
[Folio 100 Android Development] NIMMVier:
unresponsive screen

I had problems with unresponsive screen after browsing a wile,

with the patch the problems are gone.
[Folio 100 Android Development] genepax:
http://www.youtube.com/watch?feature=player_profilepage&v=bo1C-VKK7EI

Here is a video of my Folio reacting to the dirt on the touchscreen...

My Folio has the full FolioMod v1.3d with the test patch and only adw.launcher installed.
[Folio 100 Android Development] xoloinc:
I have to agree on this one. Don't understand why there have to be a bunch of apps preinstalled. I'm picky ;) but it's a little bit annoying to be sitting uinstalling apps every time I do reset and reinstall.

Ok, understand if you dexter dont want to put the time to clean up after developing and testing, but wouldn't it be better to make a version that is totally clean of extra apps, and let the users them self download and install from this forum what they want? Maybe just include the one in the toshiba rom.

This would probably also make it easier to single out erratic behaviour in eventual extra apps that make ppl cry for help when it's in fact is program/service error in an application instead of the mod itself.

I lay flat if the general concesus is that preinstalled apps should be there, but couldn't it be a option to consider.
[Folio 100 Android Development] Dexter_nlb:
deleted! not important
[Folio 100 Android Development] laudrup69:
¿You've done a factory reset before and after?
[Folio 100 Android Development] SoJoS:
Please don't drop it Dexter, your work is much appreciated!

You made my Folio shine. I'm kinda broke right now, but will definitely donate.
[Folio 100 Android Development] Dexter_nlb:
i agree that a possible "gapps" based folio with no extra apps, could maybe exclude if an app is sometimes causing problems.. let me consider it.

making all the images does take time to prep.
[Folio 100 Android Development] shpitz:
Dexter,

Never mind, we thank you for your activity.

Reduce the device to tablet can show off with.

Again, thank you without you there was nothing to do with the device.
[Folio 100 Android Development] Dexter_nlb:
IR remote

I noticed another thread discussing IrDa , if its supported, so i picked mine up and tested.. and to my surprise its not working anymore.. can anyone else confirm? while i debug with older images..

ps: V1.2 really had standby powerbutton issues btw, i have 3 times awaken it, and everytime i had to push several times to make it wakeup, so v1.3d is really an improvement on the awake issue, but still not perfect i know..
[Folio 100 Android Development] mchabr:
I was thinking the same. I have my favorite apps backed up anyway. Maybe just the mod related tools. Thanks.
[Folio 100 Android Development] Dexter_nlb:
FRAG!!!

It just required another removal of the battery and my remote was working fine.. i forgot about that trick :-(
[Folio 100 Android Development] NIMMVier:
Befor and after a patch i dont make a factory reset.

But i make the factory reset befor and after a new rom.
[Folio 100 Android Development] kakkio:
we all appreciate your work, please don't take in account 2 idiots..... the world is full of them....
[Folio 100 Android Development] B_Thax:
+1

There are always many trolls out there hehe... your work makes the folio a great device!
[Folio 100 Android Development] Maremagnum:
Thanks for checking the ir thingy :), so it works just for receiving or also to send data? (there is any app to experiment with remotes? or what have you used?)
[Folio 100 Android Development] Den'ice:
... error of quote ...
[Folio 100 Android Development] Den'ice:
+1

Thank you dexter !
[Folio 100 Android Development] Dexter_nlb:
somehow the receiver is connected so input is in android reports back as if it comes from a keyboard.. so the ir function is built into the framework / kernel and atm i dont know how they implemented it, but it works (when it works)
[Folio 100 Android Development] GrigAdri:
Just ignore the idiots. The world is full of them!

A BIG THANK YOU FOR YOUR EFFORTS AND SUPERB WORK!
[Folio 100 Android Development] Dexter_nlb:
Framerate versus refreshrate on my hack

Viewsonic users are suddenly being scared away with "your device can max manage 75hz"... i think its total rubbish..

I tried to point out very early on, that its was an increase in framerate, not refreshrate of the screen display..

those two are very different, and facts can very well be, that my hack really didnt do much good, as if we go way over 140 frames and your folio100 only runs with a 50-75hz refresh rate, there are frames lost.

But damaging the device? no way... if that was true i would have seen it the instance i hit the 170 framerate i did, but also was very buggy and picture was distored with wrong colors..
[Folio 100 Android Development] kakkio:
try to point them HERE .... it could help (maybe) ;)

edit:

no doesn't help I see