yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 10.1 General] khanh1289:
Can someone please tell me what bugs are still present under the latest nightly? I know there are weird audio? And I'm using 8013. I also assume cm10 for our device is 4.2.2 now right?
[Galaxy Note 10.1 General] Catalyste:
oh ok ... thanks for the info, guess i'll stick with stock then :)
[Galaxy Note 10.1 General] khanh1289:
Is anyone having problems downloading nightly 0520?
[Galaxy Note 10.1 General] kanute1:
Me too. It give me a md5 error.

Gesendet von meinem GT-N8000 mit Tapatalk 2
[Galaxy Note 10.1 General] :
Perhaps some camera issues, but as far as I know I would say none. But I have to mention that I don't use docks and that the feature to detect a pen distach has not been implemented yet. I contacted the dev about that one, but no response.

--

Sent with Tapatalk
[Galaxy Note 10.1 General] adamski123:
So what recovery do I need to flash the latest CM 10.1 nightly? (23/05/13)... I currently have the highonandroid one installed.

Thanks.
[Galaxy Note 10.1 General] AlienSr1:
You should be good on that one :), if it gives you an error try TWRP Recovery.
[Galaxy Note 10.1 General] Jason2k13:
installing flash

hi does anybody know how to install flash on the cm10.1 nightly?

On any browser will do
[Galaxy Note 10.1 General] :
Flash is obsolete for Android. Blame Adobe and ban flash websites.

--

Sent with Tapatalk
[Galaxy Note 10.1 General] gmfeny:
http://download.macromedia.com/pub/...roid/11.1.115.58/install_flash_player_ics.apk

Uhh thanks :confused:
[Galaxy Note 10.1 General] benpaddlejones:
Does anyone know the IP address or URL of cyanogenmod update servers. My work appease to have blocked them and I need to get them unblocked.

Ben :)
[Galaxy Note 10.1 General] :
Why would you employee bother to block those specific urls? :). Isnt it more likely that cyanogenmod is a rom and that it is blocked by filters on keywords based on that?

Just do a ping in command box or terminal to www.cyanogenmod.com and get.cm at home and you see the addresses.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Galaxy Note 10.1 General] benpaddlejones:
Thanks didn't think of that :)

I work in education we block everything fun and or educational...

:)
[Galaxy Note 10.1 General] :
You're welcome.

And considering CM ain't fun but purely a lifestyle, the block should be unmade! :)

--

Sent with Tapatalk
[Galaxy Note 10.1 General] The Troll:
details on doesn't work?

the OP seems outdated..
[Galaxy Note 10.1 General] benpaddlejones:
Given the news that Android 4.3 may have IR blast built in will this bring the IR burst back to our Note 10.1? Or are there still some missing OEM drivers?

http://www.slashgear.com/android-4-3-jelly-bean-will-have-ir-blaster-support-heres-why-30284325/

Ben
[Galaxy Note 10.1 General] Doud303:
Hello,

i have trouble with MX-Player, H/W decoder doesnt work with some avi videos andS/W decoder is reeeealy slow.

am i the only one having this problem ? is it reported ?

thanks form the rom goodness =)
[Galaxy Note 10.1 General] Entropy512:
Since none of the Exynos4 maintainers except possibly plodey are planning on working on the next Android revision for Exynos4 devices, doesn't really matter.

Exynos4 devices are currently on minimal life support with regards to CM, and have been for months.
[Galaxy Note 10.1 General] benpaddlejones:
Thanks, so does that mean we might not see CM11 ???
[Galaxy Note 10.1 General] :
Why not? If the blobs are compatible it should work.

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Galaxy Note 10.1 General] iofthestorm:
That post is purely speculation, he's basically just saying "these devices with stock Android will have IR blasters so the next version of Android should support it". At this point we don't know what "stock Android" on the GS4 or One actually means in terms of open source support. In any case, I'm pretty sure it would require significant effort to make the drivers for our tablet match any hypothetical API that Google introduces in the future, and such an API would almost certainly not support any existing apps like Peel which I presume are using manufacturer specific APIs. But it would be cool to see it happen, I'm just very doubtful that it actually will.
[Galaxy Note 10.1 General] fstof:
Well 4.3 having native IR support won't be too far fetched...

I stand corrected, but wasn't this the same with NFC? I think Samsung had some NFC support in its ROM's before Google added it to AOSP... I'm just guessing here
[Galaxy Note 10.1 General] Entropy512:
Not likely unless Samsung makes major changes (like actually keeping a promise they make to the community) or we get some fresh maintainers on the exynos4 platform - existing ones are tired of the endless bashing of heads against a wall.
[Galaxy Note 10.1 General] phearus:
Having read your post and wondering "how can Samsung not supply semiconductor information about a device they sell to other OEMs" I found this page:

https://www.samsung.com/global/busi...ct/application/detail?productId=7745&iaId=844

It has a download link to a data sheet (called "user manual" here) that explains all the tech and peripherals of the Exynos4 devices - not the best data sheet - but certainly not the worst I have seen. Also, the device has a Cortex A9 core - you can download endless technical data about this intellectual property directly from ARM. Everything any decent hardware engineer could ask for.

So I am starting to think that all this hating on Samsung about their device and lack of communication regarding it is completely unfounded. What's more, I think the problem here is not the Exynos4 device itself - it is note10.1 motherboard and daughterboard interfacing ignorance. Now Samsung cannot be called out for protecting their IP in this regard. The Note 10.1 device is not open hardware - it is proprietary technology developed and sold commercially. Why would Samsung release the specific details of this when in all likelyhood it would be used by their competitors to build cheaper clones of the tablet, as well as us Android development nerds?

There are other ways to figure out what is going on with these daughterboards. - though I am unsure of the legality of this. Has anyone actually opened their tablet up and applied a logic sniffer to the interface? My bet is it is I2C or some SPI protocol. Hell you can look at the daughter board's component names and numbers and get a whole lot of info regarding what is going. Regarding the io ports used to drive the device - there are only a limited number of serial peripherals on the Exynos4 - look at the data sheet for their exact pin numbers and config details - from there it is just a matter of trial and error - assuming of course a serial interface and protocol.

If we really want these features, I am sure someone will be willing to put in some of this groundwork. I would, but I have a PhD to complete, and 2 fulltime jobs, not to mention a family, countless Star Wars and other Sci-fi books to read, amongst other commitments.

We as a community really do need to stop hating on Samsung for protecting their business interests - or we are really no better than patent-trolls like Apple. Instead of complaining in our forums, how about doing something pragmatic about the situation.

That all said - I don't even miss the IR - never even used it when I was on stock - and I even have a Samsung TV!
[Galaxy Note 10.1 General] Entropy512:
I've read the datasheet. Note that it has zero information on FIMG2D (FIMG doesn't even appear ANYWHERE in the datasheet), and next to no information on MFC (just a few clock references). There are major subsystems in the Exynos4 which the datasheet either does not mention whatsoever, or just has bare minimum references to which registers control their clocks.

TI's datasheets are more complete AND they have functional reference source at omapzoom and other locations

Qualcomm does not provide datasheets, but they DO provide robust reference source code with complete history at CodeAurora that is updated on a regular basis. - It's rare to see release tags more than 2-3 days old - https://www.codeaurora.org/cgit/quic/la/kernel/msm/ as one example

Samsung has NOTHING that comes anywhere CLOSE to OMAPzoom or CAF - we have incomplete datasheets, and reference source that dates back to some time in between Gingerbread and ICS

If you had done any research into the problems we are having, you would have seen that all of our problems are with internal functional blocks of the Exynos4 (mostly the graphics subsystem) and are common to ALL Exynos4 devices in CM. The external stuff (hung off off of the chip with I2C, SPI, whatever) is NOT a problem, since those are all handled by the kernel, for which we DO have source code. So no, sniffing I2C/SPI/whatever buses would not help us in the slightest.

If the problem were with peripherals and not the core SoC like you claim it is - why is it that the d2 family is so much easier to support than the i9300, despite having the exact same screen, wifi chip, bluetooth chip, etc? Guess what the only difference is? The core SoC itself and the support chips (most SoCs are tightly integrated with their PMICs)
[Galaxy Note 10.1 General] MTAlmeida:
Hi Entropy512 .. long time no "see" ! .. since I sold my G.Note N7000 and got the Nexus 4 !

Now I got the N8000 ... and I'm glad to see you around here...

.. but, as I can see, the "Battle against Samsung's ineficiency" haven't change, hum !
[Galaxy Note 10.1 General] phearus:
Hey - my bad. I'm not trying to step on anyone's toes - just trying to help.

Seems kind of self-destructive on Samsung's part to hold out on the details of the tech - I believe you that they are - like I said I only looked into it briefly. Guess they are not really interested in selling many ICs to other OEMs. Sigh.

Point me towards the core body of the Exynos4 work - research has to start somewhere - and I will dig a little deeper; if new blood is what you want then I can try and get up to date with your progress and difficulties/challenges, and help-out where and when I can!

Thanks for clearing this up.
[Galaxy Note 10.1 General] Entropy512:
hardware/samsung/exynos4 - One of the biggest issues right now is the fact that our hwcomposer is pretty much "vsync passthrough placebocomposer" if you allocate video buffers from ION memory instead of FIMC1 memory. In addition, Samsung has made major changes to hwcomposer since the version with source posted at http://git.insignal.co.kr/samsung/e..._slsi/exynos4/tree/libhwcomposer?h=exynos-ics - There's an entirely new compositionType in use, and much of the decision logic of which compositionType to use is different. Unfortunately Samsung's compiler inlined a bunch of stuff, so Hex-Rays decompiled code is a nightmare to read.

The other big problem is the fact that Samsung considers whatever trick they used to keep Mali r2p4 from leaking memory like a sieve in Jellybean some super-ultra-secret. The end result is we keep on having to use r3p0/r3p1 Mali blobs from leaks (since almost all official releases are staying with r2p4), which are frequently unstable as hell. The latest r3p1 blobs suck less - but hey, it took us nearly a year from Jellybean's release to get them!
[Galaxy Note 10.1 General] dpwhitty11:
Just found a little bug, not sure if its been reported yet.

If you have a PDF opened in the adobe reader app, and you're in another app, trying to switch into adobe reader while it still has the PDF loaded will result in a SystemUI force close. Recent apps then doesn't open again until the screen is turned off and back on.
[Galaxy Note 10.1 General] benpaddlejones:
Anyone else got the "System UI has stopped" from latest nightly"?

Had to do a clean install
[Galaxy Note 10.1 General] MystereT:
I do, on fresh install from stock, made correct factory / cache, etc

retried many times but still system UI issue

Running on N8010 on latest 20130704 n8000
[Galaxy Note 10.1 General] Airtioteclint:
Same. I retried with a few different gapps package and it did not work. N8013.
[Galaxy Note 10.1 General] :
I had it too. Reverted back to nightly of 3 july.
[Galaxy Note 10.1 General] ranjitpai:
Galaxy Note 2 N7100 - CM 10.1 - Car Bluetooth issue

I have CM 10.1 flashed on a Galaxy Note 2 N7100. This is my first custom ROM and I absolutely love it but ...

I am facing the following issues.

1)When I connect my phone via Bluetooth to my car stereo and try to access Phonebook, Recent calls etc. my stereo says "Feature Not Supported".

2)Bluetooth audio I connect my phone to the stereo and play songs on Apollo but the Track/Artist etc. are not showing up on the stereo.

On stock Samsung ROM these features were available.

Am I missing some A2DP drivers or something?
[Galaxy Note 10.1 General] Eric-Mod:
This is the Galaxy Note 10.1 Forum :cowboy:

Here is the Galaxy Note 2 Forum Disussion Thread : *Click*
[Galaxy Note 10.1 General] abamann:
Send to ROMManager Direct Download: cm-10.1-20130705-NIGHTLY-n8013.zip

md5sum: 964173474df724d5e57b67fa8d493013 Short URL: http://get.cm/get/91I

System UI has stopped"

---------- Post added at 03:46 PM ---------- Previous post was at 03:32 PM ----------

two updates failed in systemUI ... weird
[Galaxy Note 10.1 General] espenfjo:
It will be fixed in tomorrows build.
[Galaxy Note 10.1 General] abamann:
Fixed in 0706, perfect! :thumbup:;)

Inviato dal mio GT-N8013 con Tapatalk 2
[Galaxy Note 10.1 General] manni2:
I just updated to nightly 0718 from a nightly which was like 2 months old and can't get the screen to lock.

Will factory reset in a few minutes and let you know if that fixes things.

Update: factory reset did fix everything.
[Galaxy Note 10.1 General] stunnedjack:
couple of questions

2 questions

The first, I see in the screenshots that the home, back and recent buttons are on the far left side but when I flashed this rom, and they are in the middle, was this changed in a newer nightly, I am new to this version and installed the newest nightly.

2nd, I also see that the notification and status bar, are on the top on each side, and in other screenshots and videos they are on the bottom, so is this a new nightly change again.

The reason I am wondering is they are not really located in good locations to me for a 10.1" tablet.
[Galaxy Note 10.1 General] FPtje:
Welcome to android 4.2.2. It's not a decision from cm, it's one from Google.
[Galaxy Note 10.1 General] stunnedjack:
oh

Oh, I didn't know that. Kinda sucks cause I liked how it was setup before.
[Galaxy Note 10.1 General] Entropy512:
Yeah... we never got around to updating the screenshots. All of the exynos4 guys were totally fried by the time we got 4.2 semi-working.

hell one of my threads still says 4.1 even though it's 4.2 now...
[Galaxy Note 10.1 General] fstof:
I see the last couple of nighties that the camera is broken again :(

Not a train smash but still too bad

Can anyone else confirm?
[Galaxy Note 10.1 General] blair287:
i cant flash cwm recovery everytime i flash it it still boots to stock recovery
[Galaxy Note 10.1 General] :
Camera works for me.

--

Sent with Tapatalk

---------- Post added at 09:14 AM ---------- Previous post was at 09:13 AM ----------

Anyone with a not working signal indicator for the mobile connection in the status bar/notification tray?

--

Sent with Tapatalk
[Galaxy Note 10.1 General] :
Anyone?...

--

Sent with Tapatalk
[Galaxy Note 10.1 General] :
Same, the camera's preview freezes after taking a photo. If it was working before, why would they change it?
[Galaxy Note 10.1 General] havok115:
Same Issue

I have the exact same problem with tonight's nightly, I take a picture and it hangs up on the last picture, the only way I can take another picture is if I close the camera app, and restart it.

If anyone figures out a fix for this I would appreciate knowing.
[Galaxy Note 10.1 General] iofthestorm:
I hear rumblings in other boards about IR support coming in CM, any chance it could come to N80xx? Referring to http://review.cyanogenmod.org/#/c/44580/3

I don't care strongly one way or the other, since I rarely watch TV and rarely use my tablet for anything besides note taking and watching movies, but it'd be cool to have that capability. Though I guess we're not getting official 10.2 nightlies so that's not super relevant anymore maybe?
[Galaxy Note 10.1 General] Entropy512:
There's a set of 10.1 patches that give IR support to N80xx, but they've been held up in review while people try to figure out a way to have "common" IR support across all devices that support it. In my opinion this isn't possible, as the HTC, Sony, and Samsung IR interfaces are so vastly different.

We might eventually get 10.2 nightlies, but I haven't even touched 10.2 on any of my devices yet as I'm trying to finalize 10.1 for find5 (minor cleanups) and wifi Tablet Z (GPS is still borked, once that's fixed it goes to RC).
[Galaxy Note 10.1 General] havok115:
Camera still broken

After last night's nightly, I thought my camera would be fixed, but it is still broken when I take a picture it freeze on the preview. Any chance this will be fixed soon? Anything else I can provide that would be helpful?
[Galaxy Note 10.1 General] Entropy512:
Probably not going to be fixed soon since this device is pretty low on everyone's priority list right now. Likely not until the weather stops being so nice, which greatly reduces time spent on any of my devices. :)
[Galaxy Note 10.1 General] havok115:
Figures....

Yeah I kinda figured, I don't even know why I bothered to post to be honest, because I almost never use the camera on the thing. I was just wondering. I really wanted 4.3, but it looks like that is a long long ways off, that also makes me sad, especially since they started 10.2 rollouts of the Verizon Note 10.1, which I believe is similar hardware. Oh well, guess I just wait and see what happens!

Thank you for the reply....
[Galaxy Note 10.1 General] theprogram1:
humberos has cm10.2 built for the Note. It worked fine for me on N8013. It's in the CM10.1 thread, around the end.
[Galaxy Note 10.1 General] iofthestorm:
Yeah that's the impression I got, seems like they'd need to provide all three APIs to get anything useful done, which seems like a massive kludge if they could do it.

I'm not in any rush for 10.2, I know humberos has some builds out and I personally haven't updated my tablet in months anyway. Whenever you get to it that'll be great, I know how much you hate Exynos devices.
[Galaxy Note 10.1 General] havok115:
HumberOS

I installed HumberOS two nights ago, very buggy, but it does indeed work. I have some serious issues though. I will likely drop back to CM10.1, but I really am in need of 10.2, I have 4 younger children and I would love to have the restricted access on my tablet. I will likely wait for the CM team to really start to move on this product.

Let me ask a question, how much different in the SCH-i925 than the N8013. I run into the Assert problem when I install updates and such on my tablet, and so I know how to remove that from the script, but could the i925 device Image load and work on a N8013? I believe they are similar hardware, but I am not 100% sure. I don't want to waste the time even trying if there is no point.

In any case I am excited and can't wait to have a more stable version of 10.2 for the N8013, please let me know if there is anything I can do to help with this project?

---------- Post added at 10:15 AM ---------- Previous post was at 10:09 AM ----------

Also, just wanted to say I just noticed a new update on Humber's download page. He has a nightly 8/27 version now.

Sorry I am too new a user to actually create a link....
[Galaxy Note 10.1 General] Entropy512:
Many of the bugs are probably common to all Exynos4 devices. The usual mess...

There's not much you can do to help - the problem lies with Samsung.

As far as the I925 - I'm fairly certain it has a Qualcomm modem, and may have other differences. Since it uses a Qcom modem, it almost surely has a different partition layout than the N80xx, although even if it doesn't, you are guaranteed to lose 3G if you flash an N801x build.
[Galaxy Note 10.1 General] havok115:
Well then....

Well, my N8013 is Wifi only, so the loss of 3G is not a big deal for me. However, Humber's new build is a lot more stable than the 8/21 build. I wanted to post to his new thread, but I am too new a user here at XDA. So, for now I can do nothing.

Do you know, Does Humber code for CM directly, or is he just doing this as a side project?
[Galaxy Note 10.1 General] Entropy512:
Side project... He occasionally submits to Gerrit but not often.
[Galaxy Note 10.1 General] humberos:
Yeah!

I forked all sources from official CM but my build is a side project.

The main difference between official and my builds are:

Kernel Source (merged with latest kernel.org - my github)

android_framework_base (sgt7 repo)

android_package_apps_Settings (sgt7 repo)

android_package_apps_Trebuchet (sgt7 repo)

We have a lot of work (for tablets) in sgt7 repos.

At least all sgt7 repos were created for Galaxy Tab 7" (P1000) and them have many features preserved for Tablet UI. All thanks to @sbradymobile .

I am a newbie android developer and by following great devs like @Entropy512, @espenfjo, @cdesai, @codeworkx, @pawitp, etc, I am trying (day by day) to learn more a little bit.

Thanks!
[Galaxy Note 10.1 General] havok115:
Graphical issues

I can't post in the official 10.2 HumberOS thread, however I tried the Graphical Fix someone provided:

Hello to all,

cm team solved the graphical glitches. Works for my S3 and N8010.

Edit the build.prop file in the system folder:

OLD: hwui.render_dirty_regions=false

NEW: debug.hwui.render_dirty_regions=false

--> reboot

Seems to work for me, my N8013 has no more glitches in the graphics, so you can add that on your next build. I am running your 8/27 build on my Tablet at home myself, and if there is anything I can do to help you move this process along I would be more than happy to help. Seems to be fine, the graphics glitches, where things get funky is now gone, however Netflix is still not working with the patch above.

Let me know if there is anything I can do to assist you in getting all these things working. I have to assume it has something to do with the graphics drivers.
[Galaxy Note 10.1 General] FPtje:
Edit: I somehow doubt that is the problem. It would be silly if the problem was a variable being named wrongly. Something like that shod be found with debugging.

I know little of these things, though, so I can be wrong.
[Galaxy Note 10.1 General] havok115:
Maybe, Maybe not.

You could be right, however the glitches that I saw in Firefox, were quite simple, when I turned my N8013 to portrait the Address bar did not properly change, it was left stretched and out of sync. When I just opened Netflix, the screen would go black or get stuck on the login page, but if I clicked the actual Netflix browser would be there, but the screen was a streched version of the login screen, and as I clicked around it would finally refresh itself, and turn out okay.

As of 8am this morning Central Timezone, I updated my file, and have not experienced any glitches of the like since. I can't load any videos in Netflix, but the app itself loads properly with no glitches, when I click on a video it just hangs at loading, and never starts the video, and my firefox now switches back and forth between Landscape and Portrait without any address bar stretch. So I have to assume this does indeed fix a lot of the glitchyness in the OS, however there are still graphics problems, which I assume are driver related, but this did clear up quite a bit of the little glitches that were indeed there.
[Galaxy Note 10.1 General] Entropy512:
Netflix is broken on all Exynos4 devices in CM without horrible hacks (one of them being my Xposed module, which is linked to from somewhere in this thread...) - it's one of the number one reasons no Exynos4 device should have received an RC1 build last night.
[Galaxy Note 10.1 General] FPtje:
I'm quoting an old post from January here, but I just got an s pen with eraser for my birthday. My apps do not detect the eraser, which is a real shame. I am on nightly 27-08-2013, which is the latest as of now. Is there anything I can do to help debug?