yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] iDar:
Did you try a new one because I also have 2 old cables. I am still using both of them recharging and for connecting my tab with PC but using those cables my device was not recognized in ODIN when my device was stuck so I bought a new cable and it worked in first go. .
[Galaxy Tab  Android Development] robjective:
I'd like to be added to the list of CDMA testers. Thanks
[Galaxy Tab  Android Development] DJCrapsody:
No damage, cleaned, not recognized as well.

Considering one of them is from the Galaxy Tab 2 that was bought not long ago, I've tried a new one.

REVIVAL IN PROGRESS:

1. Trying out the 4-hours-overnight-charge & 20-minutes-odin-detect-wait method. But doesn't seem to have any effect yet.

2. Already tried on 2 PCs and different USB ports.
[Galaxy Tab  Android Development] droiduzr2:
Then your device has a damaged port.

This happened on a Samsung phone I had. It would charge but never detect the phone in Windows or Linux.

Remember to have Odin open FIRST then put the unit into download mode THEN connect the cable to the computer and Odin should recognize it.

You have to do it in that order.
[Galaxy Tab  Android Development] DJCrapsody:
Not a damaged port. Data transfer is fine, previous ODIN flashes are fine too, I've tried doing the 3 steps in all the orders you can think of (total of 6 orders).
[Galaxy Tab  Android Development] stimpz0r:
and you tried this in download mode of course?

download mode = holding power + vol DOWN until you see the galaxy tab splash, let go of the power button and you will see the download screen. once there ODIN (or Heimdall) should easily be able to detect your tab.

i strongly suggest getting Heimdall working instead of Odin and extracting a kernel from cm 10.2 - once you flash that you will be able to get back into recovery and work from there - note that the tab wont boot with a cm 10.2 kernel, but it will get you recovery.

see previous posts on how to use Heimdall from command line, or use the frontend and flash the boot.img as both KERNEL and RECOVERY.
[Galaxy Tab  Android Development] droiduzr2:
did you try different computers?

also try other usb ports

try using mobil odin

put your file on the external sdcard
[Galaxy Tab  Android Development] DJCrapsody:
Well considering I've flashed using ODIN before, could be easily known that I'm of course in download mode.

Both Heimdall and ODIN have the same issue of not detecting my device.
[Galaxy Tab  Android Development] boatpoyo:
For now, Can't play 1080p vedio file
[Galaxy Tab  Android Development] enakeprimen:
AOSP 4.4.1 makes WhatsApp running well on ART mode.. Great :good:
[Galaxy Tab  Android Development] robindebruin:
recovery

hey i can boot both from system and buttons to cwm recovery
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback.

Sent from my GT-P1000 running KitKat
[Galaxy Tab  Android Development] priyana:
Hi devas,

I have a question.

Up to CM 10.1, if we come from stock partition, the kernel is able to repartition from bml to mtd of certain sizing.

Can't we have CM 11 kernel/install script that automatically repartition from bml to the newer mtd with larger cache?
[Galaxy Tab  Android Development] adi6262:
I was going to suggest exactly this! +1.
[Galaxy Tab  Android Development] robindebruin:
My cache partition is 502 MB can i use art with that

---------- Post added at 03:37 PM ---------- Previous post was at 03:06 PM ----------

It worked ?
[Galaxy Tab  Android Development] robindebruin:
Hey my log show some error

+ /tmp/busybox true

+ /tmp/busybox mkdir -p /radio

+ /tmp/busybox grep -q /radio /proc/mounts

+ /tmp/busybox umount -l /dev/block/mtdblock3

umount: can't forcibly umount /dev/block/mtdblock3: Invalid argument

+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock3 /radio

+ /tmp/busybox test -e /radio/modem.bin

+ /tmp/busybox umount -l /radio

+ /tmp/busybox test -e /sdcard/cyanogenmod.cfg

+ /tmp/bml_over_mtd.sh boot 72 reservoir 2004 /tmp/boot.img

+ /tmp/busybox umount -l /system

umount: can't forcibly umount /system: Invalid argument

+ exit 0
[Galaxy Tab  Android Development] droiduzr2:
I think I might know what you need to do.

Assuming that you have a working ROm, use the dialer to enter the code to get you into service mode and look for setting the connection to USB.

I recall something like this a long time ago. You have to go into the service menu and set the connection to USB mode. It might have gotten set to PDA or phone mode, you will see the other options in that menu.

good luck
[Galaxy Tab  Android Development] bunchies:
Any progress for the P1C getting 4.4?

Its only used as a WiFi tablet so I can't be a tester for cdma

and If CDMA is the only issue could you have a build for it that is WiFi only?
[Galaxy Tab  Android Development] terenceng:
Someone had brought this up earlier. Sure it can be done, but I want the flasher to be held directly accountable for his actions and not blame it on install script if anything goes wrong. He has to take that first step, and bear all the risks. If it is any consolation, it is VERY DIFFICULT to brick your tab or screw up your sdcard beyond repair UNLESS YOU INTENTIONALLY WANT THAT TO HAPPEN. And as someone pointed out, this is XDA.

Though not a big fan of Overcome, kudos to you for spreading the word on Overcome all this years. It was the first custom rom on my p1. Why not work on it to have a more recent Android version instead of stopping at GB? Give KitKat a try. The builders scene is never too crowded.
[Galaxy Tab  Android Development] robindebruin:
Hey apps are fast opening but installing takes verry long
[Galaxy Tab  Android Development] priyana:
Hi terenceng. I am not a developer, not a programmer at all. Just a system guy in the real world.

I wish I know how to mod at all.

I only spread overcome with sos_sifou and aprilla helps to host the file, because it is so reliable to restock with it.

As about user blaming install script, isn't all the current kernel already do the mtd repartitioning? Anyway, just so that more people can enjoy ART.
[Galaxy Tab  Android Development] stimpz0r:
It is absolutely doable - however if cdesai decides to use a different partition table on his official releases (whenever he decides to release them) then it will cause mass problem between builds. What is needed is to get a decision made on what partition layout will work best for all and implement that throughout.

---------- Post added at 10:18 PM ---------- Previous post was at 10:14 PM ----------

Well considering you never mentioned that you were in download mode, it's an easy assumption to make.

Next time someone tries to help you I suggest you don't make a smart remark and be thankful for the fact someone is trying to help you.
[Galaxy Tab  Android Development] DJCrapsody:
I do apologize if it sounded like a "smart remark", no intentions on doing so, and I do appreciate your attempt to assist. Will continue trying to revive this damn tablet.

UPDATE:

Thanks to those who attempted to help. Appreciate it lots, I have found the only solution that worked. I will sound stupid when you guys read the next line:

I installed Kies (which I hate a lot since I don't really have a TouchWiz device) and it worked.

I KNOW. I hate Kies that much. :(
[Galaxy Tab  Android Development] robindebruin:
Cx5 could you plz give look on this

---------- Post added at 03:50 PM ---------- Previous post was at 03:50 PM ----------

Hey my log show some error

+ /tmp/busybox true

+ /tmp/busybox mkdir -p /radio

+ /tmp/busybox grep -q /radio /proc/mounts

+ /tmp/busybox umount -l /dev/block/mtdblock3

umount: can't forcibly umount /dev/block/mtdblock3: Invalid argument

+ /tmp/busybox mount -t yaffs2 /dev/block/mtdblock3 /radio

+ /tmp/busybox test -e /radio/modem.bin

+ /tmp/busybox umount -l /radio

+ /tmp/busybox test -e /sdcard/cyanogenmod.cfg

+ /tmp/bml_over_mtd.sh boot 72 reservoir 2004 /tmp/boot.img

+ /tmp/busybox umount -l /system

umount: can't forcibly umount /system: Invalid argument

+ exit 0
[Galaxy Tab  Android Development] cx5:
Answers to how to get those numbers & what do they mean?

EDIT 12th Dec 5:35PM - 200MB only enough for ROM to use ART but not enough with gapps, now I am using 256MB, so far so good. below no longer valid

From

Command (m for help): p as per adviced by darkpal to check the total number of heads. Mine was 1 like his.

Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes

1 heads, 16 sectors/track, 1944064 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 5 1681920 13455328 83 Linux

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2 1681921 1931264 1994752 83 Linux

Partition 2 does not end on cylinder boundary

/dev/block/mmcblk0p3 1931265 1944064 102400 83 Linux

Partition 3 does not end on cylinder boundary

102400 is the 100MB cache that most of us have.

It seems be to coming from 1944064 minus 1931265 = 12799, which doesn't look like 100MB at all. It's OK it's a reference.

Since we want another 100MB (someone said worked for him, not necessary 256MB, so I am trying, god bless).

Then we minus another or should I say the same 12799 on 1931265 = 1918466

Then work our way up again, is just minus 1 = 1918465

So the new partition 2 shall continue as per laid out above from 1681921 but ends at 1918465.

Then partition 3 starts from 1918466 ends at 1944064

rerun "p" and we'll see 204792 around 200MB. It comes from 1944064 minus 1918466 = 25598

then 25598 multiply 16 and multiply 512 = 209698816 around 200MB.

---------- Post added 10th December 2013 at 12:07 AM ---------- Previous post was 9th December 2013 at 11:57 PM ----------

@robindebruin,

I have looked at your logs, but I am not a dev, not a programmer either. It took me two weeks by re-reading everyone's post, especially areshinakya, freetogo and darkpal to understand and make it work for myself.

What kind of help do you need?

[MENTION=535343]all[/MENTION], 200MB cache is working for me.

Installed Terence's rom 6th Dec, cut down slim version without IME, no wallpaper, no soundrecorder, no videoeditor, no TTS, 160MB rom.

23:51 reboots from fresh all wipe and install light version rom.

23:58 shows android upgrading 71 apps in all.

00:05 complete. home screen appear. ONE FC.

Again it's repeating as shown in youtube. 7 minutes to get from CM logo (off center half way cut off) then another 8 minutes to home screen. 15 mins in all. Regardless of how many apps I think.

Reboot into TWRP OK. Installing gapps core + standard now.

EDIT 12th Dec 5:35PM - 200MB only enough for ROM to use ART but not enough with gapps, now I am using 256MB, so far so good. above no longer valid
[Galaxy Tab  Android Development] robindebruin:
Yeah but is is harmfull if that happens at every boot

---------- Post added at 04:14 PM ---------- Previous post was at 04:09 PM ----------
[Galaxy Tab  Android Development] cx5:
Thanks DarkPal. I didn't understand when I first saw your statement, but ultimately remembered deep in my mind, hence checked as you said. Luckily, avoided a mess of my own. Double thanks.
[Galaxy Tab  Android Development] zecampesien:
TWRP access

Hello,

I also installed Terence's rom 6th Dec. Worked ok but I had few FCs.

So i went to TWRP to wipe several times. It did a "kind of" factory reset.

I rebooted.

Well. My GTab is now stock on 4.4 with no app at all.

However, I forgot to flash Gapps :(

Since the factory reset, I also cannot choose to boot from recovery.

Any help would be much appreciated to go back to TWRP.

Tx !
[Galaxy Tab  Android Development] 1sthandy:
worked on last rom 6 Dec 2013 Android 4.4.1 for me

tested a few usb Sticks also connecting Canon Eos650D with Magic Lantern

Greetings 1sthandy
[Galaxy Tab  Android Development] robindebruin:
Plz show your cable
[Galaxy Tab  Android Development] 1sthandy:
http://www.droidwiki.de/Samsung/Galaxy_Tab/USB_Host_Controller

Greetings 1sthandy
[Galaxy Tab  Android Development] yellowshed:
use heimdal flash

Hi, I had this several times. You need to get a boot.img from another ROM with TWRP and use heimdal to flash - check previous posts for command line and suggestions of where to find the image. I used the one from the JB MR release from the SGT7 team.

On flashing, the tab will reboot. As it does so, use power and vol up to boot into recovery. Then re-flash ROM and GApps together and do a Dalvic/cache wipe.

Hope that helps

YellowShed
[Galaxy Tab  Android Development] zecampesien:
Tx for your tip YellowShed.

I am wondering why you suggest to use boot.img from another ROM since it is already present in this CM11 ROM ?

I will use this command

heimdall flash --KERNEL boot.img --RECOVERY boot.img

Do you think this is the good one ?

Tx
[Galaxy Tab  Android Development] yellowshed:
I'm taking the advice from terenceng who says you can't use the one from his ROM as it doesn't do the vol up/power thing to go into recovery. He said use the boot.img from another ROM, though you won't be able to boot with it, it's enough to get you into recovery.

YellowShed
[Galaxy Tab  Android Development] insanity213:
Regarding a P1C build - Not sure how far along you are, but was wondering if you had a working manifest and/or blobs? Would be willing to attempt to get it to build but not sure where to go for the vendor specific stuff. Should I install the latest CM and rip those blobs?
[Galaxy Tab  Android Development] terenceng:
Thanks I've those. Need to first make the P1C boot to system with cm10.2+.
[Galaxy Tab  Android Development] id-robot:
My repartition process

I flashed successfully from CM10.2(cm-10.2-20131104-UNOFFICIAL-p1.zip) to CM 11(cm-11-20131201-terenceng-p1.zip).

Following are processes to repartition.

After flashing, it took about 5 min to reboot completely. And then I converted to ART and took about 10 min to upgrade 79 apps.

I felt running apps in ART is faster.

==================================

go to recovery mode

>adb shell

~ # ls

~ # umount /cache

~ # fdisk /dev/block/mmcblk0

The number of cylinders for this disk is set to 1944064.

There is nothing wrong with that, but this is larger than 1024,

and could in certain setups cause problems with:

1) software that runs at boot time (e.g., old versions of LILO)

2) booting and partitioning software from other OSs

(e.g., DOS FDISK, OS/2 FDISK)

Command (m for help): d

d

Partition number (1-4): 2

2

Command (m for help): d

d

Partition number (1-4): 3

3

Command (m for help): n

n

Command action

e extended

p primary partition (1-4)

p

p

Partition number (1-4): 2

2

First cylinder (2-1944064, default 2): 1681924

1681924

Last cylinder or +size or +sizeM or +sizeK (1681924-1944064, default 1944064): 1911296

1911296

Command (m for help): n

n

Command action

e extended

p primary partition (1-4)

p

p

Partition number (1-4): 3

3

First cylinder (2-1944064, default 2): 1911300

1911300

Last cylinder or +size or +sizeM or +sizeK (1911300-1944064, default 1944064): 1944064

1944064

Command (m for help): p

Disk /dev/block/mmcblk0: 15.9 GB, 15925772288 bytes

1 heads, 16 sectors/track, 1944064 cylinders

Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System

/dev/block/mmcblk0p1 * 129 1660160 13280256 c Win95 FAT32 (LBA)

Partition 1 does not end on cylinder boundary

/dev/block/mmcblk0p2 1681924 1911296 1834984 83 Linux

/dev/block/mmcblk0p3 1911300 1944064 262120 83 Linux

Command (m for help): w

w

The partition table has been altered.

Calling ioctl() to re-read partition table

~ #
[Galaxy Tab  Android Development] terenceng:
New CM-11 Build [Dec 11, 2013]

New cm-11.0 build [cm-11-20131211-terenceng-p1.zip]. Refer to changelog.
[Galaxy Tab  Android Development] terenceng:
Survey: ART on the P1000 (2nd round)

Since the 1st round of survey, some of you have converted to ART and played with it on your P1000.

(Those who missed the 1st round can go back a few posts and read the first round of feedbacks. Those who did the 1st round can do it again - you might have a slightly different experience.)

Let's have some statistics on ART running on the P1000.

For those who still have not converted to ART:

A. Why don't you convert?

(Possible answers: Don't know how to partition internal sdcard / Don't want to risk damaging internal sdcard / It is still experimental / Happy with Dalvik and see no need to change / etc)

B. Would you convert to ART some time in future?

For those who have converted to ART:

1. How many attempts did you make before successfully converted to ART (count only those after cache partition resize)?

2. Does your tab boot up faster?

3. What are the apps you notice run faster in ART mode?

4. What are the apps you notice do not run any faster in ART mode?

5. So far which apps you have tried to use cause FCs in ART mode?

6. With the current state of ART, and after playing with it on the P1000, are you happy/satisfied/unhappy/disillusioned/etc.?

7. Are you staying with ART, or going back to Dalvik?

Feel free to add any other things you want to say about ART on the P1000...
[Galaxy Tab  Android Development] boatpoyo:
Answer

For A : Don't know how to partition internal sdcard

For B : Yes
[Galaxy Tab  Android Development] cheatman:
Get the official CM11 latest nightly here: http://get.cm/get/cFj

It has the latest commits and the recovery at boot works fine. I'm testing ART now.

Cheers,

C.
[Galaxy Tab  Android Development] spike1985:
I am on 11th of December build right now. Boots fine. Did not try Art. TV-Out (analog) just gives a "colorful stripe" on bottom of the remote screen in both NTSC and Pal.
[Galaxy Tab  Android Development] fitree:
repartition

hi

i've succesfully flashed my tab to cm11 4.4.1

now i would to try ART

checked my partition table using "Partition Table" apps, it showed my cache partition size is 98++ MB

i've read in the first post,saying that cache at least needs to be above 105mb++

question is,how do i resize my partition ?

thanks
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback.

Your cache needs to be at least 200MB. Read back a few posts and search for posts by areshinakya, DarkPal, freetogo, cx5, and others on the repartitioning/resize procedure.
[Galaxy Tab  Android Development] daclothe:
Willing to test on P1C if you still need testers.
[Galaxy Tab  Android Development] cx5:
2nd round reply

first attempt ART successful, always successful, on all types of rom on all release and all version.

But when add gapps always fail, no matter install b4 or after ART, no matter what type, banks, cheatman's link, storm31's link, all FC. Some outright none-stop FC, completely unusable. Some allow to signin to playstore, but never get passed. Stuck at signing in. Never ever once completed, on all 3 types of rom, all release. All gapps are good before ART.

unknown because always have residual apps repeating the "android is upgrading", on all 3 types of rom.

for those moment without FC tried a lot of apps, does not appear faster,

nor slower.

first attempt ART few days back I think, from 4.3, without WIPE, few FC, all good, but whatsapp, titanium, sms, email not working, forced to reflash.

unknown, but willing to keep testing. Not qualified to answer.

willing to continue trying ART.

sidenotes:-

on office notebook CWM6045 + TWRP235 does not allow ADB to PC, also can't mount storage, but old CWM5xxx can ADB and change cache partition ??? but at home PC everything ok I think???

always convert to ART without gmail account, does this affect it?

always connected to power supply, can't be this ghost right?

TWRP wipe SYSTEM helps, but restocking from overcome is sometimes needed, don't know why.

CWM full is not sufficient, sometimes a lot of FC right after reflash. Got to TWRP or overcome restock.

I wonder is it 200MB marginal enough, will try 256MB.
[Galaxy Tab  Android Development] p1000haha:
settings - interface - quick settings panel - tiles and layout

dosen't work
[Galaxy Tab  Android Development] terenceng:
New Android 4.4.2 Build

New build [cm-11-20131212-terenceng-p1.zip]
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback. That option is not enabled yet by the devs.
[Galaxy Tab  Android Development] cx5:
[MENTION=1535215]terenceng[/MENTION] & devs devs et all, [MENTION=3506409]cdesai[/MENTION] [MENTION=3031478]humberos[/MENTION] [MENTION=490310]cheatman[/MENTION] [MENTION=3380725]storm31[/MENTION] [MENTION=4101982]alroger[/MENTION]

BIG SURPRISE !!!!!

My mmcblk0 changed from 1 ONE head to 4 FOUR head.

I just tried to change cache partition from 200MB to 256 and found out it turned into 4 HEAD, I could not use my previous numbers, went to use areshinakya's numbers instead.

edit

1 ONE HEAD was on TWRP2.3.5 (I think) dated 9th Dec

4 FOUR HEAD was on CWM5.1.2.6 dated 12th Dec
[Galaxy Tab  Android Development] storm31:
We have current cwm 6, not cwm 5:), but i have not seen that cdesai has changed anything in device repos.. It could be that AOSP or terenceng have changed anything. What for rom you have cuurent?
[Galaxy Tab  Android Development] cheatman:
The number of heads has nothing to do with the recovery version/type. As far as I know, the number of heads can be changed by fdisk when you write the configuration to the disk, depending on your changes and the partition setup/size/type/configuration. Also, you can manually specify the head number using the expert settings. You can read further here: http://www.computerhope.com/unix/fdisk.htm

Cheers,

C.
[Galaxy Tab  Android Development] cx5:
[MENTION=3380725]storm31[/MENTION], you're CWM is 6.0.4.5 I know.

My own problem is my notebook cannot ADB to your kernel. But my home PC can ADB to TWRP2.3.5. Anyway it's my own problem.

But my notebook like CWM5.1.2.6, hence I used CWM5126 to change cache partition and was shocked to see HEAD become 4, not previously 1.

EDIT now I know because of FASTCHARGE my notebook can't access it by ADB, thanks for explaining in another post.

Anyway, no problem, just info for you all devs.

I am now installing your ROM + core then convert to ART to try 256MB cache helps or not.

---------- Post added at 05:04 PM ---------- Previous post was at 05:03 PM ----------

@cheatman, oh I see, thanks. But I didn't change anything. It changed by itself. I don't know why.
[Galaxy Tab  Android Development] gorelshv:
Has anyone tried Tv out hdmi?
[Galaxy Tab  Android Development] cx5:
200MB cache NOT ENOUGH

[MENTION=1535215]terenceng[/MENTION] & devs devs et all, [MENTION=3506409]cdesai[/MENTION] [MENTION=3031478]humberos[/MENTION] [MENTION=490310]cheatman[/MENTION] [MENTION=3380725]storm31[/MENTION] @alroger

200MB cache NOT ENOUGH. rom can convert to ART, but all gapps FC.

now I run 256MB, immediately OK, no more FC. gapps OK. Trying other apks now, report back later.

Sorry to everyone who has been using 200MB....... very sorry.
[Galaxy Tab  Android Development] DroidTalk:
for guys like me, its too much to tinker with adb and repatitioning, i stay away from kitkat until it handles the repartitioning process itself.

thanks devs for brining kitkat to the beloved galaxy tab :)
[Galaxy Tab  Android Development] enakeprimen:
I surprised that Android 4.4.2 custom ROM is available for P1000 in this build. It's very fast and I happy to download it to try. I just flashed my tab with this build, but there is no keyboard on this build? Settings > Language & input. No keyboard as the input methods :(
[Galaxy Tab  Android Development] pinguinolandia:
WHAT USE GAPPS?:confused:
[Galaxy Tab  Android Development] terenceng:
If you install many more apps, then of course the cache size needs to go up accordingly if you use ART.

I'd like to hear about the optimal cache size for the typical installation: ROM + GApps Core/Standard + various apps + some allowance for further apps: around 300MB?

The default AOSP keyboard should be there (if not try reinstalling ROM). You can also install additional keyboards from Play Store/certain GApps packages.

You can try BaNkS GApps
[Galaxy Tab  Android Development] enakeprimen:
I have reinstalled the ROM and install the latest Banks GApps (https://mega.co.nz/#F!KEdCFDrB!C5xHHQ6ntj4Xoey7EfRlkw) to make sure it but still there is no keyboard in this build. Installing from Play Store need to login first, no keyboard to type the account :D