Camelia, the Perl 6 bug

IRC log for #motoactv, 2012-04-05

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

All times shown according to UTC.

Time Nick Message
00:01 dproldan I started over again from the beginning a few hours ago,  just now I've finished building CM7 again.   I didn't clone any "similar product",  just followed AOSP guide
00:01 dproldan I have 15 or 16 files total in my device and vendor tree now,  the previous tries  some hundreds
00:41 lownox joined #motoactv
00:55 Guest1884 joined #motoactv
02:13 RussellAlan joined #motoactv
02:14 lownox joined #motoactv
02:14 lownox hey guys
02:14 lownox does the modified 5.6 boot img work with the 6.6 update?
02:14 lownox just thought i would ask before I tried
02:14 RussellAlan hey guys need some help... flashed ClearDroid 1.0 then directly flashed 1.1 now stuck in bootloop
02:14 RussellAlan what are the hard keys for cwm?
02:15 lownox there aren't any to my knowledge
02:15 RussellAlan how do i get out of bootloop?
02:15 lownox hold start and power until device shuts off
02:15 lownox then you can go back into fastboot
02:15 lownox and flash again
02:16 lownox rom will still be on your sdcard
02:16 lownox once you root you can adb reboot recovery and flash the rom again
02:16 lownox brb
02:16 RussellAlan flash cwm again?
02:16 RussellAlan gotcha
02:17 [mbm] lownox: yeah, same boot image
02:19 [mbm] motorola version numbers are annoying; the download for the latest is called 5.6.12, and yet on the device it shows up as 1.6.6
02:20 [mbm] at any rate, I went to all the trouble of obtaining a stock boot image from the latest only to discover nothing had actually changed
02:26 bigbob joined #motoactv
02:27 RussellAlan joined #motoactv
02:28 RussellAlan wait
02:28 RussellAlan how can i flash recovery infastboot?
02:28 RussellAlan well
02:28 RussellAlan fastboot flash recovery recovery.img
02:29 RussellAlan i flashed it
02:30 RussellAlan but now how do i get into recovery?
02:32 RussellAlan [mdm] help meh
02:32 RussellAlan =D
02:37 RussellAlan Can someone help me get into cwm
02:39 RussellAlan rebooted hoping to be in cwm, but still at bootloop
02:45 RussellAlan joined #motoactv
03:05 lownox mbm: thanks
03:06 lownox I think it is time to just load a bunch of crap on this device.
03:06 lownox just because
06:06 JohnDoe_ joined #motoactv
06:13 ds2 has anyone looked into BLE sensors available? like a compass, etc?
06:15 christefano joined #motoactv
06:42 christefano joined #motoactv
06:42 christefano joined #motoactv
06:51 [mbm] ds2: nope; started poking at the msp430 though
06:59 ds2 [mbm]: have you tried the flashing tools?
07:06 [mbm] the "msp430" binary? yep.
07:17 ds2 so we can load our own code onto it?
07:54 [mbm] I suppose if you knew how to program it
07:55 [mbm] I've been looking at it in the more abstract black box; poke at it and see if I can figure out what the outputs mean
09:33 dproldan is this link working?  https://picasaweb.google.com/1110675822355581​99450/MotoACTVMicrophone?authuser=0&authk​ey=Gv1sRgCOOV7ZiHxM6P2gE&feat=directlink
09:34 dproldan or this one better : https://picasaweb.google.com/111067582235558199450​/MotoACTVMicrophone?authuser=0&feat=directlink
14:04 dproldan joined #motoactv
15:05 cmw joined #motoactv
16:02 [mbm] cmw: those disected pictures on your site .. did you take any of the screen or other internals?
16:15 dproldan I asked him once,  he said those are the only ones he has
16:16 dproldan the FCC has some documents
16:16 dproldan https://fjallfoss.fcc.gov/oetcf/eas/reports/​ViewExhibitReport.cfm?mode=Exhibits&Requ​estTimeout=500&calledFromFrame=N&app​lication_id=706940&fcc_id=%27IHDP6MB*%27
16:16 dproldan more are coming out next month 15th
16:18 dproldan if you have 2950 USD lying arounf:  http://www.teardown.com/AllRepo​rts/Product.aspx?reportid=2064
16:19 dproldan or maybe you can find/hack  a download link
16:22 dproldan I think bdaman80 had it opened up,  because his battery had a bubble
16:25 dproldan about the teardown report,  I found a link that shouln't be public :  http://www.ubmtechinsights.com/privateAs​sets/0/2147483738/2147483775/2147483906/​6b6a2eb0-cf4e-4a70-88c1-1352fd86e494.pdf
16:26 dproldan you know quite a bit about routers, :-) ,  maybe you can find the report...
16:27 dproldan http://www.youtube.com/watch?v=dnrs​UbK_O0o&list=UUXeC_6_e1mdWMLUhL​-oYNoA&index=3&feature=plcp
16:27 dproldan you can see the display in that video
16:29 dproldan if you look carefully,  you can read some numbers printed on the display,  zoom, enhance...
18:05 christefano joined #motoactv
18:15 dproldan [mbm]: took a look?
18:25 UnwinnableDonB joined #motoactv
18:27 [mbm] huh?
18:27 * [mbm] scrolls up
18:27 [mbm] ah
18:29 [mbm] I didn't think of usimg the fcc site; normally they only take pictures of the transmitter
18:29 dproldan there are no pictures unfortunately yet
18:29 dproldan motorola requeted confidentiality
18:29 dproldan they should come out net month IIRC
18:30 [mbm] oh, aside, saw your pictures of the mic
18:30 [mbm] interesting although it'd be better if it was less bulky
18:30 dproldan heh,  made  new, smaller version
18:31 [mbm] of course the smaller you make it the harder it'd be to remove
18:31 dproldan yep
18:31 dproldan look at version 2
18:31 dproldan https://picasaweb.google.com/111067582235558199450​/MotoACTVMicrophone?authuser=0&feat=directlink
18:32 [mbm] heh, a bit better
18:32 dproldan but I'm planning making one that grows to the side instead
18:32 [mbm] wtf do you use the mic for?
18:32 dproldan text input
18:33 dproldan voice recorder,
18:33 [mbm] wasn't sure if it was some dick tracy wrist phone
18:34 dproldan heh
18:34 dproldan I found that echo 2 to sys/class/graphics/fb0/rotate is working
18:35 ds2 Nice
18:35 ds2 you can get small mics
18:35 UnwinnableDonB Would this be the wrong place to ask how (or if) Runkeeper runs on the device once it's rooted?
18:35 [mbm] dproldan: yep, but then you need to also rotate the touchscreen input
18:36 ds2 dproldan: why not just use a bluetooth ear peice?
18:37 dproldan battery consumption,  don't like BT ear pieces
18:37 ds2 I see
18:37 [mbm] UnwinnableDonB: you mean rootkeeper?
18:38 UnwinnableDonB mbm: No, I mean Runkeeper.
18:39 UnwinnableDonB Another fitness app. Been using it with my phone for a while, but if I can get it running on the MOTOACTV I'll spend a few bucks and not worry about having my phone in my pocket the whole time.
18:39 * [mbm] takes a stab - motorola util that keeps track of running exercise?
18:40 UnwinnableDonB It's not by Motorola.
18:42 [mbm] oh, motorola has something (presumably) similar built in
18:42 UnwinnableDonB Right, but I have two years worth of data already in Runkeeper and would like to continue using it if I can.
18:43 [mbm] detects when you start running while wearing the device, records gps and counts calories, steps, etc
18:43 UnwinnableDonB It looks like there's a website to convert the MOTOACTV CSV to a TCX file, then import into RK, but I'd rather cut out the middle man and just run RK natively on the device if at all possible.
18:44 [mbm] dunno how well standard android apps will work; two problems, screen resolution, and not all sensor data is available through android calls
18:44 ds2 not all? isn't none more accurate? :)
18:45 [mbm] well, gps works :)
18:45 ds2 that doesn't use the sensor API
18:45 [mbm] right
18:45 ds2 if you can get a stream of data from the MSP430 for teh raw data, it is trivial to export that over the sensor API
18:46 [mbm] none of the compas, orientation, light sensor(?) stuff works
18:46 ds2 there is no compass, right?
18:46 [mbm] dunno
18:46 ds2 orientation needs a compass (or maybe a gyro)
18:47 ds2 light sensor might not exists (at lease I don't see the brightness changing)
18:47 [mbm] an accelerometer can give you basic oprientation
18:48 [mbm] anyway, thinking that the razr also uses an msp430
18:49 [mbm] not sure at what level things are broken though
18:49 ds2 but orientation is based off of north
18:49 UnwinnableDonB left #motoactv
18:49 dproldan ds2: there's a light senser on the bottom.right corner
18:49 [mbm] is the msp430 not providing data or is libhardware and the sensor api ignoring it?
18:49 ds2 dproldan: thought that was an LED?
18:49 dproldan led is top.right
18:49 ds2 from the logs, it appears libsensors is ignoring it
18:50 ds2 libsensors just reads from the kernel stuff
18:50 dproldan moto's quality touch
18:50 [mbm] so you think the msp430 is providing the data and doesn't need firmware changes?
18:52 ds2 the msp430 is just a I2C slave isn't it?
18:52 [mbm] probably
18:52 [mbm] but there's an msp firmware for it
18:53 ds2 maybe there is another I2C address that has raw data
18:53 [mbm] in /system/etc/msp...
18:53 ds2 yes
18:53 [mbm] there's actually two firmwarea there
18:53 ds2 the msp430 has a i2c hardware block
18:53 ds2 wonder if we can locate the chips on the board and id stuff from that
18:54 [mbm] one gets used for 'msp430 boot -f' and another for 'msp430 bootfactory -f'
18:54 ds2 what does msp430 do?
18:54 [mbm] the msp430 util also has what looks to be an i2c read
18:54 dproldan input0 is mspensor porcessor
18:54 ds2 (the binary)
18:55 dproldan sys/class/input/input0
18:55 ds2 is it suppose to program it or?
18:55 dproldan input??
18:55 dproldan that's for receiving data
18:55 ds2 input is a common way to interface with sensors
18:55 [mbm] you can run 'msp430 read 0 10' and it reads 10 bytes from offset or register 0
18:55 ds2 in both directions :(
18:56 dproldan oh
18:56 dproldan let's see
18:56 ds2 I wonder if msp430 read uses jtag or spybiwire
18:56 [mbm] you can also do 'msp430 debug 255' or any other number
18:56 ds2 does debug 256 work?
18:56 [mbm] oops, above should be msp430 tread ..
18:56 [mbm] which is a test read
18:57 dproldan cat /dev/input/event   ...
18:57 [mbm] thinking it's all just a wrapper fpr i2c
18:57 [mbm] the boot seems to send the firmware in several packets
18:58 ds2 were you able to strace it?
18:58 [mbm] factory returns 0 for all tread commands
18:58 [mbm] normal firmware has some data
18:58 ds2 dproldan: look for evtest.c
18:58 [mbm] nope, haven't got all my utils on the motoactv uet
18:58 ds2 or actually... no
18:59 ds2 dproldan: do getevents /dev/input/event0
18:59 ds2 in an adb shell
18:59 ds2 not as nice as evtest but that should be there already
18:59 [mbm] anyway, all of the above msp430 commands are harmless; worst case you may need a reboot
18:59 dproldan definitely rotation is getting sent to event0
19:00 [mbm] dproldan: nifty, so libsensors is just stupid?
19:00 dproldan looks like
19:00 dproldan they dumbed it down
19:00 ds2 easy enough to rewrite
19:00 dproldan i hope
19:01 ds2 did it for GB and ICS stuff already
19:01 [mbm] probably another moto device with an omap3 and an msp430 you can yank the library from, if so lazy
19:01 dproldan great
19:02 ds2 [mbm]: just replace system/lib/hw/sensors.NAMEOFPLATFORM.so
19:02 ds2 it is loaded as a shared object/plugin
19:02 [mbm] that's what I mean
19:03 [mbm] I'm just too lazy to write my own version and would probably just copy that file from another moto phone
19:04 ds2 heheh
19:05 dproldan there's already a sensors.G2.so
19:07 ds2 replace that
19:08 dproldan ok, will do
19:09 ds2 nice... event0 seems to be a 2 axis accel
19:10 ds2 very low res one
19:13 ds2 event6 seems to alias event0
19:13 ds2 enough of a diversion
19:13 ds2 als doesn't seem to respond
19:14 dproldan what is als
19:14 ds2 I assume that is the light sensor
19:14 dproldan there's a leds, cpcap-als
19:15 dproldan leds-cpcap-als
19:15 ds2 capcaps-als?
19:15 ds2 I see a cpcap-key
19:15 ds2 cyttsp3-i2c
19:15 ds2 and a als
19:15 ds2 what version are you on?
19:15 dproldan 5.6.0
19:15 ds2 hmmm same here
19:15 dproldan or whatever they call this :-)
19:16 ds2 Ohhhhh
19:16 ds2 how did you get to 5.6.0?
19:16 dproldan flashed images
19:17 dproldan well,  upgraded when I got the device,  but the last time I flashed system.img, boot.img
19:17 ds2 hmmm okay, so that rules out me having a different kernel
19:18 dproldan sys/leds/classes
19:18 dproldan sys/classes/leds
19:18 dproldan sorry
19:18 dproldan cpcap-als-led
19:19 ds2 where are you looking?
19:20 dproldan nothing,  there are only three leds in the system,  classes/leds show 4
19:20 dproldan well,  R, G, B, charging, Backlight
19:20 ds2 I mean to get those names
19:21 dproldan dunno,  you don't have them?  I'm in ADB shell
19:21 dproldan "/sys/classes/leds"
19:22 ds2 no... are you looking in /proc, /sys or ?
19:22 dproldan shit "sys/class/leds"
19:22 dproldan sorry about that
19:22 ds2 ah okay
19:22 ds2 what about for the input devices?
19:22 ds2 still trying to resolve why we have different names
19:22 dproldan let me see
19:23 dproldan this is in sys/class/input/ input0
19:23 dproldan input1
19:23 dproldan event0
19:23 dproldan event1
19:23 dproldan input2
19:23 dproldan event2
19:23 dproldan input3
19:23 dproldan event3
19:23 dproldan input4
19:23 dproldan event4
19:23 dproldan input5
19:23 dproldan event5
19:23 dproldan input6
19:23 dproldan event6
19:24 ds2 Oh.. .we are looking in different places
19:24 ds2 cat /proc/bus/input/devices
19:24 dproldan same result
19:24 ds2 you still see different names?
19:28 dproldan don't know what you mean,  we whare talking about the led,  I made a type,  I don't think we have different names
19:28 dproldan where, typo
19:28 ds2 and I was talking about the input devices... definitely different things
19:29 christefano joined #motoactv
19:34 dproldan oooh,  I may have found something...
19:35 dproldan looks like the back button is part of the touchscreen
19:37 dproldan cat /dev/input/event2 works for the whole screen and the back button
19:37 ds2 what about the area outside of the backbutton but off the screen?
19:38 dproldan nope,  but I saw a file somewhere that was about that
19:40 dproldan well,  in the PCB there's a small metal piece that looks like the capacitive sensor,  but I wasn't expecting this button to be in the same input device
19:41 christefano joined #motoactv
19:47 dproldan in /sys/board_properties/virtualkeys.cyttsp3-i2c
19:59 dproldan ç
20:02 CEnnis91 dproldan: yea all soft keys are part of the touch screen
20:02 CEnnis91 even in pre 3.0
20:03 CEnnis91 [mbm]: i cant remember if you ever told me, is that whole softkey area accessible, or is it only the back button corner
20:04 dproldan so maybe it's possible to modidy that virtualkeys.cyttsp3-i2c to provide more buttons?
20:04 CEnnis91 dproldan: depends
20:05 dproldan I think it's a hardware button,  mapped through the TS controller
20:05 CEnnis91 if the area by the back button is accessible and registers touch, then sure
20:05 CEnnis91 but we dont want to take up screen real estate to put them on the touchscreen
20:06 CEnnis91 also, for in-android situtations, its possible to add key combos to perform certain actions
20:06 CEnnis91 like, power+music = open music for example
20:09 dproldan k
20:37 [mbm] huh, I'll need to take another look at the touchscreen
20:38 [mbm] android sees it as two different pieces
20:38 [mbm] and unlike my droid I can't start an event in the middle of the screen and continue it through the capacitive buttons
20:39 [mbm] so I had assumed they were separate
20:39 dproldan I think they're separate
20:39 [mbm] if it's one massive touchscreen we may be able to map new keys next to the back button
20:39 dproldan in the PCB pictures,  you can see the sensor for the back button
20:41 [mbm] also I seem to remember the key mapping for the soft keys came from devtree
20:41 dproldan does the droid have that virutalkeys file?
20:42 [mbm] the droid1 had a touchscreen that extended to the capacitive buttons and then the kernel was passed parameters for x/y of virtual buttons and the scan code
20:44 [mbm] since it was all part of the same touchscreen and keys were only detected on the initial press, it was possible to swipe through the buttons and get one continuous line which android clamped to the screen resolution
20:48 CEnnis91 [mbm]: and you never made that zoom by scrolling on the virtual keys modue
20:48 CEnnis91 module*
20:53 [mbm] lol
20:53 [mbm] yeah, never got around to that 9ne
20:53 [mbm] one
21:06 ds2 CEnnis91: did you have your unit disassembled?
21:44 [mbm] he doesn't have one yet; been doing all his work blindly
21:44 [mbm] think utkanos is supposed to hand off the motoactv to CEnnis91
21:45 dproldan bdaman80 had his unit opened
21:45 dproldan http://www.youtube.com/watch?v=dnrs​UbK_O0o&list=UUXeC_6_e1mdWMLUhL​-oYNoA&index=3&feature=plcp
21:46 ds2 oh... for some reason I thought he was the one that started it all with the blog posting
21:48 [mbm] no, that was cmw
21:50 ds2 that is a person? I thought that was the recovery
21:50 ds2 boy am I lost :(
21:50 dproldan :-)
21:51 dproldan cmw <> cwm
21:52 dproldan the pictures from his blog are not from a release device,  you can see some differences,  and the shieldings are removed,  etc
21:52 ds2 oh
21:53 [mbm] ds2: recovery is clockwork recovery; cwr
21:53 ds2 the website is like clock work mods recovery or something like that
21:54 [mbm] oh
21:54 ds2 hence my confusion
21:54 [mbm] dunno, but I do know it's a reference to the movie clockwork orange
21:55 ds2 *shrug*
21:55 ds2 i am a bare bones, fastboot flashing person
21:56 [mbm] ditto, but all the cm fanatics are unreasonably obsessed with cw
21:56 [mbm] it might fall under the category of can't teach an old dog new tricks
21:57 ds2 *shrug*
21:57 ds2 depends on what you are used to I guess
21:59 [mbm] anyway, the clockwork logo is based on the bowler hat and eyeshadow used in the movie; koush (original author) homepage was also done in a movie tribute style
21:59 dproldan [mbm]: saw those links about teardown.com and ubmtechinsights.com?
22:00 ds2 the reason I was asking if someone has it apart is that you can see the ITO on the glass if you hold it to the light right
22:00 ds2 since the button area is painted black, one needs to look from the back
22:00 [mbm] and if I remember right, it used orange menus in clockwork recovery
22:00 [mbm] ds2: saw then but I'll wait until I'm not on a mobile to poke around the sites
22:01 ds2 *nod* and I am suppose to be working on other things right now too ;)
22:02 dproldan hope you get something with your kungfe
22:02 dproldan kungfu
22:04 * [mbm] isn't going to pay someone $2950 to find out what could also be discovered with $199 and a hammer
22:05 ds2 hahahahahahaha
22:05 [mbm] chip decapping is fun and all, but in most cases you can just read the part number off the package
22:06 ds2 yep
22:06 ds2 has anyone found which accel is on there?
22:31 * [mbm] has a hammer; just need a spare motoactv
22:49 CEnnis91|Mobile joined #motoactv
23:45 dproldan can't restore a backup I made with recovery
23:46 dproldan Error while erasing boot image!Formatting /boot...
23:46 dproldan E:format_volume: no MTD partition "/dev/block/mmcblk1p12"
23:46 dproldan what would be the right command
23:47 [mbm] probably expects a name like BOOT which it then looks up in an internal table
23:52 ds2 mmcblk1p12 is not a MTD device
23:52 dproldan I think this is a bug in utkanos's recovery
23:52 ds2 there is no concept of erasing it other then maybe zeroing (unless you want to do the SD/MMC discard block command)
23:52 [mbm] wait, which recovery are you using?
23:53 dproldan utkanos cwrecovery mod
23:53 [mbm] oh
23:53 dproldan there's no backup/restore in the stock recovery
23:54 dproldan bah,  it's ok,  I flashed a boot.img
23:54 dproldan I'll tell him later
23:54 [mbm] wasn't sure if you'd done another recovery as part of the cm port you were working on
23:54 dproldan no, I have more than enough
23:54 [mbm] and yeah, just unpack the backup and flash via fastboot

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