yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] rayzryd266:
I don't see dsb9938 anywhere so you may be right. When flashing the kernel can I flash just that file in heimdall... and is a wipe required afterwards?
[Galaxy Tab  Android Development] cooljo555:
The only issues I'm having so far is that when I leave my tab plugged in to charge overnight, I occasionally wake up to an unresponsive black screen; I'm assuming the device is still powered on but does not respond to any of the button presses, only when I hold the power button for like 15 seconds will the device power down then back up. Has anyone else noticed this? I am running @1.2 Max 1.0 min with smoothass. I'm remove OC to see if that's the issue.

Also, is anyone else having issues with the market saying its incompatible with this device for apps like maps and zinio, ones I know for sure I have been able to download in the previous version of the market.

Lastly, I get random force closes on random apps, mostly my verizon, maps, and process.acore, not enough to ruin my use but even after force stop and clear data on these apps, when I leave the tab for a while then come back to it, i sometines unlock to a force close or two
[Galaxy Tab  Android Development] cooljo555:
Yes u can flash just kernel, don't believe wipe is required as I don't think this kernel converts to ext4
[Galaxy Tab  Android Development] rayzryd266:
I reflashed the kernel and still have the same results in setcpu - I am re-downloading the rom to see if I got a bad download the first time and will re-try the kernel to see if that fixes things for me. I'm wondering if I should be wiping cache and dalvik prior to flashing the kernel (I always did with my tbolt), but not sure if that applies with the tab.

Other than the things I've listed, everything is working great. Transitions are smooth and layout is awesome. I will be golden if I can get the wifi/3g fixed (I'm hoping that the kernel will do that)

BTW-here's my tab info in about if that helps:

hardware - I800.0.3

model - sch I800

firmware - 2.3.5

baseband s:I800.0.3V.E104

kernel - 2.6.35.7

build - sch I800 E104
[Galaxy Tab  Android Development] leapinlar:
You definitely have the wrong kernel. The kernel should say:

2.6.35.7-dsb9938.VZW.GTab.EI04.1.1.2

You should be able to flash just the kernel. You are right, it may be a bad download and unzip. Did you have gingerbread on your device before you flashed Galaxy Cubed? If so and your kernel flash failed, you would still have the stock gingerbread kernel installed (or worse, the froyo kernel).

That also might account for your wifi problems. The wifi kernel module has to be matched to your kernel, and it's probably likely dsb9938 rebuilt his kernel module to match his custom kernel and that gets installed to /system with his factoryrfs. (Edit: I can't seem to find a wifi kernel module on this device, so maybe it's done a different way. In any case, having the wrong kernel could cause wifi issues.)

It's always a good idea to wipe cache and dalvik cache any time you flash anything. Not always necessary to wipe data.
[Galaxy Tab  Android Development] rayzryd266:
I checked md5sums and got a good download - reflashed the kernel and it soft bricked the tab. I put it in download mode and reflashed the whole rom and noticed right away a few differences - got the cube wallpaper this time (I think I copied an older version before it was taken down - the wallpaper was an abstract thing) Now everything looks like the OP including the kernel information.

Only thing so far is I lost 3g after about 5 minutes of booting up (didn't even finish the set up process). Running on wifi for now but will reboot after setup and let things settle for a while to see what happens.

---------- Post added at 12:17 PM ---------- Previous post was at 12:04 PM ----------

when I bricked it I couldn't get back to the recovery screen - it just hung on an empty battery screen or on the samsung screen. I got it into download mode and re-installed the rom (without wiping anything) but wiped afterwards. Do you think I should I stop now and wipe then re-install....before I go through and replace all my apps and accounts?

Also - I kept getting a forceclose error: Sorry! The application Market (process com.android.vending) has stopped unexpectedly. Please try again.

I went back and cleared data from the app and rebooted with no other issues so far.
[Galaxy Tab  Android Development] leapinlar:
The reason I recommended wiping cache and dalvik cache is that the contents of dalvik cache must match the apps you have on your system. That cache helps loading and running those apps. If you don't wipe before trying to run them, you have a chance that they won't match (you might have flashed newer versions of your apps). By deleting what is there, you force the system to rebuild the cache on first boot so they have to match. If you are using recovery to flash, it does not matter which order you do it, as long as it's done before you boot. Of course if you wipe data, you have to reinstall all your added apps and reconfigure your system apps.
[Galaxy Tab  Android Development] rustyshack3:
Looks like 1.6GHz is just a bit too much for the Tab. Mine started FCing like crazy and then powered off. Glad I didn't set at boot. 1.4GHz seems to be great, but I still don't have it set at boot. I rarely reboot my Tab, so I don't mind setting it each time. The lagfree governor is my favorite. Also, if you are just playing music, that's a good time to underclock to say 800MHz to save battery.

Just some tips for anyone just starting to play with overclocking.
[Galaxy Tab  Android Development] rayzryd266:
I am going to go ahead and re-wipe everything and then reflash the rom. I can't get 3g to hold for more than a few minutes, so I wanna start from scratch to see if it's not a hardware problem (bought this tab "factory refurbished" from big red).
[Galaxy Tab  Android Development] leapinlar:
You can also try one of the vanilla stock, rooted gingerbread 2.3.5 ROMs here. There is one by dsb9938 and one by lexriley (his is titled root guide, but has a vanilla ROM). That way you can rule out hardware issues as a cause. If you still have problems, it is probably hardware.
[Galaxy Tab  Android Development] rayzryd266:
good idea! Will give that a shot if this doesn't fix it
[Galaxy Tab  Android Development] rayzryd266:
it's a no go for me - 3g won't stick on anything. Got Verizon to send me another tab. Anybody have the files (verizon stock 2.3.5) to unroot before I send it back. It's a shame though, because everything else is working.
[Galaxy Tab  Android Development] dav3yb:
are you using setcpu to do this?

does setcpu just use that slider and you apply it at that? the set to boot option is just to lock that into place right?
[Galaxy Tab  Android Development] leapinlar:
Yes, use setcpu. Move the slider and it instantly takes effect. Do not check set on boot until you are sure it is stable at the selected speed. Let it operate for a while. You might even want to go to info and run a stress test to see how it performs at the new selected top speed. When you are sure it's stable then you can come back and add the check so that it always starts out at the new settings.
[Galaxy Tab  Android Development] rayzryd266:
Can anyone point me to a stock 2.3.5 rom (not rooted) - searched and I keep getting rooted ones. I found a older ECO2 file (which updated to the 2.3.5) but it has the superuser app installed with no way to remove it - even though it's not rooted. I need to get this back to stock before I send it back. Any help is greatly appreciated
[Galaxy Tab  Android Development] Jacklad:
I used the files at the following link:

http://www.droidforums.net/forum/sam...oyo-2-2-a.html

Flash the files in Heimdall - will bring you to STOCK EC02, then allow you to download and apply the 2.3.5 VZW OTA upgrade as well - worked great for me -
[Galaxy Tab  Android Development] leapinlar:
Your link is broken. It has the ... in the middle that does not allow the page to be found.
[Galaxy Tab  Android Development] rayzryd266:
Were you able to load this file without superuser in it? And it does appear broken (page not found) as leapinair stated.
[Galaxy Tab  Android Development] leapinlar:
The existence of superuser.apk is not necessarily evidence of having been rooted. That app can be installed from the market. It can't be uninstalled using your unrooted Tab if it was installed in /system/app.

The reason the OTA update does not remove the superuser is because it is a patch, not a complete new system. The patch does remove su, I think, and that is why you lose root.

However, I think superuser.apk can be removed with ADB on your PC.

I sent my rooted Tab in for warranty replacement because it had a borked battery and no way to turn it on. Never got any grief from Verizon.
[Galaxy Tab  Android Development] leapinlar:
Another thing you can try is to flash back to EC02 with the superuser.apk in it (don't let it update to EI04) and root with SuperOneClick 2.2. Then immediately unroot with it. I don't know if that removes all evidence or not.

Edit: Come to think of it, I used Z4root to root my EC02. That may work too. The unroot on it says it removes all files it installed. And you do all that from your Tab.
[Galaxy Tab  Android Development] rayzryd266:
Ok, thats a relief! I am currently not rooted (checked with setcpu) but have the su in the app drawer and was worried. I totally suck at adb and stay away from it for fear of destroying any device I try to modify with it.

Here's my new dilema - since unrooting my 3g has been fine all day, not one glitch! This was my reason for getting a replacement. When I get home I am going to re-load cubed3 and see what it does (i can always send the replacement back). My thinking is that I jacked it up when I first tried to install cubed. If nothing else, I am gaining valuable experience with this device...lol. If it works, I will apoligize in advance for cluttering up the thread with my noobness.
[Galaxy Tab  Android Development] Jacklad:
So sorry - this should work - copied from browser -

http://www.droidforums.net/forum/sa...-how-flash-stock-rooted-ec02-froyo-2-2-a.html

Sorry again -

FYI - link may look incomplete, but I can click and get to site -
[Galaxy Tab  Android Development] rayzryd266:
I saw that while in my search of the www for a solution. I didnt use it because the file says rooted EC02.
[Galaxy Tab  Android Development] leapinlar:
I think I figured out your 3g problem!

Cubed3 and his vanilla rooted ROM do not install the updated modem.bin file needed for EI04. The OTA update does install the updated modem.bin file to your system. So, unless you did the OTA first before you installed Cubed3, you would have the EI02 or earlier modem installed, giving you 3g problems. Now that you have done the OTA, you have the right modem and Cubed3 should work.

So, as a warning to any that want to install this ROM, be sure you have done the OTA update to EI04 first.

(dsb9938, you sort of say this in one of your posts buried in the middle of this thread, but I recommend you modify your first post to give a clear warning. And maybe include a link and some instructions on how to apply the OTA.)
[Galaxy Tab  Android Development] prscott1:
The techs working on the pads typically don't go diving into the apps or folders - so you should be okay. :)
[Galaxy Tab  Android Development] rayzryd266:
Not sure if this is my solution. I re-installed the rom and it worked (3g) for awhile, but eventually crashed again. If no one else is having this issue it must be something I'm doing or done. Is there something I could clear or reset to try it fresh or maybe a different kernel (just grasping at straws here) I really love this rom and want to keep it as my daily, but 3g is a must and I just can't get mine to stick.....
[Galaxy Tab  Android Development] leapinlar:
You mentioned the 3g worked all day. But you said you were not home. But now you're home with a new ROM and it quit working. Could it be your cell towers at home? Or does it not work away from home too? Just a thought.
[Galaxy Tab  Android Development] rayzryd266:
Hmmmmm.......Haven't tried it away from home - my phones get great 3g signal here but I will test it tomorrow to see if that's the case.
[Galaxy Tab  Android Development] leapinlar:
You say your phones get great 3g coverage at home. Verizon 3g? How do you have your CDMA roaming set in settings? Do you have it on automatic, or home only? Try automatic if it's not already.
[Galaxy Tab  Android Development] leapinlar:
I did a little more research. Based on what you posted earlier about your settings, you had the new modem installed from the getgo. Your information in baseband said EI04. That is the modem version. So either you or the person you bought it from had done the OTA. So I see why there was no improvement.

I still suspect tower connection problems.
[Galaxy Tab  Android Development] rayzryd266:
Isn't E104 the same modem everyone here is on? I lose the 3g everywhere I've been today (4 different locations).... I just don't get it. I have to reboot to get it back. I'm gonna do a complete wipe and try the vanilla for a full day. Other than that, the only thing i can try is another device
[Galaxy Tab  Android Development] leapinlar:
EI04 is the latest modem that people are on. Do a data wipe to. That way there is no carry over except the modem and bootloaders. I tried to find the original DJ11 files for heimdall, including bootloaders and modem, but can't seem to find it now. I know I saw it somewhere. That would take you completely to original stock. But I can't find it.
[Galaxy Tab  Android Development] rayzryd266:
http://www.androidcentral.com/whos-having-data-issues-verizon

I wonder if this had anything to do with my issues - doesnt really matter now since they just sent me a replacement. This is just my kind of luck too
[Galaxy Tab  Android Development] larry0071:
I'm with no 3G, no 4G, and not even 1X here North of Pittsburgh. Luckily I'm now set home on WiFi.

HTC Thunderbolt 4G using Tapatalk.
[Galaxy Tab  Android Development] rustyshack3:
Hey, any chance you can get the Wii remote support working with this rom?
[Galaxy Tab  Android Development] tylercarter:
I can see a tablet going through a TV in the near future.
[Galaxy Tab  Android Development] dsb9938:
Dunno what that is.

D
[Galaxy Tab  Android Development] dav3yb:
so i got my tab in today! pretty excited... did the vzw update for it to play around with it a bit first... but im downloading galaxy cubed right now...

you have to put the tab in download mode first right? where it has the yellow caution sign and "Downloading... Do not turn off target!!!" ??

you flash from there, then boot into recovery mode (vol up) and factory wipe?

.....

well it took a while after the reboot from flashing, but it looks like im up and running on Galaxy Cubed...

is there a way to turn off the verizon modem? or disable it looking for data? it says im data roaming and its kind of annoying looking at that.
[Galaxy Tab  Android Development] leapinlar:
You can go to settings, wireless and networks, mobile networks, and uncheck use packet data. This at least stops it from trying to connect. I don't know if that will remove all annoying notifications.
[Galaxy Tab  Android Development] Lubencw:
Just flashed this last night after running cm7..Very clean and smooth . Love it
[Galaxy Tab  Android Development] dav3yb:
so this morning i've been getting a lot of force closes on android.process.acore

has anyone else had this issue?

added:

i just tried to re-flash galaxy cubed, and after it booted up, i restarted the device, and right when i unlocked it, i get the acore force close. =(

sadly, i could find nothing about the acore process, seems to be something that could be caused by multiple things. i've gone back to the stock rooted rom, and things seem to be working fine from there.
[Galaxy Tab  Android Development] hirurg:
hello everyone

I do not know what not to do it properly, but when it starts to boot can be heard ringing in the background and the screen stays black, does not want to go on. in recovery not enter at all ... other ROMs work properly only the constant real problems. Who is there any solution for this my problem.

thanks to all
[Galaxy Tab  Android Development] o2sys:
OC @ 1.6 it freezes and restarts, Have it at 1.4 and seems stable
[Galaxy Tab  Android Development] SuperDave1685:
Hey there guys. Awesome ROM. I've been running it for a couple weeks now with no real issues (other than stupid things I've done).

Just a quick question - I changed the wallpaper, but I'd like to get back to the wallpaper that was installed with the ROM (the one with the cube of drawers). How do I get back to that? Is it saved somewhere?
[Galaxy Tab  Android Development] beechnut:
I looked through the thread. Did we ever get any resolution on the battery draining while the device is turned off. It was mentioned that it might have been a kernal problem but I think that was prior to updates. In any case I have the latest version of cubed and my battery is discharging over night with the device off. I lost like 15% battery over night.

Thanks for all your hard work!
[Galaxy Tab  Android Development] prscott1:
AFTER flashing cubed, remember to go back into recovery mode and wipe data/cache. This will clear up all the force closes.

---------- Post added at 12:42 PM ---------- Previous post was at 12:40 PM ----------

I was having some issues with battery drain, but doing another wipe of the system, data, cache partitions cleared it up for me. Also, for me, the boot up process alone takes a few cycles off my battery. I lose less battery on my pad by keeping it turned on overnight than by shutting it off. I only lose a couple percent points with it off over about an 8 - 9 hr period. I keep sync on too.

---------- Post added at 12:44 PM ---------- Previous post was at 12:42 PM ----------

I would suggest that you reflash the Cubed ROM using heimdall and then wipe data and cache AFTER you flash the ROM.
[Galaxy Tab  Android Development] rustyshack3:
It's not using the tablet AS the remote, it is using the Wii remote with the tablet.

People use that for emulators, etc.

---------- Post added at 01:53 PM ---------- Previous post was at 01:51 PM ----------

You can turn on Airplane mode and then turn wifi on/off separately.

You can also hold the power button and then click Data network mode to turn data off.

---------- Post added at 01:54 PM ---------- Previous post was at 01:53 PM ----------

Weird, I think that was the same day my tablet started doing that. acore was crashing all day. After a couple reboots, it stopped.
[Galaxy Tab  Android Development] cooljo555:
I didnt know that this was an issue, I will check this on mine and report back. I was having issues with force closes on maps and when I left the tab unused for a while it wouldn't wake up, I had to hold down the power until it rebooted. I reloaded the stock rom then took the update then flashed GCubed3 and yet the problem persisted. I tried getting autokiller from the market but am unable to download BC my "device is incompatible" which I know i should be able to get. Finally I am using automatic task killer from the market and all seems well, it closes apps when I unlock. i can select a list I want to keep on my device but not running in the background and so far I haven't had any fc's yet or the unresponsive black screen I mentioned earlier.
[Galaxy Tab  Android Development] TadPole415:
Tab's pre-GCubed3 flash state

With regard to returning Tab to stock before taking the [OTA] updates before flashing GCubed3, I'm wondering if D's "[2.3.5]Stock+Root Vanilla" ROM is an adequate starting point for flashing GCubed3...?

Before successfully flashing "[2.3.5]Stock+Root Vanilla" ROM, I had to "Restore VZW Galaxy Tab to stock DJ11", as flashing Z4ROOTed Tab resulted in failure to start (in addition, volume-up/power menu flashed several times on-screen, then disappeared...so data/cache wipe not possible).

Although the rooted kernels of both ROMs are different, I'm hoping the rooted-stock will not interfere with flashing GCubed3...? (As the many tweaks of GCubed3 ROM are "calling to me...")
[Galaxy Tab  Android Development] leapinlar:
To have the correct modem (baseband) you need to go through the OTA update first. Neither D's Cubed 3 nor his Stock + Root Vanilla have the modem update to EI04 baseband.

And you need to be at EC02 (Froyo 2.2) or older for the OTA to work.
[Galaxy Tab  Android Development] dav3yb:
After both times flashing it, i did boot into recovery and wiped everything. after a reboot, the acore process continued to force close.

I might try it again if i get a chance, but right now i've got the stock and rooted rom on it, and i've got it set up a bit more to how i like it.

i rebooted the device 3 or 4 times, and i continued to get the force close.

i really liked how galaxy cubed looked, but to be honest, touchwiz 4 was even more of a headache than the stock launcher it came with.
[Galaxy Tab  Android Development] vickers24/7:
anyone having problems with tab going into airplane mode by itself and losing 3g connection repeatedly. I am running the original cubed before the rebuild. any help would be great
[Galaxy Tab  Android Development] dsb9938:
Upgrade.

D
[Galaxy Tab  Android Development] vickers24/7:
As in upgrade to the cubed rebuild???
[Galaxy Tab  Android Development] rayzryd266:
can anyone tell me how to add icons to the dock? I found where I can add slots but I am unable to place any app icons in it.
[Galaxy Tab  Android Development] leapinlar:
You should be able to just drag and drop an icon from your desktop to the empty dock position. If you can't, you may have desktop locked. Go to menu, more, and tap unlock desktop.
[Galaxy Tab  Android Development] prscott1:
You should upgrade to the latest cubed. No problems.

---------- Post added at 12:11 PM ---------- Previous post was at 12:07 PM ----------

First go to preferences - Dock Settings - and set the number of apps you want in the dock in Icon Dock Count. Restart and Save under Power Controls on the UI Settings.

Then, go back home and open the app drawer. Go to menu and press edit. Then drag and drop the apps you want on it.
[Galaxy Tab  Android Development] rayzryd266:
Thanks! That worked like a charm - couldn't figure that out for the life of me.

Is it common for the tab to reboot when long pressing an app (like to move it)? If not, are there any ideas on settings or tweeks to correct it.
[Galaxy Tab  Android Development] adrian2pm:
can i use cwm to flash this rom on sprint tab?
[Galaxy Tab  Android Development] leapinlar:
I don't know if it will work on a sprint tab, but you definitely cannot flash it with cwm. It has to be done with Heimdall.
[Galaxy Tab  Android Development] adrian2pm:
thanks..ill stay away
[Galaxy Tab  Android Development] ShannonPricePhoto:
loving this ROM, nice and fast.

question tho.. on the pull down for notifications and brightness... in landscape you can never see the notifications because the switchers and brightness are way bigger than they need to be. Can I put in a request to revamp this? I used a rom on my captivate and they went nuts on making that functional and 'pretty'
[Galaxy Tab  Android Development] jferg5:
ok guys, i'm getting a tab off my friend, i believe its still stock 2.2. i'm used to using odin, att captivate, can i just odin a kernel, then flash. or do i need to use hemindall to do it all? if hemindall, do i just need to place the correct extracted files in the slots like i saw in a tutorial? thanks for all the work, looking forward to being a part of your group.

sent from cappy ice cream sandwich
[Galaxy Tab  Android Development] laihafloyd:
you must use heimdall. And yes, extract the files, put them in their corresponding slots, get into d/l mode, plug in the tab, flash, get into recovery and wipe data/factory reset. Worked like a charm for me.
[Galaxy Tab  Android Development] SuperDave1685:
Just place the respective files in Heimdall and then flash. Easy as cake really. Just make sure you install the drivers from the /drivers folder once you extract Heimdall