yashsingh1/xdaforums huggingface dataset:
[Other SmartWatches] Saeviomage:
So, I've had _partial_ success building this. In as much as I got as far as getting real code errors instead of LOCAL_MODULE_TAG is wrong errors...

What I had to do:

#---------------------------------------------Script starts here---------------------------------------

#1. Set up my system for doing a build and get repo (which is not a step listed in the normal setup steps)

#2. checkout android

mkdir motoactv_development

cd motoactv_development

repo init -u https://android.googlesource.com/platform/manifest -b android-2.3.4_r1

repo sync

#3. Download the motorola sources

cd ..

mkdir motoactv_source

cd motoactv_source

for i in system-core.tgz system-wlan-ti.tgz README.txt system-bluetooth.tgz motorola-external-visualization.tgz motorola-external-wbxmlparser.tgz motorola-external-util-linux.tgz motorola-external-jcifs.tgz motorola-external-jid3lib.tgz motorola-external-lbl.tgz motorola-external-bthelp.tgz motorola-external-hunspell.tgz kernel-omap3.tgz hardware-ti-omap3.tgz external-iproute2.tgz external-iptables.tgz external-elfcopy.tgz external-elfutils.tgz external-expat.tgz external-e2fsprogs.tgz external-dnsmasq.tgz external-dbus.tgz external-bluetooth-bluez.tgz external-bluetooth-glib.tgz external-bison.tgz external-alsa-lib.tgz bionic.tgz

do

if [ ! -f $i ]

then

echo $i

wget --trust-server-name "https://downloads.sourceforge.net/project/motoactv.motorola/MOTOACTV-Americas/1.7.11/$i"

fi

done

#4. Extract them:

for i in *.tgz

do

tar -xvf $i

done

#5. Copy those extracted folders into the android tree

for i in *

do

if [ -d $i ]

then

cp -r $i ../motoactv_development

fi

done

cd motoactv_development

#6. Get dproldan's stuff

mkdir device/motorola/G2/

vendor/motorola/G2/

git clone https://github.com/dproldan/android_device_motorola_G2.git device/motorola/G2

git clone https://github.com/dproldan/android_vendor_motorola_G2.git vendor/motorola/G2

#7. Fix LOCAL_MODULE_TAGS

find ./ -name Android.mk -exec grep -l "LOCAL_MODULE_TAGS := user" {} \; -exec sed s/"LOCAL_MODULE_TAGS := user"/"LOCAL_MODULE_TAGS := optional"/g {} \;

find ./ -name Android.mk -exec grep -l "LOCAL_MODULE_TAGS := eng user" {} \; -exec sed s/"LOCAL_MODULE_TAGS := eng user"/"LOCAL_MODULE_TAGS := eng optional"/g {} \;

#7. Build the user space components:

. build/envsetup.sh

lunch generic_G2-userdebug

make

#8. Manually fix all the remaining broken LOCAL_MODULE_TAGS that crop up by adding the line LOCAL_MODULE_TAGS := optional to the Android.mk files that come up when you type make. Type make again and keep cycling until it stops whinging.

#--------------------------------------SCRIPT ENDS HERE------------------------------

That's as far as I've gotten. Now I've got a couple of c++ errors showing up, and I'll get to fixing them. Interestingly, one of them is in the bluetooth module (it being broken is the primary reason my watch is not running this rom).

Note: I haven't actually run the above as a script, because I don't want to go through the whole checkout/unzip etc procedure again. If you do run it as-is and hit issues, please say so and how you fixed the problem.
[Other SmartWatches] cerealpirate:
runs good !

I have this running holo launcher and flit keyboard. have a few other apps running as well. good work
[Other SmartWatches] hackerse7en:
THEME

It´s full 100% compatible with UOT Kitchen, i've done a theme in there for our small beast,

just flash it via CWKMOD

:laugh::laugh::laugh::laugh::laugh::laugh:
[Other SmartWatches] Prack:
Wow this looks awesome, any chance it would work on ClearD's rom and other launchers?
[Other SmartWatches] hackerse7en:
not sure about that but il give it a try asap
[Other SmartWatches] cerealpirate:
smb working on this !!!

just a heads up ... I have been running this rom for about a week now and love it. I just installed smb server on here and it works !!!! now i can transfer my files via wifi. Thanks to all the devs that are working on this rom. I would like a different lock screen on here kinda like the ics one would be great ;):good:
[Other SmartWatches] speedyink:
Widget locker
[Other SmartWatches] southbird:
I just bought a MotoACTV this week to play with ROMs ... tried ClearDroid first, but it just felt like it was hanging on too much to its MotoACTV legacy. But this ROM is AMAZING. Very snappy, a lot of fun. Stock keyboard is the only thing that's kind of unreasonable, but the suggested Flit keyboard works well enough.

I originally bought one of those Z1 Smartwatches last year, and was very disappointed at how closed off it is, and also its performance seems terrible... lots of lag. I'll give them credit though that they came up with a better regular keyboard that fit the tiny display. (And of course it can actually act as an [ancient] smartphone, and has a camera.)

MotoACTV can definitely rock Gingerbread. :) No idea if this ROM will ever be developed further, but I think I've pretty much got all the functionality I can expect out of the small package. It's mostly just going to be for geek points for me anyway...
[Other SmartWatches] Saeviomage:
I personally find swype works extremely well, although you need to change DPI and set the screen to portrait to get accept license terms when you first install it.
[Other SmartWatches] southbird:
In the OP, dproldan mentioned that he "bricked" his MotoACTV. I'm wondering if he let the battery run to zero.

Today I let the MotoACTV running this ROM go completely dead, and that put it in a bad state where plugging in the charging cable brought up the "M" logo and ... nothing else. It couldn't even be shut off by holding the power button. I suspect that whatever is supposed to put up the "charging battery" animation gets overwritten with this ROM.

I basically pulled the whole thing apart so I could disconnect the battery, and found that it would charge up a bit ... so once the charger was disconnected, and there was enough juice to do so, it powered up as normal.

I did do an in between experiment where I unplugged the battery, and started it up in fastboot mode; that worked, although I'm unsure whether it was charging. (It probably was.)

Point is, if you let it go dead, you probably want to put it into fastboot to avoid the charging animation and subsequent freeze until it has enough power to get back to normal Android.
[Other SmartWatches] dproldan:
No, when searching for the correct partitions and mount points, I managed to format the whole internal flash memory. All the partitions are gone, including Fastboot, recovery, etc. This one's completely bricked. :(
[Other SmartWatches] ClearD:
Not sure about his rom, but no other roms charge in fastboot. Seeing as it's bootloader related, and I highly doubt he wrote a new bootloader (not that he couldn't if he wanted ;) ), I don't think it was charging, and I have to strongly advise against anyone using fastboot with a low battery, as it only drains faster. Instead, charge the device with a wall charger or a car charger, not a computer USB port. :)

I don't know anything about it, but could you JTAG anything? I've never done anything like that before, but I figure it could be done, and seeing how much more extensive your knowledge is than my own, I'd figure you'd be the one that could figure it out lol. Has anyone even attempted it yet?
[Other SmartWatches] fg:
this mostly worked as a script, but i did have to run repo sync by hand and i had some path issues with lunch.

these build steps have definitely yielded different results from my previous builds... I definitely have to change any Android.mk files by hand to add missing LOCAL_MODULE_TAGS, just change the existing "user" ones to "optionals"

I think I've gotten as far you at this point, with external/bluetooth/bluez/src/adapter.c completely failing to compile. by this time i was too tired to continue and didn't press on
[Other SmartWatches] Prack:
I've let mine go dead for a month or two, never had any issues after connecting to a standard wall charger. Also it does NOT charge in fastboot.
[Other SmartWatches] southbird:
Just to answer all of these ...

Obviously this ROM doesn't distribute a bootloader ... it is only a system image. :) I used all but the system.img from DPRom for the missing files. Not sure if this is related.

To clarify, I'm not using Fastboot, I'm just using it as a mode to go in the watch without it being frozen in a way I have no control over it. Also FYI, since the battery was so low, the watch's behavior is to flash the message "Battery Low. Cannot program." a few times and then it shuts itself off.

After I had posted it, I noticed the battery was in "Unknown" state, and I shut down the watch. It did not turn back on. I'm assuming the battery was effectively dead and it was only running on wall charge. For some reason it got into some kind of bad state and wasn't working with the battery properly. This may have been due to a bad connection to the battery. Once again, plugging it in to the charger caused it to go to the completely frozen "M" screen. I disassembled it and replugged the battery again.

Once again, I went into fastboot to prevent the watch from being uselessly frozen. It flashed the message and went off. I left it this way a while. Came back later, and it had a decent charge and was behaving properly. Working good now, battery and all.

Except for Superuser, which as of yet has never worked right...
[Other SmartWatches] ClearD:
Very weird. Happy that it's working though. And re rooting may fix a superuser issue :)

Sent using XDA-funded carrier pigeons
[Other SmartWatches] southbird:
Yup, used the AnyRoot from MOTOACTV ROMS thread, worked like a charm.
[Other SmartWatches] speedyink:
Hey, that's kinda like what I had to do when I overclocked it and it would randomly drain to 0. I've never let my battery get that low other than that time though, its not especially good for them. Oh, and I never got a frozen m screen when I plugged it in, I got no reaction whatsoever. But going into fastboot with a different button combo (for some reason the standard one didn't work) would flash that message then I could charge.
[Other SmartWatches] southbird:
Yeah, and I could and did charge after the message flashed and went off. Not sure what was causing the frozen screen.
[Other SmartWatches] Jarocks:
I didn't see any noticeable test points on CWM's teardown. Then again a lot of the pictures are out of focus.

Tapatalked from my Galaxy Note 8.0
[Other SmartWatches] alienbiker99:
just around to flashing this and playing aroudn with it. used ClearD's latest rom's boot.img everthing seems to be working well. would love to see this with cm7 too!
[Other SmartWatches] Saeviomage:
Hey dp - could you just clarify that

"Extract each one of those files (except external-webkit) to motoactv_development folder, they have to overwrite complete folders, do not merge!"

means I should be deleting the folders before extracting files to them?

Secondly - do you recall whether you had issues compiling the bluetooth modules and what you might have done to get them going?
[Other SmartWatches] dproldan:
Yes, exactly that.

Sorry, I don't remember specifics. There were many problems while compiling, but searching the error messages in google usually gave me the solution.
[Other SmartWatches] Saeviomage:
Well, I got it to compile, create a system.img, install and run with only one issue (a status bar crash) that your image does not have, so I consider that a decent success.

The status bar crashed due to:

08-07 21:44:12.615 1475 1475 E AndroidRuntime: Caused by: android.content.res.Resources$NotFoundException: File res/drawable-ldpi/stat_sys_signal_4_fully.png from drawable resource ID #0x7f02007d: .xml extension required)

But apart from that, it's a functioning Reactv.

I'm considering putting up a github repository that contains all of the modifications that need to be done to a vanilla android checkout (ie - all the 1.7.11 motoactv sources with the module tag and other modifications that are needed). As far as I know, everything involved is open source. Does anyone have information to the contrary that might stop me doing that?

dp - would you be ok with me putting your vendor and device folders in there too?

I just figure this stuff might be easier if people didn't have to muck about getting things to compile and could just checkout vanilla android, copy these files over and start fixing real bugs.
[Other SmartWatches] willfck4beer:
Any further progress? :)
[Other SmartWatches] Saeviomage:
Well, I pinned down that the only difference between my status bar apk and that of DP's is a difference in the dex file: the resource is present and accounted for.

I also did some more looking into the bluetooth issue. The logcat is full of statements like

08-07 21:47:35.865 1195 1644 E BluetoothService: setRemoteDeviceProperty for a device not in cache:50:F5:20:B3:8E:86

08-07 21:47:36.381 1558 1558 E CachedBluetoothDeviceManager: Got bonding state changed for 50:F5:20:B3:8E:86, but we have no record of that device.

08-07 21:47:36.444 1195 1397 E BluetoothService: getRemoteDeviceProperty: Namenot present:50:F5:20:B3:8E:86

It looks to me like discovery is failing and this is basically screwing up everything. That may make sense, given that the stock MOTOACTV doesn't really 'do' normal discovery.

I haven't had time to look into things further.
[Other SmartWatches] Saeviomage:
Status bar apk is fixed - I think it was just a result of interrupting and restarting a compilation. A recompile fixed the issue completely.

On the topic of the bluetooth bug, I was testing on the train and my watch properly detected an ipad, getting name and all, while at the same time failing to find any other device. Since it wasn't my ipad and I had no idea where the owner actually was, I don't know if pairing would have actually worked.

But still, it narrows down where the issue is occurring. I'm now pretty confident that the issue is in device detection, so it gives me somewhere to focus my attention, although navigating to the other side of dbus from the BluetoothService looks like a bit of a chore... Fingers crossed I can get the ipad I have at home to pair, and I can then see what is different between it and other devices.
[Other SmartWatches] speechman:
I'm really interested in your progress!
[Other SmartWatches] speedyink:
Any progress on this is exciting!
[Other SmartWatches] dproldan:
I made a couple of compilations yesterday, cleaning things a bit, etc

I will post a new preview in the next days.
[Other SmartWatches] Saeviomage:
Good to hear from you again dproldan! Did you manage to reactivate your moto?
[Other SmartWatches] dproldan:
No, that one is dead for good. I bought another motoactv so I could have a development unit and a daily driver. This is the one I'm using now.
[Other SmartWatches] fg:
bane449 had a great tip back in post #29 to move the dalvik cache to the preinstall partition for more space. I've been using this since then. would make for a good option on any new builds
[Other SmartWatches] Jarocks:
dproldan, are you going to sync with the repo on github as well?
[Other SmartWatches] smb_gaiden:
Does this image work with the 16GB MotoACTV? Quite eager to try this out. Thanks!
[Other SmartWatches] alienbiker99:
any updates on the source for getting a cm7 build? with the way google apps are updated now having the best customizable rom would make this watch even better. thanks

Out of curiosity has a jb build been attempted for this watch?
[Other SmartWatches] christiansfreeman:
bluetooth

hey can i connect this rom to my phone from bluetooth? and use apps like tablet talk
[Other SmartWatches] Saeviomage:
The answer is... no, not right now.

However I'm working on it. Currently I'm at the following conclusions:

Reactv, like the base motoactv rom filters out any bluetooth devices from a normal discovery that do not provide headset services (and possibly others - I saw an ios device show up in discovery once). It does this filtering at an extremely early stage - before the data hits hcidump or dbus-monitor. This means you cannot send pairing requests from the motoactv, although you can accept them.

However, even if you start the pairing from another device, the motoactv will not refresh the bluetooth information for non-headset devices automatically. This means it doesn't update the name of the device, or the services offered etc.

Which in turn means that apps making use of bluetooth crash because they fail to find information on a bluetooth device that is clearly present.

It is possible to use hcitool to directly query bluetooth devices and find out their name and services, however as far as I know, none of the command line tools will update the bluetooth cache.

My suspicion is that the original motoactv pairing app is manually filling out this information in the bluetooth cache and that's why we can get things working on the original motoactv rom.

Hopefully the filtering occurs in bluez somewhere. I'm currently trying to track that down, and once I find it I will excise it. If that doesn't turn out to be possible, it may be possible to write some sort of code that forces updating the cache, although that will be notably more complex.
[Other SmartWatches] sirocyl:
Sorry I didn't see this until now, but if you're still watching, I'm running this on a 16GB and it works fine.
[Other SmartWatches] alienbiker99:
any word on updates?
[Other SmartWatches] fernandoavc:
Yep that would be great to hear!

+1
[Other SmartWatches] dproldan:
Yep. Working on it!
[Other SmartWatches] alienbiker99:
awesome I can test if need be. I have a fastboot cable if anything goes wrong.

..Is it safe to delete other mmcblk1 partitions such as the preinstall? in an effort to gain more system or data space
[Other SmartWatches] funnycreature:
I'm also on stand-by for updates!!!!
[Other SmartWatches] fernandoavc:
+1

Every one is willing to see it DPRoldan! ;)
[Other SmartWatches] Saeviomage:
Personally I just move my dalvik cache there and symlink it. Less risk, and all the app space I need.
[Other SmartWatches] alienbiker99:
They have been discussing this on the nook color. im not sure how similar the chipsets are beyond the omap3. but it makes sense as they are combining the userdata/media partition while expanding the system partition. this has has been suggested by google for honeycomb and above. Here the info and the early script not sure if this has been implemented fully yet but i wonder if it can be used for the moto actv. http://xdaforums.com/showthread.php?t=1370873&page=401

http://xdaforums.com/showthread.php?p=49944789
[Other SmartWatches] Newbleeto:
I wouldn't recommend anyone trying this unless you wanna end up with a fancy wrist-brick! Good idea for development though :)
[Other SmartWatches] hackerse7en:
Port roms to motoactv

Hi Dproldan, thanks a lot for yor contribution to motoactv development.

I,ve triyng to port other roms to motoactv using yours, but with no sucess!

I was hoping you or someone in here could give some lights,

First i extract the system.img (using this method)

How do you make a folder became a flashables systems.img (i used this method and it flashes but wont pass the M logo)

If i manage to port it can i make it public?

thanks,
[Other SmartWatches] tigercat:
Try making your system.img with ext3 file system format, not yaffs2-sparse format.

Hint:

https://github.com/dproldan/android_device_motorola_G2/blob/master/mk_system_img_commands

Or,

Just modify base rom:

1. Unzip base rom (ReACTV preview 18 = systemPreview18.zip).

2. Rename unzipped base rom from systemPreview18.img to system.img.

3. Mount rom file to folder.

$ sudo mount -o loop ./system.img /somewhere/you/want

4. Modify files as you like under /somewhere/you/want to make your customized or ported rom.

5. If finished, then unmount.

$ sudo umount /somewhere/you/want

6. Unmounted system.img file is now your customized rom. Enjoy!

If you find some trouble in your customization, back to 3.
[Other SmartWatches] hackerse7en:
thanks a Lot, as soon as i get home ill give it a try and brick it again :D ahah
[Other SmartWatches] mtvdeo:
This is the most amazing rom EVER

- ADW launcher + hide status bar

- Android 4.4 theme for kitkat icons

- No lock Screen App

- UCCW widget

- UCCW android wear widget

= you've got an android wear watch!
[Other SmartWatches] Prack:
Did a similar thing, not sure if mine works as well as yours but i used UCCW widget with Wear UCCW. Set 4 screens up all with clock at top and gmail, messages, weather and calls all on the bottom of their own screens. Looks cool, not as functional as I would like it to be though.
[Other SmartWatches] conmonks:
Does this have... before i buy.

I will plan on buying this MotoACTV, but was seeing if the audio input was ever fixed? looks promising
[Other SmartWatches] chadbot3k:
do you have screenshots, or pictures? would really like to see your setup.
[Other SmartWatches] fernandoavc:
+1

Enviado de meu Nexus 5 usando Tapatalk
[Other SmartWatches] pdrift:
I realise this is a long shot due to how late I am to the party, but after flashing this rom, how do I get into cwm?
[Other SmartWatches] ClearD:
Plug watch into computer, start adb command prompt, issue command: adb reboot recovery
[Other SmartWatches] pdrift:
Thank you, I managed to do it after posting but I didn't get a chance to comment on here until now. I installed the USB enabler app so now I can do it from there. I like this rom a lot, the only problem is I ran our of space already lol.

---------- Post added at 05:18 PM ---------- Previous post was at 05:12 PM ----------

Does anyone have directions for doing this?

I know I have a couple optimus v's and in the version of cwm running on then there was an option to partition the SD card to use with link2sd. that would be nice to get working on the motoactv but I don't have the now how to do it.

I'd like to use bane449's trick to get more space if someone can help me out.
[Other SmartWatches] pdrift:
I've still been trying with no luck to symlink the dalvik-cache. I don't know exactly what to do so I went in es file explorer with root permision enabled and mounted as read/write. I went into the preinstall folder and just deleted everything. Then using smanager i created a script (mount -o bind /data/dalvik-cache/ /preinstall/dalvik-cache). I made sure to check root and boot and saved it. I even went and made the dalvik-cache folder manually in the preinstall folder. After rebooting nothing changed. I've also tried using gscript lite with no luck. All I want is to have some space. I even tried to repartition the internal sd with gparted so I can use link2sd. Tried resizing the sd partition and wanted to create a 500MB sd-ext partition formated as ext3. Gparted would not let me create another primary partition so I didn't apply anything.

Can anyone give me some pointers? I just want to be able to instal some apps without constantly running out of space. I just watched a video on youtube of some guy running GTA III on his motoactv. How does he fit that and I cant even update my apps.. ARGH!!

On the plus side I can run tasker on this ROM. I've been playing around with some scenes to keep me busy lol.
[Other SmartWatches] Micopero:
Thank you for the hard work !

Till now it is the best ROM for Motoactv, this is really precious, thank you for putting time in this, God bless you :)
[Other SmartWatches] pocketedgejr:
Not sure if anyone uses this still, tried experimenting with it but everytime Google Play services dumps its fat but all over my limited free space.

and I go from nothing installed to nothing installed and running out of space alert. Anyone have a solution? (I'm guessing don't install gapps is the only answer)
[Other SmartWatches] SashSheen:
Can you provide the instructions please?

---------- Post added at 08:29 AM ---------- Previous post was at 08:23 AM ----------

Did you get this working?
[Other SmartWatches] CadBuRy.VN:
Till now it is the best ROM for Motoactv :)