yashsingh1/xdaforums huggingface dataset:
[Folio 100 Android Development] Dexter_nlb:
I'm personally looking forward to your great release of a fully compatible kernel of 2.6.36.3 with full driver support and LCD display driver included..

great news, you're the man! you know what others don't :-)
[Folio 100 Android Development] Kervala:
Android resolution is not "fixed", HC adapts itself to what you're using :)

If you're in 1024x600, HC will work in 1024x600 (just test with emulator and you'll see it works).

Currently, we are stuck with 2.6.32-9 provided by Toshiba but nobody knows if HC is able to run with this kernel version, but it could be possible :)
[Folio 100 Android Development] roglio:
I don't think so: if you run HC emulator in 1024x600 you will see a cropped desktop.
[Folio 100 Android Development] Kervala:
Only a part is cropped at the top left side and I think it's fixed in real HC (not emulator) :

http://kervala.net/download/1103181033_device_hc.png
[Folio 100 Android Development] Sinate:
I mean for toshiba it's easy, but they don't do-> Money, it's better for toshiba to release a new revision of the folio with honeycomb to win more money
[Folio 100 Android Development] Sinate:
Both working on Tegra 2 (different driver because of honeycomb) sure, different display is normal, i only talk about Tegra 2... if XOOM can work on honeycomb, folio 100 can work on it too...

The most important is the Tegra 2, the resolution, drivers, etc can't be a problem for toshiba
[Folio 100 Android Development] Kervala:
Did you check Toshiba kernel ?

A lot of drivers we are using are not provided in kernel 2.6.36 (the kernel which is used by Xoom).

Dexter tried to backport them but it seems like some interfaces changed.
[Folio 100 Android Development] Sinate:
Like i said before, i'm not talking about myself but i'm talking about toshiba can do it if they want to do it, it's just a question of time or they can make a hybrid kernel, i don't know.

Don't have any SDK Folio 100 ? and SDK XOOM ?

Did you see you can launch honeycomb on a Desire HD ?
[Folio 100 Android Development] Kervala:
Toshiba confirmed Folio 100 won't be ported to HC.

We just have kernel sources because they are GPL and any modification must be made public. Android Framework released by Toshiba is the same as on nvidia git and since it's not GPL they don't need to release it. All other modifications are not released neither (they fixed the size of wallpapers for example).

If you prefer HC without any hardware acceleration, that's your choice :) But when I bought my Folio 100 it was for its hardware capabilities. And btw HTC doesn't have the same policy as Toshiba concerning open source and I didn't know HTC Desire HD was a Tegra 2 device :p
[Folio 100 Android Development] Sinate:
Hardware acceleration -> SDK Tegra 2, it's really impossible to use it for that... i don't think so...

Impossible don't exist on a Open source

I don't mean Desire HD is a Tegra 2 Device ! it's just a example, HC on HTC desire HD (Different resolution, memory, CPU) and when you know HC is more for Tegra 2...

Policy of toshiba, it's just policy...

Are you sure don't have GPL Tegra 2 ? check in here

http://www.codon.org.uk/~mjg59/android_tablets/
[Folio 100 Android Development] Kervala:
I abandon, you don't even read and understand my responses...
[Folio 100 Android Development] mblaster:
Writing > Reading :p

No, seriously, I would preffer to see this thread back on topic instead of discussing if toshiba should do this or that.
[Folio 100 Android Development] Sinate:
I understand, it's you don't want to realize, the port of HC is completly possible, we have access to every information of the Folio 100 and how to make something strong.

Now Dexter is not the only person need to work on it, that is more the problem, the Folio 100 community is not the same as the HTC community, that's why you don't see anybody take risk to make something.

Toshiba probably have all to launch HC on folio 100, but don't make any sense for this compagny to release that, need to win money, what is the better way for Toshiba ? take care about a old product or launch a new product with everything on it ?
[Folio 100 Android Development] Kervala:
I noticed nvidia added new files to support PAZ00 board which seems to be used by Toshiba AC100 :

+config MACH_PAZ00
+ bool "Paz00 board"
+ help
+ Support for the Toshiba AC100/Dynabook AZ netbook

See commit : http://android.git.kernel.org/?p=ke...5;hp=c871fe663a6368fd0e98f5a3bfd81b0b9c591266

Perhaps it could work with our Folio 100.
[Folio 100 Android Development] Sinate:
It works on Folio ;)
[Folio 100 Android Development] Dexter_nlb:
so 2.6.36.3 is running on folio now?
[Folio 100 Android Development] Sinate:
I guess yes, the AC100 work on it, don't have any reason the folio don't work ;)
[Folio 100 Android Development] Dexter_nlb:
could REALLY be nice.. so we can make honeycomb run on our tablet..

atm, i dont have the env in place, but im sure ill reconfigure the following week if its true.. because its probably just taking the config.gz from xoom, and disable xoom hardware and then enable this instead to begin to have board support, then at least taking it from here..
[Folio 100 Android Development] Dexter_nlb:
actually that means AC100 can get Honeycomb now? im sure such a custom mod, would be greatly appreciated :-) to begin with...
[Folio 100 Android Development] Sinate:
I don't have AC100, but a friend have the AC100 was compiling a rom yesterday with the new git from NVIDIA and like he said to me, it works really good but some bugs need to be fixed

Probably gonna release in here http://tosh-ac100.wetpaint.com/

You can see some people working on 2.6.39 already, check the work of Colin http://www.mentby.com/colin-cross-3/arm-tegra-updates-for-2639.html
[Folio 100 Android Development] DerArtem:
Have you compiled it?

Can you share your .config?
[Folio 100 Android Development] Sinate:
I didn't compile, it was a friend who did it for his AC100, but it works for sure ! remember the Folio 100 is a AC100 without keyboard :)
[Folio 100 Android Development] Dexter_nlb:
so can you get your friends compiled kernel, so we can test it on our folio?

since you heard it works, it will be easier to check a confirmed version, than experimenting alot more to get there.
[Folio 100 Android Development] Sinate:
I already asked him, he needs to fix some bugs and it will put online directly after that.

But apparently the last git are helpfull, you can make by yourself too

I will check if i can do something.
[Folio 100 Android Development] DerArtem:
No, the hardware is different. The AC100 kernel does not boot on the Folio ...
[Folio 100 Android Development] Topogigi:
I can confirm this. It does not boot...
[Folio 100 Android Development] Sinate:
Hardware is different, where ? the Kernel from the AC100 can boot on Folio 100,

but you need to change some stuff (about the screen configuration)

I can confirm the kernel of AC100 boot on Folio 100, you just need to change the system configuration of the screen !
[Folio 100 Android Development] Dexter_nlb:
at least i can confirm the screen driver is very sensitive.. i tried to add another "touch" to its 4 touch screen, and kernel didnt boot, although it says max 5 is supported in the kernel, the driver ****ed up. so if the driver from ac100 does not do touch at all, thats probably one good reason its not booting.

but then, we're back to sq.1 with a non-booting honeycomb kernel.. and drivers need porting. no news on that one..
[Folio 100 Android Development] Sinate:
You need a alternative screen driver compatible honeycomb, the problem is more the screen driver from toshiba make trouble for compile something strong, you can check my problem, look like the 4 touch screen don't exist on my folio.

http://kotelett.no/ac100/phh/ this kernel AC100 boot on Folio 100, it was for Ubuntu

Make a hybrid, take the screen driver from Ginger and use it with the git of the AC100 to launch honeycomb on Folio 100
[Folio 100 Android Development] MrMEEE:
Does anyone have a config-file that's working for the git 2.6.36??

Then I will try to implement the gingerbread driver..
[Folio 100 Android Development] mblaster:
I found some development on the paz00/ac100 kernel here on gitorious:

http://gitorious.org/~marvin24/ac100/marvin24s-kernel

They develop for chromeos, but still it might be a valuable ressource. There is also a paz00_defconfig in the /arch/arm/config folder, might be something to start from.
[Folio 100 Android Development] weeds2000:
today I received the source for the Toshiba Kernel. It turns out that it was the same version we already had. The archive was created on November 12th 2010.

I tried to build the kernel and booting the system got stuck in the 2s elapsed in InitFifo; is daemon started?

However the kernel booted and the screen turned on. (It still was completly black of course)

I know have pushed many of the system binaries and libraries from the latest stock ROM to my device and I can boot the self compiled kernel, as well as kernels previously posted in this thread.

ATM I'm not sure if toshiba has even updated the kernel for their latest release. It seems that some Nvidia userspace libraries got mixed up or something,

I'm suspecting nvrm_daemon together with the graphics subsystem. As when the boot failed, I was missing the following messages from logcat:

03-20 21:02:37.753: DEBUG/(940): NvGrFbDevOpen: Opened fb0 on disp 0 size 1024x600 format 1 rate 73.000000

03-20 21:02:37.763: INFO/tosfb(940): waiting connection...

It seems that the tosfb was not able to connect to the framebuffer device before, therefore the screen stays dark.

system_server, mediaserver and tosfb entered the above mentioned loop.

I cannot say which files exactly caused the problems, as I have pushed nearly the whole system/bin and system/lib directories to the device.
[Folio 100 Android Development] nopy:
If someone can try my kernel from https://github.com/nopy/kernel_folio100/commits/android-tegra-2.6.32-betelgeuse/ and run it on foliomod 1.4. I build my kernel from here and i actually have cyanogenmod running with the binaries from foliomod 1.4

I am completly wrong or too tired ... i just messed up my files, nvrm_daemon i used is from 1.3 ;(

sorry for the noise
[Folio 100 Android Development] Dexter_nlb:
the have updated the kernel for sure... if you look at it in a different way..

put the kernel on 1.3d foliomod, and its still not booting.. because the nvrm_daemon is also old...

if you use the new "nvrm_daemon"(1.4) on 1.3d it can be made to work, as nvrm_daemon opens your screen..

tosfb only handles the dump of framebuffers for framegrabber apk..thats is primary function.

but new kernel + new nvrm_daemon is a good combo.. newkernel old nvrm_daemon is not a solution..
[Folio 100 Android Development] Sinate:
I have some good news !

Android 3.0 on Folio 100 is coming.

Toshiba will release a new major update !

Anyway the next Acer tab 100 is a 7inch tab with exactly the same resolution, same ram, same chip than the Folio 100 and released with Honeycomb !

Iconia Tab A100
[Folio 100 Android Development] roglio:
Where do you heard it?
[Folio 100 Android Development] Kervala:
Source please ? :)
[Folio 100 Android Development] Sinate:
From a dev NV.

And you can see the last update of Tegra 2 HC was yesterday

http://android.git.kernel.org/?p=ke...;hb=refs/heads/android-tegra-2.6.36-honeycomb
[Folio 100 Android Development] mblaster:
??? Head of android-tegra-2.6.36-honeycomb is still at a commit from 2 weeks ago. Actually your link leads to that (old) commit.
[Folio 100 Android Development] Sinate:
Check in here http://android.git.kernel.org/?p=kernel/tegra.git;a=summary

Check the last update of Colin Cross
[Folio 100 Android Development] Dexter_nlb:
i doubt acer is so stupid to release a 7" tablet with all the sad hardware problems as the folio, and even one that no one buys since rumour then gets to be "its a folio, beware!"..

but for me its sounds like you seem to make all tabs "common", but in fact they use different vendors for displays,wifi/bt,sensor .. so it might be a tegra2 based solution, but a world of difference when you look at it more closely, and i dont think you got the details yet..
[Folio 100 Android Development] Sinate:
The wifi/bt and sensor look like common and the screen look like same, same problem of angles :)

http://www.youtube.com/watch?v=v-JET0WjHhU
[Folio 100 Android Development] mblaster:
Already checked there,too. But none of Colin Cross's commits of the last 2 days are related to the folio. In fact, the latest commit is a simple merge of linux-tegra-2.3.36 into android-tegra-2.6.36 ...
[Folio 100 Android Development] Sinate:
I didn't said is related to the folio, i said is the last update of HC on Tegra 2
[Folio 100 Android Development] dpaganello:
The visual screen angle of this device is amazing compared to Folio :-(
[Folio 100 Android Development] Sinate:
Are you kidding ? it's the same one... it's because the screen size is smaller look like better...
[Folio 100 Android Development] Kervala:
Tegra 2 or Folio 100 ?
[Folio 100 Android Development] mp1405:
Sorry for reading Android 3.0 on Folio

Sorry for reading "Android 3.0 on Folio 100"
[Folio 100 Android Development] Sinate:
Android 3.0 on Folio released by Toshiba soon (next month)

And i talking about the last update for Tegra 2 !
[Folio 100 Android Development] ma1999:
Android 3.0 on Folio 200 released by Toshiba soon,

Android 3.0 on Folio 100 doubtfull.
[Folio 100 Android Development] Sinate:
If you want... i know what i'm talking about thanks, damm did you know Android 3.0 is just a OS ?!

Toshiba will release soon Android 3.0 update on Folio 100

The Folio 200 is like iPad 2, a new tablet

Old Galaxy TAB gonna have Android 3.0

Acer Iconia TAB 100 (same stuff of Folio 100) gonna have Android 3.0

Hannspree announce the update Android 3.0 on Hannspad (same stuff of Folio 100)

Toshiba want to Apologize for everything happen on Folio 100 and would release Android 3.0 on it

You know Android 3.0 is a OS, is open source... remember that !
[Folio 100 Android Development] Homer314:
Source ?
[Folio 100 Android Development] ma1999:
Please, I really want Honeycomb to my Folio, and from Toshiba would be really great. But Toshiba UK has stated that Folio 100 will not get Honeycomb and Google has stated that Honeycomb devices must have better screen resolution and two cameras (and other stuff).

So, I and probaby others wants official Toshiba confirmation to belive it.

And please let it be true :))
[Folio 100 Android Development] DerArtem:
Guys,

we are talking about kernel development and not about manufacturer support here...

I would like to tell you that I got kernel 2.6.36 running on my folio. Also the screen initialized. I need some more time for the tests ....
[Folio 100 Android Development] Topogigi:
Great news indeed. Waiting for more....
[Folio 100 Android Development] Kervala:
Yes, really great news !

Are non ODM_KIT drivers working with our Folio 100 ?
[Folio 100 Android Development] ma1999:
Correct, bad of me.

Is the 2.6.36 the kernel Honeycomb uses ?

Will the (things I miss most in FM 1.4) drivers/support for 3G and NTFS compile right out of the box or will they have to be modified (for a possible FM 1.5 w Android 2.2)
[Folio 100 Android Development] mblaster:
Good News: Got overclocking to 1.4GHz working! Atm. cpufreq is broken, so no dynamic clocking or setcpu ...

Linpack went up from ~37 to ~52 Mflops, which is exactly 1.4 times better.

Will push to my github as soon as I got the stuff cleaned up and, perhaps, cpufreq working again. For the impatient ones I attached a boot.img (€: for CM7) which may blow up your device ... The zip is NOT FLASHABLE, extract and use fastboot. To try just boot it via fastboot boot boot.img.OC.

€€: Quadrant ramps up from 1900 to 2600, impressive.

€€€: https://github.com/mblaster/linux_2.6.32_folio100/commits/Folio100-2.6.32.9-OC

cpufreq still broken, perhaps it would be better to port only some changes from cpu-tegra.c to the old cpufreq.c ... Got no mor time today, but feel fre to play around with the code. If it does not boot or you want a higher oc play around with the value of the last commit.
[Folio 100 Android Development] Dexter_nlb:
@mblaster

I tested the zImage itself with foliomod, and its not booting :-(

and here i mean i extract zImage and repacked new boot.img.
[Folio 100 Android Development] mblaster:
Which Foliomod version? Should work with 1.3 as not much has changed from stock kernel ...

I attached a zImage with a lower oc (1.2 GHz), maybe your board cant handle 1.4 GHz? Mine crashed randomly during boot at 1.5 GHz.

€: Would be nice if somone could confirm that my boot.img works with cm7.
[Folio 100 Android Development] Dexter_nlb:
i am using FolioBlur actually (which is originated from 1.4) but no matter if framebuffer is wrong or not, im still not getting to my adb shell at all.

which i can with 1.3 kernel (which im trying to get running with 1.4 mod)
[Folio 100 Android Development] kepler1982:
LOL! You're forgetting that toshiba has to use time and resources on making functioning drivers and a framework for 3.0... something they most certainly will not.
[Folio 100 Android Development] Dexter_nlb:
now it loads, but?

Processor : ARMv7 Processor rev 0 (v7l)

processor : 0

BogoMIPS : 1998.84

processor : 1

BogoMIPS : 1992.29

seems to me its not oc'd?
[Folio 100 Android Development] mblaster:
Perhaps it somehow relies on a working cpufreq driver? I will look into it tomorrow and try with Folioblur myself. No more time today, real life is calling...
[Folio 100 Android Development] mblaster:
Try some benchmark. This somehow is reported incorrectly. Had the same issue.
[Folio 100 Android Development] castle972:
Hi, can you explain to me how to use this kernel, like an update? or i put it in an update before flashing? thanks in advance.
[Folio 100 Android Development] guiooom:
..it works with folio mod 1.4?
[Folio 100 Android Development] mblaster:
It is not usable like an update.zip by intention. It is at the moment just a proof of concept/test and not ready to be used widely (may cause some crashes etc...). Please just be patient until a more advanced version of this is ready.

I guess not. If you extract the zImage from the boot.img and repack it with a Foliomod 1.3x ramdisk you *might* be lucky. But be aware of what I said above.
[Folio 100 Android Development] guiooom:
:) thank .
[Folio 100 Android Development] mblaster:
Huge advances on the overclocking front!

Got it working now with functional frequency scaling. You can write min/max values for the scaling to the sysfs interface and they are obeyed. Setcpu still does not work correctly. It shows the right maximum frequency, but allows only max values of 1GHz. I dont know why.

The value for 'cat /proc/cpuinfo' seems to be calculated once on boot as it does not vary over time (2nd cpu can have a different value, but this one is also constant).

My Folio is now running at 1.5GHz with a slight Overvolting of +50mV (roughly +5%).

zImage and boot.img for CM7 (1.5GHz//1150mV) are attached. If I find some time I will add a flashable zip later (both zipfiles are not flashable).

!!! Disclaimer: This kernel overclocks and overvolts your device! Your Folio might fry/explode/get damaged! Use At your own risk!!!

€: The changes are on my github already.
[Folio 100 Android Development] Dexter_nlb:
A now it works with FolioMod too :-)

Thanks Mblaster!!

here is the update.zip for Folio1.3 (does NOT work with 1.4)

test scores

LINPACK: 53

Quadrant score: 3750

after some more testing, seems 1.5Ghz is not fully stable :-( , sometimes hangs when going into wifi, and wifi does not seem to work at all (also known from XOOM i think when oc'd)

so it works for benchmarking, but i think less speed for daily use..
[Folio 100 Android Development] castle972:
anyone want explain how i can try this kernel?

thanks for your previous reply.
[Folio 100 Android Development] mblaster:
If you use Foliomod 1.3 (!!! NOT 1.4 !!!) just flash Dexters .zip via recovery. If it does not boot or give random hangups under load then there is a good chance that your cpu can't handle 1.5GHz, as the kernel defaults to that frequeny.
[Folio 100 Android Development] castle972:
excuse me im too speed and i never saw it was a flashable zip. Now with folio mod 1.3 i using it (the kernel). But i can test with quadrant. Quadrant have a bug and wont to test my cpu it jump the test and tart with graphic test. So it was the same with folio mod 1.4. do you know why.
[Folio 100 Android Development] castle972:
after many reset quadrant run all tests and show 4183pts...ya man...thanks for participated.
[Folio 100 Android Development] mblaster:
Yesterday I came across this posts of mich059 (thank you) in the gerneral section, which point out a workaround for the SOD problem:

I guess it is more probably related to the cpu voltage at the corresponding frequency, than to the frequency itself. I think that the cpu sometimes fails to re-initialize its clock after waking up from sleep mode and hope that a voltage bump can solve this. If not, I could remove the lower frequencies entirely.

I made a zImage and boot.imgs for CM7 and Foliomod13 with bumped voltages for the lower frequency range. Would be nice if someone could make a flashable zip of the stuff to make it availlable for a broader range of testers (I have no access to zipsign atm, ain't at home).

Be aware that the immages are all overclocked to 1.5GHz and overvolted. The max voltage is even a bit higher than in the last OC image.

Please supply lots of feedback if it is working. I will also try with my own folio, but the SOD is a rare issue with my device. I guess SOD varies with each chip.

As always, changes are on my github.
[Folio 100 Android Development] Topogigi:
I'm sorry I can't test it ATM cause I'm on Foliomod 1.4, but really hope you could solve this issue.
[Folio 100 Android Development] Dexter_nlb:
I cannot test your new atm, as i am trying to get the Atrix webtop app to run on our folio and elocityA7, so we can run ubuntu AND android, just like its done on atrix4G, its sooo cool! (of course on our setup it will need a bluetooth keyb and mouse)

but running linux full workstation + android tab is nice.

so far the mediacenter works now. so folio is a remote and through hdmi is the actual mediacenter screen, so 2 different screens coming from your folio output :-)

i will see if the xoom kernel might have some extras to support the framebuffer for linux, that might be missing, so i can recompile the 1.3 kernel and add linux support (hopefully) which is another kernel trick.
[Folio 100 Android Development] xitrumch:
Wow, Ubuntu + Android on Folio tablet? How is that for awesomeness!!!!

I can surely show it off and laugh in front of those who own Xoom or Ipad 2, lol ;))
[Folio 100 Android Development] Cpasjuste:
Id like to port my "Pimp My CPU" application (search this forum for it) to use your kernel fully! If someone have a spare folio to send me :p
[Folio 100 Android Development] DerArtem:
Kernel 2.6.36

Hi,

sorry, but I had no time during the last days.

Here is how to compile kernel 2.6.36 for the folio:

http://pastebin.com/LZJY7XH3

1. Get the sources:

git clone http://git.chromium.org/git/kernel-next.git

git checkout origin/chromeos-tegra-2.6.36

2. Apply the diff.

3. Compile the kernel

Here you can see the kernel booting:

http://pastebin.com/KcBgvX8P

What I have not managed is to get the android kernel running. It is not booting yet. Only the chromeos kernel is working so faar...
[Folio 100 Android Development] CA3iR0:
I can only hope honeycomb to come to our folios! :rolleyes:

2.2 really sucks on tablets.
[Folio 100 Android Development] DerArtem:
Hi,

I have finally got some breakthrough on the kernel development.

I will create a git repo soon with the 2.6.36 honeycomb kernel for folio 100.

So faar I got video and internal flash memory working, but there is still a lot of work to do...

At least I am starting to understand how the kernel is working internally and how to port it to the folio :)

The ac100 guys - especially marvin24 have helped me out a lot in the area...
[Folio 100 Android Development] Kervala:
Great job :)

So are we stuck with odm_kit drivers or can we use the standard ones ?