yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] chris....:
None here

Sent from my Galaxy Tab running CM7
[Galaxy Tab  Android Development] robkoehler:
What was the expected result?
[Galaxy Tab  Android Development] btyork:
It may not be written to format the animation? I know a lot of roms come without a modem, and the one on the system persists through flashing... Just an immediate thought.

Swyped from my "better than an iPad" tab running Overcome Hermes.
[Galaxy Tab  Android Development] Technomancer:
It should format the whole system partition (stl9) using mke2fs.

It does this:

ui_print("Formatting system ...");

run_program("/tmp/mke2fs", "-m", "0", "-O", "has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize", "-L", "system", "-M", "/system", "/dev/block/stl9");

ui_print("Mounting system ...");

run_program("/tmp/busybox", "mount", "-t", "ext4", "/dev/block/stl9", "/system");

See if manually unmounting /system from adb before installing the update helps.
[Galaxy Tab  Android Development] Yom:
Thank you!

Well, since the boot animation lives in the /system partition, when formatted and flashed over the file should disappear if there is no bootanimation.zip file in the ROM zip.

I ended up formatting all partitions manually from CWM and then re-flashed. That did the trick.
[Galaxy Tab  Android Development] Technomancer:
Just flash kernel and factoryfs with Heimdall. I find it much more reliable.

Also, when upgrading from older release you don't need to wipe, just flash kernel and factoryfs.
[Galaxy Tab  Android Development] caveman999:
The first CM7 ROM that I flashed from you was the 6-13 version. The capacitive buttons worked great at first (without any vibration, but still functional). After a while, however, the capacitive home button stopped working and I had to switch to using the on screen buttons from the tablet tweaks.

Yesterday I flashed your 6-21 version (using Heimdall again) and while the haptic feedback from the buttons worked great and the home button functioned at first. After about half an hour it wouldn't work anymore. It would still vibrate but nothing would happen.

Has anyone else experienced this issue? It seems really wonky. Why would something work at first but stop later when all I did was restore my apps using titanium backup?

Thanks for any advice.
[Galaxy Tab  Android Development] k0sh:
why wouldn't u flash it again ? or put the update to ur sdcard and flash it via cwm and see if that work with you
[Galaxy Tab  Android Development] caveman999:
I did flash it again. With a whole different version. I figured it was either a bug from the first flash or in that version that might be worked out in the next. So then I did flash it again. And the bug was still there. I don't think a third flash would fix anything.

I didn't try it from CWR because I have read about people having lots of problems using that and Technomancer even said in his first post that if anything goes wrong use Heimdall, which makes this option seem more reliable.
[Galaxy Tab  Android Development] k0sh:
yeah Tech mention that , in case something goes wrong :) flash the update via cwm over the one you flash it via heimdall , nothing gonna happen if you try it :) i have feelings it will work ;) give it a try
[Galaxy Tab  Android Development] caveman999:
Okay, thanks. Ill reflash CM7 later today and get back with my results.
[Galaxy Tab  Android Development] DaReDa:
Someones gettint the sound issue fixed with the JPZ Modem?
[Galaxy Tab  Android Development] krumbs:
Thanks for this ROM. Loving it. Coming from Overcome's latest version with a JPZ modem.

Used CWM and flashed twice, as advised by an earlier poster: Boot in CWM, wipe, flash, reboot in recovery, wipe, flash again, reboot.

The only problem i have stumbled across is that the external SD card won't automount on reboot. I have to manually pull out the card and push it back in. Any fix for this, please?

Have replaced the vold.fstab with the one that restores Samsung's default folder structure. Interestingly, the Storage Setting still refers to /mnt/emmc.
[Galaxy Tab  Android Development] slimdizzy:
I use the JPZ modem. What sound issue are you talking about?
[Galaxy Tab  Android Development] slimdizzy:
That would be correct if your did the "switch back to Samsung" method. Internal (non replaceable) would now be /mnt/sdcard and the replaceable one would now be /mnt/emmc (external multimedia memory card, or something like that). As for the automount issue there is a fix for that in the regular android forums. If I can find the link i will edit my post.
[Galaxy Tab  Android Development] ayman07:
I forgot which modem I was using since I switched over to stock to get 3G working. Will test out JK5.

From the Tab.

www.twitter.com/ayman07
[Galaxy Tab  Android Development] ayman07:
edit:

IT WORKS! using JK5 modem fixes voice for me! Awesome call. here it is if anyone needs it.

http://www.multiupload.com/C77D86WZWG

thanks technomacer!

sorry about the double post.
[Galaxy Tab  Android Development] Technomancer:
Major WIN! ;-) Thanks ayman07! I was really worried about that one.
[Galaxy Tab  Android Development] beeroatsnp90x:
Can someone make a video? :)
[Galaxy Tab  Android Development] Landroid:
doesnt work for me... :( ill try to reflash everything and see if that works

edit: if i flash the modem, teh settings show Modem Version: P1000XXJM6
[Galaxy Tab  Android Development] paulshields:
Tried the JK5 ROM and calls worked fine. Starting to come together :).
[Galaxy Tab  Android Development] rmanaudio:
Technomancer you are just amazing. I loaded your beta on my tab last night and it works amazing.

Had to first convert back to rfs from ext4 then it loaded no problem!

Love your beta so far. Everything works great except for a few issues you already know about (no video playback, no camera, no charging while off) but everything else is so fast.

I can't wait till it is all done. Keep up the good work! I will have a donation for you when your work is complete.

CM needs to make you part of their group so that this can get a seal of approval so some idiots stop being upset about this port/mod
[Galaxy Tab  Android Development] Landroid:
@Technomancer

u are in the news ;)

http://www.androidcentral.com/cyano...l+(Android+Central)&utm_content=Google+Reader
[Galaxy Tab  Android Development] iamloco:
@Technomancer

great job the BT is better than Samsung one

I've been using sportstracker with a zephyr HxM (hearth rate monitor BT)

after 25min or so the system always freeze

just finished 30min and nothing no freeze no crash and even better performance
[Galaxy Tab  Android Development] julianLo:
@Landroid: flashing the modem file ayman07 posted solved the problem for me, I now have working voice :)

Great that it's finally working :)

@iamloco : isn't the tab a little big for running? :D
[Galaxy Tab  Android Development] Flash2KXX:
Loaded the beta on my Tab- impressed with the progress so far, though the hwrotation=90 thing really bugs me. I had a few issues with the DPI being 180 as well, it messes up the rotary lockscreen and when I attempted to set it to 240 via LCD Density Changer (System setting) it causes constant FCs. Also I couldn't figure out how to install gapps since CWM is screwed up. Looking forward to the final product though for sure :)
[Galaxy Tab  Android Development] paulshields:
Yeah, there are still lots of bugs but it's still the best (only?) Gingerbread ROM available for the Tab so it's a great start :). My main bug at the moment is with the Google Reader RSS app. It doesn't scale properly when reading articles.

I've found CWM to be a nightmare on the Tab, apart from when using modaco's kernel. I suspect it's as much down to how Samsung handle external SD's as much as anything else. I'm hopeful that these issues will be resolved in the days and weeks ahead.
[Galaxy Tab  Android Development] 2600hz:
Hello

installed Heimdall and libusb

but

download mode connection Galaxy Tab no recognition.......

Please uploaad

CM7 Gingerbread Public Beta (cm7beta.zip) ClockworkMod Recovery version file
[Galaxy Tab  Android Development] Galaxyer:
+1

kindly, if it is possible, CWM3 version will be appreciated...the TAB already Ext4 converted
[Galaxy Tab  Android Development] julianLo:
You can also flash with odin.

Just 2 simple steps:

1. rename factoryfs.ext4 to factoryfs.rfs

2. tar -H ustar -cf odin.tar zImage factoryfs.rfs dbdata.rfs cache.rfs

then you can flash the tar-file using odin.
[Galaxy Tab  Android Development] Technomancer:
Hey, do you use some armband or something to run with your Tab?

I was running with Nexus One and RunStar but I can't find a way to attach the Tab to me for running.
[Galaxy Tab  Android Development] Technomancer:
Final release will be all EXT4. For now it is mixed to make it easier for people to switch there and back.
[Galaxy Tab  Android Development] -RioT-:
Sooo.... Does that mean it will be easier to switch back and forth from the modaco ext4 rom? ;) ;)

As I understand, that one might not be updated for to long.
[Galaxy Tab  Android Development] humberos:
Hi, @technomacer

This version works on P1000L tab version?

If not, how/what can I do for help to built it?

Thank you!

P1000LVJJJ3
[Galaxy Tab  Android Development] ayman07:
@technomacer its sort of strange but Bluetooth seems to be working after using the JK5 modem. Not sure if its related.

I made a quick video.

http://www.youtube.com/watch?v=Zzwgvzpev2Q&feature=youtube_gdata_player

From the Tab.

www.twitter.com/ayman07
[Galaxy Tab  Android Development] Namaless:
With KM2 not found any sound issues ;)
[Galaxy Tab  Android Development] DaReDa:
In the first Post there is this little text.

So i can go to CM7?

Well, thanks.
[Galaxy Tab  Android Development] TheGrammarFreak:
Yes. If sound doesn't work, change modem ;)
[Galaxy Tab  Android Development] enyeng:
Mobile Network and Wifi based Location bug?

I have been using the CM7 for the last few days and it has been very good so far. Thanks a lot!

One thing that I've just realized, however, is that the Mobile Network and Wifi based Location does not seem to work well in my Tab (yes, I am sure that the box for this option is ticked). The weather widget is not properly updated when I'm moving. Furthermore, my Tasker profiles which use Network-based location context also fails to fire.

Any one has similar problem? Is there some kind of way to trigger the update for location so that I can check if it is indeed working / not working properly?
[Galaxy Tab  Android Development] Technomancer:
After recent audio library fixes there have been reports that JPZ modems work, so you can try them, If it works for you with JPZ, please post here and I will update the first post.

@caveman999

About the touch buttons issue. It seems weird, especially if you say that if you press the touch button it buzzes, it means that the keyboard event has been generated by input layer and went through Android stack. Are you running any app that changes buttons functionality or intercepts them? Try full wipe, recently there were changes in some long press button settings in CM7 maybe you have some old setting stuck?

To anyone messing with their vold.fstab.

I set it up the way it is for a reason. If you change it and it doesn't work for you please go back to default setting.

@enyeng About location.

I'll look into it. I always switch it off because I don't like to be tracked.
[Galaxy Tab  Android Development] caveman999:
Currently I have no app installed (to my knowledge) that changes the functionality of the capcitive buttons. I just did another complete install using Heimdall after factory resetting the device and wiping all caches and I wiped everything again after the flash just to be certain. I then followed k0sh's advice and flashed the CWM file over CM7. The home button worked at first, but like all other times it stopped working even though it is still providing haptic feedback.
[Galaxy Tab  Android Development] k0sh:
thats so strange though . maybe there is some settings you should look for it in setting\CM7 settings\tweak or any settings you can find about the buttons
[Galaxy Tab  Android Development] Technomancer:
If it is providing haptic feedback it works and the event made it from the kernel through android input layers. I don't know what is so unique about your Tab that it is not further recognized by your android system. It seems to work for everyone else. Look for clues in logcat and dmesg.
[Galaxy Tab  Android Development] HighSun_Murder:
Help Help Help.

I know I'm probably going to get blasted for this but is there an easier explanation on how to install this ROM?

I have a AT&T GTab that I rooted using Super one click.

I'd like to know if I can just drag n Drop a rom update.zip to the root of my device enter recovery and flash it, or do i have to jump through 1000 hoop's to get it there?

Every write up i see seems like its over complicated.

Also is there an easy way to back up My GTab in the event that I Brick it?

I know I know, use the Search box. Well,.... i did that and I also asked a similar question on the "questions" thread and got BS responses.

Please Help my eye's are killing me from trolling multiple sites looking for an reliable answer.

Thanks in Advance

-Murder-
[Galaxy Tab  Android Development] k0sh:
to bakcup your rom\firmware , check this guide , http://xdaforums.com/showthread.php?t=850359
[Galaxy Tab  Android Development] natious:
You can put the. Zip on the SD and flash it, but that didnt work for me, so I used heidmil, to use it you just open the heidmil download and place everything in it in the corrisponding spot and flash away, its really assimple as that, but its safe to be on stock safe gb first

swyped from a galaxy far far away
[Galaxy Tab  Android Development] robkoehler:
If the op doesn't make sense, walk away or make friends with someone and start dm'ing
[Galaxy Tab  Android Development] caveman999:
Unfortunately I don't know how to use logcat or dmesg.
[Galaxy Tab  Android Development] Technomancer:
Get adb. Install adb drivers for Tab if you are using Windows.

from console, type

adb logcat

and you will see the logcat

or

adb shell dmesg

to see output of kernel message log

you can also use logcat or dmesg command in terminal

or install aLogcat
[Galaxy Tab  Android Development] caveman999:
Okay, thanks.
[Galaxy Tab  Android Development] TheGrammarFreak:
I'll be your friend ;) If you need a walkthrough you can PM me, find me on GTalk or Skype ;)
[Galaxy Tab  Android Development] caveman999:
I just ran logcat and dmesg. What things should I be looking for that would tell me why the home button won't work?
[Galaxy Tab  Android Development] Technomancer:
@caveman999

error messages of any kind?

btw, does reboot help or the buttons do not work even after reboot?

you can save logcat to a file

using command line like this

adb logcat > filename.txt

and press ctrl-c after a while

and post the log on pastie.org and send me PM.
[Galaxy Tab  Android Development] caveman999:
I think I figured out the problem. When restoring my apps and data using titanium backup I would select the option "Restore missing apps + all system data". My guess is that this copied over a system file from the Overcome ROM that i was running that is incompatible with CM7. I just did another full install and have been running problem free for over half an hour (way longer than i was able before). This time the restore option that i used was "Restore missing apps with data". When i did have the problem, rebooting the tab wouldn't work. I dont know which system file would cause this problem, though, which is especially weird since it didnt affect any other buttons other than the home button. Also, the home button issue didnt set in right after the titanium restore, it was more like a few minutes afterwards.
[Galaxy Tab  Android Development] enyeng:
Display of recent apps bug?

Have anyone ever encountered the display for list of recent application (i.e. when HOME button is long-pressed) is somewhat misaligned?

The two pictures below show the difference.

The left picture is the expected display, the right is when it is misaligned (also just now noticed that the transparency in the right image is gone). The thing is that I am not really sure what cause the misalignment. It looks randomly occur while I am not doing anything extraordinary.

I did not make changes to the 'default' DPI of 200. Launcher is Launcher Pro. The number of recent application to be shown (Menu -> CM Setting -> Input -> Long-press home setting -> Number of recent apps) is set to 12.

Functionality wise, I find no problem at all in this 'misaligned' GUI.
[Galaxy Tab  Android Development] natious:
I have this aswell now and then, but I'm on 185dpi

swyped from a galaxy far far away
[Galaxy Tab  Android Development] caveman999:
The same thing happens to me.
[Galaxy Tab  Android Development] DemonGloom:
I recommend you to try KsLauncher from market.. You can bind it on home longpress and it give s much more functions than default window..
[Galaxy Tab  Android Development] paulshields:
Just chiming in to say that I've noticed that too. GPS (navigation etc) definitely works, but location/weather services that use GPS fail. For now I just hard code it.

[edit for clarity). Geo location services seem to fail whether GPS is enabled or not. This is when trying Beautiful Widgets, Fancy Widget Pro, or the built-in Genie service.

Example from Beautiful Widgets logcat:

D/Beautiful Widgets( 4359): Setting location for widget
I/ActivityManager( 185): Displayed com.levelup.beautifulwidgets/.LocationSelectorAccuweather: +377ms
V/Beautiful Widgets( 4359): Service AccuWeather onStart()
D/Beautiful Widgets( 4359): Service AccuWeather Thread started
I/Beautiful Widgets( 4359): Provider is network
I/Beautiful Widgets( 4359): Requesting location update
D/Beautiful Widgets( 4359): Accuweather == true
V/Beautiful Widgets( 4359): Service AccuWeather onStart()
D/Beautiful Widgets( 4359): Widget from config installed
D/Beautiful Widgets( 4359): Service AccuWeather Thread started
I/Beautiful Widgets( 4359): Provider is network
I/Beautiful Widgets( 4359): Requesting location update
D/dalvikvm( 3327): GC_EXTERNAL_ALLOC freed 490K, 47% free 3457K/6471K, external 4189K/4303K, paused 29ms
D/dalvikvm( 1955): GC_EXPLICIT freed 8K, 53% free 2697K/5639K, external 0K/0K, paused 74ms
D/Beautiful Widgets( 4359): Aborting locations updates, no fix within 40seconds
I/Beautiful Widgets( 4359): Geocoding the location...
W/Beautiful Widgets( 4359): GetMyLocation: location is null, using latest coordinates
I/Beautiful Widgets( 4359): Lat: 48.86
I/Beautiful Widgets( 4359): Lng: 2.32
W/Beautiful Widgets( 4359): Geocoding failed, using previous city name.
W/Beautiful Widgets( 4359): java.io.IOException: Service not Available
W/Beautiful Widgets( 4359): at android.location.Geocoder.getFromLocation(Geocoder.java:136)
W/Beautiful Widgets( 4359): at com.levelup.beautifulwidgets.UpdateAccuweather.runMyGeoAccuweather(UpdateAccuweather.java:470)
W/Beautiful Widgets( 4359): at com.levelup.beautifulwidgets.UpdateAccuweather.access$0(UpdateAccuweather.java:420)
W/Beautiful Widgets( 4359): at com.levelup.beautifulwidgets.UpdateAccuweather$3.run(UpdateAccuweather.java:396)
W/Beautiful Widgets( 4359): at java.util.Timer$TimerImpl.run(Timer.java:284)
[Galaxy Tab  Android Development] paulshields:
Don't have that problem with the stock CM7 - ADW launcher and 200DPI. Maybe a Launcher Pro quirk?
[Galaxy Tab  Android Development] maxtcee:
ok i think i found i glitch in the music sound stop and starting

ive been messing with slacker radio/music player all morning and every time the display times out the music starts to lag and cut in and out then i get black screen of death and have to try to unlock the tab to restart slacker/music player to play it again

so even if i turn display time out to 30 min which is max once the display goes black i get that sound cutting out and screen of death

anybody else getting this
[Galaxy Tab  Android Development] DemonGloom:
I got the same problem today.. And flashed to overcome.. As I listen to music all the time..
[Galaxy Tab  Android Development] Technomancer:
I have been listening to music for hours yesterday at work using A2DP headphones.

What music player do you use? Which tab do you have? Euro, ATT or TMO?
[Galaxy Tab  Android Development] maxtcee:
att tab slacker or stock player

weird thing is the screen of death thought it was because or smartass but it does it even without set cpu

once the 30 min display timeout is up i get the sound lag
[Galaxy Tab  Android Development] Jeffro64:
Weird thing is... After the 6-21 update my Moto BT headset works as it should both on incoming calls and incoming calls while music is playing. But I too lose the music when the screen goes to sleep. I don't need to reboot or anything just wake the tab by pushing the power button, and as soon as the screen comes back on the music starts playing again.

On another note... Sorry I didn't report back on the Moto headset working as it should sooner, been working a lot and today was the first chance I had to mess with it. Thanks for whatever you did to fix that Tech!
[Galaxy Tab  Android Development] Technomancer:
interesting. when i was listening to music the tab was in keyboard dock and it had no problems when screen went off. maybe it tries to go into deeper sleep when its purely on battery. i'll test more on tuesday. in meantime please try testing what happens when it is connected vs not.
[Galaxy Tab  Android Development] maxtcee:
ill testb my keyboard dock tonight and post results manyana

also mind you it wasnt on pure battery i had it plugged into ac
[Galaxy Tab  Android Development] Jeffro64:
OK, Got a chance to play around with it this morning. I have it plugged into AC power and I get the same results. BTW.. this only happens while on BT, if just listening to music from the tab it works fine after the screen goes to sleep.

I also tried different settings in SetCPU and disabling the lockscreen music controls but nothing seemed to work. I use Power Amp for my music player but this happens with the built in player too. I'll keep playing around with it but not sure what could be causing the problem.

Tech... When you flash a new update do you just flash over or do you wipe all and do a complete install? Just trying to find the difference in what you do compared to what I/others might have done.
[Galaxy Tab  Android Development] Yom:
Weird issue after reboot : unless tab is quickly turned off and on, it will stay with its screen turned on, won't load any startup apps, and drain the battery if unplugged...

I saw this same issue on Overcome, and I think it was fixed in the kernel...

Posted using my hacked, rooted, undervolted, overclocked, pimped-out and overall bad-ass Samsung Galaxy Tab.
[Galaxy Tab  Android Development] Technomancer:
Could you find any refernce or post about how it was fixed in Overcome?

BTW, anyone having reboots when the Tab goes to sleep, it is a sure sign of still having Froyo bootloaders.

@Jeffro64

I haven't wiped my tab since I switched to use GB kernel in my CM7 port. You don't need to wipe after updates, only after switching from other ROM.

I guess I will keep on "testing" music + bluetooth ;-)

Did you see anything interesting in logcat when music stops playing? Also, please be sure not to use any over/under clocking, volting, different governors etc. Keep it like stock.
[Galaxy Tab  Android Development] Jeffro64:
OK kewl... I didn't think you would be doing wipes, just making sure trying to narrow things down. I haven't had a chance to do a logcat yet but will asap.
[Galaxy Tab  Android Development] tangcla:
I'm a latecomer to the party... so my understanding is that this ROM is good enough to use for daily use, except for video recording?
[Galaxy Tab  Android Development] Yom:
Dude, this firmware kicks ass!

Posted using my hacked, rooted, undervolted, overclocked, pimped-out and overall bad-ass Samsung Galaxy Tab.
[Galaxy Tab  Android Development] Technomancer:
Yes, I use it as my daily driver on my giant phone ;)
[Galaxy Tab  Android Development] tangcla:
Great!

I have a Telstra Galaxy Tab from Australia, would this be suitable?