Короче, накатил я снова 2.1, отредактировав немного сктрипт, но так ничего хорошего не получилось. Вечером прошился, просипаюсь глядь на тело, а оно мертвое. Видать эти манипуляции так его грузят, что батарея с 60% разрядилась полностью за ночь. Разберитесь, кто нибудь, а то я полный чайник
A story on how to build an unofficial webOS 2.1.0 Doctor for PixiPlus on Verizon, AT&T, and WR (ROW)/Pixi on Sprint!! I have a Verizon PixiPlus that I use for a MP3 player, great device, it is not connected to Verizon at this time. There is a method to install webOS 2.1.0 on the device, but it is WR (ROW) and configuring it is not easy… Based on the following links: webOS 2.1 on Pixi effort, Official Thread and This is it. webOS 2.1 on *your* Pixi Plus GSM | The NuttyBunny Well I designed two scripts, one that when used with the backup source of webOS 2.1.0 will turn it into a Verizon webOS 2.1.0 doctor, which one can use to build the device to webOS 2.1.0, I have been using it for a while, but it was not polished… By polished, I mean the dialog boxes do not fit the screen the correct way, things do not handle themselves as good as they could. Now will this process speed up the PixiPlus, NO, it is a 600MHz CPU, and for that it, it is slow, but once polished, it does seem to be more graceful in its presentation. Will this be faster then the stock webOS 2.1.0 on the PixiPlus, Yes, I seem to notice it being less laggy and at least now it looks much better, but come on this is a PixiPlus. webOS Patches (the device will report webOS 2.1.0, but the only patch I had to get from webOS 2.1.2 was the UberCalendar), the backup application works and will restore if device wiped. With this doctor the device will report webOS 2.1.0 to Palm, webOS Quick Install incorrectly reports it, but preware knows it is an Arm6 device and works well.
The second script will take the Veer webOS 2.1.2 framework, javascripts, and updated apps, webOS 2.2.4 enyo, updated App Catalog (yes you will have full access to webOS app catalog, but even though you will be at webOS 2.1.0 the app catalog is smart enough to know that the device is a PIXI/PIXIPLUS and will present only apps allowed for that platform), Bing Maps, and QuickOffice and Veer maps to GoogleMaps, and include the MotionApps Classic Bits, this will bring one to a better polished webOS 2.1.0 design. What HP/Palm should have done for all devices! The details and steps I took to make this happen. First, I use a MAC for webOS script development; the MAC like Windows came standard with a case-insensitive disk subsystem. So using Disk Utility I had to create a 10G disk (DMG) that is formatted case sensitive. Once I did that it automounted, I used terminal to git the meta doctor, and I copied the doctors that are needed for the first script (the script will pull them down if not there), but it will want the webOS 2.1.0 files (I will not post the files or where to get them google is ones friend here). Running the first script: Now once the script runs the first time it unpacks the Verizon PixiPlus 1.4.5.1 doctor, then stops informing that the directory “Not prepared for webOS 2.1.0 build extract” and “Please create 210 directory under …” and it gives you the directory where the directory “210” should be created… Use terminal to mkdir –p doctor/210 Re-run the script now it complains “Not prepared for webOS 2.1.0 build extract” and “webOS 2.1.0 rootfs file not present”. Now copy the PIXI webOS 2.1.0 rootfs file (a long hex file name tar that is gziped), the updated boot tar (rhymes with pixi and starts with the letter 'f') to the 210 directory, and your boot logo your wish to user under scripts/bootlogo.tga (I used the HP logo). Re-run the script, now it will ungzip both webOS 2.1.0 files just copied and it will then copy the main rootfs file and then transform it… When that script is done, a Verizon webOS 2.1.0 doctor is created and moved to the “downloads” directory and unpacked. If you used the first script’s JAR file and run it, it will be a webOS 2.1.0 stock (but again not polished, this is according to the MD5SUMS the closest I can come to a stock webOS 2.1.0 doctor) Now we are ready to run the second script the polishing…
The second script grabs the doctor (from downloads, if not unpacked, unpacks it) and removes the stock PixiPlus older webOS files, and then injects the updated webOS 2.1.2/2.2.4 files in their place. Now it starts the JAR to Doctor the Device. The first thing you will notice, is that the doctor will behave like a webOS 1.4.5.1 doctor because that is where I start, but it will layout the disk (corrected for the PixiPlus, swap is brought back to 196M where it should be) to webOS 2.1.0 standard, I have not tested going from webOS 1.4.5.1 doctor to webOS 2.1.0 doctor or backwards. But it should work fine YMMV…
Next thing I am going to work on is port the webOS 2.2.4 Veer framework components to the Pixi (at least try due to a change in the webkit version)…
Scripts are attached, as I am not going to distribute the webOS 2.1.0 source (backup files), the doctor created from both of these scripts, but I am starting a new thread in order to assist others in building a doctor.
FYI there is still issues with the depends on the VZNavigator so it does not install but can be installed via ipkg install -nodeps, and the amazon service also does not get installed (not sure if it is needed) but I install it after anyway via the command line.
As my device is not on Verizon Wireless network, I can not say if it (VZNavigator) works or not.
Make sure you have backed up all USB and APP data you wish to keep, not sure how it handles going from webOS 1.4.x to webOS 2.1.0 (assume it will wipe all, but it might preserve it), as I went from webOS 1.4.5.1 to webOS 2.1.0 but with a blank (no data, no apps, no palm profile) PIXIPLUS.
Последний раз редактировалось Alexey2332 31 мар 2012, 23:02, всего редактировалось 1 раз.