yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] sudisk:
Thanks for the tip.

I'm at work now so I'll try that tonight :)

You should be awake when I get home (9h delta makes long discussions even longer :D )
[Galaxy Note 10.1 Android Development] chappatti:
My 'Performance' setting shows CPU 1 & 2 offline. And running at 200mhz.:confused::confused: Need to wait for a kernel or something??? Or should I just ignore it for now...

Or is it just me ?????

Thanks for any input!
[Galaxy Note 10.1 Android Development] iofthestorm:
To be honest I don't think performance settings work yet, not sure why though.
[Galaxy Note 10.1 Android Development] :
On 12/3 build now. I'm noticing that my tablet won't wake up from deep sleep. Anyone else have this?

Just fyi, if you hold the power button in for 5 seconds or so, the tablet will restart.
[Galaxy Note 10.1 Android Development] iofthestorm:
I'm not seeing this, can you try and get a logcat when it happens? Like, connect via USB to your computer and see if adb logcat does anything, that might reveal what's preventing your tablet from waking. Does this happen all the time, or just some times?
[Galaxy Note 10.1 Android Development] manxexile:
Thank you

First let me thank you #Iof for the ROM.

FYI; I initially tried to install via TWRP 2.6.3.0 but was unsuccessful on three occasions so installed the latest Clockwork Mod Recovery using the Root Recovery Tool App and installation went without a hitch, this was topped off by installing the pa_gapps-modular-mini-4.4-20131126-signed.zip

Only glitch so far that I have noticed is that WiFi is reluctant to change automatically from 2.4GHz to 5GHz and vice versa. Otherwise all seems tickety boo!
[Galaxy Note 10.1 Android Development] chappatti:
Are you getting the build from Omni.org? Or has iofthestorm updated something!!

How would you flash the nightlies over a current omni on the n8013?

Thanks for any help!

Update: Never mind, I got it now!! :laugh:
[Galaxy Note 10.1 Android Development] :
Wish I could but I can't find my stock charger (with USB) anywhere! Need to buy a new one. I've only had it happen after the tablet is sitting a sleep for more than a few minutes.

I'm gonna try wiping and flashing again... Last time I dirty flashed
[Galaxy Note 10.1 Android Development] iofthestorm:
Did you try the recovery I posted, or the one from TWRP's site? The issue is that the TWRP guys just have not updated the one for n8013 for a while so it's not compatible with Kitkat based ROMs due to SELinux. That's why my build is just labeled as 2.6.3.x because it's not an official release.

Yeah, we don't have nightlies yet. I submitted the required information to them but I don't know when it'll go through, as they have a lot of stuff to work on. Anyway, I don't mind doing my own builds and will probably keep releasing them after nightlies as well so that people can try out stuff that's more work in progress. I'll post a new reply here and update the OP and the changelog post when I do so. To flash a new build, just flash it over the old one, no data wipe necessary.

Ah, yeah I had a third party cable which didn't work well for adb so I ended up having to buy an OEM cable a few weeks ago.

Clean flashing should not be necessary, however doing so can isolate whether the problem is due to the ROM or some misbehaving application. In general though it's perfectly fine to flash new versions without wiping data unless otherwise noted.
[Galaxy Note 10.1 Android Development] :
I think it was probably a misbehaving application... Wiped, reflashed and now everything is fine.
[Galaxy Note 10.1 Android Development] iofthestorm:
Good to hear. Have you ever experienced the weird white screen of doom? Someone else mentioned that they had it happen to them, and I was wondering if that was what you were experiencing. Like for me, occasionally when I wake my tablet I'll get a white screen, sometimes with weird fading on the corners. But when I went to logcat it it magically fixed itself :(. Really curious what it is. Entropy512 said in another thread that it'd be very hard to actually damage the LCD so we probably don't need to worry about that but it's still a bug that should be fixed.

By the way, it looks like the clock being cut off was fixed, I'm guessing I just picked a bad time to repo sync when I did my first build. There's an interesting option to add backgrounds based on the time of day to the clock display; personally I think it looks a little weird right now but it could be cool, but I think maybe I just merged at a time when there was some work in progress for that which was fixed later.
[Galaxy Note 10.1 Android Development] :
Alright so I got it again. Its like the backlight is on but LCD pixels are some form of white or gray. Here is a log cat I tried to get using an apk called catlog https://www.dropbox.com/s/hpzsc6de2jirjkp/logcat_and_device_info.zip catlog should have been recording while the screen was haywire

---------- Post added at 10:45 PM ---------- Previous post was at 10:37 PM ----------

I think W.S.O.D was occurring around 15:25

---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------

15:25:14 ... There are some errors about LED 's
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh nice, that should be useful! Yeah, the thing that happens to me sounds the same, mostly white with some weird grays. That's annoying then, I guess we'll need to figure out why that's happening.

I haven't looked at the logs but I know that the configuration for the Torch app is messed up currently, so that might be what the LED messages are referring to. I've actually fixed it so that Torch works locally but I have other random debugging crap in my build so I didn't want to upload that.

Either that or notification LED maybe which we don't have. I doubt LED refers to the screen but I could be wrong.
[Galaxy Note 10.1 Android Development] :
Sounds good. Thanks for looking into it!
[Galaxy Note 10.1 Android Development] chappatti:
I see the white screen - but not of doom, because in 1-2 secs the screen comes back. It is not pure white or such, but just black screen with a white hue. It started only with KitKat. I would guess I am luckier than you that I do not have the doom part!! :angel:
[Galaxy Note 10.1 Android Development] iofthestorm:
Actually, it might be the same thing for me, as the last time it happened it went away a few minutes later. But before it wouldn't go away until I rebooted. I guess it's fairly likely that it's a side effect of the Mali r3p2 drivers because this is probably the only ROM on n8013 using them as far as I know.

[MENTION=591147]Entropy512[/MENTION], if you've got the time, any ideas?

Edit: actually, I guess you haven't worked on Exynos devices recently, who should I bug instead? Rebellos or xplodwild or something?
[Galaxy Note 10.1 Android Development] chappatti:
Yup, it sounds like a graphics glitch on this. But is version/ROM specific.
[Galaxy Note 10.1 Android Development] phearus:
You could bug [MENTION=3031478]humberos[/MENTION] (Humberto - you can thank me later ;)); he is an n80xx ninja.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh yeah, I was hoping for a while he would do an Omni port but he seemed to have disappeared so eventually I got tired of waiting and did it myself. It'd be good to have him take a look.

Ugh, got the weird persistence thing again. It looks like this: https://www.dropbox.com/sc/m6zr1tikx2jfoq6/liDslmpS5B

Has anyone else had this happen? I think it's related to the white screen problem but I'm not sure, since no one else has mentioned this kind of thing specifically (having previous screens persist in the corners).
[Galaxy Note 10.1 Android Development] chappatti:
Your best bet is to flash a stock JB 4.1. If it goes away it is KitKat causing it.

UPDATE: Ok, I looked very carefully at your image #3. And that IS image persistence. A quick search on xda suggests this to be a relatively common issue. see for e.g. this post (nd many others liek this). Apparently, IPS and AMOLED screens do this sometimes.

http://xdaforums.com/showthread.php?t=1697876

I now also clearly remember my Asus Tranformer that had a bright-ish screen had a burn in of my soft keyboard a few times when I used to use it. It was surprisingly dependent which sof keyboard I installed !! I remember taht quite clearly. So I would say that you can download the app suggested and "erase" the persistence.
[Galaxy Note 10.1 Android Development] chappatti:
Dirty flash OK? Or must clean wipe to install...?

Thanks!
[Galaxy Note 10.1 Android Development] ytain:
There's a problem with bluetooth, it seems that it can accept bluetooth keyboards, but not bluetooth mouse.

I've tried many ways to connect my old Logitech Bluetooth Travel Mouse V270 to my tablet (N8010), tried to pair it to no avail. OmniROM won't accept it, but it shows it in the list.

Here is the pastebin of the log for bluetooth events http://pastebin.com/PthKifE0

The bluetooth id for the mouse is 00:07:61:6a:77:ba.

Can anyone else confirm if your bluetooth mouse works with OmniROM from Jan 17 2014?

The mouse connected and paired quickly before on stock 4.1.2 and RevoltJB 4.3.1.

Ytain
[Galaxy Note 10.1 Android Development] planetf1:
Latest 8013 twrp & omnirom installed here on my n8010 - working great. Previously had the last build, so no wipe etc.

Obviously not used for long yet, but I do love how fast and solid the rom is! Using ART too.
[Galaxy Note 10.1 Android Development] iofthestorm:
Dirty flash is always okay unless specifically mentioned otherwise, but I don't find it likely that we would break backwards compatibility like that except for extraordinary circumstances (eg. if it was a matter of security).
[Galaxy Note 10.1 Android Development] iofthestorm:
I know you haven't said anything, but just to make it clear for anyone else, ART is highly experimental and if you experience issues when using it you should first switch back to Dalvik and see if they remain. As of now no one supports the use of ART, including Google, it's primarily there so that developers can update their apps if necessary.
[Galaxy Note 10.1 Android Development] planetf1:
Of course, a very prudent reminder

I admit I was expecting more issues with it... Also have an s4 i9505, but samsung have hidden/removed the art option. Not a surprise as it's targetted at mass consumer market.
[Galaxy Note 10.1 Android Development] xrage28:
Installed it today and it runs very smooth on my 8010 .

Thanx for it !!!
[Galaxy Note 10.1 Android Development] tabtxk:
I'm still confused, i don't get any error flashing in philz. also n8010, but n8013 version of philz. the n8010 version is old (5.15.0).and not usable for kitkat, don't try it. If you want to try latest n8013 use the link in philz main-thread -> http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n8013, i just realized that the one in the note10.1 forum here is kinda old. (Might have to flash it (first time) through odin).

Anyways, gonna flash your recovery and latest build now.

Thanks ;)
[Galaxy Note 10.1 Android Development] iofthestorm:
If you use a recovery for n8013 your tablet will identify as such for installation purposes, so you will be able to flash n8013 ROMs without issue. The goal of the n801x version was to allow flashing on n8010 (I.e. recoveries identifying themselves as n8010) but if there is no up to date recovery for n8010 that's kind of a moot point. Still, I guess it's easier for people to understand that the same build works for two devices that way.
[Galaxy Note 10.1 Android Development] artyfarty:
Thanks! Found the way. "put aside"

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy Note 10.1 Android Development] gravis_jg:
Hi all

I need little help ... how to flash .img file ?

Im using Phill Touch right now and I know how to flash tar file but .img ...hmmm

anyway this is great omni rom Im very appreciate

hawk

never mind - Ive manged... :)
[Galaxy Note 10.1 Android Development] claytonjn:
I just tested the 1/17 and 1/28 builds and have zero issued with my bluetooth mouse. Maybe an app is interfering?
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah, I thought I had it in the OP but looks like it wasn't there (updated the OP now). Anyway you can use Recovery Tools from your device to flash a recovery, or Mobile Odin if you've got it.
[Galaxy Note 10.1 Android Development] gravis_jg:
Recovery Tool take good care of .img but Mobile Odin ? only .tar I think ... or maybe Im wrong ...hmmm

Thanks anyway - its all fine now
[Galaxy Note 10.1 Android Development] iofthestorm:
I always use Mobile Odin, although I think it may require the file to be called recovery.img, not sure. But recovery tools is free so it's easier to recommend anyway. Haven't actually used it myself though.
[Galaxy Note 10.1 Android Development] mtoneman:
Answering my own question here, hut just flashed the 1/28 build and the Netflix issue is solved. No more stutters and it looks like it goes to "full resolution" a lot quicker than before.

Thanks!
[Galaxy Note 10.1 Android Development] direwolf1:
Thanks for the awesome ROM. So glad to be running KitKat on my N8013. Sorry if I'm missing an obvious setting somewhere, but is there a way to get dual pane settings?
[Galaxy Note 10.1 Android Development] Jiggs82:
Unfortunately they took it out in KitKat
[Galaxy Note 10.1 Android Development] ©h®is:
i use recovery tools and i can recommend it
[Galaxy Note 10.1 Android Development] easyguy:
Thanks for fixing the recovery and also updating this ROM.

I thought development for this device was dead, now this bring excitement back into the device.
[Galaxy Note 10.1 Android Development] ytain:
The OmniROM from Jan 27 is slightly worse cosmetically than the Jan 17.

I still cannot connect to my bluetooth mouse to pair with it.
[Galaxy Note 10.1 Android Development] roywheels:
Pressing the recent apps and holding one of the app icons will put you into multi-window mode. Is that what you were looking for?

What does that even mean? Lol. :silly:
[Galaxy Note 10.1 Android Development] artyfarty:
Someone have problems with stock Sammy earphones? My microphone don't works, even if it works with sgs3

Inviato dal mio GT-N8000 utilizzando Tapatalk
[Galaxy Note 10.1 Android Development] FPtje:
Settings app Crash: go to settings, security, set lockscreen to off, try to reopen settings, security.

I can't give you a logcat atm, but you should be able to reproduce it.
[Galaxy Note 10.1 Android Development] iofthestorm:
There was a fix floating around this forum somewhere, sorry I'm on my phone or I'd find it for you. Basically you need to replace an audio configuration file. If we can figure out whether it actually works I can submit it for review.
[Galaxy Note 10.1 Android Development] artyfarty:
maybe this?

http://xdaforums.com/showthread.php?t=2579637

i will try tonight, I am at work now.

thanks!
[Galaxy Note 10.1 Android Development] ytain:
The OmniROM for N801X released on Jan 27 has more issues. It keeps the CPU temperature around 70°C and it feels laggy when scrolling the listviews. It occurs whenever I did dirty flashing or clean flashing (total wipe before flashing). Going back to Jan 17 release returns it to normal.

The Jan 27 release has glitches in the UI part:

- after powering on or rebooting the device, it gives briefly a black screen for one second when showing the first screen after the lockscreen step (doesn't occur on previous releases)

- three apps I use are positioned in a glitchy way on the screen: 'Micro CPU Monitor', 'Network Monitor Mini Pro' and 'Status Bar Mini' screen positions I set are respected for the first 5 minutes, then after they are shifted elsewhere. (Doesn't happen in the previous releases).
[Galaxy Note 10.1 Android Development] claytonjn:
Hey, I was finally able to get a logcat, here: http://l.bitcasa.com/JlDS2bOE

I used the -v long flags so there's a ton of stuff in it, but the last thing in the log is this:

[ 01-29 12:20:52.630 2236: 2236 I/DockObserver ]

Dock state changed: 1

Here's the dmesg: http://l.bitcasa.com/udQUdDZ-

It doesn't seem like a lot to go on really. Interestingly, the same behavior occurs whether the dock is plugged in to power or not. It occurs about 90% of the time when docked. I haven't been able to figure out a pattern or any reproducible method for when it does/doesn't occur. My hunch is that it's a kernel issue since it appears everything just stops functioning, the screen freezes, and after a few seconds it just turns off. If you can think of anything else I could do to try to troubleshoot let me know...
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah no, I meant in this subforum. Found it here: http://xdaforums.com/showthread.php?t=2568787
[Galaxy Note 10.1 Android Development] mtoneman:
I have a n8010 an on both the 17/1 and 28/1 builds have this problem with me. If I pause or switch to another app using audio I have to unplug an re-insert the headphones to get sound again. Happens on Netflix, Spotify, Google Music etc...
[Galaxy Note 10.1 Android Development] planetf1:
Oddly I'm not getting this issue with the Jan 27 build... Great battery life, running cool. Cpu at 200MHz though Interestingly despite not touching governor, one core is stuck offline

---------- Post added at 12:10 AM ---------- Previous post was at 12:08 AM ----------

If no one else sees the core issue I wonder if it's gone bad...?
[Galaxy Note 10.1 Android Development] claytonjn:
Now that you mention it, Trickster shows Core 1 always offline for me too.

-Sent from My Galaxy Note 10.1 using Tapatalk
[Galaxy Note 10.1 Android Development] iofthestorm:
I've seen this happen sometimes, not really sure what the deal is. I guess hotplugging is kinda weird, I've seen oftentimes that all my cores sit at 200mhz but nothing gets disabled either. I think Qualcomm's hotplug implementation might just be a lot better than everyone else's. Might be a bug in the kernel or the governors though.
[Galaxy Note 10.1 Android Development] iofthestorm:
That is really extreme, could you try and get a logcat and dmesg? I don't see how that could possibly happen, it's most likely a misbehaving app or something. 70C should make your tablet hot to the touch O_O. I don't think anyone else is having this problem.

By the way, as a general reference, to get dmesg output you need to be running as root (so eg. run "su" in terminal or make sure running adb as root is checked in settings).
[Galaxy Note 10.1 Android Development] claytonjn:
I didn't see a setting for running adb as root so I just ran it in a terminal emulator. I would have figured it out earlier but it took me 30 minutes to realize that adb wasn't working because I hadn't updated the SDK past 4.2.2 and I was running late for class. Anyways, I included the link for the dmesg along with the link for the logcat in the previous post. Let me know if there's anything else I could do.
[Galaxy Note 10.1 Android Development] chappatti:
I can confirm the following: CPU temp is at 90F, battery temp is at 72F, and one core is always reported as "stopped"...

DOH! In my case it is in °F so not much worry here. = 33°C...

But core is offline.
[Galaxy Note 10.1 Android Development] TheMorpheus:
I've been able to build Omni for N8000 :laugh:

I enjoy try new stuff so in my build you'll find some cherry-pick but that means that the rom could be unstable.

My last one has Navigation bar customization (just merged), Upgrade network traffic meter and Disable safe headset volume warning(cherry-pick). Now I'm trying to add Multiwindow PS 18 (I've tried last patch but right now is useless)

Here's the link: http://d-h.st/PLe

P.S.

Follow me on G+ for new build
[Galaxy Note 10.1 Android Development] TheMorpheus:
Duble post

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] rtunru:
Switching from front to back camera

.. still caused my N8010 to crash :(
[Galaxy Note 10.1 Android Development] cyrilobasuyi:
CWM Recovery by S.A.M.E.R.D

Hey, don't know if anybody tried flash in over SAMERDs latest cwm recovery. I flashed the Jan 17build over that when i had issues with TWRP(kept reading my N8000 as N8013. N so far its been smooth..just thinking aloud though...maybe TWRP isn't the only recovery compatible with this..

Hey and iofthestorm good job on the ROM. Nice buttery feel.
[Galaxy Note 10.1 Android Development] MontanAndroid:
Rom 2014-01-28

Just installed the 1-28 ROM, confirmed on my 8013.

Switching from front to back camera forces hard reboot.
[Galaxy Note 10.1 Android Development] ytain:
The hard reboot caused by the switching cameras in Camera app found in OmniROM is an old issue coming from CyanogenMod builds. I think the Camera app (which is based on the Focal camera app developed by the guy who founded OmniROM along with others) is not initializing/freeing the camera correctly.

There's Camera360 app which works perfectly. ( https://play.google.com/store/apps/details?id=vStudio.Android.Camera360 )

Ytain
[Galaxy Note 10.1 Android Development] bavmouse:
3G ist not working here.
[Galaxy Note 10.1 Android Development] jelinek.01:
Another minority user with dock

Sorry for bringing it back again, but what about the dock keyboard?

It seems that i'm the third person who would very much like to use the dock - I was used to use Tasker with Samsung dock plugin and secure settings for switching between External keyboard helper Pro and my favorite Hacker's keyboard (I had the Samsung keyboard frozen on the stock FW to block it interfering, I'm rooted).

It was very nicely working setup, but now I can't use the dock even as oversized charge stand, the tablet freezes completely when inserted in dock and reboots itself almost instantly. I've found in this thread that the keyboard driver is disabled because of interferring with soft keyboard (blocking it) - is it possible to enable it somehow?

Can I do something to help fixing it?

Everithing other seems very nice (just missing the tabletUI), my favorite function is the screen expansion.

Thanks!
[Galaxy Note 10.1 Android Development] iofthestorm:
Ohhhh, I didn't realize the others were talking about the keyboard dock. Well, I guess Entropy512 didn't want to include a hack which forces the soft keyboard because basically the keyboard dock driver reports as being present even when it's not. The better solution would be to fix the driver so that it correctly reports the presence or absence of a keyboard, but since no developers have it we can't fix it, and we assumed few users have it so we decided not to merge the hack. But now several users are reporting that they do have it (across a few Samsung tablets) so we may be able to reverse that decision. Alternatively we could try to fix the driver now but it would be hard to do it blind. But I can certainly put the hack back into my builds, and maybe if I can get a log from you guys using the dock I can try to figure out what code paths it's going through when the dock is actually inserted and removed. But right now I'm pretty busy with school, but on the weekend I can roll up another build for you to play with. I can't promise anything in terms of finding a more permanent fix, but at the least you'll have a more up to date build to use.
[Galaxy Note 10.1 Android Development] jelinek.01:
And how did the stock FW work?

I think it used their Samsung keyboard, which when selected, checked presence of dock and then did or didn't show. That's why for other touch keyboards and selecting other kb layout than Samsung's Czech QWERTZ I had to use the Tasker detection plugin and switch between "ExternalKeyboardHelper" input method and other SW keyboard (I'm quite happy with Hacker's keyboard). So if the forcing of SW keyboard could be conditioned by dock presence, it would work quite nicely.

I get it that the trouble is the detection of real presence of the dock?
[Galaxy Note 10.1 Android Development] artyfarty:
this hack works fine, thanks for the tip!
[Galaxy Note 10.1 Android Development] ©h®is:
Did you had the right apn settings?

You have to add them manually..;)

Gesendet von meinem Nexus 4 mit Tapatalk
[Galaxy Note 10.1 Android Development] bavmouse:
now it works, thank you!
[Galaxy Note 10.1 Android Development] rtunru:
Thank you for the tip.