yashsingh1/xdaforums huggingface dataset:
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Mine was dirty-flashed from 12.1.2014-build, so I don't know.

Just want to do a little bug-report and mention the widgets beside dashclock-widget which I forgot... They are YouTube-; TegraZone-; internal clock-; SMS-; Spotify-; 3*GooglePlay-; Öffi-; Google-Drive-; Google-Now-; Calculator-; Google-Now-"Which Song"-; Avast-; Energy-; Google-Play-Music-Widget... All that and still running fluid on this "old ass tablet". :D

The graphic-glitch-fixes can cause system crashes (I guess it is neither a simple software-hang, nor a Kernel - Panic [still could be thought], but a fatal system-error, since it crashes and reboots to the "Samsung Galaxy Tab 10.1"-logo, instead of softrebooting to the Omni-Logo.)!

I think a buffer/cache or" VRAM" get's corrupted... I'm not sure if it is the frame-buffer, but could be it if there's written to it while it's drawn and there's no handler to correctly do this after another, rather than during drawing... Also could be a mid-buffer, but then it is more likely to show something like the flicker... Is the picture we see double-, or triple-buffered, or simply "single buffered" (means directly written to the frame-buffer)?

The issue can be reproduced in both, the Immersive-Mode and Normal-Mode. It seems to belong to the "blend-out" of the System-UI and also happens if an app supports the blend-out of the System-UI in Normal-Mode.

It can be triggered way easier, if it blends in and out very often in a short time. Try the recent-apps-button, let notifications show up, go into an app (so keep notifications open and double-click on the app you want to show up from recent apps, etc.) in a short time. This example causes 2-3 very fast changes between apps and blend out, or not..

All in all, those "fixes" introduce serious crashes and I rather have the newest ROM in a stable state with flickers, than vice versa...

But IMHO,... Yes, it looks better without flickers.

Best suggestion is to keep Immersive-Mode off currently, but those crashes can still happen in Normal-Mode!

Beside that, the ROM is very stable... No FCs as of yet, whatsoever... :)

A1-Kernel even squeezes more speed out of our Tab.

I changed VM-Heap-Size to 60, even thought since this build it even ran fluid with basic setting. Just to be "sure". :D
[Galaxy Tab 10.1 Android Development] Raistlin1:
When I turned my Tab off last night to charge it the tab would not charge, I took cable off and put back on but same result.

This morning I turned my tab on after being plugged in all night and it did not charge at all. I connected the cable while the tab was on and it started charging. This was all done using the charging brick and cable the tab originally came with and I am on the ROM version right before this most recent release and using TWRP.

I also noticed that it took a pretty long time to hold the power button down to get the tab to turn on, this was never an issue on the official ROM.
[Galaxy Tab 10.1 Android Development] rogconnect:
http://goo.im/devs/BaNkS/GApps/4.2.2
[Galaxy Tab 10.1 Android Development] eushaun99:
[MENTION=5626369]TnA.Plastic[/MENTION] try setting the heapsize and heapgrowthlimit to 116. That's what v6 supercharger sets based on the ram. Oh ya, performance control can't edit heapsize etc values since its in build.prop.
[Galaxy Tab 10.1 Android Development] kodrnusa:
Where is the download link for the rom? Am I blind?
[Galaxy Tab 10.1 Android Development] alexkno:
http://xdaforums.com/showthread.php?p=49571208
[Galaxy Tab 10.1 Android Development] kodrnusa:
Which gapps to use? Link?
[Galaxy Tab 10.1 Android Development] eushaun99:
Google search PA 0 day gapps.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Ups, yerp build.prop...

Will try that later. No issues as of yet...

Btw.: The newest build also seems to address the screen-rotation-issue! :)

[MENTION=566998]raistlin[/MENTION]: are you coming from HC, or ICS?
[Galaxy Tab 10.1 Android Development] nokia-xxx:
Here you go:

https://www.androidfilehost.com/?fid=23311191640114537
[Galaxy Tab 10.1 Android Development] Dreameagl:
I'm not sure if this is a documented issue. When you change the slider shortcuts for the lock screen in landscape, half the targets are off screen to the right. I can only get to all of them in portrait.
[Galaxy Tab 10.1 Android Development] eushaun99:
Thanks. I wanna know your opinion on setting both to 116 since you seem to be the guy that can notice even the slightest of lags. :D
[Galaxy Tab 10.1 Android Development] alejandrob1:
I just installed following op instructions but I get stuck in the omni boot screen. Did it on the latest cwm, and when I selected reboot system now i got a message that stock kernel might be flashed and hit no, does that has anything to do or what am I missing. Thanks in advance
[Galaxy Tab 10.1 Android Development] crippleye:
Interface is a bit chaotic, but the system becomes more useable from build to build, keep up a good work
[Galaxy Tab 10.1 Android Development] rogconnect:
Try flashing with TWRP 2.6.3
[Galaxy Tab 10.1 Android Development] fleckdalm:
The latest build is working really great! Thank you very much!!
[Galaxy Tab 10.1 Android Development] drashran:
Can u explain a bit, how it works on Tab

I am unable to understand some of the things stated in the update below

I am using BaNKS ''11-26 GApps Core 4.4 signed''
[Galaxy Tab 10.1 Android Development] nokia-xxx:
I tried several GAPPS, but none of them worked for me... This was the first functional GAPPS version I ran into....

Has anyone tried the ART runtime of this ROM?
[Galaxy Tab 10.1 Android Development] alejandrob1:
Just tried with trwp 2.6.0 and it just wont boot, i will give it a try with the latest trwp. Noob question for that matter, to update twrp i just have to search and flash the latest version?
[Galaxy Tab 10.1 Android Development] rogconnect:
Search for Aaccount's latest kernel.....flash it and then reboot recovery and then flash the ROM and SuperSU 1.89.zip.

Sent from SPH-P100 KitKat 4.4.2 using Tapatalk Pro
[Galaxy Tab 10.1 Android Development] nokia-xxx:
I used CWM as well, but I not only deleted all possible data & cache. I also formatted everything (system, cache, data... ofcourse not the SDCARD)....

Could that be a solution for you?
[Galaxy Tab 10.1 Android Development] rogconnect:
ART .....using since first build... no what so ever problems if no EXPLODED installed.

Sent from SPH-P100 KitKat 4.4.2 using Tapatalk Pro
[Galaxy Tab 10.1 Android Development] tonisauffa:
Hi guys......I have a problem with the debug usb......the pc don't see the tablet as a device! Who can help me? Thanks

Inviato dal mio LG-D802 utilizzando Tapatalk
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Settings --> Storage (or however it is called... In German it is called "Speicher"...) --> Three dots menu --> Tick MTP - Device...

[MENTION=4467956]nokia-xxx[/MENTION]: Yepp, I'm using it since the first build of this ROM. It runs quite good and within an app, or even starting one could be faster, but it is really an experimental feature and is not officially supported by the omni-team, thus if there are issues you're on your own... It introduces some idle-times and isn't 100% stable, but it works quite good...
[Galaxy Tab 10.1 Android Development] wonderer2:
This issue has been answered before many times. Go back some pages and You will get an answer...
[Galaxy Tab 10.1 Android Development] alejandrob1:
I flashed A1 kernel but still no luck, the only thing left is the supersu, I flashed 1.85 and you are saying 1.89, i will do it altough I dont think that should be the cause of my tablet not booting.

Any links fir 1.89 supersu? Thanks
[Galaxy Tab 10.1 Android Development] kodrnusa:
I tryed gapps 4.4.2 odexed beta v5, but then I stuck on boot logo. Omni rom logo is displyed for 10 minutes. And just doesn't boot up.

Is there any gapps app that works?
[Galaxy Tab 10.1 Android Development] TabGuy:
I installed today's update. I can report that bluetooth speaker connection is still broken.
[Galaxy Tab 10.1 Android Development] rogconnect:
This twrp2630-wifi.zip?

http://download.chainfire.eu/376/SuperSU/UPDATE-SuperSU-v1.89.zip
[Galaxy Tab 10.1 Android Development] alejandrob1:
Yes I am using that recovery but it just wont boot, now im out of ideas
[Galaxy Tab 10.1 Android Development] rogconnect:
Did u format system after full wipe b4 install the ROM?
[Galaxy Tab 10.1 Android Development] wtgserpant:
Install the PA minimal gapps as the other ones are too big for our root partition. And also use the latest recovery.

Clear cache after installing gapps.I dirty flashed on 4.2 and its working very well. ?
[Galaxy Tab 10.1 Android Development] alejandrob1:
Tanks for your help, it finally booted it was the gapps package
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Nope, it is related to files residing on the data-partition, probably system-settings-related. Flashing another Kernel can help in this regard... Another way might be to downgrade to an old version, start it up once without changing settings and then again reflash the ROM, after wiping atleast system, cache and Dalvik-Cache...

Best way is to try to wipe data also and re-install your apps after installing the ROM.

[MENTION=3067140]kodrnusa[/MENTION]: I think you've ran into the same problem. Either that, or it didn't copied some necessary gapps-files, because of the package being to big... But that should still let the system boot up in most cases... Try to format data.

[MENTION=4311537]bothof[/MENTION]you: Wiping Data should help. You can make a backup and restore it, if this won't help.

Edit: O.k. Atleast Alejandro's problem got fixed...
[Galaxy Tab 10.1 Android Development] TRSHD:
So ashamed...

Hello all! I don't consider myself as a n00b, but there must be something right in front of me that I can't figure out and I'm now completely helpless...

I'm coming from stock on my p7500 but for the love of gawd, I CAN'T FLASH THE TWRP on the damn thing!!! I uninstalled Kies, the tab is recognized by Odin and all, converted the TWRP .zip to a .tar but it's still not working!!

I've been on this for the past week and I've now swallowed my pride, please, help...

Thank you all!

PS: win7 32bit
[Galaxy Tab 10.1 Android Development] jmy006:
hdmi

hi guys

this evening I tried the plug hdmi but it does not work ,

I am the only one?

once again thank for your work :good:
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Why don't you just try to install a recovery thru Odin, which for sure works (CWM for example) and then flash the zip?

[MENTION=3033992]kasper_h[/MENTION]: Would you mind updating the first post with the new date and also the known issues, like bluetooth-audio and HDMI not working? Another thing is, that screen-recording causes soft-reboots (Kernel - Panic?). Immersive-Mode should be disabled thought... (it is causing serious system-crashes, probably due to the "graphic-glitch-fixes"... More indeep explanation a few sites back...)

Those other issue mentioned there, are virtually non-existant anymore (Screenshot is enabled and doesn't cause a sluggish System-UI anymore and for example the "rotation-issue" got fixed in the 19.1.2014-build).
[Galaxy Tab 10.1 Android Development] EvgeniX:
Hi,

its only me or where is link to download ROM?
[Galaxy Tab 10.1 Android Development] kasper_h:
Can someone confirm the issue with HDMI? No cable to test ATM. Can't update OP now, as the xda app crashes when I try to do so.

Anyway, for those with issues upon installing: make sure to wipe /system in addition to factory reset. And first flash ROM and boot. Then reboot to recovery to separately flash gapps. Seems to work better to flash all at the same time.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Here the procedure to cause the serious system-crash:

WARNING!

I'm not responsible to any damage to anyone's hardware/tab who tries it, but I reproduced the problem at any case, when I tried it this way...

There could be Data-loss and/or NAND-Corruptions, if there are writes done to it, while the system crashes...

For example your partition-table could be corrupted and you have to re-flash your Tab with Odin!

(*) -freshly boot up your system, to make sure there's nothing else, which can cause it...

(*) -let it "settle"/rest for a few minutes, to make sure all is booted up and started... (so no NAND-Writes are done and the System doesn't hang because of some kind of overload...)

-enable Immersive-Mode, since it's very hard to trigger the same thing on Normal-Mode and AFAIK is only possible with apps support "blending out" the System-UI.

-start for example Google Chrome

-go to your Launcher

(*) -drag down notifications (Seems a bit easier to trigger then.)

-press recent-apps-button

-drag down notifications

-double-press on the app you started before

(*optional)

Better yet do it fast, but I think Immersive-Mode on, recent-apps-button press, notifications-drag-down and double-tap should be enough to trigger it/the crash/event.

Short graphic-glitches should occur somewhere in between the procedure. Shortly after double-press, the system should freeze and after estiminated 10-15Seconds, the Tab should "hard-reboot" to the Samsung-Logo.

This procedure should only work on the 5.1.2014- and the 19.1.2014-build, not on the 12.1.2014-build and all those builds before 5.1!

Anyone want's to try and/or can confirm it? :)

...and to quote myself ( :D) and without looking at the source(-changes/fixes) I think this is the cause of it:

Still could be something else thought...

I should add, that I use another modem (which shouldn't be an issue thought) and the A1-Kernel (which could be an issue, but I seriously doubt it. I believe I also had those crashes without A1 on 5.1.2014-build. I definitely could trigger the event there. I'm just not sure, if I installed A1 already.).
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Seems legit. I'll try it in my p4 since I bricked my p4wifi.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Up on finding the bug, I expect it to be in the function which is called, when the "visible screen-size" (which Apps can use) is re-allocated or atleast is connected to it, thus possibly corrupting the frame-buffer.

Of course it is only speculation from the behavior of and how to trigger the event + graphic-glitches I've seen and screen-shoted (but couldn't attach).

If not there I still believe the bug to be in the render-engine, which sets up the frames outputted to the screen and it seems to be in conjunction with the screen-reallocation (which also possibly could be another culprit for the soft-reboots, if you screen-record).

Maybe wrong Frame-Resolution (old res drawn, while new res is added to the buffer) or "dirty writes" to the frame-buffer.

Maybe there are even multiple bugs "interconnected" with each other and thus produce issues (I believe it could be due to the different ways you can crash the System.).

I could be totally off the way, but I'm usually good at what I'm doing (and I seriously think it is related to the frame-buffer). :cyclops:
[Galaxy Tab 10.1 Android Development] pitpit24:
Truly? If the app is not working, use the website... I find it more convenient then using an app to navigate on a forum...
[Galaxy Tab 10.1 Android Development] SystemDoctor:
I don't know why but in the middle of the process my p4 has shut down unexpectdedly and won't turn on.

Also, I installed this rom and YourZGapps 4.3 and I seem to be getting Setup WIzard has stopped alot.

NOTE: I always wipe /sdcard after installing any rom, Is this the problem?
[Galaxy Tab 10.1 Android Development] rogconnect:
I don't why you install a old gapps for 4.3 on KK 4.4.2 too.
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Oops, I meant 4.4, I tried using PA GApps but still, Setup Wizard Crashes like usual
[Galaxy Tab 10.1 Android Development] biggiebro:
I tried a number of gapps but only core gapps work. So after trying few time i use banks core gapp. The standard version of any gapp do not work
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Have a link?
[Galaxy Tab 10.1 Android Development] biggiebro:
http://xdaforums.com/showthread.php?t=2560364
[Galaxy Tab 10.1 Android Development] SystemDoctor:
Still doesn't work, I'll try redoqnloading the rom itself
[Galaxy Tab 10.1 Android Development] TRSHD:
Well that's my issue, Odin doesn't allow me to install the recovery...
[Galaxy Tab 10.1 Android Development] EvgeniX:
where I can download this ROM?
[Galaxy Tab 10.1 Android Development] kasper_h:
I updated OP.

I will not be trying you later posted method to crash the tab, as I really need it to work well the coming days :) Anyway, there is still work being done on improving hwcomposer code for older tegra devices. There is now a patch under review for hwcomposer blending of statusbar for example. But I'm now expert on this type of code, so I won't be able to solve any of this.

The thing I do know is that the 12-Jan build, that could not be crashed, did not use hwcomposer for graphical output. This is the reason the 19-Jan build feels much smoother (it has a 100% higher score in Quadrant on graphics).
[Galaxy Tab 10.1 Android Development] eushaun99:
[MENTION=3033992]kasper_h[/MENTION] you should probably put a link to either the banks gapps or PA 0-day gapps in the OP so people won't get confused.
[Galaxy Tab 10.1 Android Development] r0by:
check this post
[Galaxy Tab 10.1 Android Development] biggiebro:
A link to a working GApp as suggested by eushaun99 will save me a lot of time
[Galaxy Tab 10.1 Android Development] kasper_h:
Guess what I just did :) I just added a link to PA 0 day gapps in OP. The reason I never added a link is that gapps packages seem to fluctuate by the day (and I just flashed a very early gapps package the first time I booted the ROM, and never updated it as it is updated automatically anyway).

I also added the advice to flash the ROM, boot the ROM, and then reboot to recovery for flashing gapps/supersu, if the ROM won't boot after wiping and flashing all three packages in a row.
[Galaxy Tab 10.1 Android Development] seven2099:
Where is the link to download the actual ROM?

---------- Post added at 02:29 AM ---------- Previous post was at 02:25 AM ----------

No clue why its not in the OP - but incase anyone is looking for it.

http://rootaxbox.no-ip.org/kasper_h/roms/p4wifi/omni44/
[Galaxy Tab 10.1 Android Development] kasper_h:
Yesterday, i probably accidently removed the link from OP when updating it. Re-added it
[Galaxy Tab 10.1 Android Development] kasper_h:
On my phone, the website is difficult to work on :)
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Even not those which for sure works for others?

Maybe you should do a full Odin - flash before...

Well, there didn't happen any of that sort of problems to me. I just mentioned it, because it is technically possible (atleast during NAND-Writes) so no-one complains...

Ah, so "hwcomposer" is it called, what I was referring with "render engine" to... Thanks for that!

Would you mind linking to the original-files, the fixes and the hwcomposer-blending-fix?

I'm quite used to hardware-near software, Abstractionlayers, etc.

Might be related to a double/triple-buffer, thus the Hardware doesn't have to wait for the frame to be drawn until it pushes the new frame to the main-frame-buffer... It can pre-render them and latency due to "wait-times" should be reduced.

Just a guess "into the blue"... Simply could be a better way of using & utilizing the hardware...

Ah, Btw.: Your opening-post is almost perfect now! :)

Would you mind adding the info, that people should disable "Immersive-Mode" for now (possibly in bold)?
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
Well I meant doing a full-wipe with Odin and an image which includes it all... The OS, the Recovery, original Modem, etc.

Your Partition table could be bugous... This should fix it.
[Galaxy Tab 10.1 Android Development] TRSHD:
Basically, flash the stock firmware? This doesn't change the fact that I can't find a TWRP version that's flashable with Odin...
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
I specifically asked you, if you can flash any other recovery with Odin and AFAIR you either disregarded that or said you can't, thus leading me to the conclusion that your partition - table could be bugous...

I just tried to give you a workaround and I've got the exact same issues before,... The reason was something bugous on NAND, probably the partition-table being corrupted and I got it fixed by reflashing the Tab with Odin "fully".
[Galaxy Tab 10.1 Android Development] SystemDoctor:
So as far as I know if you forgot your device's lockscreen pattern you can remove it by using your GMail Account but know I can't seem to do that can anyone help me?
[Galaxy Tab 10.1 Android Development] eushaun99:
There's none. What's so difficult with flashing a zip?
[Galaxy Tab 10.1 Android Development] bert73:
Bootloop

I tried to do a clean install: tried twrp 260 263 several gapps: bootloop. Then i did a reboot between rom and gapps: stuck in welcome screen.

At last i did a dirty flash: noproblem at all ?????
[Galaxy Tab 10.1 Android Development] kasper_h:
I have added the immersive-mode-risk to OP. In bold :)

Anyways, the 19-Jan build contains this patch to activate hwcomposer:

https://gerrit.omnirom.org/#/c/4492/16

After that, I merged these two patches:

https://gerrit.omnirom.org/#/c/4988/

https://gerrit.omnirom.org/#/c/4989/

(this is not part of a released ROM, but is present in my current test ROM).

After that I tried to reproduce the crash using your method posted yesterday, but I was unable to crash the system....I will upload this testbuild tonight so you can also test whether it works fine for you.
[Galaxy Tab 10.1 Android Development] TnA.Plastic:
THX! :)

Ah, the second patchset(s) seem to address the issue, cool! :)

Not sure yet how well it is implemented, since it's a bit much to read in 2 minutes.

Hm,... Even thought I've got a 3G-P4, I will test it nevertheless... I hope I don't need to "full wipe" (don't want to wipe data).

Hope it doesn't cause issues with my system-settings...
[Galaxy Tab 10.1 Android Development] mahalong:
how to change tablet UI????:D
[Galaxy Tab 10.1 Android Development] kasper_h:
Just do a backup before testing, so you always can return :)

No time to build anything in the next 48h, so no p4 build in next days.

Not possible.

Verstuurd van mijn Nexus 5
[Galaxy Tab 10.1 Android Development] TabGuy:
Do we see any chance of getting bluetooth speaker connectivity working? If not I'll have to regress and go back to CM.

.
[Galaxy Tab 10.1 Android Development] mrbubba999:
A few pages back someone mentioned Netflix still crashed, is that still the case with the latest?
[Galaxy Tab 10.1 Android Development] eushaun99:
Refer to OP under 'tips'.
[Galaxy Tab 10.1 Android Development] pitpit24:
But you are not on a phone, as said in your signature...
[Galaxy Tab 10.1 Android Development] kasper_h:
The message referred to was posted with Nexus 5 :)

Anyway, enough off topic.

Here is a testbuild:

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

Should solve the issues with hwcomposer
[Galaxy Tab 10.1 Android Development] TRSHD:
Well, Odin only allows me to flash either a .tar, .md5 or .pit file. Impossible to select a .zip.
[Galaxy Tab 10.1 Android Development] eushaun99:
Then flash it in recovery. Or Odin flash cwm first then flash twrp in recovery.
[Galaxy Tab 10.1 Android Development] alexkno:
Yes, but if it's a zip then very likely it's supposed to be flashed via recovery.