yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] WhitestSand:
Is anyone running xposed framework with this ROM??
[Galaxy Note 10.1 Android Development] sully112277:
Running fine for me. Try mounting system folder before installing.
[Galaxy Note 10.1 Android Development] TheMorpheus:
When you find the time, can you make a N8000 version so I can test it?

Thanks!! :good:
[Galaxy Note 10.1 Android Development] iofthestorm:
Thanks for reminding me, running off a build now. I'm also packaging up just the kernel and blobs in a flashable zip so that people can just flash that on top of an r3p2 build (and then potentially run whatever other AOSP kernel they want to).

I think in the future I'll keep doing mali r3p2 builds, but with the kernel downgrade zips people will be able to work around the glitches while we figure out what the actual issue is.
[Galaxy Note 10.1 Android Development] *d1000:
Rotation is now fixed on 01 ROM. Briefly saw 2 white lines when waking up device. Did it a few times in a row then I got my phone out to take a photo and it stopped :) Restricted user profiles is not working...can create accounts but when attempting to use after unlocking screen nothing happens (black screen). Can use pull down menu to get into menu options but cannot get to launcher it is blank. Had this issue with the IOKP ROM as well. Thanks for your continued great work. Still no sound though on N8010 :(
[Galaxy Note 10.1 Android Development] iofthestorm:
Screen glitch workaround

As an update, here's some workarounds for the screen issues. You can flash the kernel zips (also includes proper blobs) if you're on an existing Omni build, otherwise flash the full ROM zips. Though, you may want to download both in case I screwed up the kernel zip (I tested the n8013 version but not n8000 for obvious reasons).

kernel_n8000_mali_r3p1.zip

kernel_n8013_mali_r3p1.zip

omni-4.4.2-20140103-n8000-MaliRevert.zip

omni-4.4.2-20140102-n8013-MaliRevert.zip

And to reiterate, in the future I'll go back to Mali r3p2 which does have the issue, because I'd rather solve the issue than work around it, but for those who don't want graphical bugs you should be able to flash the kernel zip to fix them.

Edit: Kernel zips removed, they break wifi. Will have to figure this out later, I'll just keep building with r3p1 for now.,
[Galaxy Note 10.1 Android Development] dbodom:
So far, I can't recreate the white screen or edge ghosting on this downlevel Mali version. Perhaps this fixed our problem. Thanks for the kernel zips.
[Galaxy Note 10.1 Android Development] tsukaza:
I flashed the 02 mali ROM over the previous version and so far have not seem any more screen ill effects. Great work Happy New Year.
[Galaxy Note 10.1 Android Development] Jiggs82:
I see omnirom team had merged in quick settings tiles from cm/aospa earlier today but I don't see them nowhere in the settings on the latest build today, am I looking in the wrong place or are will we have to wait for another build? Thanks
[Galaxy Note 10.1 Android Development] phearus:
First I flashed kernel_n8000_mali_r3p1.zip - and it broke WiFi. It just wouldn't turn on.

No biggie.

Then I flashed omni-4.4.2-20140103-n8000-MaliRevert.zip, and all was well again. I also had to reflash superuser, but not Gapps. No sign of any weird screen stuff yet - will only report back on the matter if I see something.

Good job [MENTION=3125261]iofthestorm[/MENTION]! This will do nicely.

Now, something a bit off-topic to the screen business. I have a 64gb SD card. No matter what filesystem it is, android only ever sees it as a 59gb SD card.

So, as a workaround I have a scheme. Instead of one 64gb partition that gets truncated to 59gb, I have made two (fat32 for now - for convenience rather technical ability, so I am happy and will change later, once things are working) partitions, one 48gb, the other 16gb.

My question begins - how do I get android to mount the second partition?

I have tried adding the appropriate line in fstab.smdk4x12 that corresponds to the other partition, and added what needs to be added to init.smdk4x12.rc, however I cannot find the storage_list.XML anywhere, as outlined here: http://source.android.com/devices/tech/storage/config-example.html.

It seems on a reboot these files get refreshed / overwritten to their original form.

So there are several question I am asking for help with, for our devices specifically.

1. How can I mount both my SD partitions?

2a. Assuming I am on the right track with init-scripts and fstab, why are these scripts getting rewritten at boot?

2b. And, more importantly, where are they being rewritten from so I can hack-up the originals?

2c. Is storage_list.XML even a thing, and where is it?

3. Is there an easier way than this?

Thanks peeps, and [MENTION=3125261]iofthestorm[/MENTION] for the epic work.

---------- Post added at 12:12 PM ---------- Previous post was at 12:05 PM ----------

Apologies for the double-post... But I just have to get this out of my system!

So much this! The quick settings tiles functionality from CM is the only missing feature from this ROM. With it, OmniRom will be complete (not saying they should stop there, or not finish the WIP stuff, just saying that it will be at a very-very healthy starting-point. Everything after this are "nice-to-haves," and not necessarily essential).

That said, [MENTION=3125261]iofthestorm[/MENTION] - no hurry and no pressure, etc - when it happens it will happen. You have done epic work thus-far and for that we are all very grateful.
[Galaxy Note 10.1 Android Development] iofthestorm:
I didn't sync up for the Mali revert builds, I just rolled back kernel and blobs and rebuilt. That said, are you talking about this? https://gerrit.omnirom.org/#/c/4211/ I think that got merged after I built anyway. I can sync and rebuild (I'll stick to Mali r3p1 for this one too, since I'm not sure if there's an issue with my kernel zips).
[Galaxy Note 10.1 Android Development] Jiggs82:
Yes exactly and if you can sync and rebuild that would be awesome :D btw I haven't had no white screen glitches with the latest 2 builds on my n8013 good work sir :good:
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh damn, you're right, wifi is broken if you just flash the kernel. Sorry about that, my first time trying to package a kernel by itself and I just decided to remove everything except the boot.img and the mali blobs from the regular zip, modify the install script, and then zip it back up. I wasn't sure if there would be issues with drivers compiled as modules and I'm guessing that's what the problem is. I'll just remove the kernel zips for now then and keep going with r3p1 until I can find time to figure out how to package a kernel properly.
[Galaxy Note 10.1 Android Development] iofthestorm:
Alright, trying something different here, I rolled my own download tracking code and I'm gonna upload to my own server rather than XDA (I really want to see accurate download counts, plus I'm bored). These builds have the new QuickSettings toggles and configuration (hit the pencil to edit, tap an icon to enable/disable, drag to reorder). And still using Mali r3p1 so should be free of screen glitches.

omni-4.4.2-20140103-n8000-HOMEMADE.zip

omni-4.4.2-20140103-n8013-HOMEMADE.zip

Let me know how the download speed and reliability is compared to XDA; this is really a cheap VPS but it seems relatively fast for cheap VPSes. It's also easier for me to upload to this than XDA, and I might be able to set up OpenDelta updates as well (I put off trying it out because I was hoping we'd get official builds sooner, but I guess I'll probably continue doing my unofficial testing builds after official builds anyway, and in the meantime it might be nice to have OTA updates). Though I think I borked the configuration on this build so it won't work for the next one (i.e. if I can get the configuration right on the next build, you might get update notifications for the one after that).
[Galaxy Note 10.1 Android Development] TheMorpheus:
Download speed isn't bad!

The rom seems to work good, no white screen yet... Nice work!

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] planetf1:
I'm still on the 8013 rom from 1/1, which I installed almost immediately it was posted. Not a single white screen issue so far..... Post #291

I was getting white screens before. Clearly I'm only 2 days in but it's interesting nevertheless

If/when I do get an issue I'll upgrade to the p1 based build but I'll stick with it for a while. I can;'t think I changed anything else....
[Galaxy Note 10.1 Android Development] tsukaza:
dling 20140103 now, great to play with :) Thanks.
[Galaxy Note 10.1 Android Development] electrikjesus:
So far, the 1/03/14 build for the N8013 is running well with NO SCREEN ISSUES, no force closes, or any other issues :) I think it might be about time for me to re-flash my recovery the way it should be and stick with this ROM full time now. Awesome work as always.
[Galaxy Note 10.1 Android Development] Nemury:
can i dirty flash this?

Yes you can i did dirty flash it an it is working very nice.
[Galaxy Note 10.1 Android Development] ponygon101:
Sorry if this is a stupid question but if you're waiting for official builds, why don't you join Omni and make your unofficial builds official?
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh, what I mean is that I've submitted the information to them for making it officially supported but I'm sort of waiting to hear back from them. It was almost merged once but there is one little hack that was required that they didn't want to merge if it was possible to avoid it, so they asked me to try and figure out a proper fix basically. The issue is that the keyboard dock driver registers itself as an input device even if it's not detected, and it doesn't seem to be unregistering itself like it's supposed to. So Android thinks that there's a physical keyboard and refuses to show the software keyboard. There's a hack that's been used in CM for a while for devices with this issue that just forces it to always show a software keyboard, but the thinking was that if there was a proper fix it'd be better to fix the issue than add a workaround for it. I proposed a couple solutions (the most likely one being to just disable the keyboard dock driver since I doubt anyone actually has one who wants to run Omni) and I'm waiting to hear back on what I should do.

I also wanted to fix the screen issues before official nightlies, just so that when we start a new thread it is less cluttered with irrelevant information, but it'd be better to have nightlies and then fix the issue later than not have nightlies IMO (I just don't want to spend ~2 hours doing builds and uploading them when a build bot could do it for me).
[Galaxy Note 10.1 Android Development] TheMorpheus:
I agree, they should accept already, the build is stable and now the white screen broblem is gone!

I have just one issue, that I've already reported, I'm unable to play with Real Reacing 3 the audio is completely messed up... Strange that nobody else reported this, aren't you guys play whit anything?

Sent from my GT_N8000
[Galaxy Note 10.1 Android Development] planetf1:
I just downloaded that game to try and confirm the sound his very messed up.

No problems with any other apps but i rarely play games
[Galaxy Note 10.1 Android Development] iofthestorm:
Well the thing is I haven't actually fixed the issue in a way that's mergeable unless they want to roll back the Mali drivers for all Exynos 4 devices (which arguably might be a good idea if there are other issues that people aren't realizing are related on other devices). And besides that everyone is very busy, and it's not that bad for me to rebuild and upload files occasionally while there are no nightlies.

Oh sorry about that, I also had the same issue with NFS Most Wanted. Though I don't play that many games on Android, and if I do its mostly on my phone because the tablet I awkward to hold for most games. Not sure what the issue is yet.
[Galaxy Note 10.1 Android Development] planetf1:
OK I had the screen issue finally on the p2 build... Time to update....
[Galaxy Note 10.1 Android Development] xlamian:
Thanks for all the hard work and help. I am once more enjoying this great tablet on an awesome ROM. Keep up with the great work, as it's probably the best AOSP ROM that I have been for the 8013.

I actually get better DL speed on the new server.

Cheers
[Galaxy Note 10.1 Android Development] iofthestorm:
You know, it's really true that 5 minutes talking to an expert is better than 5 hours (or even days) of banging your head against a wall blindly ;)

Thanks to a little conversation I had with Entropy512 today on IRC, we narrowed down the screen issue - it's not related to Mali at all, but rather the s3cfb driver (display driver). I had assumed that they were related but it turns out I was able to just revert the one commit introducing updates to s3cfb rather than roll back everything. It seems like the issues are still gone, but now we're still using Mali r3p2. I'd like to narrow this down further to the actual change that causes the issues (this commit has 36k lines added and 53k lines removed, lol), but for now this is a huge step forward in finding out what's wrong.

Here's another pair of test builds. This time, I've only reverted this commit in the kernel. Please give it a whirl and let me know if you experience issues.

omni-4.4.2-20140104-n8000-HOMEMADE.zip

omni-4.4.2-20140104-n8013-HOMEMADE.zip

Also, glad to hear the server is working fine, it's only a $7/month VPS so I'm pleased that it's actually performing well. I guess it just doesn't get nearly as much load as XDA does so for our purposes it's fine :D
[Galaxy Note 10.1 Android Development] Kidromulous:
G

Flashing

Edit: Working great so far
[Galaxy Note 10.1 Android Development] dbodom:
Flashed the latest. Seems okay on my n8013. Will test over the next day or two to see if the white screen or edge ghosting issues are still resolved.
[Galaxy Note 10.1 Android Development] planetf1:
Ditto. Flashing. Good news
[Galaxy Note 10.1 Android Development] Ba7rani123:
I have a suggestion for the keyboard fix, how about making it optional ? Like a switch to enable/disable keyboard driver.

IMO they have a point, having a proper fix leads to less bugs...
[Galaxy Note 10.1 Android Development] The Zel:
Latest build is running great and expecially with no lags (it did lag with earlier builds). Thanks dev, great work! :thumbup:
[Galaxy Note 10.1 Android Development] electrikjesus:
Came across one issue so far on the 01-04-14 build with getting Superuser to work right. I flashed the usual SuperSU .zip after updating, wiped dalvik and cache, and no SuperSU was shown in the apps list :( It would retain the permissions granted to apps in the past like ROM Manager, but it would not pop up when new apps asked for permission. I eventually had to manually install SuperSU and reboot to get it to work. Other than that, so far so good!
[Galaxy Note 10.1 Android Development] Nemury:
I have the same problem Titanium requesting Root access forever
[Galaxy Note 10.1 Android Development] al5911:
Flashed on my N8000. All good including getting root to work. Unfortunately my 3G is not working. Any help?

Edit: NVM...just forgot to setup the apn for my phone operator....

Other than the offline charging animaion is not working, overall the rom is really working on my N8000. Thanks.
[Galaxy Note 10.1 Android Development] Kaiser130:
While using some apps, often the central function keys disappear. I have to turn off and on the screen to review the key
[Galaxy Note 10.1 Android Development] benjiboythelad:
Sorry dose multiwindow work on this rom or do I have to cherry pick it ?
[Galaxy Note 10.1 Android Development] Kidromulous:
A quicker way to fix this is by merely pulling down the notification shade I think the bug is associated with immersive mode.
[Galaxy Note 10.1 Android Development] iofthestorm:
Err, that's a feature of Kitkat, just swipe up from the bottom of the screen to bring them back. Same with the status bar at the top. It's just a more useful full screen mode.
[Galaxy Note 10.1 Android Development] Kaiser130:
Thanks, you're right!
[Galaxy Note 10.1 Android Development] iofthestorm:
Should be included, just try long pressing an app in the multitasking view. Though I realized last night that my last build was missing some stuff such as the GPS fix so maybe I forgot it. Next time I'll have GPS fixed (as an aside, I'm beginning to learn how incompetent Samsung can be, it's their source releases which break GPS randomly - this should be illegal, because it's clear that there's no way the source they release corresponds to the kernel on a shipping device unless all wifi tablets have broken GPS, but I guess it's kind of a gray area).
[Galaxy Note 10.1 Android Development] dbodom:
Just noticed you're right - GPS is broken again. When do you think a new release is coming?
[Galaxy Note 10.1 Android Development] xlamian:
Deleted
[Galaxy Note 10.1 Android Development] benjiboythelad:
Haha im anooyyed at their lack of compatability with android stuff custom boot animations on stock, and splash, grr but omni ( sounds good ill doit tomorrow )

Would happen to know if its possible to put samsungs multiwindow framework too any rom,
[Galaxy Note 10.1 Android Development] iofthestorm:
I'll probably roll something up tonight just to fix GPS, maybe cherry pick some neat upcoming features. I'm still working on a proper fix for the screen issues without a massive commit and I think we're getting close (Entropy512 had something he was going to test this morning).
[Galaxy Note 10.1 Android Development] iofthestorm:
Here's a little test build for N8013 only, because I don't have time to run another build unfortunately :/. N8013 gets to be the guinea pigs today.

I've tried to update the framebuffer and LCD drivers to those included in the latest i9300 kernel source drop (previously there was a mixture of code from before the source drop and after - it's weird because the i9300 kernel drop has updated drivers for n80xx which no n80xx build yet has seen... so I guess it's possible that N80xx will continue to see updates in the future, or they were just refactoring that code because they were bored). I thus undid the revert I did earlier to fix the screen issues, so if this also fixes them that means we've found our proper fix and can move forward!

omni-4.4.2-20140106-n8013-HOMEMADE.zip

As usual, let me know if you see any of graphical issues that we've been discussing here (white screen on being unplugged from charger being the only one we know how to reproduce, but of course there are the other gremlins lurking as well).

Also, GPS is fixed again, sorry about that mixup.

Oh, and this build has Quiet Hours, not sure if the previous ones did.

Edit: Oh, I just tried setting up OpenDelta (the last few builds have actually been pointing to my server as the update server) - could you guys try going to System -> Check for Updates and see if it works? It'd just be interesting, probably not a big deal either way.

Edit2: Wait... try now lol, didn't finish uploading when I first edited.
[Galaxy Note 10.1 Android Development] Rongogo:
My first install of this rom, mayby usefull for other poeple.

Used latest phillz recovery.

Install this rom, for me the latest n8000 build.

Install latest gapss for Kitkat.

Boot rom, and setup the device.

Now reboot into recovery.

Root ROM again with phillz recovery. (It's a option in the recovery menu)

Download Su app from Chainfire, Install and reboot.

Download and install wanam exposed.

Install exposed module gravity box for KK.

Tweak you device

Hints: go tot setup, device info, and tap a few times fast on the build info box, on the bottom, so you can get dev rigts.

Grtz Rongogo
[Galaxy Note 10.1 Android Development] dbodom:
Installed the latest. GPS working and I don't see any screen issues.... yet. I'll test it out today. By the way, I did Check for Updates and it just reported I was up to date. Is that the expected result? Let me know. Thanks for all your efforts.
[Galaxy Note 10.1 Android Development] iofthestorm:
Well, the goal was to have it update you from 0104 to 0106, but I guess that didn't work out. Oh well, not a big deal, I feel like now that Entropy512 is helping we *have* to be close to official, hopefully I can catch him on IRC today.
[Galaxy Note 10.1 Android Development] xlamian:
System update working, yeah! I will report on the rest later .
[Galaxy Note 10.1 Android Development] jusliloleme:
Did the System Update and downloaded/verified 0106. Selected Flash Now and booted into recovery (CWM v6.0.3.6). Got the following:

Warning: No file_contexts

Waiting for SD Card to mount (20s)

SD Card mounted...

Verifying SD Card marker...

SD Card marker not found...

Error processing ROM Manager script. Please verify that you are performing the backup, restore, or ROM installation from ROM Manager v4.4.0.0 or higher.

/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue

Am I missing something?
[Galaxy Note 10.1 Android Development] iofthestorm:
Oh sorry, I think it requires TWRP.
[Galaxy Note 10.1 Android Development] jaxxes:
Yep, it does require TWRP to apply the update automatically. What I've been doing on the note 2 is downloading the update, telling it to flash under philz, then when the error comes up, navigate to the opendelta folder and apply the update without issue. Works really well since rather than going through the auto reboot that most updates like this have, I have the chance to also reflash root before rebooting.

And otherwise, n8013, been working of the 1/04 build I believe it is with none of the major screen issues. I still get a slight flicker about half an inch from the left side of the screen (in portrait, power button on the right, how I usually hold my tablet) when I scroll through things quickly, but that's extremely minor. I also noticed that even though the charging animation is still messed up when the tablet is powered down, it hasn't been turning itself back on. Love this ROM and gets better with every nightly!
[Galaxy Note 10.1 Android Development] wadken1:
Just did the system update from 04/01 to 06/01(brit date format). It downloaded the whole zip rather than a delta possibly because this was the first attempt?

Anyhow I'm using latest PhilZ recovery for N8013 and everything went perfectly.

For me PhilZ is preferable as the TWRP GUI is quite dodgy and very annoying to use.
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah, there's a sort of bug in the touchscreen event handling for TWRP for n80xx and some other devices. I've submitted a patch to fix it and actually I should probably update my TWRP that's listed here with it, but the issue is that my TWRP is still kind of broken so I don't really want to recommend people use it until I fix it. So yeah, I've just been recommending Philz, I just didn't realize that the automatic updates require TWRP. I guess that's another thing I should fix when I get a chance.
[Galaxy Note 10.1 Android Development] wadken1:
My auto update did work with PhilZ!
[Galaxy Note 10.1 Android Development] iofthestorm:
Those of you who are using the Xposed module or the standalone flashable zip from liquid64, does it fix only Netflix or all video streaming? I would expect it to only fix Netflix but not other apps (they both seem specifically targetted to fix the Netflix app), but I wonder if the issue is the same.
[Galaxy Note 10.1 Android Development] :
Netflix, youtube (in app and in chrome) and hulu plus work for me. I just tried that Twitch app that you mentioned and it does not work -- sound but no video. So that's interesting.....

---------- Post added at 08:45 PM ---------- Previous post was at 08:41 PM ----------

Hey [MENTION=3125261]iofthestorm[/MENTION], did you want bug reports to be posted somewhere? Just came across a bug... Swype on aosp keyboard causes it to crash. I switched to Google keyboard and that works fine.
[Galaxy Note 10.1 Android Development] iofthestorm:
Ah yeah, try out the "Bug Reports" thing at the top of the thread. Seems like a good way to keep things organized. I've noticed that too, but I just use Swiftkey so it didn't bother me too much.