Camelia, the Perl 6 bug

IRC log for #motoactv, 2012-04-06

| Channels | #motoactv index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:07 dproldan those backups are tar files,  can't flash them
00:26 lownox joined #motoactv
00:43 cmw joined #motoactv
01:00 christefano_ joined #motoactv
01:40 ds2 is this a stock X11 that uses /dev/fb0 only or one that knows about the pxa168fb?
01:40 ds2 blah
01:41 [mbm] wrong channel?
01:41 ds2 yes
01:41 ds2 sorry
01:42 bigbob joined #motoactv
01:45 bigbob Is there a reason to update to the newest version of firmware besides the golf feautures? Or should I stay a 4.55.78?
01:46 bigbob And Let me say thanks, the devs have made this watch into a badass little device
01:46 Quietlyawesome94 joined #motoactv
01:48 bdaman80 left #motoactv
02:04 bigbob joined #motoactv
02:29 [mbm] makes absolutely no difference, the root is not an exploit; doesn't depend on an old version
02:45 bigbob Ok thanks, I just got every running like I want it so I don't want to start again, I am not a golfer anyways
03:57 lownox joined #motoactv
04:00 Quietlyawesome94 joined #motoactv
04:26 christefano joined #motoactv
04:33 Quietlyawesome94 joined #motoactv
04:43 Quietlyawesome94 joined #motoactv
05:14 [mbm] hmm.
05:45 [mbm] huh, automatic brightness actually does work
05:57 christefano joined #motoactv
07:30 dproldan joined #motoactv
07:33 dproldan what command did you use to enable it?  when I set it in my launcher,  it does nothing.
07:34 dproldan bigbob: the only interesting thing in the newer version,  for me,  is the flick to turn on.
07:41 [mbm] dproldan: I didn't, was just poking around getevent and saw als
07:41 [mbm] and then noticed the screen dimmed when I was playing with the light
07:42 dproldan I can't see it dimming,  maybe i have a different setting somewhre
07:43 [mbm] there's a 1-2 second delay
07:43 [mbm] also just finished digging through the kernel to figure out exactly how the back key is mapped
07:45 dproldan what did you see?
07:48 [mbm] 0x01:158:232:187:10:10
07:49 dproldan yeah
07:49 [mbm] scancode 158, x:232 y:187 w:10 h:10
07:49 dproldan that's the virtualkeus file
07:49 [mbm] yep
07:49 dproldan keys
07:49 dproldan ok
07:49 [mbm] now to do some mangling
07:50 dproldan I though those were the values,  then the zero point is on the top-right of the device?
07:51 [mbm] would seem so
07:53 dproldan ahh,  makes sense,  I think the zero degress rotation for everything is usb connector down..
07:54 dproldan when I did a mirror to the fb,  it rotated upside-down
07:55 dproldan when you put it usb connector-down,  it is rightly a horizontal rotation
07:55 dproldan *horizontal mirror
08:02 [mbm] hmm changed the width to 255 and it still only works in the corner :/
08:06 [mbm] maybe I'll just set a new hotspot over the battery icon
08:07 dproldan_mob joined #motoactv
08:13 dproldan x and y values are the center!
08:13 dproldan The first key has a Linux scan code of 158 (KEY_BACK), centerX of 55, centerY of 835, width of 90 and height of 55.
08:13 dproldan maybe setting width to 255 is too much
08:15 dproldan add something like this ?  0x01:139:232:110:10:10
08:15 [mbm] thought of that and moved the center over
08:16 dproldan should put a menu key in the center
08:55 [mbm] http://pastebin.com/R4wr5nbs
09:02 dproldan yes?  vkey_map = [9e 00 e8 00 bb 00 0a 00 0a 00];
09:02 dproldan };
09:03 [mbm] yep.
09:03 [mbm] seeing what happens when I recompile it with a new map
09:04 dproldan looks good
09:04 dproldan more buttons :-)
09:04 [mbm] that's the plan
09:05 dproldan what about this? als_enabled = [00];
09:09 [mbm] 0x01:158:232:187:10:10:0x01:102:5:5:10:10
09:09 [mbm] hmm, that should map a home key at 0,0 but it doesn't seem to be working :/
09:12 dproldan that's next to the music button,  maybe there's no touch there because of the rgb led
09:13 dproldan did you modify the key layout?  maybe home button is not mapped anywhere
09:15 [mbm] home button is mapped
09:16 [mbm] think I'm too close to the edge though
09:17 DPRoldan_mob2 joined #motoactv
09:20 dproldan safest place is next to the back button,  maybe the system thinks 5,5 is ON the drawable area (on top of the display) but 232 is past it
09:21 dproldan check that,  102,232,100,10,10
09:21 [mbm] ok, let's try next to the back button
09:23 [mbm] 66 00 d8 00 bb 00 0a 00 0a 00
09:24 dproldan eh?  you changed X!,  you need to chnage Y
09:24 [mbm] 0x01:158:232:187:10:10:0x01:102:216:187:10:10
09:25 dproldan remember the rotation
09:25 [mbm] x isn't along the bottom?
09:26 dproldan nope,  Y is back button- light sensor
09:26 [mbm] 66 00 e8 00 ab 00 0a 00 0a 00 ?
09:27 dproldan yes
09:28 dproldan or better yet 66 00 e8 00 64 00 0a 00 0a 00
09:29 dproldan 10,10 is a really small spot,  if you put them too close together,  it could be difficult to tap it
09:29 [mbm] still only getting the back button
09:29 dproldan hmm
09:29 [mbm] and tried before of changing the width of the back button and nadda
09:30 [mbm] it really only likes that spot
09:30 [mbm] hmm .. let me try moving the back button and see if it still trigger at that spot
09:30 dproldan good idea
09:33 [mbm] 0x01:158:88:91:10:10:0x01:102:232:171:10:10
09:33 [mbm] back button disabled
09:36 dproldan just try to move the back button somewhere next to it self:  0x01:158:232:100:10:10
09:36 dproldan without home button for now
09:43 DPRoldan_mob joined #motoactv
09:45 [mbm] 0x01:158:120:91:10:80
09:45 dproldan that's on top of the display
09:47 [mbm] should overlap with the actual back button
09:50 dproldan from the blog:  A touch device should never clamp touch coordinates to the bounds of the active area. If a touch exits the active area, it should be reported as being outside of the active area, or it should not be reported at all.
09:52 dproldan oh, that's for when you go out of the active area
09:53 [mbm] 0x01:158:232:171:10:128
09:53 [mbm] if I'm reading that right it should be the entire bottom
09:53 dproldan yep, should
09:54 [mbm] isn't :/
09:55 dproldan :-(
09:55 [mbm] back button works but pretty much the same as stock :/
09:56 [mbm] didn't get extended
10:05 dproldan I could be wrong about X and Y ,  maybe 0x01:158:100:187:1028:10
10:07 * [mbm] tries 0x01:158:232:187:160:160
10:11 [mbm] still not extending the hotspot area :/
10:11 DPRoldan_mob2 joined #motoactv
10:11 17WAA1XW6 joined #motoactv
10:15 [mbm] anything else in devtree worth changing?
10:17 dproldan how are you checking the result?  getevent?
10:17 dproldan cat event4?
10:17 [mbm] the back key is pretty easy to spot, go into a menu and drop out with the back key
10:17 [mbm] but yeah, getevent can also be used
10:19 [mbm] touch seems to have a massive firmware
10:20 dproldan sometimes the TS controller is used for other things
10:21 dproldan maybe it's just a generic firmware full of unused options
10:24 dproldan another idea,  you always have tried to expand the buttons,  but when you expand them,  maybe the pressure value drops too much for the button to be triggered
10:27 [mbm] thinking the abs_params might be interesting
10:32 [mbm] hmm, nope, clamping there is 0-255
10:40 dproldan the pressure thing has nothing to do with clamping
10:53 christefano joined #motoactv
10:59 dproldan 0x01:158:100:187:10:10    or     0x01:158:232:100:10:10  should work   depending on the X and Y
13:18 dproldan <---  opened his device
13:35 cmw joined #motoactv
14:39 dproldan some more ICs in the MotoACTV:
14:39 dproldan 1 Cirrus Logic CS48L10-CWZ DSP - Audio 48L10CWZ, A0AI1114, TWN
14:39 dproldan Cirrus Logic CS42L73-CWZ Audio Codec - Ultra Low Power, Stereo, w/ Mono 1W Headphone Amplifier 42L73CWZ, B0AP1114, TWN
14:39 dproldan cypress TrueTouch  CP7457AT
14:40 dproldan Texas Instruments M430V294  ??
15:43 [mbm] last one is probably the msp430
15:44 dproldan oh, right
18:34 [mbm] hmm.
18:35 dproldan sup?
18:35 [mbm] bored.
18:36 dproldan here,  some more pictures : https://picasaweb.google.com/1​11067582235558199450/MotoACTV
18:38 [mbm] ooh
18:39 dproldan my memory module is toshiba,  bdaman80's is Sandisk,  don't know if his MA is 16GB
18:39 [mbm] reminds me, in bdman's video linked yesterday the back plate had a ribbon cable on it
18:40 [mbm] couldn't see why in the video
18:40 dproldan that's for the audio jack
18:41 [mbm] ah, yeah just figured that out looking at those photos
18:41 [mbm] btw, your photos?
18:41 dproldan yep
18:42 dproldan <--  can only wait a few days before opening the gadgets
18:43 [mbm] lol
18:43 [mbm] I still want to know who makes the screen
18:43 dproldan sorry,  no way to tell from looking at it
18:45 [mbm] did you at least get pictures of all the markings?
18:46 dproldan on the display?  no,  what you see in the pictures
18:49 dproldan any idea on how to simulate a headset plug-in?
18:49 dproldan <6>[17397.488372] cpcap spi1.0: New headset state: 0
18:49 dproldan <6>[17397.488891] cpcap spi1.0: Headset key event: old=0, new=0
18:50 dproldan or
18:50 dproldan 03-08 10:53:20.264  1201  1214 V HeadsetObserver: Intent.ACTION_HEADSET_PLUG: state: 0 name: No Device mic: 0
18:50 dproldan that was "out"
18:50 dproldan this is "in": 03-08 10:53:09.366  1201  1214 V HeadsetObserver: Intent.ACTION_HEADSET_PLUG: state: 1 name: Headset without mic mic: 0
18:51 bigbob joined #motoactv
18:51 dproldan some way to simulate that from the shell?
19:31 christefano joined #motoactv
19:44 CEnnis91|Mobile joined #motoactv
21:15 christefano joined #motoactv
22:48 Quietlyawesome94 joined #motoactv
23:43 Quietlyawesome94 joined #motoactv

| Channels | #motoactv index | Today | | Search | Google Search | Plain-Text | summary