yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] ani55:
How does it know the resolution of my screen and the cm7 one. Because in your hc build prop( which is a lot more organised) It has resolution and everything?
[Galaxy Tab  Android Development] ani55:
Thank you very much, hopefully we will then release a test version. :)
[Galaxy Tab  Android Development] mssmison:
Quick note, make sure that the new kernel/initrdfs uses the proper new class statements in the *.rc files, there's been a change to that.

Secondary, getting the system to boot isn't terrible once you have the right class statements and new services loading in the init.rc. There will be challenges however with networking due in part I beleive to the sdk build most are sourced from.

I spent some time playing with it the other day, and waiting for the source is the best idea. You'll probably get it booting, but would want to have the source to make some of the changes requried to really get it working more than 80%.

I totally appluad you guys for starting on this though :) Good to see.
[Galaxy Tab  Android Development] ani55:
Get mssmison, good to see you back! I am following your porting guide, but is the build.prop the only thing that you need to edit when you port from device to device.

Btw I am porting from nexus s. :)
[Galaxy Tab  Android Development] cminion:
has anyone tried the kernel from the HC build? Just a stab in the dark but that could at least provide a starting point

Im also starting to take a look at this but im more of higher level software guy
[Galaxy Tab  Android Development] ani55:
I need someone to build a kernel please
[Galaxy Tab  Android Development] TheGrammarFreak:
Woah, changing the DPI to 160 is sweet. :D Nice find.

You also get a different set of default wallpapers...
[Galaxy Tab  Android Development] eboIa:
Yes!yes!

This is what I wrote 1-2 days ago here at:

http://xdaforums.com/showpost.php?p=19600531&postcount=189

I'm glad to see that somebody tested the enviroments of it, as we need real tablet interface, instead of phone like.

I think we don't need soft buttons, the duplicated features (as we have dedicated 'buttons') totally not needed, and we get some more space without it also.

Hope you could finish this way and we will get an errorless interface!

Thanks for everybody on this thread!
[Galaxy Tab  Android Development] kay_kiat88:
Yeah I saw your post, that's why I tried it! Not sure if the on-screen buttons can be done away with as it is (I think) deeply integrated with SystemUI. I may be wrong though.

@TheGrammarFreak

lol yeah. You get honeycomb wallpapers lol. But the tablet UI on our SGT 7.0 does look really sweet eh.
[Galaxy Tab  Android Development] eboIa:
One litle bit over-thought of my previous post, wereally do not need soft buttons, and Google told also that the usage of those are not must feature, so the OS compatible with devices with 'hard' buttons, without any duplicated elements... but as the soft buttons on tablet layout are on the statusbar (instead of discrete button bar what we got on phone layout) we neede to use it and in practice it is not a real problem. In this case the only bas side of it, that we will have hard and soft buttons on the device with almost the same functions, and the global visual apperiance is also bad as we can see same symbols on status bar, and on hard buttons also... Could it be any possibilities to switch of soft buttons from statusbar, as we could not delete the hard buttons:) Any opinions?

Thanks for your works again!!!

Maybe you could start a check-list on this topic that what features working or not yet... and could be corrected on every step forward.
[Galaxy Tab  Android Development] bullyfrog:
Actually, call me crazy, but the hard buttons get in the way when playing games or in landscape. I was actually thinking the opposite..Turn the hard buttons off completely.. No lights, nada..this allows us to grip the tab better (while in landscape). Anyway, i think we're getting way ahead of ourselves. Lets give the devs room to iron out the bare essentials first. The objective should just be getting a usable daily..but i do wish a dev one day (i am patient) feels the same as me and compiles a rom like that :)
[Galaxy Tab  Android Development] adi6262:
I think the same :)

soft buttons better.
[Galaxy Tab  Android Development] ani55:
I think that is a very good idea :)
[Galaxy Tab  Android Development] AnttiV:
I'm all for this also. Although at first I was in love with the hard buttons, I've come to dislike them mostly. They are always in the way and a small careless grab of the tab and whoosh! you're back to the home screen. After getting my 8.9 Tab I grew fond of the soft buttons *very* quickly. I think it would be for the better to do away with the hard buttons for good and just use the soft buttons. The freed "area of grabbing" would be a bigger plus (imo) than that of losing the functionality of the hard buttons.
[Galaxy Tab  Android Development] Angel_666:
Funny, but Honeycomb users hate this soft buttons, coz it take part of screen.. As for koxudaxi build - the black stripe is because system don't know, that we have hard buttons, and don't know how to use it. USR folder with correct keychars and keylaout from Tab, and new framework-help to fix this. I'm say again - 90% of needed libs and drv are finished and lay in public access. But they don't work properly until we tune init.rc, init.smdks5pc110

and build.prop. If we tun it - we have almost all works.
[Galaxy Tab  Android Development] jaiiscool:
I also love the idea, but would hate to loose the real estate on the gorgeous 7"

And somehow we have got used to holding the tab in a certain manner :)

But if the soft buttons are on the notification bar and not the dedicated strip, then it will be best......
[Galaxy Tab  Android Development] eboIa:
Thanks for the replys!!!

So now what is the conclusion?

HC users hate soft buttons as they eat the screen-space...

(just for info: on watching movies this space is also available, as in this case the movie is can fill the whole screen, just some little point allow to get the soft buttons back... I thing that on any fullscreen app the situation is the same...)

You would like to use soft buttons instead of hard buttons:)

The device have hard buttons so I think this question is not just for the users, but for also the device possibilities...:)

And finally on the tablet layout the soft buttons are on the status bar, so we could not simply switch off, as the status bar is basic needed thing. On phone layout the situation is different, as on that we have dedicated button bar, and dedicated status bar, but we could not use phone layout, as our device is tablet, and all we want tablet specified applications, and layouts...

This last paragraph is the answer I think, so we will get soft buttons, on statusbar in all cases, then we need to paint over (with black) the hard buttons, and use the system how its planned to use.

I just hate the duplicated features, symbols, anyway I like soft buttons, as they are on the same place in portrait and landscape also, so much more comfortable...

Opinions? :)
[Galaxy Tab  Android Development] kay_kiat88:
How bout concentrating on the basics first? Wifi, gsm, bluetooth etc, before fixing UI stuffs.
[Galaxy Tab  Android Development] biffroy:
You're in the news! http://androidcommunity.com/original-samsung-galaxy-tab-joins-the-ice-cream-sandwich-party-20111123/

This is my SGSII. There are many like it but this one is mine.
[Galaxy Tab  Android Development] BulletproofIdeal:
Awesome post mssmison! On a side note I wish that I had the time/knowledge to help out more than bug testing. Hopefully once the semester (4 short weeks away :D) I'll be able to begin reading, learning.
[Galaxy Tab  Android Development] ani55:
@mssmison

do i place this file in file on galaxy tab running ics?

or do i place this somewhere in update.zip, if so where?
[Galaxy Tab  Android Development] Angel_666:
mssmison GOLD Post! Thanks!

It's a sources, bro. Tweaked sources, ithink.. :)
[Galaxy Tab  Android Development] TheGrammarFreak:
It's used at compile time, if you're not compiling it's prolly not of much use to you.
[Galaxy Tab  Android Development] cpgeek:
I couldn't disagree more. they take up valuable display real estate that could be used for a few more lines of resolution of my applications. there are hard buttons to specifically prevent the taking up of precious display real estate. also, those functions really never change. you need each of those 4 functions in whatever application you are working in, so they should be hard buttons.

in the end however, I think it might be a good idea to make this a checkbox in the settings app, or have a dev build a program that makes that change and reboot to toggle.

---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------

Have we verified that this will solve the wifi issue (working build?), and does this do anything for gsm?
[Galaxy Tab  Android Development] ani55:
Thanks, not compiling just replacing libs and stuff

I thought this was source though, it looked familiar.

ANYWAY: New update being uploading, added wifi drivers and a few more system apps i.e file manager, ro manager etc.
[Galaxy Tab  Android Development] TheGrammarFreak:
If there are lib sources in there you can use them, I'm sure. I thought you were gonna just drag'n'drop around. Sorry :o

My mistake
[Galaxy Tab  Android Development] ani55:
Not yet, but I have included rom manager.apk so when wifi works, which will be in a matter of days (or hours!) you will be able to install straight from ICS! :D
[Galaxy Tab  Android Development] ani55:
Rom uploaded!

btw, for anyone who thinks wifi will be working in new release, i don't think so.

we just need to add few lines in source.

I have just added drivers and a few other apps.
[Galaxy Tab  Android Development] kay_kiat88:
@ani55 Did you include the changes by msmission? The build.prop didn't include those changes. Or did I download the wrong ROM lol. hmm I downloaded ani55 test version gt-p1000 ICS v1.zip. Seems like the old rom.
[Galaxy Tab  Android Development] jaiiscool:
Is the new link updated in first post? Or where is it
[Galaxy Tab  Android Development] ani55:
OMG! I can't believe it, i left the old build.prop in the new update :eek:

So sorry guys, will upload on a different website too. :mad:
[Galaxy Tab  Android Development] Angel_666:
22:33:22.157 Info GPS 153 gps_init() : SAMSUNG GPS DRIVER INITIALIZED [Ver 2.0] 2011.03.31)

GPS fixed.

update

22:45:17.345 Debug VoldCmdListener 78 volume mount /mnt/sdcard/external_sd
22:45:17.345 Info Vold 78 /dev/block/vold/179:9 being considered for volume sdcard/external_sd

External SD Fixed :)
[Galaxy Tab  Android Development] EmperorX:
Man.... This is turning out to be an amazing week!
[Galaxy Tab  Android Development] sevensheaven:
when i tryed to install i get E:signature verification failed?

is this because of a stock rom(i have root acces)

regards stef

ps i did rename to update.zip
[Galaxy Tab  Android Development] kay_kiat88:
No not because of that. The zip file is zipped up wrongly. U need to extract the folders inside and rezip it up again.
[Galaxy Tab  Android Development] ani55:
Please replace the build.prop with this one

Sorry!
[Galaxy Tab  Android Development] DaReDa:
@angel,

did you try the wifi thing?

Working GPS and external SD sounds pretty good.
[Galaxy Tab  Android Development] Angel_666:
WiFi is hard thing.. driver works, but can't communicate with interface..
[Galaxy Tab  Android Development] ayysir:
I think instead of everyone posting random fixes through the thread, just up a build with all the fixes plus cwm

That's what she said...
[Galaxy Tab  Android Development] mssmison:
Quick note, to all the questions about softbuttons or not, it's seriously a 10 minute compile job (once the system is made) to make framework with soft buttons. I believe this build is sourced from the i9000 build yes? If so I already posted framework there with soft buttons, which someone turned into a flashable.

so let's not waste any more of this thread about that? cool.
[Galaxy Tab  Android Development] Angel_666:
I upload all fixes without problem. Problem is - that our kernels and ramfs and inits are different. I use my build to find and select needed fixes. Than, we can apply it on koxudaxi's clean and fast rom. But first - need correct ini's and build props to build rom from sources.

My is from i9000+nexus. Koxudaxy is from tuna. The problem - tuna device have TiOMAP4+PowerVR , but not s3c.. That,s why in koxudaxy system are different codecs and libs (for TiOMAP)
[Galaxy Tab  Android Development] ani55:
build.prop for GSM tab
[Galaxy Tab  Android Development] mssmison:
Right, Koxudaxy is working to build the proper vendor config for the tab, so basically anyone could download the source +his files and build. That's what my long post was about.

So for your build, the frameworks I posted in the i9000 thread would work to create the soft buttons.

Moving forward though, continue both. Every advancement you make in terms of the libs/prop settings will only help Koxudaxy as he builds the device config.

For Kouxuaxy, you should be able to start with the cm7 galaxy tab device config as your base and work from there, that would really help you guys.

Keep up the great work, ingnore the people who complain and always want more and keep having fun :)
[Galaxy Tab  Android Development] splattx_x:
Good to know! That being said. I own a P1010 Tab and would like to start working in development for it... do you think I could use your work as base or are the tabs really that much different?

One thing I know is that I should first work on making the Gingerbread bootloaders work for the P1010 since we're "officially" stuck at Froyo...
[Galaxy Tab  Android Development] dcbogdan:
I've installed the latest alpha (koxudaxi_rom_koxudaxi_ics_rom_alpha1) but I'm quite stucked as the launcher crashes. I'm only able to get into Settings from the notification bar. Even in the settings the Applications section crashes.

First I've installed over the Overcome 3.something that I had, without a wipe (I just forgot) and I thought that was the problem.

So I have installed the Overcome safe stock 5 and then the Overcome kernel 4.0, waited for it convert to ext4 and installed alpha 1 again. I still get the same error "Unfortunately, Launcher has stopped."

Am I doing something wrong? Is there some debug info I could provide to help?

Thanks
[Galaxy Tab  Android Development] madkat:
Just a thought - if anyone is doing dev work on Android and doesn't have a decent box to build on, would it help to have access to a build server? Basically you'd check in your changes to github - presumably as a branch, I'm a Microsoft guy principally so I generally deal with shelfsets in TFS, does github do anything similar? - and then instruct the build server (through a web interface) to get your branch(/shelfset/whatever) and build it. I could see about getting notifications by email, too - depending on how long builds are likely to take.

Feedback? PM me if you prefer not to clog this thread, I'm posting this here because this seems like somewhere it would be well received if deemed useful.
[Galaxy Tab  Android Development] mssmison:
That's an awesome idea.

In fairness though the initial build is only what takes the longest, on my vm with 2gigs of ram it took about 4 hours. After than changes only take 10-20 minutes.
[Galaxy Tab  Android Development] koxudaxi:
hi,

i rebuild system from source code and start making android config for galaxy tab.

but,it need alot of time...

and i tried fix wifi driver, the result is not good yet.

please give me the time for developing the ICS

this project just start, we can see completely the rom in....

we fix a few bug and problems today .i think "day by day doing" is very important things

sorry i couldn't write comments in this thread.

but,i read this thread throughout the day:)

a report of my test rom

*there is not blank of screen

*boot seed to more quick

*copy cwm from my GB kernel

*tried fix wifi. <---need a lot of time
[Galaxy Tab  Android Development] madkat:
OK, interesting to know. I was thinking about pricing up an i7 with a 64Gb SSD & 8Gb RAM (I can add a slower disk for archival if necessary), just need someone to set up the necessary toolchain when the time comes - I work with a guy who's able to sort out a web interface, if nothing suitable already exists. Downloads are likely to be slow (under 1mbit) until I can secure a decent connection - but it may well be possible to package only changed files (effectively a patch on the previous version) into a zip.

Anyone else interested? It doesn't have to be tied down to a single project.
[Galaxy Tab  Android Development] jaiiscool:
Just noticed that ro.sf.lcd_density is mentioned twice, 180 & 240 in the build.prop
[Galaxy Tab  Android Development] dcbogdan:
You are right and that is what caused my problem (that I mentioned in an earlier post) with the Launcher crashing. I've modified build.prop and the lowest density that the launcher works at is 220, any value under that is causing it to crash.

Edit: As stated earlier in the thread a density of 160 also works.
[Galaxy Tab  Android Development] cdesai:
Even i was going to do the same, actually i've already started, lets talk about it over gtalk/gmail, and then one of us uploads it to github and then the other can start playing with it, mine doesnt boot yet though, so probably you should do the honours!
[Galaxy Tab  Android Development] lambstone:
@ani55, just a suggestion. could you include this into the first post? I was wondering what works and what doesn't but I had to sift through all the pages to come up with a list. I'm not sure which ones are still relevant to build 2 so I've included everything.

Things that work and/or are fixed

GPS - LINK

External SD - LINK

Sound - LINK

Multitouch

Camera - LINK

Things not yet working and/or are untested

Wifi

Camera

Bluetooth

Phone

Autorotation

Things to Know

This build does not contain the 3 soft buttons we see on Galaxy Nexus. Reason being we have capacitive buttons on the Galaxy Tab. The 3 soft buttons are optional for devices without any buttons.

Have to install apps via adb

Honeycomb tablet apps works

Apparently it is super smooth. Like when you lube up butter smooth.

Things not to do

Do not flash it if you do not own a P1000 and NO. P1010 is not P1000. Neither is P1000N same as P1000

Tips & Tricks

ro.sf.lcd_density is mentioned twice, 180 & 240 in the build.prop -> edit it to <220 otherwise launcher will break. 160 gives honeycomb layout. Recommend set to either 160 or 240.

Video of it in action - LINK

Quick and easy installation guide
[Galaxy Tab  Android Development] theREDlegion:
Not trying to be a d!ck, but, this is the confusion I was referring to. As the thread grows it only gets worse.

---------- Post added at 09:42 AM ---------- Previous post was at 09:39 AM ----------

Nice post lambstone.

I was going to PM the OP with a suggestion with a similar idea to try and help but that is perfect.
[Galaxy Tab  Android Development] laxanoulis1:
Koudaxi version:

Boots perfect

Very Smooth

Widgets Works

Calender Works

Camera > Cannot connect (with angels file)

File Manager Works (Finaly i found out that the File Manager doesn't show me the .mp3 files i had on my SD card, check it.)

Market doesn' t work

Messaging Works but the keyboard doesn't appear

Music i think it works (It opens but i don't have tracks to try it so i dont know if sound is ok!)

Phone opens but ther are only 3 buttons, Search, Phone & delete button and on top there is a blank orange stripe

Rom Manager opens

Root Explorer Works

Sensors doesn't work for me

And something else, on main screen, i dont have buttons for "back", "home", and "multytask" is this normal?

Thats all, i will try angels ROM later and i will report what works and what don't!

---------- Post added at 06:35 PM ---------- Previous post was at 06:26 PM ----------

;) You can check my report! :)) You can try it yourself too! This is exciting! :D
[Galaxy Tab  Android Development] ani55:
@koudaxi, i have added the the wifi drivers and others in my link (bcm4329.ko and few other libs and stuff)

All you need to do is add the lines in source to use these drivers such as ones provided by mssmison.
[Galaxy Tab  Android Development] koxudaxi:
i tried it. but wifi system dump errors on logcat which said "the kernel return value is error"

i must port a wifi driver from newer version. i just check other kernel.
[Galaxy Tab  Android Development] ani55:
Should we try the honeycomb driver from dario's rom?
[Galaxy Tab  Android Development] ani55:
OP edited, sorry for the disorganisation!
[Galaxy Tab  Android Development] Andy:
Gents, and ladies. I've done a bit of clean up.

I've removed non-dev related chatter & associated replies.

Keep things on-topic, you have achieved great things here, its a shame to hide the progress with pages & pages of rubbish.

XDA Rule 1 - Search

XDA Rule 15 (NEW) - Keep posts/threads on-topic
[Galaxy Tab  Android Development] ani55:
Thanks for clearing the clutter :)
[Galaxy Tab  Android Development] ani55:
New download link for my rom :ftp://195.222.101.81/../../

username: upload

password:ics

Thanks to woochewski for the his hosting!
[Galaxy Tab  Android Development] laxanoulis1:
Nice and fast host!!

Can you tell us if new link has build.prop fix(I mean ro.sf.lcd_density)?
[Galaxy Tab  Android Development] ani55:
@koudaxi

try this driver, it is slightly modified from original bcm4329.ko
[Galaxy Tab  Android Development] kay_kiat88:
U can find out yourself by extracting just the build.prop from /system found in the .zip and opening it with any text reader.
[Galaxy Tab  Android Development] ani55:
Yep, lcd density has been changed to 240

Change the build.prop to then one in OP
[Galaxy Tab  Android Development] TheGrammarFreak:
User and password for file host in OP would be handy ;)
[Galaxy Tab  Android Development] ani55:
I already have :D
[Galaxy Tab  Android Development] TheGrammarFreak:
Lol, either I'm blind or you're quick.

I reckon I'm blind
[Galaxy Tab  Android Development] laxanoulis1:
Before any tester install the .zip of ICS, i recommend to you to install Root Explorer...., it will help you with fix files!!
[Galaxy Tab  Android Development] EmperorX:
You're blind ;)

It has been there since he edited the post for clarity :)
[Galaxy Tab  Android Development] woocashewski:
aargh

at last i can post here :)

yesterday i try to install yesterday's version, and i'm very surprised, how fast it is, taking into account, that SGT is not dual-multi-penta core ;P

it's much more stable that honeycomb posted here some time ago...

patiently waiting for next release...

woocashewski

PS - it would be better, when ani55 didn;t post here read/write ftp credentials,

it would be safer, and quicker to post links like:

ftp://xda:xda@195.222.101.81/alpha1.zip
[Galaxy Tab  Android Development] mssmison:
another sweet tidbit I found today for those working on creating the proper vendor/device tree to build from source.

Add /device/samsung/galaxytab/overlay/frameworks/base/packages/SystemUI/res/values/config.xml

<! -- Whether we're using the tablet-optimized recents interface (we use this value at runtime for some things) -->

<bool name="config_recents_interface_for_tablets">true</bool>

<! -- Control whether status bar should distinguish HSPA data icon form UMTS data icon on devices -->

<bool name="config_hspa_data_distinguishable">true</bool>