Database Develop

[Q] Nookie Froyo SDCARD Bootable Issues and Resolutions

I loaded the Nookie Froyo to SDCARD and have been having weird issue all of which has been reported here and in other forums elsewhere. I thought I would take a few minutes and list them out and how I fixed it and also list a few I am still having to see if there is any resolution.
These resolutions are based on posts from this forum and others. I do not have the links for them all as I have scoured so many and tried so many things I stopped book marking them.
My Nookie Froyo is 0.6.8 from http://forum.xda-developers.com/showthread.php?t=922324 (Thank you Brianf21) and I used the free EASEUS Partition Manager to extend #4 to the end of the 8GB SDCARD (http://www.partition-tool.com/). I am also using the multi-u-boot.bin from rookie1 (sweet thing as I can boot SDCARD or stock Nook Color w/out taking out the card!)
If I missed credit to anyone please forgive me. I am not a developer, just an end user that likes to play and am working off of other people’s hard work.
Problem 1: Market downloads apps and then stops and won’t download anymore.
Resolution: Go into Settings/Application Settings/Manage applications. Select ALL. Scroll down to Market and tap it. Tap Force Stop. Tab Clear Data and tap ok to any warning messages. Go to Google Services Framework in All Applications and tap Clear Data. Tap OK and and warning. Power off and back on.
Market should work now and if you got sign in errors for Goggle Talk that should also work. On first run of Market you may not see all of you installed apps. After I installed an app, exited market and went back in all installed Apps were present and accounted for. Been good since doing this and will continue to monitor.
Problem2: WiFi doesn’t work after sleep.
Resolution: Go into Settings/Wireless Networks and Settings/Wifi Settings Hit the Menu Button and tap Advanced. Select Wifi Sleep policy and set it to Never.
Go back to Wireless Networks and Settings and tap Mobile networks. Deselect anything in there that is 2g/3g (I have a nook color so not needed for me).
Run a file manager program that gives you root access (I used Root Explorer). Go into /System/App and rename Phone.apk to Phone.apk.old. Rename TelephonyProvider.apk also to .old. Power off and back on again as you will eventually get errors the phone doesn’t work. Again I am on a Nook Color so no phone and no need to load it.
Problem3: Can’t get the latest Google Framework to load.
problem 3 was resolved kinda by a new build from the developer
Problem 4: Market not showing all apps (protected apps missing)
edit the build.prop using something like root explorer. change the ro.build.fingerprint line to what is shown below (make a backup copy just in case). go into device settings and clear the market cache (not data) and force stop. clear the data for the google framework and force stop. reboot your nook and go into the market. search for something that was missing like vevo. if it apears you should be good.
ro.build.fingerprint=verizon/voles/sholes/sholes:2.2.1/FRG83D/60505:user/release-keys
Mike…

Froyomod: Wifi does not work

I recently flashed the froyomod 2.6 rom, and have found the speed and overall feel to be absolutely fantastic. I am however having issues with the inability to connect to the wireless network in my home. The wifi status shows a constant scanning/disconnected. I found a recommended fix in one thread, however do not understand these instructions:
Turn off wifi
rename /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
Turn on wifi
Sometimes that works (android will make a new .conf file)
If not, reboot
Where do I find the file in question? The renaming itself sounds simple enough, but the actual location of the file is what I do not understand.

I use Root Explorer to view files that are system config files. I have heard of people using ES File Explorer but have never tried it.

i heard of something called the "Blade wifi fix", its in the market and it might work

I was able to perform the described file name change, but unfortunately that did nothing to fix my problem. It looks like I'll be trying out a different rom soon instead so that I can use wifi.

SwiftKeyX

I have the phone version, not the tablet edition, and that may be part of my problem (but I doubt it...)
There is no "Language and keyboard" setting, either in the regular settings menu or in the Nook Color settings area.
While the Nook Color app does allow for changing keyboard, it says that the .apk must be in /system/app
- that isn't a problem - I used AndroZip to b/u the swiftkey.apk file to the SD card, then used root explorer to copy it to /system/app (yeah - I'm sure there are easier/better ways, but that's what I did...)
It still won't let me change the keyboard to swiftkey (which, btw, is FREE today in the Amazon Marketplace. I'd purchased it in the regular market on my phone previously, so installing it on the Nook was easy).
Does anyone have insight into how to get this done... or if it can be?
Thanks,
~K

I got it to work, at least partially. The keyboard shows up, but I don't see the predictions and the popups on keypress are distracting. But perhaps you'll have better success than I did.
However, as far as your problem goes--I think you should check the permissions on the file you copied to /system/app. I used File Expert to copy the file over, but I found that I had to edit the permissions afterwards to match the permissions of the other files in that folder. Then I reboot the nook and the nook tools app recognized the other keyboard. After that, launch the swiftkey x configurator from your app drawer and follow the steps there. A lot of the settings come up as blank buttons on the nook, so I did the process in parallel on my android phone so I knew what I was doing.
Good luck! And if you figure out how to make the predictions work, I'd love to know!

thepdm said:
I got it to work, at least partially. The keyboard shows up, but I don't see the predictions and the popups on keypress are distracting. But perhaps you'll have better success than I did.
However, as far as your problem goes--I think you should check the permissions on the file you copied to /system/app. I used File Expert to copy the file over, but I found that I had to edit the permissions afterwards to match the permissions of the other files in that folder. Then I reboot the nook and the nook tools app recognized the other keyboard. After that, launch the swiftkey x configurator from your app drawer and follow the steps there. A lot of the settings come up as blank buttons on the nook, so I did the process in parallel on my android phone so I knew what I was doing.
Good luck! And if you figure out how to make the predictions work, I'd love to know!
Click to expand...
Click to collapse
Is anybody able to get the GMAIL personalization to work?
I'm prompted for my username and password, but when I submit them I get a blank window (where I should be able to select "grant access")
thanks

Kalash said:
[...] While the Nook Color app does allow for changing keyboard, it says that the .apk must be in /system/app
- that isn't a problem - I used AndroZip to b/u the swiftkey.apk file to the SD card, then used root explorer to copy it to /system/app (yeah - I'm sure there are easier/better ways, but that's what I did...)
It still won't let me change the keyboard to swiftkey (which, btw, is FREE today in the Amazon Marketplace. I'd purchased it in the regular market on my phone previously, so installing it on the Nook was easy).
Click to expand...
Click to collapse
Hopefully you've fixed this in the time since you first posted, but for anybody else trying to do the same: The new keyboard option won't show up in NOOK Color Tools after you copy the .apk to /system/app until you do a reboot.
I had the best luck with Smart Keyboard Pro. You can set a high contrast theme with no animations whatsoever, so it's easy to see and it doesn't flicker except for toggling between upper- and lower-case letters. I have never been able to get predictions to work with Swiftkey or Smart Keyboard on my NST. I do shut off the auto-caps and other features that can be hard to use on the NST.
---------- Post added at 10:22 AM ---------- Previous post was at 10:17 AM ----------
Zorkman said:
Is anybody able to get the GMAIL personalization to work?
I'm prompted for my username and password, but when I submit them I get a blank window (where I should be able to select "grant access")
thanks
Click to expand...
Click to collapse
I have never been able to get prediction working on the NST, so personalization wouldn't help.

[APP][NST/G] Screenshot

*completely reworked and improved app in the post immediately following*
I created a little one-touch app to utilize the native screencap capability of the NST. As noted a long time ago in another thread, this capability is a little odd, as it results in a blue or green-scale image. This app corrects that issue, converting to 256-greyscale.
But....what about Screenshot Easy or any of several other PlayStore apps? Actually, I have used Screenshot Easy for some time, and I do like it. What I really wanted, however, was a capability reminiscent of the power-button option in CyanogenMod ROMs where one touch can give you a screenshot of any screen, right while you are looking at it. While adding that function to the power button on the NST is beyond my pay grade, I was able to do this much. To get the most out of this app, you need to have a hardware button available. Using NTMM, assign that button to the app and you can then take a screenshot at any time (except on the sleep screensaver--yeah, I had to try!). I included a few examples below.
Install
1. Download the apk file (below)
2. Transfer to your NST [probably also NSTG--can someone confirm?]
3. Touch on icon from your file manager and choose to install.
4. In the root of your SD card, create a folder called "Pictures". Within that folder, create another folder called "Screenshots". Folder names and locations must be exact. Sorry.
*This app requires root access because it is executing shell commands. The first time you try to use it you will likely get a screenshot of your SuperUser app permission screen*
Screenshots are saved with names like "screenshot_7-29-2017_13.57.jpg" (yup, that's the date and time). When a shot is taken, a notification appears as a confirmation.
To assign a hardware button to the app, use Nook Touch Mod Manager (NTMM), or just tap on the app icon to take a screenshot.
Edit: I have recently discovered that these apps--and all Tasker-generated apps--have a dependency on two library files normally installed with GApps. If you do not have GApps installed on your device, you can still use these apps by copying the two attached files into the locations shown below (the xml file is zipped so you can download it rather than view it):
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.maps.jar
Set permissions for both files to rw-r--r-- and reboot.

Version 2!
6-21-23: updated to 2.2
--removed dependency on Screenshot Easy app (you can uninstall it)
--added small binary file, fb2png, which "replaces" malfunctioning device screenshot routine
This is a completely re-worked approach to a one-touch screenshot which is now part of my Alternate Power Menu app, here as a stand-alone.
Install
1. Unzip the attached file
2. Copy over Google maps library files as described in post #1 above (if not already present)
3. Copy the file "fb2png" to /data/local, set permissions to rwx rx rx
4. Create the folders /sdcard/Pictures/Screenshots
5. Install the Screenshot app
Use
You can take a screenshot by tapping on the app icon, but the best use is to assign the app to a hardware button using NookTouch ModManager. When you take a shot, there is a brief pause and then eventually a "flash" of a smaller image of the screen (see attached image below), followed by a notification. Because the app now requires root in order to determine whether the device is in portrait or landscape orientation, your first screenshot might be of the SuperUser permission screen. That won't happen a second time.

something could be wrong with the Screenshot version2_1 you reproduced.
Click to expand...
Click to collapse
Maybe, but I've installed the app on two NST devices without problems. However, it's not been tested on older firmwares, only 1.2.1 and 1.2.2. I don't see any reason why it should not work on the older firmware.
Check the Screenshot Easy configuration and make sure the image format is set correctly and that the path for saving the images is correct.
I'm out of the country now and don't have my NST with me, but I'll be back in a week and double check the uploaded apk. Could have been corrupted I guess.

lz199366 said:
Thanks for your reply. I tried to copy your settings 100%ly.
However, it can't take shots if I set the settings exactly the same as yours(it 'flashed' but create nothing in the folder)
Screenshots will only be taken when I turned on those two options(see in the attachment).'Start capture' and 'Notification icon' have to be turned if I want to take shots on my NST.
Also, I have updated my previous post to show how different the picture quality was by using 2 screenshot methods
Click to expand...
Click to collapse
I'm sitting in an airport lounge thinking about this problem. Did you try assigning the 2.1 version screenshot app to some other hardware key? Something about the timing on the long-press "n" might be causing an issue?

OK, I downloaded the posted 2.1 apk file and installed it on my NST running FW 1.2.1 and also a second one running 1.2.2. I didn't have the app installed previously because I use the Alternative Power Menu app and that includes the same screenshot routine.
To be brief: it works perfectly on both devices.
I can't emphasize enough the importance of having the two Maps files properly installed prior to the installation of the Screenshot app (if you do not have a prior GApps installation). That includes the reboot once the two files have been copied into the correct folders and their permissions set properly.
If you have done that and the app still refuses to function then there must be something about the older FW you are running, although I can't imagine what because the app really doesn't interact with the B&N stuff, but I suppose they could have found some Android 2.1 issues and corrected them in later FW versions.

Locked out of /sdcard again??? V11

I rooted my 4XL and find that I'm locked out of doing anything with /sdcard (AKA /storage/emulated/0). Specifically, I'm trying to point Poweramp at the Music folder, and d/l AdAway's hosts files. Obviously there's a work-around to let apps use /sdcard, but what?

Apps have to ask permission through scoped storage.
For example, in PowerAmp, go to Settings > Music Folders... delete your previous selections if you're having trouble... click "Enable" next to your device name(which points to sdcard in effect) or click the + icon to pick otherwise. The system's folder picker will show up and you can either choose the root of device storage(~sdcard) or the Music folder. Once you tap "Use this folder" at the bottom, PowerAmp will show a list of checkboxes to select folders rooted at your selected folder. Check the desired folders and tap "Select Folders". PowerAmp should initiate a scan automatically.
Some apps cannot select the root of your device storage, but it seems like PowerAmp can. (I guess it identified itself to Google as a file manager)
I'm not following what you're trying to do with AdAway... it systemlessly modifies /etc/hosts and that will be overwritten every list update. Are you trying to get into Android/data/org.adaway?

Thanks for getting back to me.
PowerAmp has, in "Misc." options, a legacy option to manage access to SD's. That moved from my previous phone to the P4XL as part of the overall porting effort (I hate moving phones!!). Turn off the option and life is good. End of that problem.
AdAway... I'm confused about what happened right after I installed it, but it's alive and well now. It looked as though I couldn't get the host list to store anywhere in the phone. That's what prompted the question. When I looked at AdAway just now, it says it killed off five figures worth of ads. Yea!
Why things looked weird then, and look fine now, is a mystery I leave for others to fret over. Having too many other mysteries in my life (e.g. where do my car keys go when I need them the most?), I'll let this mystery age out of my "to be puzzled over" queue.