yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 General] havok115:
Okay

So CM released a 10.2, and I must say it works, albeit it works about as good as HumberOS. I would like to add I do miss some of the features Humber has in his side project, the Tablet UI is quite nice, and HALO is well, I don't care about HALO at all.

In any case I can assume CM has no plans to add IR, or anything like that which I believe Humber is planning on adding at some point.

All around, the CM 10.2 is quite solid, works fine, thanx for the release.

---------- Post added at 09:51 AM ---------- Previous post was at 09:39 AM ----------

So now is your build going to be based off of the 10.2 nightlies that CM released, just with your additions? Or are you starting with a base of like nightly 8/21? I guess what I am asking is if you pull down the CM nightlies and then modify them, or did you pull down a nightly a long time ago and continue moving forward with that image? Anyways, let me know, some of your additions I love in my tablet, so I might just continue to use your nightlies if you continue to work on them.
[Galaxy Note 10.1 General] Entropy512:
There's work being done on IR. Someone implemented it on the GS4 1-2 months ago at least, and the GS4 support works on N80xx. However the guys doing it want to try and do something that's cross-device and works with Samsung, Sony, and HTC - which is why the Samsung IR support hasn't been merged.

However I think the above goal is not possible - the IR interfaces are WAY too different between the three OEMs for there to be any hope of a common API.
[Galaxy Note 10.1 General] fstof:
Well, this is some good news

is updating from 10.1 to 10.2 as simple as installing a new nightly + new gapps?

I currently have 3 user profiles on it, will they all stay in tact?

thanks for any info
[Galaxy Note 10.1 General] iofthestorm:
Don't know about the profiles but otherwise yes, you can just install it over 10.1, with the new gapps.
[Galaxy Note 10.1 General] bleez99:
Installed the official 10.2 and GPS does not work. Full wipe install. Think it's a kernel issue. Reverted back to 10.1. [MENTION=3031478]humberos[/MENTION] has a fix for it in his builds but not sure if it will be in the official code branch in s timely fashion or ever.

When dialog fails, it's time for violence.
[Galaxy Note 10.1 General] Yemble:
GPS Broken on N8010 with CM 10.2

I can confirm that GPS is broken with all versions of CM 10.2 (as of 2nd Sep) on N8010 running N8013 variant of CM.

GPS is absolutely critical for me since I use my tablet for navigation. I would appreciate an urgent fix if at all possible... Please !
[Galaxy Note 10.1 General] fstof:
Indeed 10.2 GPS is busted... not a train smash for me will have to play Ingress on my phone then :P

my biggest gripe is the camera that is also still not working since 10.1
[Galaxy Note 10.1 General] havok115:
The camera is still broken in the 9/8 nightly.
[Galaxy Note 10.1 General] stunnedjack:
browser

Everytime I open the chrome browser is restarts my Note to the CM spinning logo. been like this for about 2-3 weeks.
[Galaxy Note 10.1 General] xX_Nexus_Xx:
Chrome is working fine for me...had same issue before but did a clean install with 10.2+latest gapps and it works (besides camera and gpsd issues as known)
[Galaxy Note 10.1 General] humberos:
Ok, I will upload this fix today later.

Please, wait next build.

Thanks.

Edited:

Uploaded: http://review.cyanogenmod.org/#/c/50829/4

Waiting review process.
[Galaxy Note 10.1 General] Entropy512:
i'm getting tired of Samsung constantly breaking those ifdefs...

Also of note, n80xx no longer has any active maintainers in CyanogenMod. Espen and I might do an n80xx bringup in whatever project we move to, if any, but neither of us are working on CM any more after the Focal licensing dispute.
[Galaxy Note 10.1 General] warp2:
[MENTION=3031478]humberos[/MENTION]

Thank You!
[Galaxy Note 10.1 General] Yemble:
Why is it that the CPU Frequency options within the Performance settings are greyed out for the I9300 and N8010 in CM 10.2? I thought that the whole point of custom ROMs was to enable advanced capabilities of devices not normally accessible in stock ROMs?

The Samsung CPUs can be overclocked, so why is CM blocking this?
[Galaxy Note 10.1 General] Ahmed_Mans95:
Cant find performance tab in settings, why?
[Galaxy Note 10.1 General] havok115:
HumberOS

What happened to HumberOS?
[Galaxy Note 10.1 General] iRoNX:
there is still someone who is working on the device for the new nightly?
[Galaxy Note 10.1 General] Entropy512:
At some point one of us might get it running with omni, but basically this device has a grand total of 0 maintainers who are still with CyanogenMod now.
[Galaxy Note 10.1 General] phearus:
Nice work driving away your contributors cyanogen Inc. Seems like a good start to business.
[Galaxy Note 10.1 General] weihan1102:
is possible to get multiwindow on cm?
[Galaxy Note 10.1 General] Ahmed_Mans95:
I updated to latest nightly yesterday then my home screen is all weird

http://www.imageshack.com/scaled/large/703/my9p.png

What do I do?
[Galaxy Note 10.1 General] greekunit690:
You need to change the margins in the launcher menu
[Galaxy Note 10.1 General] azm.azman82:
My wifi not working properly
[Galaxy Note 10.1 General] warp2:
download-notification-icons

the download-notify-icons can not be removed properly. if the download-notification-icons are removed from the status-bar, they will re-appear in the next few time.

How can i fix this?
[Galaxy Note 10.1 General] mfc_alpha:
Headset Mic

Is the headset mic working ?
[Galaxy Note 10.1 General] mfc_alpha:
Hello,

As I'm a developper in my every day I've solve the headset mic.

But, as I'm a noob on this forum, I cannot share the information on developpers thread.

Anybody can help me ?
[Galaxy Note 10.1 General] phearus:
Hmmnnn, you could try pushing the fix upstream (rather send CyanogenMod a pull request) push the fix to gerrit, etc.

If you go to the CyanogenMod website and sift about there you can find the names / aliases of our device maintainers. From there you can contact them and get the fix upstream.

Also, if you are a developer, and are familiar enough with our devices, I'm sure they would welcome another contributor - if you are up for it.

Oh look, here is a link to one-such page:

https://www.google.com.my/url?sa=t&...VdjU5o5UOh3biJmVw&sig2=NrrreP-g7-rE2DLQfOoC1A

:)
[Galaxy Note 10.1 General] Entropy512:
This particular device has 0 active maintainers in CM. We won't look at any reviews sent to CM gerrit.

I'm planning on eventually getting the device back up and running in omni, but I haven't gotten around to it yet. Someone else is of course welcome to do a 4.3/4.4 bringup of this device so it's ready in omni. (Neither of the N80xx maintainers have touched it since CM10.1)
[Galaxy Note 10.1 General] iofthestorm:
For the record I've done an Omni 4.3 bring up and it's my daily driver (really the work I had to do was trivial). I also made an attempt at 4.4 a couple weeks ago but back then stuff was seriously in flux so it was not really a usable build (touch rejection was not working when using the stylus, among other things). I will probably make another attempt this weekend and see how it is, and if it's reasonably usable I will push stuff over to Gerrit for review.
[Galaxy Note 10.1 General] phearus:
Bummer.

What is omni, BTW?

Edit: another ROM perhaps? This one:

http://omnirom.org/

Awesome - I had wondered if anything good was to come of the whole CyanogenMod Inc community back-stab. And they even have "open" in the title.

Nice-one community - FOSS FTW!
[Galaxy Note 10.1 General] Entropy512:
Yeah 4.3 bringup should be minimal, and tbh 4.4 shouldn't be too bad - I just haven't had the time. I actually -1ed some stuff on gerrit because it would've conflicted with n80xx devices. IIRC, touch rejection with stylus is a frameworks hack that I didn't think we even had in 4.3
[Galaxy Note 10.1 General] KuroKeita:
hey, is there anyone having the same pbl as me: can't use the microphone on any haedphone, earphone
[Galaxy Note 10.1 General] iofthestorm:
Yeah, the only difference with 4.4 was that I had to actually configure the recovery correctly since the last released version of TWRP for n8013 didn't support SELinux (when I did the 4.3 build I didn't bother properly configuring TWRP) and there were some framework hacks I had to cherry pick from 4.3 or comment out their corresponding overlay values. As it was my first attempt trying to do any of this stuff there was just a bit of fumbling in the dark (the only reason I got anything working at all was probably because xplodwild did stuff for i9300 first). At this point I imagine the same device tree should just work since there's now a TWRP configuration on smdk4412-common and people have been doing builds for the Note 2s.

Thanks for remembering us on the smdk4412-common patches, that was nice.
[Galaxy Note 10.1 General] phearus:
You two talking like this are getting me all excited inside. So, who's gonna start the Omni N80xx threads?

Can we assume that the Note 10.1 variants are gonna get official builds, sooner or later? That'd be awesome.

One last thing for you both:

[MENTION=3125261]iofthestorm[/MENTION] - are you going to make your build public before then? I appreciate that doing so would mean typical flood of annoying people at our doorstep, but still, it'd be cool to be rocking some Omni while we wait for the "real-deal" (for lack of a better term).

[MENTION=591147]Entropy512[/MENTION] - have you had anyone showing much interest creating Omni ports for Devices like the BeagleBone and the Raspberry Pi? Would Omni be interested in adding these to the supported list, if you had maintainers? I ask as I am playing with the BBone and the Pi, and would be very interested in getting involved with an Omni port.

Thanks Gents - sorry 'bout the wall-of-questions; Omni has got me all open-source excited about Android again!
[Galaxy Note 10.1 General] iofthestorm:
As a student with finals coming up, I personally don't have the time to deal with any support issues so I probably won't be uploading any of my own personal builds. If/when I get a chance to contribute stuff to Gerrit this may result in official builds, but I'll defer to more senior developers for that decision. The work isn't mine anyway, I just took the device tree Entropy512 and espenfjo made for CM and plugged it into the Omni source tree more or less. Although, if I do a multiwindow build I may throw that up somewhere with explicitly no support given as I imagine people might be interested in that.

I concur with the excitement though, this was the impetus for me to finally get off my as and figure out how to build a new ROM after not needing to for ages because most of the ROMs were already out there. I hope to contribute more in the future.
[Galaxy Note 10.1 General] Entropy512:
Pi is too weaksauce for modern Android.

BBone might be doable. I have the original (non- Black) version but just no time.

I also have a PandaBoard but it has always disliked my TV in Android with ANY Android build I've ever tried.

My next potential project is going to be a WandBoard (freescale i.MX6) if I have the time.
[Galaxy Note 10.1 General] iofthestorm:
Do you recall where the touch rejection hack might be? Like general file names or paths to look in? I've been trying to find it but have not been successful. I'm surprised there are people using it on the Note 2 without that feature, I find the Note 10.1 impossible to write on without it but maybe it's just the larger size that forces you to rest on the screen more, and maybe most people don't actually use the Notes for taking notes. I just did another 4.4 build for myself yesterday, it's definitely much smoother than when I last tried it.

Ah never mind, I did what I should have done earlier and used git log - - grep, found all sorts of useful stuff to cherry pick.
[Galaxy Note 10.1 General] phearus:
You're a tease, man! ;)

But seriously - do you have a public repo, say github, where one could clone your work / contribute back to it?

[MENTION=591147]Entropy512[/MENTION] - I dig the Pi's inferior abilities buzz. Oooh, have you seen the new Improv board from the KDE-Plasma / Vivaldi peeps - I think they are onto something there, with the upgradable CPU module. Also - the Vavaldi tablet with a similar modular approach is going to be awesome!

I think you misunderstood what I was getting-at. I am interested in maintaining / contributing to a BeagleBone / BBB of Omni ROM - though right now am testing the waters, etc. I am also interested in helping with the N8000 - so my next move is to get hold of some code and start building - see above.

One final aside for this post: like how Cyanogen Inc. hijacked community contributions - Omni has highjacked one of their threads! Haha, take that corporate-turncoats!
[Galaxy Note 10.1 General] iofthestorm:
Well, it was really espenfjo's thread anyway heh.

My GitHub account is linked in my xda profile (click on my name). There's honestly not much that I've actually done for this though, so I'd prefer if you didn't fork me - maybe sometime this weekend I'll try to initiate the process of having all the needed repos forked to omnirom and all that good stuff. I'll push what I've got locally there though but it's a pain to keep it up to date when you're cherry picking.

And you know what, I'll just leave this link here, since I feel bad for teasing, but with NO support implied whatsoever, this may eat your dog or cause zombie turkeys to destroy your house etc etc. I don't want to make a thread right now because I don't have the time to properly set one up and in any case I feel I shouldn't be a device maintainer anyway, since all I did was pull in stuff Entropy512 and espenfjo did. So all credit is to them. If you do decide to flash this, make sure to first flash the recovery I have uploaded there. All the recoveries on xda are out of date and don't support SELinux enabled ROMs such as those based on Android 4.4 (or at least that's my understanding). Make backups etc etc and don't post feedback here please.

[MENTION=591147]Entropy512[/MENTION] if you want me to remove this from the thread I'll be happy to oblige. But I figure this thread is already so off topic (and hell, the title hasn't even been updated since 10.1) it can't hurt to post this here.

http://xdaforums.com/showthread.php?t=2550308
[Galaxy Note 10.1 General] Entropy512:
Yeah, it's somewhere in frameworks/base... That's about all I know. I also need to pull in stylus gestures too.

Some of the recent work on the Oppo N1 may lead to some hints as to how to get stylus gesture screenshots to properly work. It doesn't have stylus, but it DOES have its own "special" input device.

LOL. Yeah, a lot of the Exynos4 CM threads now have omni discussion after most of the eyxnos4 maintainers jumped ship. Espen is also involved with omni, but in case you couldn't tell, even before the whole Focal mess he was mostly retired from maintainer work due to lack of time.
[Galaxy Note 10.1 General] iofthestorm:
I did end up finding it and submitting it to gerrit, and I added you as a reviewer whenever you get a chance - I realize you're very busy with other stuff of course, but whenever you get to it that will be cool. I've also set up device trees and all that and posted here: http://xdaforums.com/showpost.php?p=48011337&postcount=86 as well as made a thread for my builds here: http://xdaforums.com/showthread.php?t=2550308

Whenever you get a chance to take a look, I would really appreciate it!

One thing that's been worrying me is that I have experienced weird, sort of "analog" screen corruption issues. Eg. the outer edges will start to fade, especially the corners, or the images in the corners will suddenly become persistent temporarily - eg. even in recovery the clock in the top right was showing, but basically just a faded version of the image that was in the corners. At first I thought the fading was part of the Kitkat launcher, but then I realized it persisted across apps and then even when I rebooted into recovery. Powering down for a while fixed it.

I've also had the screen go all white after unlock, except for weird faded black corners as before - again, sort of analog looking in nature. One other person reported white screen after unlock but didn't mention anything about the corners. (I say analog because I've had other issues where I get lines scrambling across my screen, due to a loose LCD cable - I reinserted it once to fix the issues but then it came back again. Those were more clearly "digital" artifacts, hence I call this "analog". Also why I'm not sure if I just have had a bad unit for a year or if it's a problem with my builds.)

I had been running my own build of Omni 4.3 for about 3 weeks before I moved on to 4.4 and never had issues with that. I think 4.4 is where we moved to the Mali r3p2 driver, correct? I'm wondering if there's something wrong with the LCD driver for n8013 in those drivers, or something like that. Would it be possible to cause permanent damage to the screen? If so I'll pull my builds and tell everyone to downgrade to something else, but I'm not sure whether it's actually damaging since powering down for a few minutes seems to fix any persistence issues, and rebooting fixes the white screen.
[Galaxy Note 10.1 General] Entropy512:
It would be really hard to cause any permanent damage to the screen... But it sounds almost like your display cable might be failing again. Those symptoms sound almost exactly like what happened to my Nvidia SHIELD and that was running rooted stock firmware for days before the display started flaking out.
[Galaxy Note 10.1 General] mfc_alpha:
Let me know if you get back on this device.
[Galaxy Note 10.1 General] FPtje:
EDIT: I FIXED IT! :D

(this post was about the S Pen eraser not working)

I've found the problem! The palm rejection also rejected input from the eraser, since the eraser activates palm rejection, it never works.

I'm preparing a patch!!!

Edit:

http://review.cyanogenmod.org/#/c/56424/

I am over the moon with my first cyanogenmod patch.
[Galaxy Note 10.1 General] X-Stranger:
Just in case someone is interested in: dual-booting native firmware and CM 10.2
[Galaxy Note 10.1 General] FPtje:
Hmm, my patch is rather inactive. I think I read something about assigning a reviewer. Do I need to assign someone? If so, whom should I assign?
[Galaxy Note 10.1 General] iofthestorm:
Probably inactive because the N80xx maintainers left CyanogenMod. No one is actively developing it anymore, though there are probably some unofficial builds going around. However, sbrissen is still doing the LTE version so you could add him as a reviewer.

You could also submit it to Omni's Gerrit as well. There aren't official builds yet but I've been doing unofficial builds for n8000/n8013, and I'd be happy to incorporate your patch (see my signature for the thread). I'm working on getting nightlies but there's a few things I need to take care of first I believe.
[Galaxy Note 10.1 General] FPtje:
Alright, I added sbrissen as a reviewer. I looked at his threads and found that he should indeed look at it. He's the maintainer of the Note II, Note 8.0 and the SCH-I925 Note 10.1 (whatever that is). I don't think the bug applies to our device only. It should happen to all pen supporting devices.

I'm not sure about sending it to Omni ROM. Surely if I send it to your gerrit, I should also send it to ALL other AOSP/Cyanogenmod ROMs for ALL Note devices? I don't think I should be the one to take the initiative there, but correct me if I'm wrong.

I don't mind if you cherry-pick my commit. Please do!
[Galaxy Note 10.1 General] iofthestorm:
Yes, now that you mention it it should affect all Wacom pen bearing devices. I925 is just the Verizon Wireless LTE version.

Alright, I just wanted to let you submit it, but you're right, you should probably just submit it to the ones you actually want to use and other ROMs can cherry pick it if they want. Author is preserved anyway. I'll submit it to omni then, I always wondered why my Wacom pen from my old Windows tablet never supported the erasers on my Note 10.1, even though Android was supposed to support erasers. Actually, it's funny, I was the one who cherry picked the palm rejection patch for omni's 4.4 branch, I should have noticed then that it would have this effect on the eraser (of course, I wasn't really thinking about it at the time). Time to dig up my Wacom pen!
[Galaxy Note 10.1 General] FPtje:
I'm quite unsure what's happening to the patch. Steve Kondik said "let's get this into 11", but the status is still "review in progress". Is it my responsibility to also send a patch to 11?
[Galaxy Note 10.1 General] iofthestorm:
I think sbrissen is taking care of it, I got an email from Gerrit about it today. The tricky thing is that I don't know if there are even CM11 nightlies for N8013.
[Galaxy Note 10.1 General] FPtje:
There aren't. That's why I sent the pull request to 10.2.

Apparently arcee is asked to review it. I'm not sure why, but he's welcome the the stylus party.
[Galaxy Note 10.1 General] Entropy512:
I can't remember if I merged this to omni, but I'll merge the stylus patch tonight if I remember. :)

Omni is REALLY close for n801x (and should be ready for n8000 too... but espenfjo hasn't turned on his device in 6+ months and it really needs to be tested). Main holdups are a display driver cleanup in the kernel (we want to make sure we don't break other 4412 devices) and figuring out exactly how to properly handle the device rename. For months, n8013 builds have run flawlessly on n8010 and we have the asserts set for that, but to make it less confusing for users I want to try and name the builds n801x to make it more clear that both devices use the same build.
[Galaxy Note 10.1 General] iofthestorm:
Heh, you still have commit rights on CM after all that?

It's not merged on omni, the build bot said it broke the build for some reason even though it's a one line change and was fine locally. Maybe a dependency issue, I'll try rebasing and resubmitting it.

By the way, kind of weird to be communicating across random threads as well as IRC but since you mentioned it, I did do a bring up for n8000 as well with a handful of testers to confirm it works and they did confirm that everything was working equally well as the n8013 build. I did end up publishing a couple builds and according to my server logs there were several hundred completed downloads with no extra issues on top of whatever n8013 had (I borked audio on the first build due to the build.prop thing with audio_hw.c but we figured that one out pretty quick).
[Galaxy Note 10.1 General] FPtje:
Nice I guess I'll switch to omni then. That ROM sounds like it has nice stuff in it.

Also, do you have any idea why there's such a delay in the Cyanogenmod developers merging my patch?

I'm kind of nervous about it, but I'm also afraid to ask about it on the review page. I don't want to sound impatient or rude.
[Galaxy Note 10.1 General] Entropy512:
I'm 90% certain I no longer have +2 anywhere, so I'm the same as any other gerrit submitter.

Now I remember why I hadn't yet merged it. Silly buildbot. :) We should figure out a way that admins can override the bot if it derps without having to recreate a new PS. Maybe just a rebase will do... hmm...

No clue. They tend to do a poor job of reviewing external submissions from people they don't recognize.

(I admit, I even do this too on omni sometimes... Although lately I'm just way behind across the board.)
[Galaxy Note 10.1 General] benpaddlejones:
Hi all

Thanks to all the dev's and maintainers.

Does this mean end of the road for the N801x on Cyanogenmod???

Also can you share a link to OMNI for the N801x its not shown as a supported device.

Ben
[Galaxy Note 10.1 General] :
Yep, and that is a bit sad. Especially when considering that the official KitKat will be released around May this year, as stated by Samsung and Sammobile. com.