Database Users

Manual Nooter 4.5.6 Observations

My first voyage down the rooted path was to put Honeycomb on a microSD card. When B&N came out with the 1.2 update, I downloaded that and decided to go the Manual Nooter route.
First of all, many thanks to all who have worked so hard on this! My first objective was to be able to read Kindle and Nook books on my Nook Color, and that is a cinch now! This Manual Nooter setup is more stable than running HC off a card was, and I can access the stock B&N reader and Kindle and other apps without switching cards and rebooting.
I have had only one problem downloading an app from Market so far. I needed to unmount my card before the app would install, but the dev said that this is an issue with the app, not Nook Color or MN.
Gmail would not work with MN 4.5.6, though it worked with 4.5.2. But I downloaded an updated Gmail from Market, and my Gmail problem was cured.
MN includes some "unadvertised" apps, like Facebook and Twitter. I can't seem to uninstall them. Does anyone know how that might be done?
Overall, I'm a happy camper. But I would like to know how to get rid of Facebook and Twitter.

Have you tried using Titanium Backup to uninstall them?

Windsor1959 said:
MN includes some "unadvertised" apps, like Facebook and Twitter. I can't seem to uninstall them. Does anyone know how that might be done?
Overall, I'm a happy camper. But I would like to know how to get rid of Facebook and Twitter.
Click to expand...
Click to collapse
I'm pretty sure those aren't part of MN. If they are, I don't know what they're stuffed in because there isn't an apk for them.
By the way, gmail worked perfect me right out of the gate.

doncaruana said:
I'm pretty sure those aren't part of MN. If they are, I don't know what they're stuffed in because there isn't an apk for them.
By the way, gmail worked perfect me right out of the gate.
Click to expand...
Click to collapse
Looks to me like Twitter and Facebook were in 4.5.2, but were not included in 4.5.6.
Anyways, if you don't want them, just to go system\app, mount as RW, and delete the apk.
EDIT: oh and for the gmail, I found the upgrade from 4.5.2 to 4.5.6 caused a FC on open. But deleting the cache\data cures it. I guess a re-install also works!

Would I need an app like Root Explorer to be able to mount as RW when I go to system/app? I see that a lot of folks have Titanium backup and Root Explorer, so maybe I'd find them pretty useful.
Thanks for the replies.

Both are well worth the money but imo root explorer is a must buy if you nooter.
Sent from my SAMSUNG-SGH-I897 using XDA App

I installed Titanium Backup, and I was able to uninstall Facebook and Twitter with it. Root Explorer looks like something worth the price, too.
Here's a newbie question: Titanium Backup gave me a window telling me I should activate USB debugging on my Nook Color. I'm guessing that USB debugging involves me connecting my Nook Color to a PC or laptop, but what does it actually mean? Thanks!
Edit: Okay, I found my answer for USB debugging. If I want to use ADB to push things into my Nook, or use Titanium Backup to backup my apps, I'll need to enable USB debugging. (Does that sound right?)

Apps force closing
I've rooted the NC since I first got it and tried all different versions when I finally settled on AutoNooter and loved it. When the 1.2 update came out I updated and hated the stock version so went with ManualNooter as soon as it was "kind of up and running OK". The NookHome app takes care of the In-Store stuff. Thanks to everyone working on all of these updates.
The problem I had was that GoogleSearch bar and News and Weather app would force close. Managed to fix the GoogleSearch bar with the FakeGPS app. works fine now. ---- Still have the News and Weather app which came with the installation .zip 4.5.6 in MN force closing though. Tried force-stop and clear Data didn't do anything.
Can't find it on Market either so I could reinstall it. Anyone have ANY ideas? I always loved that app on previous versions and would like to use it.

andream2g said:
I've rooted the NC since I first got it and tried all different versions when I finally settled on AutoNooter and loved it. When the 1.2 update came out I updated and hated the stock version so went with ManualNooter as soon as it was "kind of up and running OK". The NookHome app takes care of the In-Store stuff. Thanks to everyone working on all of these updates.
The problem I had was that GoogleSearch bar and News and Weather app would force close. Managed to fix the GoogleSearch bar with the FakeGPS app. works fine now. ---- Still have the News and Weather app which came with the installation .zip 4.5.6 in MN force closing though. Tried force-stop and clear Data didn't do anything.
Can't find it on Market either so I could reinstall it. Anyone have ANY ideas? I always loved that app on previous versions and would like to use it.
Click to expand...
Click to collapse
Hrm... I was of the understanding that News and Weather was FCing because there was no location. This isn't the case if you're using FakeGPS perhaps you could grab and post a logcat from when trying to run it?

I'm also experiencing this with News and Weather. I just installed Fake GPS and it took care of the Google search issue I also had. I went from a stock 1.2 to 4.5.6.
Also anyone had any luck with HBO GO app? It isn't listed in market, but I tried to download from Android site and it says I have no Android phone in my account......

GabrialDestruir said:
Hrm... I was of the understanding that News and Weather was FCing because there was no location. This isn't the case if you're using FakeGPS perhaps you could grab and post a logcat from when trying to run it?
Click to expand...
Click to collapse
I appologize if this log isn't quiet what you had in mind. It seems to forceclose because it can't get a location. Maybe I need to find something else to fake a location.
Here is a log:
cmp=com.google.android.apps.genie.geniewidget/.activities.NewsActivity }
05-09 10:54:40.124 I/ActivityManager( 966): Start proc com.google.android.apps.genie.geniewidget for activity com.google.android.apps.genie.geniewidget/.activities.NewsActivity: pid=1392 uid=10003 gids={3003, 1015}
05-09 10:54:40.407 D/WifiService( 966): ACTION_BATTERY_CHANGED pluggedType: 0
05-09 10:54:40.831 E/AndroidRuntime( 1392): FATAL EXCEPTION: Thread-12
05-09 10:54:40.831 E/AndroidRuntime( 1392): java.lang.IllegalArgumentException: provider=network
05-09 10:54:40.890 W/ActivityManager( 966): Force finishing activity com.google.android.apps.genie.geniewidget/.activities.NewsActivity
05-09 10:54:40.904 I/ActivityManager( 966): Process com.google.android.apps.genie.geniewidget (pid 1392) has died.
05-09 10:54:40.904 W/ActivityManager( 966): Scheduling restart of crashed service com.google.android.apps.genie.geniewidget/.GenieRefreshService in 5000ms
05-09 10:54:40.906 I/WindowManager( 966): WIN DEATH: Window{4a12f678 com.google.android.apps.genie.geniewidget/com.google.android.apps.genie.geniewidget.activities.NewsActivity paused=true}
05-09 10:54:40.960 W/InputManagerService( 966): Got RemoteException sending setActive(false) notification to pid 1392 uid 10003
05-09 10:54:45.921 I/ActivityManager( 966): Start proc com.google.android.apps.genie.geniewidget for service com.google.android.apps.genie.geniewidget/.GenieRefreshService: pid=1409 uid=10003 gids={3003, 1015}
ActivityManager( 966): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=com.google.android.apps.genie.geniewidget/.activities.NewsActivity }
05-09 10:57:21.527 E/AndroidRuntime( 1409): FATAL EXCEPTION: Thread-12
05-09 10:57:21.527 E/AndroidRuntime( 1409): java.lang.IllegalArgumentException: provider=network
05-09 10:57:21.573 W/ActivityManager( 966): Force finishing activity com.google.android.apps.genie.geniewidget/.activities.NewsActivity
05-09 10:57:21.603 I/ActivityManager( 966): Process com.google.android.apps.genie.geniewidget (pid 1409) has died.
05-09 10:57:21.603 W/ActivityManager( 966): Service crashed 2 times, stopping: ServiceRecord{4a29cc20 com.google.android.apps.genie.geniewidget/.GenieRefreshService}
05-09 10:57:21.613 I/WindowManager( 966): WIN DEATH: Window{4a2f6590 com.google.android.apps.genie.geniewidget/com.google.android.apps.genie.geniewidget.activities.NewsActivity paused=true}
05-09 10:57:21.700 W/InputManagerService( 966): Starting input on non-focused client [email protected] (uid=10049 pid=1038)
05-09 10:57:21.702 W/InputManagerService( 966): Client not active, ignoring focus gain of: [email protected]
05-09 10:57:23.271 W/InputManagerService( 966): Got RemoteException sending setActive(false) notification to pid 1409 uid 10003
05-09 10:57:31.654 I/ActivityManager( 966): Starting activity: Intent { act=android.intent.action.MAIN cat=[android.intent.category.LAUNCHER] flg=0x10200000 cmp=ukzzang.android.app.logviewer/.act.MainAct }
05-09

i was able to install Galery 3D from Android 2.3 and Gingerbread keyboard as well from this thread http://forum.xda-developers.com/showthread.php?t=880068
Manual Nooter rocks ...

I applied manual nooter 4.5.6 to my stock 1.2 and I can't get any of the GApps to work (Market, Gmail, GSearch, News and Weather). They all just force shut down as soon as they start. I've looked at all the apps in the Application Manager and none of them have anything in the cache. I've tried shutting them all down, clearing the data and rebooting, but I'm still not getting anything.
Looking at the luck people were having with the faked location I enabled Allow Mock Locations in the Development Settings, but I can't find anywhere to actually set the location. Since I can't access the market, and 4.5.6 didn't come up with a file manager I can't load any apps (i.e. FakeGPS). Anyone have any ideas?

I think I figured out what most of my issues were... I hadn't done a thorough enough reset when I un-rooted 1.1 to install the B&N 1.2 update. I used clockwork mod to do a factory reset, reinstalled manual nooter and the GApps that are not location dependent are now working. Weird thing... I had to go through the steps for the partial market display. That worked and I installed Astro File Manager. However, something about doing that killed the Market app... started getting the forced shutdown. Gmail still works and YouTube still works, but the Market won't load anymore.

I am replying to this thread with my experience to perhaps further a solution to the remaining problems. I have been running a Nook rooted with Auto Nooter. When 1.2 came out, I restored it to stock, updated to 1.2 and rooted with 4.5.6. I initially had a visibility problem with the market, but following the instructions at these forums, I cured most of that. I have noticed the following remaining issues:
1. Like everyone else, I have found that News and Weather doesn't work; it simply opens and closes.
2. Regarding the market, even after making the visibility fix, I have the following problems:
--The "downloads" tab in the market showed all but one of the apps that I had purchased before the 1.2 update, etc., but it showed none of the free installs. By going to the market on my computer browser, I was able to see all of the old downloads, including the free ones, and the one paid one that didn't show on the Nook. However, I couldn't download anything from there because it insisted that there was no "phone" associated with this account. Of course, this was easily solved for the freebies by downloading them again.
--This one is truly bizarre. The purchased app that I have not been able to recover is something called iBird Pro (for which there is a corresponding free app). This app worked fine under the Auto Nooter. When I search for "iBird" in the market from the Nook, it returns a pick list that includes the words "IBird", "ibird pro", and other similar words and phrases. If I pick any of these for my search term, it returns a response that there are no matches for the word in the market. This seems impossible since the market is clearly getting my request corrrectly, in fact guessing the word before I finish typing it, and from that point it shouldn't matter what my side of the conversation is doing. Of course, if I try the same thing on my desktop, it returns with a list of programs, including IBird Pro. I have tried getting to the app in others ways, such as searching for "bird." The market returns other matches, but not the one I want. I have tried to get at this app using the website "android zoom". When I have a link sent to my Nook by the android zoom website and try to access the market with it, I get an error message. I tried android zoom with an app I was able to retrieve from the market and it worked. I don't know if this happens with any other app, but I'd be surprised if it did not.

I've done some additional research here as well and what I've discovered is that I'm getting a single download out of the Market. After that the application doesn't seem to run anymore. I've tried redoing the "fix market" steps and rebooting, but after the first market download/install the Market App just won't run anymore. Doesn't seem to matter what the app is either as I've tried a couple. The only similarity so far is that I've stuck with free apps.

Nook Social App broken after root
I read. A lot, which is why I bought the NC. The thing that made me root it was a.) I root everything and b.) email on the NC SUCKED and very few apps (missed my Maildroid). Since I do read and share what I read (I'm a writer by day, tech junkie at night) I'm a little disappointed that NC social sharing app that came with stock is not letting me change the password settings to my FB account. I recently changed my FB password and went into the stock settings to change the pw and I get an, "Invalid Parameters!" message. How do I correct that? It is really important to me to have that feature.

Does changing the date actually force the update check?

Can anyone confirm that changing the date actually forces a check? Though the idea has been tossed around here like truth for a couple of days, I have seen only one post where someone said it works. Everyone else has said something along the lines of: I came home and it was up.
Everyone knows that if you set the clock forward, it says that the system was checked under system updates. Sorry, but that's not proof that it checks. That's proof that update check clock changes. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:
1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.
Can someone who's gotten the update explain what it looks like? When you turned it on, did it come up right after the animation? If you did the date trick, did you click "set" and it popped up immediately on screen? I am starting to think that the date change thing is only slowing this down; it just resets the clock for the update, it doesn't actually force the check.
Anyone have any other ideas? I am supposed to be studying for a final which is certainly why I'm obsessing about this, but I really can't help it. Anything to take my mind off studying for that horrible class. This final is going to kill me. (Then again, it's the last one I will EVER take!!!)

No it hasn't worked for me.

Coldheat1906 said:
No it hasn't worked for me.
Click to expand...
Click to collapse
Thanks. It hasn't worked for many people. I'm curious if anyone knows if it CAN work, or if it's just a myth.

the update will appear as a notification on the lower right hand of your Xoom kin a like a notification like you are downloading something from the market.

slack04 said:
Can anyone confirm that changing the date actually forces a check? ...
Click to expand...
Click to collapse
On my Wifi only Xoom it forces a check.
For example;
1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm
So it did force a check.
Whether or not an update is available for your Xoom is a different story.
The date change will force a check but not force the actual update.

laredo7mm said:
On my Wifi only Xoom it forces a check.
For example;
1. My Xoom says it last checked for an update at 1:10pm and it is now 6:10pm on the same day
2. I change the date to one day in advance
3. I go to sytem updates and it says it last checked at 6:10pm
So it did force a check.
Whether or not an update is available for your Xoom is a different story.
The date change will force a check but not force the actual update.
Click to expand...
Click to collapse
Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post. I am asking if anyone has proof that changing the clock date actually forces a check. Proof would be either:
1) Someone has had the update actually happen immediately after changing the clock; or
2) There's evidence of internet activity consistent with checking for an update.

you can force an update check using these steps:
1. hold power+volup, the xoom will reboot
2. after reboot go to system settings and check for updates

doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.

ruinah said:
doin this hasn't worked for me at all. Tried several times even with reboots. Yes the time changes but doesn't mean it really did anything. Frustrated the Wifi users are rolling today and here I sit with 3G and nothing still.
Click to expand...
Click to collapse
Yesterday I re-imaged my xoom to stock but realized too late that I was using 3.0 instead of 3.0.1. I went in and changed the date and set it back to automatic. My Xoom immediately started downloading the 3.0.1 patch. That is about as much proof as I can provide.

Yes it does force a check
This is what shows up in the logcat after changing the date:
D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
D/Beautiful Widgets( 846): Received Weather refresh Intent
E/Beautiful Widgets( 846): Acquiring new WakeLock on an existing notheld instance
D/Beautiful Widgets( 846): Service for Weather started
V/Beautiful Widgets( 846): Service AccuWeather onStart()
D/Beautiful Widgets( 846): Service AccuWeather Thread started
I/Beautiful Widgets( 846): Provider is network
I/Beautiful Widgets( 846): Requesting location update
I/EventLogService( 247): Aggregate from 1307904746624 (log), 1307904746506 (data)
E/TelephonyManager( 247): Hidden constructor called more than once per process!
E/TelephonyManager( 247): Original: com.google.android.location, new: com.google.android.gsf
I/CheckinService( 247): Preparing to send checkin request
I/EventLogService( 247): Accumulating logs since 1307904965403
D/dalvikvm( 846): GC_CONCURRENT freed 867K, 13% free 8280K/9479K, paused 3ms+4ms
I/CheckinTask( 247): Sending checkin request (1486 bytes)
D/dalvikvm( 846): GC_CONCURRENT freed 561K, 12% free 8406K/9479K, paused 3ms+3ms
V/AlarmClock( 8642): AlarmInitReceiver finished
D/dalvikvm( 133): GC_CONCURRENT freed 3891K, 29% free 21271K/29639K, paused 4ms+10ms
D/CalendarWidget( 8547): Scheduled next update at [1307941200000] 00:00:00 (+603 mins)
D/dalvikvm( 846): GC_CONCURRENT freed 963K, 14% free 8177K/9479K, paused 5ms+7ms
D/dalvikvm( 846): GC_CONCURRENT freed 494K, 12% free 8348K/9479K, paused 4ms+3ms
D/dalvikvm( 227): GC_FOR_ALLOC freed 1629K, 3% free 124319K/127879K, paused 77ms
D/dalvikvm( 227): GC_CONCURRENT freed 519K, 3% free 124143K/127879K, paused 2ms+13ms
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
As you can see I still haven't gotten 3.1

El Daddy said:
This is what shows up in the logcat after changing the date:
D/SystemClock( 8596): Setting time of day to sec=1307904965
D/SystemClock( 133): Setting time of day to sec=1305226357
...
...
...
I/CheckinTask( 247): Checkin success: https://android.clients.google.com/checkin (1 requests sent)
I/CheckinService( 247): From server: Intent { act=android.server.checkin.FOTA_CANCEL }
Click to expand...
Click to collapse
slack04 said:
Sorry, but that's not proof that it checks. That's proof that update check clock changes. I thought that was clear in my first post...
Click to expand...
Click to collapse
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.

laredo7mm said:
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.
Click to expand...
Click to collapse
Excuse me? Yeah, I edited the post to make my question more clear.
Your post was not useful; in fact it showed that you hadn't really thought through the process before you posted. I wasn't rude to you, I just pointed out the error in your logic, which made me realize that I should go back and clarify my question. Who's the "d-bag" here?

Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.
Wtf?
Sent from my Xoom using XDA Premium App

El Daddy said:
Huh? I edited my post to bold the checkin. I skimmed through this thread and thought I would confirm to people it did indeed check in. I'm not trying to show anyone up. Just trying to be helpful.
Wtf?
Sent from my Xoom using XDA Premium App
Click to expand...
Click to collapse
Thanks dude, you answered the question. He was actually talking to me; I couldn't tell you what his problem is, though. In any case, you've answered the question, so I'm going to go back to clock-changing-update-checking right now! Thank you!

well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.

I explained how this works in my post below:
http://forum.xda-developers.com/showthread.php?t=1076295

RadDudeTommy said:
well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.
Click to expand...
Click to collapse
It's moot at this point, but it was when you wrote your post also. What I was suggesting was that, if it wasn't actually checking by changing the date, then we could be stopping the actual update check from happening by trying, therefore setting us back by 12 hours (about the frequency of the automatic checks) every time we tried to "cheat." Of course, now that it's shown that the check does actually query the server (and that makes very little difference to when you actually get your update) my original guess (not statement) is obviously incorrect.

laredo7mm said:
Well, there you have your proof. Now, go study and quit being such a d-bag. I guess you were not clear since you had to go back and edit your post after I submitted my initial response.
Click to expand...
Click to collapse
+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.
Sent from my ADR6300 using XDA App

RadDudeTommy said:
well I'm just glad its been proven. And I don't agree with the ops original statement that it would have caused an issue if it didn't actually force a check. Only because I don't feel that changing the date would actually affect anything to do with checking for an update, either way it is checking the same server w/the same access codes.
For example, if someone would have 3.0 and set the date back to the xooms launch day and ran a check for an update would still be updated to 3.01 or if lucky 3.1.
Like the date on your xoom is only for creating time stamps on the xoom.
Click to expand...
Click to collapse
Suppose our entire solar system was contained in a drop of water abiut to get wiped by a windshield wiper?

kyoteqwik said:
+1
Really getting tired of this guy talking down to everyone. Don't know when I have ever see someone as condescending.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
That's friendly.

The differences in the book icon from 1.1 to 1.2

Seems like there are precious few of us out there still using rooted stock - probably 90% of the posts refer to CM7. Personally I tried it (around r83 or so) and it didn't do anything for me, so I'm still on rooted stock 1.2. And I would love for that damned book icon to still work like it does on my rooted 1.1!
Eventually the OS kills the home app if it's just in the background (or something happens) and even that doesn't allow it to work anymore (until you 'refresh' it). So I was wondering if anyone else even cares anymore or if there's any possibility of some more work towards getting it operational. I'd be glad to help in any way I could. I've even kept one of my two nooks on 1.1 just because it still works there even after rooted so I could compare or something.
Anyone still interested in getting the book icon to work on 1.2??

Well, for what it's worth, a little logcat action yielded some interesting info (at least to me).
On my 1.1 rooted nook, with the home launcher *not* running, when I press the book icon it actually starts the nook home app up and the affiledownload service:
D/StatusBar( 829): Sending intent to launch last book
I/ActivityManager( 829): Start proc com.bn.nook.home for broadcast com.bn.nook.home/.HomeBroadcastReceiver: pid=2233 uid=10000 gids={1015, 3003, 2001}
I/ActivityManager( 829): Start proc com.bn.nook.affiledownloadservice for service com.bn.nook.affiledownloadservice/.AFfileDownloadService: pid=2241 uid=10000 gids={1015, 3003, 2001}
D/FileDownloadService( 2233): initService() bound with true
I/ActivityManager( 829): Starting activity: Intent { act=android.intent.action.VIEW dat=<...path to book to be read....> }
Afterward, I see both the home and affiledownload service are now running on 1.1
Now, on my 1.2 rooted nook, with the home app not running, when I press the icon, it tries to launch, but seems to fail:
D/StatusBar( 1049): Sending intent to launch last book
I/ActivityManager( 1049): Start proc com.bn.nook.home for broadcast com.bn.nook.home/.HomeBroadcastReceiver: pid=13588 uid=10000 gids={1015, 3003, 2001}
D/DeviceManagerBroadcastReceiver( 1284): action (com.bn.devicemanager.ACTION_DEVICE_USAGE)
D/FileDownloadService(13588): initService() bound with true
I/DeviceManagerHandler( 1284): HandleMessage(): msg.what (7)
D/FileDownloadService(13588): Service Check :Service is ready
D/FileDownloadService(13588): onServiceConnected() connected
Subsequent attempts no longer try to launch the services, because they are loaded, but the icon still doesn't work.
I haven't gone any farther into the difference yet and I'm just sort of clumsily diving through this. I'll look at the home app and the device manager next to see if anything is of interest there. My hope is that I'll find something that will flip the light on to one of the devs and they can throw something together to fix this.
If anyone else has anything to offer or thinks I'm crazy or on the wrong track, please pipe in...

Little more work here and I looked at the events buffer as well, turned on the timings and merged them. I'm not sure why, but you can see that 1.1 launches the affiledownload service which it seems is key to opening the file. For 1.2, the devicemanager pops here instead of the downloadservice, but I don't get why.

In App-billing Cycle Question

Hi Guys,
I am developing a word game app similar to 4 pics 1 word and other trivia games.
I have a question on the in-app billing of coins and other items.
I have used the google play apk in my code, and the in-app purchases work fine FIRST time around.
However, when i click on the option i have purchased previously, nothing happens and i receive an error.
For example, If i purchase 100 coins for $1 the first transaction will be fine, and i will receive my 100 coins.
But then if i want to purchase the 100 coins again, it will not try to connect to google play and i will receive an error.
Have pasted the log of the error below:
java.lang.IllegalStateException: Could not execute method of the activity at android.view.View$1.onClick(View.java:3633) at android.view.View.performClick(View.java:4240) at android.view.View$PerformClick.run(View.java:17721) at android.os.Handler.handleCallback(Handler.java:730) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:137) at android.app.ActivityThread.main(ActivityThread.java:5103) at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:737) at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:553) at dalvik.system.NativeStart.main(Native Method) Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Method.invokeNative(Native Method) at java.lang.reflect.Method.invoke(Method.java:525) at android.view.View$1.onClick(View.java:3628) ... 11 more Caused by: java.lang.IllegalStateException: Can't start async operation (launchPurchaseFlow) because another async operation(launchPurchaseFlow) is in progress. at com.android.vending.billing.util.IabHelper.flagStartAsync(IabHelper.java:794) at com.android.vending.billing.util.IabHelper.launchPurchaseFlow(IabHelper.java:358) at com.android.vending.billing.util.IabHelper.launchPurchaseFlow(IabHelper.java:324) at com.bhn.wordgame.ShopActivity.on2(ShopActivity.java:86) ... 14 more
has a similar issue occurred for any other developers? Cant seem to figure out why this happens
Thanks in advance for your help!

Omar7 said:
java.lang.IllegalStateException: Could not execute method of the activity at
Click to expand...
Click to collapse
Without seeing the code, it's impossible to tell exactly. But it's saying that whatever method your calling cannot be called at that time - either the play library hasn't been initialized yet, or you're not consuming the purchase so that the user cannot buy it again. (See: https://developer.android.com/google/play/billing/api.html)
--Mike.

The problem is this here:
Omar7 said:
Code:
Caused by: java.lang.IllegalStateException: Can't start async operation (launchPurchaseFlow) because another async operation(launchPurchaseFlow) is in progress.
Click to expand...
Click to collapse
So it seems that you're not properly finalizing your previous purchase or you aren't correctly initializing the second payment ( but I have to say, I don't know the library, so can't help you with the details)

Are you executing that in the main thread?

[Q] TetherGPS client on NST; or, any hope of keeping background services stable?

So I've been toying with the idea of using the NST as a hiking pad. Backcountry Navigator seems to run fairly well on the Nook. After enabling mock locations via Sqlite3, I was able to get TetherGPS picking up GPS location data from my phone... except the service keeps dying.
At first, I thought the service stopped updating the location because of the app's paywall. But after purchasing the full version of TetherGPS, I determined that the Tethergps service seems to be dying after a resource-intensive application such as Maps or Backcountry Navigator starts getting demanding.
Adb reads:
I/NotificationService( 880): enqueueToast pkg=com.comptonsoft.tgps [email protected] duration=0
~service starts~
I/ActivityManager( 880): Process com.comptonsoft.tgps (pid 5222) has died.
W/ActivityManager( 880): Scheduling restart of crashed service com.comptonsoft.tgps/.TGPS_client in 14063ms
I/ActivityManager( 880): Start proc com.comptonsoft.tgps for service com.comptonsoft.tgps/.TGPS_client: pid=5393 uid=10057 gids={3003}
~service attempts to restart, but the notifications flag just hangs and GPS updates do not commence. service needs to be restarted manually~
I tried freeing up a sizeable chunk of RAM for testing, but extra available RAM didn't change the behavior. I'm wondering if I couldn't be hitting some limit in maximum concurrent processes. Are there any settings I could be pushing via Sqlite3 to allow more processes?
I am of course open to any other suggestions or theories.
I'm currently using Pinguy's custom NST firmware. I'll try to make certain the behavior is the same with other rooting methods.

You could try Memory Locker app, it is a paid app but is very cheap. Works on Android 2.1 and working on my NST.
https://play.google.com/store/apps/details?id=com.smartprojects.MemoryLocker