yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Ok that's reassuring.

Great, just what I was looking for, many thanks :)
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
So some more questions:

Any limit to the size of the kernel? Presumably just the size of the partition (which after extracting the image for backup seems to be a pretty large 15.4MB)?

What do all the .rc files in the raminitfs do? They are as follows: fota.rc, init.goldfish.rc, init.rc, init.smdkc110.rc, lpm.rc, recovery.rc

The init.rc is the normal init.rc file, so that's fine. Presumably the recovery.rc file is run if the bootloader detects that recovery mode is wanted (holding down keys during boot). The init.goldfish.rc? I guess this is to do with the emulator, though why it would be in a release image I don't know.

I assume that init.smdkc110.rc is automatically run somewhere along the line, though I don't see where it's started.

Any thoughts on lpm.rc and fota.rc? Are multiple .rc files run for the normal and recovery boots?

Thanks :)
[Galaxy Tab Q&A, Help & Troubleshooting] Technomancer:
lpm.rc is for low power mode that displays battery charging animation

goldfish is for running the rom under qemu.

backup your rom using rotobackup. compile samsung's kernel from sources, mix up default initramfs with meego's init scripts. pack all Meego stuff into loop mounted disk image. then flash zImage to kernel and your disk image to factoryfs using heimdall. I assume you have experience hacking N8xx/N900 and Maemo or Meego?

factoryfs is around 300MB so I think it should fit Meego and it (and kernel) can be easily restored with heimdall.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Thanks for the comprehensive reply :)

Yes I do have experience hacking Maemo/Meego, though have never really had to fiddle with init scripts before and this is as good a reason as any to learn.

I'd actually like to dual boot, so am modifying recovery.rc to bring up the Meego system on the external SD card.

Am just fiddling about building extra kernel modules now (needs btrfs for my image for example) and modifying the recovery.rc file.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Hmm, well I was all set to go and flash my new zImage and was looking for the heimdall command line, when I saw this at the top of one of the threads in this part of the forum (http://xdaforums.com/showthread.php?t=870690):

Which has made me worry a bit that I've missed a recovery partition with its own kernel and wrongly assumed that the same kernel is used for both recovery and normal running, just with a different .rc file to be interpreted by init.

Any thoughts?
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Do we trust the partition sizes reported here: http://xdaforums.com/showpost.php?p=9471190&postcount=14

They seem very small for the kernel partition. I used RotoHammer's dd method to grab the contents of the partitions as a backup, so am assuming the sizes shown above are not correct (or represent something else?)

Going back to RECOVERY and ZIMAGE partitions - the ZIMAGE partition contains a recovery.rc, the question is really whether, even if they use the same zImage in both the ZIMAGE and RECOVERY partitions, the version in the RECOVERY partition is actually booted if recovery mode is selected (by holding the up volume key, etc.)? OTOH it may be that the RECOVERY partition is either empty or unused, has anyone tested specifically to see whether recovery.rc is run from the ZIMAGE partition?
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Well I think I can answer my own question there, I flashed my modified kernel (modified recovery.rc) only to the KERNEL partition, and it boots normally if I don't touch anything, and just gets stuck on the first Samsung screen if I boot in recovery mode.

So it's doing something, I just can't tell what. Not sure if any kernel messages are getting lost behind that image, or perhaps they aren't even output to the framebuffer at all. I seem to remember seeing something about disabling the splashscreen so I'll go and have a look for that. Anyone got any other suggestions?

P.S. I also note there's a flash of screen corruption as the device starts up with my new kernel, I don't remember seeing that before. Is this a usual occurance?
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
I see from the Nexus S port that including adbd in the image seems to be the way to go for early messages, I'll need to generate a new Meego image and have another go later on.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Interesting, I can't see that I've done anything wrong, and my extra init shell script is not started. I am trying to use the "exec" keyword in recovery.rc to start a shell script which will pass control to the Meego rootfs. At the start of my shell script I start adbd (i.e. still within the initramfs), so I should be able to tell if it has started, and it doesn't appear to do so.

Therefore I did some Googling, and I've seen that in some cases the initramfs init does not implement the "exec" keyword (http://forum.samdroid.net/f9/new-init-exec-import-implemented-3280/). This is troublesome for me as it's what I'm trying to use, but at least would explain why I don't seem to leave the init process :)

I couldn't see the Samsung specific source for init anywhere, has anyone found any? I'm not happy to replace it using the standard Android source as I'm guessing there's code missing which allows the bootloader to tell init how the device was started so that it knows which of the .rc files to run. Has anyone looked into this?

Thanks :)
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Looking at the code in that link it looks pretty straightforward, just a case of parsing the kernel command line (though I might just reverse engineer the existing init first to make sure I'm not missing anything).

Would still be easier to get the actual source code from Samsung, so I've emailed their Open Source group.
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
I get it with CM
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Does CM use a compressed initramfs? I'm using one of those and wondering if it's something to do with the (admittedly small) extra time required to move to init.

I don't have my Tab with me here, could someone post the output of /proc/cmdline please? You'll need to be root. Thanks.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Well it's booting you'll all be glad to hear.

More details to follow, but from memory the following were required:

Custom kernel to add btrfs support (as the image I'm booting is a btrfs partition on the external SD); kernel patch to allow compile-time cmdline to be added to the end of the bootloader cmdline (to enable console=tty0); replace Android init with init script to perform some basic setup then pivot_root to the Meego partition.

Next steps are to get the Meego system running usefully (which includes getting a terminal as currently I just have a login prompt but no way of inputting anything!) and also seeing whether I can get dual booting working with an Android system standard boot and Meego replacing the recovery boot.

Poor pic, but still: http://people.bath.ac.uk/enpsgp/Tab/PICT0040.JPG
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
Good stuff. Thanks for keeping us informed.
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
After you've got the groundwork for this done, how easy would it be to get Ubuntu running?
[Galaxy Tab Q&A, Help & Troubleshooting] brilldoctor:
Try google http://lmgtfy.com/?q=ubuntu+on+galaxy+tab
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
That's using chroot, which I don't want. I want it running natively.

Sent from my Galaxy Tab
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Re Ubuntu, yes it should actually work in exactly the same way, no further modifications required, though I'm not sure how good the Ubuntu touchscreen interface is (or indeed if it exists)?

I've been a bit weighed down with work in the tail end of this week, but will crack on with my efforts this weekend. I was thinking of trying to use a usb keyboard to give me the ability to at least enter text - I hope it will be possible to override the usb_switch which controls which kernel modules are insmod'ed depending on the cable type (assuming the official keyboard uses this ability to switch the device into usb OTG host mode).
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
HTC HD2 has a NAND ROM for Ubuntu ;)
[Galaxy Tab Q&A, Help & Troubleshooting] savit:
Hi lardman,

I have no much interrest into Nokia stuff, however the way you describe your findings is extremely interresting!

So, since there was no post from you lately, could you please update us how you managed starting X? Or maybe you have already finished your porting? :)

Best regards

Savit
[Galaxy Tab Q&A, Help & Troubleshooting] Temar:
Yes, please keep us up to date. Very interesting thread.
[Galaxy Tab Q&A, Help & Troubleshooting] iuzar:
Mate, he just said yesterday what are his plans, two posts above yours :(
[Galaxy Tab Q&A, Help & Troubleshooting] savit:
Excuse me iuzar, but I dont really get your point.

I am curious about the progress, because of what I have learned about his plans from the post you referr to.

Is anything wrong about showing the dev our interrest in his work an encouraging him to share?

Have a nice day :)
[Galaxy Tab Q&A, Help & Troubleshooting] iuzar:
I think I misunderstood your request. I thought you haven't seen his post from yesterday. Sorry mate :D

You too have a nice day :)
[Galaxy Tab Q&A, Help & Troubleshooting] savit:
It's OK :)
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Sorry chaps, busy weekend too, but I'm back on the case. So things to do now:

Check the decompiled Android init to see how it determines bootstate (i.e. normal or recovery) so that I can make the device dualboot at will (this will make dev work faster as I will be able to simply edit my btrfs image on the SD card rather than needing to flash the original kernel back when I want to actually use the device!)

Work out whether/how to get a USB keyboard working. If anyone has the official keyboard and would like to post the dmesg output just after it's attached that would be great (I've been wondering about walking into my local shop and asking them if I can try the display keyboard with my device and just happening to save the dmesg output while I'm there :) )

Then the next step is making the Meego image vaguely useful, so input and the like.

I also need to write up the steps to backup, create kernel, flash kernel, etc., so that other people can get involved.
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
I'm pretty friendly with the guys in my local shop, so I could probably get dmesg if you can't.
[Galaxy Tab Q&A, Help & Troubleshooting] savit:
Hi Ladrman,

Nice to hear from you again. Unfortunatelly not there is no keyboard in my scope.

Is the keyboard really a must? Aren't you able to control the device over adbd or similar remote shell service?

Best regards

Savit
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Thanks :) Well if you're able to do it before the weekend that would be very useful as I won't be able to make it into town before then.

Yes adbd should really be possible, just a case of getting the network up (presumably, as it hasn't become available yet). A keyboard would just be nice (though probably as much hassle as the network to get sorted) and I'm curious to know if it would work too! :)
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
http://pastebin.com/ccrcWPNK
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Many thanks :)

At first glance though there doesn't appear to be anything indicating that the kb dock is necessarily a USB kb.

Around line 2086 we see a notification that a docking station is attached. I'll have to do some grep'ing of the kernel source to see what generates the different messages and whether they are actually USB-related (which is still my gut feeling).

Again, many thanks for that info :)
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
If you need anything else just ask ;)

Sent from my HTC Legend
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Ok, so it appears that the keyboard is not connected using usb, but rather as a serial device over a uart. See the p1_keyboard.c file in the kernel source.

But it does look like USB OTG host should be possible. We're still trying to decipher the exact way of getting this (and indeed even the device to be seen as a USB client after a Linux boot)
[Galaxy Tab Q&A, Help & Troubleshooting] TheGrammarFreak:
Sadface.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Well I've got bored with the repeated cycle of boot, watch messages until login prompt, try adb shell, fail, switch off, pull SD, put SD in PC, look at messages, repeat, caused by still not having a way to log into the device. I've therefore bought a Tab kb doc (for £39.99 at Carphone Warehouse online, which seemed reasonable) as I was able to log into Meego while standing with my head cocked to the side (unrotated fb on that Meego image) in my local Carphone Warehouse shop.

Hopefully having some interactivity should make life easier. As you may know lilstevie is working on porting Ubuntu, and as we have the same fundamental issues we're working together on this. I hope to have some useful and happy news for you as soon as this kb dock turns up (mid-week) and I've had a chance to do some tweaking (hopefully to get USB networking up so anyone else without a kb dock can login and start hacking.)

I will also write up some instructions as to how to get started with all this stuff as I have a long and boring train journey to make this week - seems perfect.

Anyway we're still beavering away, don't worry :)
[Galaxy Tab Q&A, Help & Troubleshooting] idumych:
Glad to hear you're still working on it! It seems to me that the main issue is you guys need to write a new video driver that supports the Tab. I know Ubuntu uses Xorg which is totally different from the Android framebuffer. As far as Meego goes, I'm pretty sure that uses X as well but I could be wrong.
[Galaxy Tab Q&A, Help & Troubleshooting] lardman:
Long time, no news. Sorry have been pretty busy at work so not much time to do Tab hacking.

So to summarise, Meego boots and you can login using a kb dock (I bought one on discount) or if you create an appropriate script in the Meego rootfs you can bring wifi up and login over ssh (thanks to lilstevie for working out the firmware loading for the wifi driver).

So we have a fully interactive text login, but that's not much use unless you have a kb dock or have another device with which to send commands to the Tab.

Starting Xorg seems troublesome, basically it will start up and run quite happily, but just blanks the screen. Therefore I'm going to do some driver comparison work this weekend to see why e.g. the Nexus S works, but our Tab doesn't.

Any help, ideas appreciated of course.

Status and instructions here: http://wiki.meego.com/ARM/Hummingbird#Samsung_Galaxy_Tab

These still need some work, and I'll be filling them out and adding more explanation as I go along, but should give sufficient info, links and files for people to build an image if they so desire (yes, go on, help with the hacking! :))

Cheers :)
[Galaxy Tab Q&A, Help & Troubleshooting] daml:
hi, how you going with this? awesome project, you got a lot further than i did...
[Desire HD Q&A, Help & Troubleshooting] Semi666:
For some reason my system buttons such a home menu back and search are no longer backlighted. Is there some option how to turn it back on ?
[Desire HD Q&A, Help & Troubleshooting] tkolev:
I think the backlight of the buttons is controlled be the ambient light sensor, so if you turn your screen in a dark room they will light up.
[Touch Diamond2, Pure Android Development] Honzac353:
I have a problem with xdandroid, can not see sd card!:mad: (eg media player or image viewer) card is formatted to FAT32.

But the "Android With HTC Sense, 3D and sound (by LENINred)", see the sd card!!!:confused:.

Does anyone have a similar problem? anyone knows how to solve it? or is it normal?

thanks

additions: on the xdAndroid headphones do not work, but on "Android With HTC Sense, 3D and sound (by LENINred)" works

I have both used the same latest kernels
[Touch Diamond2, Pure Android Development] wavesshock:
First: Try to format your sd once again and put all of the files to the root.

Second: Try this:

"Headset

"snd.force_headset=X"

1=USB headset

2=3.5mm headset

"

it' from the official xdandroid-thread (http://xdaforums.com/showthread.php?t=509493) --> this solved headphone issue for me. ;-)
[Touch Diamond2, Pure Android Development] wavesshock:
forgot to say: you have to copy the text to the startup text. paste it there
[Touch Diamond2, Pure Android Development] rhanson002:
startup.txt

I add the snd.force_headset=2 into the startup.txt and save it. I boot Android and it's not fixing the headset sound problem. When I go back to the startup.txt file, the snd.force_headset=2 command is gone. What am I doing wrong?
[Touch Diamond2, Pure Android Development] pego2007:
@ Honzac353

Go to boot-loader,plug the usb-cord into pc.Systemmanager will found an new device.

After that can can sync again with mobile-device-center.

greetz and happy sunday

pego2007
[Galaxy Tab General] gigino:
Hi

I'm going crazy with this Galaxy Tab I need to enter Letters in the postcode tab but it well only let me put numbers can someone tell me how to resolve this problem or is they a softare that I coukld uswe to resolve this shareware or freeware?

please help

Thanks

Gigino
[Galaxy Tab General] Mado007:
Had the same problem. Solved it by syncing thru Kies with Outlook. If you have Outlook perhaps it can help you to.
[Epic 4G Accessories] electronicmaji:
Are there any recommendation on the best film I can buy? I can't stand the smudges anymore!
[Epic 4G Accessories] NeonMonster:
Steinheil SGP protectors are by far the best screens out!

There is the Ultra Clear which is crystal clear, but tend to be just as or more fingerprint magnets then the glass by itself.

They also make the SGP Anti-Fingerprint Matte screens, which make the screen matte, and there for, finger prints don't show up on them. The downfall to the Anti-Fingerprint reduces the screen clarity by a small amount.

I ordered the Anti Fingerprint, and I honestly love it. The package comes with 2 screens, and I was able to get the 1st one done perfectly. The matte screen is a nice texture, similar to a resisitive touchscreen. It makes a slight sliding sound when swiping or using Swype but I have grown to like the sound a bit. About screen clarity, YES I can tell there is a bit more of a haze on the screen, specially when on bright white background. But I don't notice it when the screens on, and the anti fingerprint is MORE than enough reason to keep the screen protector on. As far as anti-fingerprint goes, fingerprints are a thing of the past! :)

from a epic Galaxy far, far away.
[Epic 4G Accessories] globalninja:
I use zagg invisible shields. They are working out pretty great, easy to clean also.
[Epic 4G Accessories] friedricebob:
I'm rocking the Realook.

Pros:

Clarity

Smoothness (I can't stand the 'tacky' feel)

Exact Fit

2 in the kit

Durable so far

Reasonable price

Cons:

Fingerprints can show while screen off

Reduced sensitivity of capacitive buttons (any full-screen will have this)
[Epic 4G Accessories] xeonbuilder:
Im using the Bodyguardz. Super clear and you get enough for 2 applications for the same price of 1 zagg set. They are the best I have ever used.

Also these dont reduce the sensitivity at all from what I have seen on the buttons. The buttons stink to begin with so that might be why. lol.
[Epic 4G Accessories] globalninja:
Are bodyguardz more rigid? Sometime i think i put too much water when applying my zagg and there are slight waves and i can make little ridges by running my nail against the shield.
[Epic 4G Accessories] h0st1le:
Another Vote for Steinheil SGP protectors, I opted for the crystal clear version, first application was a breeze, can hardly tell the protector is even on the screen.. it is a fingerprint magnet but I really wanted it to protect against key scratches and such. so far I wouldn't use another.
[Epic 4G Accessories] popper668:
stealth gaurds are what i like and the price is right. under 3$
[Epic 4G Accessories] fastmikey1969:
Bodyguardz isn't too bad on the orange peel, but its still pretty soft.

Using the realook, its hard plastic and smooth, zero orange peel.

Heard good things about the SGP too, may try that next once this one gets worn out.
[Epic 4G Accessories] Comando156:
I have tried sedio, invisiable shield, body guardz, and I have to say the best hands down is realook. I can't even tell its there and feals just like the glass. Trust me best one.
[Epic 4G Accessories] pipskicks:
What's wrong with no skin? Never scratched the hero and dropped it a bit...

I liked the zagg on my blackberries but it didn't help the touchscreen and eventually became a bother....
[Epic 4G Accessories] Mighty442:
I'm using the Skinomi full body screen for my Epic, some people have had problems putting it on but I didn't have any issues. I like it a lot, and it comes with a life time warranty. I put a scratch on mine and sent in the mail form to get a new one, they sent it out, they charge for postage and you have to send the old film back but it still works out pretty well.
[Epic 4G Accessories] Shoote72:
I have a zagg, it doesn't ever get that dirty look, doesn't peel around the edges, it has very clean look and feel, sensetivity is outstanding, no glues and chemical residues, and the special little bottle full of "special solution" used for applying the screen protecter... Water

Don't forget the Lifetime Warrenty for those that are going to use their Epic for the rest their life.
[Epic 4G Accessories] churro7:
Skinomi pwns

sent from my epic 4g with no 4g
[Epic 4G Accessories] boominz28:
I wonder if there is a gell that we can put on our screens that would be to either repair light scratches or can protect it from scratches
[Epic 4G Accessories] juanaraya92679:
Phantom Skinz all the way. Goes on smooth and feels smooth. Very little orange peel effect.
[Epic 4G Accessories] eheaps:
I just got the Steinheil anti fingerprint screen (it was like $8 for two on amazon), it was extremely easy to install and fits the screen perfectly. I didn't get it so much for protection, but more for the anti smudge and I have to say it works great for that purpose. It does have a noticeable matte look on our gorgeous screens, but I decided to take the tradeoff of the no prints. It also feels very different, it doesn't feel glass like or even plastic film like and you can hear you're finger swiping on it, again no big deal though. There is no decrease in sensitivity as well.

For protection purposes, I had skinomi on my hero, and once installed right (moderate difficulty) that worked out well for the duration that I used my phone.
[Epic 4G Accessories] professoroak:
What's the difference between the SPG "Anti-figerprint" and the "Ultra oleophobic?" Is it just the matte texture on the former? I'm debating between the two. I like the feeling of the matte but does it compromise the quality of the screen to an unpleasant effect?

Edit: Nvm, I watched a youtube video of the difference between the Anti-Fingerprint matte screen protector and the Ultra oleophobic clear screen protector. On the SGP website, it appears that they don't have an Ultra Oleophobic screen protector for the Epic quite yet.
[Epic 4G Accessories] Red_Cheeks:
The other day a phone droid x a guy had, had a screen protector that kinda felt like paper. But there was hardly any figer marks. Does anyone know which one im talking about. I know it was on a droid x but i would like one like it for my epic.