yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 Android Development] iofthestorm:
The camera app isn't based on Focal, just FYI. But that's really interesting. I haven't really looked into camera issues because there's a patch for open source camera HAL that I want to try out at some point, which might fix various errors. Last time I tried it though it caused issues with video recording so that will need to be fixed first. Right now I'm just kind of coasting until official nightlies come out though, I'd rather keep it simple for myself to put out new builds when necessary until there's a build bot doing it for us :D.
[Galaxy Note 10.1 Android Development] chappatti:
HDMI...

Re HDMI in KitKat... Apparently these guys (link below) on the Asus TF700 have HDMI working on kitkat 4.4.2. I posted there but am yet to get a reply..Any way to look into it?

xdaforums.com/showthread.php?t=1957660

One note, theTF700 has a built in micrpo-HDMI port in it. Don't know if that makes a difference over using a dock or adapter....
[Galaxy Note 10.1 Android Development] iofthestorm:
Sorry if I wasn't clear earlier, it has nothing to do with Kitkat and everything to do with Exynos. It has been broken on AOSP based ROMs on all Exynos4 devices for quite some time (possibly forever). Transformer will have nothing to do with us. And the fact that their port is built in probably means fewer layers to go through as well.
[Galaxy Note 10.1 Android Development] chappatti:
Thanks, master! I get it now... I will think about dumping the Note 10.1and go to the TF700. :p:p
[Galaxy Note 10.1 Android Development] asoep1:
{Edit}I fixed the system Ui problem but now when I try to take a screenshot or screen record the tablet freezes and needs rebooted any fix for this?
[Galaxy Note 10.1 Android Development] jaxxes:
Just tried out omniswitch on the note 2 and love it. I presume it will be a way to launch favorite apps in multiwindow as well. Would be nice to see it here, but definitely eager for those nightlies, so keep up the awesome work!
[Galaxy Note 10.1 Android Development] koxminator:
Many thanks for this great rom! However, I just experienced something strange, but I don't know yet, what is related to (01/28 version).

When I start a game (Star Wars Pinball), it feels like a bit laggy. Previously I used Humberos' 4.3.1 ROM, and it was flawlessly smooth. Maybe it's related to a governor and an IO scheduler setting?

By the way everything else is smooth and fine.
[Galaxy Note 10.1 Android Development] chappatti:
Back to HDMI...ahem

Does it matter that the Note 3 with the Exynos is now officially KitKat 4.4,and HDMI works there, can we adapt it to our tablet...

Just thinking....??:):angel:
[Galaxy Note 10.1 Android Development] iofthestorm:
Well, not really... They're Exynos 5 which is completely different from what I understand. There is one possibility that some devs were mentioning on IRC today, if we can upgrade our kernel to version 3.4 (from 3.0) and upgrade a lot of the drivers, we could have a similar graphics stack as the Nexus 10 and there's a chance HDMI would work then. But it's basically an insane amount of work from what I understand, one guy was attempting it but he kind of gave up once he realized that he needed to upgrade the kernel and not just the drivers. It may happen eventually, but I wouldn't hold your breath.
[Galaxy Note 10.1 Android Development] iofthestorm:
OK, here's some new builds, now with Omniswitch. Also, for keyboard dock folks, I forgot to re-enable the keyboard dock driver, so sorry about that. I'm really busy today but maybe tomorrow I'll try and put up a build with it enabled.

omni-4.4.2-20140202-n801x-HOMEMADE.zip

omni-4.4.2-20140203-n8000-HOMEMADE.zip

(version numbers are different but the code is the same, just happened to build at different times).
[Galaxy Note 10.1 Android Development] chappatti:
Thanks iofthestorm, for patiently answering my questions !!

Sign off a classic Dev... Kudos:good:
[Galaxy Note 10.1 Android Development] esgie:
Your twrp is unable to restore any copy performed by itself with my stock rom.

It says Failed every time, regarding every partition.

Regular twrp cant restore them too.

Hope i've not lost all my data thanks to your recovery.

U know the fix?
[Galaxy Note 10.1 Android Development] Rongogo:
You flash it self on your tablet, you can't blame the developer, or others.

But what you can try is, Phil's recovery, and set the system pad's to /mnt/sdcard, and not to /emulated/0 in the recovery, don't forget to reboot the recovery, after chance the paths.

After reboot the recovery, try to restore the backup

Rongogo
[Galaxy Note 10.1 Android Development] chappatti:
Nobody asked you to flash your tablet. Right throughout this thread people have been talking about this recovery issue, almost every page.... You have to read what other people have d before you flash anything. You do not flash blindly..
[Galaxy Note 10.1 Android Development] banderos101:
Any chance a note user could possibly post a youtube vid of multiwindow working for the most recent realeases, or anything else you think worth showing?
[Galaxy Note 10.1 Android Development] lazer155:
If I'm already on omni rom and want to update to a new version of it, do I still have to reflash supersu and the gapps?
[Galaxy Note 10.1 Android Development] claytonjn:
SuperSU depends on if you choose to install the SuperSU backup script. Gapps depends what Gapps package you use.

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Galaxy Note 10.1 Android Development] gravis_jg:
damn u r so halpfull ... thanks 4 that
[Galaxy Note 10.1 Android Development] lazer155:
Where can I find the backup script? I've searched and couldn't find it. I'm using the gapps package in the OP of this thread.
[Galaxy Note 10.1 Android Development] claytonjn:
Open SuperSU>Settings>Install SuperSU backup script

You shouldn't have to flash Gapps every time with the PA Gapps.

-Sent from my Developer Edition Galaxy S4 using Tapatalk
[Galaxy Note 10.1 Android Development] iofthestorm:
What exactly happened? I need way more information than that. If you're still on my recovery please note the exact error message, and also after you get the error go to the main menu, then "Advanced", then "Copy Log to SD" and please upload it here. Also make sure to note exactly what ROM you are running, is it completely stock or a stock based ROM or what?

Hold on, there should be no problem restoring backups as far as I know, I don't recall anyone reporting that. All I did was rebuild TWRP from the latest source, as well as fix the touchscreen bugs, but that should have nothing to do with backups.
[Galaxy Note 10.1 Android Development] yvesfg:
The Link is Broken!

Hi!

I have tried to download the new build, but the link is broken and the torrent have no seeders.

omni-4.4.2-20140203-n8000-HOMEMADE.zip

---------- Post added at 01:24 AM ---------- Previous post was at 01:15 AM ----------

Direct Download is now Working!

Thanks...
[Galaxy Note 10.1 Android Development] planetf1:
The new build is working well. Stable, responsive, but the dropped core issue is still there. This time around it seems to be core 2 (3rd one) that tends to stick offline... Or be reported as such anyway

---------- Post added at 11:54 AM ---------- Previous post was at 11:52 AM ----------

Actually system tuner shows them all as online so perhaps this is purely a cosmetic issue in the performance settings ui
[Galaxy Note 10.1 Android Development] chappatti:
In my book, you don't c**ap on the dev and blame him as though he was the one that made your tablet go "woosh"...... It's wrong to

blame

anyone (note I say blame) - even beside the dev - on threads if their advice does not work .. Whining about your loss may be OK, but actually blaming someone as though they were

responsible for it

... Nah.

This stuff

"Hope i've not lost all my data thanks to your recovery."

Nope. Not done, . (<period) !
[Galaxy Note 10.1 Android Development] esgie:
I have already read three comments with a criticism that I shall not blame the dev and that I have flashed blah blah blah myself.

Can you repeat it again, five or seven times? I think I didn't understood yet, and as for now I still insist that my cat, not me, flashed the recovery.

Ridiculous....

I thought we are talking about a technical issues - as it is mainly a dev forum - but seems I was wrong, as the users really seem to be deterimned to talk not about the CWM recovery, but about my Moral Unpurity. Goddamn, shut up guys, if you have nothing smart to say.

I will not sue the dev, I will not call him names, I will be not calling to him during the night with a blackmail, I will not blow up his house, I will not send a masked assassins to hunt him up. Roger that?

I'd rather concentrate on dealing with the issue, so whole community can benefit from more stable product.

The problem is not restoring, but creating backup. Your recovery restored previous backups (made with "stock" TWRP) without issues; however, "stock" recovery also failed to recover that damaged backup that caused the issue.

I dealt with the problem, by combining half-month old backup which was working and the "damaged" backup, which I was able to decompress and extract using command line tar (tar -x -f system.*.win -C /sdcard/system.tmp, etc.); then I had been manually copying folders and files which I have modified in last half a month with cp -pf, bla bla bla it took over 8 h to recover all the stuff I was interested in, but I have dealt with the problem.

(extracting system/data with tar straight to the partition didn't worked, unfortunately...)...

I had done a recovery.log in the time I was dealing with the problem, but I no longer have it (sorry, my data was more important for me..). Also, I wish not to reply all the process, for obvious reasons. However, AFAIR, the log said only about tar failure, nothing more, no exact explanation.

The effects were that the TWRP was wiping the partition (no matter if it was boot, efs, system, cache or data... I have tried to recover them individually...), and after that it was starting to flash the backup, but failed every time at the same beginning, no matter which partition did I flash.

The backups were performed to exfat partitioned 64gb external sd card, Samsung class 10, with compression.

Is it possible that the reason was selecting an option in SuperSU to survive OTA updates (I use localized SuperSu, so dunno what is the name of the option in English...)?

Additional bugs in the TWRP I have found, just btw:

- screen isnt turning off, the backlight remain on (it is turning off in "stock" TWRP - important issue, as it is draining a lot of battery)

- cannot mount preload at all (which is also an issue for me, as I used to utilize this partition for my purposes).

Hope it might help you...

PS As for now, switched to Philz + Aroma, but looking forward to get return to TWRP...

EDIT:

Found the log!

http://www40.zippyshare.com/v/80964793/file.html
[Galaxy Note 10.1 Android Development] chappatti:
Okay since you got the message, let's see if we can help.....

Note: These comments are solely my opinion, and cannot be used against me in a court of law.

1. On KitKat 4.4, for various reasons, backups/restore are not backward compatible. You have to make a backup with the older recovery, then flash the new recovery and then upgrade to 4.4. You cannot anymore flash the new recovery AND THEN make the backup, and then upgrade. Generally, it does not matter whether it is CWM or TWRP the issue seems to be the same, although some luck can be expected with CWM vs TWRP. In any case, it is better not to try. Basically, do not try to make backups of JB 4.3 with any 4.4 "versions" of recoveries TWRP or CWM.

2. This will also be true for restoring. You have to wipe data in new recovery etc., then flash back to old recovery and then restore to previous version from backup. In this case, one will have to use the keypresses to get into recovery. I would suggest using the same recovery used to make the backup.

3. From all experiences I have read, for the Note 10.1, Philz recovery is the only sure-shot.

4. Although this is the thread for the Note 10.1 2014 edition, http://xdaforums.com/showthread.php?t=2515656 you will see at least

"CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it". Another point to note.

5. The OFFICIAL TWRP recovery page lists only recovery 2.6.3.0 as the latest for the Note 10.1. So any other recovery is a modded one. It is going to have its own quirks. In the post in item 4, the invitation to add recoveries for "unsupported" devices is interesting.

6. When on Kitkat use Philz recovery for the "safest" option.

If you feel anything I said is wrong, go ahead and call me names and whatever you like. Get it out of your system, it does not hurt me !! :p:p

And then you can correct it. !!! :)
[Galaxy Note 10.1 Android Development] banderos101:
just wondering, off chance has anyone tested this with this rom

"TouchWiz On A Non-Samsung Phone?! Madness!!"

http://androiddissected.com/touchwiz-on-a-non-samsung-phone-madness/

"This is not a TouchWiz-based ROM or some random UCCW skin; this is the real launcher which you simply install on top of your current layout. You can still enjoy the brilliance of your own custom ROM while using Samsung’s TouchWiz launcher."

specifically, does the spen features work, snotes?

offchance that someone has
[Galaxy Note 10.1 Android Development] rhumbus:
After spending a couple of hours reading this whole thread thoroughly last night, I installed this ROM on a n8000, and everything looks impressively good so far. So just joined in here to say thank you very much for the hard work of iofthestorm and the contributes.

Was wondering: did anyone manage to run GravityBox [KK] on the latest build? I have 2.9.5 installed and it's refusing to start...

EDIT: I spoke too soon. I had wanam Xposed installed too and it probably interfered with GravityBox. I disabled it and all is dandy now.

Thanks!
[Galaxy Note 10.1 Android Development] hotyys:
3 cores are offline after running for a while.

this rom is definitely unusable
[Galaxy Note 10.1 Android Development] wadken1:
This ROM is perfectly usable.

Having CPU cores offline is expected & desired hot-plugging behaviour to save battery while not much is happening on your device. Try looking around XDA there's plenty of text around telling you how this works for the various CPU governors.

If you don't like the behaviour of a particular governor then choose another. For me Pegasusq works fine for most circumstances - I swap to Performance when game playing.

Cheers
[Galaxy Note 10.1 Android Development] roywheels:
Why post a comment like that? It isn't useful to anyone.

I've been using the rom for weeks now and it's far from unusable. I wouldn't use any other rom at the moment.

Has anyone been using the new omniswitch? It seems a little ugly at the moment but I can see it being a useful addition to the interface.
[Galaxy Note 10.1 Android Development] hotyys:
I'm perfectly aware that the cores going offline is a normal behaviour, but the problem is that they never go online again which leads to the extreme slow of overall responsiveness.

I have to flash back to the PAC rom, which obviously doesn't possess such problem.
[Galaxy Note 10.1 Android Development] roywheels:
So we're all using an extremely slow rom are we? Nope. That's just not true. Don't you think more people would notice if only one core was working? My tablet has been running great since I installed omnirom.

Afaik, both the pacman rom and this rom share kernel sources (humberos's kernel dev). But then you're probably 'perfectly aware' of this already.

Again, your posting is of no help to anyone. Going back to another rom seems like the best idea for you seeing as you're so certain this issue is affecting everyone...
[Galaxy Note 10.1 Android Development] wadken1:
The cores do go back on-line again when they need to!! If they didn't my would truely be unusable as you say and so would everyone else's but they're not.

If you just sit there watching a readout of the core behaviour then you are not imposing anything like a sufficient computational load for them be turned on.

Also be aware that not all CPU core monitoring is being accurately presented.
[Galaxy Note 10.1 Android Development] kokero:
Hey there!

Could some one post a .tar file of the TWRP 2.6.3.1 recovery so I can flash on Odin, please?

Thanks!
[Galaxy Note 10.1 Android Development] hotyys:
I was not just sitting there reading the cores' state.

I thought there might be some apps occupying cpu resource, so I checked running processes, and killed some suspicious apps, but the response to my touch is still very laggy.

After trying some cpu monitoring tools, such as System Tuner, I found out the core issue which I mentioned before.

The rom is great, except for the core issue which is really annoying.

PS: device model is N8000
[Galaxy Note 10.1 Android Development] iofthestorm:
What governor are you using? Pegasusq, the default, is probably the best, some of the others are not designed for hotplugging. And I think it is the case that if you're on pegasusq, and it disables a core, and then you switch governors to one which doesn't support hotplugging, that core will be stuck off.

As others have mentioned, this problem clearly is not affecting the majority of users, so without more information it's quite possible that you're doing something wrong.
[Galaxy Note 10.1 Android Development] hotyys:
Thanks for your reply, and explanation.

I have reflashed the rom, and am still exploring.

hope it's because I did something wrong.

I'll update the post with new findings.

again, thanks for the fantastic rom.
[Galaxy Note 10.1 Android Development] iofthestorm:
Hey! I've been recommending people use on-device flashing methods such as Recovery Tools or Mobile Odin or Flashify, just because I was too lazy to look up how to make an Odin flashable tar. I just looked into it and it seems like I don't have to do anything special other than name the recovery file recovery.img, so here you go. Unfortunately this is completely untested as I don't have my USB cable with me at the moment, but the process was simple enough that it should just work.

twrp-2.6.3.1-n8000.tar.md5

twrp-2.6.3.1-n8013.tar.md5
[Galaxy Note 10.1 Android Development] kokero:
Thanks man, you are awesome!

I have just installed Recovery Tools on my n8000, it is already rooted, but I don't have any custom recovery, because of that I'll have problems flashing the .img file with it or not? I was kind of scared to use it, thats because I asked for .tar file so I could use Odin method wich I'm more familiarised :S

Thanks!
[Galaxy Note 10.1 Android Development] iofthestorm:
I'm not sure. My impression is that if you're rooted it should work, since it probably just remounts recovery as writable and then dd's the image file to the recovery partition, but I don't know this for a fact since I've never tried it personally. Anyway, you could probably give the tar a try and see if it works.
[Galaxy Note 10.1 Android Development] kokero:
So how have you installed the Rom on your device, which is the method you recommend? Thats the first custom Rom that I'm going to install on my tablet, and I'm kind of scared XD

Thanks!
[Galaxy Note 10.1 Android Development] iofthestorm:
Hah, it's been so long, I don't remember. I bought my Note 10.1 the second day it was available, and flashed CM on it as soon as it was released. Probably used Odin at the time, it's the fastest way to install a custom ROM since it doesn't require root. I wasn't aware of Recovery Tools until recently tbh, though I had Mobile Odin for a while.
[Galaxy Note 10.1 Android Development] esgie:
Hehee... Even if we assume the worst scenario (a madman who will be so determined to sue you...) you shall not worry at all - you have included a clause that ur not responsible for any damage of the devices in the op; this clause shall be understood as an statement of will, equal to a licence clause (however, not as official as "true" licence text...), which I am accepting by downloading your stuff ;]

I have never planned such an actions. However, you may want to reconsider the "whatever" part - as you probably do not want someone to blow up your house or send assassins after your head ;)))

Referring to the rest of your post: thank your for your explanations (won't it be a good idea to include a warning in the op that your recovery is NOT 4.1.2 compatibile? This will prevent users from such a disasters like mine... and remember, that obviously not everyone know how to unpack tar from command line, copy single files with appropriate permissions, etc...). However, after reading your explanations, I am still not sure - is the Philz v5 recovery compatibile with both new & old roms, or at least with old ones? Is so v6 (which fails to run AromaFM atm on N8000, but I will surely want to use it if the dev fixes the bug...)? I have flashed it after the discussed accident, made some backups, but still haven't performed a restore - is there a risk that it will fail again? Let me remind that the ROM which will be a subject of backup & restore is NOT aosp based, but ol' good 4.1.2 Sammy's-based...

Otherwise, it seems that I would want to get back to official TWRP (will be a hard experience - meanwhile I felt love in Aroma FM and terminal...) (no, no, no, it will be definitely ESSENTIAL to secure my own ass and do a last-resort backup with official TWRP before testing if Philz do work - unfortunately, I haven't got enough free space on my device/sd card atm)...

Also, I wonder if you can give me a tip: what're the exact reasons of incompatibilities between old & new recoveries (a single keyword will be enough :) )?

Plus, I have a two not-related question:

- do you know any custom, feature-rich kernel, that support this ROM? Do you maybe have plans (or have a knowledge about someone's elses' plans) to release one in the future?

- does your ROM support IrDA?

- does your ROM support AllShare Cast (and if no: do you know any workaround to make AllShare Cast working?)

Thank you for your hard work and time, and sorry if you felt attacked or accused before - that absolutely wasn't my target...
[Galaxy Note 10.1 Android Development] chappatti:
AHEM, AHEM.......I'M NOT THE DEV OR THE OP....JUST A SELF-APPOINTED MINISTER FOR JUSTICE. The OP and GrandMaster of this storm is ..................IOFTHESTORM..............taaadaaaaaa......!!!!!!! :laugh::laugh:

Let me put this ut there and then answer your questions !!!
[Galaxy Note 10.1 Android Development] eddy2302:
Hi guys :D I'can't understand how to make works my 64gb sd card...someone can help me?

Thanks!

Please use simple words, I'm not so good in english!
[Galaxy Note 10.1 Android Development] alirey:
Your sd card file system is exFAT?

I am not sure that Omni supports exfat.

Format it with fat32.

Search for a tool, that can format sd cards with fat32 and size is 64gb.

Windows Standard can only format max 32gb partitions with fat32.

Hope it was simple enough ;)
[Galaxy Note 10.1 Android Development] chappatti:
Yeah, I am friendly and helpful and, damn, I am always right....... Well that's what my momma told me!!!!!!! He, he, he:p:laugh::o:D:angel:
[Galaxy Note 10.1 Android Development] banderos101:
Run forest, Run........:D
[Galaxy Note 10.1 Android Development] eddy2302:
Thanks mate :) I used Partition Master and it works! Just another question, it ask me for "cluster size" is it right to put it 32kb?

Regards :highfive:
[Galaxy Note 10.1 Android Development] alirey:
16kb or 32kb is ok :)
[Galaxy Note 10.1 Android Development] iofthestorm:
Actually, Omni should support 64 GB exFAT. FAT is more likely to work but I did buy a 64 GB card after all the exFAT stuff was merged and it does work now. Not sure what the issue is that causes some cards not to work.
[Galaxy Note 10.1 Android Development] chappatti:
L.O.L !!! :laugh::laugh:

Yeah, and with my box of chocolates..........
[Galaxy Note 10.1 Android Development] kokero:
Hi again! Your .tar files worked so smooth! Thanks again! I'm currently using your ROM, and the only bugs I saw was unnamble to open Gallery and compressed pássword numbers on lock screen. Good ROM!