Quote:
Originally Posted by pablob
Hi Steve!
I'm sorry I haven't been following to closely, these are busy times. 
Regarding the ann* file, it seems to be an annotation, and I guess the serial number is put there to make it match the originating device.
/fridge is just a link to /intstorage, so it makes sense they have the same stuff. Once the library is set to external, I don't think any of the files in /intstorage matter anymore, only the ones in /sdcard.
Regarding my suggestion to change the serial number, you don't have to keep the old one forever! Once you restore the library (which I would hope would work), change the serial back to the Allmine one and apply the "Library fix" by hand. That should fix the library, and keep access to the market.
I did not know about the office... If you change the device in the build.prop file, you'll probably lose access to the market, though. Maybe you can switch the device depending on what you want to do? |
Quote:
Originally Posted by mytwobears
Hi Steve,
Sorry I am just now checking back.
my build.prop files list the following:
ro.product.device=edgejr
ro.product.name=edgejr
I also have the same note in my build.prop file with only the first line remmed out.
If your ro.product.name is passion, you should change it to edgejr. When you make the change to your build.prop file you should get a prompt to save the old file as a backup. After making the change, I still had access to the market.
|
============================================
Thanks for responding, pablob and mytwobears.
Regarding the build.prop items, the value for ro.product.device already was edgejr; the ro.build.product (which is said to be obsolete) and the ro.product.name both HAD a value of passion. I changed those without any losing access to the market or gaining access to the office documents in the Library.
I wasn't sure whether some of the .edge subfolders were links rather than real duplicate instances of the same files. I think the details of and variations in the file structures (such as the differences between the ones on my PE and those reported by ken_jennings in the thread he started) may be valuable in some future development problems.
What I did by making a backup before upgrading is very undesirable and hopefully very atypical <g>. However, a few others might experience similar issues.
I mentioned the ann file only, the failure to complete a restore of library files (although being accepted as a valid backup file) and the problems with office and multimedia files only because I hadn't seen them mentioned by anyone else. This suggests either that almost no one else has done this, or anyone else simply fixed it in some way (if so, I wish they would post their experience <g>).
The problem for me actually is a minor one (I don't expect to do much with office documents on the PE).
Mostly, it stimulates me to study a specific aspect of the PE.
I actually need to get used to using the PE on a regular basis to see what I tend to do with it and then consider what changes/fixes/improvements/optimizations are worth while trying.
This is a nice group of posters!
Steve
P.S. vicinc, I am not sure if your post was directed at one of my comments.