I use multiple ROMs how can I have CoPilot installed on them?

  • Question
  • Updated 1 year ago
  • Answered
At different times, I install and use an assortment of ROMs ranging from 2.1 to 2.3.4.
What I want to know is why I can't have my purchased copy of Copilot installed on all of these ROMs which I flash to only ONE device?
For example, I purchased Copilot9 while using a 2.3.4 ROM but I then flashed a 2.2 ROM. I tried to install my purchase but was told by Copilot that it was already in use on another device. This is incorrect. The device is the same, the ROM is different.
I don't see why you are checking anything other than the phone's IMEI, my Copliot ID and the purchase details from the Market.
This is like buying a pair of shoes but being told that you can't wear them if you change your socks!
Also, the instructions given in the FAQ for transferring Copilot to a new ROM are incorrect. They state "You can deactivate CoPilot Live by selecting Menu > Settings > Licensing then press Deactivate" - no such menu exists.

f1she4rs

  • 16 Posts
  • 5 Likes
  • confused & disappointed

Posted 3 years ago

  • 15

UncleMike

  • 175 Posts
  • 25 Likes
If you're flashing multiple ROMs, then you're already rooted. In this case you can use Titanium Backup to backup and restore Copilot when switching ROMs. While I agree that there should be no limit to activations on the same device, this approach works for me and avoids any activation headaches.

f1she4rs

  • 16 Posts
  • 5 Likes
Thanks that was the first thing I tried ;)
When I restore app+data it asks me to create a new ID or use existing. Then it says "We're sorry. Product key is already in use on another device".
When I restore app without data, it first unpacks the copilot libs/data then asks me to create a new ID or use existing.... and we're back to the same issue.

Are you sure you've done this with Copilot 9 (it works for me with Copilot 8)? If so, can you offer any other suggestions.

@Copilot team - it would be nice to get an official response to this as I can imagine it will cause issues when official ROM updates are released. Also, can you publish what device data you are using to check for multiple installations? I think we ought to know...

leesmart1971

  • 1 Post
  • 0 Likes
I asked the same question on this forum and was told that I could move my product key once (requiring an email to ALK support) but would fall foul of the activation policy if I keep switching ROMs. Not happy.

eezytiger

  • 110 Posts
  • 12 Likes
Same problem here. I've got a support ticket raised and am awaiting a sensible response. So far I've only had a worthless one.

Fortunatey I had a Nandroid backup of my original ROM so I was able to restore everything, but the old ROM was 2.1 and I want to run 2.3. Not happy. :(

What happens when I replace the phone completely? More hoops to jump through or more money to pay? Neither option is acceptable. I have other paid software and I have no problem re-installing that following a complete wipe and ROM change. Why does CoPilot have to be so sucky at this basic stuff? Link the licence to my Google account, not the hardware or OS I'm running at the time of first install.

UncleMike

  • 175 Posts
  • 25 Likes
I have only tried using Titanium Backup with Copilot v8, though I was successful.

These additional measures that ALK goes through to protect their product are really unnecessary, and only serve to inconvenience legitimate users. I thought these bizarre antics went out with the '90s.

I don't see why the app would be tied to the OS version in any way. If when Copilot starts, it sees a different (presumably newer) Android version than it did the last time it started, how is it to know whether you've installed a new ROM, or simply applied a manufacturer supplied OTA update? Will non-rooted users who go receive OTA updates go through this same headache?

billpier314

  • 20 Posts
  • 0 Likes
I had Copilot8 and witched ROMS all the time with no issue and v9 will not let you/me switch ROMs and if you call them only once?! If I had known that it would have been a no sale. Seriously you need to tie it to the phone equipment ID number. What's going to happen with OTA ROM updates? Or is that your plan to generate income? if so all you're going to do i lose customers. This one has one foot out the door already.

eezytiger

  • 110 Posts
  • 12 Likes
Applying a new ROM can change the "name" of the hardware, as is the case when installing Cyanogenmod 7 onto my UK Orange San Francisco. Maybe if the device name renamed unaltered there would be no problem, this time, but why not use something like IMEI, if you must tie it to a device (bad idea) or [B]GOOGLE ACCOUNT[/B], which is what was used to buy the app in the first place.

f1she4rs

  • 16 Posts
  • 5 Likes
The fact is that my IMEI doesn't change when I change my ROM and my Market history doesn't change when I change my ROM. These are really the only things that ALK need to check.

If Android Market says "purchased" for my device and lets me download the software then it should run. End of story.

The restriction I am facing would appear to be in direct breach of the EULA which states that I can have the software installed on any one device at a time. The EULA only mentions OS version restrictions if you are installing to another device. The fact that ALK's anti-piracy technology is flawed can not negate the other contract terms regarding installations.

I may pursue this as a legal matter should ALK refuse to correct the issue.

tiserotta

  • 2 Posts
  • 0 Likes
I'm in the same boat. Last alk product I will purchase. In fact I'm pissed with google for their crappy 15 minute refund policy also! Heck by the time the maps are downloaded you're 15 minutes has expired!

mark

  • 4 Posts
  • 0 Likes
Couldn't agree more, had same, won't buy again unless issues resolved. Rom's should make no difference and don't get me started on poi issues appreciate they're looking into it and a patch may be forthcoming but this should all have been resolved prior to release. Still waiting for pocket world GPS cam issue to be sorted. Very disappointed.

tilbury

  • 5 Posts
  • 3 Likes
There is a least one way to solve this issue that worked for me:

Prequesites: new rom, copilot folder on sd, app not installed

1. Rename SD-folder by e.g adding .bak
2. Install copilot from market, start and try to login till "sorry" message appears
3. Start a filemanager of your choice and delete the new copilot folder while app is still running.
4. Switch back to app and login should work (of course error some messages pop up as folder is missing). Go till app tells you it can't dl maps cause basic maps are missing.
5. Copy maps folder from copilot.bak folder to the 'real' copilot folder, which should be already recreated.
6. Switch back to app and voila, it works (at least for me). maybe you have to restart/kill copilot.

I pretty sure the 'trick' works also in a simpler way (maybe just delete everyhing but the maps folder) but this is how i worked for me just 1 hour ago.
The first time i managed to get it work was 2 days ago and i'm sure it was simpler, but i can' remeber exactly cause ... hmm .. let me say 'to much wine and too much song' :D .

Hope it works for you also,

Cheers & happy navigating

billpier314

  • 20 Posts
  • 0 Likes
All mine does is it keeps unpacking and rebuilding the folder and of course tells me "sorry" Activations key is in use. I switch out of it (not close) but whenever I return to it after deleting folder it just acts like I'm reopening it and re-installs the folder. ALK this is the type of SHEEZZZ that makes people crack your software and pirate it. And the excessive activations policy. Is just more BS

You went from the BEST app I ever bought for my phone to DO not buy again status.
Good Job!

tiserotta

  • 2 Posts
  • 0 Likes
Thanks Tilbury...this works!! I just renamed the original folder on the SD card by adding the extension ".bak" then installed app from the market. It let me sign in with my existing ID and never said "sorry this key has already been activated on another device". I then just copied the map folder from the renamed .bak folder (NA for North America) to the new file that was created when copilot was installed from the market and wala it works again!

Thanks for this find!!!

tilbury

  • 5 Posts
  • 3 Likes
Glad to help you and that it obviously works for more people than just me ;)

rmanaka

  • 4 Posts
  • 0 Likes
Nope, doesn't work as it still won't transfer any of your PAID add-ons!!!

eezytiger

  • 110 Posts
  • 12 Likes
I've just successfully re-activated CoPilot after updating my ROM from 2.1 Eclair to 2.3 Gingerbread. I only followed step 1 from Tilbury's post....

1. Rename SD-folder by e.g adding .bak

and progress is as smooth as silk. I logged on with my original ID without problem and quickly went through the customisatoin option.

I've chosen to re-download the maps rather than copy anything over from the original folder, since I'm on WiFi with an unlimited broadband service and I'd rather start "clean" than risk any contamination from the original install.

Everything is working as expected.

rmanaka

  • 4 Posts
  • 0 Likes
See above!!!

f1she4rs

  • 16 Posts
  • 5 Likes
thanks tilbury & eezytiger - eezytiger, I'm thinking your method might let me switch back & forth between more than one ROM so long as I have mulitple copies of my copilot folder on SD.... one for each ROM...

@ALK, this still needs an official response and fix though!

eezytiger

  • 110 Posts
  • 12 Likes
The way this seems to work is to not have a pre-existing folder structure which can be recognised by CoPilot. If you want to create a series of "backups" of folder structures, one per ROM, then you can try that, but I'd be worried about overwriting an important file from a backup which might screw with the most recent installation/activation. Who knows how the activation is recorded on the device itself? Is there a time stamp or some sort of hash value that gets generated with each install? Does that need to match with a server based record? Could there be a server based activation count limit which you might hit after 2, 3, 4 installs? I'm thinking caution might be advisable. So far we have some lucky results. Will the luck continue?

xdalaw

  • 6 Posts
  • 1 Like
Same problem here. Thanks for the help from the other frustrated users!

As for ALK, I opened a ticket yesterday. This is a real PITA, especially since version 8 did not have this issue when flashing through different ROMS.
CoPilot really needs to ease-up on their licensing scheme with Android. This isn't 2005, and these are no longer $75.00+ apps, but rather $9.99 apps. And, they should really be making things easier for those of us who still bother to buy GPS software, as Google keeps enhancing it's own offering, and keeps moving towards making Google Maps Navigation a fully off-line product.
Is ALK trying to drive it's (dwindling) remaining android customers away? Sure feels like this when they do something as frustrating as this.

xdalaw

  • 6 Posts
  • 1 Like
Another issue is transferring Live Traffic subscriptions. I was able to transfer my version 8 remaining subscription to my first installation, but when I flashed another ROM and created a new SD folder which allowed me to install maps, my traffic subsciption would not transfer. It remains stuck with my first ROM I put it on.

tilbury

  • 5 Posts
  • 3 Likes
you have to choose transfer/restore licence (using german version so i don't know exactly-button in the upper right corner) under Active Traffic oder the same under account.
A funny side note is, that after my last 'reactivate' i got 13 month of Active Traffic, not just 12.

xdalaw

  • 6 Posts
  • 1 Like
I was able to transfer it the first time from v.8 to the new version. But, I wasn't able to do so between ROMs.

tilbury

  • 5 Posts
  • 3 Likes
strange, for me it worked. Have you restored via "Active Traffic" option or by "My Account" ?

xdalaw

  • 6 Posts
  • 1 Like
Tried but didn't work after the first "transfer."

f1she4rs

  • 16 Posts
  • 5 Likes
OK, I've done a little more poking around here and it seems that the data ALK are hung up on is in the /save/ subfolder.

Each installation gets its own product key (why, I don't know) and this is stored in /save/pk.txt
The product key is also contained in /save/DeviceInfo.xml

So, the easiest way to handle multiple installs is to just delete (or rename) your /save/ folder before installing Copilot on a new ROM. Also do this if you reflash a backup ROM that already has Copilot installed.

Copilot will happily replace the missing data and you still have your maps, places etc

xdalaw

  • 6 Posts
  • 1 Like
This worked well for the maps I previously downloaded on an earlier ROM. Still won't allow my traffic subscription to work from v.8 (previously moved over to original ROM being used when bought new CP.)
Thank you, though, for this tip!

tilbury

  • 5 Posts
  • 3 Likes
As i said, there has to be a smarter method than mine. ;)
But i pretty sure that i have tried the simple one with just renaming the original folder before and it doesn't work.

As i have to clean up my SD cause nandroid does not work anymore, i will try again if the simple method works and it was some fault by me.

Btw. thnx for your find/info f1she4rs

EDIT: Without trying again, some thing comes to my mind which could be the reason for the "long" method". I have done a Titanium Backup restore first. So i guess there was data left on device under /data/data.
Only a guess but i think it a good one :D

mark

  • 4 Posts
  • 0 Likes
works great, thankyou very much, now lets see if THEY can sort the other issues out!!!!!!!!!

xdalaw

  • 6 Posts
  • 1 Like
Here's the response to my support ticket.. Note the .cfg file must also be deleted/renamed:

"Discussion Thread
---------------------------------------------------------------
Response (Brandt) - 05/07/2011 02.13 PM
Dear Andrew,

Thank you for contacting CoPilot Technical Support. Please follow the instructions below for your version of Copilot....

COPILOT LIVE PREMIUM:
- Uninstall CoPilot
- Connect your device to your computer via USB and mount the SD card
- Browse the \SD Card\com.alk.copilot.namarket.premiumusa
- Delete the "save" folder and the "user.cfg" file
- Reinstall CoPilot from the Android Market

COPILOT LIVE STANDARD:
- Uninstall CoPilot
- Connect your device to your computer via USB and mount the SD card
- Browse the \SD Card\com.alk.copilot.namarket.standardusa
- Delete the "save" folder and the "user.cfg" file
- Reinstall CoPilot from the Android Market

Regards,

CoPilot Technical Support"

Still a pain, but at least we know what ALK says to do for reinstalls.

Still wondering about traffic subscriptions being transferred from ROM to ROM.

billpier314

  • 20 Posts
  • 0 Likes
except it doesn't work :-( Really how can this work ? they must have my email tied to the activation and that ROM info stored on their servers?

f1she4rs

  • 16 Posts
  • 5 Likes
Yeah, don't delete the user.cfg - there's no data in there related to registration.

Alberto Stoian

  • 2 Posts
  • 0 Likes
alberto