webOS Nation Forums >  Homebrew >  WebOS Internals > WebOS Internals Meta-Doctor
WebOS Internals Meta-Doctor
  Reply
Like Tree4Likes

 
Thread Tools Display Modes
Old 09/26/2012, 06:19 PM   #701 (permalink)
Developer
 
rwhitby's Avatar
 
Posts: 10,568
Quote:
Originally Posted by mtiberio View Post
I have both a pre+ and a pre2, and don't mind experimenting, but is there an easy way (without actually doctoring) for me to find out what the differences are between the following builds? What is the difference between a meta and test script or a super and a test script? Is one prefered? Is one more feature rich? Is one more stripped down?

test-verizon-preplus-2.1.0 and meta-verizon-preplus-2.1.0
test-verizon-preplus-2.2.4 and super-verizon-preplus-2.2.4
test-verizon-pre2-2.2.4 and super-verizon-pre2-2.2.4


Thanks,
Mike
Easiest way is just to read the scripts. "Test" and "Super" seem to be obvious names for the corresponding functionality.

-- Rod
__________________
WebOS Internals and Preware Founder and Developer
You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
All donations go back into development.
www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
rwhitby is offline   Reply With Quote
Old 09/26/2012, 10:34 PM   #702 (permalink)
Member
 
Posts: 1,609
Quote:
Originally Posted by mtiberio View Post
I have both a pre+ and a pre2, and don’t mind experimenting, but is there an easy way (without actually doctoring) for me to find out what the differences are between the following builds? What is the difference between a meta and test script or a super and a test script? Is one preferred? Is one more feature rich? Is one more stripped down?

test-verizon-preplus-2.1.0 and meta-verizon-preplus-2.1.0
test-verizon-preplus-2.2.4 and super-verizon-preplus-2.2.4
test-verizon-pre2-2.2.4 and super-verizon-pre2-2.2.4


Thanks,
Mike
Quote:
Originally Posted by rwhitby View Post
Easiest way is just to read the scripts. "Test" and "Super" seem to be obvious names for the corresponding functionality.

-- Rod
The scripts I wrote test/super are my attempt to make a doctor as clean as possible with the right functionality, test-verizon-preplus-2.1.0, is my attempt to make as close to a Verizon PrePlus 2.1.0 as possible, but updating a few modules to get the best out of both worlds, give one MAP with the Touchpad (webos 2.2.4 BlueTooth Stack), Updated Flash.Enyo,Calender/contacts sync for Google/Yahoo (from webOS 2.2.4), Motionapps Classic Support (from webOS 1.4.5.1/2.0.1), Default Maps swapped to Mobile Google Maps, Updated Carrier Apps from Veer webOS 2.1.2 (Palm Voice Command), Pre2 webOS 2.1.0 (Skype Mobile, VZNavigator, Verizon Carrier Configuration, Amazon MP3 Store). Whereas the meta-verizon-preplus-2.1.0, is the WR 2.1.0 with Verizon Pre2 carrier apps. It is up to the user as to which they wish to choose.

The webOS 2.2.4 scripts, the test-verizon-preplus-2.2.4/test-verizon-pre2-2.2.4, is a vanilla script which was to test the functionality of webOS 2.2.4 on the PrePlus/Pre2 (close to a stock released doctor), the super-verizon-preplus-2.2.4/super-verizon-pre2-2.2.4 was to update the functionality, updated Motionapps Classic Support (from webOS 1.4.5.1/2.0.1), Updated carrier apps from Pre3 webOS 2.2.4, Default Maps swapped to Mobile Google Maps, webOS 2.1.0 YouTube app, although one can also add the Bookmark webOS 2.2.4 YouTube app.

I hope that helps.... Also there are threads for the Verizon PrePlus and Pre2 scripts if you need further information

WebOS 2.2.4 on Palm Pre+ or Pre...

2.2.4 for the VZW Pre 2?
John Steffes is offline   Reply With Quote
Liked by mtiberio likes this.
Thanked By: mtiberio
Old 09/27/2012, 09:19 AM   #703 (permalink)
Member
 
mtiberio's Avatar
 
Posts: 306
Thanks for the input. I just spent some time looking at both 2.1.0 scripts in side by side vi's (since diff jackpots) and it looked like test had skype added, at least from the IPKS defines, but otherwise they were similar. Obviously I missed a bunch. I now see the block of $make's where you unpack all the sources for the goodies in the test script. Thanks for the lesson...
mtiberio is offline   Reply With Quote
Old 01/05/2013, 11:29 AM   #704 (permalink)
Member
 
Posts: 26
I had started my own thread, but I suppose this might be a more appropriate place to ask my question.

I was gifted a strange Pre. It started life as a Verizon Pre Plus. The previous owner turned it into a FrankenPre using his Sprint comms board. He then got a Rogers Pre 2, and did another comms board swap - the Sprint board into the 2, the Rogers board into the Plus.

So, I have a Verizon Pre Plus, that thinks it's a Sprint phone, but has a Rogers GSM comms board in it.

I'd like to get it up and running as a spare phone. I have an unlocked Pre 2 as a daily driver, and I'd like to have the Plus ready to accept my SIM should anything happen to the 2. I've tried a few (meta-) Doctors, but I keep getting token mismatch errors. How do I work around that? I know that tokens can be baked into a Doctor, but is it possible to get the proper tokens now?

Thanks for any help.
__________________
Primary phone: Unlocked Pre 2 on Straight Talk
Old phone: Sprint Pre (twice replaced, thrice repaired)
Parts phone: eBay Sprint Pre (scratched, bad ESN)
Potential spare phone: Verizon Pre Plus, formerly with Sprint Pre board, now with Rogers Pre 2 board
jeffro-tull is offline   Reply With Quote
Old 10/05/2013, 07:48 AM   #705 (permalink)
Member
 
Tyh2o's Avatar
 
Posts: 40
Does anyone have a meta doctor made for an unlocked at&t pre 3 running 2.24 with the option to set up over WiFi?
Tyh2o is offline   Reply With Quote
Old 10/05/2013, 12:50 PM   #706 (permalink)
pivotCE Developer
 
Alan Morford's Avatar
 
Posts: 1,248
Quote:
Originally Posted by Tyh2o View Post
Does anyone have a meta doctor made for an unlocked at&t pre 3 running 2.24 with the option to set up over WiFi?
That already exists for distribution http://downloads.help.palm.com/webos...24mantaatt.jar. I'm under the impression that once a device is unlocked it remains unlocked regardless of a fresh doctor. Someone correct me if I'm wrong. That link is for an AT&T Pre 3 for 2.2.4. To set up over wifi simply hit the emergency call button on the setup screen and type ##DEVMODE#, set developer mode to on, the device will reboot, and then you can enable wifi and use impostah to login to your palm profile. Otherwise, visit Application:MetaDoctor - WebOS Internals to learn about what options you have. Good luck.
__________________
Follow me on Twitter
For the latest webOS news check out pivotCE
Alan Morford is offline   Reply With Quote
Old 02/26/2015, 07:59 AM   #707 (permalink)
Homebrew Developer
 
davodego's Avatar
 
Posts: 90
I did a big misstake.
I have a att veer in germany. I thought I can run the webosdoctor for EU to make the SIMLock go away. It does not work. So I catch the unlock code but the Veer with EU webOS don't accept the code. I think i have to give the code in Original AT&T webOS. I can't go back, because the webosdoctor refused to run on the wrong model 160ueu and 160una.

INFO: WARING: carrierList on the webOS Dr is : att and carrierToken on the device is : row


I have tried some configs in Meta Doctor but I have no succes to run the doctor.

Can please anybody help me. How can i use the metadoctor to reverse the meta-veer-unpersonate-wr-2.2.1 script.
The veer will be lost if not.
__________________
-----------------------------------------------------------------------------
Daniel from Kranichfeld, Thüringen, Germay, Old Europe
davodego is offline   Reply With Quote
Old 02/27/2015, 08:12 PM   #708 (permalink)
Member
 
Posts: 396
Hmm, well, I'm not the expert at this (there are people better than me at it by far). However, If you want to try it, I attempted to make a meta-doctor script do impersonate att from wr which you may be able to use to get back to the original att afterward. I'm not able to test this, and If you run it and it completely borks your veer, please don't blame me. I won't blame you if you never use this script, as you are assuming risk there. Again, if you are really worried about the health of your veer, do NOT use this script. If you figure you got nothing to lose then maybe you wanna try it and let me know how it went.
I had to add the stupid .txt extension to allow me to upload it. If it freaks out, just remove the .txt

Good luck
Attached Files
File Type: txt meta-wr-veer-impersonate-att-2.1.1.txt (2.8 KB, 0 views) Email Attachment
creepingmee is offline   Reply With Quote
Old 02/28/2015, 12:18 AM   #709 (permalink)
Homebrew Developer
 
davodego's Avatar
 
Posts: 90
Quote:
Hmm, well, I'm not the expert at this (there are people better than me at it by far). However, If you want to try it, I attempted to make a meta-doctor script do impersonate att from wr which you may be able to use to get back to the original att afterward. I'm not able to test this, and If you run it and it completely borks your veer, please don't blame me. I won't blame you if you never use this script, as you are assuming risk there. Again, if you are really worried about the health of your veer, do NOT use this script. If you figure you got nothing to lose then maybe you wanna try it and let me know how it went.
I had to add the stupid .txt extension to allow me to upload it. If it freaks out, just remove the .txt

Good luck
Thanks for your offer. I've done it this way. I changed the settings from att, wr, row and webosdoctor jar i opponent. There were many tries bevore i reached the correct setting. Im not sure in detail if it was the right reverse way. Because the original att webosdoctor refused to run. The device was set to row after running my reverse Script. But it worked, and with this i have executed the wr webosdoctor. It wastes much time.

Would anybody take a look at the script for? Maybe for uploading in the metadoctor git?


-- Sent from my TouchPad using Communities
__________________
-----------------------------------------------------------------------------
Daniel from Kranichfeld, Thüringen, Germay, Old Europe
davodego is offline   Reply With Quote
Old 03/12/2015, 07:09 PM   #710 (permalink)
Member
 
Posts: 90
I came to a strange conclusion, so I'm documenting it here as I didn't seen it written anywhere.
The documentation of meta-doctor says that setting CHANGE_KEYBOARD_TYPE to 'y' or 'y1' produces the same result (QWERTZ keyboard). But in reality it produces slightly different results. Namely the alternate character list is different with the two settings.
The 'y1' produces the alternate characters corresponding to the standard german (RAW) layout ('-' on the P key), while 'y' produces a strange german layout where the main keys correspond to the german layout but the alternate characters to the english one (= on the P key).
tylla is offline   Reply With Quote
Old 03/16/2015, 06:28 AM   #711 (permalink)
Member
 
Posts: 82
Good to know.
gsfx is offline   Reply With Quote
Old 03/17/2015, 05:21 PM   #712 (permalink)
Member
 
mhous33's Avatar
 
Posts: 98
I just picked up a Pre 3 recently after being away from webOS since my Pixi+ died a few years ago.
I picked up an at&t version that i successfully unlocked (thanks to Dogbert!) and used meta-doctor to make a vanilla doctor.
After successfully building with the original script, I modified it to use the 2.2.4 wr doctor in place of the 2.2.0 wr doctor, and everything seems to be working well.

TL;DR
Is there any reason why the original at&t pre 3 vanilla script used 2.2.0 instead of 2.2.4, or is it just because the 2.2.4 image wasn't available at the time?
mhous33 is offline   Reply With Quote
Reply

 

Thread Tools
Display Modes



 


Content Relevant URLs by vBSEO 3.6.0