yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Indeed multiwindow is a problem in the most recent build. That's why whenever I want to switch apps I need to go back to the app drawer because I don't want to keep on getting this issue
[Galaxy Tab 10.1 Android Development] kasper_h:
I have removed multiwindow for the time being, so the next build should be free from this issue (but will also lack the feature itself).
[Galaxy Tab 10.1 Android Development] pspnewcomer:
After installed p4 rom. My p7500 tab cant connect my 3g data. Any solution?
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Yepp, it has got some issues! It can auto-activate itself somehow now & then.

It also seems to cause app-crashes/restarts and rarely even soft-reboots.

I also noticed: If you dirty-flashed from an older build, you've got to clean the cache of some apps! App of the day is an good example (shows logo, then current app-list, then-logo again and so on...), but also Voodoo and a few others seem to be affected.

On the other hand, the fixes to hwcomposer and/or surfaceflinger really improve the ROM!

Can't get it to crash anymore in Immersive-Mode and graphical issues also seem to be fixed. But I didn't tested it excessively yet.

Add an APN in Settings --> more (in Network related stuff).

---------- Post added at 02:33 PM ---------- Previous post was at 01:53 PM ----------

Think I've found the issue, which causes the Tab to soft-reboot...

It happens, if you start an app from recent apps which got terminated before... Maybe a pointer-issue?
[Galaxy Tab 10.1 Android Development] pspnewcomer:
Thanks. That means this ROM cannot auto detect the network APN?
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
AFAIK this is a problem for all Android-Custom-ROMs since 4.3 (atleast for our Tab). Atleast it can detect it on this 4.4-CROM, but even thought it showed my provider, I still had to manually add the APN to get FULL 3G-Functionality.

Another thing I just noticed... Overclocking seems to work, but isn't set on boot... Am I the only one to have this problem?

...and... Yet another thing... If you're on Immersive-Mode and got to use multi-window, the bottom-bar isn't shown and the app also leave a black border on the bottom and don't stretch to full-screen (multi-window-thread not being notified of the device running in Immersive-Mode, or simply not adapting to it?).
[Galaxy Tab 10.1 Android Development] r0by:
Installed the newest version. Working fine, imei is finnaly ok, yepp!

But, the system is laggy. Ony for me?

Install the rom twice with full wipe.

May cause the governor settings in the perfomance menu? What is the recommended settings?
[Galaxy Tab 10.1 Android Development] AAccount:
Setting overclock on boot might cause boot hangs at the "Samsung Galaxy Tab 10.1" logo. It's a dumb luck process. Sometimes it hangs sometimes it doesn't. It's specially designed to reset to the stock 1GHz speed on every boot to remove luck out of the equation when booting :p
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
The system itself, or the launcher?

Try another Launcher like Nova Launcher (Prime), or you can get Go Launcher Ex for free today with a promo-code! :)

Really a full wipe, including Data and SDcard?

Currently there is no recommended governor, atleast AFAIK.

---------- Post added at 05:40 PM ---------- Previous post was at 05:37 PM ----------

Ah, I see. Hope we can have the luck "on our side" at some day, thus it'll not hang on the logo...
[Galaxy Tab 10.1 Android Development] r0by:
Really full wipe:) Push rom to sd with adb:)

I think the lag is not launcher specific (try a chance for apex), I see it on settings menu scrolling. And under Opera too. Try factory reset, same result.

Otherwise, no problem, thx the good job and waiting the next smooth version:good:
[Galaxy Tab 10.1 Android Development] kasper_h:
Changelog of 25-Jan-2014

-Omni codebase of 25-Jan

-Removed Multi-Window

-Added a series of patches that should save battery life

-Added ribbon tiles (notification screen)

Downloads:

P4WIFI:

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

P4:

http://rootaxbox.no-ip.org/kasper_h/roms/p4/omni44/
[Galaxy Tab 10.1 Android Development] sgs9:
great, simple dirty flash, work, thanks a lot.

Gesendet von meinem GT-P7500 mit Tapatalk
[Galaxy Tab 10.1 Android Development] highjagger:
it rocks

here too, thanks.

i switched from cm10.2 to 05.01.2014 build. this rom is _much_ faster. we use the tablet with two google accounts.

under cm10.2 switching user was terrible slow, also using chrome. now that works fine.

i had some trouble with setting governor/frequencies via menu also with smartassV2.

the second core get as max_freq only 456mhz after resume from suspend. also it seems that only one cpu is affected from the setting. i use an own userinit.sh to set governor (wheatley) and max_freq (1200) for both cores. with wheatley everything works also after resume.

on default there is only one zram, but we have 2 cores. to maximize cpu usage we could use 2 zram with swap on same prio to share the compression load between the two cores.

is it possibile to add zram.num_devices=2 to the kernel parameters? than everyone who like to use it can initialize it with an own startscript.

thx very much for that build and go on.
[Galaxy Tab 10.1 Android Development] biggiebro:
Just complete a dirty flash and the ROM feels much more responsive. Noted the battery saving feature. Although the previous multi-window implementation does not work well I hope that it will made it into the next update. It is a very useful feauture.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Agreed! I really hope for a stable and sufficient multi-window-approach!

I'm still on the old ROM,...
[Galaxy Tab 10.1 Android Development] decatf:
The brightness settings don't apply on boot to what it is actually set to. On boot it is always boots to the same brightness level.
[Galaxy Tab 10.1 Android Development] Dreameagl:
The "screen-off animation" doesn't seem to change for me. The PA had a really nice electron beam/CRT animation, but I just seem to get a fade out no matter which option I choose.
[Galaxy Tab 10.1 Android Development] fatjoejr2001:
Theme engine implementation in the near future?
[Galaxy Tab 10.1 Android Development] alexkno:
Yes, same here. Although I use auto brightness. But I need to de-activate and reactivate it after boot as it always comes up with very high brightness
[Galaxy Tab 10.1 Android Development] eushaun99:
That would be up to the Omni team to implement it. A good alternative is using XthemeEngine which requires Xposed framework.
[Galaxy Tab 10.1 Android Development] kasper_h:
I don't know whether that really works. All devices I looked at, also other multi-core CPU ones, don't use 2 here (also the example code of code does not show that AFAIK),

I also like it a lot, and there is some work being done on it, so it hopefully improves soon.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Flashed the new build now...

Meanwhile (before flashing the new build) I found another reason, for normal app-reboots... If you activate Dark Omni and it changes colors, while you're in an app... For example if you let it change by light-condition...

Yepp, Electron-Beam-Animation doesn't work currently.

The ROM still seem to have some IO-Issues here and there (regardless which governor is used).

Sometimes it acts like if DATA-IO is PIOed, instead of DMAed... Even on a nearly clean ROM there can be short idle-times.

Honestly,... Most hangs and idle-times which occur do so, because of an app in background hanging... If the system gets slow, it is more because of the app - management of the OS, rather than because of too less CPU-Power.

Btw.:That's what normal build.prop - values seem to be for VM Heap.

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m

So,... Honeycomb-Stock-ROM - values for our Tab seem to be:

dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=288m

...according to what I've found on stackoverflow.com

Didn't found the ICS - values for our Tab yet.

I'm going to try these values later...

Might stop some apps from FCing and hanging, causing the system to slow down...

Edit: Which build.prop-tweaks have an effect in Android 4.4.x?

Any of these:

debug.sf.hw=1
debug.performance.tuning=1
ro.kernel.checkjni=0
ro.config.nocheckin=1
persist.sys.use_dithering=0
video.accelerate.hw=1

?
[Galaxy Tab 10.1 Android Development] kellyj1978:
Hello All,

I dont know what i have done but i have a issue after completing a full wipe to install the latest version

Wiped data

wiped cache

wiped dalvik

pushed rom to device

flash rom

reboot

once booted i am getting - unfortunately, google text-to-speech engine has stopped (no gapps installed yet)

click ok then i get a black screen, but the back arrow is displayed

i hit back then get the google text-to-speech message again - hit ok

now at the wizard hit the next button

then get unfortunately, setup wizard has stopped

i get taken back the the black screen with the back button

Using 6036 CWM

i have tried re downloading rom and pushing it to the device again but i get the same error
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Try to wipe system-partition, before you install the ROM.

This build is the fastest of all in fluidness/Responsiveness, but seems to be slow in Videos? Not sure, if it is a problem of the Game One - App..
[Galaxy Tab 10.1 Android Development] X1iGGVV:
Nice ROM, but! One question about searching: if I mark some text on the screan, before on 4.3.2 ROM, In the header jumps up options for, copy, mark all, Websearching and searching the marker text on the screan. It works in the apps too. Now is this searching posebility away. Why? Feels like a step in the wrong direction. ?

Skickat från min GT-P7500 via Tapatalk
[Galaxy Tab 10.1 Android Development] kasper_h:
For me it still works. But it does depend on the app, some apps do not work with it. But that is then an app problem, not a ROM problem, AFAIK.
[Galaxy Tab 10.1 Android Development] X1iGGVV:
Same app I use and it dont work anymore. I havet not this searching posebility nowhare anymore. Hmm.. ?

Skickat från min GT-P7500 via Tapatalk
[Galaxy Tab 10.1 Android Development] kasper_h:
It may be related to kitkat-update to the app...

I just tried browser, gmail, xda HD (which has no "search now button", but the other for select/cut/copy are there).
[Galaxy Tab 10.1 Android Development] sgs9:
copy thing ;) work fine on my tablet.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Here are some bugs that I found, Please verify if possible

1)Google Play Store Crashes after the latest build, need to reflash gapps

2)Some apps got uninstalled

I'll be on the lookout for more.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Nope, both didn't happen to me.

I dirty-flashed all builds since 5.1.2014-build.

All in all, it is the most stable, fast and fluid/responsive ROM for our Tab. Atleast IMHO...

Known issues:

-Multiwindow or Split-screen-suport isn't in the newest build, but it also feels even more responsive. Idle-times are shorter and less App FC. Another issue the newer real Multiwindow-implementation compared to Split-screen-support introduced was softrebooting, if you tapped on an app, which FCed before but was still shown under "Recent Apps".

-DarkOmni-Autoswitching can lead some apps to reboot like Chrome Beta...

-Network-activity- and speed-indicators don't work currently

-SwithOff/Standby - Animation ("Electron-Beam/CRT-SwitchOff)

-Partially the things mentioned in OP.

-settings like clock-speed are not set on boot, due to it seemingly being pure luck, if the tab does hang on Samsung Galaxy Tab 10.1 - Logo, or not...

[MENTION=3033992]kasper_h[/MENTION]:

The newest build is VERY STABLE, even thought not all functions are working...

Some Apps are of course still FCing on overload, or restart once Dark-Omni auto-changes but I couldn't get it to fully crash, or soft-reboot neither way I'm trying it.

I mention it, because I think the crash- and Immersive-Mode - note in OP under issues can be removed. :)
[Galaxy Tab 10.1 Android Development] kasper_h:
1. Yes, also to me the version without multiwindow seems both smoother and more stable

2. I had no issues with DarkUI, but it does change some low-level stuff that app may no like

3. Network activities hasn't work for any Omni ROM (JB/KK) on our tab, whereas it works for other devices (including tablets). I have no idea why, code seems to be fine

4. The screen-off animation is something I think I solved, but we will see that in the next release

5. It is indeed better to no set frequencies on boot, as AAccount explained.

Glad you like this latest builds. It is for me the first time I don't feel the urge to solve all kinds of things and rebuild ASAP :)
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Hope they get an implementation of Multiwindow running, which doesn't suck so much power. Doesn't even seem to use so much CPU-, but introduces heavy I/O - Load. Any way to debug this specifically with some Android-internal tools?

You can try it by setting it to auto-change on daylight. It also seems to cause widget-crashes and occasionally because of that even Launcher - hangs and FC-Requests.

"Winter-light" (kinda grayish) is perfect for multiple changes within 10Seconds (I'm in Europe, not Australia, so it's Winter here).

I know. Just wanted to mention it, to get an updated known issues list, for the OP.

Would be kind of cool. I used it on PAC before, even on Diamond if it was present there and it looks cool.

I even used it on HTC One X with CM10.2 Stable.

But there must be some kind of cause,... I really hope this to be working someday... Maybe a little waiting-delay somewhere might help?

...or is it an init - issue?

Yerp, hwcomposer&surfaceflinger-updates and fixes really pushed Responsiveness and stability... In case of multiwindow,... Well even the Omni-ROM consider the new version to be experimental... Let's see, how well it works in 2weeks/a month. :)
[Galaxy Tab 10.1 Android Development] TabGuy:
I vote against multi-window if given a vote. It seems to remove stability. I have a Note 3 and a Note 2 and find multiwindow uninteresting. Most apps aren't multi-window aware and only half of the app is displayed when in a window. It's a waste of time to me.
[Galaxy Tab 10.1 Android Development] Raistlin1:
Dirty flashed the latest from doing a clean flash of the version right before this one and I have noticed when I am using Chrome that my screen flickers sometimes, didn't notice this previously.

So far this build is awesome though, Chrome is very fast compared to how it was on ICS. Love immersive mode but I don't like that the notification bar goes away, I would prefer to keep the top bar and lose the bottom bar as an option. With that being said the immersive mode works very well, sometimes have an issue with swiping up to get to the back button but that is probably just user error.
[Galaxy Tab 10.1 Android Development] Osirus71:
^^^^^^^^^^^^^^^^What he said......maybe multiwindow could be a flash able zip to enable it for those that want that feature....
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
IMHO, MultiWindow IS cool, but as long as even the Omni-Team (just noticed it made Omni-ROM out of Omni-Team in my previous post...) considers the new Staple-MultiWindow experimental and as long as it introduces too much IO-Load, thus decreasing system-stability and overall performance, even if only one app is running and using full-screen and as long as the implementation simply isn't more efficient, I also vote for a "normal build".

But time will tell... I'm sure we'll see it someday, maybe even natively supported by Google/Android. :)

Just look at the current build and how fluid it runs even with snapshot and 2-bar-system-ui. Not even Diamond ROM was that responsive&fluid... Not Omni 4.3, not SGT7 and sincerely not PAC (neither of those builds).

Other than that, the wait-/idle-times are very short, compared to any other ROM. Going into and coming out of StandBy; switching between apps, scrolling in apps... Most, if not all (not sure about audio/video-stuff) is faster and smoother. Proper Auto-rotation is implemented, even ART is working quite good (but due to it's nature of also being an experimental feature, it sometimes introduces some quirks, lags and instabilities).

Now how much time passed since those other already quite good builds?

I'm almost sure we'll see a stable & fluid build before my next birthday (which is in the end of march), including a non-so-experimental MultiWindow-Implementation. :D
[Galaxy Tab 10.1 Android Development] kasper_h:
I agree with the above post that large steps have already been made and we will hopefully see even more improvements in the near future :)

With regard to ART: I merged a whole range of experimental patches for the art runtime. Feels good to me :)
[Galaxy Tab 10.1 Android Development] hemligsomfan:
First of all, thank you for your hard work. Love that you are doing the work on our old tablet.

Second: bugg report.

Installed a December release (i think) early January. Everything worked perfectly. No flickering att all of the screen, Netflix worket fine (autoupdate on). SuperSU installed fine.

Flashed Jan 19 build (on top of the old): Unable to flash SuperSU (redownloaded several times), Superuser finaly worked after some testing around. Introduced flickering, Netflix stoped working (autoupdate). Downgraded to sugested version, didnt have time to start and check if it helped. Forgot autoupdate on and it autoupdated. Didnt mater, worked like a charm anyway :)

Flashed Jan 25 build: Lots of flickering. And it killed Simpsons: Taped Out. Can not for the life of me get it to start. Redownloaded and did a clean install, newly downloaded gapps pack, Still unable to flash SuperSU, Superuser works.

Without a working Simpsons: Tapped Out i had to revert back to the Jan 19 build (yay i remebered to do a backup)

Any chance there will be a MD5 checksum inkluded in later builds. Would be nice to know if the .zip is intact.

and olso is there any plans to include settings like in CM for OC and governor?

Thanx.
[Galaxy Tab 10.1 Android Development] kasper_h:
I will look into md5.

OC is anyway available.

Governor/scheduler as well: available in performance settings.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] biggiebro:
I love the multi-window feauture, it is one of the maim contributors for productivity on this note (I am still using it for work). The idea of I can use a browser/PDF reader along side email/office app means that I do not have to use bits of paper etc to jot down important point anymore. I am drawn to this omni rom with the promise of multi window feature. A flashable zip will be the best solution.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
I'm sure we will. :)

Also in the currently released build? It is quite good already, but still not as "mature" as Dalvik-VM.

I can also confirm that there are more flickers than on some older builds. I even had a flicker on the Omni-Logo, shortly before it shows the PIN-PAD...

Also got the Tab to soft-reboot, by holding the power-button to show the extended power-menu...

...and PIN-PAD-Issue seem to be present on P4-build still, but I know you've said you won't work on P4-Specific bugs.
[Galaxy Tab 10.1 Android Development] kasper_h:
ART improvements are present on the latest release of 25-Jan.

I do not understand the pin-pad issue, as the pin-pad on p4wifi looks fine. And upstream patches have been merged that should have solved it. So I have no idea how to solve it....even if I would :)

I also have a bit more flickering. I am working on a small update ATM, that will have some layout (in the settings app) & colour schemes solved (there is sometimes white-text-on-white-background), I also cleaned out some of my projects that may be causing some of the graphical issues.
[Galaxy Tab 10.1 Android Development] kasper_h:
Changelog of 28-Jan-2014

-Omni codebase of 27-Jan

-removed dysfunctional stuff (KitKat white-on-white, double-tap-to-sleep, network speed, and many other minor patches).

-updated keyboard based on CM (QWERTZ has more multi-function keys, multi-function options are shown in ligher grey).

-improved privacy guard

-additional lockscreen options

-hopefully solve some graphical glitches

-screen-off animations work (but are glitchy :))

Downloads:

P4WIFI:

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

P4:

http://rootaxbox.no-ip.org/kasper_h/roms/p4/omni44/
[Galaxy Tab 10.1 Android Development] kasper_h:
Oh, forgot to mention in changelog: the issue with soft-reboots when pressing power button is also solved.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Ah, now I understand the confusion...

Just to point it out... EVER, when I pointed out the PIN-PAD-Issue, I was referring to the SIM-PIN-PAD!

Well, seems to be intended for the normal PIN-PAD, not the SIM-PIN-PAD...

Yepp, noticed the white-on-white, but forgot to mention it.

About the last part: "Which namely are?"

THX! Will try it later.
[Galaxy Tab 10.1 Android Development] X1iGGVV:
In dark OMNI when answering a email! White background and white letters, that make dark OMNI impossible to use. ? That is some of the white-on-white situations, in my cace actually the only one that I havet problem with. I gues that it can be some more as usually like SMS aso.

Skickat från min GT-P7500 via Tapatalk
[Galaxy Tab 10.1 Android Development] kasper_h:
There are indeed still a few places remaining with white-on-white problems, but it should have been drastically reduced in the latest build.
[Galaxy Tab 10.1 Android Development] X1iGGVV:
I'm on the lasr one! ? Nice job U havet done anyway! Keep upp ... ?

Skickat från min GT-P7500 via Tapatalk
[Galaxy Tab 10.1 Android Development] hemligsomfan:
Can't seem to find the Performance menu. At the bottom of settings right?

Will try out the latest build later today.
[Galaxy Tab 10.1 Android Development] kasper_h:
You need to go to About>Tablet first. Press build number 7 times. And watch the magic happen :)
[Galaxy Tab 10.1 Android Development] hemligsomfan:
Natural. Cut that wasn't included in OP I figured that that step wasn't necessary. :eek:
[Galaxy Tab 10.1 Android Development] alexkno:
Thanks! Another great ROM. But a pitty that double tab to sleep has gone :(

sent via Tapatalk
[Galaxy Tab 10.1 Android Development] decatf:
Deep Sleep state is not working.
[Galaxy Tab 10.1 Android Development] TabGuy:
Kasper,

Until the bluetooth speaker connectivity is licked I have to move back to 4.3. I know you did both Omni and Infamous versions for 4.3. Which one do you recommend?

Thanks.
[Galaxy Tab 10.1 Android Development] rickyq12:
Which recovery is recommended to flash KK on our tabs? CWM or TWRP?
[Galaxy Tab 10.1 Android Development] John Kester:
Both work, but I use CWM 6.0.3.6 and have not had any issues.

Cheers.
[Galaxy Tab 10.1 Android Development] rickyq12:
Thanks man...I appreciate the quick response.
[Galaxy Tab 10.1 Android Development] rickyq12:
OK...I've honestly searched and can't find a zip file or any type of way to update my recovery.

Where and how do I flash the latest recovery to flash KK?
[Galaxy Tab 10.1 Android Development] Soryuu:
TWRP is available in the A1 kernel thread, as a flashable zip (called twrp2630.zip). So if you already have a custom recovery, you can just flash that through it.
[Galaxy Tab 10.1 Android Development] kasper_h:
They are very different in many aspects :) In general, Omni has less features and is more stable.
[Galaxy Tab 10.1 Android Development] jaibar:
How did you check it?

When I look into battery usage, it definitely shows the device is in deep sleep, as well as wakelock detector and betterbatterystats, so if all of them are saying it is deep sleeping, then it probably is... :silly:

Did you check for some rogue app keeping your device awake?
[Galaxy Tab 10.1 Android Development] kasper_h:
Indeed, my device sleeps fine as well. So probably an app that keeps the device awake. I prefer betterbatterystats to check for such apps (or processes).

Verstuurd van mijn Nexus 5