Page 4 of 4 FirstFirst 1234
Results 61 to 80 of 80
Like Tree2Likes
  1.    #61  
    You should read the Meta-Doctor documentation to understand the DEVICE and CARRIER required arguments.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  2. #62  
    Quote Originally Posted by rwhitby View Post
    The Meta-Doctor solution will work on a Veer.

    -- Rod
    Quote Originally Posted by rwhitby View Post
    You should read the Meta-Doctor documentation to understand the DEVICE and CARRIER required arguments.

    -- Rod
    Done, but i can't find the file castle.xml in the folder build/veer-p160una-wr-2.1.1/webOS/


    this is my log:

    root@ubuntu:~/meta-doctor# make DEVICE=veer CARRIER=wr all unpack patch
    [: 3: p160una: unexpected operator
    [: 3: 2.1.1: unexpected operator
    make unpack patch pack
    make[1]: Entering directory `/home/bebz/meta-doctor'
    rm -rf build/veer-p160una-wr-2.1.1
    mkdir -p build/veer-p160una-wr-2.1.1
    cp downloads/webosdoctorp160una-wr-2.1.1.jar build/veer-p160una-wr-2.1.1/webosdoctorp160una-wr-2.1.1.jar
    ( cd build/veer-p160una-wr-2.1.1 ; \
    unzip -q webosdoctorp160una-wr-2.1.1.jar META-INF/MANIFEST.MF com/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/veer-p160una-wr-2.1.1 ; \
    unzip -q webosdoctorp160una-wr-2.1.1.jar resources/wr.tar )
    mkdir -p build/veer-p160una-wr-2.1.1/webOS
    tar -C build/veer-p160una-wr-2.1.1/webOS \
    -f build/veer-p160una-wr-2.1.1/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/veer-p160una-wr-2.1.1/webOS/BootLogo.tga
    mkdir -p build/veer-p160una-wr-2.1.1/carrier
    tar -f build/veer-p160una-wr-2.1.1/resources/wr.tar -t \
    > build/veer-p160una-wr-2.1.1/carrier-file-list.txt
    tar -C build/veer-p160una-wr-2.1.1/carrier \
    -f build/veer-p160una-wr-2.1.1/resources/wr.tar -x
    gunzip -f build/veer-p160una-wr-2.1.1/webOS/nova-cust-image-broadway.rootfs.tar.gz
    mkdir -p build/veer-p160una-wr-2.1.1/rootfs
    tar -C build/veer-p160una-wr-2.1.1/rootfs --wildcards \
    -f build/veer-p160una-wr-2.1.1/webOS/nova-cust-image-broadway.rootfs.tar \
    -x ./usr/lib/ipkg/info
    rm -f build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt
    for package in com.palm.app.firstuse palmbuildinfo ; do \
    if [ -f build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.list ] ; then \
    cat build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.list | \
    sed -e 's|^|.|' >> build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt ; \
    fi ; \
    done
    tar -C build/veer-p160una-wr-2.1.1/rootfs --wildcards \
    -f build/veer-p160una-wr-2.1.1/webOS/nova-cust-image-broadway.rootfs.tar \
    -x -T build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt ./boot ./lib/modules ./md5sums*
    touch build/veer-p160una-wr-2.1.1/.unpacked
    rm -f build/veer-p160una-wr-2.1.1/.patched
    [ -d patches/webos-2.1.1 ]
    for package in com.palm.app.firstuse palmbuildinfo ; do \
    mv build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.old ; \
    ( cd build/veer-p160una-wr-2.1.1/rootfs ; \
    cat ./usr/lib/ipkg/info/$package.list | sed -e 's|^|.|' | \
    xargs -I '{}' find '{}' -type f -prune -print | xargs md5sum ) \
    > build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.new ; \
    ./scripts/replace-md5sums.py \
    build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.old build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.new \
    > build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums ; \
    rm -f build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.old build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.md5sums.new ; \
    done
    if [ -f build/veer-p160una-wr-2.1.1/rootfs/md5sums.gz ] ; then \
    gunzip -c < build/veer-p160una-wr-2.1.1/rootfs/md5sums.gz > build/veer-p160una-wr-2.1.1/rootfs/md5sums ; \
    fi
    mv build/veer-p160una-wr-2.1.1/rootfs/md5sums build/veer-p160una-wr-2.1.1/rootfs/md5sums.old
    ( cd build/veer-p160una-wr-2.1.1/rootfs ; find . -type f | xargs md5sum ) \
    > build/veer-p160una-wr-2.1.1/rootfs/md5sums.new
    ./scripts/replace-md5sums.py build/veer-p160una-wr-2.1.1/rootfs/md5sums.old build/veer-p160una-wr-2.1.1/rootfs/md5sums.new > \
    build/veer-p160una-wr-2.1.1/rootfs/md5sums
    rm -f build/veer-p160una-wr-2.1.1/rootfs/md5sums.old build/veer-p160una-wr-2.1.1/rootfs/md5sums.new
    touch build/veer-p160una-wr-2.1.1/.patched
    rm -f build/veer-p160una-wr-2.1.1/.packed
    ( cd build/veer-p160una-wr-2.1.1/rootfs ; mkdir -p ./boot ./lib/modules ./var/luna/preferences ./var/gadget ./var/home/root ./var/preferences ./var/palm/data )
    rm -f build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt
    for package in com.palm.app.firstuse palmbuildinfo ; do \
    cat build/veer-p160una-wr-2.1.1/rootfs/usr/lib/ipkg/info/$package.list | \
    sed -e 's|^|.|' >> build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt ; \
    done
    if [ -f build/veer-p160una-wr-2.1.1/rootfs/md5sums.gz ] ; then \
    gzip -f build/veer-p160una-wr-2.1.1/rootfs/md5sums ; \
    fi
    tar -C build/veer-p160una-wr-2.1.1/rootfs --wildcards \
    -f build/veer-p160una-wr-2.1.1/webOS/nova-cust-image-broadway.rootfs.tar \
    --delete -T build/veer-p160una-wr-2.1.1/ipkgs-file-list.txt \
    ./usr/lib/ipkg/info ./boot ./lib/modules ./md5sums*
    ( cd build/veer-p160una-wr-2.1.1/rootfs ; \
    tar -f ../webOS/nova-cust-image-broadway.rootfs.tar \
    --numeric-owner --owner=0 --group=0 \
    --append -T ../ipkgs-file-list.txt \
    ./usr/lib/ipkg/info ./boot ./lib/modules ./var/luna/preferences ./var/gadget ./var/home/root ./var/preferences ./var/palm/data ./md5sums* )
    gzip -f build/veer-p160una-wr-2.1.1/webOS/nova-cust-image-broadway.rootfs.tar
    ( cd build/veer-p160una-wr-2.1.1/webOS ; \
    tar -f ../resources/webOS.tar \
    --numeric-owner --owner=0 --group=0 -h \
    -c . )
    sed -i.orig -e '/^Name: /d' -e '/^SHA1-Digest: /d' -e '/^ /d' -e '/^\n$/d' \
    build/veer-p160una-wr-2.1.1/META-INF/MANIFEST.MF
    ( cd build/veer-p160una-wr-2.1.1 ; \
    zip -q -d webosdoctorp160una-wr-2.1.1.jar META-INF/MANIFEST.MF META-INF/JARKEY.* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/veer-p160una-wr-2.1.1 ; \
    zip -q webosdoctorp160una-wr-2.1.1.jar META-INF/MANIFEST.MF \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/veer-p160una-wr-2.1.1/carrier ; \
    tar -f ../resources/wr.tar \
    --numeric-owner --owner=0 --group=0 -h \
    -c -T ../carrier-file-list.txt )
    ( cd build/veer-p160una-wr-2.1.1 ; \
    zip -q -d webosdoctorp160una-wr-2.1.1.jar resources/wr.tar )
    ( cd build/veer-p160una-wr-2.1.1 ; \
    zip -q webosdoctorp160una-wr-2.1.1.jar resources/wr.tar )

    Your custom doctor file has been created at build/veer-p160una-wr-2.1.1/webosdoctorp160una-wr-2.1.1.jar

    touch build/veer-p160una-wr-2.1.1/.packed
    make[1]: Leaving directory `/home/bebz/meta-doctor'
    make: Nothing to be done for `unpack'.
    make: Nothing to be done for `patch'.
  3.    #63  
    For the veer it will be broadway.xml

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  4. #64  
    Quote Originally Posted by rwhitby View Post
    For the veer it will be broadway.xml

    -- Rod
    Cool, thanks.

    does this look right to you:

    <?xml version="1.0" encoding="UTF-8"?>
    <!-- Installer Rules for Broadway Hardware -->
    <TrenchCoat>
    <CPU type="MSM7X30"/>
    <Flash type="mmc" alignment="32768" reusePartitions="true" device="/dev/mmcblk0">
    <Entry type="mbr" size="512" align="false"/>
    <Entry type="space" partition="0x6" size="102400KB" reformat="false"/> <!-- p1, FAT (amss, chainbootie) -->
    <Entry type="space" partition="0x4d" size="500KB" reformat="false"/> <!-- p2, CFG_DATA; dbl.mbn -->
    <Entry type="space" partition="0x46" size="1500KB" reformat="false"/> <!-- p3, OSBL; osbl.mbn -->

    <!-- Here begins the extended partitions (extended partition p4) -->
    <Entry type="space" partition="0x4e" size="1MB" reformat="false"/> <!-- p5, EFS2 -->
    <Entry type="space" partition="0x4c" size="1MB" reformat="false"/> <!-- p6, FOTA -->
    <Entry type="space" partition="0x4a" size="3072KB" reformat="false"/> <!-- p7, MODEM_ST1 -->
    <Entry type="space" partition="0x4b" size="3072KB" reformat="false"/> <!-- p8, MODEM_ST2 -->
    <Entry type="space" partition="0x50" size="6000KB" reformat="false"/> <!-- p9, ADSP; adsp.mbn -->
    <Entry type="space" partition="0x58" size="3072KB" reformat="false"/> <!-- p10, MODEM_GOLDEN -->
    <Entry type="space" partition="0xff" size="3072KB" reformat="false"/> <!-- p11, MODEM_PAD -->

    <!-- Here is palm territory. There be dragons. -->
    <Entry type="bootloader" partition="0x48" size="2500KB" alignment="0x4000000" reusePartition="false" file="${BOOTIE}"/> <!-- p12, APPS (bootie) -->
    <Entry type="nvram" size="4MB" reusePartition="false">
    <Section name="env" type="env" size="16KB">
    <Val name="installer" value="trenchcoat"/>
    <Val name="autoboot" action="delete"/>
    <Val name="bootfile" action="delete"/>
    </Section>
    <Section name="tokens" type="token" size="4KB">
    <Val name="installer" value="trenchcoat"/>
    <Val name="KEYoBRD" action="overwrite" value="z"/>
    </Section>
    <Section name="logo-boot" type="image" file="BootLogo.tga"/>
    <Section name="logo-chg" type="image" file="Charging.tga"/>
    <Section name="logo-badchg" type="image" file="NoPower.tga"/>
    <Section name="logo-nobatt" type="image" file="NoBatt.tga"/>
    <Section name="logo-badsys" type="image" file="BadSys.tga"/>
    <Section name="logo-nosys" type="image" file="NoSys.tga"/>
    <Section name="logo-sync" type="image" file="Sync.tga"/>
    <Section name="logo-panic" type="image" file="Panic.tga"/>
    <Section name="logo-disk" type="image" file="Disk.tga"/>
    </Entry>
    <Entry type="ext3" size="32MB" reusePartition="false" mount="/boot"/> <!-- p14, /boot -->
    <Entry type="lvm" id="pv" size="*" alignment="0x4000000" reusePartition="false" metadatasize="8MB" metadatacopies="2"/> <!-- p15, LVM -->
    </Flash>
    <VolumeGroups>
    <Group name="store" pv="pv" physicalextentsize="8MB">
    <Volume id="root" type="ext3" size="456MB" mount="/"/>
    <Volume id="var" type="ext3" size="64MB" mount="/var"/>
    <Volume id="update" type="ext3" size="16MB" mount="/var/lib/update"/>
    <Volume id="log" type="ext3" size="24MB" mount="/var/log"/>
    <Volume id="mojodb" type="ext3" size="144MB" mount="/var/db"/>
    <Volume id="filecache" type="ext3" size="136MB" inode_size="256" mount="/var/file-cache"/>
    <Volume id="media" type="fat32" size="*" mount="/media/internal"/>
    <Volume id="swap" size="104MB"/>
    </Group>
    </VolumeGroups>
    <Filesystem fstab="/etc/fstab">
    <Mount device="rootfs" mount="/" type="ext3" options="ro,suid,dev,exec,auto,nouser,async,noatime" freq="1" passno="1"/>
    <Mount id="var" options="noatime,data=writeback" freq="0" passno="0"/>
    <Mount id="mojodb" options="noatime" freq="0" passno="0"/>
    <Mount id="filecache" options="noatime,user_xattr" freq="0" passno="0"/>
    <Mount id="log" options="noatime" freq="0" passno="0"/>
    <Mount id="update" options="noauto,noatime" freq="0" passno="0"/>
    <Mount device="proc" mount="/proc" type="proc" options="defaults" freq="0" passno="0"/>
    <Mount device="devpts" mount="/dev/pts" type="devpts" options="mode=0620,gid=5" freq="0" passno="0"/>
    <Mount device="tmpfs" mount="/tmp" type="tmpfs" options="size=32M,mode=1777" freq="0" passno="0"/>
    <Mount device="tmpfs" mount="/var/run" type="tmpfs" options="size=16M,mode=1777" freq="0" passno="0"/>
    <Mount device="tmpfs" mount="/var/tmp" type="tmpfs" options="size=32M,mode=1777" freq="0" passno="0"/>
    <Mount device="tmpfs" mount="/media/ram" type="tmpfs" options="defaults" freq="0" passno="0"/>
    <Mount id="media" options="utf8,shortname=mixed,umask=0000" freq="0" passno="0"/>
    </Filesystem>
    <Images>
    <File file="${NOVATGZ}" target="/"/>
    </Images>
    <PostInstall file="/sbin/tcpostflash.sh"/>
    </TrenchCoat>
  5.    #65  
    The red line is correct. I assume the rest is unchanged.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  6. #66  
    Quote Originally Posted by rwhitby View Post
    The red line is correct. I assume the rest is unchanged.

    -- Rod
    yup, what am i doing wrong here:

    root@ubuntu:~/meta-doctor# make DEVICE=veer CARRIER=wr all pack
    [: 3: p160una: unexpected operator
    [: 3: 2.1.1: unexpected operator
    make unpack patch pack
    make[1]: Entering directory `/home/bebz/meta-doctor'
    make[1]: Nothing to be done for `unpack'.
    make[1]: Nothing to be done for `patch'.
    make[1]: Nothing to be done for `pack'.
    make[1]: Leaving directory `/home/bebz/meta-doctor'
    make: Nothing to be done for `pack'.
  7.    #67  
    Quote Originally Posted by bebz View Post
    yup, what am i doing wrong here:

    root@ubuntu:~/meta-doctor# make DEVICE=veer CARRIER=wr all pack
    [: 3: p160una: unexpected operator
    [: 3: 2.1.1: unexpected operator
    make unpack patch pack
    make[1]: Entering directory `/home/bebz/meta-doctor'
    make[1]: Nothing to be done for `unpack'.
    make[1]: Nothing to be done for `patch'.
    make[1]: Nothing to be done for `pack'.
    make[1]: Leaving directory `/home/bebz/meta-doctor'
    make: Nothing to be done for `pack'.
    Don't do pack the first time. Only pack after you've edited the xml file.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  8. #68  
    Quote Originally Posted by rwhitby View Post
    Don't do pack the first time. Only pack after you've edited the xml file.

    -- Rod
    what do you mean? i edited the file then i did that command
  9. #69  
    i repeated the entire process and getting the same results. i only run the command after i edit the file and nothing. i even tried to test and doctored the veer, but nothing occured. what's the exact command to pack for the veer, i'm typing:

    make DEVICE=veer CARRIER=wr all pack

    Basically the process consists of the following steps once meta doctor is ready:
    1. make clobber
    2. make DEVICE=veer CARRIER=wr all unpack patch
    3. edit the broadway.xml (attached)
    4. save
    5. make DEVICE=veer CARRIER=wr all pack

    Please help, i cannot pack it to doctor
    Attached Files Attached Files
  10.    #70  
    Quote Originally Posted by bebz View Post
    i repeated the entire process and getting the same results. i only run the command after i edit the file and nothing. i even tried to test and doctored the veer, but nothing occured. what's the exact command to pack for the veer, i'm typing:

    make DEVICE=veer CARRIER=wr all pack

    Basically the process consists of the following steps once meta doctor is ready:
    1. make clobber
    2. make DEVICE=veer CARRIER=wr all unpack patch
    3. edit the broadway.xml (attached)
    4. save
    5. make DEVICE=veer CARRIER=wr all pack

    Please help, i cannot pack it to doctor
    Leave out the 'all' from step 2.

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  11. #71  
    Thanks to Rod and webos-internals.

    always worth donating to webos-internals. Keep up the amazing work.
  12. pml
    pml is offline
    pml's Avatar
    Posts
    47 Posts
    #72  
    As plenty of Germans ordered Pre3 phones via Palm Eurostore yesterday, there will soon be high demand in changing the keyboard layout from QWERTY to QWERTZ on the Pre3.

    What do you think, will it work a similar way here on WebOS 2.2?

    Other question: I guess modifying even the hardware layout, i.e. exchanging the keypad, is rather impossible?!

    Thanks in advance!
  13. pml
    pml is offline
    pml's Avatar
    Posts
    47 Posts
    #73  
    How about this solution, as it is not so demanding:
    see: forums.precentral.net/palm-pre-pre-plus/243338-how-easily-change-qwertz-qwerty-pre.html
    [I'm not allowed to post links yet...]

    The questions then would be:
    * Which keycodes to add for , , , , which are normally accessible via [Orange]+a, o, u, s
    * There should be the concept of startup-scripts, right? So the keycodes could be set somewhere there?!

    But I guess, these changes will be overwritten by an OTA upgrade (if there is any to come...), right?
  14.    #74  
    Quote Originally Posted by pml View Post
    As plenty of Germans ordered Pre3 phones via Palm Eurostore yesterday, there will soon be high demand in changing the keyboard layout from QWERTY to QWERTZ on the Pre3.

    What do you think, will it work a similar way here on WebOS 2.2?

    Other question: I guess modifying even the hardware layout, i.e. exchanging the keypad, is rather impossible?!

    Thanks in advance!
    I expect Meta-Doctor will be able to change the logical keyboard layout using the existing mechanism.

    I also expect the keyboard symbols are just a plastic overlay, easily removable and replaceable like on previous devices too.

    -- Rod
  15. #75  
    Quote Originally Posted by pml View Post
    How about this solution, as it is not so demanding:
    see: forums.precentral.net/palm-pre-pre-plus/243338-how-easily-change-qwertz-qwerty-pre.html
    [I'm not allowed to post links yet...]

    The questions then would be:
    * Which keycodes to add for , , , , which are normally accessible via [Orange]+a, o, u, s
    * There should be the concept of startup-scripts, right? So the keycodes could be set somewhere there?!

    But I guess, these changes will be overwritten by an OTA upgrade (if there is any to come...), right?
    I made a reply in the other thread regarding the non-metadoctor way.If you don't like to doctor now that shellscript i put there can save you a lot of work after luna restart. the umlauts are no prob sym&a works.
    http://forums.precentral.net/palm-pr...ml#post3106843
  16. #76  
    i know this is kinda offtopic, but is there a way to have a qwertz bluetooth keyboard not acting as qwertY on webos 2. it seems to work on the touchpad, but i don't know in which systemfiles to look for to change the layout in bluetooth mode. any hint rod? i did to find so much regarding this on webosinternals
    http://forums.precentral.net/palm-pr...rd-qwertz.html
  17. #77  
    Just followed these instructions and reflashed my AZERTY-Pre3 to QWERTY.
    Worked perfectly
    treacl likes this.
  18. #78  
    @grinsekatze just curious, but which instructions specifically? the one on the frontpage?
  19. #79  
    Yes, the ones on the frontpage... for the Pre3 that is:

    Code:
    1. `make DEVICE=pre3 CARRIER=wr unpack patch'
    2. modify `./build/pre3-p220manta-wr-2.2.0/webOS/mataray.xml'
    3. `make DEVICE=pre3 CARRIER=wr all pack'
    treacl likes this.
  20. #80  
    Quote Originally Posted by rwhitby View Post
    Leave out the 'all' from step 2.

    -- Rod
    Worked great on my QWERTZ Veer, thanks Rod! It's really easy using Meta-Doctor.
Page 4 of 4 FirstFirst 1234

Posting Permissions