http://wiki.webos-internals.org/api.php?action=feedcontributions&feedformat=atom&user=Egaudet 2026-04-21T08:56:50Z User contributions MediaWiki 1.35.1 http://wiki.webos-internals.org/index.php?title=Application:FreeTether&diff=12507 2011-01-05T05:56:45Z

<p>Egaudet: </p> <hr /> <div>{{application<br /> |name=freeTether<br /> |type=webOS<br /> |version=Version: 0.99.6<br /> |tag=Networking<br /> |screenshot=FreeTether_ss1.png<br /> |description=}}<br /> <br /> {{icon|Icon_FreeTether.png|float:right;}}<br /> <br /> Works with all current devices running webOS version 1.4.5 or later:<br /> <br /> 1. Add the test feeds to preware (see [[Testing Feeds]])<br /> <br /> 2. Load preware, refresh feeds, and install freeTether<br /> <br /> 3. Enjoy Free Tethering</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Pre%27s_flash_disk&diff=12277 2010-12-08T03:55:02Z

<p>Egaudet: </p> <hr /> <div>The Pre's flash disk appears to the device as a MMC and uses the standard fdisk partition scheme, with a MBR-like structure in the first block. There are three partitions:<br /> <br /> # type 0xf0 start 0x00000400 size 0x00002000 [[NVRAM]] and [[Tokens]]<br /> # type 0x83 start 0x00002400 size 0x00010000 /boot (ext3)<br /> # type 0x8e start 0x00012400 size 0x00f3dc00 Logical Volumes<br /> <br /> The space between the MBR and the first partition are used to store the bootloader ([[Bootie]]). The /boot partition contains the linux kernel (in uImage format), a copy of the bootloader and the minimal userland required to start the LVM and to pivot the root to /dev/mapper/store-root and perform the &quot;real&quot; boot from there.<br /> <br /> == webos 1.4.5 Pre ==<br /> The first 512K contains the MBR and Bootie.<br /> <br /> The Flash is set up as follows:<br /> <br /> * MBR - 512 Bytes<br /> * Bootie Size - 4 Bytes<br /> * Load Address - 4 Bytes<br /> * Bootie - ~54K for Pre, ~105K for Pixi<br /> * ??? - Rest of 512K space before first partition<br /> * partition 1 (NVRM) - 4M<br /> * partition 2 (/boot) - 32M<br /> * partition 3 (LVM) - rest of Flash<br /> <br /> <br /> Partitions:<br /> # type 0xf0 start 0x00080000 size 0x00400000 [[NVRAM] and [[Tokens]]<br /> # type 0x83 start 0x00480000 size 0x02000000 /boot (ext3)<br /> # type 0x8e start 0x02480000 size 0x1e7b8000 Logical Volumes</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Application:SuperTux&diff=11274 2010-09-11T04:18:31Z

<p>Egaudet: </p> <hr /> <div>{{application<br /> |name=SuperTux<br /> |version=1.0.2<br /> |type=webOS<br /> |tag=Games<br /> |screenshot=Supertux_Screenshot_1.png<br /> |description=Classic 2D jump'n run sidescroller game in a style similar to the original Super Mario games. GPL<br /> }}<br /> <br /> [[Image:Supertux_icon.png]]<br /> <br /> == '''Credit''' ==<br /> Ported and Packaged by Eric J Gaudet Jan 2010<br /> <br /> == '''Controls''' ==<br /> '''Screen controls''' &lt;br&gt;<br /> Tilt for joystick directions &lt;br&gt;<br /> Tilt up towards you to duck &lt;br&gt;<br /> Tap gesture area to jump &lt;br&gt;<br /> Tap and hold gesture area to high jump &lt;br&gt;<br /> Tap screen to throw fireball &lt;br&gt;<br /> Swipe down for Menu. (Note that Tux will jump before menu loads) &lt;br&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Auto-Update_Patch_Technology&diff=11147 2010-09-01T23:52:54Z

<p>Egaudet: </p> <hr /> <div>Here we can discuss the future of AUPT and where we should go from here. Here are some ideas I've been thinking about for the next generation of AUPT as a C service using AUFS overlay.<br /> <br /> == Directory Structure ==<br /> /media/internal/.patches<br /> <br /> * patch.db - patch state database file (doesn't -have- to be database?)<br /> * webos-$version/ - version specific overlay<br /> * webos-$version/&lt;package&gt;/ - palm package<br /> * webos-$version/&lt;package&gt;/path/to/files - patched files<br /> * stock/path/to/files - Stock backup files<br /> * work-area/path/to/files - A place to do the actual patching/testing, before copying files to in-use overlay. This will make sure there are fewer chances to have partial-patch installations and other odd issues that may arise. (Is this needed or overkill?)<br /> <br /> Each &lt;package&gt; would be an aufs branch. Or maybe the C-service/statefile would keep track of the hunk -&gt; file -&gt; package connection. Today I've been pondering using the source code for GNU patch in the C service. <br /> <br /> == NO overlay branches ==<br /> These are branches that will need to not be modified by any custom overlay<br /> * /boot<br /> * /dev<br /> * /proc<br /> * /sys<br /> * /usr/lib/ipkg<br /> * /media/internal<br /> * /lib<br /> * /bin<br /> * /sbin<br /> * /mnt<br /> <br /> (Should we just use /usr and /etc as allowable patch branches?)<br /> <br /> == Statefile ==<br /> A database state file with patch information may be needed. <br /> Possible things to store are the following:<br /> * What palm packages and files each patch touches<br /> * What order the patches were applied in. It may have to be on a per file basis.<br /> * rw aupt branches (see directory structure) - cryptk brings up good point to make the aupt branches ro as well<br /> * ro stock branches (see No overlay branches) marking the overlays as 'dirty' and re-starting the service may be needed for updates to patching service. Possibly provide a way for faulty patches preventing Luna from starting to be detected.<br /> * current webos version<br /> <br /> == Upstart ==<br /> Upon booting, the upstart service needs to be started as early as possible to get the aufs overlay over before things like Luna start reading files. The starting of the patch service should do at a bare minimum some sanity checks before mounting the overlay. Some sort of flag for not booting cleanly the last time should be detected if possible.<br /> <br /> == OTA ==<br /> Using &quot;stop on started start_update&quot; we can rip out the overlay during a Palm OTA update. On the next boot the webos version will be different and the patch service -could- attempt to re-patch as many 'patches' as possible. Since all the patch packages will change to new feed and require update all via preware anyway, we can just leave this to the user to hit update all instead (as it is now), and then all the patches will be installed to the new webos-version overlay.<br /> <br /> == Other random things to think about ==<br /> * what to do with files that are written outside of aupt that will appear in aufs branches?<br /> * Possibly track the version of the palm package that a patch is applied to, rather than assuming webos version means correct package version. Would also allow forward compatibility if Palm ever started allowing package updates without webos version changes. <br /> * Would it be useful to use combinediff on a pacakge (or file) basis?<br /> <br /> === --[[User:Egaudet|Egaudet]] 22:25, 25 August 2010 (UTC) ===<br /> <br /> === Continued discussion ===<br /> <br /> *cryptk: &quot;there could be a file that stores the currently selected patch profile, that way the correct aufs overlay is used, after aufs is loaded that file is cleared to be re-written when the upstart service is closed cleanly. then it would double as our bad boot flag&quot;<br /> *multiple webos-version patches in single ipk vs. multiple webos-version feeds</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Icons&diff=11091 2010-08-30T03:36:37Z

<p>Egaudet: </p> <hr /> <div>== This is a Thinking Page at the Moment ==<br /> <br /> Bringing the webOS-Internals ecosystem together through their icons. This is an ''optional'' suggestion being posed to those maintaining a org.webosinternals.* project. The &quot;ice&quot; platform will be the visual indication that an application or service is being maintained by a webOS-Internals member and is OSS.<br /> <br /> If you would like an icon created for an application add it to the list at the bottom of this page. Icon designs will go through a few phases of critiques before they will be finalized. During this process users will be able to see the changes on this page.<br /> <br /> == webOS-Internals Icons (more will be added shortly) ==<br /> <br /> {{icon|Icon_WebOSInternals_Base.png}}<br /> {{icon|Icon_WebOSInternals_Base_Plugin.png}}<br /> {{icon|Icon_WebOSInternals_Base_Service.png}}<br /> {{icon|Icon_WebOSInternals_Base_Patch.png}}<br /> {{icon|Icon_WebOSInternals_Base_Optware.png}}<br /> {{icon|Icon_WebOSInternals_WebOSInternals.png}}<br /> {{icon|Icon_WebOSInternals_Box.png}}<br /> {{icon|Icon_WebOSInternals_Box_Empty.png}}<br /> {{icon|Icon_WebOSInternals_Box_Tux.png}}<br /> {{icon|Icon_WebOSInternals_Terminal.png}}<br /> {{icon|Icon_WebOSInternals_TerminalService.png}}<br /> {{icon|Icon_WebOSInternals_Keyboard.png}}<br /> {{icon|Icon_WebOSInternals_Preware.png}}<br /> {{icon|Icon_WebOSInternals_PackageManager.png}}<br /> {{icon|Icon_WebOSInternals_AccelerometerService.png}}<br /> {{icon|Icon_Service_LED.png}}<br /> {{icon|Icon_WebOSInternals_Battery.png}}<br /> {{icon|Icon_WebOSInternals_BatteryService.png}}<br /> {{icon|Icon_WebOSInternals_StopLight.png}}<br /> {{icon|Icon_WebOSInternals_ProcessMonitor.png}}<br /> {{icon|Icon_WebOSInternals_ProcessService.png}}<br /> {{icon|Icon_WebOSInternals_Upstart.png}}<br /> {{icon|Icon_WebOSInternals_UpstartService.png}}<br /> {{icon|Icon_WebOSInternals_DropBear.png}}<br /> {{icon|Icon_WebOSInternals_OpenSSH.png}}<br /> {{icon|Icon_WebOSInternals_Nano.png}}<br /> {{icon|Icon_WebOSInternals_Password.png}}<br /> {{icon|Icon_WebOSInternals_OpenSSL.png}}<br /> {{icon|Icon_WebOSInternals_ZLib.png}}<br /> {{icon|Icon_WebOSInternals_GNUReadlineLib.png}}<br /> {{icon|Icon_WebOSInternals_GnuPatchBinary.png}}<br /> {{icon|Icon_WebOSInternals_wIRC.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_Service.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_Alert.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_PM.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_Invite.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_Invite2.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_Upload.png}}<br /> {{icon|Icon_WebOSInternals_wIRC_DCC.png}}<br /> {{icon|Icon_WebOSInternals_Camera.png}}<br /> {{icon|Icon_WebOSInternals_PrecorderNew.png}}<br /> {{icon|Icon_WebOSInternals_CameraWIP.png}}<br /> {{icon|Icon_Patch_Dangerous.png}}<br /> {{icon|Icon_Patch_Deadly.png}}<br /> {{icon|Icon_FreeTether.png}}<br /> {{icon|Icon_MvApp.png}}<br /> {{icon|Icon_Worm.png}}<br /> {{icon|Icon_Tetris.png}}<br /> {{icon|Icon_Asteroids.png}}<br /> {{icon|Icon_SpaceInvaders.png}}<br /> {{icon|Icon_PDK.png}}<br /> {{icon|Icon_lighttpd.png}}<br /> {{icon|Icon_OpenVPN.png}}<br /> {{icon|Icon_Terminus.png}}<br /> {{icon|Icon_WebOSInternals_SaveRestore.png}}<br /> {{icon|Icon_WebOSInternals_Kernel.png}}<br /> {{icon|Icon_WebOSInternals_Kernel_mem.png}}<br /> {{icon|Icon_WebOSInternals_Govnah.png}}<br /> {{icon|Icon_WebOSInternals_Saver.png}}<br /> {{icon|Govenericon.png}}<br /> {{icon|Icon_NGiNX.png}}<br /> {{icon|Icon_WebOSInternals_Lumberjack.png}}<br /> {{icon|Icon_WebOSInternals_KeyBoss.png}}<br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Patch Icons ==<br /> <br /> {{icon|Icon_WebOSInternals_Patch.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Actualpercent.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Amazonstore.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Applauncher.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Batteryandpercent.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Browser.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Calculator.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Calendar.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Camera.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Clock.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Contacts.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Devmodelauncher.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Email.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Findapps.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Luna.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Messaging.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Musicplayer.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Nascar.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Nfl.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Pandora.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Pdfviewer.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Percent.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Phone.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Phonepreferences.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Photos.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Screenlock.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Smile.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Soundsandalerts.png}}<br /> {{icon|Icon_WebOSInternals_Patches_SprintNav.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Sprinttv.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Tasks.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Videoplayer.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Wifi.png}}<br /> {{icon|Icon_WebOSInternals_Patches_Youtube.png}}<br /> <br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Other Icons ==<br /> <br /> {{icon|Icon_Box.png}}<br /> {{icon|Icon_Box_Arrow.png}}<br /> {{icon|Icon_Box_Cog.png}}<br /> {{icon|Icon_Preware.png}}<br /> <br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Alternatives ==<br /> <br /> {{icon|Icon_PrewareAlt.png}}<br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Icons For other Applications (for reference only) ==<br /> <br /> {{icon|Icon_Reversi.png}}<br /> {{icon|Icon_Airplane.png}}<br /> {{icon|Icon_TheFingWeather.png}}<br /> {{icon|Icon_Chat.png}}<br /> {{icon|Icon_Chat_Small.png}}<br /> {{icon|Icon_Chat_Individual.png}}<br /> {{icon|Icon_Chat_Group.png}}<br /> {{icon|Icon_Chat_Three.png}}<br /> {{icon|Icon_Chat_Report.png}}<br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Icons For other Services (for reference only) ==<br /> <br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == Small Icons ==<br /> <br /> {{icon|Icon_WebOSInternals_Plugin_Small.png}}<br /> {{icon|Icon_WebOSInternals_Installed_Small.png}}<br /> {{icon|Icon_WebOSInternals_Updates_Small.png}}<br /> {{icon|Icon_WebOSInternals_Service_Small.png}}<br /> {{icon|Icon_WebOSInternals_Patch_Small.png}}<br /> {{icon|Icon_WebOSInternals_Tools_Small.png}}<br /> {{icon|Icon_WebOSInternals_Optware_Small.png}}<br /> &lt;div style=&quot;clear:both;&quot;&gt;&lt;/div&gt;<br /> <br /> == WebOS-Internals - Services and Applications that still need icons ==<br /> <br /> * GNU Patch Binary<br /> <br /> * JSTop<br /> <br /> * Upstart Manager<br /> <br /> == Just Talk Below ==<br /> <br /> Should this page and [http://www.webos-internals.org/wiki/Mojo_Design_Icons this page] be merged in some way?</div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:Icon_WebOSInternals_KeyBoss.png&diff=11090 2010-08-30T03:36:08Z

<p>Egaudet: </p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=WhoIsWho&diff=11067 2010-08-29T01:31:27Z

<p>Egaudet: </p> <hr /> <div>This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.<br /> <br /> {{AboutMe|alias=rwhitby|realname=Rod Whitby|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}<br /> <br /> {{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BOFH)|aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}<br /> <br /> {{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}<br /> <br /> {{AboutMe|alias=destinal|realname=|responsibility=|aboutme=}}<br /> <br /> {{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate|aboutme=Research assistant / cognitive science grad student by day; webos developer by night }}<br /> <br /> {{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and randomness|aboutme=Busy debugging}}<br /> <br /> {{AboutMe|alias=oil|realname=Brandon VanBelle|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}<br /> <br /> {{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}<br /> <br /> {{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}<br /> <br /> {{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}<br /> <br /> {{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}<br /> <br /> {{AboutMe|alias=swisstomcat|realname=Markus Leutwyler|responsibility=Chief German Translator (ja, genau!) and Javascript Parts Donator to different Projects. Also European Propaganda Minister. |aboutme=Web and Mobile Developer}}<br /> <br /> {{AboutMe|alias=jhojho|realname=|responsibility=Warthog kernel developer|aboutme=}}<br /> <br /> {{AboutMe|alias=cryptk|realname=Chris Jowett|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}<br /> <br /> {{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating nice patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}</div>

Egaudet http://wiki.webos-internals.org/index.php?title=WhoIsWho&diff=11066 2010-08-29T01:24:25Z

<p>Egaudet: </p> <hr /> <div>This page lists all the WebOS Internals developers, and the projects and activities for which each is responsible. Names are listed in chronological order of officially joining the WebOS Internals team.<br /> <br /> {{AboutMe|alias=rwhitby|realname=Rod Whitby|responsibility=Founder and Project Lead for WebOS Internals and Preware |aboutme=Homebrew Ecosystem Architect. Lead developer for Save/Restore. Co-Lead developer for Preware, Govnah and UberKernel. Co-developer for a number of other packages. Oh, and a family and full-time day job too.}}<br /> <br /> {{AboutMe|alias=ka6sox|realname=Tom King|responsibility=Chief Server Infrastructure Architect and Sys-Admin Team Lead(aka BOFH)|aboutme=FT:High Power RF, VHDL/Verilog Design, Play Time: Dabble with Kernel development.}}<br /> <br /> {{AboutMe|alias=rboatright|realname=Rick Boatright|responsibility=Chief Evangelist|aboutme=}}<br /> <br /> {{AboutMe|alias=destinal|realname=|responsibility=|aboutme=}}<br /> <br /> {{AboutMe|alias=PuffTheMagic|realname=Ryan Hope|responsibility=Play devil's advocate|aboutme=Research assistant / cognitive science grad student by day; webos developer by night }}<br /> <br /> {{AboutMe|alias=egaudet|realname=Eric Gaudet|responsibility=AUPT architect and dibble dabbler|aboutme=Busy debugging}}<br /> <br /> {{AboutMe|alias=oil|realname=Brandon VanBelle|responsibility=Minister of Awesomeness|aboutme=It's not my fault!}}<br /> <br /> {{AboutMe|alias=dtzWill|realname=Will Dietz|responsibility=Various WebOS Internals games, X11, WIDK management|aboutme=CS grad student who spends entirely too much time on WebOS }}<br /> <br /> {{AboutMe|alias=zsoc|realname=|responsibility=Multimedia subsystem architect|aboutme=}}<br /> <br /> {{AboutMe|alias=uNiXpSyChO|realname=Marco Benton|responsibility=BOFH and Kernel hacker|aboutme=[[Full-time]]; SysAdmin, SAN Admin, Network Admin. [[Part-time]]; System integration and network design consulting. [[Free-time]]; programming - since that's what i used to do full-time 20 years ago. }}<br /> <br /> {{AboutMe|alias=sbromwich|realname=Steve Bromwich|responsibility=Kernel developer|aboutme=Dilettante kernel programmer concentrating mostly on extending battery life.}}<br /> <br /> {{AboutMe|alias=swisstomcat|realname=Markus Leutwyler|responsibility=Chief German Translator (ja, genau!) and Javascript Parts Donator to different Projects. Also European Propaganda Minister. |aboutme=Web and Mobile Developer}}<br /> <br /> {{AboutMe|alias=jhojho|realname=|responsibility=Warthog kernel developer|aboutme=}}<br /> <br /> {{AboutMe|alias=cryptk|realname=Chris Jowett|responsibility=Server administration and management|aboutme=I work as a full time linux systems administratior as my day job and lend that knowledge to keep the WebOS Internals servers running as well as they possibly can.}}<br /> <br /> {{AboutMe|alias=sconix|realname=Janne Julkunen|responsibility=Creating nice patches and developing Mode Switcher|aboutme=Involved with Linux way too much :)}}</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Auto-Update_Patch_Technology&diff=10972 2010-08-25T22:37:02Z

<p>Egaudet: </p> <hr /> <div>Here we can discuss the future of AUPT and where we should go from here. Here are some ideas I've been thinking about for the next generation of AUPT as a C service using AUFS overlay.<br /> <br /> == Directory Structure ==<br /> /media/internal/.patches<br /> <br /> * patch.db - patch state database file (doesn't -have- to be database?)<br /> * webos-$version/ - version specific overlay<br /> * webos-$version/&lt;package&gt;/ - palm package<br /> * webos-$version/&lt;package&gt;/path/to/files - patched files<br /> * stock/path/to/files - Stock backup files<br /> * work-area/path/to/files - A place to do the actual patching/testing, before copying files to in-use overlay. This will make sure there are fewer chances to have partial-patch installations and other odd issues that may arise. (Is this needed or overkill?)<br /> <br /> Each &lt;package&gt; would be an aufs branch. Or maybe the C-service/statefile would keep track of the hunk -&gt; file -&gt; package connection. Today I've been pondering using the source code for GNU patch in the C service. <br /> <br /> == NO overlay branches ==<br /> These are branches that will need to not be modified by any custom overlay<br /> * /boot<br /> * /dev<br /> * /proc<br /> * /sys<br /> * /usr/lib/ipkg<br /> * /media/internal<br /> * /lib<br /> * /bin<br /> * /sbin<br /> * /mnt<br /> <br /> (Should we just use /usr and /etc as allowable patch branches?)<br /> <br /> == Statefile ==<br /> A database state file with patch information may be needed. <br /> Possible things to store are the following:<br /> * What palm packages and files each patch touches<br /> * What order the patches were applied in. It may have to be on a per file basis.<br /> * rw aupt branches (see directory structure) - cryptk brings up good point to make the aupt branches ro as well<br /> * ro stock branches (see No overlay branches) marking the overlays as 'dirty' and re-starting the service may be needed for updates to patching service. Possibly provide a way for faulty patches preventing Luna from starting to be detected.<br /> * current webos version<br /> <br /> == Upstart ==<br /> Upon booting, the upstart service needs to be started as early as possible to get the aufs overlay over before things like Luna start reading files. The starting of the patch service should do at a bare minimum some sanity checks before mounting the overlay. Some sort of flag for not booting cleanly the last time should be detected if possible.<br /> <br /> == OTA ==<br /> Using &quot;stop on started start_update&quot; we can rip out the overlay during a Palm OTA update. On the next boot the webos version will be different and the patch service -could- attempt to re-patch as many 'patches' as possible. Since all the patch packages will change to new feed and require update all via preware anyway, we can just leave this to the user to hit update all instead (as it is now), and then all the patches will be installed to the new webos-version overlay.<br /> <br /> == Other random things to think about ==<br /> * what to do with files that are written outside of aupt that will appear in aufs branches?<br /> * Possibly track the version of the palm package that a patch is applied to, rather than assuming webos version means correct package version. Would also allow forward compatibility if Palm ever started allowing package updates without webos version changes. <br /> * Would it be useful to use combinediff on a pacakge (or file) basis?<br /> <br /> === --[[User:Egaudet|Egaudet]] 22:25, 25 August 2010 (UTC) ===<br /> <br /> === Continued discussion ===<br /> <br /> cryptk: &quot;there could be a file that stores the currently selected patch profile, that way the correct aufs overlay is used, after aufs is loaded that file is cleared to be re-written when the upstart service is closed cleanly. then it would double as our bad boot flag&quot;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Auto-Update_Patch_Technology&diff=10971 2010-08-25T22:25:01Z

<p>Egaudet: New page: Here we can discuss the future of AUPT and where we should go from here. Here are some ideas I've been thinking about for the next generation of AUPT as a C service using AUFS overlay. =...</p> <hr /> <div>Here we can discuss the future of AUPT and where we should go from here. Here are some ideas I've been thinking about for the next generation of AUPT as a C service using AUFS overlay.<br /> <br /> == Directory Structure ==<br /> /media/internal/.patches<br /> <br /> * patch.db - patch state database file (doesn't -have- to be database?)<br /> * webos-$version/ - version specific overlay<br /> * webos-$version/&lt;package&gt;/ - palm package<br /> * webos-$version/&lt;package&gt;/path/to/files - patched files<br /> * stock/path/to/files - Stock backup files<br /> * work-area/path/to/files - A place to do the actual patching/testing, before copying files to in-use overlay. This will make sure there are fewer chances to have partial-patch installations and other odd issues that may arise. (Is this needed or overkill?)<br /> <br /> Each &lt;package&gt; would be an aufs branch. Or maybe the C-service/statefile would keep track of the hunk -&gt; file -&gt; package connection. Today I've been pondering using the source code for GNU patch in the C service. <br /> <br /> == NO overlay branches ==<br /> These are branches that will need to not be modified by any custom overlay<br /> * /boot<br /> * /dev<br /> * /proc<br /> * /sys<br /> * /usr/lib/ipkg<br /> * /media/internal<br /> * /lib<br /> * /bin<br /> * /sbin<br /> * /mnt<br /> <br /> (Should we just use /usr and /etc as allowable patch branches?)<br /> <br /> == Statefile ==<br /> A database state file with patch information may be needed. <br /> Possible things to store are the following:<br /> * What palm packages and files each patch touches<br /> * What order the patches were applied in. It may have to be on a per file basis.<br /> * rw aupt branches (see directory structure) - cryptk brings up good point to make the aupt branches ro as well<br /> * ro stock branches (see No overlay branches) marking the overlays as 'dirty' and re-starting the service may be needed for updates to patching service. Possibly provide a way for faulty patches preventing Luna from starting to be detected.<br /> * current webos version<br /> <br /> == Upstart ==<br /> Upon booting, the upstart service needs to be started as early as possible to get the aufs overlay over before things like Luna start reading files. The starting of the patch service should do at a bare minimum some sanity checks before mounting the overlay. Some sort of flag for not booting cleanly the last time should be detected if possible.<br /> <br /> == OTA ==<br /> Using &quot;stop on started start_update&quot; we can rip out the overlay during a Palm OTA update. On the next boot the webos version will be different and the patch service -could- attempt to re-patch as many 'patches' as possible. Since all the patch packages will change to new feed and require update all via preware anyway, we can just leave this to the user to hit update all instead (as it is now), and then all the patches will be installed to the new webos-version overlay.<br /> <br /> == Other random things to think about ==<br /> * what to do with files that are written outside of aupt that will appear in aufs branches?<br /> * Possibly track the version of the palm package that a patch is applied to, rather than assuming webos version means correct package version. Would also allow forward compatibility if Palm ever started allowing package updates without webos version changes. <br /> * Would it be useful to use combinediff on a pacakge (or file) basis?<br /> <br /> === --[[User:Egaudet|Egaudet]] 22:25, 25 August 2010 (UTC) ===</div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:Keyboss_ss1.png&diff=10929 2010-08-23T03:08:44Z

<p>Egaudet: uploaded a new version of &quot;Image:Keyboss ss1.png&quot;</p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=Application:Lumberjack&diff=10890 2010-08-19T03:43:54Z

<p>Egaudet: </p> <hr /> <div>{{application<br /> |name=Lumberjack<br /> |type=webOS<br /> |version=0.1.1 Beta<br /> |tag=Utilities<br /> |screenshot=Lumberjack_ss1.png<br /> |description=}}<br /> <br /> =Summary=<br /> {{icon|Icon_WebOSInternals_Lumberjack.png|float:right;}}Lumberjack is an on-device logging tool. It allows you to view and follow the logs for specific applications from the /var/log/messages file.<br /> <br /> Its goal is to make debugging apps without a workstation better and easier.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=KeyBoss&diff=10433 2010-07-03T01:51:58Z

<p>Egaudet: New page: {{application |name=KeyBoss |type=webOS |version=Version: 0.1.0 &lt;br /&gt;(2 Jul 2010) |tag=System Utilities |screenshot=Keyboss_ss1.png |description= == Summary == KeyBoss is an Application...</p> <hr /> <div>{{application<br /> |name=KeyBoss<br /> |type=webOS<br /> |version=Version: 0.1.0 &lt;br /&gt;(2 Jul 2010)<br /> |tag=System Utilities<br /> |screenshot=Keyboss_ss1.png<br /> |description=<br /> <br /> == Summary == <br /> KeyBoss is an Application + Service combination to give greater control over the keyboard and keyboard events. It currently allows you to change the repeat rate of the hard keyboard events, emulate keyboard events (used by Virtual Keyboard), and also gives KeyCaps type functionality. When enabled you can either hold a key for capital letter and/or doubletap a key for the key's symbol. <br /> <br /> NOTE: You must install the Uinput Module package for the KeyCaps and emulation (for VKB) functionalities to work.<br /> <br /> == Ideas ==<br /> This is only the first attempt at it, but I hope to add more control and options. For instance KeyCaps control on a key-by-key basis. Also maybe keyboard &quot;profiles&quot; to allow quickly switching between languages for instance. <br /> }}</div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:Keyboss_ss1.png&diff=10432 2010-07-03T01:46:32Z

<p>Egaudet: </p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:Keyboss_2010-30-06_215524.png&diff=10413 2010-07-01T01:57:03Z

<p>Egaudet: </p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:RemixGlossy.png&diff=10363 2010-06-21T03:03:17Z

<p>Egaudet: uploaded a new version of &quot;Image:RemixGlossy.png&quot;</p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:RemixClassic.png&diff=10362 2010-06-21T03:02:31Z

<p>Egaudet: uploaded a new version of &quot;Image:RemixClassic.png&quot;</p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=File:Remix_ice.png&diff=10353 2010-06-18T23:12:15Z

<p>Egaudet: </p> <hr /> <div></div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9077 2010-02-16T06:01:34Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> === Emergency File Verification ===<br /> Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap &quot;Show IPKG log&quot; to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-patches.log file in USB mode for this information. <br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> <br /> === aupt-1 ===<br /> * First implementation<br /> <br /> === aupt-2 === <br /> * Attempt to re-order logic in prerm to check for OTA first before trying to -R the patch <br /> <br /> === aupt-3 ===<br /> * Fixed order of OTA checking to avoid potential rare case of OTA containing changes that allow a patch to -R incorrectly<br /> * Fixed bug in aupt-2 so that patches actually get unapplied<br /> * Renamed backups file to file_list in patch control dir to avoid potential conflicts with Palm backup operations<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9072 2010-02-16T02:07:24Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> === Emergency File Verification ===<br /> Upon installation, this package will run through all known stock md5sums and check against the known safe patch technology version(s). Simply install this package and if you receive an error that means that there is some unknown or outdated file modification or patch installation. If installing via Preware you can tap &quot;Show IPKG log&quot; to see which packages/files are touched by outdated/unknown patching technologies. You can also check the webos-patches.log file in USB mode for this information. <br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> <br /> === aupt-1 ===<br /> * First implementation<br /> <br /> === aupt-2 === <br /> * Re-ordered logic in prerm to check for OTA first before trying to -R the patch <br /> * '''Bug causes all patches to believe they are OTA on removal and thus do not actually unapply the patch'''<br /> <br /> === aupt-3 ===<br /> * Fixed bug in aupt-2 so that patches actually get unapplied<br /> * Renamed backups file to file_list in patch control dir<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9071 2010-02-16T01:14:25Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> <br /> === aupt-1 ===<br /> * First implementation<br /> <br /> === aupt-2 === <br /> * Re-ordered logic in prerm to check for OTA first before trying to -R the patch <br /> * '''Bug causes all patches to believe they are OTA on removal and thus do not actually unapply the patch'''<br /> <br /> === aupt-3 ===<br /> * Fixed bug in aupt-2 so that patches actually get unapplied<br /> * Renamed backups file to file_list in patch control dir<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9070 2010-02-16T01:14:06Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> <br /> === aupt-1 ===<br /> * First implementation<br /> <br /> === aupt-2 === <br /> * Re-ordered logic in prerm to check for OTA first before trying to -R the patch <br /> * '''Bug causes all patches to believe they are OTA on removal and thus do not actually unapply the patch'''<br /> <br /> === aupt-3 ===<br /> * Fixed bug in aupt-2 so that patches actually get unapplied<br /> * Renamed backups file to file_list in patch control dir<br /> <br /> All versions are fully compatible with each other<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9068 2010-02-15T20:38:49Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> * aupt-1: First implementation<br /> * aupt-2: Re-ordered logic in prerm to check for OTA first before trying to -R the patch '''EVIL bug causes all patches to believe they are OTA on removal'''<br /> <br /> All versions are fully compatible with each other<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-2 has a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9067 2010-02-15T20:13:56Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> ==== Preware ====<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> ==== WebOS Quick Install ====<br /> WebOS Quick Install is fully compatible with webOS-Internals Auto-Update Patch Technology (AUPT). When you enter the Tweaks section, after a webOS update, WebOS Quick Install will detect the version change and will open an update helper.<br /> <br /> For on-feed patches , the update helper will update out-of-date patches to the new version's equivalent (or a dummy package if an updated patch has not yet been released).<br /> <br /> For [http://forums.precentral.net/canuck-software/210767-how-install-patch-files-wosqi.html .patch files installed with WebOS Quick Install], the update helper will uninstall them. It will also check to see if the patch can be successfully re-applied. If it can be re-applied, the patch will be reinstalled.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> * aupt-1: First implementation<br /> * aupt-2: Re-ordered logic in prerm to check for OTA first before trying to -R the patch<br /> <br /> All versions are fully compatible with each other<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> * There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> * aupt-1 and aupt-2 have a bug in the removal logic that cause it to see all packages as updated and removes the package without actually unapplying the patch.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9026 2010-02-12T04:48:27Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == AUPT Versions ==<br /> * aupt-1: First implementation<br /> * aupt-2: Re-ordered logic in prerm to check for OTA first before trying to -R the patch<br /> <br /> All versions are fully compatible with each other<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9025 2010-02-12T03:39:08Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> * Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> * Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> * Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9024 2010-02-12T03:28:45Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> * It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> * When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9023 2010-02-12T03:28:21Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> * If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> * If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> * If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> * Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> * webOS Repair Utility<br /> * webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. After an OTA update perform the following steps:<br /> <br /> * Launch Preware<br /> * Tap application menu -&gt; Update Feeds<br /> * Tap Package Updates <br /> * Tap Update All.<br /> <br /> (SEE: Known Issues section for known roadbumps in Preware's Update All function with regards to patches)<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> 1) It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> <br /> 2.) When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9022 2010-02-12T03:25:58Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> 1) If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> 2) If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> 3) If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> 1) Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> 2) webOS Repair Utility<br /> 3) webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap Update All.<br /> <br /> == Submissions ==<br /> Submit all patches to be included into the webos-patches feed found in Preware and webOS Quick Install to: http://patches.webos-internals.org/<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> 1) It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> <br /> 2.) When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9021 2010-02-12T03:25:26Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> 1) If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> 2) If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> 3) If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> 1) Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> 2) webOS Repair Utility<br /> 3) webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap Update All.<br /> <br /> == Submissions ==<br /> Submit all patches to http://patches.webos-internals.org/<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> 1) It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> <br /> 2.) When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9020 2010-02-12T03:23:46Z

<p>Egaudet: </p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new webOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new webOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or webOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === webOS Doctor ===<br /> <br /> The webOS Doctor is a great way to ensure you are running completely stock Palm webOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> 1) If you used a doctor version that is a PRIOR webOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> 2) If you used a doctor version that is the SAME webOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> 3) If you used a doctor version that is a LATER webOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a webOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and webOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm webOS files is by using the webOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> 1) Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> 2) webOS Repair Utility<br /> 3) webOS Doctor<br /> <br /> AUPT patches are built with smart post-install scripts that are able to detect when a patch is already applied to the stock webOS files. If you remember all the patches you had installed before the partial/full erase you may simply re-install each Patch individually as usual (Preware or QI v3.01 or later)<br /> <br /> === OTA Update ===<br /> In the past it was recommended and required to remove all patches prior to updating webOS Over The Air (OTA). The new AUPT system makes this unnecessary and allows you to leave patches installed and then update them all after an OTA update to a new version of webOS. After a webOS OTA update you may use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap Update All.<br /> <br /> == Known Issues ==<br /> === Preware ===<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> 1) It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> <br /> 2.) When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> === Miscellaneous ===<br /> There are rare circumstances where a collection of patches in the same category may have to be installed/removed in a certain order and may fail (safely) to install or remove in different orders.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a webOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a webOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock webOS by performing a full erase followed by a webOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform webOS Doctor to ensure all Palm webOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Auto-Update_Patch_Technology&diff=9019 2010-02-12T03:13:23Z

<p>Egaudet: New page: == Introduction == Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and ...</p> <hr /> <div>== Introduction ==<br /> Auto-Update Patch Technology (AUPT) is the existing patching technology found in all homebrew patches in the webos-patches feed. AUPT is built into the installation and removal scripts of patches and allows patches to be installed/removed even after faulty installs, partial or full erases, webos doctors and even OTA updates to new WebOS versions!<br /> <br /> There is also a concept of placeholder patches in the webos-patches feeds. All patches will at least build a dummy package with version ending in -0. These dummy packages may be installed to serve as a placeholder so that when they are ported to the new WebOS version you will see the Update available in Preware. This will be useful to know when a patch has been ported to the new WebOS version after an OTA update without having to check the forums every so often.<br /> <br /> All patch installations and removals will now log to /media/internal/webos-patches.log and should be examined for detailed information with regards to any patch installation or removal failures.<br /> <br /> == Installation ==<br /> Always install patches with Preware or WebOS Quick Install v3.01 or later. <br /> <br /> == Verification ==<br /> You may wish to verify that all of your installed patches were indeed installed with AUPT built in and that there are no left-over older or incompatible patches installed. In order to do this, you can open the text file .webosinternals.patches.packages found in USB mode from your PC. Each package should contain &quot;aupt-N&quot; indicating the version of aupt built into that patch. Currently aupt-1 is the only version of aupt. If there are ANY lines in that file that contain nothing after the package name that indicates an old incompatible technology was built into that patch. '''Remove these packages immediately and re-install''' (see: Installation section)<br /> <br /> == Re-installation and Upgrades ==<br /> There are various scenarios you may find yourself in where a patch may be installed or uninstalled. We will discuss what to do after each of these situations. <br /> <br /> === WebOS Doctor ===<br /> The WebOS Doctor is a great way to ensure you are running completely stock Palm WebOS files in the root filesystem. There are 3 situations you can be in with patches installed after WebOS Doctor.<br /> <br /> 1) If you used a doctor version that is a PRIOR WebOS version than the one that was running when you installed the Patches, install &quot;Emergency Patch Recovery&quot; (EPR) to wipe the device of the patch package information. There are no supported downgrade automatic patch installations.<br /> <br /> 2) If you used a doctor version that is the SAME WebOS version as the one that was used to install the Patches, simply install &quot;Emergency Service Enabler&quot; (ESE) to re-apply all of your installed patches.<br /> <br /> 3) If you used a doctor version that is a LATER WebOS version than the one that was running when you installed the Patches, use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> === Partial/Full Erase ===<br /> All of your homebrew and App Catalog packages as well as all media data including pictures survive a WebOS Doctor and sometimes it is desired to wipe clean the media partition or remove all packages. The situation may arise where you needed to do a partial or full erase without doctoring the device. If you perform a partial or full erase while patches are installed, this will only remove the package data that lists these patches as installed in Preware and WebOS Quick Install. The patches will still be applied to Palm's WebOS files. There is not yet a supported method to recover the patch package data. For now it is recommended to clean up all the patches via one of the following methods. These methods are listed in order of robustness. '''The only -guaranteed- way to ensure stock Palm WebOS files is by using the WebOS doctor: [[Webos Doctor Versions]]'''<br /> <br /> 1) Install &quot;Emergency Patch Recovery&quot; (EPR)<br /> 2) WebOS Repair Utility<br /> 3) WebOS Doctor<br /> <br /> === OTA Update ===<br /> During previous Use Preware's Update All feature. Launch Preware, Update Feeds, tap Package updates and tap update all. <br /> <br /> == Known Issues ==<br /> There are some known bumps in Preware's update-all with regards to patches, but no major roadblocks. The known issues and workarounds for them are:<br /> <br /> 1) It will stop when trying to update a dependent package. The workaround here is to remove patches that depend on another patch or package that has an update. For instance the uscl memos patch depends on universal command line patch. The update all will fail when it gets to these patches, and you can workaround that by removing the uscl memos patch and then re-running update all.<br /> <br /> 2.) When the &quot;install&quot; part of the remove/install update process for a patch fails, Preware's installed list doesn't refresh automatically so the failed patch still lists on the update screen as installed. You can workaround this by updating feeds or tapping &quot;remove&quot; on the left-over package in Preware.<br /> <br /> == Known Conflicts ==<br /> * Greg's great Messaging Plugins solution contains a patch to the messaging application that has yet to be incorporated with AUPT. This may cause conflicts with some messaging patches causing installation to fail and should -always- be removed prior to a WebOS OTA update.<br /> * Themes have yet to be incorporated into AUPT and may cause conflicts with patches. Themes should also -always- be removed prior to a WebOS OTA update.<br /> <br /> == Troubleshooting ==<br /> Patching is by nature a very ugly beast. There are bound to be unforeseen issues and difficult to debug situations. In the end you can always get back to a completely stock WebOS by performing a full erase followed by a WebOS doctor. Here we will list some known problems and workarounds.<br /> <br /> == Emergency ==<br /> In the event that you find yourself in an unsupported situation with regards to patching or simply want to ensure a clean slate of stock Palm WebOS files without any patches, the following is the only guaranteed method:<br /> <br /> 1) Backup / take not of any homebrew packages installed as well as any App Catalog applications that are not backed up via your Palm Profile<br /> 2) Go into device info -&gt; reset -&gt; Partial Erase to erase all applications.<br /> 3) Perform WebOS Doctor to ensure all Palm WebOS files are stock.<br /> <br /> You may also try the quick solution of installing &quot;Emergency Patch Recovery&quot; (EPR). Please note that this relies on information that patches saved/stored and is not a robust or guaranteed way to ensure patches are completely removed. It is very safe and works a vast majority of the time as intended, it simply is not guaranteed to clean up everything.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=On_Screen_Keyboard&diff=8924 2010-02-04T17:32:36Z

<p>Egaudet: </p> <hr /> <div>{{template:patch}}<br /> [[Image: VirtualKeyboard_1.png|thumb|right]]<br /> [[Image: VirtualKeyboard_2.png|thumb|right]]<br /> <br /> =Intoduction=<br /> [[Image: VirtualKeyboard_3.png|thumb|right]]<br /> The Palm Pre lacks a stock Virtual Keyboard, which can come in handy in many situations. Having a virtual keyboard is good for quick text responses/notes without having to stress the slider too much. Although the biggest use for a virtual keyboard on the Palm Pre is landscape mode. The goal of this Patch/Application is to have a fully integrated Virtual Keyboard for the many tasks where it is an inconvenience to use the hardware keyboard.<br /> <br /> =Operation= <br /> Unlike the Palm Symbol keyboard, you do not have to open the Pre's hardware keyboard to get the on-screen keyboard. Double-tapping the gesture area (near the round silver button) will bring up the on-screen keyboard if you are in a text input field. Tap with two fingers separated or Double-tap quickly. Currently the rendering takes a few seconds, and a 3rd tap will hide/stop the rendering. After you double-tap the blinking cursor should freeze for a few seconds while the keyboard renders. Be patient, future versions will work to minimize the load lag. When the Virtual Keyboard is displayed, a single tap on the gesture area will hide it.<br /> <br /> === Theme Selector key ===<br /> [[Image: VirtualKeyboard_4.png|160px|bottom]]&lt;br&gt;&lt;br&gt;<br /> The Theme Selector key is the lower left gears key on the default theme. On the remix themes the theme selector key is the lower right blank key. Tapping this brings up a list of installed themes to switch between.&lt;br&gt;&lt;br&gt;<br /> <br /> === Drag Mode Key ===<br /> [[Image: VirtualKeyboard_5.png|160px|bottom]]&lt;br&gt;&lt;br&gt;<br /> The Keyboard Drag-mode key is the finger key on the lower right side of the keyboard. On the remix themes the drag-mode key is the lower left blank key. Tapping this puts the keyboard into drag-mode, simply drag and drop the keyboard up and down the screen while this key is active.<br /> <br /> =Installation Procedure=<br /> Use the WebOS Internals over the air installer [[Application:Preware|Preware]] and simply select the software keyboard from the list of available patches and install it. From Preware go to Available Pacakges -&gt; Patch -&gt; Mojo to find the Virtual Keyboard.<br /> <br /> =Known Issues=<br /> * 3-second Load Lag<br /> * Must highlight the text box that was highlighted when the VKB was drawn in order to single-tap hide<br /> * Backspace/Enter does not work in web pages <br /> * Lacks Autocorrect<br /> * Need configuration/customization application support<br /> <br /> =Themes and Options=<br /> You may wish to add haptic feedback, click sound feedback and/or custom themes. Currently this consists of editing json file(s). For detailed information on themes and options: [[Virtual Keyboard Configuration]]<br /> <br /> =Technical Background, Explanation and History=<br /> On an unmodified Pre if you press the &quot;sym&quot; key a scrollable 5x5 keyboard pops up full of alternate characters. <br /> <br /> This is controlled by code incorporated into the framework.js. The specific functions there can be seeen in '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/javascripts/widget_charselector.js'''<br /> <br /> with the layout controlled by 3 files in '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/templates/charselector'''<br /> <br /> the actual list of characters that appear on the screen is controlled by '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/resources/en_us/alternatechars_table.json'''<br /> <br /> On 12 August 2009 Webos-internals contributor Eric Gaudet (irc egaudet) announced success at patching the framework.js to accept a new function derived from the charselector widget. This pre-alpha proof of concept on-screen keyboard was made available as a patch. Since that time, the keyboard has been extended to work in search fields, to be installable as an IPKG, and to be themeable. <br /> <br /> ''Note that this requires patching the primary framework of WebOS.'' This is not an application running on top of WebOS but rather a modification of the operation of the OS itself to render a custom widget.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Virtual_Keybord_Configuration&diff=8923 2010-02-04T17:29:38Z

<p>Egaudet: Virtual Keybord Configuration moved to Virtual Keyboard Configuration</p> <hr /> <div>#REDIRECT [[Virtual Keyboard Configuration]]</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Virtual_Keyboard_Configuration&diff=8922 2010-02-04T17:29:38Z

<p>Egaudet: Virtual Keybord Configuration moved to Virtual Keyboard Configuration</p> <hr /> <div>=Options and Themes=<br /> <br /> The keyboard has several user configurable options. As of 28 August 2009 there is no keyboard configuration app. However, '''you do not have to have root access''' to configure the keyboard. Simply attach your Pre to your computer in USB Drive Mode. Then, navigate to the Pre's USB drive. On your desktop, there will be a directory (folder) called virtual-keyboard. (From within the Pre this is /media/internal/virtual-keyboard ''which is the same place''.) <br /> <br /> Inside that folder, you will find a file named virtual-keyboard/kb_config.json. Use your editor of choice (such as Wordpad - ''do not use MS Word'') to edit that file. You may change any of the following options: <br /> * haptic : &lt;number&gt; - How long to vibrate upon touch (0 - 100 ms) (50 seems good. 100 makes the keyboard lag a little. <br /> * clickFile : &lt;string&gt; - Sound file if any to play upon button click (e.g. click1.wav)<br /> * installed_themes : [{label:&lt;string&gt;,value:&lt;string&gt;},...] - Installed themes, label is the display name and value is the themes folder name<br /> * theme : &lt;string&gt; - Name of keyboard theme to use. Three themes ship with the keyboard: <br /> ** remix_classic<br /> ** remix_glossy<br /> ** remix_ice<br /> *: You may choose any of the three or add your own theme in an appropriate folder and name it as you please. See below on creating theme files.<br /> <br /> &lt;TABLE&gt;&lt;TR&gt;&lt;TD&gt;Remix Classic [[Image:remixClassic.png|70px]]&lt;/TD&gt;&lt;TD&gt;Remix Glossy [[Image:remixGlossy.png|70px]]&lt;/TD&gt;&lt;TD&gt;Remix Ice [[Image:remixIce.png|70px]]&lt;/TD&gt;&lt;/TR&gt;&lt;/TABLE&gt;<br /> <br /> == Additional Available Themes - Not working ==<br /> <br /> &lt;TABLE&gt;&lt;TR&gt;&lt;TD&gt;<br /> '''Eazys Theme''' [[image:28731d1251393689-screen-keyboard-bugs-functionality-enhancements-messaging_2009-27-08_121219.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28732d1251393700-screen-keyboard-bugs-functionality-enhancements-eazys_theme.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''Eazys Theme 2''' [[image:eazystheme2.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28963d1251487552-screen-keyboard-bugs-functionality-enhancements-eazys_theme2.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;'''Eazys Theme Gloss''' [[image:eazysthemegloss.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28953d1251482182-screen-keyboard-bugs-functionality-enhancements-eazys_themegloss.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''Eazys Trans''' [[image:eazystrans.png|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28924d1251474261-screen-keyboard-bugs-functionality-enhancements-eazys_trans.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;'''dianehelen Glossy Blue''' [[image:glossyblue.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29123d1251633769-screen-keyboard-bugs-functionality-enhancements-glossy_blue.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''2sslow Blue''' [[Image:messaging_2009-27-08_213107.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28850d1251436402-screen-keyboard-bugs-functionality-enhancements-2sslow_blue.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;tr&gt;&lt;td&gt;'''pychozoundz sleek light''' [[Image:SleekLight.jpg|thumb|80px]]&lt;/td&gt;&lt;td&gt;'''and dark'''[[Image:sleekDark.jpg|thumb|80px]][http://www.2shared.com/file/7441193/71eb02de/sleek_light_dark.html]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Un-Designer LucasPapaya [[Image:LucasPapaya.jpg|thumb|80px]] [http://dl.getdropbox.com/u/15257/LucasPapaya.zip]&lt;/td&gt;<br /> <br /> <br /> <br /> <br /> &lt;TD&gt; '''dianehelen Autumn''' [[image:autumnkb.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29125d1251633839-screen-keyboard-bugs-functionality-enhancements-autumn.zip]<br /> &lt;/td&gt;<br /> <br /> <br /> <br /> <br /> &lt;/tr&gt;<br /> <br /> <br /> <br /> &lt;TR&gt; &lt;TD&gt;'''dianehelen Denali''' [[image:denalikb.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29127d1251633870-screen-keyboard-bugs-functionality-enhancements-denali.zip]<br /> &lt;/TD&gt;<br /> <br /> &lt;TD&gt;<br /> <br /> <br /> '''dianehelen RBW(RedBlackWhite)''' [[image:rbwkb.jpg|thumb|80px]] Download [http://forums.precentral.net/attachments/web-os-development/29218d1251678400-onscreen-keyboard-theme-instructions-rwb.zip]<br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;/TD&gt;&lt;/TR&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;/table&gt;<br /> <br /> <br /> =Creating Keyboard Themes=<br /> The virtual keyboard layout is a &quot;list&quot; of rows containing 10 &quot;elements&quot; each. The design allows for the keys to span multiple elements.<br /> <br /> The virtual keyboard will look for themes located at /media/internal/virtual-keyboard/themes/<br /> In this directory there shall exist theme-named directories with the following structure and options:<br /> <br /> theme_config.json is the file that will control what images in this directory should be used and how. <br /> <br /> The first layer of the JSON for each key element will have 3 parts:<br /> index:&lt;Integer&gt;,portrait:{},landscape:{}<br /> <br /> index - index of key<br /> portrait - orientation JSON describing theme layout for portrait mode<br /> landscape - orientation JSON describing theme layout for landscape mode<br /> <br /> <br /> Inside of the orientation JSON's we have another 3 parts:<br /> normal:{},function:{},shift:{}<br /> <br /> normal - key description JSON when in normal keyboard<br /> function - key description JSON when function (orange) key is active<br /> shift - key description JSON when shift key is active<br /> <br /> <br /> The key description JSON has the following 4 parts:<br /> keyCode:&lt;Integer&gt;,display:{},output:&lt;String&gt;,span:&lt;Integer&gt;<br /> <br /> keyCode - currently only used for special action keys (shift, function, etc..)<br /> display - key display JSON<br /> output - output string when key is pressed<br /> span - number of element-widths to span (1 element-width=10%)<br /> <br /> <br /> The key display JSON has 2 parts:<br /> html:&lt;String&gt;,img:&lt;String&gt;<br /> <br /> html - HTML to display as element if no img supplied<br /> img - Image (including relative path in this theme's directory) to display as element</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Virtual_Keyboard_Configuration&diff=8921 2010-02-04T17:25:10Z

<p>Egaudet: New page: =Options and Themes= The keyboard has several user configurable options. As of 28 August 2009 there is no keyboard configuration app. However, '''you do not have to have root access''' ...</p> <hr /> <div>=Options and Themes=<br /> <br /> The keyboard has several user configurable options. As of 28 August 2009 there is no keyboard configuration app. However, '''you do not have to have root access''' to configure the keyboard. Simply attach your Pre to your computer in USB Drive Mode. Then, navigate to the Pre's USB drive. On your desktop, there will be a directory (folder) called virtual-keyboard. (From within the Pre this is /media/internal/virtual-keyboard ''which is the same place''.) <br /> <br /> Inside that folder, you will find a file named virtual-keyboard/kb_config.json. Use your editor of choice (such as Wordpad - ''do not use MS Word'') to edit that file. You may change any of the following options: <br /> * haptic : &lt;number&gt; - How long to vibrate upon touch (0 - 100 ms) (50 seems good. 100 makes the keyboard lag a little. <br /> * clickFile : &lt;string&gt; - Sound file if any to play upon button click (e.g. click1.wav)<br /> * installed_themes : [{label:&lt;string&gt;,value:&lt;string&gt;},...] - Installed themes, label is the display name and value is the themes folder name<br /> * theme : &lt;string&gt; - Name of keyboard theme to use. Three themes ship with the keyboard: <br /> ** remix_classic<br /> ** remix_glossy<br /> ** remix_ice<br /> *: You may choose any of the three or add your own theme in an appropriate folder and name it as you please. See below on creating theme files.<br /> <br /> &lt;TABLE&gt;&lt;TR&gt;&lt;TD&gt;Remix Classic [[Image:remixClassic.png|70px]]&lt;/TD&gt;&lt;TD&gt;Remix Glossy [[Image:remixGlossy.png|70px]]&lt;/TD&gt;&lt;TD&gt;Remix Ice [[Image:remixIce.png|70px]]&lt;/TD&gt;&lt;/TR&gt;&lt;/TABLE&gt;<br /> <br /> == Additional Available Themes - Not working ==<br /> <br /> &lt;TABLE&gt;&lt;TR&gt;&lt;TD&gt;<br /> '''Eazys Theme''' [[image:28731d1251393689-screen-keyboard-bugs-functionality-enhancements-messaging_2009-27-08_121219.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28732d1251393700-screen-keyboard-bugs-functionality-enhancements-eazys_theme.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''Eazys Theme 2''' [[image:eazystheme2.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28963d1251487552-screen-keyboard-bugs-functionality-enhancements-eazys_theme2.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;'''Eazys Theme Gloss''' [[image:eazysthemegloss.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28953d1251482182-screen-keyboard-bugs-functionality-enhancements-eazys_themegloss.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''Eazys Trans''' [[image:eazystrans.png|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28924d1251474261-screen-keyboard-bugs-functionality-enhancements-eazys_trans.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;'''dianehelen Glossy Blue''' [[image:glossyblue.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29123d1251633769-screen-keyboard-bugs-functionality-enhancements-glossy_blue.zip]<br /> <br /> &lt;/TD&gt;&lt;TD&gt;'''2sslow Blue''' [[Image:messaging_2009-27-08_213107.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/28850d1251436402-screen-keyboard-bugs-functionality-enhancements-2sslow_blue.zip]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;tr&gt;&lt;td&gt;'''pychozoundz sleek light''' [[Image:SleekLight.jpg|thumb|80px]]&lt;/td&gt;&lt;td&gt;'''and dark'''[[Image:sleekDark.jpg|thumb|80px]][http://www.2shared.com/file/7441193/71eb02de/sleek_light_dark.html]<br /> <br /> &lt;/TD&gt;&lt;/TR&gt;&lt;TR&gt;&lt;TD&gt;Un-Designer LucasPapaya [[Image:LucasPapaya.jpg|thumb|80px]] [http://dl.getdropbox.com/u/15257/LucasPapaya.zip]&lt;/td&gt;<br /> <br /> <br /> <br /> <br /> &lt;TD&gt; '''dianehelen Autumn''' [[image:autumnkb.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29125d1251633839-screen-keyboard-bugs-functionality-enhancements-autumn.zip]<br /> &lt;/td&gt;<br /> <br /> <br /> <br /> <br /> &lt;/tr&gt;<br /> <br /> <br /> <br /> &lt;TR&gt; &lt;TD&gt;'''dianehelen Denali''' [[image:denalikb.jpg|thumb|80px]] Download [http://discussion.treocentral.com/attachments/web-os-development/29127d1251633870-screen-keyboard-bugs-functionality-enhancements-denali.zip]<br /> &lt;/TD&gt;<br /> <br /> &lt;TD&gt;<br /> <br /> <br /> '''dianehelen RBW(RedBlackWhite)''' [[image:rbwkb.jpg|thumb|80px]] Download [http://forums.precentral.net/attachments/web-os-development/29218d1251678400-onscreen-keyboard-theme-instructions-rwb.zip]<br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;/TD&gt;&lt;/TR&gt;<br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> <br /> &lt;/table&gt;<br /> <br /> <br /> =Creating Keyboard Themes=<br /> The virtual keyboard layout is a &quot;list&quot; of rows containing 10 &quot;elements&quot; each. The design allows for the keys to span multiple elements.<br /> <br /> The virtual keyboard will look for themes located at /media/internal/virtual-keyboard/themes/<br /> In this directory there shall exist theme-named directories with the following structure and options:<br /> <br /> theme_config.json is the file that will control what images in this directory should be used and how. <br /> <br /> The first layer of the JSON for each key element will have 3 parts:<br /> index:&lt;Integer&gt;,portrait:{},landscape:{}<br /> <br /> index - index of key<br /> portrait - orientation JSON describing theme layout for portrait mode<br /> landscape - orientation JSON describing theme layout for landscape mode<br /> <br /> <br /> Inside of the orientation JSON's we have another 3 parts:<br /> normal:{},function:{},shift:{}<br /> <br /> normal - key description JSON when in normal keyboard<br /> function - key description JSON when function (orange) key is active<br /> shift - key description JSON when shift key is active<br /> <br /> <br /> The key description JSON has the following 4 parts:<br /> keyCode:&lt;Integer&gt;,display:{},output:&lt;String&gt;,span:&lt;Integer&gt;<br /> <br /> keyCode - currently only used for special action keys (shift, function, etc..)<br /> display - key display JSON<br /> output - output string when key is pressed<br /> span - number of element-widths to span (1 element-width=10%)<br /> <br /> <br /> The key display JSON has 2 parts:<br /> html:&lt;String&gt;,img:&lt;String&gt;<br /> <br /> html - HTML to display as element if no img supplied<br /> img - Image (including relative path in this theme's directory) to display as element</div>

Egaudet http://wiki.webos-internals.org/index.php?title=On_Screen_Keyboard&diff=8920 2010-02-04T17:22:34Z

<p>Egaudet: </p> <hr /> <div>{{template:patch}}<br /> [[Image: VirtualKeyboard_1.png|thumb|right]]<br /> [[Image: VirtualKeyboard_2.png|thumb|right]]<br /> <br /> =Intoduction=<br /> [[Image: VirtualKeyboard_3.png|thumb|right]]<br /> The Palm Pre lacks a stock Virtual Keyboard, which can come in handy in many situations. Having a virtual keyboard is good for quick text responses/notes without having to stress the slider too much. Although the biggest use for a virtual keyboard on the Palm Pre is landscape mode. The goal of this Patch/Application is to have a fully integrated Virtual Keyboard for the many tasks where it is an inconvenience to use the hardware keyboard.<br /> <br /> =Operation= <br /> Unlike the Palm Symbol keyboard, you do not have to open the Pre's hardware keyboard to get the on-screen keyboard. Double-tapping the gesture area (near the round silver button) will bring up the on-screen keyboard if you are in a text input field. Tap with two fingers separated or Double-tap quickly. Currently the rendering takes a few seconds, and a 3rd tap will hide/stop the rendering. After you double-tap the blinking cursor should freeze for a few seconds while the keyboard renders. Be patient, future versions will work to minimize the load lag. When the Virtual Keyboard is displayed, a single tap on the gesture area will hide it.<br /> <br /> === Theme Selector key ===<br /> [[Image: VirtualKeyboard_4.png|160px|bottom]]&lt;br&gt;&lt;br&gt;<br /> The Theme Selector key is the lower left gears key on the default theme. On the remix themes the theme selector key is the lower right blank key. Tapping this brings up a list of installed themes to switch between.&lt;br&gt;&lt;br&gt;<br /> <br /> === Drag Mode Key ===<br /> [[Image: VirtualKeyboard_5.png|160px|bottom]]&lt;br&gt;&lt;br&gt;<br /> The Keyboard Drag-mode key is the finger key on the lower right side of the keyboard. On the remix themes the drag-mode key is the lower left blank key. Tapping this puts the keyboard into drag-mode, simply drag and drop the keyboard up and down the screen while this key is active.<br /> <br /> =Installation Procedure=<br /> Use the WebOS Internals over the air installer [[Application:Preware|Preware]] and simply select the software keyboard from the list of available patches and install it. From Preware go to Available Pacakges -&gt; Patch -&gt; Mojo to find the Virtual Keyboard.<br /> <br /> =Known Issues=<br /> * 3-second Load Lag<br /> * Must highlight the text box that was highlighted when the VKB was drawn in order to single-tap hide<br /> * Backspace/Enter does not work in web pages <br /> * Lacks Autocorrect<br /> <br /> <br /> =Technical Background, Explanation and History=<br /> On an unmodified Pre if you press the &quot;sym&quot; key a scrollable 5x5 keyboard pops up full of alternate characters. <br /> <br /> This is controlled by code incorporated into the framework.js. The specific functions there can be seeen in '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/javascripts/widget_charselector.js'''<br /> <br /> with the layout controlled by 3 files in '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/templates/charselector'''<br /> <br /> the actual list of characters that appear on the screen is controlled by '''/usr/palm/frameworks/mojo/submissions/&lt;framework_version&gt;/resources/en_us/alternatechars_table.json'''<br /> <br /> On 12 August 2009 Webos-internals contributor Eric Gaudet (irc egaudet) announced success at patching the framework.js to accept a new function derived from the charselector widget. This pre-alpha proof of concept on-screen keyboard was made available as a patch. Since that time, the keyboard has been extended to work in search fields, to be installable as an IPKG, and to be themeable. <br /> <br /> ''Note that this requires patching the primary framework of WebOS.'' This is not an application running on top of WebOS but rather a modification of the operation of the OS itself to render a custom widget.</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Portal:Updating_webOS_Versions&diff=8854 2010-02-01T21:40:38Z

<p>Egaudet: </p> <hr /> <div>{{portal-header<br /> |Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results. If you have already updated webOS and did not remove your themes/patches, you will still need to follow these steps.<br /> <br /> # Make sure you are running the latest versions of [[Application:Preware|Preware]] and the Package Manager Service.<br /> #: If you are not, then go to http://install.preware.org/ and install them.<br /> # Open [[Application:Preware|Preware]] and select Installed Packages.<br /> # Remove any Theme(s) you have installed. There SHOULD only be one...<br /> # Update webOS. :) (If you have already updated, skip this step.)<br /> # Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).<br /> # Select Update Feeds.<br /> # All of your Patches should show as needing an update, tap Update All<br /> # Reinstall theme if desired<br /> # Thank the webOS-Internals group!<br /> <br /> If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.<br /> <br /> &lt;br /&gt;<br /> ''For advanced users:'' You can dump a list of installed packages using the following technique. This assumes you already have shell access to your your Pre via novaterm or ssh.<br /> <br /> *'''1.''' Ssh into your Pre (you do not need to adopt root privileges)<br /> *'''2.''' Type (no quotes) &quot;ipkg -o /var list_installed &lt;nowiki&gt;|&lt;/nowiki&gt; grep patches&quot;. This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.<br /> <br /> Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.<br /> }}</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Portal:Updating_webOS_Versions&diff=8853 2010-02-01T21:39:52Z

<p>Egaudet: </p> <hr /> <div>{{portal-header<br /> |Before updating to a new version of webOS, it is very important to follow certain procedures. Here is an outline of the recommended way to update your webOS when you use Patches (and/or Themes) installed via [[Application:Preware|Preware]]. Deviating from this procedure could cause unwanted results. If you have already updated webOS and did not remove your themes/patches, you will still need to follow these steps.<br /> <br /> # Make sure you are running the latest versions of [[Application:Preware|Preware]] and the Package Manager Service.<br /> #: If you are not, then go to http://install.preware.org/ and install them.<br /> # Open [[Application:Preware|Preware]] and select Installed Packages.<br /> # Remove any Theme(s) you have installed. There SHOULD only be one...<br /> # Go back to the main menu and select &quot;List of Everything&quot; and search for &quot;Emergency&quot;.<br /> # Update webOS. :) (If you have already updated, skip this step.)<br /> # Fire up [[Application:Preware|Preware]] and bring down the App Menu (top left corner).<br /> # Select Update Feeds.<br /> # All of your Patches should show as needing an update, tap Update All<br /> # Reinstall theme if desired<br /> # Thank the webOS-Internals group!<br /> <br /> If you need any assistance, or just want to chat, download an IRC client and join us in [irc://irc.freenode.net/webos-internals #webos-internals] on FreeNode.<br /> <br /> &lt;br /&gt;<br /> ''For advanced users:'' You can dump a list of installed packages using the following technique. This assumes you already have shell access to your your Pre via novaterm or ssh.<br /> <br /> *'''1.''' Ssh into your Pre (you do not need to adopt root privileges)<br /> *'''2.''' Type (no quotes) &quot;ipkg -o /var list_installed &lt;nowiki&gt;|&lt;/nowiki&gt; grep patches&quot;. This will display the list of patches applied to your Pre. You can redirect this output to a file or copy-and-paste it from your shell window.<br /> <br /> Special thanks to dbSooner on the [irc://irc.freenode.net/webos-internals #webos-internals] IRC channel for proposing this method.<br /> }}</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8851 2010-02-01T19:31:40Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Organization ===<br /> I suppose we could list all the Parts of themeing and how we want to separate/organize:<br /> &lt;pre&gt;<br /> Wallpaper<br /> Launch Icons<br /> System Images<br /> Global CSS classes<br /> Emoticons<br /> Fonts<br /> &lt;/pre&gt;<br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> Launch Point Icons are given a launchPointId, which by default is simply the &lt;appid&gt;_default. Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file. If no launchPointId is given, &lt;appid&gt;_default will be set.<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon },<br /> { appId: com.palm.browser, launchPointId: 12022008, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> },<br /> <br /> emoticons, fonts, top/bottom bar size (luna.conf and other /etc/palm configuration options etc...)<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8850 2010-02-01T19:30:47Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> I suppose we could list all the Parts of themeing and how we want to separate/organize:<br /> &lt;pre&gt;<br /> Wallpaper<br /> Launch Icons<br /> System Images<br /> Global CSS classes<br /> Emoticons<br /> Fonts<br /> &lt;/pre&gt;<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> Launch Point Icons are given a launchPointId, which by default is simply the &lt;appid&gt;_default. Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file. If no launchPointId is given, &lt;appid&gt;_default will be set.<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon },<br /> { appId: com.palm.browser, launchPointId: 12022008, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> },<br /> <br /> emoticons, fonts, top/bottom bar size (luna.conf and other /etc/palm configuration options etc...)<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8829 2010-02-01T06:19:42Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> Launch Point Icons are given a launchPointId, which by default is simply the &lt;appid&gt;_default. Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file. If no launchPointId is given, &lt;appid&gt;_default will be set.<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon },<br /> { appId: com.palm.browser, launchPointId: 12022008, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> },<br /> <br /> emoticons, fonts, top/bottom bar size (luna.conf and other /etc/palm configuration options etc...)<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8808 2010-02-01T00:33:16Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> Launch Point Icons are given a launchPointId, which by default is simply the &lt;appid&gt;_default. Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file. If no launchPointId is given, &lt;appid&gt;_default will be set.<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon },<br /> { appId: com.palm.browser, launchPointId: 12022008, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8807 2010-02-01T00:32:28Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> Launch Point Icons are given a launchPointId, which by default is simply the &lt;appid&gt;_default. Something like sprint portal is set up with launchPointId 12022008 seemingly via /usr/luna/launchpoints/12022008 file.<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon },<br /> { appId: com.palm.browser, launchPointId: 12022008, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8804 2010-02-01T00:19:08Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { launchPointId: com.palm.package1_default, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { launchPointId: com.palm.package2_default, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8803 2010-02-01T00:18:25Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v4 ====<br /> theme_config.json sans required quotes<br /> &lt;pre&gt;<br /> { <br /> applications:<br /> [<br /> { appId: com.palm.package1, icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { appId: com.palm.package2, icon: relative/path/to/icon }<br /> ],<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> image: relative/path/to/image<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8800 2010-01-31T18:36:13Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v3 ====<br /> theme_config.json sans required quotes<br /> &lt;pre&gt;<br /> { <br /> app:<br /> {<br /> { com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { com.palm.package2: { icon: relative/path/to/icon }<br /> },<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> },<br /> <br /> wallpaper:<br /> {<br /> icon: relative/path/to/icon<br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8797 2010-01-31T08:34:59Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v3 ====<br /> theme_config.json sans required quotes<br /> &lt;pre&gt;<br /> { <br /> app:<br /> {<br /> { com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { com.palm.package2: { icon: relative/path/to/icon }<br /> },<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> Does this assume that the css files pointed to will be sparse? [[User:Rboatright|rboatright]] 06:19, 31 January 2010 (UTC)<br /> <br /> ---<br /> <br /> I've done some testing and I've now verified the CSS loading model. Currently every app (including top-bar and app-launcher) call the single framework function Mojo.loadStylesheetsWithLink when loaded. This goes through and loads all the global css from the framework first and then all the app specific css. I patched this function to read the theme_config.json and load the global cssFileName (if exists) followed by the app specific cssFileName AFTER all the existing css loading is done (i.e. all global and app css). So this will allow overwriting as little or as much CSS as desired in the entire system. [[User:Egaudet|Egaudet]] 08:34, 31 January 2010 (UTC)<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8794 2010-01-31T05:53:00Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet v3 ====<br /> theme_config.json sans required quotes<br /> &lt;pre&gt;<br /> { <br /> app:<br /> {<br /> { com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css },<br /> { com.palm.package2: { icon: relative/path/to/icon }<br /> },<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css <br /> }<br /> }<br /> &lt;/pre&gt;<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet http://wiki.webos-internals.org/index.php?title=Talk:Theme_Management_API&diff=8793 2010-01-31T05:39:06Z

<p>Egaudet: </p> <hr /> <div>The original idea is a bit lacking with regards to file path restrictions. If we are going to create a legit Theme API, we should do it right and start off with an easy to read and create config file. Let's discuss what this should look like<br /> <br /> === Theme API Config File ===<br /> ==== egaudet ====<br /> theme_config.json<br /> &lt;pre&gt;<br /> app:<br /> {<br /> com.palm.package1: { icon: relative/path/to/icon, cssFileName: relative/path/to/css };<br /> com.palm.package2: { icon: relative/path/to/icon };<br /> };<br /> <br /> global:<br /> {<br /> cssFileName: relative/path/to/global/css<br /> }<br /> &lt;/pre&gt;<br /> <br /> ==== PuffTheMagic v3 ====<br /> <br /> &lt;pre&gt;<br /> applications:<br /> {<br /> com.palm.package1:<br /> {<br /> launcherIcon = relative/path/to/icon1;<br /> }<br /> com.palm.package2:<br /> {<br /> css = relative/path/to/css2;<br /> }<br /> com.palm.package3:<br /> {<br /> css = relative/path/to/cs3;<br /> launcherIcon = relative/path/to/icon3;<br /> }<br /> };<br /> &lt;/pre&gt;<br /> ==== rboatright =====<br /> <br /> global css replacements not related to apps<br /> &lt;pre&gt;<br /> {<br /> cssFileName: relative/path/to/replacement/cssFile.css<br /> }<br /> &lt;/pre&gt;<br /> ==== zsoc ====<br /> &lt;pre&gt;<br /> HOW DID THIS GET HERE I AM NOT GOOD WITH COMPUTER<br /> &lt;/pre&gt;</div>

Egaudet