Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,812,702 Members 45,384 Now Online
XDA Developers Android and Mobile Development Forum

[HOW-TO] Google Calendar sync, sideloading on rooted 1.4.1

Tip us?
 
CSX321
Old
(Last edited by CSX321; 31st January 2012 at 05:59 AM.) Reason: link obsolete
#1  
CSX321's Avatar
Senior Member - OP
Thanks Meter 73
Posts: 139
Join Date: Aug 2009
Location: Southern IL USA

 
DONATE TO ME
Default [HOW-TO] Google Calendar sync, sideloading on rooted 1.4.1

I finally have everything set up and working the way I want on my rooted 1.4.1 Tablet, so I thought I would share.

I couldn't find anything on getting Google Calendar installed and syncing to work on a rooted 1.4.1 Nook Tablet, but here is how you can do it:

First, download the Calendar.apk and CalendarProvider.apk files for Android 2.3 from here. (Update: DeanGibson has noted this link is obsolete, but that the files can be extracted from the NT 1.4.0 acclaim_update.zip file.)
Next, copy Calendar.apk to /system/app with Root Explorer.
Now use Root Explorer to copy /data/system/packages.xml somewhere such as /media/My Files/Documents, and use adb to pull it to your machine.
Edit packages.xml with a Unix-compatible editor, and delete userId="___" and sharedUserId="___" from all the lines related to Calendar. I think there are either three or four lines. Don't delete the entire line, just the userId/sharedUserId attribute.
Save the file, push it back to the Tablet, and use Root Explorer to copy it back to /data/system. (The first time I tried to paste it, I got an out-of-memory error for some reason. I just copied and pasted it again, and it worked.)
Reboot the Tablet.
Use adb to install CalendarProvider.apk.
Reboot the Tablet.
You should now be able to enable Calendar sync for your Gmail account in Account and Sync Settings, and your Google Calendar will work, as will apps that use it, such as Business Calendar.

---------------------

Now for enabling sideloading. I tried NT Hidden Settings, but for some reason even the latest version didn't work for me to enable sideloading. I just fell back on the technique of manually enabling it in settings.db:

Use Root Explorer to copy /data/data/com.android.providers.settings/databases/settings.db somewhere such as /media/My Files/Documents, and use adb to pull it to your machine.
Make sure you have sqlite3 installed on your machine.
From a command prompt in the directory where you have settings.db (all on one line):
Code:
sqlite3 settings.db "update secure set value=1 where 
name='install_non_market_apps';"
Push settings.db back to the Tablet, and copy it back to /data/data/com.android.providers.settings/databases using Root Explorer.
Reboot the Tablet.
Unknown sources in Applications Settings should now be checked and you should be able to sideload apps again.


The Following 8 Users Say Thank You to CSX321 For This Useful Post: [ Click to Expand ]
 
elmulletlargo
Old
(Last edited by elmulletlargo; 10th January 2012 at 12:25 AM.)
#2  
Junior Member
Thanks Meter 3
Posts: 10
Join Date: Oct 2009
Default Procedure failing for me

Hi there,

I'm having trouble installing CalendarProvider.apk via adb, getting
"Failure [INSTALL_FAILED_SHARED_USER_INCOMPATIBLE]"

I have gone through packages.xml twice (missed one the first time apparently) and removed all of the userId and sharedUserId attributes from any tags having anything to do with calendar.

I found a strange key in one of the tags:

<package name="com.android.calendar" codePath="/data/app/com.android.calendar-1.apk" nativeLibraryPath="/mismatched_uid/settings_10064/fs_10028" flags="0" ft="1349c1ed328" it="1349c1ed756" ut="1349c1ed756" version="10" uidError="true">

nativeLibraryPath: this could have resulted from a prior attempt at trying to install calendar and calendarprovider without first modifying the packages.xml last week. I keep checking and reattempting am failing. Might I be on the right track with my assumption? Would you mind checking yours to see if these nativeLibraryPath and uidError tags ought to be there?

Thanks
 
Loglud
Old
#3  
Senior Member
Thanks Meter 442
Posts: 200
Join Date: Jul 2011

 
DONATE TO ME
Quote:
Originally Posted by CSX321 View Post
I finally have everything set up and working the way I want on my rooted 1.4.1 Tablet, so I thought I would share...
Out of curiosity what did you use to root 1.4.1, procedural wise?
 
CSX321
Old
(Last edited by CSX321; 10th January 2012 at 03:10 AM.)
#4  
CSX321's Avatar
Senior Member - OP
Thanks Meter 73
Posts: 139
Join Date: Aug 2009
Location: Southern IL USA

 
DONATE TO ME
Quote:
Originally Posted by Loglud View Post
Out of curiosity what did you use to root 1.4.1, procedural wise?
I used DeanGibson's minimal rooting procedure from this thread. (Edit...It was at "release candidate" when I used it.)
 
CSX321
Old
#5  
CSX321's Avatar
Senior Member - OP
Thanks Meter 73
Posts: 139
Join Date: Aug 2009
Location: Southern IL USA

 
DONATE TO ME
Quote:
Originally Posted by elmulletlargo View Post
Might I be on the right track with my assumption? Would you mind checking yours to see if these nativeLibraryPath and uidError tags ought to be there?
Yes, I think probably you are onto something. Mine has this:

<package name="com.android.calendar" codePath="/system/app/Calendar.apk" nativeLibraryPath="/data/data/com.android.calendar/lib" flags="1" ft="134bbf21a48" it="134bbf21a48" ut="134bbf21a48" version="8">

You might need to also remove one or both of those error-related attributes, then reboot and try installing CalendarProvider.apk again.
 
elmulletlargo
Old
#6  
Junior Member
Thanks Meter 3
Posts: 10
Join Date: Oct 2009
I ended up in an endless-loop boot screen and reverted to base 1.4.0 and redid the DeanGibson method. First thing after geting back to 1.4.1 with root was to do this calendar trick before things got too polluted. Now I get a process com.android.calendar stopping unexpectedly. Force Close. Not sure where to go from here
 
CSX321
Old
(Last edited by CSX321; 10th January 2012 at 08:02 AM.)
#7  
CSX321's Avatar
Senior Member - OP
Thanks Meter 73
Posts: 139
Join Date: Aug 2009
Location: Southern IL USA

 
DONATE TO ME
Quote:
Originally Posted by elmulletlargo View Post
Now I get a process com.android.calendar stopping unexpectedly. Force Close. Not sure where to go from here
At what point did you get that? I've actually done the procedure twice, because I corrupted my accounts.db file while trying to work out how to do it and had to Erase and Deregister and start over. I think I got an error from Calendar the second time at one point before I was through, but it didn't seem to interfere with the process.

Also, are you sure you got packages.xml put back in place? As I noted, the first time I tried to put it back in /data/system I got an error, and there was no file there at all. I had to go back and copy and paste my modified version with Root Explorer again. That might cause a boot loop; I'm sure it would cause some kind of major problems.

Edit...FWIW, I just had to do it again. I was messing around with build.prop and experimenting with some of the built-in apps, and I managed to erase and deregister it again. I don't know if it's necessary, but I made sure to preserve the permissions on packages.xml. (Got the same out of space error trying to paste it the first time, too.)
 
brianf21
Old
#8  
Senior Member
Thanks Meter 480
Posts: 623
Join Date: Oct 2010
Location: Davie, FL
Quote:
Originally Posted by CSX321 View Post
Now for enabling sideloading. I tried NT Hidden Settings, but for some reason even the latest version didn't work for me to enable sideloading. I just fell back on the technique of manually enabling it in settings.db:
I figured out why it was not working for some people. Busybox must be installed before using NT Hidden Settings. I will fix this in the near future.
If there is anything else that I can't help you with, please hesitate to ask.
 
CSX321
Old
#9  
CSX321's Avatar
Senior Member - OP
Thanks Meter 73
Posts: 139
Join Date: Aug 2009
Location: Southern IL USA

 
DONATE TO ME
Quote:
Originally Posted by brianf21 View Post
I figured out why it was not working for some people. Busybox must be installed before using NT Hidden Settings. I will fix this in the near future.
Ah, okay. Thanks.

Is anybody else getting Calendar sync to work beside me? I've done it this way three times now, and had no real problems.
 
elmulletlargo
Old
#10  
Junior Member
Thanks Meter 3
Posts: 10
Join Date: Oct 2009
Could you perhaps be more precise on what tags you removed the userId and SharedUserId's from? Possibly I was over-aggressive. In theory, I may be able to uninstall calendarProvider via adb, put back my original packages.xml (which I was smart enough to back up, this time ) and give it another shot without starting from a 1.4.0 wipe. I just finished getting everything back on there and hate the thought of doing it all over again. Very excited to hear that we may be just a few weeks away from putting CM9 on these and unleashing the beast!

I would love to be able to confirm this procedure for you.

Thanks,

Bill

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes