if ( !male == false && married == true ) echo “need help remembering details…”;
if ( expectations == bad ) echo “No warranty expressed or implied…”;
if ( !male == false && married == true ) echo “need help remembering details…”;
if ( expectations == bad ) echo “No warranty expressed or implied…”;
Recently purchased this book: http://www.amazon.com/Professional-Android-Application-Development-ebook/dp/B007SR7NOO/ref=pd_sim_kstore_14?ie=UTF8&m=AG56TWVU5XWC2
In Chapter 3, the section discussing “Activity state event handlers” ends with this statement:
As shown in the preceding code, you should always call back to the superclass when overriding these event handlers.
So simple question… Why?
Followed the steps on this page: http://stackoverflow.com/questions/3645319/why-do-i-get-a-sqlite3-not-found-error-on-a-rooted-nexus-one-when-i-try-to-op
Note: They look the same and should give the same result, but only did the steps that copy the binary to /sdcard first.
The sqlite3 binary came from an AVD VM I created. I used ‘adb’ to pull it off the VM.
I’ll also include a copy/paste of the steps:
$ adb push sqlite3 /sdcard/
$ adb shell
$ su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# dd if=/sdcard/sqlite3 of=/system/bin/sqlite3
# chmod 4755 /system/bin/sqlite3
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock3 /system
Followed the guide at this link: http://androidforums.com/international-galaxy-nexus-all-things-root/502204-galaxy-nexus-root-un-root-without-unlocking-bootloader.html
Used on a Galaxy Nexus using v.4.0.2 prior to receiving an OTA.
Note: The official Samsung USB drivers for the Galaxy Nexus work. No need to do the USB or FastBoot drivers step.
And don’t forget to DL OTA Rootkeeper.
Issue: Share permissions are not working as I would like. I set HomeGroup permissions to “Read” and created a user on the server with the same username as my client and gave this user “Read/Write” permissions. But I’m only getting “Write” permissions when I increase HomeGroup permissions.
Why is my client not logging in with the username?
Hopefully Google will be kind to me…
Solution: Well, apparently HomeGroup permissions override individual user permissions. I just tested this by giving myself no access, but leaving HomeGroup as RW and was still able to access my files. Then when I removed HomeGroup access, I was denied access. Not how I would like permissions to work, but oh well…
While the install of WHS 2011 went very well, getting everything setup has taken some extra time and was further complicated by network access being quite slow and unresponsive at times.
However, I may have resolved the issue very quickly. Or it was just a coincidence and the server likes me right now.
(Possible) Solution: On the WHS 2011 server, disable IPv6 support for the NIC. It was that simple and quick.
Assuming this was the issue, I’m now wondering how this was affecting the install of the client software, which took FOREVER. Could this have made that go faster?
The install of WHS 2011 went pretty smoothly.
Biggest issue was a little static electricity that froze the system during the install. Had to start over, but was not far in, so not a big loss. No hardware lost either (silver lining!).
The install automatically partitions the main drive, with no option to change. Other than the feeling of losing control, I can understand this decision.
The install DOES require a network connection to perform. Not sure why during… Afterwards when needing to do all the updates (and there are a good number) sure… But during?
I was worried that the Shuttle BIOS would not like the lack of a monitor / keyboard / mouse connected post-install, but it did not complain a bit. Win!
I did disable “Shadow Copies” on my drives. Primarily to reduce space usage since I cannot just add more drives to increase space (and got the biggest 2.5″ drives I could find). We’ve never had a need for this feature, so its not a big loss.
The client connector installs were very time consuming. The wizard says it could take 30 mins or more… Try well over 1 hour with little feedback that things are even working. At least this time, patience worked.
One Issue / Resolution: I did hit a small snag when installing the client connector software. I believe it may have been a conflict with the old client connector software, which I had already removed as a first step. However, it kept saying that it could not install because of another software install was happening (or something like that). So I restarted and that solved the problem. I guess there was something still hanging around from the uninstall.
Had an HP EX485 running Windows Home Server.
We liked it.
It died.
Took the opportunity to get my hands dirty…
Some Thoughts: