Related
Hi,
I´m writing this post to notify that there is a new official update from toshiba.
I cannot give more information, because my folio is in SAT, but the version number might be "18/02/2011 (2.2.5.0131)". I have no info about changes yet, but I´ve red something about preparation for the new flash player and more utilities.
My source:
htcmania.com/showthread.php?p=1874046&posted=1#post1874046
(Sorry, I can´t still post urls, you may add the usual www to check the adress)
Maybe we have new materials for our favourite mods (for me, Folionotion and foliomod, I can´t decide).
Any additional info will be wellcome, thanks
herozote said:
Hi,
I´m writing this post to notify that there is a new official update from toshiba.
I cannot give more information, because my folio is in SAT, but the version number might be "18/02/2011 (2.2.5.0131)". I have no info about changes yet, but I´ve red something about preparation for the new flash player and more utilities.
My source:
htcmania.com/showthread.php?p=1874046&posted=1#post1874046
(Sorry, I can´t still post urls, you may add the usual www to check the adress)
Maybe we have new materials for our favourite mods (for me, Folionotion and foliomod, I can´t decide).
Any additional info will be wellcome, thanks
Click to expand...
Click to collapse
New update is fantastic, touchscreen is super sensitive, battery lenght really improve, And rotation od screen is super fast and smooth. Flash work perfectly. Really a great update. Finally I can say thanks Toshiba.
Impressive the laggs are completly removed
MCLP said:
Impressive the laggs are completly removed
Click to expand...
Click to collapse
Is there support to market place?
Will we have it in mods ???
I have installed it.
It seems to be more performance in 3D games.
Flash plugin preinstaled, and it can run the flash animation in Toshiba's web page .
It solves some bug about brong accelerometer axis in some games.
But no Android Market, only the same *sigh* Toshiba Market.
The question is whether we can install FolioMod on top of this update or not. For me,it's not worth updating this without DexterMod, which is already very good imo
xitrumch said:
The question is whether we can install FolioMod on top of this update or not. For me,it's not worth updating this without DexterMod, which is already very good imo
Click to expand...
Click to collapse
if you wantt custom mods, you avoid the update!!!!
THIS UPDATE WILL BLOCK YOUR UPDATE OPTIONS, AND BYE BYE CUSTOM ROMS
I confirm that the root of 5.0131 is ok yessssssss !
I'm guessing this updates the recovery kernel, and the recovery kernel is the only place that the recovery kernel is visible from to write? So root access is not enough for a simple way of updating the whole OS partition.
tshoulihane said:
I'm guessing this updates the recovery kernel, and the recovery kernel is the only place that the recovery kernel is visible from to write? So root access is not enough for a simple way of updating the whole OS partition.
Click to expand...
Click to collapse
they might have blocked it on the new update as well, making it really hard to get revert.. but on previous editions you can easily write a new recovery.
the partition is visible at partition 7, but this might have changed.
i have not had the luxury to look at the actual update, so what is inside, is for me to find out.. then we get all the nasty details.
ok guys... anyone having installed this update pls kindly report the following:
1. stability status
(crashes freezez sod)
2. software issue - can sideloaded applications be installed and used?
3. root ability ?
4. 3d games like dangeon defenders working ?
5. custom flashing ability?
sader0 said:
ok guys... anyone having installed this update pls kindly report the following:
1. stability status
(crashes freezez sod)
2. software issue - can sideloaded applications be installed and used?
3. root ability ?
4. 3d games like dangeon defenders working ?
5. custom flashing ability?
Click to expand...
Click to collapse
1. no craches or freezing
2.3d games like the one mentioned should work has a charm
3.root ability yes
4.ability to sideloads apps not tested but should be fine since you can root its easily
5 custom flashing ability yes using adb to instal first the old kernel
basicly the tablets works has it was ment to be i think that toshiba might even suprise everyone by realeasing honeycomb for this tablet in future
When I go to Toshiba Service Station, there is no update available(using Dexters wonderful foliomod). How do I get to see it and if I want to install how do I keep all the wonderful stuff on it already. This is my wifes and not mine so she will get pissed off if she loses everything on it again?
Thanks.
go back to stock rom and update it should work
MCLP said:
2.3d games like the one mentioned should work has a charm
Click to expand...
Click to collapse
you will need build.prop changes to some games working, and gameloft is still the same as CPU has not changed..
MCLP said:
4.ability to sideloads apps not tested but should be fine since you can root its easily
Click to expand...
Click to collapse
So you can use market now
MCLP said:
5 custom flashing ability yes using adb to instal first the old kernel
Click to expand...
Click to collapse
guess how many users will ask how do it i think its a step backwards, and too complex for regulars...
MCLP said:
basicly the tablets works has it was ment to be i think that toshiba might even suprise everyone by realeasing honeycomb for this tablet in future
Click to expand...
Click to collapse
unless it got market, gmail and syncing support, its not like its meant to be yet..
and honeycomb will not appear as display is just 1024x600, so no chance of a google certification for folio100 here, same as with gapps support. so forgot toshiba solving that..
Saw people got honeycomb running on nook color with the same resolution screen... no certification does not mean that is not possible...so we still can have our fingers crossed on that
sader0 said:
Saw people got honeycomb running on nook color with the same resolution screen... no certification does not mean that is not possible...so we still can have our fingers crossed on that
Click to expand...
Click to collapse
i wrote: Toshiba do not deliver, that does not mean i can't
I don't doubt you can. But I guess this screen resolution difference could cause troubles in some apps again
Just read about the new update and the issues with it. I have my Folio sent in for repair and they always update to the latest firmware before sending back to customer, so it looks like im in deep ****. I know how to use adb and fastboot, use them all the time on my desire hd and my VEGA. Maybe someone could write a good guide on how to flash this old recovery and which of all the rooting procedures that works with the new firmware. I also dont know how to get Folio in fastboot. But if we have a working root we can flash the old recovery or clockwork recovery, is that right? Because if not i might as well throw it away. No use in trying to sell it, no one will buy a useless tablet anyways. HOPING FOR A GUIDE CALLED: HOW TO RESTORE YOUR FOLIO WITH FLASHABLE RECOVERY
You can download the ROM files from here: http://goo.gl/ETPsm
Sorry I haven't had the time to package it for CWM. Hoping somebody here can do that for me.
Ta!
Care to elaborate, whats working, whats not...
Thanks, looking forward for this.
It should be everything included in this video
http://www.youtube.com/watch?v=dyPeT-ZUbBw&feature=youtube_gdata_player
Can't wait till someone compiles a ROM
how do I apply the update, you have any doc?
rosarafael said:
how do I apply the update, you have any doc?
Click to expand...
Click to collapse
Once someone compiles a ROM, it will be flashable via revovery.
rosarafael said:
how do I apply the update, you have any doc?
Click to expand...
Click to collapse
If you don't know how to flash it, then it's best for you to not even try.
It's an ALPHA (or even before an alpha) made from SDK image ported (quickly) to the Nexus One.
This means a lot of things are not working, it's not stable and can not be used as "main rom".
Just wait, "usable" ICS roms will come but now it's just too soon.
I asked him in a twitter. Here is answer:
Too many things to list that's not working. Here's what's working: touchscreen, hard buttons, battery indicator, accelerometer.
Click to expand...
Click to collapse
I ask, to see if there is any specific procedure, to work as many resources.
Unfortunately I do not know build a room, but, I try and install them, and if I can. Help improve.
With my comments.
Tks
Looking for devs to help in modifying gralloc.qsd8k.so to work in ICS. Please post below if ou can help.
The first problem is making a hwcomposer.qsdk8.so for Nexus One, this enables the hardware acceleration, needed for ICS.
I don't know, but I think it's actually possible without ICS source code
Just search for "hwcomposer android" on google
Sent from my GT-I9100 using XDA App
Oh! And you need to push EGL libs from Nexus One.
/system/egl
Sent from my GT-I9100 using XDA App
No. They are not compatible with the default gralloc module.
How did you get touchscreen to work? I am working on ICS port and wanted to know.
How can I make a zip package from your sources?
whooa. how you guys got touchscreen working please share
I'm looking for devs with NDK experience. PM me please if you can help.
Might have found a solution to the slow emulated graphics.
dr1337 said:
I'm looking for devs with NDK experience. PM me please if you can help.
Might have found a solution to the slow emulated graphics.
Click to expand...
Click to collapse
Sorry, I cant help, but if there is any other thing maybe i can...
Finally with a CM7.1 package i can boot this, but have you wifi working?
im working on this aswell.
DJ_Steve said:
im working on this aswell.
Click to expand...
Click to collapse
is ts working for you ?
Same question for touchscreen guys
I have it working on my HD2 but it has some stupid screen pointer I have to drag through the screen...
I needed a working cifs module for my view and decided to provide modules that people in the other thread were looking for as well.
cifs performed well in both kernels. References to slow_work have been removed.
Honestly, I didn't test tun.ko or nls_utf8.ko other than to make sure that they went through insmod with out any errors. The HC kernel seems to already have tun compiled in to the kernel as the dmesg error said it already existed. YMMV.
I based the update zips off of LeeDroid's last go at it, so thanks to him for that.
With this, the update zips support init.d, but unless you have it, you'll have to do an insmod when needed. I use CIFSManager from the market for cifs. Be sure to go through the settings to load the module as needed.
Here are the goodies:
For GB - Kernel 2.6.35.10-g5b3e78b:
flashable zip here (updated link 3/24/13)
includes:
cifs.ko
tun.ko
nls_utf8.ko
For HC - Kernel 2.6.35.10-g238a0bf:
flashable zip here (updated link 3/24/13)
includes:
cifs.ko
nls_utf8.ko
(does not include tun.ko for reasons stated above)
You're on your own with these from now on. Good luck!
FrakMe
PS: if the links die again, just send me a pm to let me know.
FrakMe said:
I needed a working cifs module for my view and decided to provide modules that people in the other thread were looking for as well.
cifs performed well in both kernels. References to slow_work have been removed.
Honestly, I didn't test tun.ko or nls_utf8.ko other than to make sure that they went through insmod with out any errors. The HC kernel seems to already have tun compiled in to the kernel as the dmesg error said it already existed. YMMV.
I based the update zips off of LeeDroid's last go at it, so thanks to him for that.
With this, the update zips support init.d, but unless you have it, you'll have to do an insmod when needed. I use CIFSManager from the market for cifs. Be sure to go through the settings to load the module as needed.
Here are the goodies:
For GB - Kernel 2.6.35.10-g5b3e78b:
flashable zip here
includes:
cifs.ko
tun.ko
nls_utf8.ko
For HC - Kernel 2.6.35.10-g238a0bf:
flashable zip here
includes:
cifs.ko
nls_utf8.ko
(does not include tun.ko for reasons stated above)
You're on your own with these from now on. Good luck!
FrakMe
Click to expand...
Click to collapse
So do these work or are you just posting them to let people build off of?
Thank you sooo much.
Works on my stock HC.
Been waiting a long time for this. My view is finally perfect.
spartan1987 said:
So do these work or are you just posting them to let people build off of?
Click to expand...
Click to collapse
They work, at least as far as I can test tun and nls_utf8.
I'm using the cifs module now on my hc view.
I just don't plan to do a lot of maintenance/updates on them. I used the flyer hc and view gb kernels from htcdev, if you were wondering.
x51 said:
Thank you sooo much.
Works on my stock HC.
Been waiting a long time for this. My view is finally perfect.
Click to expand...
Click to collapse
Your welcome.
I'm glad someone besides me found them useful.
I reverted my View running ViperRom to Stock GB and these modules are working.... I am restoring my apps from a TitaniumBackup directory on a WDMyBookLive now! Thanks so much!
For those of you that have the openvpn working, can you get all your internet traffic routed thru the vpn tunnel? I install the openvpn-installer-0.2.4.apk and openvpn-settings-0.4.9.apk, got error and couldn't connect. I then substituted the openvpn binary from the openvpn-static-2.1.1.bz2, and am able to connect to the openvpn server, but I keep getting the "connecting" or "connected" message in the status bar, and all my internet traffics don't seem to go thru the tunnel. Anyone has the same problem?
I have a View running HC at the moment.
coolbird said:
For those of you that have the openvpn working, can you get all your internet traffic routed thru the vpn tunnel? I install the openvpn-installer-0.2.4.apk and openvpn-settings-0.4.9.apk, got error and couldn't connect. I then substituted the openvpn binary from the openvpn-static-2.1.1.bz2, and am able to connect to the openvpn server, but I keep getting the "connecting" or "connected" message in the status bar, and all my internet traffics don't seem to go thru the tunnel. Anyone has the same problem?
I have a View running HC at the moment.
Click to expand...
Click to collapse
This isn't the place for that question. Might want to try the Q&A board.
Does anyone still have a copy of these? Specifically the HC ones? Original link no longer works. Thanks.
tselling said:
Does anyone still have a copy of these? Specifically the HC ones? Original link no longer works. Thanks.
Click to expand...
Click to collapse
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
FrakMe said:
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
Click to expand...
Click to collapse
Thanks.
---------- Post added at 05:37 PM ---------- Previous post was at 05:14 PM ----------
FrakMe said:
Sorry for the wait, I don't frequent this forum.
I re-uploaded the files to a new host and updated the links in the OP.
Good luck.
Click to expand...
Click to collapse
Hi, The Honeycomb file appears to be the wrong one. Its and exe file and when opened doesn't have the drivers.. has some other stuff. Could you check on that please. Thanks..
tselling said:
Thanks.
---------- Post added at 05:37 PM ---------- Previous post was at 05:14 PM ----------
Hi, The Honeycomb file appears to be the wrong one. Its and exe file and when opened doesn't have the drivers.. has some other stuff. Could you check on that please. Thanks..
Click to expand...
Click to collapse
The link does indeed go to the correct zip file. View-stock_hc-CIFS-UTF8-FrakMe.zip
Use the "continue as free user" option on sockshare instead of the top one with their downloader.
from the init.d scripts section of this thread: forum.xda-developers.com/showthread.php?t=1227269
which ones can i run on a stock locked rooted prime? i think stock doesnt support init.d scripts but theres a tutorial on how to enable it but i dont know which ones from the thread would work. i hope to get some responses because every time i post a question i get more views than replies. thanks
fcortes626 said:
from the init.d scripts section of this thread: forum.xda-developers.com/showthread.php?t=1227269
which ones can i run on a stock locked rooted prime? i think stock doesnt support init.d scripts but theres a tutorial on how to enable it but i dont know which ones from the thread would work. i hope to get some responses because every time i post a question i get more views than replies. thanks
Click to expand...
Click to collapse
The stock kernel won't execute init.d scripts so none of them will work for you.
And since your prime is still locked you can't install a different kernel.
Therefore your decisions is first to unlock then install a custom rom (most include a kernel that supports init.d). Then you can spend time checking out various scripts.
djmcnz said:
The stock kernel won't execute init.d scripts so none of them will work for you.
And since your prime is still locked you can't install a different kernel.
Therefore your decisions is first to unlock then install a custom rom (most include a kernel that supports init.d). Then you can spend time checking out various scripts.
Click to expand...
Click to collapse
oh ok. i saw a post somewhere where it showed how to add init script support to stock roms. thanks for the reply. ill just find another way to add more points to my benchmark
fcortes626 said:
oh ok. i saw a post somewhere where it showed how to add init script support to stock roms. thanks for the reply. ill just find another way to add more points to my benchmark
Click to expand...
Click to collapse
You won't get a great benchmark with the stock rom I'm afraid... too much crap is going on and the kernel is not very quick.
djmcnz said:
You won't get a great benchmark with the stock rom I'm afraid... too much crap is going on and the kernel is not very quick.
Click to expand...
Click to collapse
i got a 10960 mostly all higher scores are from overclocking it
djmcnz said:
The stock kernel won't execute init.d scripts so none of them will work for you.
And since your prime is still locked you can't install a different kernel.
Therefore your decisions is first to unlock then install a custom rom (most include a kernel that supports init.d). Then you can spend time checking out various scripts.
Click to expand...
Click to collapse
That is a large bummer. I'd like to run some init.d scripts (primarily to run crontab), but the unlock tool isn't working on my Prime (unknown error nonsense).
cmckitterick said:
...the unlock tool isn't working on my Prime...
Click to expand...
Click to collapse
That's a larger bummer... :crying:
And I read that ASUS won't provide a path to resolution? Sucks.
Hey guys, my question is essentially what the title says. I find that in CM10 based roms, that whenever I use the stock cyanogen mod browser, it automatically goes into desktop mode (and is stuck there. The desktop mode checkbox, however, is unchecked.) I'm fairly sure it worked before I used the touch pad fix here - http://forum.xda-developers.com/showthread.php?t=1893343 - So I think it might be a framework/build.prop issue, but I'm not sure. I've been looking to fix this problem everywhere but haven't really been able to find a solution. Do you guys have any idea what the fix might be?
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
smokerman said:
hey..this was better on general section or in some thread..i remember you posted this on one of the roms..but seems to be a general cm10 problem..so maybe better install another browser for your needs.
Click to expand...
Click to collapse
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
fishvtt said:
Oh I asked in your racing jb rom thread, but now I'm trying to make a cm10 based rom of my own, and it seems that after testing many other Cm10 roms, everyone has this issue. But I think it's a build.prop thing, cause I'm sure that before, on Sonygenmod Cm10, it worked normally, but after I applied the touchpad fix, that's when it started messing up.
Since this is more of a universal problem, I thought all the devs here might have some insight on a fix for this.
Click to expand...
Click to collapse
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
smokerman said:
even with FXP rom you have this issue..and it doesnt have touchpad fix..so cant be caused by that.
Click to expand...
Click to collapse
Hey, smokerman, would you know how to mess with .jar files. I kinda want to go exploring to see if I can do anything.
you have here a simple guide by @CriGiu
http://forum.xda-developers.com/showthread.php?t=2322231
could help you.:good:
fishvtt said:
Oh ok guys, I can confirm that this is a framework problem. Not a build.prop problem. To figure this out, I used four different versions of the sonygen cm10 mod. First version was with old build.prop and old framework, witch worked fine, and the second was with old framework, but new build.prop, which also worked fine. New framework, old build.prop did not give me the mobile version of google, however, as long with the new build.prop, new framework.
So now, we just need to find out what exactly is wrong with the new version of the framework. I feel like the new framework causes the phone to look like a tablet to the cyanogenmod stock browser, but I'm not sure.
With this post I have attached both the new framework, and the old framework, if anyone else wanted to run any tests on their own. (or figure out what's wrong).
I can also supply both build.prop's if you guys think it's necessary.
I should also say, that this is an issue, for without the new framework, touchpads won't be able to work. So if anyone can help modify the new framework or anything, I would really appreciate the help.
Click to expand...
Click to collapse
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
Oh ok, I'll try testing that out.
CriGiu said:
The framework inside the patch in the first post of sonygenmod solves that issue
(it was caused by an older framework)
Click to expand...
Click to collapse
All right, well that seems to do the trick. When I try to use the touchpad activator app, it gives me the "error 5 expected reciever of type android.view.ViewRoot, but got android.view.ViewRootImpl". But, Dead Trigger works perfectly how it's supposed to, and the stock browser is using the mobile version now. Just remember to make the necessary build.prop changes as outlined in Fahrenheit's guide.