**** BEGIN LOGGING AT Mon Feb 20 03:00:00 2012 Feb 20 03:06:19 (Disclaimer: I work there, but don't have anything noteworthy to say ... just started using preware for the first time and thought it was funny to see this channel on an irc network I've been on since the dawn of time .. reason I was asking about palm employees is that I'd imagine most of the boys on the other side of the house would be the types to hang out in here) Feb 20 03:11:03 Kysh: who are you ? Feb 20 03:12:46 I'm Kysh. ^.^ Feb 20 03:12:56 Is this a trick question? ~.^ Feb 20 03:28:25 bhuey, foxy, apparently :P Feb 20 03:36:21 bhuey === caterpillar, Kysh === Alice Feb 20 03:36:33 wrea: ? Feb 20 03:37:04 Kysh, your whois has your real name as foxy Feb 20 03:37:23 Oh. Feb 20 03:37:24 yes Feb 20 03:37:28 That's correct :> Feb 20 06:57:23 Hi, try to understand some basic conceptions here. a few questions on PDK. Feb 20 06:58:07 Does a PDK app has any relationship with NPAPI plugin? does the PDL built upon NPAPI ? Feb 20 06:59:18 Seems to me, in one way, it can run as a standalone app. it don't looks like a npapi plugin. While in hybrid app, it works as a embed object, which looks pretty like a npapi plugin... Feb 20 07:02:59 So, is the palm port webkit implement its own interface for plugin? Feb 20 07:03:25 with those PDL_callJS staff Feb 20 07:37:05 Hello Feb 20 07:38:09 Anyone alive in here familiar with the HP Touchpad? Feb 20 07:41:15 depends on how familiar you need - I'm not one of the experts here, but I'll help if I can? Feb 20 07:42:14 thanks :) Feb 20 07:42:40 I have one here that belongs to a friend. He complained it stopped charging then shut down when the battery got too low Feb 20 07:42:59 now all it does it come up with a battery icon with a ? mark inside Feb 20 07:43:36 I can get it to load as 2 diff usb devices. a qualcomm loader and a palm device. but can't get into the proper usb recovery mode for webos doctor to detect it Feb 20 07:45:13 I've charged it fully (as far as I can tell). let it sit on the screen with the battery icon all day till it powered down Feb 20 07:46:41 I assume you tried the forced reboot by holding down the home button & power button simultaneously for about 10 seconds? Feb 20 07:46:50 did the 20-30 second home+ power more times than I can remember.. it just keeps commin back to that battery screen Feb 20 07:46:59 ah Feb 20 07:47:17 and it's plugged in with the doctor running when you reboot it? Feb 20 07:47:58 yes Feb 20 07:48:32 if it's not in either that qualcomm loader or palm mode it doesn't detect at all in windows or mac os Feb 20 07:49:06 I found drivers for the qualcomm dloader device but haven't found a driver for when it comes up as simply "Palm" Feb 20 07:49:32 assuming it wouldn't much matter for webos doctor anyway since it's likely not the device it's searching for Feb 20 07:49:45 this isn't a fix, but I'd suggest installing novacom & starting the novacom server, then doing the forced restart while plugged in and seeing what the output is Feb 20 07:50:00 let me get you a link Feb 20 07:50:08 I have those tools installed Feb 20 07:50:25 downloaded and installed webOS sdk etc Feb 20 07:50:49 I didn't figure novacom would be able to communicate with the touchpad since webos doctor doesn't see it Feb 20 07:51:27 well, novacomd will at least tell you if it's being detected? there are things that it can do that the doctor doesn't Feb 20 07:53:33 ran novacom.exe from commandline Feb 20 07:53:47 just says "unable to find device" Feb 20 07:53:59 bother - it just occurred to me that it may be harder to see the debugging output. I'm running linux, so if I run novacomd separately it'll give me that output. Feb 20 07:54:09 ah Feb 20 07:54:43 and on reboot while it's running you see no messages at all? Feb 20 07:55:27 it didn't leave me in a console etc of any sort Feb 20 07:55:38 just gave that error message and dropped me back to the command prompt Feb 20 07:55:47 is it novacom.exe I should be running? Feb 20 07:56:27 I've flashed/rooted a number of android phones etc.. kinda why I ended up with this thing Feb 20 07:56:36 assuming novacom is kinda like adb Feb 20 07:57:17 but I'm completely lost when it comes to webos devices Feb 20 07:57:29 this touchpad is the first one I've had to mess with Feb 20 07:58:07 I just want to double-check - you rebooted and held down the volume up, right? Feb 20 07:58:28 right Feb 20 07:58:31 that sucks, generally it's been the least frustrating to deal with of anything I've had to flash or root Feb 20 07:58:37 that toggles the "Palm" device Feb 20 07:58:49 but I don't have a driver for that Feb 20 07:59:04 the novacom driver installer doesn't cover it Feb 20 07:59:34 I'm assuming the usb recovery mode is an entirely diff thing than what I'm gettin now Feb 20 07:59:57 everything I've read says the tpad should come up with a USB symbol on the screen when it's in usb recovery Feb 20 08:00:26 novacom I'm thinking needs it like that to "see" it Feb 20 08:01:03 I've read about this happening with other palm devices like the pre Feb 20 08:01:11 there's an even lower-level of connection than the default recovery, but I'm not sure how exactly it differs between the different webos devices, so I should probably bow out Feb 20 08:01:16 where it gets stuck on the battery icon with the question mark Feb 20 08:01:31 but to fix those they say to pull the battery. get it into usb recovery then pop the battery back in Feb 20 08:01:38 urgh, yeah Feb 20 08:01:42 thats obviously not a easy method with this ;) Feb 20 08:01:46 I got an error vaguely like that at one point, but I don't think it was the same thing and rebooting holding power & up did it Feb 20 08:01:50 yes, not really an option Feb 20 08:01:55 sorry I wasted your time Feb 20 08:02:08 you didn't at all Feb 20 08:02:15 I appreciate the help Feb 20 08:03:00 I'd try and figure out more, but I have access to neither a windows nor a mac machine and I'm guessing at the differences Feb 20 08:03:10 would you have any idea where I could get that "Palm" driver? Feb 20 08:03:28 it's not part of the novacom driver kit Feb 20 08:04:13 neither was the qualcomm device driver. I stumbled across that in a forum somewhere but haven't lucked into the proper driver for the VolUP+Power device Feb 20 08:05:07 from what I've read it's supposed to go directly to the usb icon on the screen with volup+power but it gives me a black screen with that palm device only Feb 20 08:06:19 the only way it will display anything on the screen is if I unplug the usb and do home+power reset. I get the battery + ? icon. with it plugged into usb the screen stays black on reset and only the charging lights work Feb 20 08:07:25 I guess I could install the sdk on the mac. it's pretty much the same as linux as far as the tools and commands Feb 20 08:07:40 see if it can detect it there Feb 20 08:08:29 might be useful, if only because the command line tools might give more output? Feb 20 08:08:57 definitely lurk in the channel, though - someone more knowledgeable is likely to get back to you Feb 20 08:09:30 will do :) Feb 20 08:09:47 I'll let you know how the mac side with novacom works Feb 20 08:10:20 I only tried using webos doctor with it. it does pick up the palm device that my win7 comp doesn't have the drivers for Feb 20 08:10:43 so maybe it'll be "good enough" for novacom Feb 20 08:11:06 at least the webos doctor will give you some debugging output if you run the jar from the command line? I hate 100% gui stuff Feb 20 08:11:43 yeah I didn't try that Feb 20 08:12:02 I only used the standard gui and sat there staring at the greyed out next button Feb 20 08:12:10 when it's tryin to find the tpad Feb 20 08:12:21 I am going to confidently project that it won't do anything useful, thus increasing the chance I'll be proved wrong and you'll get something out of it Feb 20 08:12:24 ah Feb 20 08:12:33 I understand Feb 20 08:12:43 I'm willing to try about anything though Feb 20 08:13:11 been messing with this a couple hours now. Like to get it fixed after investing some time Feb 20 08:13:16 on a mission now :P Feb 20 08:13:54 it's only a couple months old and he tried exchanging it where he bought it first Feb 20 08:14:07 and even contacted HP.. he didn't have any luck with their support Feb 20 08:15:40 I could crack open the case and probably unplug the battery but in the event it's actually a hardware failure and I can't reflash it to fix Feb 20 08:15:53 I'd rather not void the warranty Feb 20 08:22:43 I definitely wouldn't do that yet - there are options between the webos doctor level and that? I'm just not familiar enough with them to help. I tend to stick to poking at luna & digging through the boot & app files Feb 20 08:24:47 yeah I'm sure there is some way to either reload the first stage boot loader Feb 20 08:25:08 or force it to ignore that battery error and go into the normal usb recovery Feb 20 08:25:26 on mac OS I started novacomd then ran novacom Feb 20 08:25:43 got the same thing as windows. "unable to find device" Feb 20 08:28:16 on the mac that usb device named palm has the manufacture name "bootie" Feb 20 08:28:31 bootie is the low-level boot loader they use Feb 20 08:28:38 so I'm figuring thats a device for dev level boot loader coding Feb 20 08:29:52 I haven't seen any info at all in my searching relating to working with that Feb 20 08:30:08 like writing a new boot loader etc Feb 20 08:30:26 most of what I read is that the devices are fairly unbrickable :) Feb 20 08:30:38 and this one seems to have essentially managed it itself Feb 20 08:30:55 your friend is talented Feb 20 08:31:05 it still responds but not enough to get the HP recovery tools to do their job Feb 20 08:31:31 yeah. I'm not sure what happened to set it all off Feb 20 08:31:47 he's not a tech user at all.. knows enough to plug it in Feb 20 08:32:17 so if a flash went bad it would have been during a normal auto update or something Feb 20 08:32:40 he wouldn't have been doing anything like messing with rooting it etc Feb 20 08:33:11 now me on the other hand Feb 20 08:33:27 if this were mine and it died it would most likely be my doing Feb 20 08:33:34 putting ICS or something on it Feb 20 08:34:13 I got it after the fact so I didn't get to see what caused the problem Feb 20 08:34:38 other than that battery error blocking usb recovery mode being quite a bad design choice Feb 20 08:35:22 looks like a decent device Feb 20 09:03:17 I do kind of wonder if that error symbol can get triggered by things other than low battery Feb 20 09:03:39 and yeah, they're pretty nice and generally aren't this much of a pain to recover. Feb 20 09:04:46 well it's not the low battery icon Feb 20 09:04:56 that one is a battery with a red line at the bottom Feb 20 09:05:09 oh! yeah, I know the both the ones you mean. Feb 20 09:05:26 for that matter I've used the webOS Meta-Doctor to put my semi-destroyed original Pre into dev mode, get it on the network, etc. after it took a four story fall onto marble Feb 20 09:05:37 it's the one with the ? in it.. labeled nobat.tga in the webos doctor jar file Feb 20 09:06:21 I extracted it and grabbed what I think is the bootie bin file and the recovery uimage Feb 20 09:06:44 noticed tga files that showed the various startup screens and errors Feb 20 09:07:17 obviously there is a battery since it charges and will run off it for hours Feb 20 09:07:25 but it assumes it's mia Feb 20 09:07:53 I've read that it's not an uncommon thing for webos devices to get confused Feb 20 09:08:12 and the chip that reads the battery state needs reset/flashed Feb 20 09:08:40 but to get to that point you have to pull the battery to get it into usb recovery I think.. if I understood the directions right anyway Feb 20 09:08:59 then after it's in usb recovery you pop the battery back in before the webos doctor update Feb 20 09:09:26 those instructions are for a webos phone of course Feb 20 09:09:31 easy to do that Feb 20 09:16:12 I'm betting you could hose it even farther with: https://github.com/jcsullins/qdl-upload Feb 20 09:16:21 but I suspect that's kind of the opposite of what you want to do Feb 20 09:16:37 (and yes, that was not a serious suggestion) Feb 20 09:18:16 also this thread seems to have a little useful info, but mostly of the "hope you've got JTAG kit laying around" variety: http://forums.webosnation.com/hp-touchpad/310969-battery-icon-w-question-mark-researching.html Feb 20 09:21:28 I downloaded and compiled a omap boot tool that was made for the palm pre Feb 20 09:21:49 it's running and I have the touchpad started in bootie recovery mode Feb 20 09:21:56 but it's not finding it Feb 20 09:22:16 I saw something about having to edit the device ID in source for another phone Feb 20 09:22:27 so I will probably have to do that for it to find the touchpad Feb 20 09:23:10 but it's supposed to be able to manually load bootie into recovery mode by sending the bin over usb Feb 20 09:25:17 looking at those pages you linked Feb 20 09:25:33 see that one forum post sounds about right Feb 20 09:25:42 I really doubt it's an actual bad battery Feb 20 09:25:48 I think the touchpad is just confused Feb 20 09:26:02 he actually had 2 and opened the good one up Feb 20 09:26:12 swapped the battery and still had the problem Feb 20 09:26:44 this guy wasn't attempting to install any custom roms Feb 20 09:27:17 but I'd imagine that error can occur from a bad flash of any type Feb 20 09:27:34 even like being powered down mid webos update etc Feb 20 09:28:32 one thing is for sure.. he broke this one pretty good :) Feb 20 09:28:54 by the time I get it working I should at least have a good enough toolset installed to fix almost any problem on them Feb 20 09:53:53 Amperage: nieve: the qdl-upload program does not work Feb 20 09:54:52 what is that for anyway? Feb 20 09:55:19 it's was attempt to create program to load stuff from QDL mode Feb 20 09:55:50 I ran into a dead end with the omap3 boot tool. edited the vendor/device ID and recompiled. said it found the touchpad but couldn't get the asic ID Feb 20 09:56:21 so whatever method was used on the palm pre must not be compatible with the HP touchpad Feb 20 09:56:43 palm pre is not based on qualcom chipset is it? Feb 20 09:57:32 no. just checked. it's a TI Feb 20 09:58:10 these tools are talking directly to CPU, so VERY CPU specific Feb 20 09:58:26 yeah I'm just tryin everything :/ Feb 20 09:58:31 was following http://www.webos-internals.org/wiki/Last_Resort_Emergency_BootLoader_Recovery Feb 20 09:59:07 seems a shame that battery error stops even recovery mode from loading Feb 20 09:59:13 does novaterm connect to it at all? Feb 20 09:59:21 no. doesn't get that far :( Feb 20 09:59:54 I can only get the qualcomm serial device and a Palm device with the manufacture "bootie" to show up Feb 20 10:00:33 what do you do to get it in the "bootie" mode? Feb 20 10:00:38 when I do the home+power reset it goes straight to that battery question mark screen Feb 20 10:01:21 hold home + power + voldown to get into qualcomm mode then do home + power + volup twice Feb 20 10:01:43 I can't get it directly into the palm/bootie mode without putting it in qualcomm mode first Feb 20 10:01:45 jcsullins: I probably shouldn't even have joked about it - I certainly didn't think it was at a running stage. Feb 20 10:02:33 hmm. when it's in the bootie mode, have you tried connecting w/ novaterm? Feb 20 10:02:52 but if I first start it with the qualcomm usb device showing up then do the home+power+volup twice the palm device shows up. vendor ID 8030 dev id 8070 Feb 20 10:03:12 no i haven't tried novaterm yet Feb 20 10:03:25 take me one sec Feb 20 10:03:32 ok, brb Feb 20 10:06:21 novaterm gives me the same "unable to find device" error that novacom does Feb 20 10:07:57 hmm, so what happens when you hold Power+Home for ~20 secs? does it give the question mark inside battery? Feb 20 10:09:06 yeah if its unplugged Feb 20 10:09:30 it does something different when it's plugged? Feb 20 10:09:33 if I have the usb cable plugged in it just goes black screen with the cycling home button lights Feb 20 10:09:57 unplugged it goes directly to the battery icon screen with the question mark Feb 20 10:10:20 but it will sit on that screen for hours till the battery goes critical Feb 20 10:10:31 oh, really? have you connected it to AC cable and let it sit for few hours? (the cycling home button lights means it's trying to charge) Feb 20 10:10:41 then occasionally when I home+power it will briefly flash the low batt icon before going to the ? Feb 20 10:11:11 yeah I've left it charge for ages on the original adapter. 3 other usb adapters. a couple comps etc Feb 20 10:11:39 it actually takes a charge cause I've run it so dead it would only show the battery icon for 2-3 seconds before powering back down Feb 20 10:11:56 if I plug it in for a couple hours it will hold that screen for a long time Feb 20 10:12:16 so the battery is charging/discharging what seems to be normally Feb 20 10:12:55 course the touchpad isn't convinced :) Feb 20 10:13:25 have you confirmed somehow that the HP AC charger is working properly? Feb 20 10:14:02 yeah I charged my droidX with it for 10 min or so and battery level went up ~5% Feb 20 10:14:39 ok, how long have you let it sit on the HP AC charger without taking it off? Feb 20 10:15:36 all night Feb 20 10:15:47 at least 9 hours Feb 20 10:16:10 when he first gave it to me I couldn't get anything on the screen. was completely dead Feb 20 10:16:27 was back of touchpad was at all when you took it off? Feb 20 10:16:29 I plugged it in for about 20 minutes to the HP charger and started gettin the battery with the ? Feb 20 10:16:37 was back of touchpad warm at all when you took it off? Feb 20 10:16:44 so I assumed it might just need charged more and left it plugged in til I woke up Feb 20 10:16:55 no but the charger was warm Feb 20 10:17:17 when i took it back off it had been plugged in for 9 hours or so Feb 20 10:17:32 most likely if it was warm during charging it topped off and had time to cool before I woke up Feb 20 10:17:55 might try leaving it on (HP AC) charger for like 24-48 hrs Feb 20 10:19:07 I've heard of it taking that long sometimes to "kick it to life" when the battery gets dead Feb 20 10:19:27 I think it's actually detecting the battery level Feb 20 10:19:38 but then immediately after deciding something else is wrong Feb 20 10:19:43 and it stops booting Feb 20 10:20:12 cause like I said a bit ago. if I leave it sit on that battery icon a while.. 4-5 hours it'll power down Feb 20 10:20:33 if you plug into HP AC charger and hold Power+Home for ~20 secs, does it give the blinking home? Feb 20 10:20:39 and if I keep doing home+power at that point it'll flash the low battery icon for literally like 1/4 second before the ? icon Feb 20 10:20:57 if I them plug it in to charge for a while I don't get the low battery icon before the ? icon anymore Feb 20 10:21:07 yeah Feb 20 10:21:15 the strange thing though Feb 20 10:21:29 if I plug it in to charge and do the home+power reset Feb 20 10:21:43 after a few seconds the home button charging lights start flashing Feb 20 10:21:46 black screen Feb 20 10:21:56 then if I unplug it from the charger Feb 20 10:22:03 the lights still continue to flash Feb 20 10:22:14 until I do another home+power reset Feb 20 10:22:48 I'm not sure if that's normal behavior but i thought it seemed strange Feb 20 10:23:22 yeah, that doesn't really surprise me. I think it programs the chip that controls the leds to do that then "sleep/charges" Feb 20 10:24:06 what was it doing after you left in on the AC charger for 9 hours? Feb 20 10:24:21 I did notice also that if I leave it plugged in to charge for a while.. i didn't watch it the whole time Feb 20 10:24:31 but even though the screen starts out black Feb 20 10:24:47 eventually the screen will turn on and show the battery ? icon Feb 20 10:24:56 but it takes a while.. probably 30+min Feb 20 10:25:16 if it's not plugged in the screen shows up right away Feb 20 10:25:43 when I woke up after the ~9hour charge it was sitting there with the battery screen Feb 20 10:25:59 the battery screen? the one with the ? mark? Feb 20 10:26:04 yeah Feb 20 10:26:10 that's the only one it's ever stopped on Feb 20 10:26:31 it only flashes the low battery icon briefly when it's powering up on an actual low charge Feb 20 10:26:42 but always ends up on the ? icon Feb 20 10:26:58 I've never managed to get it to the usb icon Feb 20 10:27:23 I'm assuming if I can get it there a webos doctor flash might fix the goofy battery issue Feb 20 10:27:58 might be the battery really is fried... any reason HP support can't be called? Feb 20 10:28:34 he tried. dunno exactly who he talked to but he said he was getting the run around by HP support Feb 20 10:28:58 so he tried just returning it to the retailer and they wouldn't exchange it either Feb 20 10:29:02 it's ~2months old Feb 20 10:29:46 the battery actually holds a charge.. but I know there is firmware and some chips built into the battery Feb 20 10:29:52 from what you've told me, I'd think they'd fairly quickly send you (him) a box to return in for repair... Feb 20 10:29:56 that may be reporting wrong Feb 20 10:30:03 yeah, that might be Feb 20 10:30:35 I had a problem last year with a lion upgrade that killed my macbook pro battery Feb 20 10:30:46 really common issue. apple of course denies it Feb 20 10:31:06 even though tons of them just happened to have bad batteries after upgrading from snow leo to lion :) Feb 20 10:31:33 something was corrupting the battery firmware basically making them a paperweight Feb 20 10:31:59 I would suggest you call HP support and tell them what you told me Feb 20 10:32:00 the thing that makes me wonder though about the battery Feb 20 10:32:31 was the link nieve posted earlier Feb 20 10:32:55 guy I think pulled the plug on a webos update Feb 20 10:33:07 and ended up with the ? battery issue Feb 20 10:33:25 he tried pulling the bat from a known good touchpad and still had the same Feb 20 10:34:41 later in the same post somebody claimed that the chip responsible for managing charging etc most likely gets flashed during webos updates Feb 20 10:35:20 PmA6Updater performs the flash Feb 20 10:35:44 A6 reports battery stats, yes Feb 20 10:35:56 course without novaterm and gaining access to the device Feb 20 10:36:04 I can't run that to force a reflash Feb 20 10:36:40 but considering that it's possible a bad flash could cause that if the charging system flash got messed up Feb 20 10:37:19 I wish I saw what it was doing before it powered off and failed to come back up Feb 20 10:37:51 I got it with the story about sucky support and he said "it's busted.. please fix" :P Feb 20 10:38:46 what I don't understand is even if the battery is completely MIA Feb 20 10:39:04 why they would design a system you couldn't at least gain filesystem access to Feb 20 10:40:36 Amperage: I may have something to try ... what OS do you have on PC? (hopes linux) Feb 20 10:41:02 I have win7 and mac os Feb 20 10:41:11 both with sdk and nova tools etc installed Feb 20 10:41:38 on the mac side it's pretty much the same as linux.. diff paths to the tools Feb 20 10:41:48 but the commands and output look identical Feb 20 10:42:26 ok, macos might work Feb 20 10:42:35 if need be I can install linux on vmware or something Feb 20 10:42:49 if macos command prompt doesn't cooperate Feb 20 10:43:23 when you get the 8030/8070 vid/pid ... can you get more info on what it's reporting ... I think that's a DFU mode, but not sure Feb 20 10:44:04 let me plug back into the macbook Feb 20 10:46:28 ok got it back up and detecting the "Palm" device Feb 20 10:47:23 it's reported as the vendor/device ID you listed. manufacture is listed as bootie Feb 20 10:47:29 version 10.00 Feb 20 10:48:01 if you have a shell command to dump more device info lemme know Feb 20 10:48:05 can give it a shot Feb 20 10:48:16 folks Feb 20 10:48:25 but system info only gives basic info Feb 20 10:48:45 Amperage: you have a "lsusb" command in macos? Feb 20 10:49:16 not found Feb 20 10:49:33 so it's not installed anyway. lemme see if it's avail for darwin Feb 20 10:50:59 I haven't use a mac heavily for a while, but isn't there a system_profiler command that'll do it? Feb 20 10:51:37 yeah Feb 20 10:51:42 i just did it Feb 20 10:52:04 system_profiler SPUSBDataType Feb 20 10:52:14 supposed to be the equiv of lsusb Feb 20 10:52:29 but it just gives me the same info that the gui profiler lists Feb 20 10:52:31 ah, thanks - now I can find that in my irc logs if I ever get another mac Feb 20 10:52:34 *sigh* Feb 20 10:53:12 just ran across "ioreg -p IOUSB -l" output that looks more extensive Feb 20 10:53:56 I should have just asked my gf if I could snag her mac earlier :P Feb 20 10:54:03 yeah. more detailed info on that Feb 20 10:54:09 even in a handy tree view :) Feb 20 10:54:18 shows how they are connected to hubs etc Feb 20 10:55:54 jcsullins: did you need more detailed info on the device? Feb 20 10:56:22 does the more detailed info say anything about "DFU" ? Feb 20 10:56:45 or "Device Firmware Update" ? Feb 20 10:57:16 nope. just more info on protocols etc Feb 20 10:58:03 hmm, ok, well I'm almost certain that that vid/pid you mentioned *IS* for DFU.. (b/c I just put mine in it) Feb 20 10:58:12 the friendly names for "USB Product Name" is Palm. "USB Vendor Name" is bootie Feb 20 10:58:28 so at least it's a device dealing with the boot loader Feb 20 10:58:40 so I might have something to help, but it'd be a day or two before I could get it ready ... Feb 20 10:58:48 dunno if it's linked to the boot.bin stage that loads bootie. or bootie itself Feb 20 10:59:05 I'm figuring the latter Feb 20 10:59:28 technically, there is two booties -- the one that that vid/pid is referring to is the first one Feb 20 11:00:24 if you put yours in qualcomm mode Feb 20 11:00:35 what is the device id Feb 20 11:00:42 I read somewhere that there is 2 Feb 20 11:01:02 one is used for normal operation and one is some sort of "bricked" fallback Feb 20 11:02:19 this one comes up vendor ID 9008 Feb 20 11:02:47 for the QHSUSB_DLOAD Feb 20 11:03:43 that *is* the "bricked fallback", but you can enter it by doing Power+VolUp IIRC Feb 20 11:04:10 btw, what was the product id? Feb 20 11:04:32 on the palm device of qualcomm? Feb 20 11:04:36 or* Feb 20 11:04:53 qualcom (the one w/ QHUSB_DLOAD) Feb 20 11:05:11 05c6 Feb 20 11:05:59 that's just a usb-> serial inferface tho right? Feb 20 11:06:06 for low level junk Feb 20 11:06:30 well, little more complicated than usb->serial, I think Feb 20 11:06:51 most of the devices I've messed with like that Feb 20 11:07:00 it's kinda essentially a poor man's jtag Feb 20 11:07:06 but it is the mode where you talk directly to the CPU for "de-bricking" ... but there aren't any public programs to do so (only HP/Qualcom has) Feb 20 11:07:38 I've had to write directly to the serial interface on some dell alienware comps Feb 20 11:08:02 cause a poorly mannered firmware update was bricking the lighting chips Feb 20 11:08:49 yeah I'm not sure that would help with this anyway Feb 20 11:09:02 I think this problem is a bit higher level Feb 20 11:09:09 Amperage: I may be able to fix a version of moboot that will allow you to boot, but it'd be a couple of days ... Feb 20 11:09:24 since you said it has 2 booties. the first is where I'm stuck Feb 20 11:09:44 and it stops before it hands execution off to the 2nd that is responsible for entering usb recovery mode right? Feb 20 11:09:47 a couple of days is faster than HP service would do turnaround Feb 20 11:10:01 I don't want you to go outta your way Feb 20 11:10:08 unless you are simply curious Feb 20 11:10:40 some changes I've been planning on implementing anyway Feb 20 11:10:56 not saying it will fix the problem -- would still suggest calling HP Feb 20 11:11:11 yeah i could mention it to him again Feb 20 11:11:36 but he didn't seem all too happy with his previous call to support Feb 20 11:11:53 which is how I ended up with it ;) Feb 20 11:12:17 I don't mind toying around with stuff. I'm the curious type Feb 20 11:12:22 might have just got a bad support person -- happens Feb 20 11:12:28 and perhaps the info could be used later Feb 20 11:13:20 but I have a whole ton of ps3 and xboxs piled up here. I would have liked a quick volup+power and 30 minutes watching webos doctor :) Feb 20 11:14:00 oh well.. what can ya do eh? :) Feb 20 11:14:47 oh the subject of moboot Feb 20 11:15:06 was read some about that in a android guide Feb 20 11:15:11 reading* Feb 20 11:15:38 that doesn't normally get flashed like this does it? Feb 20 11:15:55 think it was using some dev mode with webos itself booted Feb 20 11:17:09 moboot is typically used as a chain-loaded bootloader (bootie loads moboot) that gives menu and allows booting into multiple OSes (webOS, Android, etc.) Feb 20 11:17:49 yeah i just found where I saw it Feb 20 11:17:59 was installed as part of acme installer Feb 20 11:18:10 however, with some mods, I should be able to get it to load via the DFU mode to allow bypassing the second-stage bootie.... (I wrote moboot, btw) Feb 20 11:18:48 nice Feb 20 11:19:03 I do some coding myself. iphone dev etc Feb 20 11:19:13 I don't dabble much with low levels stuff though Feb 20 11:20:04 I do miss the old dos C days Feb 20 11:20:16 before bloated APIs took over Feb 20 11:21:49 it's much faster to use stuff like cocoa but seeing a app that can be done in ASM and a 2k memory footprint Feb 20 11:21:57 gobble up 30mb Feb 20 11:22:40 makes the me from 1985 want to jump forward in time and punch myself for being lazy :) Feb 20 11:23:04 heh, yeah .. coding low-level a different ballgame Feb 20 11:23:33 Amperage: you stay on here much? Feb 20 11:23:46 first time I'm afraid Feb 20 11:23:55 this touchpad is my first run in with a webos device Feb 20 11:24:11 I got a tough one outta the gate it seems ;) Feb 20 11:24:40 I can stop back whenever you like though Feb 20 11:24:40 ah, ok ... was gonna say I'd just let you know when I have mods for moboot... but if not on here, guess I can't do that ... :) Feb 20 11:25:36 or if you use gtalk etc you could just give me a shout there Feb 20 11:27:15 you seem to prefer the linux side of things Feb 20 11:27:39 I'm not a big fan of windows myself but I'm a gamer Feb 20 11:27:43 so.. yeah Feb 20 11:27:52 Amperage: how about you PM me your email, and I'll email you? Feb 20 11:27:59 spend most of my time in windows Feb 20 11:28:20 do you know of any working win7 64 drivers for that palm "bootie" device? Feb 20 11:29:48 no Feb 20 11:30:10 most likely will need to use a dfutool in macos, but first will need to modify moboot Feb 20 15:08:24 hi Feb 20 18:11:21 Hey all. I'm at it again. Checking out how Kubuntu Active (Plasma Active 2 rebased on Ubuntu) will behave on the TouchPad. Along the way I've done a few interesting things that might be useful to other power users (upgraded the distro, installed some support packages, etc) that I think belongs on the ubuntu chroot page. I was going to add it, but I don't have access. Feb 20 18:11:35 If I write it up, is there somebody I can submit it to to add it to the page? Feb 20 18:35:45 It's a wiki... Feb 20 18:37:29 Cerealklr, rwhitby can grant you access to edit the wiki Feb 20 18:38:19 That would be fine too. I just assumed since it was locked down it'd be easier to work through an intermediary. Feb 20 18:49:34 easier for who? Feb 20 18:50:16 the status quo, I suppose Feb 20 19:09:31 Cerealklr: my point was only that it might be easier to get you setup with an account than it would for someone to take the time to edit the wki Feb 20 19:12:12 Fair enough. I already have an account (I've contributed in the past) Feb 20 19:12:16 but that page is locked. Feb 20 19:25:40 which page Feb 20 19:25:58 the locking down of edit perms happened somewhat more recently Feb 20 20:36:12