yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
You're kidding right?

Install 200 Apps and let some stuff run in background (Skype, ADM, Bittorrent, etc.)

It is definitely faster... Greenify and other apps which free RAM might be good, but that doesn't change the fact, that with KSM disabled those "idle-times" are nearly gone, even without apps like Greenify...

IT IS NOT GETTING MUCH MORE FLUID, BUT THOSE IDLE-TIMES WHERE THE TAB STALLS FOR UP TO 30 SECONDS (for example due to a crash of a background-app, so not only if you are running many background-apps) ARE NEARLY GONE! You also recognize it when you type on keyboard... Sometimes I have short idle-times, for example if I type (in Chrome or whatever), while it installs an app. Gone... It's definitely better and not a Placebo. :p

Sorry for writing some sentences in "all-caps"... Shouldn't meant to be shouting, but rather that you see (in my text-block :D) what really improves.

IT DOES RUN BETTER ON ALL PREVIOUS JB-ROMs!

IT DEFINITELY IS BECAUSE OF THE ROM, REGARDLESS OF HOW BAD THE APP MIGHT BE!

Well, technically it isn't as bad... But it is simply a ported app (one more abstraction while runtime) and I think the emulation-core isn't JNI, whereas it is in drastic's case...

So, what should KSM be for if it needs an external app to not cause bad performance on specific setups?

Shouldn't it be the opposite? I even had it cause idle-times on my HTC One X, when I didn't had many apps installed...

That is not the dialer-app, is it?

Maybe you don't have the 3G-Version of the Tab, where you can do normal "phone-calls" like you do with a normal phone... :p
[Galaxy Tab 10.1 Android Development] kashortiexda:
I am running the P4 3G version and phone calls on the stock standard AOSP dialler work just fine, the mic works great... I just received a call (nice minimalistic popup btw)

however.... On Google Now the app gets stuck at initialising

sent from my P4 OmniRom 4.4.2
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Thank you for confirming it! :good:
[Galaxy Tab 10.1 Android Development] kashortiexda:
[MENTION=5626369]TnA.Plastic[/MENTION] is your network speed monitor working?

Also just tried wifi tethering, doesn't seem to be working either.... how 'bout you?

sent from my P4 OmniRom 4.4.2
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Hm,... Is it the third option in Settings?

"Datenverbrauch" in German translation?

Yes, indeed it does show the graph and how many Byte/KB/MB each app used.

Didn' t tried any tethering yet.

Have you wiped "data"; "system"; "cache" and "dalvik cache", before installing Omni 4.4?
[Galaxy Tab 10.1 Android Development] kashortiexda:
under Settings, Bars, Network speed indicator

sent from my P4 OmniRom 4.4.2
[Galaxy Tab 10.1 Android Development] kasper_h:
This doesn't work on tablets yet....
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Ah,... Nope, only shows "0B/s".

Edit: kasper_h was faster
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Regarding the PIN-PAD-Issue: It shows correctly, once I hit enter and the SIM-PIN is verified and just before it shows the Unlock-Screen, but it doesn't while it is simply shown.
[Galaxy Tab 10.1 Android Development] alexkno:
Great Rom!!! Just testing now for some hours. Currently I only miss the cm browser. Is there any possibility to install it including the favorites sync?
[Galaxy Tab 10.1 Android Development] mcmb03:
This has been said again and again, but Omni has nothing in common with cm so it is more than likely no. It might work manually pushing it but if you like the cm features more you should be on a cm rom. There are many alternatives to sync browser favorites you can also try out :)
[Galaxy Tab 10.1 Android Development] alexkno:
Thanks for the answer but in fact I like pure aosp much more than cm, and I always thought cm browser was in fact aosp...and I suspect omni is aosp based too, that's why expected the aosp browser to be there. But ok, will look for an alternative syncing with the aosp browser I use on my other devices

Edit:Will try whether this helps: https://play.google.com/store/apps/details?id=de.mkrtchyan.aospinstaller
[Galaxy Tab 10.1 Android Development] eushaun99:
Actually, this is the first time its been mentioned about the AOSP browser. It is, in fact under AOSP and not under CM.

Can't tell you clearly since I've went back to omni 4.3, but I think the browser was there wasn't it? Can somebody on this ROM confirm? The browser is here in omni 4.3.
[Galaxy Tab 10.1 Android Development] alexkno:
Maybe it has problems with art? As this is the only major thing I changed yet. Will check the zip whether it's in or not.

Edit: it is in. Don't know why it wasn't installed. Just extracted it from the zip and fine now, thanks!
[Galaxy Tab 10.1 Android Development] AAccount:
You can push the CM browser apk from any cm11 rom to /system/app if you want it. I still make my own omni kitkat builds and mine makes the CM browser straight from their sources. I push the apk to my I9300 every time I make a rom so you can do it. You can also push the cm calculator.

Also, OMNI has given us a new year's treat with a hidden bonus. Just tried it myself.
[Galaxy Tab 10.1 Android Development] kasper_h:
Nice :)

I will add CM Browser from the next update, and CM Calculator is already part of the build posted here.
[Galaxy Tab 10.1 Android Development] Krusade:
Please Delete
[Galaxy Tab 10.1 Android Development] eushaun99:
But isn't the browser already there? In the ROM zip I see Browser.apk in /system/app.
[Galaxy Tab 10.1 Android Development] kasper_h:
Yeah, but cm version is more extensive.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] crippleye:
Cm browser showed the best results, i ve tested almost all the browsers, each one had bad issues

It would be good to post suitable gapps pack too.. for noobs like me:)
[Galaxy Tab 10.1 Android Development] mrbubba999:
Is there a way to get video streaming to work? Trying to use twitch and I get sound but no video, YouTube works fine though
[Galaxy Tab 10.1 Android Development] AAccount:
Youtube HD fix should be coming along with the camera, video recording and microphone. The camera was fixed by the omni team. It's the commit I mentioned a little while back. For reasons I will never understand, a fixed camera also fixes the GPU video playback. With no microphone, the camera will take pictures but not record video. I tried it yesterday and it hangs when you stop video recording.

Today, I gave the ICS blobs another go and after many hours they're working. The microphone is alive again. I did a quick 3 second 720p video tour of my room before.
[Galaxy Tab 10.1 Android Development] rogconnect:
So I guess Netflix is fixed too!
[Galaxy Tab 10.1 Android Development] kasper_h:
Hopefully it is!

I am now implementing the audio fixes of AAccount, which seem to be really great! I will then clean out my whole repo and do a clean build (will take about 4 hours). Hopefully, this will result in a fully functional build soon :)
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Cool! :)

Are you sure it is not the other way around?

I would rather expect the camera to be dependent on the GPU-Stuff...

...and it all works correctly?

Camera/Video with sound and also fluid?

Hope this fixes the horrible sound I've got in nds4droid.

Can't wait for the New Years Eve - build/"Gift". :)

Edit:

So to sum up the changes:

-Camera works now (Skype-Video, Camera/Video and other Apps which make use of the camera are working)

-Hardware-acceleration is working (thus YouTube HD, Netflix, etc. is working and overall performance should be at least a bit better [even thought it is quite good already without)

-Microphone is working (finally all microphone-based apps are working, not only the dialer and maybe very few other apps)

-Sound is working better (hopefully fixes what occurred to me in nds4droid)

-Android 4.4/KitKat's new screen-recording-feature and the good old "screen-(picture-)capture works.

-CM-Browser will be added

-Something else?

Bugs remaining:

-PIN-PAD-Issue (Numbers are shown "cut-off")

-Some little bugs here and there, like Connection - Speed and indicators not yet working on Omni-ROM for Tablets

-On-top-holding-issue (bottom-bar is not showing)

-etc.

Now, let's get (back) on bug-hunt. :)
[Galaxy Tab 10.1 Android Development] eushaun99:
It is now exactly 12.11 am in my area and I just wanna wish kasper_h, AAcount, all the devs in the gtab 10.1 forum, and all members here a HAPPY NEW YEAR!! Special thanks to AAcount and kasper_h for working so hard in bringing KitKat 4.4 to our tabs. :) :)
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Still 6 and half an hour "to go" in my area... :D
[Galaxy Tab 10.1 Android Development] kasper_h:
I have no issues with pin pad? How about others?

Other issues are generic omni issues. Will look into that, but no easy solutions.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
I'd be pleased with a build which includes the mic-, cam- & hardware-support. :D

I can do a full-wipe, if formatting "only" data+system+cache+Dalvik cache isn't enough.

Btw.: Did I get all changes right?
[Galaxy Tab 10.1 Android Development] kasper_h:
Still compiling. First going to a party before uploading the new build. Hopefully, it solves all issues you mentioned. A full wipe will probably not be required

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Even the "On-top-holding-issue" fixed? O.o

I guess the Omni-Stuff/Features which where non-functional still don't work, right?

Going off for a party in 2 hours and need to "prepare". ^^

Hardware-acceleration (at least partial support) would be a good start into the new year. Anxiously waiting for it! :fingers-crossed:

Edit: Is A1-Kernel compatible to this ROM and does it perform better, or is it pretty much the same?
[Galaxy Tab 10.1 Android Development] AAccount:
One thing to note is that kasper_h and I discussed whether to ever enable screenshots or not. On the omni gerrit, it appears as if someone managed to port the old screenshot method. That person has also tested the solution on his own devices and it works on there. I have no idea who this person is.

Now the problem with screenshots is that it makes the new 2 bar UI laggy. The cause for this is beyond me but I figured this out, out of dumb luck. I would have to guess it's a problem with nvidia's graphics driver. Since kasper_h and I rarely ever use the screenshots, we agreed to permanently disable screenshots even if the fix gets merged. We think a buttery smooth UI is worth giving up screenshots and probably screen recording.

This lag is the reason I had tabletUI on my CM10.2 rom. However, tabletUI has multi user issues and will not feature customizable quick tiles.

Just a heads up.
[Galaxy Tab 10.1 Android Development] rogconnect:
Screen shot and screen recording are not necessary on our tab.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Yepp, I agree on that.

I just hope it can be re-enabled, if it doesn't cause any more slowdowns...

Btw.: What about your A1-Kernel. Does it work with this ROM and if it does, is it in any way better than the Kernel shipped with the ROM? I used it before and really liked it.
[Galaxy Tab 10.1 Android Development] AAccount:
Yeah my kernel does work with this rom. (Check my signature :p ) Custom kernels are more about personal preference since all of them likely have the same major enhancements but have a few different extras here and there depending on what the creator thought was important. Just check out kasper_h's custom kernel thread and mine and see what fits your taste.

Obviously since I am the creator of my custom kernel, it fits my taste exactly :p
[Galaxy Tab 10.1 Android Development] John Kester:
-1 here. Screenshot is essential to me. It all depends on what you do with the device and the nature of your work.

Cheers.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Well, I don't like slowdowns, but I still want the accu to last long.

I'd really like to use the 785MB RAM and so on...
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Same here my friend
[Galaxy Tab 10.1 Android Development] rogconnect:
Blame Nvidia for not giving you the support for screenshots. Never buy another Tegra chip tablet no more.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
But the Tegra's graphics are so good I can't resist buying them
[Galaxy Tab 10.1 Android Development] TabGuy:
There are apps to enable screen shots.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Screenshot is currently disabled and even if you install an app to take screenshots, it will say storage is in use
[Galaxy Tab 10.1 Android Development] kasper_h:
Exactly.

As AAccount said, enabling screenshots will slowdown the tab noticeably, so therefore we will not activate it. If you REALLY rely on screenshot, you may need to choose another ROM....or compile yourself.
[Galaxy Tab 10.1 Android Development] kasper_h:
There is a new build. PLEASE READ THE POST BEFORE INSTALLING.

-There are instructions below to activate camera

-ActiveDisplay has been replaced by Lockscreen notification. This is still WIP. Completely disabling this will cause systemui crashes. If you are not willing to test, wait a few days for a next build.

Changelog of 01-Jan-2014

p75x0 specific:

-Fixes to camera

-Fixes to audio

-> camera and all should function now. However, camera is still disabled (unless you do a factory reset). To enable camera without a factory reset, please use this:

pm enable com.android.camera2/com.android.camera.CameraLauncher

(can be done through adb or terminal emulator)

General Omni:

-Omni codebase of 31-Dec

-Updated QS toggle modification patch (based on AOSPA -> press the new edit button above the toggles to modify the QS toggle screen -> press to remove/add / hold to move around)

-Removed ActiveDisplay (even with all the improvements, it remained buggy)

-Added lockscreen notification (replacement for Active Display - not yet perfect, so do not post bugs - can be tuned in Settings>Security>Lockscreen Notifications)

-Ported privacy guard from CM (can be found in Security menu)

-More keyboard tuning (see Settings>Input>Advanced)

-Ported Quiet Hours from CM

Downloads:

P4WIFI:

http://rootaxbox.no-ip.org/kasper_h/roms/p4wifi/omni44/

http://www.xdafileserver.nl/index.php?dir=Samsung/Galaxy+S/MackayROM/p4wifi/omni44

P4:

http://rootaxbox.no-ip.org/kasper_h/roms/p4/omni44/

http://www.xdafileserver.nl/index.php?dir=Samsung/Galaxy+S/MackayROM/p4/omni44
[Galaxy Tab 10.1 Android Development] rogconnect:
Downloading now, thanks !
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Kasper and Aaccount i love you guys !!

EVERYTHING works! :) thanks!
[Galaxy Tab 10.1 Android Development] kashortiexda:
thanks kasper_h... did you manage to get mic fixed it Google Now initialise?
[Galaxy Tab 10.1 Android Development] paiktaras:
i have the 4.3 omni version to my tab. To do upgrade to 4.4 should flash and gapps for 4.4 or not ?
[Galaxy Tab 10.1 Android Development] AAccount:
Yes you should flash new gapps.

Just a note to everyone else. The command kasper_h posted to enable the camera

must be run as ROOT

.
[Galaxy Tab 10.1 Android Development] paiktaras:
this gapps is ok ?

http://goo.im/devs/paranoidandroid/roms/gapps/pa_gapps-stock-4.4.2-20131230-signed.zip

the mod for the phone calls that I have by ics which functioned and with 4.3 works normally now?
[Galaxy Tab 10.1 Android Development] rogconnect:
Terminal emulator.....

Should type : su

Enter and then type the command.
[Galaxy Tab 10.1 Android Development] fleckdalm:
Thank you very much for keeping our old tab alive!! I really appreciate your great work, is there a way to donate to you? ;)
[Galaxy Tab 10.1 Android Development] kivimart:
How about netflix?
[Galaxy Tab 10.1 Android Development] rogconnect:
YouTube HD and live streaming working fine... So Netflix should be working. Sorry I dropped Netflix subscription so cannot confirm it.
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
I first flashed the 12012014 ROM over 27december one, camera worked perfect, HD video's work, microphone works brilliant, but then i did something weird with those quicktiles, i clicked on the torch i think which was not working, then, on no mather what app i opened, if i scrolled down in an app (like settings, file manager,etc) the app crashed, so i did a factory reset and now everything works like it should :) thanks!
[Galaxy Tab 10.1 Android Development] jmy006:
For my, all is functional :laugh:

Really very good work!

And I too would be almost has to make a donation :good:
[Galaxy Tab 10.1 Android Development] paiktaras:
can someone answer my questions in post No. 242 ?
[Galaxy Tab 10.1 Android Development] kasper_h:
These gapps should be fine. I would not flash mods designed for 4.3, unless you have a nandroid backup so you get easily get back...
[Galaxy Tab 10.1 Android Development] TabGuy:
I can report that Netflix crashes immediately upon trying to load. Bummer. Back to CM. Sigh.
[Galaxy Tab 10.1 Android Development] fleckdalm:
Really great rom! The only issue i have so far is that there is a really strange animation when i rotate für Device. Is that a known issue?

Is there an option to enable battery percentage in notification bar?

Thanks

Fleckdalm
[Galaxy Tab 10.1 Android Development] DefQoN_BE:
Settings > battery/accu> battery indicator
[Galaxy Tab 10.1 Android Development] Dreameagl:
Which of those gaps versions are you using. I downloaded the latest one and it doesn't install. I downloaded it twice, but no dice.
[Galaxy Tab 10.1 Android Development] AAccount:
Status 7 metadata error?

Sent from my GT-P7510
[Galaxy Tab 10.1 Android Development] Dreameagl:
Status 0

Same as when I downloaded the version from Sept. 19..

Update:

I downloaded a few more, and only the oldest gapps in the list worked.
[Galaxy Tab 10.1 Android Development] damngood98:
Can anyone else confirm? And have you tried perhaps using another kernel?
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Did anyone got the error of the dialer-app crashing on startup?

-wiped system, cache, dalvik cache, data.

-installed Rom+gapps.

-wiped dalvik cache and cache again (just to be sure)

-rebooted

Everything else works very good!

If the dialer-problem is some kind of error on my side, I'd say this ROM finally feels ready for daily use (fluidity, responsiveness, efficieny), but it still has some bugs.

PIN-PAD still looks “squashed" when I enter the PIN, but as soon as I press enter and the SIM got "unlocked", the PIN-PAD “stretches“ and the Numbers are shown normally before the PIN-PAD vanishes and my normal lock-screen is started

Hold the Tab on top and the bottom-bar still vanishes completely.This also seems to cause the heavy flickering, if you activate screen-record in the settings for the power-button-menu (yes, I know what you said about these features... I'm only mentioning it.), hold the tab "on top" and Start screen-recording. This doesn't happen if you hold the tab in normal position...

Edit: Just saw, this does also happen IF YOU DO NOT hold the Tab in Landscape-Mode Samsung-logo down-side.
[Galaxy Tab 10.1 Android Development] drp:
Same here; Netflix crashes prior to login screen. Rest of ROM great so far.
[Galaxy Tab 10.1 Android Development] AAccount:
My I9300 has a netflix script on it because apparently it also has issues with netflix. Try running the attached script and see if it works. I just ripped the file straight from the update.zip.

I don't have netflix. I just know of the script's existence.
[Galaxy Tab 10.1 Android Development] rogconnect:
My n7000 has it too......I tried to push it to my P-7510. But Netflix app just FC when clicked.
[Galaxy Tab 10.1 Android Development] AAccount:
Oh, well that's the best I can come up with.
[Galaxy Tab 10.1 Android Development] rogconnect:
Yeah... well maybe it's app related!

Viki, FiOS mobile ...works fine for me even HD streaming not forgetting YouTube HD and LIVE streaming work too. Yet, paid subscription Netflix don't.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Anyone here with a gt-p7500/7501, wich can verify the issue I mentioned?

-“on-top-holding-issue"

-PIN-PAD squashed

-Dialer crashing, when you start it
[Galaxy Tab 10.1 Android Development] SystemDoctor:
I can't seem to enable camera through Terminal Emulator any help?
[Galaxy Tab 10.1 Android Development] jaibar:
You need to enable superuser first. Just type "su" (without the quotation marks), then {enter}. You should see the superuser icon #.

Then type the command to enable camera and {enter}. Make sure you type the exact line without typo errors.

Should work. I think it was mentioned a couple of times in previous page, but maybe needs to be added to OP so there is less confusion?
[Galaxy Tab 10.1 Android Development] SystemDoctor:
It says killed? Should it say that?
[Galaxy Tab 10.1 Android Development] jaibar:
You sure you got root? Did you reflash supersu immediately after flashing ROM as instructed in OP? Or modified script so it is done semi-automatically?
[Galaxy Tab 10.1 Android Development] SystemDoctor:
I have root but I didn't flash SuperSU immediately after flashing is this the problem?
[Galaxy Tab 10.1 Android Development] crippleye:
Omnirom has no root by default. Make clean install and flash SuperSu above.

---------- Post added at 09:10 AM ---------- Previous post was at 08:58 AM ----------

Well i ve been flashed this rom today.

bad

1. 2g/3g toglle dont work system menu toggle too. Thats sad...

2. System localization missing in some menu places

3. Stock launcher works a bit slow for now

Good

1. Keyboard a bit better than 4.2

2. I really like home screen)

3. Camera works

Will stay some more on this rom and push some buttons... :D
[Galaxy Tab 10.1 Android Development] otcd:
USB

Thank you for the ROM. For some reason connecting the TAB via the USB to the PC, the TAB is no longer found nor shown. Any idea?
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Make sure that MTP connection is enabled via settings
[Galaxy Tab 10.1 Android Development] eushaun99:
Settings -> storage -> 3 dot menu -> USB computer connection. Make sure MTP is ticked. It seems to be unticked by default.
[Galaxy Tab 10.1 Android Development] otcd:
Perfect!! Thank you Sir.

---------- Post added at 11:50 AM ---------- Previous post was at 11:49 AM ----------

Thank you!!
[Galaxy Tab 10.1 Android Development] sub501:
Update OMNI -> OMNI always ruin my tablet

Tested second time. The update from previous OMNI version is always breaking my tablet.

Tested P7500:

21 -> 27/12 update - not working

27 -> 01/01 update - not working

In both cases the tablet is stuck on "Finishing boot". Reboot is not solving the issue.

Installing from scratch (wipe) is working but this is not a solution in my case as I have 3 user accounts and various app/configs.

Any idea? Could it be an issue with the update on multiuser setup? Is it related to this message received during flash "Unknown filesystem datamedia"?
[Galaxy Tab 10.1 Android Development] durius:
wi-fi error

hi,

I wanted to have a taste of KitKat on my p7500 and so decided to install this rom.

After a few problems during setup all solved with some try an error attemps, I am having trouble with wi-fi connection.

I can connect to my wi-fi network but there is no data transmission and all webpages and services (such as google play) do not work.

If I switch to 3g connection all is fine.

Can someone tell if this is a known issue and some tips to solve it?

thank you to the developers for such a nice work
[Galaxy Tab 10.1 Android Development] John Kester:
Dialer crashes on me too!
[Galaxy Tab 10.1 Android Development] kasper_h:
You will need to fully wipe (assuming you come from Omni 4.3?). No way around it when moving between major android revisions. It's a one-time thing, updating from Omni kitkat -> Omni kitkat is a simple dirty flash.

This is why there are apps like titanium: helpful to backup apps/settings.

I have said before the the p4 build is a courtesy to those with a p7500. I will not do any work on it. If someone has a solution, they can push it to my github and I will include it in future builds.