yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab  Android Development] Mjoelnir77:
No problem with the google camera here. I restocked directly before installing the current build - maybe depending on installation history before this is needed here. I also had camera problems before (that`s why i restocked) and had FC`s on all camera apps when trying to take a picture.
[Galaxy Tab  Android Development] alfish2000:
How did you restock?

Here is how I did it:

1. - 5. http://xdaforums.com/showpost.php?p=51715825&postcount=358

6. wipe cache, wipe dalvik, format system, then flash rom (cm-11-20140410-UNOFFICIAL-p1.zip), flash gapps (4-11_GApps_Standard_4.4.2_signed.zip).

7. wipe cache, wipe dalvik, format system, then flash rom (cm-11-20140414-UNOFFICIAL-p1.zip), flash gapps (4-11_GApps_Standard_4.4.2_signed.zip).
[Galaxy Tab  Android Development] Mjoelnir77:
1) Flash Stocksafe_V5 (from Overcome) with Odin

2) Flash Overcome Kernel

3) Reboot to Recovery (i did not let Overcome Kernel boot to system/convert file system, that is not needed)

4) mount usb storage to put CM Rom on it

4) flash ROM

5) it will not flash fully but only kernel and then reboot to recovery (that is normal)

6) use the new recovery to do the usual installation that is

a) wipe /system, /data (probably both are unneded here when coming from stock), /cache

b) wipe dalvik (in advanced settings)

c) flash ROM, gapps (from banks)

d) reboot

Actually the process is very similar to all the other restock guides using Overcome guides. I just left out unneded steps.
[Galaxy Tab  Android Development] ulev:
Why not simply flash a CM ROM with Odin instead? Same result, much faster...
[Galaxy Tab  Android Development] mike2nl:
Hi storm,

first: Thak You

second: Thank You

the version from 2014-04-14 works like a charm right now for two days.

Looks very nice, fast and stable for me. Hope we will see more from you ;)

[MENTION=535343]all[/MENTION]: one question about the app drawer -

- where i can set the columns and row numbers?

- in the version from december i had a setting for that but i can't find it right now (possible blind ;))
[Galaxy Tab  Android Development] alfish2000:
Thanks.

I'll try that soon.

Meanwhile I got "Panorama" and "save to sd card" working by accident :)

I did the following on top of what I described here: http://xdaforums.com/showpost.php?p=52122451&postcount=387

1. wipe cache

2. wipe dalvik

3. format /system

4. flash cm-11-20140414-UNOFFICIAL-p1.zip

5. flash 4-16_GApps_Minimal_4.4.2_signed.zip

6. flash 4-17_GoogleHome_4.4.2_signed.zip

7. flash 4-16_AOSP_Calendar_Sync_4.4.2_signed.zip

8. flash 4-16_AOSP_Browser_Sync_4.4.2_signed.zip

Now I had 2 Camera apps in the drawer.

The Google Camera from play store and the camera from the ROM.

The Google Camera still is FC when selecting some menu or switching to video or so.

So I uninstalled the Google Camera.

But the ROMs camera now has more options.

And even I have the option to save to SD card now. Didn't have that menu at all before. See: http://xdaforums.com/showpost.php?p=51715825&postcount=358

And the Panorama is working now, which did not work before. See http://xdaforums.com/showpost.php?p=51696143&postcount=353

---------- Post added at 09:35 AM ---------- Previous post was at 09:20 AM ----------

How to flash cm-11-20140414-UNOFFICIAL-p1.zip and the gapps zips with odin?

Or do you mean to flash any other CM_ROM.tar with odin and then flash cm-11-20140414-UNOFFICIAL-p1.zip and gapps.zips with CWM?

Doesn't have the restock process some benefits (e.g. original/official start condition or something like that)?
[Galaxy Tab  Android Development] ulev:
Sorry, I was not precise enough... You use Odin only to flash a later CwM or TWPR kernel. It can be extracted from a CM ROM with fully functional recovery and converted by using a little tool called "CreatTarForKernel". I produced the kernels once and keep them handy in my Odin Folder for emergencies like a soft brlck. After flashing the kernel you can get back into recovery on the phone and install any ROM you like.

Using this quick approach the switching back to the old filesystem and partition structure doesn't occur. You can still wipe everything during the process, so I don't see any advantage of a full Restock. Since I discovered this process I never had the need to go back to Overcome. It is discussed in detail somewhere in the forums around here. I am too lazy to search...
[Galaxy Tab  Android Development] tivgnos:
ROM build date 2014-04-10 can't TILT, I found this bug on the game "TEMPLE RUN 2".
[Galaxy Tab  Android Development] ece_netsailor:
TWRP

Dear storm31,

i would like first to thank you for all your hard work, and i would like to ask how can i install TWRP recovery cause i think it has more features than CWM. i have tried to replace the boot.img by that in terenceng ROM and flash, but that didn't went well so i would like to know if there is a way to have your great rom with TWRP recovery
[Galaxy Tab  Android Development] alfish2000:
Tried your steps.

But same result.

The Google Camera from Play Store is FC often as before.
[Galaxy Tab  Android Development] ulev:
I think the latest ROM has a memory management issue. After a few days I just returned to 04.05. The best so far.

Several times a day I experienced a full freeze of the tab. Most of the time could only be fixed with a hard reboot.

I found a strange unmounted zram partition, so it seems that this kernel is very different to former ones. Returning to the old backup.

Back to 04.05. and happy (again)
[Galaxy Tab  Android Development] chickoo.t90:
The freeze issue is experienced by me too ...I can confirm ... I hard reboot once a day ...waiting for a newer version :D

Sent from my GT-P1000
[Galaxy Tab  Android Development] mike2nl:
Mhh, strange...

i dont had have any reboot from the day of installation of the 15th april.

Stable ROM and fast so as all the time.

Mhh, possible a complete new clean intallation from up the beginning can solve issues sometimes...
[Galaxy Tab  Android Development] chickoo.t90:
Yeah I thought so ...will Be doing just that right now :p will get back with results

Sent from my GT-P1000
[Galaxy Tab  Android Development] ulev:
Not in this case. The issue is connected to intense use of RAM which is only 481MB on our old lady. Normal light use might not bring it up ever. It might also be connected to the use of Xposed framework and Greenify but the core of the problem is in the ROM's memory management somewhere I am sure. I am back to the 04.05. version and everything is just fine.
[Galaxy Tab  Android Development] jmpub:
new rom cm-11-20140427-UNOFFICIAL-p1.zip

thanks
[Galaxy Tab  Android Development] storm31:
i had this patch inside already - brcm_patch for p1 cause this problem on galaxy s, i have enabled it in last rom again. Please report after trying about your problem.

1) no, this kernel doesn't support usb host: may be later...

2) the default cam has photosphere - probably you need a data wipe..

hm.. i doesn't use the phone function anymore, but i try to fix this problem.

This is a newer trebuchet version and it hasn't this settings. You can install the older trebuchet (extract it from older build)

1) I must change some device repositories for TWRP

2) we can't use older CwM backups after this

3) i haven't much time (family, work and so one..)

4) may be i can combine both recoveries (if i get more time:))?

Yes, i try some changes from omni device repositories and it can be possible that we get problems with this changes. But i haven't problems with 04-15 rom. Some user apps can cause problems like yours also... May be you can collect some logs (i don't know if it helps after one reboot, probably no). Last rom should have one working swap.

New clean installation can help sometimes.

To problem with Google cam app:

I don't know if i can fix the problem with the new google cam app from PLAY, but if i have more time, i try to fix it

Newer rom - cm-20120427, swap should work now, cm/sgt7 commits, low ram is disabled now...
[Galaxy Tab  Android Development] leleobhz:
Storm,

I can help you with debuging if you need something i can run in my tablet.

Also, i use this app in my Razr D3 to record calls and it works well, but on P1000N (All versions since 12/2k13, when i started using you version). Some suggestion or fix for it (Or other app that works?)
[Galaxy Tab  Android Development] storm31:
The problem is that i don't know what i must change for a better call volume. I must look in humberos/cdesai's repos and search for commits, they can change this (probably kernel or device repos). If i find and change something then you can test it. I try the mentioned app also.
[Galaxy Tab  Android Development] storm31:
Yes, i had problems with a racing game also.
[Galaxy Tab  Android Development] leleobhz:
n00b question: Voodoo Patch cannot help to fix it? Even using earphones?
[Galaxy Tab  Android Development] RogerG:
thanks for confirmation regarding no usb host - I thought I must have gone mad.

regarding photosphere: data wipe did not help. then again, the cam has updated itself (to 2.1.037) since my original comment - now it FCs whenever I switch from standard photo mode to film mode and both spheres and standard panoramas are now gone completely. not that big of a deal, especially since your roms are so great in all other aspects - just fyi :)
[Galaxy Tab  Android Development] alfish2000:
Cameras are really strange for me too.

Nearly each time I restock or update the ROM they are different.

I never saw Photosphere with the stock camera.

I've updated from 4-14 to 4-27 right now and this is what I have now:

I have both cameras in parallel and for the first time I saw Panorama, Photosphere, Focuseffect in the left side menu of the Google Camera.

The Google camera also crashes when selecting video.

Photosphere, Panorama and Focuseffect seem to work.

For me the camera is also not so important but I'm really curious why these both cameras behave so strange and always a little different.

Anyway thanks for the ROM and I will test each new release for sure.
[Galaxy Tab  Android Development] jkl555:
I don't quite remember since which build I have this problem. I haven an iPhone 5 which is used as hot spot. I can only connect my P1 to iPhone 5 using wifi. If I use bluetooth, P1 can connect to the iPhone 5 but there is no internet connection. It used to work on me (I can't quite remember whether it works on KitKat or previous android OS). I am wondering if there is something obvious that I miss in the settings ? Anyone has similar issue ?
[Galaxy Tab  Android Development] mike2nl:
[MENTION=236992]Storm[/MENTION]:

-> This is a newer trebuchet version and it hasn't this settings. You can install the older trebuchet (extract it from older build)

Thanks for the hint. Will check it uit....
[Galaxy Tab  Android Development] ulev:
I am using the latest ROM for 2 days now. Memory management is working well now and brings an amazing push to performance. The reintroduced zram swap partition is mounted and obviously active now.

Temple Run works better than ever before.

That's the good part...

On the downside I still get complete memory freezes several times a day under heavy use. However, with this ROM they usually sort themselves out within a minute or so.

I also have minor problems with Xposed modules like Gravity Box which are not present in the 2014-04-05 version. I know I could try to rebuild everything from scratch instead of just wiping Dalvik but with the highly complex system I have created mainly for privacy protection I am not really looking forward of going through several hours of installation time just to end up with the same result...

What I am missing now is the old ZRAM settings to switch it on or off to see any possible effects.

Suggestions?
[Galaxy Tab  Android Development] storm31:
Tilt sensor does work in last two roms.

ZRAM settings were removed from CM Team. We use now the AOSP way for ZRAM..

Newer ROM 20140502: some minor updates for kernel, FC's with russian language are fixed, low ram mode is enabled again, newer cm commits...
[Galaxy Tab  Android Development] ulev:
Great. :good::good::good: I was waiting for that as ZRAM always was a booster.

I have temporarily uninstalled Xposed. I have a feeling this is what could cause the freeze issues after the 2014-04-05 version.

Downloading right now...
[Galaxy Tab  Android Development] metterschling:
Right, but I'm having intermittent sensor failures as well, the last one right now with 4/27 ROM. Note that not only tilt sensor is affected, but all other sensors like accel too. Re-booting always resolves the issue for me, but it is nasty. I'll pull a logcat and see if I find some relevant information therein.
[Galaxy Tab  Android Development] alfish2000:
Installed 20140502 right now.

Photosphere, Panorama and Focuseffect from Google camera is gone again.

I had that options visible and working with the previous ROM (4-27)

See here: http://xdaforums.com/showpost.php?p=52280644&postcount=408

So the Google Camera mystery continues :)

Apart from that everything seems to be fine so far (after 30 mins of testing)

Thanks for this new version.
[Galaxy Tab  Android Development] metterschling:
Same experience here, even clearing app data & re-clearing cache/dalvik does not help...
[Galaxy Tab  Android Development] ulev:
Tried to install 20140502 several times yesterday. I even wiped all partitions clean.

Observations: during boot the rotating animation went into a constant freeze, always at the same point after only one rotation. After waiting for some time the app optimization process comes up as normal, everything looks ok until the lock screen comes up.

From there, however, I get fast repetitive looping crashes of the android.systemui process. It is looping with the status bar flashing in between. Coming so fast, I cannot even power down in between 2 crashes. I had status bar configuration problems using Gravity Box with the last 2 versions already. But in this case Gravity Box (and Xposed framework) were not even installed.

A little different on fully clean installs: (1) no looping crashes until I restored the data partition from backup (2) no looping crashes until I recover Android Id from Titanium Backup, the first and only App I installed. :confused:

I tested the ROM with Winrar, everything seemed ok there.

At last I returned to the backup of my favorite 20140405. Everything back to normal. Guess I take a break from upgrading for a while...

Big thanks to storm31 anyway for all the efforts. I really love the attempt of bringing ZRAM back :good: but I need Xprivacy/Xposed to run reliably and stable even more and that is what I get with 0405...
[Galaxy Tab  Android Development] metterschling:
[MENTION=3985122]ulev[/MENTION] 20140505 with xposed&xprivacy running stable here, came from 20140427, wiped Cache, Dalvik & System partition, installed latest banks gapps, then got a smooth upgrade. Did you update xposed to the latest version (2.5.1)? This latest Version resolved a compatibility issue with recent CM11 builds...
[Galaxy Tab  Android Development] ulev:
Good to know you have my "ideal config" working. In case I want to try again... :good:

Did everything as you say with the small exception that I was using banks GAPPs 3-22, which is one before the very last. The looping crashes of the systemui process start right after the first boot, never even got to installing/activating Xposed. Could try again with GAPPS 4-16 which I downloaded today I guess. The other options I have are redownloading the ROM or really restock and start over... The latter would actually take my partition sizing back to standard as a side effect.

A very time consuming troubleshooting path as I am almost entirely happy with my 20140405 installation. Will see, maybe later this week.
[Galaxy Tab  Android Development] alfish2000:
Same for me.

I was curious and used the Xprivacy installer (from Play Store) on top of the 20140502 ROM and everything is fine so far.

No crashes.

Used GApps:

4-16_GApps_Minimal_4.4.2_signed

5-2_GoogleHome_4.4.2_signed

4-16_AOSP_Calendar_Sync_4.4.2_signed

4-16_AOSP_Browser_Sync_4.4.2_signed
[Galaxy Tab  Android Development] ulev:
Seems I figured out where the bug is :)

Disabling the wallpaper service in settings/performance is the cause for the systemui crashing. This is something I do by default for a long time right after the first boot.

Regarding Xposed Moduls: Gravity Box adjustments to the Status Bar are not working anymore for me in the last 3 ROM versions.
[Galaxy Tab  Android Development] alfish2000:
I was curious about gravity box and found that:

http://repo.xposed.info/module/com.ceco.kitkat.gravitybox

...

Compatibility

...

- SHOULD NOT be used with custom ROMs like CM, AOSPA, RootBox, SlimBean and others - it makes no sense since the most of the features are already

in the ROM (may cause conflicts and unexpected behaviour)

...

So it seems that gravity box should not be used with CM roms.

Just found that and wanted to share it.

I've never used gravity box by myself.
[Galaxy Tab  Android Development] ulev:
I am fully aware of that statement. The adjustments I used worked perfectly well on this ROM up to 2014-04-05 (and still do). What changed was the ROM, not Gravity Box. It's all about the current systemui.apk I think.

Addition: After I finally succeeded with a green field install of the 2014.05.02 ROM and everything is running well again I gave Gravity Box another try. And guess what... all my favorite adjustments are working. :)

I will miss this old lady, but I am about to move on to an Xperia Z probably as early as next week.
[Galaxy Tab  Android Development] mike2nl:
@storm31:

Thanks again for the next update to 02/05. Very smooth and fast running.

I've installed minimal gapps and all needed backpups installed.

But first i have made a complete restock and then step by step because

my sim card issue. And now that is gone and it works perfect.

Hope Trebuchet will grow more to have all nice features back ;)...

BTW:

i've tested my old mod's for 3D Photo Browser (old ACER). And it works

after i have made some zip's to test the installation. It depence on some lib's

and i have found the right one (4 libraries). Will post the link to the CM11

running apk here when i've updated my old thread about the app. That will

be a gift and something back to all CM11 users

So 3DPhoto Browser is running on CM11 :D.

But i think i need help for some ideas to have it colored in the right way. Here

the link to my old thread: link
[Galaxy Tab  Android Development] metterschling:
Just found the cause for the disappearing camera effects. Unlike the 4/27 ROM, the 5/02 build has the low_ram build.prop setting enabled again. This causes the new Google Camera to hide all of the above mentioned extra features.

Use CM file manager along with the built-in editor to set ro.config.low_ram=false in /system/build.prop (re-mount /system to r/w before, click the lock icon in CM file manager to do that), then re-boot and enjoy the effects!

[MENTION=3380725]storm31[/MENTION] any severe cause to revert the low_ram setting in the latest build? Any issues other than a slight slow-down that was reported before (I'm not sure if this is the case here...)

BTW: disabling low_ram also brings back the transparent status bar.
[Galaxy Tab  Android Development] w.sukiyaki:
hi...

need ur opinion... (u succesful rom overcome to cm 11) how?

before my p1 run cm11 but after last flashing (dunno what wrong) stuck on samsung logo..

using GB stock save n now overcome then flash to cm10 using cwm...

problem now when to flash cm11 reboot stuck at samsung logo...

*should i flash cm11. kernel mod
[Galaxy Tab  Android Development] alfish2000:
Here I wrote how I did it:

http://xdaforums.com/showthread.php?p=51715825

Maybe you are missing some wipe during the process.

First boot of cm11 sometimes takes some minutes.

Maybe you have to wait a little longer till the boot logo disappears.

Don't know what you mean with cm11 kernel mod.
[Galaxy Tab  Android Development] Ichijoe:
Does this build also suffer from the dreaded squished up Pin Pad?

I've seen newer stuff reporting that it had been, will have been fixed in a newer release, and yet its still squished on my p1000. :(

Also those Bulids of Kitkat that I tried did have working Cameras... But would crash the instant I'd switch to Video Mode. Front, Back?!

It made no difference at all. Does that (Video recording) work in this latest build too?

thx
[Galaxy Tab  Android Development] metterschling:
The Pin Pad issue was fixed some releases of storm31's builds ago and is still fixed in the 5/2 one. Search this thread to find the exact build where this change happened.

All camera functions except front camera Video recording are working with the stock CM camera, only if you use the new Google camera (2.1.043), switching to Video mode always causes a FC.

See my post above how to get the advanced features of the new camera working with the 5/2 ROM.
[Galaxy Tab  Android Development] alfish2000:
Exactly what I see on my Tab.

I was about to answer the same :)
[Galaxy Tab  Android Development] Ichijoe:
Ok so by 5/2 can I defer that you mean the May 2end Build? If so that may explain the problem, as I installed the most recent CM-Build at the time I posted the Original Question. which was from the Nightly CM11 Build(s) from the 201405- 11 & 12, And they [i.e. The Sim Unlock Pin Pad] were still squished on those builds.

I'll give the 20140502 build a shot and report back, in a bit.

P.s. I forgot to ask in my first Post, but does HD Video, (or just Video) work in the current Builds of CM11 on the P1000 GSM? Note I could care less about the C/L/N etc... etc...
[Galaxy Tab  Android Development] storm31:
this build and cm nightlies are different, i think sim unlock pad on nightlies isn't fixed. Hd video does work on this build
[Galaxy Tab  Android Development] Ichijoe:
Seems that way... 'cause everything seems to be working sans, being able to film selfies. Which doesn't bother me much TBH.

I think this can well be my new daily driver. I just need to figure out how to set up ART-Mode on this, and figure out if its work the bother.

The only thing that seems to bother me is that the Screens' a bit dimmer (outside), compared to CM10, Which was what I was using before. What I don't know is if some App is hijacking my Brightness in order to try and save Battery Life. (Greenify I'm looking at you!), But if I'm honest I ran that in CM10, and never had a problem cranking up the brightness well outside before now either.

My old man has the exact same Tab as I do, and hes still on CM10 so I'll definitely report back on this ASAP.

I'm also less enthused with having to dig though a million Menus to find the One that disables the "Safe Volume Level Cap". I couldn't quite figure that out till I found a shady area to squint at it.

Other then this. I have to say I'm truly impressed with this ROM so far.

I still have to see if I can stream At Bat Video Feeds (such as are gratis on any given day.), cause those weren't working so well under CM10. Most likely I'll shell out for MX Player sooner or latter, to fix that hopefully...
[Galaxy Tab  Android Development] storm31:
newer rom - cm-11.0-20140512-unofficial, call volume fixes from humberos kernel, new theme engine/app, low ram mode disabled again, newer cm commits...
[Galaxy Tab  Android Development] Ichijoe:
Ahhh I just needed to move some Data over, cause I'm to derp with how the GT-P3110 (Galaxy Tab 2 7.0) works with its MTP & PTP Settings. I only up till now had to deal with USB Mass Storage (GT-I9000 & GT-P1000).

In any case what I need to know is how the heck I can safely unmount my MicroSDHC Card from my Tablet(s). The P3110 seems to have that Option, but its greyed out, on it. The P1000 doesn't even give me that option.