Hi, I'd post a reply here http://forum.xda-developers.com/showthread.php?t=883175&page=75 or http://forum.xda-developers.com/showthread.php?t=938200&page=18 but this is my first post so I cannot post a reply
Here were my steps to get it all together. For reference, here is the link in the dev section (that I can't respond to).
Background: The 1.1 update installed without my knowing on a rooted 1.0.0 NC. It would go to the intro animation and would stall and restart in an infinite loop. I decided to take the plunge to Nookie Froyo on the eMMC.
I had also installed Customized Nookie Froyo 0.5.9 on a Patriot Class 10 card and it was painfully slow and market was not working. When I did this with the latest version to the eMMC it was fast and did not have any problems in either regard.
Steps:
-- Burning the image --
I unzipped and followed directions for my Mac OS X system: http://nookdevs.com/Nookie_FroYo:_Burning_a_bootable_SD_card
I booted off the SD Card, literally turn it on with the new MicroSD in there, this is the Clockwork Recovery
I went into "mounts and storage" Formatted boot, system, and data in that order. The volume keys are navigation, N button is select, and power is back. After formatting "boot" I had to restart by holding down the power key for some reason (non-responsive), but it was fine.
I then went to Wipe my Cache BEFORE restoring. I know the instructions place it last, but think about it. You want to clear everything before hand rather than after you've re-imaged it.
Then I restored the zip. You will have to select the zip.
Twiddle your thumbs. When it's done writing, you'll know cause it'll say done. Now you can take out your SD card. Go back to the Main Menu of CWR and select reboot. It'll pop you out to Nookie FROYO!
First things, first. Unlock, and then re-lock, this gets rid of lag.
Set up your Wireless, then set up an Account for Gmail in Settings > Accounts.
I then went into "Settings->Applications->Manage Applications-> Google Services Framework -> Clear Data" There was no Cache for the Market at this point.
I let it sync everything, while I set other things up (e-mail acct, time, and etc)
Then I went into Market to get Appbrain. Success!
When I synced with Appbrain I still couldn't "see" certain apps in the Market. So I went into:
Settings->Applications->Manage Applications-> Market->Clear Cache and
Settings->Applications->Manage Applications-> Google Services Framework -> Clear Data
AND REBOOT
I then saw a lot of the other apps, but couldn't find Angry Birds :-(
Finally, wanted to see how it performs as an eReader, but when I stuck my SD card in there. Crap, couldn't see it at all
Had ADB installed which is necessary and run these commands with these vold files found here ( http://dl.dropbox.com/u/313036/volds.zip ): http://forum.androidcentral.com/bar...ion-install-nookie-froyo-internal-memory.html (as well as on xda-net.
Couple of things with ADB, the screen must be on, otherwise the device goes offline and you're get protocol errors. The reboot never happened on its own, so I did it manually. SD card is recognized!
Couldn't be happier. Works very well. It's speedy without the 1.1Ghz kernels.
Those were my experiences. It's rather straightforward.
Oh forgot to mention one CAVEAT. My Power button is really really sensitive now. Like a capacitive charge turns it on (I am putting absolutely no pressure on it). Any workarounds for this?
I am enjoying the 0.6.6 flashable Nookie Froyo experience. But, I haven't yet figured out how to get the Market App on the device. Am I missing something obvious?
you should be able to find the apk in the dev section, install via adb
I'd recommend installing CUSTOMIZED Nookie Froyo as opposed to Nookie Froyo which is very vanilla whereas the customized version has a lot of things already set up -- such as the Market, Google Apps, Softkeys and SuperUser.
where does one find this CUSTOMIZED version. i assume not on xdda becaue it includes gapps>?
cray1000 said:
where does one find this CUSTOMIZED version. i assume not on xdda becaue it includes gapps>?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=938200
I am using 0.6.6 and made the updates you see in the first post
I've been trying to get Android Market app installed on my CM7 card - with no success. Everything works fine - Amazon installs apps fine - CM7 boots and works fine.
When I boot to load Android market
it detects Google Market Installer file
and shows an error - that I have
" Invalid Zip Magic 4f4421C3" and unloads Google Market Installer
* I followed the instructions in CM7 size agnostic card file
* Not logged into any Google account - or WIFI - if that makes a difference prior to install
I'd really like to have access to G-market so I can get a few readers besides Kindle to choose from. If anybody has some suggestiosn as to how I get past this road block - I would really appreciate some help.
Thanks in advance
After returning 4 HDs that developed charging and other problems following the setting of the "allow unknown sources" flag, we decided not to tempt fate with the 5th Nook HD and then I discovered that apks can be installed via ADB, bypassing the Android setting. There is a drawback, of course--the apps cannot self-update.
I did this with a copy of an apk that's no longer available in the PlayStore and which I had already installed on my NT/CM10. What I forgot was that this package came with an Aptoide Store app attached. The desired app installed on the Nook HD and runs fine, but we now get periodic random messages like "this app cannot be installed" blah, blah, blah. I'm assuming this is because the Aptoide store is trying to install itself, but of course is blocked by the Android setting that won't allow unknown sources.
My question: where do you suppose this uninstalled package is hiding? If I try to use the ADB uninstall command as if it were already installed, will that expunge it?
NOTE: This is only for Nougat (7.1) custom ROMs (such as Lineage 14.1 based)!
Make sure you do a proper nandroid backup before flashing!
I made a flashable zip for updating the libhoudini stuffs for Nougat (7.1) ROMs to 7.1.0a_y.49344. Not sure if this has been posted elsewhere before, though.
Before flashing, check your current libhoudini version by typing "houdini --version" either from adb shell or from terminal emulator. (UPDATE: Use the built-in Terminal as it doesn't work in Termux)
You should only try to flash this if your houdini version is below 7.1.0a_y.49344. Current custom ROMs usually have a houdini version of 7.1.0_y.48901 (DotOS 1.2 for example).
Flashable zip (It's about 34MB in size) (Dropbox link here)
The original source is from here, apparently taken from Nexus Player (fugu).
After flashing, "houdini --version" should report something like this:
Code:
[14902]
[14902] Houdini version: 7.1.0a_y.49344
[14902]
TESTING NEEDED: I'm not sure what this version of houdini might fix or break, so try this at your own risk. If you're currently not having problems with apps then there's no need to flash this. Compared with existing device files (7.1.0_y.48901, in /system/lib/arm/), several library files are changed, plus an additional "libgate.so" which I could identify it as being an ARM library file (so it'll also be placed in /system/lib/arm, although I'm not sure where it might be used).
EXPERIMENTAL (UNTESTED!): Here's another version in case someone might be interested. This build is 8.0.0_y.49374, and the version number literally means it's to be used for Oreo, so I'm not sure if it'll work on a 7.x ROM. The original source of this version is from Android-x86.
Flashable zip (Dropbox link here)
If the zip works, it should report the following version:
Code:
[19729]
[19729] Houdini version: 8.0.0_y.49374
[19729]
What is the use for this ?
PedroCaseiro said:
What is the use for this ?
Click to expand...
Click to collapse
It's just to put updated libhoudini libraries into the device, in hope that those updated stuffs might help with fixing some native libhoudini crashes on certain problematic ARM-only apps.
I had some ARM-only apps that always FC with native crashes (SIGSEGV) from libhoudini on Zenfone 2. Although the updated binaries unfortunately could not fix the problems entirely, at least the they work as intended as I haven't discovered anything broken by the updated stuffs yet.
However, this won't help if your app crash is due to the developer shipping an incomplete set of x86 native binaries (this can happen). You need to sideload it through adb and force it to use ARM abi, like this:
Code:
adb install --abi armeabi xxx.apk
Note that the abi name varies among apps, armeabi is just an example, it might be arm, or armeabi-v7a, depending on the app itself.
EDIT: Say, is there a way to report device incompatibilities to Play Store so I can explain the device's situation and let Play Store always ship the last known good version for our device? There seem to be some apps that previously worked, but not now due to updated native libraries that would cause native crashes on libhoudini (Play Store will still treat our device as compatible due to the device exposing the ARM abis thanks to libhoudini), and I often need to disable the app in question's auto-update to prevent Play Store updating it to the native-crashing version.
Running "houdini --version" in a terminal emulator results in:
"houdini: command not found"
for latest version of Groovy Android
deckinghalls said:
Running "houdini --version" in a terminal emulator results in:
"houdini: command not found"
for latest version of Groovy Android
Click to expand...
Click to collapse
Are you using Termux? It seems I'm getting the same result there as well, but houdini outputs just fine in the built-in Terminal as well as in the T-UI launcher.
And as for file lists:
In /system/bin there's the "houdini" binary.
Then there's "libhoudini.so" in /system/lib/ (this is the main library which is of i386 architecture).
And the rest of the files (ARM libraries) in /system/lib/arm/. These consist of the exact same set of files as the ones provided by the custom ROMs, plus an additional one (libgate.so).
LSS4181 said:
Are you using Termux? It seems I'm getting the same result there as well, but houdini outputs just fine in the built-in Terminal as well as in the T-UI launcher.
And as for file lists:
In /system/bin there's the "houdini" binary.
Then there's "libhoudini.so" in /system/lib/ (this is the main library which is of i386 architecture).
And the rest of the files (ARM libraries) in /system/lib/arm/. These consist of the exact same set of files as the ones provided by the custom ROMs, plus an additional one (libgate.so).
Click to expand...
Click to collapse
I am not sure what is meant by "the built-in Terminal" (I don't recall any ROM coming with one?) but I did use Termux as well as the terminal in TWRP. I figured out if you type "su" to get root access first, then the command works fine in Termux.
Flashed the .zip file. So far, I haven't noticed any changes, good or bad. I don't remember which apps would FC (maybe the Amazon Echo app and Disney Infinity 3.0?) but I'll keep you posted.
deckinghalls said:
I am not sure what is meant by "the built-in Terminal" (I don't recall any ROM coming with one?) but I did use Termux as well as the terminal in TWRP. I figured out if you type "su" to get root access first, then the command works fine in Termux.
Flashed the .zip file. So far, I haven't noticed any changes, good or bad. I don't remember which apps would FC (maybe the Amazon Echo app and Disney Infinity 3.0?) but I'll keep you posted.
Click to expand...
Click to collapse
Some ROMs do have built-in terminal app. However, you need to enable it, which can be done in Settings -> Developer Options (assuming you know how to enable Developer Options as well). There would be an option to enable "Local terminal" which is the built-in terminal app.
Which means it will help the x86 device run ARM ???
I do not understand. Please analyze me
Mkey_34 said:
Which means it will help the x86 device run ARM ???
I do not understand. Please analyze me
Click to expand...
Click to collapse
libhoudini is Intel's ARM binary translator that helps x86 devices run ARM apps, albeit with some limitations and performance reduction due to overhead. Without it, most apps won't be able to work at all, as they don't have x86 native libraries.
Zenfone 2 already has houdini included, that's why it could run as many apps as any other devices. The flashable zip here contains updated files (for 7.1 ROMs) in hope it could help with some problematic ARM-only apps that refuse to work with libhoudini, though in most cases the differences are barely noticeable.
LSS4181 said:
libhoudini is Intel's ARM binary translator that helps x86 devices run ARM apps, albeit with some limitations and performance reduction due to overhead. Without it, most apps won't be able to work at all, as they don't have x86 native libraries.
Zenfone 2 already has houdini included, that's why it could run as many apps as any other devices. The flashable zip here contains updated files (for 7.1 ROMs) in hope it could help with some problematic ARM-only apps that refuse to work with libhoudini, though in most cases the differences are barely noticeable.
Click to expand...
Click to collapse
Thank you
---------- Post added at 02:58 AM ---------- Previous post was at 02:53 AM ----------
something's wrong I can not download it. I need another link. thank you
My device is running Groovy Android 7.1.1, 18 May Build.
so i have successfully upgraded houdini version using your flashable file. Thank You for your work.
what if i want to revert to the houdini version that comes preinstalled with the rom, will dirty flash rom zip work?
sushuguru said:
what if i want to revert to the houdini version that comes preinstalled with the rom, will dirty flash rom zip work?
Click to expand...
Click to collapse
The zip is meant to be flashed every time you reflash the ROM, so yes, dirty flashing should be able to revert it.
But again... you're supposed to do a nandroid backup before flashing, and there's no need to flash this if you aren't encountering any native code crashes from arm-only apps at the moment.
Unfortunately, as Intel had already left the mobile market and no more Intel-powered smartphones produced anymore, some developers started to "move on" and use libraries or compiler options incompatible with houdini in order to make their apps run more efficient on modern ARM smartphones, without having to be "constrained" for compatibility reasons...
The houdini binaries I found only seems to be a minor update, and I'm not sure if Intel is still working on this or if there are possibilities to obtain an even newer houdini version with "y" suffix, which our phone uses.
Added an experimental (UNTESTED!) version found from Android-x86 (8.0.0_y.49374). This version was originally meant for Oreo, so I'm not sure if this would work on a Nougat ROM.
Currently on Android-x86 only the "y" version (which our devices use) is available. The other versions ("x" and "z") are not present, and the link would simply give you a "not found" error.
Although I don't mainly use the phone anymore, I could still conduct some tests with the device if I have time.
Bit the bullet and tested the 8.0.0_y.49374 build. Does not work. Evie force crashes right off the bat. Haven't tested further than this, but if I cannot even use my launcher of choice, that isn't a good sign.
Has anyone managed to update or replace the system Webview? I am trying to use the home assistant Wallpanel app and it works fine except custom cards fail to function, all the info I've found so far lead me to believe it's to do with the webview, maybe because it's V74 and I need a newer one, I've not managed to download one that will install, the latest one fails to install, and I've tried installing an older one (89.0.4389.86) which said it installed but checking in dev options it's still showing V74.
Anyone have any ideas?
The easiest way would be to root your device and use a Magisk Module like the Webview Manager I have attached here.
The other method is to try to change/update your framework.apk but that's really hard to do (especially with the newer android versions) without causing a bootloop.
I've been looking but not found a way to root the device yet, might just work around the limitations of the webview issue