yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback.

OP mentioned "up to 20 minutes" to have the flasher mentally prepared and be patient and not give up prematurely.... it's never meant to mean exactly or even about 20 minutes ...

Good you do not have to replace efs or modem, as OP mentioned "if necessary"....

But thanks, I have made it clearer in OP.

Reading your feedback and the one before made me try it myself a while ago: I see Google Play Store intact (i.e. still there and launchable) after converting to ART using build 12A. My case is: cache already resized, BaNkS Core GApps installed prior to ART conversion.
[Galaxy Tab  Android Development] RogerG:
i know, I was just trying to provide detailled information (e.g. in case this might for some reason which I can not fathom have any influence on other issues. :). same is true for flash-time.

I have just tried again, same result. However, I have noticed 1 more thing: when switching to ART, it says that a dozen or so apps are updating/being configured. After installing gapps, and switching back & forth again, this number significantly increases (exact number dependent on core/standard/mini) - so I guess, that gapps might in fact get installed - and just don't show up for some reason.

Also: I can install (and subsequently use) apps from their .apks without a problem - both in dalvik and in ART

ATM I don't have access to an usb/data cable, so I can't fdisk from pc (the whole reason why I waited till now to flash); I might try other 4.4 roms tomorrow and will report here on whether the gapps-issue is a shared problem (for non-cache-size-changers)

Edit: just had a rather weird experience that somewhat reinforces my belief, that gapps do (kinda) get installed: the last gapps I tried were the package that replaces the standard dialer - but since the new apps don't show up, I'm left with a tab with no dialer at all. My thought that this meant I didn't have phone-functionality turned out to be false, when my tab rang 2min ago. I could not answer/reject the call (call terminated when I pushed power to turn on the tab) and still have no dialer, but I could call the person back via the call-back function of the missed-call notification. No in-call UI, no way to end the call - interesting experience.
[Galaxy Tab  Android Development] ohtoulouz:
Some more feedback (if it helps):

Trebuchet FC setting new BG image in both Dalvik and ART modes.

I only installed Banks Core GApps (when in Dalvik mode) -> Play Store, Google Parameters and Voice recognition show up in app drawer.

Conversion to ART was flawless (I did not resize cache) and everything runs as it should (so far, but Trebuchet).

Pierre.
[Galaxy Tab  Android Development] scanferr:
Thanks :) Will try the parted one. About the GApps it really is weird but I'll try once more and see how it goes. And I did read the OP but not the whole thread :p But I'm well aware of what's going on so far!
[Galaxy Tab  Android Development] RogerG:
just did so*:

- wiped cache, dalvik, system, flashed storm31's most recent rom, installed gapps - no problem, playstore present.

- went back to recovery, wiped cache, dalvik, system, flashed 12A again, installed gapps - playstore absent.

just for fun, I also tried:

wipe, flash storm31's rom & gapps to get playstore, then dirty-flash 12A on top (no wipes at all) - playstore present, but (unsurprisingly) other bugs cropped up in the process: menu button doesn't react, even if I set different action; back and search lose short-press, but retain long-press. these issues are not present when flashing correctly - ie with all recommended wipes, so they are of course not bugs - just thought I'd save others the trouble of trying this route).

I'll stay on storm's builds for the moment but will come try again for the next major new version. thanks terenceng!

ad*: just as additional info: all flashes brought me straight to ART, which worked in every case. I had no FCs whatsoever. Cache-partition-size is still original.
[Galaxy Tab  Android Development] shollywood:
OTG??

Can't get OTG USB to work? Any setting I need to enable?
[Galaxy Tab  Android Development] terenceng:
Good suggestion; actually there are many other stuff you can remove to conserve /system space or install as user apps

Get Y cable and the USB Host Controller app from play store.

Perhaps this post will help.

Let me know what cable configuration you use and what usb device (pendrive, keyboard, mouse, hard drive?) you connect to your tab...and whether your attempts are successful
[Galaxy Tab  Android Development] p1000haha:
Everything works better, as changing from cm-11-20131212-terenceng-p1 to cm-11-20131212A-terenceng-p1 with 12-11_GApps_Core_4.4.2_signed.zip, and the cache partition size is about 295m without changing. The A version is the smoothest one I've ever tried in ART mode.

Just have a look at /system and /cache
[Galaxy Tab  Android Development] ohtoulouz:
Hi guys,

I have installed the ROM (12A), running in ART mode with dalvik.vm.dexopt-data-only=1 and the original cache size. To be honnest, I am amazed to have my old tab running KitKat and I would like to thank you terenceng for your work. Some features are not properly working (I will list them at the end, for improvement purposes) but it is overall a great work. However, I have a request, already posted by others but not really answered: for me, the main advantage of running KitKat is to run it in ART mode: without that, my previous ROM (4.2.2 AOKP SGT7) would be just fine. And, as far as I understood, running the ROM in ART mode requires an increase cache size (the dalvik.vm.dexopt-data-only=1 workaround seems less robust). Even if I am not completely stupid, the steps required for resizing the cache are out of my understanding (the various posts on the subject are not detailed enough for me to understand the process up to a safe level for my Tab). I think many of us (not really noobs but also not really geeks) would give up on this ROM without a little help on that topic: I would really apreciate if someone could write a DETAILED tutorial on how to resize this f***g cache partition !

Not working correctly (these are details, of course...)

1) virtual keyboard on lock screen to unlock sim card if messed-up (numbers are overlapping).

2) "Interface/quick setting panel/Tiles and layout" is not responding (should it?)

3) PROFILES/settings pages do not fit the screen correctly (portrait/landscape in dual pane mode).

4) Once a profile/setting is clicked for modification, the back key/command leads back to blank PROFILES/APP GROUPS pages (dual pane mode only), whereas they were populated before calling the setting page.

Cheers.

[EDIT] I think I finally understood how to resize cache: boot the Tab into recovery and use fdisk from adb shell. It is just necessary to print the partition table, delete partitions 2 and 3, recreate partitions 2 and 3 with modifed end/start value of partitions 2/3 according to the initial partition start/end values.
[Galaxy Tab  Android Development] brenzef:
After a lot of reinstalls, wipes and cache cleans I have CM11 up and running, used BaNkS Gapps (minimal version).

Like mentioned already : Boot animation is off-center for the first few 40 seconds. (this was the case with cm10 too. Cosmetic, would be nice if fixed.

Some other issues I have noticed (maybe already mentioned somewere else).

Removing apps from the screen is difficult if you have removed the Google search bar. The "x" has disappeared when you disable the Goolge search bar.

ART does not work on my P1000, continuous FC's, impossible to get around. Restored CM10 backup and did a new upgrade to CM11.

Till now, smooth operation, meaning GREAT work!!!!

Very well done!!
[Galaxy Tab  Android Development] Kat-CeDe:
Hi brenzef,

What do you mean with Banks minimal Version? I used 12a, activated ART, installed Banks core Version and no FC up to now.

Up to now very fast and stable. Thanks again!

Ralf

Gesendet von meinem GT-P1000 mit Tapatalk 4
[Galaxy Tab  Android Development] brenzef:
Hey Ralf,

I meant the BaNkS "GApps Core 4.4.2", it seems you are using the same version. (Found it on http://xdaforums.com/showthread.php?t=2012857)

What I have read about different weird problems is that in some cases there is not enough space on the device causing FC's and other errors.

I think that is the case here too. I've seen some "no space left on device" errors during boot and in CWM.

The thing is that I don't have a clue if that is really the case and if so, how to repartition the P1000, so the new partitions can accomodate the code.

Currently with Dalvik everything works like a charm, some minor things, but nothing really disturbing...
[Galaxy Tab  Android Development] ohtoulouz:
[Q] SELinux question

Hi,

just a simple question: in french, under "Etat SELinux", it is written "Application". Is it the same as "Enforcing" under "SELinux status" in english?

For my understanding, what does it mean?

Thanks,

Pierre.
[Galaxy Tab  Android Development] bunchies:
I can be a beta tester for p1c. Would like to have kitkat on it, I know you said you want 10 people but I think the people already on the list+me should be enough

Hopefully you consider development for the p1c :good:
[Galaxy Tab  Android Development] ohtoulouz:
Some feedbacks on 12A in ART mode.

Hi terenceng,

Just to give you some news about 12A, running in ART mode for about a week:

- no more FC on Trebuchet when setting the background image

(maybe because I installed another launcher and went back to Trebuchet afterwards)

The ROM is really running fine, without reboots or FC. I have included screenshots of the problems I raised in a previous post:

Screenshot1: sim card unlock messed-up keyboard

Screenshot2: profiles in dual pane mode before cliking on settings: OK

Screenshot3: profiles in dual pane mode after cliking on settings and going back: no more profiles

Screenshot4: profile settings page: misaligned, check boxes are out of the screen (similar, but less obvious, in portrait)

Screenshot5: however, if I rotate the Tab to portrait than go back to landscape, settings pages are OK.

Pierre.
[Galaxy Tab  Android Development] terenceng:
New CM-11.0 Build [Dec 16, 2013]

New cm-11.0 build [cm-11-20131216-terenceng-p1.zip]. Refer to changelog.
[Galaxy Tab  Android Development] ohtoulouz:
Hi,

you're no more mentioning the dalvik.vm.dexopt-data-only=1 workaround for ART in the OP (or I missed it..). Does it mean that you think it is not a valuable workaround on the long term? So, I suppose this ROM does not include it, right? What can I do to prepare the upgrade (create local.prop and add dalvik.vm.dexopt-data-only=1 in it? Or perhaps modif the build.prop directly in the zip by drag&drop before flashing?)

Thanks

Pierre.
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback and screenshots.

Thanks for pointing that out. It includes that property (just like build 12A). I've updated ChangeLog.

Be patient. I'm starting with cm-10.2 then proceeding to cm-11 KitKat...
[Galaxy Tab  Android Development] ohtoulouz:
Fine !

Just to be safe, I suppose there is no need to wipe something before upgrading ROM from 12A to 16, right?

(will upgrade this evening at home - can't download due to firewall policy...)

Thanks.
[Galaxy Tab  Android Development] terenceng:
You have to wipe cache, dalvik-cache, data and preferably system before you upgrade.
[Galaxy Tab  Android Development] RogerG:
just in case you haven't resolved this problem yet (or someone else runs into this as well): do a full restock before flashing.

I had the same problem with gapps/play store when NOT changing cache partition size (but didn't have the problem on other current 4.4.2 roms). Since, I have done a full restock, OC then flashed 12A & Bank's (core) gapps - everything fine (with no changes to partitions).

a very naive question [MENTION=1535215]terenceng[/MENTION]/all other experts:

when running ART, do we still need dalvik-cache? what for? I wiped it, hoping to free up some space on /data, but of course it got rebuilt during booting. Is there a way to disable it, or is it still necessary?
[Galaxy Tab  Android Development] alroger:
I guess you can call it art-cache now? But it still is a cache to speed up app loading.
[Galaxy Tab  Android Development] terenceng:
Thanks to RogerG for the feedback.

I want to confirm this issue of Play Store not appearing for the non-cache-resize case is indeed due to what RogerG said. Has anyone who have NOT resized his cache partition been able to flash BaNkS Core GApps package and yet have Play Store app appear (i.e. it did not disappear) without a full restock (but still need a full wipe and also installing GApps AFTER rom install and reboots and art conversion)?

Upon ART conversion, the ROM still uses dalvik-cache to store the generated art and other associated files (it may change in the future), so they are necessary for ART to function...
[Galaxy Tab  Android Development] terenceng:
To P1L and P1N users:

Since I only have a P1000 to test, can you guys flash the latest cm-11-YYYYMMDD-terenceng-p1.zip and have your tabs boot up successfully, or there is still a boot-loop? If the boot-loop still exists, what if, after you flash the cm-11-YYYYMMDD-terenceng-p1.zip in recovery, you reboot immediately to DOWNLOAD mode and flash the boot_p1ln.img (located inside the cm-11-YYYYMMDD-terenceng-p1.zip), does it boot up successfully? If the boot up for P1L and P1N still fails, let me know and I'll look into it. Thanks.

In addition, can you guys get into TWRP recovery by holding Volume-Up + Power buttons after flashing the latest cm-11-YYYYMMDD-terenceng-p1.zip? What if you flash boot_p1ln.img in DOWNLOAD mode - can you get into TWRP recovery from OFF state after that?
[Galaxy Tab  Android Development] allrockedout:
Question does this support mhl HDMI out?
[Galaxy Tab  Android Development] terenceng:
Hdmi was disabled for some unknown reason by the devs but I reenabled it in build 20131216. I do not have the cable to try so perhaps you or others can try it out and let us know the outcome.
[Galaxy Tab  Android Development] scanferr:
Thanks! I'll try this now and I'll tell later if it worked or not :)

I really wanted to resize cache partition but I'm affraid I mess something up as I don't know how to it for sure :p

One other thing, isn't the status bar transparent on Kit-Kat? Why every ROM has it still black? Just out of curiosity :)
[Galaxy Tab  Android Development] boatpoyo:
I have a problem with installing Gapps

I have restck to 2.3.3 but still have a problem with gapps

I use 16 Dec 2013 build after install and reboot to system.

I install pa_gapps-modular-full-4.4.2-20131215-signed and reboot to system. I can't find play store and I change to use 4.4.2 standard Gapps.

It has a same problem. What can I do, Please help me:confused::crying:
[Galaxy Tab  Android Development] pvaldeben:
Hi Just check this and said wow, KitKat for Sprint Galaxy Tab 7. I see you need testers for this device and I would like to be involved in testing the CDMA version. Please add my name to the list of testers for the Sprint SPH-P100.

Please PM me with additional details when ready.

Thanks.
[Galaxy Tab  Android Development] scanferr:
Sorry for the double post!

I can confirm this. I did a full restock and then clean ROM installation and it now the Play Store shows up. Many thanks :)
[Galaxy Tab  Android Development] terenceng:
Now there is no need to resize cache partition with the newer build.

cm-11 does not support ALL the new features in Android KitKat (at least not yet), including "transparent" status bar...

Many the PA GApps packages are either TOO BIG or INCOMPATIBLE with this rom. I've updated Installation instructions to mention that only BaNkS CORE GApps package is supported (BaNkS STANDARD package ok if you first remove some stuff from the ROM.zip).

Did you try FULL wipe but NOT full restock? Also try to install GApps AFTER rom install and reboots and ART conversion.
[Galaxy Tab  Android Development] ohtoulouz:
Yes I have,

I flashed 12A over AOKP SGT7 with all wipes wthout restocking to OC. As far as I remember, I played with the ROM for a while, then installed BanNKs GApps_Core (The search bar disappears after installing Gapps_Core, maybe it's normal). PlayStore shows up as it should and never disappears. Then I converted to ART and Playstore was still there.

Hope that helps,

[EDIT] I just saw in the OP that conversion to ART is advised before installing GApps: I am quite sure that I did it AFTER installing GApps_Core. Maybe this is related to the Playstore issue some of us are facing...

Pierre.
[Galaxy Tab  Android Development] Ukitaki:
Hi, i can try it this evening

(p.s. now it is 10 am at my place, so just wait for 12 hours till i will came back home :D )
[Galaxy Tab  Android Development] spike1985:
Analgo TV out (via 30-pin and "headphone-plug", dunno english name for that) is still not working. Just to mention. Vie "headphone" it shows nothing, sound not tested, and via 30-pin there is no sound an the screen just shows a colored line on bottom of remote screen. This is not changing/moving, no matter how much changes on the internal display. Anyway it does matter for the 30-pin, if the checkbox "TV out" is checked or not. The line is just there, if checked, otherwise "no signal". I hope I can help with this infos. I am not impatient, just wanne help.
[Galaxy Tab  Android Development] pinguinolandia:
last rom : i cannot use images like wallpaper, fc trebuchet. tethering not work.
[Galaxy Tab  Android Development] ohtoulouz:
My installation of v16

Installation of v16, comming from v12A:

- reboot recovery

- wipe data/cache/dalvik/system

- install ROM

- reboot system

-> sim unlock keyboard messed-up (as of 12A)

- play with ROM about 1/2 hour (change settings, advanced reboot, APN, ect...):

-> Trebuchet FC when changing background image (as of 12A)

-> Trebuchet settings not showing up in menu (as of 12A)

-> Nothing else to report

- reboot recovery

- install BaNKs GApps_Core (12-14)

- reboot system

-> Search Bar disappears (as of 12A)

-> PlayStore present (as of 12A)

- launch Playstore and sign in google account

- switch to ART. Takes approx. 14mn (7mn -> "Optimizing applications", then 7mn -> lock screen)

-> PlayStore still there

-> Trebuchet still FC when changing background image (as of dalvik mode)

-> Trebuchet settings still not showing up in menu (as of dalvik mode)

- install some apps, including another launcher (Xperia Launcher 2)

- home key -> choose Xperia launcher as default home

- remove Xperia lancher as default home

- home key -> choose Trebuchet (one time)

-> Trebuchet NO MORE FC when changing background image

-> Trebuchet settings SHOWING UP in menu

- home key -> go back to Xperia launcher as default home.

- Now enjoying the ROM ! Great Work terenceng !!!

Hope that helps,

Pierre
[Galaxy Tab  Android Development] RogerG:
Thanks very much to alroger and terenceg for the explanation. In hindsight it's really obvious they'd use the same path for caching.
[Galaxy Tab  Android Development] DarkPal:
Terence maybe I am still blind lol but where is the tablet ui option?
[Galaxy Tab  Android Development] terenceng:
Thanks for the feedback. I wish I had the relevant cables to test myself. Will look further into it to see what can be done.

Yes, attempts to set a wallpaper from Gallery FCs, though you can set one from CM Wallpapers, Live Wallpapers. Tethering doesn't work yet.

Your detailed feedback certainly helps, as have all your previous ones!. The historical "trace" allows us to visualize the steps leading to the specific events.... Thank you.

No you aren't blind.

To me, anything that tries to optimise the use of the tablet's (as opposed to a phone) screen estate (like multi-panes) is the start of TabletUI. I know you are thinking in terms of what most SGT7 people refer to as TabletUI, but that is not how I see it :)
[Galaxy Tab  Android Development] tat2me2:
OK, I need some help please, Flashed current build for P1000/L/N, device never did fully boot so I started over - TWRP v.2.6.3.0 - none of the tabs in twrp are lining up meaning I have to touch all over the screen to get one to work. Oh, and swipe to unlock won't work because everything is off calibration. Any advice for this issue would be greatly appreciated.
[Galaxy Tab  Android Development] p1000haha:
camera doesn't work in video mode, front camera the same
[Galaxy Tab  Android Development] terenceng:
OK it means the ROM still boot-loops on P1L/Ns. Revert back to a working ROM. First flash boot_p1ln.img using heimdall.

heimdall flash --KERNEL boot_p1ln.img

Then boot into recovery, and restore your backups, or flash your previous ROM.

You can extract the boot_p1ln.img from a suitable ROM, eg. here: http://download.cyanogenmod.org/get/jenkins/51566/cm-11-20131216-NIGHTLY-p1.zip, and flash it; let me know how it goes. BTW, during the boot up, does your tab (p1l or p1n?) seems to be booting but the CM logo keeps circling (i.e. does the system seems to be running but the CM animation never disappears?)

-------------

I have uploaded a

cm-11-CwM_boot_p1ln.img

for you.

Use: heimdall flash --KERNEL cm-11-CwM_boot_p1ln.img
[Galaxy Tab  Android Development] tat2me2:
managed to get the Restore process started, will report back shortly after flashing boot.img
[Galaxy Tab  Android Development] terenceng:
If you extract from the ROM.zip, ensure you flash boot_p1ln.img (NOT boot.img).

-------------

Hope that doesn't stop you from trying later builds on your P1L/N (but you have to learn/know how to recover from failure like this... anyway help is available).

BTW, I'm compiling a list of P1L/N willing testers, are you willing to be in it?
[Galaxy Tab  Android Development] spike1985:
Maybe I get something wrong but my Tethering (WIFI) is working just fine...

Or is BT tethering the "trouble maker"?
[Galaxy Tab  Android Development] tat2me2:
I was able to flash the cm kernel you posted, wiped cache, system, dalvik and data - then flashed the current build like before, but after 10 min. it's still on the opening screen with HumberOS in the bottom right corner. The touchscreen is responsive, because the capacitive buttons light up but nothing else.
[Galaxy Tab  Android Development] terenceng:
By "current build" you mean my latest cm-11 build? If yes, you can't flash that build anymore as obviously it doesn't work on your p1ln tab. You have to restore either your last backups or install another/your previous working ROM.

1. Go to download mode and flash the cm kernel again.

2. Boot to CwM recovery and do full wipe.

3. Continue to install another working ROM eg. the CM ROM (http://download.cyanogenmod.org/get/jenkins/51566/cm-11-20131216-NIGHTLY-p1.zip) you just extracted the boot_p1ln.img from: it is an official cm-11 build that works on your P1L/N.
[Galaxy Tab  Android Development] tat2me2:
Sorry, I misunderstood - I was able to restore but it puzzles me as to why this is not working. I've been in much worse situations with my tab. In fact, thought I bricked it a few times but was able to figure out how to get it back so I'm not what you would call a dev, but I'm no stranger to flashing - It's just been awhile since I've done anything with this particular tab. Anyway, if you don't mind, let me know when you think you might have something to try out on mine. (GT-P1000N)

Thanks for the help.
[Galaxy Tab  Android Development] terenceng:
Glad you have restored your tab with a working ROM. I'd love to have you on my list of testers. Thanks.

One P1N tester in. I need about 3 P1N and 3 P1L testers. Let me know or PM me and I'll send you the links of some P1L/N kernels/builds I will be buiding in the future for you to play and test with (but make sure you know how to recover from failure before you volunteer).
[Galaxy Tab  Android Development] jellybear456:
I successfully installed this on my sgt7 T-Mobile last night. My only problem is the play store is no where to be found..and when I download apks from the internet It won't allow me to install them. Anyone else experiencing this?

EDIT: I'm an idiot. I never flashed Gapps. Never mind!