yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] TheMorpheus:
There you go... This is a fat one, a lot of stuff for you to try! https://plus.google.com/101175765152287198424/posts/XQJaoaDoR6H

If some of you find some problems with one of Cherry-Pick I've included, please report it to me so we can find a fix!

[MENTION=1572963]marco9333[/MENTION] In the next build I'll add this patch so others can test it!

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] claytonjn:
I've seen this too, but it happens for me in portrait or landscape. FWIW, I also run OmniROM nightlies on my S4, with most of the same apps and settings, etc. and don't have this issue.
[Galaxy Note 10.1 Android Development] marco9333:
I've already merged "smdk4412: Provide available freq sysfs for exynos"﻿ in my sources. If you have done a repo sync you don't need to cherry-pick it (It will give you a error maybe).

PS. I've just upload some changes for battery and charger drivers from n8000 update7 sources with specific code for our tablets, give it a look :D
[Galaxy Note 10.1 Android Development] TheMorpheus:
Sure, I'll look into it :)

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] iofthestorm:
There's an option for transparent lock screen, but it should be off by default. Can you guys check whether it's enabled somehow? I've never seen this FYI.
[Galaxy Note 10.1 Android Development] claytonjn:
No, it's not enabled for me. I'm pretty sure every time it's happened my lock screen widgets were also not visible. After unlocking and locking again though its fine. I use pin unlock and the same lock screen widgets on both devices too, if it makes a difference.

-Sent from My Galaxy Note 10.1 using Tapatalk
[Galaxy Note 10.1 Android Development] kokero:
When the update will be available for n8000? :D

A camera fix, and headset functionality on call would be great!

Good ROM, I mean REALLY stable.

Thanks!
[Galaxy Note 10.1 Android Development] jaxxes:
I don't get this on my n8013 but I do on my note 2 running omni. I see it there in conjunction with active notifications though which I don't have running on the n8013. Is not all the time but seems to happen more frequently when I have a notification and go to unlock the phone. Not sure if that helps at all...
[Galaxy Note 10.1 Android Development] marco9333:
Wired headset on call is working properly in latest versions.

About camera someone around here stated that using a third-party camera app won't cause a reboot when switching from front to back
[Galaxy Note 10.1 Android Development] claytonjn:
I read that somewhere else too, but I don't use active notifications on my Note 10.1 either. (Or on my S4 where this doesn't happen, for that matter)
[Galaxy Note 10.1 Android Development] TheMorpheus:
New Build!! :D

Changelog: gerrit.omnirom

Fixed headset mic during call (during the first call audio not working, just start and stop a call before it starts ringing, after that audio will work until next reboot)

Fixed apn missing

Experimental fix for audio on hdmi (untested) please report

Experimental fix for audio on dock (@chappatti reported it's kind of working, audio played from speaker when on dock)

Enabled 3d audio (It's a feature included in our audio chip, it rise the volume both speakers and headphones)

Cherry-Pick:

All in One Animation Control

Blacklist support

Camera enhancements

Lockscreen wallpaper

[WIP] exynos-hotplug: Disable dynamic hotplug when governor is hotplug-aware

[WIP] Multi-window PS18

OmniGears: add new italian traslation

OmniSwitch: Add IT-Translation

Battery Save Mode isn't there because today was broken, it'll be back tomorrow.

I haven't had the time for include [MENTION=1572963]marco9333[/MENTION] new drivers...They will be in tomorrow build.

Download:

omni-4.4.2-n8000-HOMEMADE-21022014@1629.zip

Have fun!!
[Galaxy Note 10.1 Android Development] kokero:
When the "battery changing when turned off bug" will be fixed? Thanks!
[Galaxy Note 10.1 Android Development] tsukaza:
Nice, thx.
[Galaxy Note 10.1 Android Development] kokero:
I use n8000, and the last update was just available ,until now, to n80xx, is this one from TheMorpheus "oficial"? Because there is not any kind of update on the main download page from iofthestorm, when it will be available? Thanks!
[Galaxy Note 10.1 Android Development] direwolf1:
None of the builds here are official (see topic title or read the OP). iofthestorm, TheMorpheus and others are working hard and doing a great job to bring Omni to the Note 10.1, but none of the builds have been given the official Omni stamp of approval (as far as I know). iofthestorm started this thread, and TheMorpheus has been making updates and changes to fix issues on the n8000. My understanding is that this thread is based around iofthestorm's original builds, and he simply hasn't changed the OP to include TheMorpheus's builds.

FWIW, I've been running iofthestorm's builds on my n8013 for weeks now, and they're rock solid with only a few minor issues. Can't speak to TheMorpheus's builds as I don't have an n8000.
[Galaxy Note 10.1 Android Development] kokero:
I know, that's why I putted the word "oficial" into inverted commas. I just wanted to know if TheMorpheus work with iofthestorm (who is the topic creator). I'm not a developer, just an android enthusiast, and I'm currently using those roms on my n8000 since 3 weeks ago, and they are very smooth and stable.

Thanks for the answer, and sorry for expressing myself poorly. :laugh:
[Galaxy Note 10.1 Android Development] iofthestorm:
Basically, you can think of TheMorpheus's builds as equivalent to mine. I decided to stop doing my own n8000 builds since TheMorpheus was doing them anyway and he has the device. Although he likes to cherry pick more stuff than me so in some sense his are farther from official but it's not a big difference.

To be honest, I will probably not post any more n801x builds either if we can get nightlies rolling this weekend. At this point we just need to sort out recovery issues and we'll be good to go. It's annoying for me to put up clean builds when I'm working on something because stuff is often broken in my builds that I run on my own device, which I wouldn't want to release in that state.
[Galaxy Note 10.1 Android Development] kokero:
Nightlies! That's good! Where they will be availabe?

Don't leave the project, I just love your ROM, it is the best I've ever tried on all my devices! Who will continue the protect without you? :(
[Galaxy Note 10.1 Android Development] iofthestorm:
You misunderstood me, lol. When there are official nightlies for n801x there's less of a reason for me to post my own builds here. I'm not going anywhere. But I may still post stuff from time to time that needs testing. When there are official builds they'll be on the main Omni site.

N8000 is a little further from being official because no one is an official maintainer yet, not sure if marco or morpheus want to do it or if they'd be fine with me also being the maintainer for it. I think in general we prefer someone who has the device to do it but I think for other tablets there's one guy maintaining both wifi and 3g. Once we get nightlies running for N801x I'll try to bring up the topic of N8000 with Omni guys but if anyone else wants to do it first then go ahead by all means.
[Galaxy Note 10.1 Android Development] kokero:
Oh lol, OK so I will install Morphenus bluids, and check if there is any nightly available on the omni site time to time. Thanks! Oh and the new boot animation that Morphenus inserted on the new update is so beautiful, it just fits with KitKat!

Thanks again!:victory:
[Galaxy Note 10.1 Android Development] claytonjn:
Once there are nightlies available you'll get an alert right on the tablet letting you know. (Or you can go to Setting>About tablet>System updates)

OmniROM uses the OpenDelta system which means it checks what version you're on, downloads ONLY the things that changed between your version and the newest version, and creates a zip right on your device. Then you simply hit the update button and it will boot into recovery, flash the update, and reboot back into Android all automatically. It's a very awesome system and quite convenient.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh hey, turns out it was indeed a bug which was fixed today. Not sure if I'll do a new build this weekend, gonna try to push on some people to help get nightlies sorted out which will be better for you guys and me. If it doesn't happen I'll put up a new build Sunday night probably.
[Galaxy Note 10.1 Android Development] marco9333:
Are more than one maintainer allowed for a single device tree? If yes, I can be the maintainer,but sometimes I won't be reachable for a week or two so if there is another one too will be better.

PS. I've fixed front to back camera switching, do you know if other devices have this bug?

Edit 2: This is my commit https://gerrit.omnirom.org/#/c/5741/ Can you and [MENTION=1466338]TheMorpheus[/MENTION] cherry-pick this?
[Galaxy Note 10.1 Android Development] TheMorpheus:
Yes, with Camera Zoom FX works!

Yes, no problem! :good:
[Galaxy Note 10.1 Android Development] kokero:
Hey there, I am here to list the bugs and instabilities I've found out until now, I would be glad if it helps!:angel:

1- Sometimes when you try call somebody, headset doesn't works;

2- When you try "record screen" function, the OS crashes;

3- Unable to switch back to main camera on the original camera app;

4- When the user tries to load the tablet without turning it on, distorted green lines appear instead of the battery status.

(Using latest Morpheus update "omni-4.4.2-n8000-HOMEMADE-21022014@1629.zip")

Thanks for the awesome ROM!:laugh:
[Galaxy Note 10.1 Android Development] marco9333:
1) After reboot start a call and close it before it starts ringing. Now until next reboot you should be able to call and listen.

2) ....

3) I've fixed the original camera app today, maybe from next build everything will be ok (see my post two or three before this)

4) This is a known bug, I've almost fixed it (Animation starts, shows for 5 seconds and tablet reboot, and animation restart.. and so on) https://gerrit.omnirom.org/#/c/5745/

Thanks for your report :D :D
[Galaxy Note 10.1 Android Development] kokero:
I would appreciate if you could tap the thanks button :good::laugh:
[Galaxy Note 10.1 Android Development] claytonjn:
Everything you reported was already known, and he's the one fixing the issues for you. Shouldn't you be the one hitting the thanks button for him, not the other way around?
[Galaxy Note 10.1 Android Development] kokero:
Yeah, I've already done it, as I do for everybody that replies me politely :)

And bug number two wasn't already known
[Galaxy Note 10.1 Android Development] claytonjn:
At the time of my post you hadn't, or at least it wasn't showing in XDA (I even double-checked before submitting the post just to make sure I didn't miss it) ;)
[Galaxy Note 10.1 Android Development] kokero:
I kind of did :confused: what post are you talking about?
[Galaxy Note 10.1 Android Development] claytonjn:
That's true, and FWIW I just tried it and it didn't work for me either. It behaves similarly to the issue I was having with putting the tablet in the dock, the OS becomes completely unresponsive to touch. In this case, however, the tablet doesn't eventually reboot...I had to do it manually. Perhaps that's because I switched the governor to mitigate the dock issue.

Yes, it's showing that now.
[Galaxy Note 10.1 Android Development] kokero:
:victory::victory::victory:
[Galaxy Note 10.1 Android Development] chappatti:
Ok,. Finally got around to the logcat. Hope it is still useful. There are two. First is for docking, second is g for undocking (go by timestamp). No fix has been applied. But JamMaster's kernel settings had to be applied to even be able to dock without freezing.

Look for DockObsertver in logcat.
[Galaxy Note 10.1 Android Development] kokero:
Hi again, I was thinking, what happens if try to use ART instead of Dalvik, anybody tested?

:D
[Galaxy Note 10.1 Android Development] marco9333:
Mmh at least it knows that a dock is connected. Maybe is a problem with hdmi driver, if you can check could you install a terminal emulator?

If yes, open it write "su" (without quotes), enter, "cat /proc/kmsg" (without quotes), enter, connect the dock and look for any strange message.

Android seems to find it. I've included some things in the kernel about hdmi (I've looked i9003 settings, which seems to have hdmi and dock working). They might be included in new builds.

I always use ART, everything is more fluid, battery seems to last longer but it takes longer to install an app and the first boot could take more then 10 minutes depending on how many apps have you installed
[Galaxy Note 10.1 Android Development] kokero:
Thanks for answering, I'm gonna test.

I just found out another bug, sometimes, I don't know why, after the Morpheus update, the tablet is rebooting by itself when is asleep. It is nothing very serious, it does not happen all the time, is kind of rare, it just happened twice for me, and it was not on the same day.

Hope be fixed, thanks again.
[Galaxy Note 10.1 Android Development] iofthestorm:
Do you mean i9300? I'm pretty sure they don't have HDMI working. If it did work then it would work for all Exynos 4s.
[Galaxy Note 10.1 Android Development] marco9333:
I've read they have hdmi working but I maybe misunderstood. Searching I read about many users complaining about hdmi so you're right.
[Galaxy Note 10.1 Android Development] kokero:
@

marco9333

ART worked perfectly, and I noticed a increase on performance, all apps are running ok :laugh:
[Galaxy Note 10.1 Android Development] dbodom:
I use ART also. System seems more responsive but it does take longer to boot after a ROM upgrade due to the apps pre-compiling. No problems at all otherwise.
[Galaxy Note 10.1 Android Development] chappatti:
EDIT: After some searching, and looking at dmesg, I "think" that a Samsung driver from the Samsung stock Video Player maybe required to enable the software routing properly. Is it possible to get the stock Samsung Video Player and/or AllShare stuff as apks to try out??
[Galaxy Note 10.1 Android Development] marco9333:
They are surely based on tw framework, we can't port them to an aosp rom :(

So this is the situation in my opinion: hdmi driver is working so the kernel know the device and how to use it, the problem is android-side. Could you do this test with [MENTION=1466338]TheMorpheus[/MENTION]' next version when he will release it? I've enabled smartdock driver in the kernel (was there but not included)
[Galaxy Note 10.1 Android Development] FPtje:
Here's a nice tip for when you use omni switch: the switching app animation is terribly slow. It makes you think that switching apps takes two full seconds. It doesn't, it's just the animation!

Go at developer settings and disable animations. It makes the tablet loads faster. That combined with Art is God tier.

The downside is that you'll have to live without many os animations. It's really worth it for me, though. Try it and see what happens, it's not a permanent change.
[Galaxy Note 10.1 Android Development] kokero:
Hello again, I found out another glitch today, the tab was turnig off by itself, and now I discoved the reson why: Active Display, I don't know exactly what is causing the issue, but sometimes, when the notification is shown, the display becomes unresponsive to touch, then turns black, then the tab turns off by itself. (It doesn't reboot just turns off, so you need to turn the tablet on manually).
[Galaxy Note 10.1 Android Development] chappatti:
Yes. I read around and it requires a Samsug-based drivers on TW software level... Is it possible an to hack it from older ROMs?

---------- Post added at 08:36 PM ---------- Previous post was at 08:30 PM ----------

Will this run on N8013??

Thanks
[Galaxy Note 10.1 Android Development] marco9333:
We have the binaries and some code from samsung which is built and included into the rom(Now I've pushed a commit to add another file for tvout which was excluded, I don't know why)

Theoretically it should, you'll have all the phone apps but you obviously can't use them. You can always try if it's not working just go into recovery and re-install a proper rom, do at your own risk. We can install n801x roms in n8000, losing all the phone capabilities, I'm pretty sure someone around the forum has done (or just asked ???) this.
[Galaxy Note 10.1 Android Development] iofthestorm:
Tvout was disabled because it doesn't work, lol.
[Galaxy Note 10.1 Android Development] marco9333:
mmh this is a good news :D The kernel driver is working as it should, maybe we need to rewrite the "android-side" ?

I was thinking about this device which has hdmi out as default video output and our soc.

http://www.hardkernel.com/main/products/prdt_info.php?g_code=G138733896281&tab_idx=1

And source code downloadable here http://dn.odroid.com/4412/Android/4.1.2_Feb-12-2014/BSP/

They're updating their devices but maybe some useful code can be taken from their.
[Galaxy Note 10.1 Android Development] MontanAndroid:
Not enabled on mine. Unless there is another option somewhere that I cannot find.

The setting I saw was under "settings", Enable transparency on lock screen ", and it is not selected.
[Galaxy Note 10.1 Android Development] iofthestorm:
Yeah, so the deal is that their code is probably based on Linux 3.4 or a newer kernel than we're working with (haven't actually looked), and their drivers are completely different so it's not easy to port their driver code back to the 3.0 kernel that actual mobile Exynos4 devices have. But one guy is attempting it, if you use IRC talk to geecko in #teamhacksung on freenode. He's been stuck several times but slowly making progress. But eventually if he's able to backport the drivers we'll probably have significantly better performance and possibly HDMI and all that stuff working.

Yeah, it turned out to be a bug which was fixed. I'm doing a build right now but I'm hoping we can kick off nightlies tonight, but if we don't then I'll upload my build later tonight.
[Galaxy Note 10.1 Android Development] Shakes27:
I wonder if/when we get the 4.4 update from Samsung if they'll update the kernel to 3.4. Probably a pipe dream, but one can hope. Obviously not the same SOC, but did the i9500 get a 3.4 kernel with the KitKat update?

EDIT: Yes, it did.
[Galaxy Note 10.1 Android Development] iofthestorm:
Was it on 3.0 before? I think there could be some chance of it to be honest because it seems like they moved on to 3.4 stuff for other devices. I don't know if Kitkat requires any specific kernel version. There's still a good chance that they will stick to the same kernel codebase, but then again, it's hard to say since the last update these tablets saw was 4.1, so who knows what they'll need to do to upgrade. I also honestly would not be surprised if they later turn around and say they only meant to say the 2014 version and not ours :(. I guess they should update i9300 though, which would probably be enough for us since they tend to ship all their drivers in kernels rather than just the ones for the device in question (but no guarantees as to whether the other drivers are actually working).

But since there's no ETA I'd put more faith in someone like [MENTION=5145944]GeeckoDev[/MENTION] backporting the drivers than anything Samsung puts out. There's no guarantee that it'll be easy or possible to integrate whatever kernel source they do drop in the end.
[Galaxy Note 10.1 Android Development] F_R_I_T_Z:
Obs:

Barometer measurement's are crazy....
[Galaxy Note 10.1 Android Development] iofthestorm:
OK, here's hopefully the last weekly build from me, hoping someone can start up nightlies for me tomorrow. Everything is merged and ready to go, and I have merge rights now :D.

omni-4.4.2-20140224-n801x-HOMEMADE.zip

Can N8010 users confirm that their tablet now displays properly as N8010 in About Tablet? Thanks!
[Galaxy Note 10.1 Android Development] easyguy:
So the omni team finally gave you permission to do nightlies? Cool! Cant wait.
[Galaxy Note 10.1 Android Development] iofthestorm:
I mean, I've basically been a maintainer in some sense for several months, there were just a bunch of things to take care of including some stuff which affected other devices which took forever to nail down because like many others on the team, I only work on this a few hours on weekends. I think we wanted to get an official new TWRP release as well but I think in the end Entropy512 agreed that me releasing my own TWRP build should be okay, or at least, yesterday he said he would try and start nightlies for n801x. He was busy today and didn't get to it, but I'm hoping someone will set us up tomorrow. But yeah, I just finally got merge rights to the n801x and n80xx repos on gerrit, which also took several weeks of pestering people on weekends lol. So I figure things should be good to go as soon as someone who is able to add us to the build bot does so.
[Galaxy Note 10.1 Android Development] claytonjn:
[MENTION=3125261]iofthestorm[/MENTION]

This is a bit off topic but you might be able to figure this out. I'm trying to track down how the color is determined for the network speed indicator in the statusbar. Basically, I'm using the Xposed module Tinted Status Bar but it is not able to change the color of the network speed indicator. Previously there was an entry in SystemUI.apk in colors.xml for status_bar_traffic_color. I'm pretty sure if that were just changed from being a hard-coded value to follow status_bar_clock_color then it would work perfectly.

The problem is, as of this commit that entry in colors.xml was removed: https://github.com/omnirom/android_frameworks_base/commit/017c56cdb2011cea0026b97e5c40ac9b567a072e

I've looked through all of the code there and in this commit: https://github.com/omnirom/android_...mmit/391eaddbf9b68d4338ea3ff3aed35848a43af71f

I can't for the life of me figure out how the color is determined now that status_bar_traffic_color is gone.

Any thoughts? Thanks!
[Galaxy Note 10.1 Android Development] iofthestorm:
Umm, no idea off the top of my head, but if the indicator is an image then maybe it's just fixed to the color of the image? Not sure.
[Galaxy Note 10.1 Android Development] claytonjn:
What I'm referring to is the text with the speed, and indicators. Or did you mean that it's possible it samples the color directly from the indicator images and applies that to the text. All I'm familiar with in terms of Java is the very little I taught myself for an app I created at a project in one of my classes.
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh, I thought you meant the icon, not the text. Hmm... I actually have not really had a chance to dive into most frameworks code yet, just a couple parts that I was digging through trying to change random things. Mostly just been focused on device specific stuff up till now.

Hmm, looking at that commit, it seemed like the ability to style that was just removed? It says it was unused but I'm not sure, it looked used to my untrained eye. I haven't actually made a proper Android app yet so I only really know the theoretical functions of all the layout and styling stuff, never actually done it to see how those properties interact.
[Galaxy Note 10.1 Android Development] wadken1:
N8010 type indication is fine. Many thanks for all your hard work on the rom itself and in getting the nighties sorted.

Any idea why the CPU is still being reported as only running Core 1? this was happening in i9300 for a while but was corrected a couple of weeks back.

Cheers

EDIT : Just ran Antutu on both my N8010 (score 11621) and I9300 (score 18650 with Boeffla kernel, 17973 with Omni kernel ) each using the latest Omni ROM, Pegasusq governor @ 1.4GHz and CFQ scheduling. This strongly suggests that the CPU is not being correctly managed on N8010 at present. Unfortunately, no-one is currently compiling an OMNI compatible custom Kitkat kernel for the N80XX series so can't take this test to it's natural conclusion - wish I had the skills :(
[Galaxy Note 10.1 Android Development] FPtje:
Type indication works fine for me too. Shows as GT-N8010