Camelia, the Perl 6 bug

IRC log for #motoactv, 2012-04-15

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

All times shown according to UTC.

Time Nick Message
01:10 Quietlyawesome94 joined #motoactv
02:12 smbgaiden weird, could connect to the BT device for about 7 hours, now not anymore
02:12 smbgaiden weird moto
02:39 smbgaiden now it won't pair to the moto smartphone, weirdness continues
03:07 smbgaiden all hope lost, back to restore device
04:38 smbgaiden restore w/o wiping user data got me the BluetoothDevice.ACTION_FOUND back, but the socket was still hosed. Time for a userdata wipe and re-root, re-flash, and re-upgrade
05:06 smbgaiden much better
05:06 smbgaiden senstive system
05:18 smbgaiden narrowing down the problem a bit
05:18 smbgaiden Anyone notice when they have a thread running, which uses a handler to communicate back to the UI thread that after some time the UI thread stops receiving the handler messages?
05:55 dproldan joined #motoactv
05:58 smbgaiden wb sir
05:58 dproldan smbgaiden: I remember seeing some messages related to some kind of "motion timer" for the msp430,  looks like when the device doesn't move for some time,
06:00 dproldan the msp430 send data less frequently,  maybe it's messing with the rest of the system?
06:01 smbgaiden wow, you've got some extensive knowledge on this gadget!
06:01 [mbm] there's an i2c register for how often the msp refreshes
06:02 smbgaiden 04-14 22:34:29.593  2330  2348 I GPSReadThread: SENDING GPS DATA: 1024
06:02 smbgaiden 04-14 22:34:29.593  2330  2330 I ShowGPSData: MESSAGE_GPS_DATA_AVAILABLE: 1024
06:02 smbgaiden 04-14 22:34:34.593  2330  2348 I GPSReadThread: SENDING GPS DATA: 1024
06:02 smbgaiden 04-14 22:34:37.398  2330  2330 D AndroidRuntime: Shutting down VM
06:02 smbgaiden you make sense
06:03 smbgaiden about a minute and a half it decides to shut down some stuff
06:03 dproldan wow,  just like that
06:03 smbgaiden gonna re-run with continuous shaking
06:05 dproldan [mbm]: is it possible to write to that register?
06:07 smbgaiden this shaking seems to  avoid the bug
06:07 dproldan good,  now we know
06:07 smbgaiden so i guess my use case will be intact, but i need a shaking harness for my debug environment
06:08 dproldan heh,  let's find somwhere to disable it
06:08 [mbm] yep.
06:08 smbgaiden caught a log for that session, will look into it after it crashes
06:09 smbgaiden crashed
06:09 smbgaiden yea, about 1.5 minutes
06:09 [mbm] http://wiki.opticaldelusion.org/wiki/MSP430 .. look at the razr map, there's an update_rate
06:12 dproldan 04-15 08:12:21.882  1204  1688 D kinetics: MSP430_IOCTL_SET_EQUIPMENT_TYPE = 0
06:12 dproldan 04-15 08:12:21.882  1204  1688 D kinetics: MSP430_IOCTL_SET_MOTION_DELAY = 60000
06:12 smbgaiden yea, i had it going for 6 minutes straight
06:13 dproldan vs   04-15 08:13:02.358  1204  1204 D kinetics: MSP430_IOCTL_SET_MOTION_DELAY = 1000
06:13 smbgaiden then i put it down, about 20 seconds later it died
06:14 smbgaiden yep, that 1000 comes prior to the crash
06:14 smbgaiden 04-14 22:32:20.210  1205  1525 D kinetics: MSP430_IOCTL_SET_MOTION_DELAY = 1000
06:15 smbgaiden 04-14 22:34:37.398  2330  2330 D AndroidRuntime: Shutting down VM
06:15 smbgaiden hmmm, not 1:1 mapping, must be more to it. will look deeper
06:17 dproldan list the services,  find one that makes sense,  adn kill it!
06:17 dproldan !
06:17 dproldan >:-)
06:19 smbgaiden nothing obvious there
06:20 dproldan <6>[  653.017822] msp430_kick_idletimer() set regsiter 0x99 to 0xaa
06:21 smbgaiden i don't have that in my log
06:22 dproldan dmesg
06:22 smbgaiden <6>[ 4727.380676] msp430_kick_idletimer() set regsiter 0x99 to 0xaa
06:22 smbgaiden yep
06:22 smbgaiden <6>[ 4696.561676] set motion delay = 60000
06:22 smbgaiden <6>[ 4727.509399] set motion delay = 1000
06:24 smbgaiden <6>[ 4737.586029] request_suspend_state: sleep (0->3) at 4732698456691 (2012-04-15 06:08:59.315094817 UTC)
06:24 smbgaiden doing the unwanted
06:28 dproldan oh,  think I have found a low power mode for the touch screen controller
06:29 dproldan echo 1 > /sys/devices/platform/i2c_omap​.1/i2c-1/1-003b/low_power_mode
06:29 dproldan <6>[ 1396.666290] cyttsp_pr_state: ACTIVE
06:29 dproldan <6>[ 1419.323608] cyttsp_low_power_mode_store: touch low power mode=1
06:30 [mbm] hmm, need to map out the i2c buses
06:38 [mbm] there.. msp430 is sitting on i2c-2 at 0x48
06:39 smbgaiden could not repeat your research on that one
06:40 [mbm] talking to me?
06:41 dproldan I2C@0 {
06:41 dproldan bus1devices = "cyttsp3-i2c";
06:41 dproldan bus2devices = "msp430";
06:41 dproldan bus3devices = "cs42l73,lm3535";
06:41 [mbm] yeah, buses are obvious
06:41 [mbm] it's the addrs that are tricky
06:42 dproldan :-)
06:44 [mbm] anyway, proved my theory that the msp430 command was nothing more than an i2c wrapper
06:47 dproldan smbgaiden: I think this is what needs to be disabled:  04-15 08:46:36.734  1295  1454 E WSensorManager: The service is not enabled yet.unregisterEventListener
06:49 smbgaiden makes sense, but also not. It comes before setting the 04-14 22:02:15.226  1205  1210 D kinetics: MSP430_IOCTL_SET_MOTION_DELAY = 60000
06:49 smbgaiden 60k seems adequate, 1k sucks
06:53 [mbm] smbgaiden: what exactly are you trying to do with the msp?
06:53 dproldan the motion delay is not the problem for you, i think.  but the service that sets it,  is also disabling many other events,  even wifi
06:54 smbgaiden mbm: want it to leave alone my bluetooth SDP
06:55 smbgaiden connected up a 00001101-0000-1000-8000-00805F9B34FB
06:55 smbgaiden cuz moto screwed up the onNmeaReceived
06:55 [mbm] hmm that MSP430_IOCTL_SET_MOTION_DELAY is just how often the kernel polls, timing information isn't pushed to the msp
06:56 [mbm] and what does the msp have to do with bluetooth?
06:57 smbgaiden in about a minute thirty it is killing my Handler which recv the Message from the socket reading thread
06:57 smbgaiden the thread keeps spinning and sending to the handler
06:58 smbgaiden the receiver stops getting
07:00 [mbm] so the device goes to sleep and kills your reciever?
07:00 smbgaiden yep
07:01 smbgaiden thanks to the advice here, if I keep shaking the thing, it goes well beyond the minute and a half
07:01 dproldan haven't you noticed that wifi dies after a while?  i think it's also related
07:01 smbgaiden not using wifi much on this one, but highly likely related
07:03 [mbm] should be a setting somewhere for how long before it goes to sleep
07:04 [mbm] yay - http://wiki.opticaldelusion.​org/wiki/MSP430#Memory_map_.28Motoactv.29
07:04 [mbm] gps is handled by the msp?
07:05 smbgaiden im using a bluetooth gps, because moto screwed up the onNmeaReceived
07:05 dproldan lol
07:06 dproldan OMAP_OFF_MODE??
07:06 [mbm] heh yeah, there are some interesting looking ones there
07:07 [mbm] that particular one is used in msp430_kick_idletimer
07:08 [mbm] buff[0] = OMAP_OFF_MODE;
07:08 [mbm] buff[1] = WAITING_FOR_MOTION;
07:08 [mbm] err = msp430_i2c_write(ps_msp430, buff, 2);
07:08 [mbm] if (err < 0)
07:08 [mbm] printk(KERN_ERR "Unable to set MSP to waiting for motion\n");
07:12 [mbm] looks like the msp430 holds the off wakelock
07:12 [mbm] kinda suggests that smbgaiden can just grab a wakelock and prevent the device from going into sleep
07:13 dproldan think about it,  the only way to have BT on all the time is disabling this wakelock, thats why if you have bluetooth on, for anything,  the battery dies so fast
07:13 dproldan even when there's no comms
07:14 smbgaiden true, makes sense.. ~250mAh battery will choke on continuous communication
07:15 [mbm] yeah, that's one thing I hate about the motoactv smartphone app; kills the battery on both ends
07:15 dproldan and this, gentleman,  is why we need aosp on this device
07:16 smbgaiden agreement
07:16 [mbm] heh
07:16 dproldan :-)
07:18 [mbm] hmm .. MAG_H{X,Y,Z}
07:18 [mbm] msp has a magnetic compass?
07:18 dproldan [mbm]: you don't want to give it a try?  porting AOSP I mean
07:19 [mbm] I've done aosp ports before, pretty tedious
07:20 dproldan shouldn't be so difficult with this device…
07:20 dproldan I'm stuck with the mot_boot_mode,
07:21 dproldan even if I don't call it,  init doesn't keeo going
07:21 dproldan keep
07:21 [mbm] this is with cm?
07:22 dproldan yes,  at this point I don't care about cm
07:23 dproldan about the compass,  I don't think there is one,  also no hall sensor that appears in dev_tree
07:24 [mbm] stupid trick is to compile the kernel with framebuffer console and then use write commands in init.rc to write to /dev/console
07:24 dproldan vibrator
07:24 [mbm] right, but I'm looking at the kernel's memory map for the msp
07:25 [mbm] anyway, mot_boot_mode is pretty much useless for us; just sets a few properties based on how the device was booted
07:26 dproldan that's what it's supposed to do…  but If it's not called,  I can't class_start anything
07:30 [mbm] hmm magnetics are reading 0 :/
07:30 dproldan gyro?
07:31 [mbm] the accel seems to be working
07:31 dproldan accelerator and gyros are usually in the same IC
07:32 [mbm] yeah, I see accel x/y/z on the memory map
07:32 [mbm] don't see a gyro
07:34 [mbm] wonder wtf a MODULE_CONFIG is
07:40 dproldan is it possible to set BYPASS_MODE?  maybe we can check with that instrumentation.apk
07:41 dproldan and see if the msp can function as standard sensors for android
07:41 [mbm] you're looking at the razr map
07:41 [mbm] don't see that in the motoactv
07:42 dproldan yeah,  sorry
07:49 [mbm] any idea what tap_tap_3d means?
07:54 dproldan nope,  maybe has to do with the "shake to wake up" function,  you can shake it in any axis
08:16 [mbm] hmm, interesting
08:16 [mbm] kernel code for interfacing the msp has a bunch of #ifdef G1
08:17 [mbm] and it's not reporting the accelerometer values because it's not a G1
08:18 * [mbm] should probably recompile the kernel and fix that ;)
08:30 [mbm] yay.
08:39 dproldan got it?
08:41 dproldan is ti possible that G1 refers to the razr?  found some pics of the razr pcb,  the marking on its msp430 are: M430V294 M9C5RLT A TI G1
08:42 dproldan coincidence?
08:43 [mbm] dproldan: yeah, playing enigma now :)
08:43 dproldan woot!
08:44 dproldan genius
08:47 dproldan more ifdefs with G1 around ?   lol
08:48 [mbm] http://wiki.opticaldelusion.org/wiki/Motoactv#Boot
08:49 dproldan domo arigato gozaimasu
08:49 dproldan <-- bows
08:52 [mbm] g1 adds acceleration, environment, magnetic and orientation reporting
08:52 [mbm] environment is apparently the pressure and temperature registers
08:54 [mbm] guessing that acceleration is the only one that actually works
08:58 [mbm] wouldn't be surprised if polling the accel constantly drains the battery
09:00 dproldan autorotation works now?
09:00 dproldan yes!
09:00 dproldan it's rotated though
09:01 [mbm] oh does it work? cool.
09:02 dproldan yep,  only wrong direction
09:02 [mbm] easy enough to remap the axis in the kernel
09:05 dproldan side note:  if you like this about the razr : http://pws.prserv.net/fomalhaut/Re​port_Motrola_DroidRAZR(Rev.3E).pdf
09:10 [mbm] nifty
09:11 dproldan don't know if you have to change the axis on the kernel
09:11 dproldan 04-15 11:09:50.405  1205  1218 I WindowManager: Setting rotation to 0, animFlags=0
09:11 dproldan 04-15 11:09:50.428  1205  1218 I ActivityManager: Config changed: { scale=1.0 imsi=0/0 loc=es_US touch=3 keys=1/1/2 nav=1/1 orien=2 layout=17 uiMode=0 seq=19}
09:18 [mbm] hmm?
09:19 dproldan android is receiving rotation 0,  sets orien 2?
09:20 [mbm] I had to go into the enigma settings and flip x
09:21 dproldan oh,  shake to wake up is not working anymore here
09:23 [mbm] hmm, yeah, same
09:27 [mbm] not really sure what broke it
09:28 [mbm] might need to recompile the kernel without g1 just to make sure that their kernel sources aren't prior to that functionality
09:29 dproldan oh,  that could be it
09:38 [mbm] seems to be exactly the case :/
09:41 dproldan time to start bitching them for new kernel sources
09:47 [mbm] I'll poke at it more tomorro
09:47 [mbm] looks like they have an interrupt tiggered on motion
09:55 [mbm] hmm, yeah the newer kernel has a "Got gesture interrupt"
10:16 dproldan_ joined #motoactv
14:09 Snoothy joined #motoactv
14:53 dproldan joined #motoactv
15:04 dproldan joined #motoactv
15:12 dproldan joined #motoactv
15:17 Snoothy dproldan: about the accel/auto-rotate, what do you mean with wrong direction?
15:18 Snoothy is it off by 90 degrees?
15:18 dproldan yes,
15:18 dproldan witht
15:18 dproldan the the device fisically on portrait,  the UI is in landscape
15:18 Snoothy as i predicted :P
15:20 Snoothy and moto's power saving in the newest update.. is that just disabling hardware when the wakelock expires?
15:21 Snoothy wifi, accel etc.?
15:21 dproldan don't know exactly if this is from the new version
15:22 dproldan the only power saving feature in the new version is the maraton mode, right?
15:22 Snoothy http://www.engadget.com/2011/12/23/motorola-motoac​tv-firmware-bump-gives-you-marathon-battery-life/
15:22 dproldan that's only 1-3 seconds data collection
15:23 dproldan not much
15:23 Snoothy ah, so it's just a marathon workout thingy you can select and it polls less?
15:23 dproldan yes,  plus,  if you keep moving the device,  the
15:24 dproldan wakelock doesn't expire
15:24 dproldan so this doesn't apply really
15:24 Snoothy after the 1.5min, how does it start the wakelock again?
15:24 Snoothy do you have to manually wake it up?
15:25 dproldan shaking the device or puching a button
15:26 Snoothy and with bt turned on, the wakelock won't expire?
15:28 dproldan I think so,  with a bt headset or the phone's motoactv connected,  everything stays on
15:30 Snoothy any idea how long actv lasts with bt connected and just idling?
15:30 Snoothy no wifi or gps
15:30 dproldan haven't really checked all this,  I have made too many changes to be reliable
15:31 dproldan bt connected means 6-7 hours,  I think
15:33 Snoothy decent
15:38 dproldan no!  :-)
15:38 dproldan BT shouldn't mean much when it's idling
15:39 Snoothy true
15:40 Snoothy i have a bt module here which uses 8mA when paired and idling
15:43 dproldan yes,  many headsets can stay on and connected for days
15:43 dproldan of course this is not a headset, but still
15:45 dproldan there are many things that can be tweaked for battery life
15:45 Snoothy would disabling the wakelock with the bt still connected increase the battery life?
15:45 Snoothy or is it necesarry for the bt to tx/rx ?
15:46 dproldan for example,  I think the cpu minimum clock now is 200 Mhz,  this doesn't need so much speed
15:46 Snoothy ot
15:46 Snoothy it's running 600mhz stock? *
15:46 dproldan no,  the MSP430 has nothing to do with BT
15:46 Snoothy ah
15:47 dproldan I know the phones need to be at 200 Mhz min for a reliable communication with the basebadn processor,  we the motoActv has no phone part
15:48 Snoothy so you're suggesting it might go even lower?
15:49 dproldan yes,  when the device is suspended,  it shouldn't need much
16:03 Snoothy it's gonna be awesome when i get my actv.. i'm going to control these with it and some more :D
16:03 Snoothy http://i.imgur.com/PhFqt.jpg
16:03 Snoothy WIP
16:05 dproldan what is that?
16:06 Snoothy shutter shades with 6 lines of el-wire
16:06 Snoothy lights up in green when you connect AC
16:06 dproldan cool,  you're builiding it?
16:06 Snoothy yea
16:06 Snoothy credits goes to http://ch00ftech.com/2011/12/31/stronger-glasses/, tho
16:07 Snoothy my version is just going to have BT and an android app :P
16:08 dproldan nice
16:08 dproldan be sure to document the process
16:09 Snoothy most of it is already on ch00ftech, but i will write my additional steps down
17:01 dproldan joined #motoactv
17:11 dproldan joined #motoactv
17:22 dproldan joined #motoactv
17:38 [mbm] stock kernel is set to run at either 300 or 600Mhz it can easily be configured to run much lower
17:40 dproldan what about trying 50?
17:46 smbgaiden morning
17:46 Snoothy evening
17:46 smbgaiden Time to try WakeLock (then file my taxes)
17:48 smbgaiden that was weird, woke the device through zeam. pressed 'home', saw the clock in regular launcher around my bedtime. shook the device and the clock changed. they really shut stuff down without activity!
17:50 dproldan it's a good idea,  the msp430 is really low-power.  But they forgot to optimize when the device is actually doing something...
17:51 smbgaiden I guess it must have been intentional, closed system, so only need to optimize what they restricted
17:52 Snoothy the msp430 is the cpu or am i mistaken?
17:53 smbgaiden http://processors.wiki.ti.com/index.php/MSP430
17:53 smbgaiden yes
17:56 dproldan not the main cpu,  a coprocessor taking care of the sensors
17:56 Snoothy so it's only handling the sensors?
17:57 dproldan also some buttons,  I/O
17:59 smbgaiden Main CPU is ARM
18:11 smbgaiden WakeLock PARTIAL did not solve it :O
18:16 smbgaiden that one managed two minutes
18:41 smbgaiden Full wakelock is suiting my purpose
18:42 [mbm] cool.
18:42 smbgaiden Thanks mbm, you're awesome. I need to learn linux a bit better, so I can be more self-sufficient. too much windows and windows ce (and of course brew) in my blood
18:45 [mbm] android is a bastardization of linux ;)
18:47 smbgaiden :) Also notable, screendim seems to be enough also. Partial not enough. Full enough, Screen dim enough.
18:48 [mbm] btw, not sure if you saw the logs yesterday but I managed to get the acceleration sensor working in android
18:48 smbgaiden Also weird, after some hours android.bleutooth.device.action.FOUND doesn't get fired, but I can still connect by the android.bleutooth.device.action.UUID message
18:50 smbgaiden Awesome, nice work! Was it in a kernel build, some setting needing poking, or some API call from an APK?
18:51 [mbm] kernel rebuild
18:52 Snoothy what was the accel for if it wasnt available in android?
18:52 [mbm] kernel basically has a timer polling the accelerometer and reporting it as input
18:53 [mbm] it's connected to the msp430 which then uses the accelerometer to do the pedometer/calories calculations
18:54 Snoothy so they are saving power using the msp430 ?
18:54 [mbm] basically
18:54 [mbm] msp430 is a little programmable microcontroller
18:55 [mbm] it handles all the 'exercise' stuff
18:55 Snoothy is the gps also connected through the msp430?
18:55 [mbm] android mostly sits idle
18:56 smbgaiden that maps out well with my experience this morning
18:56 [mbm] I don't think so, but there are some gps references in the msp code
18:56 [mbm] I'm not sure if those are for some other product that just got left in or not
18:56 smbgaiden was in zeam and turned on the watch, then hit home button, clock was 0:40
18:56 smbgaiden i shook it and it became 10:00 or whatever
18:57 smbgaiden what is the source basis you're using for kernel probing and building?
18:57 [mbm] it's actually not the shaking that does it, it's the clock rolling over to the next minute
18:57 smbgaiden ah, coincidental timing then
18:58 [mbm] opensource.motorola.com will redirect you to sourceforge with various bits of code for all motorola's devices
18:58 [mbm] using the motoactv kernel they posted there
18:58 [mbm] but it's from several versions ago, and we discovered last night that it was before they added the shake to wake up feature
18:59 Snoothy so they haven't or won't release the new kernel?
18:59 smbgaiden thanks, when i come back from my upcoming trip I think Iwant to eliminate the BT GPS and try getting the NMEA sentences functional
18:59 [mbm] Snoothy: we probably need to bug them to get a new kernel
18:59 Snoothy oh
19:00 [mbm] either that or I reverse engineer their wakeup function
19:00 Snoothy the first option sounds more favorable :P
19:01 [mbm] yeah, didn't really want to dig through assembly code
19:01 [mbm] more testing will need to be done to see how much of a battery drain it is to report the accel values to android constantly
19:02 Snoothy why is it done constantly?
19:02 Snoothy won't you have to request the values for it to be sent?
19:03 [mbm] good question, but the code that was already in the kernel (previously disabled) just runs a timer to read the values and send them to android as input
19:03 Snoothy whats the timer set to?
19:03 [mbm] and so it seems even when android is ignoring those values they still get sent
19:04 [mbm] didn't check, but several times a second
19:04 Snoothy http://developer.android.com/reference/android/h​ardware/SensorManager.html#SENSOR_DELAY_FASTEST
19:05 Snoothy won't this have an effect on the power drain?
19:05 Snoothy Fastest/game/normal
19:05 [mbm] there's also code in there to report temperature, pressure and compass direction, although I doubt those sensors actually exist
19:05 smbgaiden keeping the dim wakelock and manually pressing power to turn off the screen might also work
19:06 [mbm] Snoothy: yeah, I don't have the sources for what they did to android to read the sensor values
19:06 smbgaiden will take a shower and then see what my log says when i am back :)
19:15 Quietlyawesome94 joined #motoactv
19:15 CEnnis91 going back a bit but
19:15 CEnnis91 [mbm]: 1:40:00 PM <dproldan> what about trying 50? -- wake issues at 50mhz
19:15 CEnnis91 ?
19:19 smbgaiden looks good, i can save the dim screen mA draw and still get my notifies
19:20 [mbm] CEnnis91: 50 would probably work
19:20 CEnnis91 i remember that the droid had some wake issues at 150 even
19:21 [mbm] well, it's not like the motoactv needs to wake up instantly to deal with an incoming call
19:22 CEnnis91 hmm this is true
19:22 [mbm] there's also less crap running in the background
19:22 Snoothy not unless you have it connected over bt
19:27 * [mbm] would like to see a rom that fixes the various moto bugs but doesn't break any of the stock apps
19:27 CEnnis91 [mbm]: which moto bugs?
19:27 CEnnis91 havent used this enough to notice anything
19:28 smbgaiden onNmeaReceived does not get fired :)
19:29 CEnnis91 sounds like a kernel issue
19:29 Snoothy <smbgaiden>Also weird, after some hours android.bleutooth.device.action.FOUND doesn't get fired, but I can still connect by the android.bleutooth.device.action.UUID message
19:29 Snoothy :)
19:30 [mbm] CEnnis91: well, fixing the accelerometer to work with android certainly seems like one :)
19:30 Snoothy but stock apps only work with 120dpi?
19:31 CEnnis91 [mbm]: im guessing its not as easy as enabling "Auto rotate display"? lol
19:32 [mbm] that doesn't work either until you fix the accelerometer
19:33 CEnnis91 [mbm]: again a kernel issue no?
19:34 [mbm] oh, so because it's a kernel issue it's not worth packaging a new rom that fixes it?
19:34 CEnnis91 i didnt say that
19:34 CEnnis91 just trying to figure out where to look for the fix =P
19:35 [mbm] thought you might have been implying it
19:35 [mbm] anyway, yeah it's a kernel issue, scroll up further
19:37 CEnnis91 [mbm]: which device do you say this matches the best kernel wise?
19:37 CEnnis91 milestone?
19:40 [mbm] hmm? moto actually posted the motoactv kernel
19:41 [mbm] although yeah, the hardare is very similar to a milestone if you're trying to get aosp running
19:41 Snoothy http://sourceforge.net/proje​cts/motoactv.motorola/files/
19:42 CEnnis91 yes they posted it ^
19:42 [mbm] kernel posted is a few versions older than the rom though
19:42 CEnnis91 [mbm]: custom kernel with stock rom should allow for at least rotation i would think
19:43 [mbm] need an updated kernel before the shake to wake feature will work
19:43 CEnnis91 =/
19:43 CEnnis91 fuck you moto
19:43 CEnnis91 didnt think about that
19:44 Snoothy how hard would it be to make moto upload a newer kernel?
19:44 [mbm] last update: 2011-11-18
19:44 [mbm] :/
19:45 [mbm] Snoothy: apart from the red tape of going through their lawyers it's just a click of the upload button
19:46 Snoothy xD
19:47 [mbm] big companies are always paranoid about posting sources and will refuse to post anything they don't have to (and sometimes even pretend that things that are gpl aren't)
19:48 CEnnis91 [mbm]: possible to add the code in module form?
19:48 CEnnis91 or theres really no way to call it so no point
19:48 [mbm] CEnnis91: possible but messy
19:48 CEnnis91 is there really a better way?
19:48 [mbm] get the damn kernel sources?
19:49 CEnnis91 oh sorry i meant realistic
19:49 [mbm] reverse engineer their changes to the kernel?
19:49 CEnnis91 go ahead
19:49 CEnnis91 no one is stopping you
19:49 CEnnis91 =)
19:52 CEnnis91 wow adb reboot recovery took forever
19:52 [mbm] well fine, if you're going to stop me like that then I won't; no point in me wasting all my time if you guys don't appreciate it
19:52 CEnnis91 heh
19:53 [mbm] bunch of freeloaders.
19:58 CEnnis91 wat is with windows not detecting this thing
20:06 dproldan joined #motoactv
20:14 [mbm] huh?
20:15 CEnnis91 windows/adb wouldnt find the device
20:15 CEnnis91 i just went to linux instead
20:23 CEnnis91 now its not found by fastboot in linux?
20:24 dproldan you're using VMs, I suppose
20:24 CEnnis91 nope
20:24 CEnnis91 and its found in lsusb just find
20:24 CEnnis91 fine*
20:25 dproldan in my linux VM,  I can see fastboot devices,  but I can't flash with it
20:26 CEnnis91 if lsusb can find it, it cant be the cable right?
20:28 CEnnis91 lol okay now back in recovery it wont even find it with lsusb
20:29 [mbm] windows is stupid, requires device specific adb drivers before the adb program will find the device
20:30 dproldan your usb rules are ok?
20:30 CEnnis91 yea
20:30 CEnnis91 after unplugging / replugging multiple times it found it
20:30 [mbm] as for fastboot make sure that you're in fastboot mode (should say fastboot on the screen) and not sbf mode
20:30 CEnnis91 yea it was in fastboot mode
20:31 dproldan btw,  did you see that the voume buttons also work for getting into fastboot mode?
20:31 CEnnis91 cuz after using the misc.img
20:31 CEnnis91 it will always boot into recovery, so im trying to just fastboot erase misc
20:31 Quietlyawesome94 joined #motoactv
20:32 CEnnis91 fyuck
20:32 dproldan yep,  that's a PITA
20:32 CEnnis91 low battery
20:32 CEnnis91 thats so fast
20:32 [mbm] heh
20:32 dproldan oops
20:32 [mbm] yeah, recovery and bootloader are massive battery drain
20:32 CEnnis91 it was at 70 when i started
20:33 CEnnis91 ...15 minutes ago
20:33 [mbm] that must have been about a hour ago?
20:33 CEnnis91 lolz
20:33 [mbm] lol
20:33 dproldan it stops working at 60 or 50, I think
20:33 [mbm] how many times did you reboot?
20:33 CEnnis91 4:15:52 PM <CEnnis91> windows/adb wouldnt find the device
20:33 CEnnis91 dproldan: oh
20:33 CEnnis91 well that would make sense
20:33 [mbm] seems like every time you reboot it knocks off 5% of the battery
20:33 CEnnis91 maybe 3?
20:34 CEnnis91 recovery -> fastboot -> recovery -> recovery a few times
20:34 CEnnis91 4?
20:34 [mbm] heh
20:34 [mbm] factory cables are awesome ;)
20:34 CEnnis91 yea yea
20:35 CEnnis91 dproldan: can you go from sbf -> fastboot mode?
20:35 [mbm] no.
20:35 dproldan vol up + power sbf,  vol down + power fastboot
20:35 CEnnis91 okay well its hanging in fastboot mode
20:35 CEnnis91 just need it to charge up
20:35 [mbm] right, you have to reboot the device and hold different buttons, you can't just switch modes
20:36 CEnnis91 got a different usb cable now
20:36 CEnnis91 i mean assuming it works on first connect i only need like 10 seconds...
20:36 CEnnis91 (including erasing time)
20:36 [mbm] umm, won't charge while in fastboot or recovery
20:37 CEnnis91 derp
20:37 CEnnis91 ummm
20:37 CEnnis91 i think it just did
20:37 [mbm] you're someho stuck in one of those modes?
20:37 CEnnis91 or i tricked the software
20:38 CEnnis91 still wont detech
20:38 CEnnis91 does detect it in lsusb
20:38 CEnnis91 wtf
20:39 CEnnis91 it looks like it wants to
20:39 CEnnis91 then it just say lolfuckyounvm
20:39 dproldan heh
20:39 CEnnis91 [mbm]: can i erase misc in sbf_flash?
20:40 [mbm] no sbfs available for the motoactv, so no.
20:41 dproldan probably you can from recovery
20:41 CEnnis91 [mbm]: sbf_flash -r --misc misc.img file.sbf
20:42 CEnnis91 hex edit out the reboot-recovery?
20:42 [mbm] you're overlooking what I just said - where are you getting file.sbf?
20:43 dproldan dd in recovery?
20:43 CEnnis91 [mbm]: i thought file.sbf didnt need to exist?
20:43 [mbm] it's a requirement
20:43 [mbm] you can't do a damn thing in sbf mode until you've pushed a ramloader to the device
20:43 [mbm] and the ramloader is hijacked from the sbf file
20:44 [mbm] anyway, on mine when I flash misc it boots into recovery and then I just use the reboot menu in recovery and it goes back to normal .. what's the issue with yours?
20:45 CEnnis91 it goes back to recovery
20:45 CEnnis91 im using utkanos's recovery thou
20:45 CEnnis91 maybe thats it
20:45 [mbm] could be
20:45 CEnnis91 but i dont understand why fastboot isnt working
20:46 [mbm] are you running fastboot as root?
20:46 CEnnis91 ive done both
20:46 [mbm] and this is the same fastboot you used to flash misc/recovery in the first place?
20:47 CEnnis91 yes i believe so
20:47 CEnnis91 3.11
20:49 CEnnis91 gonna dd in your recovery real fast
20:49 CEnnis91 i dont think i have time to debub why this is doing this
20:49 [mbm] heh
20:50 CEnnis91 haha adb wont find it
20:50 [mbm] so you managed to get a shell in recovery?
20:50 CEnnis91 here and there
20:50 CEnnis91 i wonder if theres something internal wrong
20:51 [mbm] the adb hacked into recovery is a bit buggy, only works if the cable is plgged in when recovery first boots
20:51 CEnnis91 ummm
20:51 [mbm] or you might be using an old recovery before adb support was added
20:51 CEnnis91 yea i think somethings wrong
20:51 CEnnis91 i just unplugged the usb
20:51 CEnnis91 from the device
20:51 CEnnis91 and the charging light is still on
20:51 [mbm] lol
20:51 CEnnis91 and its unresponsivve
20:52 CEnnis91 okay got it back
20:52 CEnnis91 idk wtf that was
20:52 CEnnis91 except now its "charging" with no led on
20:52 CEnnis91 but idc i have adb now
20:52 [mbm] then how do you know its charging?
20:54 CEnnis91 okay dd-ed it in
20:54 CEnnis91 charging led is back on
20:55 CEnnis91 and its back to being unresponsive lolz
20:55 CEnnis91 lol battery
20:55 CEnnis91 low*
20:56 CEnnis91 im guessing i just fucked recovery
20:56 CEnnis91 cuz it wont even goto the motologo
20:57 CEnnis91 nvm...
20:57 * CEnnis91 should probably stop with the play-by-play
20:57 [mbm] ".. just threw it out the window; hit the neighbours cat"
20:57 CEnnis91 oh this looks promising
20:57 CEnnis91 looks like its the recovery afterall
20:58 CEnnis91 can i get out of charging mode?
20:58 [mbm] dunno what you mean by that
20:58 CEnnis91 ugh ill be back later...
20:58 CEnnis91 gotta go
21:03 CEnnis91|Mobile joined #motoactv
21:04 CEnnis91_ joined #motoactv
21:05 CEnnis91_ Okay got it
21:05 CEnnis91_ [mbm]: utkanoss last recovery won't let it out of the recovery loop
21:05 [mbm] lol
21:06 CEnnis91_ Still not sure about fast boot I'll have to investigate that later
21:06 [mbm] I still say recovery on these things is just about useless
21:10 CEnnis91_ Bbl
21:21 smbgaiden took about an hour of continuous BT comm to drop 10% of battery
21:22 Snoothy screen off, no wifi ?
21:22 smbgaiden screen mostly off with checks every few minutes
21:22 smbgaiden no wifi
21:22 Snoothy gps?
21:23 smbgaiden probably no running. i didn't explicitely turn it on or off
22:15 [mbm] hmm, interesting.
22:15 [mbm] echo on > /sys/power/state
22:16 [mbm] screen turns back on, but without the full backlight so it looks black and white
22:16 [mbm] and it doesn't refresh the screen
22:17 Snoothy what happens if you then press the power button?
22:19 [mbm] then the screen lights up and it's really on
22:20 Snoothy so it turns on with no backlight when you turn state on ?
22:21 CEnnis91|Mobile joined #motoactv
22:22 CEnnis91|Mobile [mbm]: so I was thinking about your numerous comments on how you hate recovery for this device (and in general) but
22:23 CEnnis91|Mobile Because I plan to make an update.zip that will root the boot.img on the fly (so it can work with all devices)
22:24 CEnnis91|Mobile Do you have a non-recovery alternative that can do that?
22:25 [mbm] just directly push a new boot.img from fastboot?
22:27 CEnnis91|Mobile That would require me to update for each update moto pushes
22:27 CEnnis91|Mobile And for everyone to have multiple boot.imgs laying around
22:29 CEnnis91|Mobile Also
22:29 CEnnis91|Mobile That fastboot zip format
22:29 CEnnis91|Mobile Fxz or whatever?
22:30 CEnnis91|Mobile Does that have access to all partitions or only main, (mainly I'm asking for misc)
22:33 [mbm] the xml is literally just fastboot commands
22:33 [mbm] anything that works in fastboot also works in the fxz xml
22:34 CEnnis91|Mobile Okay well that can simplify the flash recovery/flash misc etc
22:43 [mbm] ti temp = 0
22:43 [mbm] , acc temp = 240
22:43 [mbm] Sending temperature = -62
22:43 [mbm] hmm.. that doesn't seem to be working ;)
22:44 [mbm] Sending pressure = 428448153 altitude = 22819
22:45 smbgaiden wow, skydiving?
22:45 smbgaiden underwater?
22:45 smbgaiden huhuhu
22:48 [mbm] Sending orientation values: yaw = 0, pitch =0, roll=0,status=10
22:48 [mbm] also not working
22:48 Snoothy gyro?
22:48 [mbm] looks like it was intended to poll one
22:53 [mbm] lmao.
22:53 [mbm] moto clock diplays steps and calories
22:53 smbgaiden i like that one
22:54 [mbm] steps: 327956
22:54 [mbm] 2
22:54 [mbm] it actually wrapped around to the next line
22:54 smbgaiden lol, i guess i may never reach that count
22:54 smbgaiden typical day is 5k steps for me
22:56 smbgaiden 04-15 15:56:08.249  1204  1536 I WifiService: Keep Wifi enabled since it's in use, current Wifi users: {1422=android.net.wifi.IKeepAlive$Stub$Proxy@407799d0}
22:56 smbgaiden biuzarre
22:56 smbgaiden I am the user, i reallyw ant it off...
22:56 [mbm] well, I admit I'm not quite that active
22:57 smbgaiden downloaded 5.6 from here: http://forum.xda-developers.com/show​post.php?p=23338342&amp;postcount=1 i dont see golf in moto's whole UI, but I find it when I go to zeam
22:58 CEnnis91|Mobile joined #motoactv
22:59 [mbm] yeah, the original 5.6.0 had golf but it wasn't shown in the exercise menu
23:00 CEnnis91|Mobile ^
23:00 [mbm] http://wiki.opticaldelusion​.org/wiki/Motoactv/firmware
23:00 * [mbm] kept notes
23:01 CEnnis91|Mobile I haven't updated it to 1.6.6
23:01 * [mbm] is constantly bugged by the inconsistent version numbering
23:02 CEnnis91|Mobile Yep
23:03 CEnnis91|Mobile I guess this is what happens when moto doesn't have a carrier at their heels
23:03 CEnnis91|Mobile (Thanks Verizon)
23:05 smbgaiden another bug
23:05 smbgaiden i wasnt sure about progress of course downloads, so i cancelled. It deleted all the files off the sdcard mount, but it did not remove from my courses
23:06 smbgaiden thanks for the version list. Im gonna have to look into updating to a newer one
23:06 Snoothy ouch
23:06 smbgaiden i went to manage apps and clear data, but the problem still persists
23:06 [mbm] heh
23:06 [mbm] bbl.
23:10 smbgaiden reboot, still bug. probably gotta delete some files myself
23:13 smbgaiden rm -r /data/data/com.motorola.motogolf/databases/golf.db
23:13 smbgaiden better
23:13 CEnnis91|Mobile What do you mean did not remove the courses
23:13 CEnnis91|Mobile In the list?
23:13 smbgaiden yea
23:13 CEnnis91|Mobile Oh the DB never got updated
23:15 CEnnis91|Mobile Bbl

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