yashsingh1/xdaforums huggingface dataset:
[Nook HD, HD+ Android Development] amaces:
That's unfortunate since it means rolling back some of the aggressive optimizations. I may ask you to test builds in the future; [MENTION=5672278]belfastraven[/MENTION], would you be able to test rendering in this game on hummingbird?

There ware major changes in the ways we're faking extra memory, plus the aggressive GCC optimizations. While some of the latter will need to be reverted per above reasons, the overall behavior should remain unchanged.

TWRP lives in bootable/recovery-twrp, but it's still buggy on hummingbird. The flipped screen means touches don't register properly, likely because the BOARD_HAS_FLIPPED_SCREEN feature hasn't been ported to the new code yet. Although I tagged it 2.8.8.0, there's no such thing yet, but the code upstream is getting close.

That would be useful information for people moving onto CM1[23], and while we could squeeze it in the Bug Reporter, I'm thinking that a dedicated thread would work pretty well for this purpose. Your choice.

That's were I'm still confused; did you make the required changes for GCC5 (i.e., bionic, frameworks)? While support for the newer toolchains is much improved compared to Lollipop, a couple of changes are still needed to complete a build with arm-linux-androideabi-5.[123].

It's totally possible, and was never opposed to it; I've been testing the benefits of UBERTC 5.3.1 for both kernel and ROM. Just wary about hardcoding optimizations in the toolchain rather than using dynamic flags in the build system, when one is trying to determine the incremental benefit of each change. As of now, the build system ends up selecting pretty much all the major Cortex-A9 flags anyway.

If you're curious about it, search the CM12 threads where the reasons why video mirroring is broken since Lollipop were discussed extensively (device audio works). Otherwise, regular Chromecasting doesn't involve any realtime A/V processing on device; it's pretty much a glorified remote.

No experience or helpful feedback here, but I do know that our hardware and touch drivers are not stellar in this regard. Most devices will never behave like a Wacom tablet since that requires a real digitizer, but a cheap stylus emulating finger input should still sort of work.

The size of the /system partition is set to 672 MB currently, which is normally sufficient for CM13 and OpenGApps nano. The last builds were using optimizations that increase the size of the unpacked binaries by about 15 MB, which brings remaining free space in /system just below the (quasi-arbitrary) 10 MB safety margin.

Future build will revert to more normal build flags, and should fit OpenGApps nano again.
[Nook HD, HD+ Android Development] belfastraven:
I'll need to go back through the l thread to determine what game it is, but I'd be happing to try to check.

The touches register properly if you can visualize flipping the screen back in your head and place your fingers accordingly--which I am bad at :) Sorry--I knew the recovery was in recovery-twrp, I was asking where the screen flipping code was. I found this in /device/bn/hummingbird/BoardConfig.mk.

#Config for building TWRP

DEVICE_RESOLUTION := 800x1280

RECOVERY_GRAPHICS_USE_LINELENGTH := true

LANDSCAPE_RESOLUTION := 1280x800

TW_DEFAULT_ROTATION := 180

BOARD_HAS_FLIPPED_SCREEN := true

but I think I made a mistake by renaming the recovery-twrp directory, recovery, thinking I would get the wrong recovery image if I didn't. I will rename and try again.

I have not yet figured out how the "build" knows it's building for TWRP (I am in a twisty little maze of passages, all alike :))

Right now I seem to be getting errors from some SEPolicy stuff if I try to build. I really wish there was some clever program that one could run to clearly show all the dependencies in the build. I have a headache!

Perhaps we can start a thread, keep the OP in it for a list of apps which are not working as of a certain date in a particular build, with discussions or requests in that thread. Your OP here could direct people( link) to that thread. It actually is rather difficult, especially for people starting to use the roms, to find information sometimes. Free-text indexing like is done in these threads is great, except if you don't know what to call something or have a name slightly wrong , etc.

I didn't make any changes in framework or bionic , other than frameworks using Os via local C_CFLAG for for the audioflinger service. I have been compiling with the cm13+optim branch. What is it that you changed for your compilations?.

BTW in my opinion, the O2 optimization in general runs more smoothly than the O3.

Have you notice this for the next nightly?

http://review.cyanogenmod.org/#/c/129614/
[Nook HD, HD+ Android Development] sasmith-129:
Thanks [MENTION=5672278]belfastraven[/MENTION], the game is [URL="https://play.google.com/store/apps/details?id=com.imangi.templerun2”] Temple Run 2[/URL]

[MENTION=4473900]amaces[/MENTION], yes, I'd certainly be willing to test experimental builds on ovation.

Thanks!
[Nook HD, HD+ Android Development] belfastraven:
With the 01/29 hummmingbird build, the game seems to run fine. I just tested it for 5 minutes but everything, seems normal to me. Hopefully, the problem doesn't show up only when your are deep into the game :)
[Nook HD, HD+ Android Development] amaces:
Right, in any case, it's not really usable as is. The needed code used to be in minuitwrp/graphics.c, parts of which are in minuitwrp/{graphics.cpp, graphics_fbdev.cpp, etc} now. As I said, the issue is lack of support for the BOARD_HAS_FLIPPED_SCREEN flag, which I'm sure will be ported back soon. The code is pretty different after the C to C++ transition, so it's not a simple or trivial change. At least, I haven't figured out a quick way to bring back that feature.

I hope you mean renaming via repo's manifest files, not manually… I guess it'll tell you at the next sync.

https://github.com/CyanogenMod/android_device_bn_common/blob/cm-12.1/BoardConfigCommon.mk#L170

I'll certainly add it when it becomes a good resources, same as I did with PeteInSequim's.

Then I don't really understand how… Things like https://android-review.googlesource.com/148147 and https://github.com/UBERMALLOW/frameworks_base/commit/07942f603fb673d44f37e5a87c2feba4d4db4947 are definitely needed; that's why I keep asking if you're sure GCC5 is used consistently everywhere. One way to make sure is to re/move any arm-linux-androideabi-4.* from prebuilts/gcc/linux-x86/arm. Also, I didn't have to modify other local flags, no matter the toolchain, or optimization flags.

Yes, they're just moving code that we already have to a centralized/common location, which many other OMAP4 devices can reuse. No difference for now, although good things may happen there in the future just by virtue of more people contributing. Either way, I will have to rename our init.omap4.rc in bn_common at some point.

If you mean the build I uploaded this morning, it's compiled without extra optimizations, so no reason for rendering issues there. We need to figure out which of my extra flags in +optim create the issue, possibly on this line.
[Nook HD, HD+ Android Development] sasmith-129:
Thanks [MENTION=5672278]belfastraven[/MENTION]. Yes, I would expect the problem to appear within the first five minutes of playing.

That begs the question of [MENTION=4473900]amaces[/MENTION] whether the 01/29 hummingbird build included build settings similar to that used for the 01/27 ovation build (also no issues) or settings similar to the ovation 01/24 build (issue first appeared).

Thanks!

---------- Post added at 03:52 PM ---------- Previous post was at 03:49 PM ----------

Strike that, [MENTION=4473900]amaces[/MENTION] already answered the question regarding build settings used.
[Nook HD, HD+ Android Development] belfastraven:
I am testing the compile again-I changed the name of the 4.8 and 4.9 toolchains so they won't be found. Thank you for not typing at me in capital letters. Tell me what toolchains you prefer that I use, and I'll test those flags and flash each rom on my nook and test the game.

What host version of linux are you running? Is it OK if I continue to build on Ubuntu 16.04 for this testing? I can start tomorrow and report back tomorrow evening with results.
[Nook HD, HD+ Android Development] acr123:
Info about newest MM builds

I have tried some of the MM builds and they make the Nook HD+ much more responsive. Is there some documentation as to what changes are made in the newest or experimental builds to help with the decision as to which MM builds one might want to try?

Thanks,

Al
[Nook HD, HD+ Android Development] amaces:
For this one test, any toolchain will do. Ubuntu Vivid (15.04) here, but no reason not to use newer distributions. Make sure that game rendering is broken with the full cm-13+optim set, then change line 63 to something like:

ARCHIDROID_GCC_CFLAGS += -Wno-error=array-bounds -Wno-error=clobbered -Wno-error=maybe-uninitialized -Wno-error=strict-overflow

If the issue persists, revert and try removing other flags that were added in this change.

The changes are all on GitHub; proper changelogs take too much time, which I'd rather use to keep the devices afloat… Otherwise, there are only two Marshmallow ROMs maintained currently: AOSP(ish) and CM. Some of the device-specific differences are described in the OP, and there are many thousands of comprehensive articles about AOSP vs. CM on the web.
[Nook HD, HD+ Android Development] amaces:
No rush since I'm leaving the more aggressive optimizations out of regular builds; it's just easier for you given the much faster compilation. BTW, definitely make clobber/clean in between builds (ccache should be fine, if you have it enabled).

On a different topic, did you happen to notice much worse idle battery drain with GCC5 ROMs? The hummingbird build in experimental is fully compiled with UBERTC 5.3.1, for example.
[Nook HD, HD+ Android Development] belfastraven:
I haven't noticed more battery drain, but I normally have nook charging when I am not using it. I'll leave it off of the charger and monitor it.

I just compiled with all 02 and the entire set of flags you indicated (line 63) all enabled, and everything runs find in the game for me--. Which is what I expected since I thought I had had all the flags enabled before. I am going to check airend once more and make sure that I haven't disabled something that you have enabled. I actually have never played video games at all, and am still suffering after-effects of the broken wrist, so I'm hoping this doesn't happen only when someone gets deep into the game. I have highest quality graphics in the game enabled. It would seem to me , too, that the larger number of pixels being dealt with might cause additional issues for the ovation that are not necessarily seen on hummingbird. If I ascertain that we are compiling with exactly the same flags, perhaps I can produce a few ovation builds for testing.

P.S. I am working on my older system , since after syncing yesterday and today on the new-one I am unable to build. Have you synced today and successfully built? If so I know that it's something I did...
[Nook HD, HD+ Android Development] amaces:
It sounded like rendering is broken from the get-go; assuming no other build issues, you may be right about hummingbird behaving differently with less than half of ovation's pixels.

Haven't synced repos in a few days, but I do anticipate at least a duplicate sepolicy error after this change. Anyway, I worked on bringing our device trees in line with the latest ti/omap4 commonization, and it should build. Not 100% sure that it'll boot properly with these init/insmod changes, but I guess we'll find out soon.

P.S. I merged support for that BOARD_HAS_FLIPPED_SCREEN flag, so the newest TWRP should be usable on hummingbird as well (only repo sync bootable/recovery-twrp needed).
[Nook HD, HD+ Android Development] belfastraven:
.

I ascertained that the only difference between are archidroid.mk files was that I had disabled the graphite flags at one point, so I re-enabled them. Still the game runs fine. It does take a few seconds to load, but no glitches after that. Perhaps when you enable optimizations again, we should make sure that we know exactly which new rom causes the problems, (the actual name of the file, to be certain). I'm sure the person with the problem will now be reporting back to you. I can then try building for ovation removing the flags one, by, one and make the roms available to you or whomever.

Yup -- I was getting duplicate errors from various .te files ,and some other stuff.

Thanks for the TWRP merge--I will try to sync and build it now now:) I had already been poking around the code--which is dangerous.
[Nook HD, HD+ Android Development] KostasR:
Is there any way to increase the /system space in our ovations? Great work as always!
[Nook HD, HD+ Android Development] belfastraven:
otacde file. ?

[MENTION=4473900]amaces[/MENTION], I notice that when I built (hummingbird) this morning after syncing, the the ota file had a new type of name cm_hummingbird-ota-cde7484a1c.zip. Is that some kind of emulater build? I lunched cm_hummingbird-userdebug as usual, but I noted when building and installing last night that the recovery gave no errors, but it exited and rebooted without installing the rom.

Also the board_flip fix for 2.8.8.0 doesn't appear to be working. I can see where the code has been amended, but am not sure the new code has actually been executed. I will try to look into that later. What is the best way to recompile TWRP without doing the entire build? when I try makes eg mm or mma, the builds are still missing things they need.

thnx.
[Nook HD, HD+ Android Development] nighty2k7:
No charging after flash

Hi there,

I flashed TWRP and then CM13 from here and a gapps package. It might be coincidence, but I nocticed that the charging functionality is gone. I have tried different chargers (which all worked before flashing), and am meanwhile down to 20%. I have shut down the tablet to ask for help before totally running out of battery.

Any chance that the disfunctional charging has been caused software-wise?

Thanks for your help!

Marco
[Nook HD, HD+ Android Development] extrem0:
Most unlikely. I'd say your USB cable is damaged. When you insert it when your tablet is off, does the ambar or green charging indicator light turns on?
[Nook HD, HD+ Android Development] nighty2k7:
Yes, if the tablet is off and I plug the cable in the tablet is powering on, the green light turns to orange, then back to green (as if fully charged) and when booting into the system I see the charge level decreasing and no reaction when pluging/unplugging the device.

So somehow the cable is functional, it seems as if the device thinks it is already fully charged.

PS: Windows recognizes a device plugging in and out
[Nook HD, HD+ Android Development] belfastraven:
It does sound like hardware; otherwise more of us would have the problem. check out this nook thread:https://bookclubs.barnesandnoble.com/thread/9608, for example. Make sure that if you are charging from a wall outlet that the charger is the proper one for a nook, most other wall plugs won't provide enough power. Also, make sure that the prongs are making good contact with the outlet. Maybe someone else here can let us know if a battery problem would also manifest itself in the way that you are seeing.
[Nook HD, HD+ Android Development] amaces:
Well, yeah, but not a convenient or fully transparent way… And really, not many reasons to do so; if you're worried about the slight increase in the last builds, that was temporary, mostly for testing. Before GApps, /system has almost 200 MB free I think, which is definitely sufficient for the pico or nano packages.

The OTA name change makes sense; as mentioned recently, I un-forked a bunch of repositories to pure CM upstream to make my life easier (see manifest history). The naming scheme you know was a minor thing I added since I don't use the bacon target, and I wanted consistent naming across CM, AOSP, etc. Nothing should be different about the content, and you can always switch to my build repo with a local manifest, or even a simple revert in .repo/manifests…

So, no reason for the ROM to not flash properly. As always, re-sync, clobber, and try again.

Yeah, scratch my previous optimism about the new TWRP on hummingbird. It appeared like it should work, and I did submit a few changes on top of the original patch, but maybe hummingbird is not using overlays as before.

I usually make the recoveryimage target, which still spends a lot of time scanning all the Makefiles, but does finish in a few minutes. If we didn't have a weird bootloader requiring the local INSTALLED_RECOVERYIMAGE_TARGET override, one could use the new mms shortcut, which finishes in under a minute.

It's very unlikely that flashing ruined the battery hardware, although it's possible some battery statistics were wiped, so healthd or whatever system component is confused temporarily. Hopefully, your battery chemistry is OK, so after some use battery will drop enough that things will reset themselves.
[Nook HD, HD+ Android Development] belfastraven:
Found out why my roms weren't installing

[MENTION=4473900]amaces[/MENTION], for your and everyone's amusement: another stupid people trick. While playing with the 2.8.8.0 hummingbird rom, I obviously enabled the "simulate actions" setting, but couldn't tell that I had done so. I finally realized that, when installing a rom ,the recovery was ending with the line "simulating actions" duh. I am back to the 2.8.7.5 rom so that I can see what I am doing....
[Nook HD, HD+ Android Development] kramnostam:
SD shown as Corrupted after trying to use as Internal Storage

Hi Herges, just wondering if you found a solution to this? I am having exactly the same problem. Running CM13 from yesterday's nightly.

Cheers
[Nook HD, HD+ Android Development] ieatabiscuit:
Firstly, how old is the SD card? Second, what speed class is it? Third are the connector pins on the card clean, and shiny?

If its old, it could be worn out and failing, they do crazy things when they are dying. As a general rule given the uses an SD card serves, I don't use anything below class 10. If it has a dull color to the pins, clean them. Rubbing alcohol, or even lightly going at it with a pencil eraser can work wonders. Even fingerprints can muck up your card's connection.
[Nook HD, HD+ Android Development] KyJelly69:
clean flashed the 0124 build for hummingbird this morning and deleted the cyanogensetupwizard.apk file per usual and now the android setup wizard stops when selecting english.

BTW i installed the pico open gapps

edit:nano makes no difference.

Edit, now I'm also having some strange issues booting the device. Holding down the power button does not work. I have to plug it in to get it to boot.

Edit:0129 build resolves the setup wizard issue. What makes this experimental? Daily driver?

Is the CM13 experimental kernel built in now since it's in the obsolete folder?
[Nook HD, HD+ Android Development] keshabbhattarai126:
I cannot find right gapps

Every time I install gapps..play services stops working and I can't login to playstore. Please suggest me right gapps link. Thank you.
[Nook HD, HD+ Android Development] reachforthesky:
http://opengapps.org/

ARM, Android 6.0 .. Only nano is small enough to fit.
[Nook HD, HD+ Android Development] amaces:
That's pretty funny, I'm not gonna lie, probably less so when it happened for you… P.S. The screen is definitely fixed in the newest hummingbird recovery.

I don't know how deleting APKs on device came to be recommended; OpenGApps have been fixed for a long time. Now, it's possible that the initial clean install on CM13 was broken in one of these builds. When that happens, you either use a previous build, or wait till it's properly fixed, rather than start removing ROM components. I only know that dirty installs have been working fine since November or so.

When things are deleted/moved to obsolete it either means those changes were incorporated into the full ROM, or were reverted/abandoned. Of course, the ROM always comes with a kernel; separate ZIPs are just means to test latest changes without flashing a whole ROM.
[Nook HD, HD+ Android Development] uberchoc:
A Sleep/Wake Issue

Hi all. I'm completely new to Android, and I recently picked up a Nook HD for my leisure reading, and found I could, per explicit instructions I've seen elsewhere on this site, get Marshmallow to run on it. What a delight. I've used every CM Hummingbird build since the 17th of January, and it's been a brilliant experience!

I wonder, however, why it is my device sometimes finds it difficult to wake from sleep. Is this a software thing? Sadly, I wasn't on stock long enough to determine if it's a hardware thing. I highly doubt it. I always do clean installs, anyhow. Any help here, please? Thank you!
[Nook HD, HD+ Android Development] belfastraven:
Could you describe what is happening in a more detail? How to you normally try to wake it? Do you have a magnetic cover? Tell us exactly what is happening.
[Nook HD, HD+ Android Development] KyJelly69:
http://xdaforums.com/showpost.php?p=64772240&postcount=254

It was suggested I do it per this post so setupwizard can install the apps from previous installation from play store.
[Nook HD, HD+ Android Development] uberchoc:
About 15% of the time, when I hit the home button to wake it from sleep; the screen responds by lighting to a dark shade of blue. I then have to hit the power button to put it back to sleep, and then wake via home button again. Sometimes I'm unlucky and it doesn't even show this dark screen. I then have to wait a while before attempting to wake it again. Sadly, there's no rhyme or reason to this behaviour.

I've noticed this doesn't happen at all while I'm within Recovery; say, when the screen goes to sleep while doing a back up. So I imagine it's certainly not a hardware issue.

No, I do not have a magnetic cover. Or any cover yet, for that matter.
[Nook HD, HD+ Android Development] belfastraven:
Do you know how to get the logs from the nook? IF you attach a logcat log here, it might give us more information. If you don't know how to do this, I'd suggest the Syslog app from the play store.

---------- Post added at 09:10 PM ---------- Previous post was at 09:02 PM ----------

@amaces, Having been running for three days now with your 5.3/5.3 build and being told by "battery" setting that I have 11 hours still available, I'd say that this is at least as batterry friendly as the 4.9 builds. I'm running a 5.3/6.0 build on my other HD right now, (with your TWRP ZIP from experimental) , but given my experience of the last week, I don't think the 6.0 eabi is as battery- friendly as the 5.3. I think some of the battery issues were fixed in the later 5.2 releases, btw.

P.S> I just looked at airend for the TWRP change that fixed this and couldn't tell what/where it was. Nothing recent that I could see mentioned the FLIPPED_SCREEN setting. Has the change not been committed yet?
[Nook HD, HD+ Android Development] highlandsun:
I just installed the Ovation experimental build. root and adb aren't working on this. /system/xbin/su had no setuid bit. I enabled that using the twrp terminal but it still doesn't give root access.

This is cm_ovation-ota-MMB29T.160127.zip
[Nook HD, HD+ Android Development] amaces:
Can you attach a screenshot with the idle battery graph?

https://github.com/airend/android_bootable_recovery/commit/871b07f7b4de54c07cb895bc48f654eec771a403

That's not how it works on CM1[23]; you need to enable root for apps-only in Developer Settings. P.S. Should you prefer SuperSU, systemless will fail to install because it doesn't know how to unpack our ramdisk, but regular version (2.52?) works OK.
[Nook HD, HD+ Android Development] TeutonJon78:
Just an update on following any gapps, openGApps has a MM build out now. Note: I have NOT tested it at all -- just an FYI.
[Nook HD, HD+ Android Development] belfastraven:
noted this from OPENGAPPS site

to install Open GApps on 6.0 your ROM needs the following patch to prevent Force Closures at first boot:

I tried flashing the nano ((with 111/05 rom) and was bootlooping...