yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] TheMorpheus:
I'm just having the white screen issue for the first time... It bad and I don't know how to make it go away :(

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] phearus:
On the subject of the screen-issues... It may be worth looking at the code for the Note 10.1 LTE version of CyanogenMod 11, see here: http://xdaforums.com/showthread.php?t=2523728 - this is assuming of course that it uses the same stuff, in the same places, as our devices - sans the LTE radio of course.
[Galaxy Note 10.1 Android Development] TheMorpheus:
Also they have a working 4.4.2 rom http://xdaforums.com/showthread.php?t=2151873

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] iofthestorm:
Ugh, not having my tablet is proving to be surprisingly frustrating; I have way more free time than I expected during this trip.

Can someone run "ls /dev/input" and "ls /dev/input/by-path" in a terminal and report back what it says? Just trying to figure out why this weird workaround is needed to ignore the keyboard dock when it's not actually connected - this causes the software keyboard to not show up because it thinks there's a physical keyboard. I think the Omni merge guys don't want to merge the hack if there's a proper fix possible.

Also, does anyone actually have a keyboard dock? I think I need to fix Samsung's dock driver but I can't really do it without having the dock to test with... obviously I can do lots of things to disable it but then I might break it for the two people who actually have it lol.
[Galaxy Note 10.1 Android Development] jeremiahEJ54:
This is what I got. I don't have a dock, so I'm no help with that

u0_a310@GT-N8013:/ $ ls dev/input

event0

event1

event2

event3

event4

event5

event6

event7

mice

mouse0

u0_a310@GT-N8013:/ $ ls /dev/input/by-path

/dev/input/by-path: No such file or directory
[Galaxy Note 10.1 Android Development] twistedsixty4:
Find the right forum for this question, your post doesn't not belong here, also please go read the rules for xda before posting.
[Galaxy Note 10.1 Android Development] TheMorpheus:
With the last PhilZ Touch 6.07.8 the Sdcard works, you have to mount it manually from the Mount & Storage menu

Here 's the link: http://goo.gl/PIZOL5
[Galaxy Note 10.1 Android Development] Akeel1994:
is it possible to update the rom ota?
[Galaxy Note 10.1 Android Development] TheMorpheus:
I found a new bug: I've tried to play with Real Racing 3 but the audio is messed up!

https://dl.dropboxusercontent.com/u/6359460/VID_20131229_022438.mp4

Log: https://db.tt/FC9phmQa
[Galaxy Note 10.1 Android Development] *d1000:
Just advising I had the screen issue for the first time with the 20131225 ROM but have not seen it on the 20131227. Screen rotation is not working at all in the latest and tablet needs to be held in portait (speakers at top and bottom when facing)...N8010
[Galaxy Note 10.1 Android Development] kkae70:
:good:This rom is good and very nice.

I found some problem

,the monitor is flashing everytime...pls help me.

..

Thanks

(sorry for my bad english):(
[Galaxy Note 10.1 Android Development] iofthestorm:
Not until there are official nightlies. Technically I could set up the needed file structure on my own server and modify the OpenDelta app but it's too much hassle for my relatively infrequent builds, and hopefully we'd get official builds sooner than later anyway.
[Galaxy Note 10.1 Android Development] planetf1:
Has anyone had screen issues with the x27 build? I'm on 25 and getting it around once a day.

So love this ROM otherwise! Its definitely very snappy (I'm experimenting with using art)
[Galaxy Note 10.1 Android Development] Kidromulous:
Yes
[Galaxy Note 10.1 Android Development] Kidromulous:
I was pm'd the answer by someone helpful but thanks anyway for your kindly worded suggestion
[Galaxy Note 10.1 Android Development] riggs170:
Haven't had any screen issues on the 25th build, been using for two days now.
[Galaxy Note 10.1 Android Development] riggs170:
Guess I shouldn't have said anything, it just happened. I wasn't able to open kmsg but I will try something different.
[Galaxy Note 10.1 Android Development] iofthestorm:
Considering that i still haven't found the root cause of the screen issues, I'd be very (pleasantly) surprised if they went away. But when I get home in a couple days I will do a build with an older kernel and graphics drivers and see how that looks; my hunch is that that'll fix it so I'll probably upload that build here but it wouldn't be a permanent fix since we don't want to hold back development. The neat thing is Humberos seems to be back (he's been committing on GitHub again) so maybe at some point he'll be able to take a look.
[Galaxy Note 10.1 Android Development] electrikjesus:
Another thing that might be worth taking a look at is what the IOKP 4.4.2 release is using for a kernel, might save you some trouble :)
[Galaxy Note 10.1 Android Development] TheMorpheus:
I'm trying IOKP https://www.dropbox.com/s/brjtxn1g755cvsj/2013_12_30_19.57.05.png

Display rotation doesn't work

Mobile Network doesn't work (like my own OmniRom)

I had a reboot after 15 minutes, waiting to see if there is a white display problem

Can I do something useful while I'm with this?

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] iofthestorm:
Would be interesting to see if this has the white screen issue I guess. I can't tell what kernel they're using, I don't see one on their GitHub and I don't know what blobs they're using so I don't know if the problem would be comparable. Though I just found out yesterday CM switched to Mali r3p2 a couple weeks ago so in theory if sbrissen's i925 builds don't have the issue then there might be a fix without moving back to older drivers. I compared his defconfig with my n8013 one last night and I didn't see any differences that appeared relevant but I think he had a couple debug options enabled that I don't have.. When I get back home tomorrow I'll play around a bit more with it. It's just annoying since there isn't really a way to reproduce the problem besides just using it for a long time.
[Galaxy Note 10.1 Android Development] dbodom:
I've had the white screen issue happen multiple times simply unplugging the charger. Its not every time, but seems to be related.
[Galaxy Note 10.1 Android Development] WhitestSand:
+1
[Galaxy Note 10.1 Android Development] iofthestorm:
Yeah, I think you're right. I've definitely noticed it happen more often when pulling it off the charger or sometimes when I turn it on while it's on the charger.

I have had it happen other times too though but it's quite likely that charging aggravates whatever condition it is that causes it.
[Galaxy Note 10.1 Android Development] TheMorpheus:
After 12 hours no sign of the white screen issue and, if you look in their thread, nobody ever had this issue.

I'll switch back to OmniRom... I miss it ;)

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] fuadhdmini:
2nd day with 27thdec build. Every time when I see it start to whitish, I straight away press power button to off display, let it be for few seconds then press back power button and walla! Whitish gone. So far this is my temporary solution :D

---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------

Forgot to thanks OP for this awesome rom. :thumbup:
[Galaxy Note 10.1 Android Development] tsukaza:
I do get the white screen once in a while, but the ROM is so good that I decided to stay with 4.4.2 build 27 :)
[Galaxy Note 10.1 Android Development] jusliloleme:
I've too have noticed the "white screen" when unplugging from my powered on tablet. The "white screen" soon fades and then I simply press the power button briefly and I'm good to go, as mention by another poster earlier.

On another note (no pun intended), when I power off my 8013 and then plug in the power cord, my 8013 decides it wants to power up. I don't see the standard start-up display, but when I unplug it, that's when I see the white screen (ok, that was kind of redundant).

It isn't really a deal killer and I'm very happy with this ROM. I'm sure that these (very minor) issues will be resolved soon.
[Galaxy Note 10.1 Android Development] iofthestorm:
Alright, here's something to try out. Went fishing around comparing my stuff to other 4.4 ROMs for Note 10.1 family devices, and noticed that CM had an updated libUMP.so when they upgraded their blobs to Mali r3p2, so I rebuilt the ROM with that. I honestly only vaguely know what this library does but there's a small chance that this might help with the white screen issue. Anyway, either way we'll find out faster if more people test so here's a couple new builds.

omni-4.4.2-20140101-n8000-HOMEMADE.zip

omni-4.4.2-20140101-n8013-HOMEMADE.zip

And it seems like CM did upgrade to Mali r3p2 drivers a couple weeks ago so if the problem is with the drivers and/or their configuration, CM should have the same issue unless it's a defconfig difference which would be easy to spot (I went through sbrissen's i925/p4noteltevzw defconfig and didn't see much different besides the stuff for LTE, but a closer look might help).
[Galaxy Note 10.1 Android Development] planetf1:
Thanks. Downloading to try now. Happy new year.
[Galaxy Note 10.1 Android Development] TheMorpheus:
Flashed, testing now!

I've asked if the i925 thread if they experienced a white screen issue and they told me that they never had it!

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] dbodom:
Flashed the latest on my n8013. I'll play with it today and see if the white screen issue still exists.
[Galaxy Note 10.1 Android Development] tsukaza:
Thanks for the new year gift, dling now.
[Galaxy Note 10.1 Android Development] iofthestorm:
Yup, I saw that haha. I actually went there a few hours after you did to ask myself, and then saw that you had already asked. Right now I think i925 is the only Galaxy Note 10.1 variant with an experienced maintainer still working on it so I'll probably be bugging sbrissen a lot in the near future.
[Galaxy Note 10.1 Android Development] Kidromulous:
White screening remains on this new build .
[Galaxy Note 10.1 Android Development] electrikjesus:
After testing it for a few days in dual boot, and switching back to stock based ROM and kernel when the screen became unusable, I can report that it did eventually go away with continuous usage on stock, but I never was able to get it to clear up while using omni. I just read the updates about being linked to usage while plugged I'd or unplugging, so I can test a bit more. I'll have to make a new image file of the update from last night and test with that too. I have to admit that when I am running this ROM, its speedy, stable, and I love the split view feature. I have no doubt that you will get to the root of the issue here.
[Galaxy Note 10.1 Android Development] iofthestorm:
Damn it, well it was worth a try I guess.
[Galaxy Note 10.1 Android Development] phearus:
OK, so I just did a google-search for android white screen, and came across a few interesting things...

Apologies if these have been mentioned / tested / though-of, already.

1. This: http://stackoverflow.com/questions/...app-it-shows-a-white-screen-for-a-few-seconds

Which makes me think that maybe the issue is no so much to do with our device and drivers, as it is to do with OmniROM's unfinished multi-split-screen thing. Maybe.

Do a build without-it / disabled, or whatever, so we can at least cross it off the list of possible causes.

2. Home screen / launcher related problems - test with different launchers.

3. Auto-brightness. Worth tinkering with.
[Galaxy Note 10.1 Android Development] DesignGrits:
So I haven't been following this thread very well. But I have been on this rom since it started. What white screen are you guys talking about? I am on the latest build but haven't flashed the latest test build the op posted yesterday.
[Galaxy Note 10.1 Android Development] jusliloleme:
Not to be an ass or anything, but why not expend a few minutes and go through the thread for the past few days and see what's been discussed?
[Galaxy Note 10.1 Android Development] phearus:
OK - so you obviously haven't seen it.

This is also interesting.

Please let us know here ALL your settings (yeah I know - tough ask - maybe just what you have "tweaked" from default) and what Gapps, and anything else, like battery-saving, app-killing, launcher apps, etc, apps you have installed.

This would be very helpful in terms of figuring out the culprit to this white-screen bug.

Has anyone managed to get a logcat after / during a white screen episode? This definitely seems like something worth looking into further.
[Galaxy Note 10.1 Android Development] golcheck:
Can confirm that cm11 has the same issue on n801x
[Galaxy Note 10.1 Android Development] DesignGrits:
Well, forget everything I said....I am by no means on the latest build. I thought there was a couple test builds that were released but I didn't know that a official builds were released. I'm still on build 20131214 with PA Full 4.4 gapps. Sorry for the confusion.

Rom: Omni Build 20131214

Gapps: PA Gapps Full 4.4

Kernel: Whatever came with Omni: 3.0.64-CM-00089-ge890f2d Date: Sat Dec 14
[Galaxy Note 10.1 Android Development] iofthestorm:
I've taken several log cats and dmesg logs during and after such episodes, haven't been able to find anything that looks like a problem so far unfortunately. The thing I'm wondering about is that there are roughly 500 downloads of each build I upload usually, and only about 20 people commenting most of the time. I wonder if it's actually really rare and only the people who have the issue are commenting? And I seem to get it somewhat unfrequently but some people seem to have it happen constantly. I also wonder if this is why sbrissen hadn't seen it, it may just be a rare issue with some hardware that gets aggravated by some drivers or something.

One thing to note is that there are actually two graphical issues, probably related, that have cropped up on this ROM. One of them is the screen slowly turning white after waking up from sleep (or sometimes just waking up white), and the other is the edges turning dark and then sort of "burning in" the image that was in the corners for a few minutes. There's also a flickering issue I've seen that's usually followed by the white screen effect.
[Galaxy Note 10.1 Android Development] iofthestorm:
Wait, official builds? There shouldn't be official builds, at least not from my work. I have talked to them a few times about it and there are still some issues I need to sort out that I haven't gotten the time for yet.
[Galaxy Note 10.1 Android Development] DesignGrits:
I didn't mean official as in official builds...I mean't your releases vs the test builds you post in the thread.
[Galaxy Note 10.1 Android Development] iofthestorm:
Is this your build that you did based off my omni device tree, or an official build? If the problem is with my device trees then it would make sense that CM has the same issue but if someone else has independently done a CM11 bring up with the same result then it's quite possible that it affects all ROMs using Mali r3p2 (and I only keep saying that because I never had this issue with any previous ROM, including my own omni 4.3 builds that I never released, and the main difference I can think of is the updated Mali drivers).
[Galaxy Note 10.1 Android Development] walirasoli:
Hi

Thanks for good rom

How can I save APN setting? There is no save option.
[Galaxy Note 10.1 Android Development] WhitestSand:
Xposed framework doesn't seem to want to install on this ROM, any suggestions?

Awesome ROM Thanks #gnome..
[Galaxy Note 10.1 Android Development] xsoullz:
How to root

i lost my root binary and how to root for this custom rom
[Galaxy Note 10.1 Android Development] dbodom:
This white screen issue is strange. On my n8013 I can create it 9 times out of 10 simply unplugging the charger. I reviewed the system logs and don't see any errors. After much research, it appears the CM releases have suffered from this white screen issue on resume also. On multiple threads they discuss the problem and tie it to heating issues or code problems or ART. I can't see it being a heat issue since with stock ROM's, this does not happen. It only started when I installed Omni ROM. Checking the performance on the ROM, I don't see it overclocked by default, so that shouldn't generate additional heat... I guess. I can't fathom how ART would create the issue. It's a firmware issue of some sort.

This may not be the Mali r3p2 drivers... or it may. Of course, Mali drivers simply render to memory and other drivers pick it up to display it, so is it the Mali kernel driver or something else? The UMP drivers? I noticed a new Mali r4p0 release. Maybe we can try that. I've read that the Mali r3px drivers were buggy....

I'm at a loss. Something's amiss since stock doesn't white out like this.
[Galaxy Note 10.1 Android Development] phearus:
Was that build you are running one of the original ones WITHOUT multi window?

If that is the case, there is a pretty massive clue as to what is causing these issues. If not, then forget I said anything.

The "corner-burn-in" sounds like some sort of display-memory corruption thing - I get similar things on bare-metal microcontroller LCD and led displays when I've ****ed-up my interrupts, and the memory gets corrupted, weird **** gets displayed.

In this case though it sounds like the memory ISNT getting corrupted - it is not getting refreshed with the latest display data.

This does all seem display-driver / some-driver / kernel memory management or interface related.

Has the mali-driver been rolled-back and tested yet? May be worth rolling forward to the new one too - if we get the same results - white-screen and image burn-in - then this may indicate that it isn't the driver, but something directly related at that low level interface.

Sorry for all the blue-sky guessing - I haven't even looked at the code yet - though I am hoping that I inadvertantly trigger a thought-process in [MENTION=3125261]iofthestorm[/MENTION]'s head-computer which leads to a solution.

Aside: I wouldn't take the download-count as any indication of adoption - I have clicked each link dozens of times before getting an actual successful download, let alone flashing them all. ****ty Internet, you see.
[Galaxy Note 10.1 Android Development] DesignGrits:
No multi window on the build I am on.
[Galaxy Note 10.1 Android Development] iofthestorm:
Can't be, I actually never uploaded a build without multiwindow - the first post is kind of misleading that way since I decided not to upload after I wrote it, and never changed that part. I'm fairly certain it has nothing to do with multiwindow, it's just too "analog" looking to be anything that high level IMO.

Ah, that makes more sense re: the download count, though I've never had that issue personally I can imagine it could be inflating the counts. I was surprised that there were that many people using AOSP ROMs on the n8013, let alone this ROM to be honest. It's always been a niche device and most people who buy this seem to want to use the Samsung features.

Haven't rolled back the Mali driver, I got thrown off a bit by the news that CM11 on the i925 didn't have this issue and was using Mali r3p2 but it may just be that the specific set of circumstances that cause it haven't occurred to anyone using it. I'll try rolling out a reverted build now though.

Upgrading the Mali driver is pretty much impossible. I don't think we have the blobs for r4p0, and generally I think vendors customize the drivers from ARM for final devices (eg. the driver code we're using is from a Samsung i9300 kernel source drop, not the ARM source releases) so I'm not sure if that code would even work on any shipping device even if we had the blobs. It seems fairly likely that we might never see r4p0 blobs, since I doubt Samsung will care about updating the Mali drivers for any of the Exynos 4 devices anymore. I don't know if there are any other devices running Mali 400 but even if they are I doubt they'll be getting updates.
[Galaxy Note 10.1 Android Development] iofthestorm:
Huh, where'd you see CM users having this issue? I don't see any CM11 threads for the Note 10.1 besides the i925 version which has no mention of it. But yeah, now that you mention it, I can definitely reliably reproduce it by plugging it in for a while and then unplugging it. That should be very useful, thanks!

Can't be related to ART, I'm not using it.

Stock is not using r3p2, the blob and driver code came from i9300, it's just that all Exynos 4 devices in OmniROM share a kernel (CM does the same I think) because generally they're compatible. If that is indeed the culprit, then it's perfectly sensible that stock or any older ROMs don't have this issue.
[Galaxy Note 10.1 Android Development] DesignGrits:
Interesting, considering I don't recall ever being able to use multi window since I started using this rom. I am well aware how to use it on omni rom. I provided the build version i am using above. Who knows, calling it a night.
[Galaxy Note 10.1 Android Development] phearus:
I think we should start looking elsewhere for blobs and code than the mess Samsung propagate with their releases. Not to say that is a good starting point, but we have other options now - or at least these are open options in development.

Check these devices out:

http://linuxgizmos.com/open-sbc-runs-linux-on-quad-core-exynos-4412/

http://www.hardkernel.com/main/products/prdt_info.php

I'm looking further into these currently - these devices are really cool, make the Rasberry Pi and Beaglebone family look like children's toys, and most interesting of all, are based on our Exynos devices. Things are going to advance for our hardware, and it will be through these devices that it happens. At least I hope I am right about this.

Worth keeping an eye on anyway.
[Galaxy Note 10.1 Android Development] iofthestorm:
Weird. Yeah I need to go to sleep too lol.

I think people have tried this in the past, but I think the problem is that Samsung hacks up the drivers for their devices and so dev board drivers have never worked on actual products. I think part of what Geecko was trying to do by upgrading Mali was to bring our drivers more in line with dev boards so that we could use the hwcomposer they use, or something like that, but he's not there yet. I think overall it seems like a lot of pain for just a potential chance of improvement and lots of potential for regressions.

Anyway, I've done a build with Mali r3p1 blobs and kernel from before the r3p2 import, and it at least boots and runs kind of fine on my tablet so I'll upload it here so people can test. Just n8013 for now, gotta sleep.

Edit: Here's a build with Mali r3p1 for n8013. Especially those of you with a lot of graphical issues, I'd be curious to see if you could try it out and see if it resolves them. My initial test of the pulling it off the charger behavior seem to not trigger the white screen thing so it may be gone, who knows.

omni-4.4.2-20140102-n8013-MaliRevert.zip
[Galaxy Note 10.1 Android Development] dbodom:
Installing now. Will test and let you know.
[Galaxy Note 10.1 Android Development] dbodom:
I've been testing the backlevel Mali release and I can't seem to recreate the white screen issue. I've only been playing with it for an hour or so, but I was consistently getting a white screen when unplugging the cable yesterday.

I'll keep at it today and see if this fixed our white screen issue. I haven't seen any of the edge ghosting either... so far.
[Galaxy Note 10.1 Android Development] iofthestorm:
Out of curiosity, did you ever see the the edge ghosting before? I forgot if that was something only I saw. There is one little problem that my tablet has additional glitches because I think the LCD cable is loose - I fixed it once by taking it apart and plugging the cable back in but it seems to have gotten loose again so I guess I'm gonna need to do it again. In the beginning I thought the glitches were from that but then other people started having them.
[Galaxy Note 10.1 Android Development] dbodom:
I had both issues - white screen on resume and edge ghosting. So far, the tablet seems to be okay, but let me continue to use it, and charge it, and see what happens.