yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] dbrickg:
Well, that's the weird thing. All the data is still there. I can see it in any file manager once the OS comes back up. It's just that TWRP (2.8.7.5) can't see it. It can't even see the backup I made this morning, after the sdcard change happened. I renamed the backup from ROM Manager, and TWRP can't see it now. It can't see the older one of my cm12.1 OS, either. But it can see the backup I made later, the one I didn't rename.

Also, the built-in file manger in TWRP doesn't work. I click on the button, and it does the little animation to show that it's been pressed, but nothing happens.

On the other hand, it turns out I can turn the nook back on with the power button... sometimes. That problem seems to be intermittent. I don't know, but it "feels" like the nook is just too busy to turn back on sometimes, and sometimes it's not so busy.
[Nook HD, HD+ Android Development] third_degreee:
This Marshmallow is running smoother than ever, great work.

Does anyone have their WiFi connection constantly switch off when the tablet is on or even when it is off?

It's so annoying!
[Nook HD, HD+ Android Development] bruce7890:
Ok - let me know
[Nook HD, HD+ Android Development] RhinoNelson:
My only 'issue' with wifi has been: It works at home, it works when I get to work and finds the new wifi network flawlessly, when I get home in the evening I lose wifi connection even after specifically telling it what network to connect to. Re-boot and the cycle starts all over again.....Certainly not the end of the world, just another of life's (Android's) quirks.
[Nook HD, HD+ Android Development] belfastraven:
Optimization etc.

[MENTION=4473900]amaces[/MENTION]

re cm-13+optim runs

First, I fixed problem in build/core/Makefile

replacing this

ifneq ($(ARCHIDROID_IGNORE_RECOVERY_SIZE),true)

$(hide) $(call assert-max-image-size,$(1),$(BOARD_RECOVERYIMAGE_PARTITION_SIZE))

endif

with

$(if $(filter-out true,$(ARCHIDROID_IGNORE_RECOVERY_SIZE)),

$(hide) $(call assert-max-image-size,$(1),$(BOARD_RECOVERYIMAGE_PARTITION_SIZE)))

Apparently, you can't use IFNEQ, IFEQ... inside a definition.

I had repo synced on the 17th and have built with O3, O2, and Os optimizations. No problems except for needing to add

1.

-freoder-blocks and the -freoder-blocks-and-partition flags to the list of flags to be ignored by CLang, in the Archidroid.mk file.

2.

LOCAL_CFLAGS += -Os in the frameworks/av/services/audioflingerAndroid.mk

The builds don't "feel" any different to me, and geekbench differences are trivial.

If there are any additional flags you want me to try, let me know. Some are commented out in the experimental section of the Archidroid.mk: some seem to require that GCC be configured a particular way, and I don't know whether it is or not. I've been looking around on the web and I'm not seeing much information on optimization of Android beyond the Ox packages and the Archidroid additions already being used, but I'll continue to explore.

I see you are building kernel with the 6.0 UBERTC toolchain now. What are you using for the non-kernel rom build?

P.S. I have been building for Ovation, also, but will cease doing that if you don't want to test the roms.

PPS I am not having trouble with MTP vs. charging on hummingbird, and WiFI has been fine. I am currently running with todays kernel (1.20) in experimental over your 1/17 rom on one nook HD and over my 1/17 O3 optimized build on another...
[Nook HD, HD+ Android Development] dbrickg:
Thanks for the offer. As amaces points out, but I didn't know, all his older releases are available in his "obsolete" folder:

https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3262390066

So, I've downloaded the 01/10 cm zip, as well as a couple of other goodies :)

PS: and, as I noted a post or two ago, my HD+ has started behaving better. The power button now powers it on again. Not sure why it stopped earlier. It felt like it was maybe just too busy to pay attention to the power button. And I was too impatient to wait for it.
[Nook HD, HD+ Android Development] brenyoka:
Constant WIFI issues on the latest Ovation build (CM-Ovation - 1/17/2016). Like always, I do clean install.

Keeps forgetting passwords after disconnect and reconnect. Worked before the 1/10 build, but haven't been long on the 1/10 one to know whether the problem was introduced in the 1/10 or in the 1/17 builds.

Also, why was the title changed - to a much older date?
[Nook HD, HD+ Android Development] TeutonJon78:
Mine was doing that on the 20160110 build, but stopped on the 20160117 one. At the end of every video of Netflix it would cycle off.
[Nook HD, HD+ Android Development] sasmith-129:
I ran the MM/CM 01-10 build (clean install) for about a week and updated (dirty flash) to the 01-17 build yesterday. The only issue I've seen is occasional screen flashing, seemingly relayed to overlays. I've seen it on both builds and it typically happens when I pull down on the status bar to view notification details and then tap on one of the notifications. It is reminiscent of some flashing in the early CM12.1 builds.

Very nice job [MENTION=4473900]amaces[/MENTION], no way I'm going back to CM 12.1. Thanks for your neverending hard work!
[Nook HD, HD+ Android Development] belfastraven:
Great. I'm just curious--do you know how it determiners sunrise and sunset? I hope it's not via a sensor--otherwise we will all be in perpetual daylight or darkness, I fear. I've noticed that playing with the color temperatures/intensities works in live display, and in trickster mod, but that the develop options

simulate color space doesn't seem to do anything.

They indeed differ. I'm not on my unix system right now, but think 02 and 03 are very close, and Os is maybe 7Meg smaller. On my system, it takes about 10 minutes longer for the optimized compiles. Have you ever looked at post-linking optimization (for C) or the dex optimization that facebook has been touting? I will look into the sources you have pointed out to me, and I will continue to build for ovation, although I'm not ready tobe a public build purveyer yet (since I'm still not sure of what I am doing don't have any good place to purvey from ;)).

By the way, on the rom that was included in the 1/17 build in experimental, I could get antutu benchmark to work. On previous recent roms and with the lastest kernel, the nook HD reboots in the middle of the 3d test. (It can never run the 3d test, but on that one rom, it didn't reboot.) The score I got was 33483.. not bad for a 3 1/2 year-old device.

thnx, boss:)
[Nook HD, HD+ Android Development] acr123:
By the way, on the rom that was included in the 1/17 build in experimental, I could get antutu benchmark to work. On previous recent roms and with the lastest kernel, the nook HD reboots in the middle of the 3d test. (It can never run the 3d test, but on that one rom, it didn't reboot.) The score I got was 33483.. not bad for a 3 1/2 year-old device.

thnx, boss:)[/QUOTE]

I updated from 1/10 to 1/17 in hopes of also getting 3D test to finish. I was,however , unable to get the 3d test to finish. I tried a few different launchers and changing some developer option settings such as force GPU rendering, lowering animation settings from 1x to 0.5x, etc but could not get the 3d test to finish.

Any suggestions.

Al
[Nook HD, HD+ Android Development] belfastraven:
I never actually got the 3d test to finish--it's just that I was able to get the rest of the tests to run. For me, (on hummingbird--Nook HD), the three D test runs first and normally my nook reboots in the middle of it. Is that what is happening to you?
[Nook HD, HD+ Android Development] acr123:
Using Nook HD+ ovation. Yes. if I run the 3d test separately it shows some frames and then slows down and finally reboots the Nook. If I do the entire benchmark test it says the 3d test could not be done and I get the main scores for the other 2 sections for a total of about 23000.

Al
[Nook HD, HD+ Android Development] belfastraven:
It sounds like you may be running and older version of Antutu. I am running the latest version (6.04-3d, 6.01 non-3d). I believe the way they are measuring has changed. With this version, if the nook reboots in the 3-d benchmark, the others won't run, and their is no way to tell it not to run the 3d benhmark. The only reason I've been trying to use it is that I am playing with code optimization and am trying to get some objective measure of whether what I am doing is making any difference.
[Nook HD, HD+ Android Development] acr123:
I'm using the same Antutu versions as you are 6.01 and 6.04. If you go to the menu at the top left, you can select 3d benchmark only - which is what starts and doesn't finish and then you get a reboot.. If you run the entire benchmark the 3d section is unsupported, but the UX , CPU & Ram sections do run. I'm not sure what you are referring to. Did you EVER get the 3d section to complete?

Al
[Nook HD, HD+ Android Development] vinceweis:
In my very short experience since trying the new kernel, I see less lag between touching an item and it opening. Seems very responsive. So far, it appears to be a huge improvement. I don't do gaming so I can't comment on that.
[Nook HD, HD+ Android Development] belfastraven:
No. Never would run 3D. But on my HD, antutu always tries to run 3d first and there is no way to stop it from trying. Only once, as I mentioned before, did it successfully run the rest of the tests. Pprobably not important..
[Nook HD, HD+ Android Development] dbrickg:
Good to hear that TWRP is working on a major update! As for the backups, I'm not very worried about them. It looks like they're still there. Even the current version of TWRP sees them, as long as I don't rename them. For some reason, they disappear in TWRPs "Restore" after I rename them. Thanks again for all your work supporting our Nook HD+s and responding to our various issues!
[Nook HD, HD+ Android Development] belfastraven:
Makes me think that perhaps TWRP keeps track of the names/locations in a file/database--it does allow you to specify a name at backup time. Just as a test, have you tried renaming a backup to the name/location where it was first first backed up.? I know that by default TWRP usesa pretty long string of numbers which I would't remember :) . You could test by naming the backup something memorable when you make it, renaming it, making sure it isn't found, and then renaming it to its original name and seeing if it is found.

---------- Post added at 07:25 PM ---------- Previous post was at 07:02 PM ----------

@amaces,

the latest hummingbird rom is generally OK. File Manager is not working properly--I synced and built yesterday also, and it doesn't work with my rom either. I think it's a cm issue. You cannot view the contents of any directory, starting with root. When you select the directory nothing happens.

The TWRP file manager see everything, but I notice that emmc/0 usedto point to the internal "sdcard" and doesn't seem to do so now.

IN the Storage and USB setting, you can "explore" the internal sdcard.

Other than that things are working well, so far.

IF I compile the kernel that I have from syncing your repository with the UBERTC 6, will I be getting the same kernel you are using in the roms you post? (I realize you are working on the kernel--I understand the timing issues)

thnx.
[Nook HD, HD+ Android Development] dbrickg:
Yeah, that's almost exactly what I meant to try this weekend... but I got distracted :) I think the original name is retained in the name of the directory where the backup is stored. But it is kind of weird, since I used to be able to change the name and yet still find the backup in TWRP. I'm hoping TWRP 2.8.8.0 will be available soon and it will fix the problem. Either that or something else fixes the problem. But, as I said, I'm not terribly concerned about it. So far the release is stable enough that, with any luck, knock on wood, etc., I won't ever have to restore from one of the lost backups :)
[Nook HD, HD+ Android Development] smileyint:
Bluetooth is working properly again. Wifi problem with PEAP,MSCHAPV2 remains unchanged. Buttery smoother touch response. Thanks Amaces.
[Nook HD, HD+ Android Development] amaces:
I'll take another look at the Wi-Fi logs, although those WPA2/Enterprise ciphers are widely used (on many campuses, for example), and would have expected lots of other reports about this.

P.S. You should remove the attachment, and change all the passwords in wpa_supplicant.conf (including wherever you're reusing them). They're available in plain text and I'm sure you don't want that.

Didn't even notice issues with the CM File Manager; I've been using Solid Explorer for a long time. They must have broken something in that app since I don't see filesystem issues. Otherwise, do you mean some sort of built-in file manager inside the TWRP user app, or in actual recovery? The former would make sense, but no reason for the latter, unless you built your own TWRP image.

No reason not to, especially that kernel's build system and options are more or less separate. As you noticed, I push local changes pretty quickly after I test them, almost obsessively so… By the way, I've been un-forking/reverting some repos in the manifest to CM upstream (e.g., system/core). Except for Nook-specific stuff, upstream has everything needed; build, bionic, omap4-next will probably follow soon. This would prevent out-of-sync issues whenever changes happen quickly upstream, but if you need specific optimizations (i.e., in build), a local manifest is equally good.

Then I must've misread, and your issue is different; next major TWRP will probably not help there.
[Nook HD, HD+ Android Development] belfastraven:
The issue seems to have been partially fixed: I still can't look at tombstones--the permissions are wrong, it (it was a CMFilemanager issue in the next nightly). I synced last (Monday) evening and am running my build now. I have an an ovation build from the same sync, compiled with the UBER 5.3 cortex-a9 specific toolchains. Just in case you want to try it--if not, I'm not insulted ;). If you ever want to try my builds, what might be a good place to put them?

I'll start using the precompiled UBER 6 for the kernel builds.

I could tell over the weekend that you were working on things. Sunday evening I finally gave up and re-inited the repo. I also now know how to "stash". :) I'm still testing flags. I'd love to be able to get -profile-generate to run, because I think there may be more "bang-for-the-buck" with doing that kind of code-specific optimization, as well as the post linkage optimization.

PS. I think that Screencast not running becuase of Ducati OMX API errors. Do you want logs, or should we just build without the app?

---------- Post added at 05:54 PM ---------- Previous post was at 05:36 PM ----------

[MENTION=4473900]amaces[/MENTION]--take a look at this

https://code.google.com/p/android/issues/detail?id=188867

I t seems that this was a widely reported problem, but is caused by server-side issues. Probably those having these problems need to report them to the sys admins.
[Nook HD, HD+ Android Development] sasmith-129:
It seems the 01-24 build introduced an issue I had run into late in the 12.1 series of builds (10/18 to be exact). I last commented on it in post 1396 in that thread.

It only seems to affect this one game that is fairly graphics intensive but it's a popular game and I haven't seen similar problems reported on different hardware/ROMs.

I guess I'll revert to the 01-17 build for now to satisfy my addiction for this game.
[Nook HD, HD+ Android Development] smileyint:
Thanks Amaces.

Removed attachment.

Didn't expect password to be in clear.
[Nook HD, HD+ Android Development] belfastraven:
see my post #330 and herehttps://code.google.com/p/android/issues/detail?id=188867

You might need to talk to the sysadmins--it may be a server-side issue. Sorry, I forgot to include you in my initial response.
[Nook HD, HD+ Android Development] amaces:
That's odd; I'm hoping that it doesn't come from upstream changes; can you test the current experimental build, which is compiled a bit differently?

So, the whole ROM can be compiled with a 5.x Android EABI now? About permissions, you must mean that CMFIleManager cannot see those files, because shell and other tools work fine. Again, we must be precise about these things; I don't really care about what CM decides to break in an easily replaceable user app, but actual filesystem changes are different.

You have many options for these quarter-GB files; I'm using Box, but Dropbox, GDrive, etc. would all work. Otherwise, it sounded like bandwidth was an issue; I'm assuming upload even more so, and you shouldn't make the effort just for my benefit. Otherwise, it's good when the threads are becoming more collaborative, which was my original intent.

We know why Screen/Chromecasting (specifically, the video portion) doesn't work; same reasons that were discussed extensively last year. Major changes to kernel, SGX DDK, and frameworks are needed in tandem, things that pretty much depend on a working 3.4 kernel. Anyway, no OMAP44[367]0 device has these working, including the ones with lots more developers like GNexus or Galaxy Tab 2.

It's usually not an issue since those configuration files are not accessible on device without root. Still, no harm done if you make sure to change those passwords.

About the Wi-Fi issue, I'm hoping that [MENTION=5672278]belfastraven[/MENTION]'s find is indeed the source of the problem. Alas, based on that thread, it sounds like Google had implemented temporary workarounds since 6.0.0_r41 based on #180 and #186, so you would have noticed some improvement on the current builds. Have you tested that the issue happens on the AOSP build (android-6.0.1_r10)?
[Nook HD, HD+ Android Development] belfastraven:
I'm using Solid Explorernow(thanks for mentioning it). I was just giving you and everyone a heads-up. Same thing with Screencast. I am talking about the app here; it showed up a few builds ago. For Screencast, which is used to record screens and audio, I have found at least one app that will work. I was just asking whether it might be better to keep Screencast out of the builds, or, if not, to have a section in one of the first couple of posts for apps known to be not working-- just a question, really.

I've been able to compile the rom with 5.3 Android toolchains for a while now. You had said not to, before, when we were just starting to test the optimizations. Most recently I have using the arm-eabi-6.0 for the kernel, and the arm-linux-androideabi-5.3-cortex-a9 toolchain for the rest of the rom. They have a "vanilla" arm-linux-androideabi-5.3, also. My last few builds have been using the 03 optimization with other flags as were set or commented out in the Archidroid.mk file. I tried uncommenting some of the other proposed flags but have gotten ice's etc. I am going to try harder to get the -profile-generate and then evaluate stuff to work. I'm not sure whether it is the 5.3 toolchain or the 03 optimizations, but I believe your battery usage is better than mine. I'm hoping that more 6.0 toolchains will be released soon.

I'm running my builds on one nook, and your builds on another (I was afraid mine was not going to make it too much longer, and wanted to make sure I could find a replacement )

I just set up a Ubuntu 16.04 test environment and building seems to work fine there, as well.

I don't have a problem uploading the roms--I would have a problem if too many people were trying to get them from my PC. For the time being, If I come up with anything really exciting, I'll put it on my google-drive.

Thanks again for your guidance.
[Nook HD, HD+ Android Development] acr123:
What app did you find that will screencast the nook HD+ ?? I also could not find the list of apps that do not work.

Al
[Nook HD, HD+ Android Development] belfastraven:
An app named ADV screen recorder will record audio and video of what is on your screen (That is what the Screencast app does--it doesn't actually "cast" the screen live) It records "upside-down"--I think our nooks have flipped screens- but you can rotate the video when you play it using apps like VLC (and others, I believe). I record You may need to play with the settings a bit, but there is help and a tutorial with the app. Their are many other apps that might work, but I haven't tried them all.

I think you misunderstood what I was saying to amaces--I was asking him whether we should keep a list of apps that we know do not work.
[Nook HD, HD+ Android Development] acr123:
I wanted to clarify that I meant mirroring not screencast. My nook HD+ works fine casting with the newer ( 2015) chromecast as long as you use one of the apps such as youtube.. However, it does not mirror your screen, even using chromecast for CM13. There is a program called mirrorenabler that has allowed mirroring to work with certain roms such as CM11 so it can not be a Nook hardware issue. In previous threads it has been has stated that " In order for Chromecast app mirror to work, google play services must be installed into system partition. " I'm not certain what this means. Maybe someone that is more technical than I am may have an idea why you can cast but not mirror using the Nook HD+?

Thanks,

Al
[Nook HD, HD+ Android Development] ajislav:
When you cast (e.g. from YouTube) you are actually streaming from the internet, not from the Nook.

Screenrecorder tries to create a MP4 stream from your screen and fails due to some blob/driver/codec issue.
[Nook HD, HD+ Android Development] mmnspeed:
Does anyone use a stylus with nook HD+..I tried some months back..I don't remember which version of android it was, but it was jittery and unusable..i thought the screen might not be sensitive enough..the stylus worked fine on my other android devices...haven't tried it again since then..neither on this ROM...
[Nook HD, HD+ Android Development] sasmith-129:
Thanks [MENTION=4473900]amaces[/MENTION], I dirty flashed the 01-27 experimental build (over 01-10) and problem does not appear to be present. So it does seem to be related to the build settings you changed. I'll continue to test further. Thanks!
[Nook HD, HD+ Android Development] king200:
The 01/27 Ovation Experimental, Ovation build flashed without problem.

Open Gapps Nano 0128, and then 01/26 would not flash due to insufficient memory. Suggested try a different version of OPGA.

With CM 13, 01/24 and OPGA 01/26, I show only 9.67 MB free (TiBU System Rom) of 693 MB total.

Plenty of internal 32GB and External 32 GB memory.
[Nook HD, HD+ Android Development] smileyint:
Thanks belfastraven. Going through a long thread.

---------- Post added at 09:36 AM ---------- Previous post was at 09:03 AM ----------

Hi Amaces,

Will find time to test aosp. Thanks.
[Nook HD, HD+ Android Development] belfastraven:
New recovery hummingbird question

[MENTION=4473900]amaces[/MENTION], I built 2.8.8.0 for hummingbird which seems to work fine except for the screen being flipped. As I am spatially challenged in the best of cases, I wonder if you could give me a hint as to where that code lives. BTW, running with a build made after syncing a couple of hours ago and with the 2.8.8.0 TWRP, everything seems to be running faster and more smoothly. What kind of magic change have you made.

thnx
[Nook HD, HD+ Android Development] extrem0:
I don't know how amaces managed to do this. I think he had some classes with David Copperfield because this is really magic! My ovation is quite smooth on recent cm13 builds.