yashsingh1/xdaforums huggingface dataset:
[Milestone XT720 Android Development] Mioze7Ae:
What you have to do is modify the framework so that you create a file called /cache/.boot_to_or and then do a normal "reboot" (not "reboot recovery"). OpenRecovery requires a normal boot, but "reboot recovery" sets some flags somewhere that the bootloader reads to boot the recovery.img instead of boot.img. (IIRC the android framework doesn't actually run "reboot recovery", it makes the calls to the kernel to set the flags and reboot). Here's how I did this in Dexter's ROM:

https://github.com/Mioze7Ae/XT720-patch/tree/master/powermenu

The "original" directory is the unmodified smali and the "modified" directory has the modified smali. You can use something like WinMerge (windows) or meld,kdiff3 (linux) to compare the files and see what I changed. IIRC the actual reboot stuff is in:

https://github.com/Mioze7Ae/XT720-p...com/android/internal/app/ShutdownThread.smali

It may be more complicated than necessary--this was one of my first serious mods and I may have diagnosed problems incorrectly. One trick is that part of the framework doesn't have permission to create "/cache/.boot_to_or". So I first tried to create a suid shell script, but on Android, SUID shell scripts are forbidden. SUID binaries are allowed.

My first thought was to just call "reboot openrecovery" after making /system/bin/reboot suid. I didn't like that because it interrupts Android's shutdown code and reboots immediately. So I decided it would be better to let the shutdown thread just create the /cache/.boot_to_or file and then just reboot normally. So instead I created a /system/xbin/boot_to_or binary that just creates /cache/.boot_to_or (must be suid see line 84 of https://github.com/Mioze7Ae/XT720-p...META-INF/com/google/android/updater-script.in).
[Milestone XT720 Android Development] creamoncrop:
will this work on a Motoroi? Korean SBF?
[Milestone XT720 Android Development] spectacle:
Is this rom much faster than miui ? Going to switch soon
[Milestone XT720 Android Development] Woody:
I have the only one market download at a time issue also, as well as the seemingly looking like it is downloading twice but really only one will be downloaded. Also cannot dl any paid apps either. I just restored using TB but not sure what the problem is with that.
[Milestone XT720 Android Development] JiroPrinz8:
Ok so just flashed this a couple of hours ago and I must say I'm somehow very lucky, haven't had a bootloop, reboot or anything like that..

ext works very well, had to reinstall apps that are FCing which is quite normal with the other ROMS, market automatically updated default apps (google, youtube) although haven't had the chance to know if the market itself has updated to the new one.. will check that out later (as I have to look at how the new market looks like so I can tell) haven't tried recording a vid yet, will edit once I do, swap is working as well, 100mb at startup and now down and stayed at 77mb..

games are freakishly fast..!! Cut the rope, samurai vengeance working flawlessly..

what can I say, am loving this rom thus far.. I dunno how one would qualify to be called beta but after hotfix6 I'd say this rom is pretty stable.. well for me personally..

amazing job to MZ as USUAL!!

And again, would love to see "recognized developer" under MZ's name, having him have the same tag as myself (senior member) is almost like an insult.. LOL..!! Lovin this one seriously! Thank you!!
[Milestone XT720 Android Development] chandanbs:
Hello ktylife,

i disabled usb debugging. still i am not able to fire up usb mass storage for my micro sd card. Looks like something is broken.. :(
[Milestone XT720 Android Development] Mioze7Ae:
I just tested and I am able to toggle and use memory card access both with and without usb debugging enabled.
[Milestone XT720 Android Development] ltwvince:
Right now is pointless to use link2sd as all installed apps are automatically moved to ext3 (app2ext). The reason link2sd works is because ext3 was mounted to /sd-ext on boot. Apps will be linked from /sd-ext/app to /sd-ext folder.

The only different I can see when using link2sd is the /data/dalvik-cache will be linked to /sd-ext/dalvik-cache folder for the link2sd app.
[Milestone XT720 Android Development] ltwvince:
Mioze7Ae, how can I remove app2ext support? As I would like to use link2sd only.

Just remove app folder under /sd-ext?
[Milestone XT720 Android Development] chandanbs:
anyone has tried out cyanogen mod themes on this rom?

and for instance dialler skin.. etc..:-)
[Milestone XT720 Android Development] Woody:
I would imagine that if app2ext is enabled, you could just put a folder in sd-ext/link2sd and it should work as long as you have the ext3 partition in there (reboot). Think that I read a few pages back that one of the Hotfixes enabled this to work.
[Milestone XT720 Android Development] Mioze7Ae:
No, I think /system/etc/init.d/07app2ext will just recreate it.

Basically, we need to edit 05mountsd and 07app2ext to make them understand link2sd. As a workaround, you could maybe disable both of those for now (I think renaming them so they don't start with two digits is enough or you could delete them--hotfix6 will erase and restore the entire init.d directory if you had to go back), but you'll also have to move your installed apps back from /sd-ext (or just assume factory reset). Link2SD's own script should be able to install and work then, but be aware that Link2SD's script has not been very robust in the past. Anyway if you're comfortable tinkering at that level you should be able to get that working until I work something more permanent out.
[Milestone XT720 Android Development] ltwvince:
Nah.. I can guarantee you that won't work. ;)

I have that folder since dexter's ROM.
[Milestone XT720 Android Development] ltwvince:
I'll give it a try tomorrow after work as here is almost 12 midnight (GMT+08). Thanks. :D
[Milestone XT720 Android Development] gera_nium:
Great Archievement! Mioze7Ae

Billion thanks to Mioze7Ae:D, i know you're the one who finally can make CM available for us. This ROM i'm waiting for...This my comment and hopefully could help us also

Notable issues:

•Do not select 1% battery increments (see post #7) - not test yet

•The default keyboard has very, very small keys. You can select the Korean keyboard or download another. - recommend to change to korean keyboard

•FM Radio does not exist and will not work.tested and yes, install_failed_missing_shared_library

•Video recording not extensively tested -- but, hey, it doesn't crash the phone immediately anymore.great and can use, eventhough SE x10 also failed and blur

•Gallery button does nothing i can use, show images as usual

•Haptic feedback is not pleasant when enabled - agree

•RomManager is dangerous on XT720- agree

•Reboot recovery goes to motorola's recovery- is true, maybe fix in next RC 0.11

other than that,

GPS fix, well done with aura sygic:)

Wifi fix, no issue at all, turn on/off no problem:)

MilestoneOverclock1.48, no issue ;can be use

recommend by milaq, use below new market if not success with stock

New Market (v3.0.26) as update.zip: New Market (v3.0.26)

:) for improvement, i think we need to get better minfree settings (to many apps running in background)...now use autokiller memory:)
[Milestone XT720 Android Development] tharan.a:
haven't had the time to flash this yet, but has anyone run quadrant? also, how stable is it? I'm pretty sure, going forward...this is the ROM to flash. Nice job Mioze7Ae, really appreciate the work!
[Milestone XT720 Android Development] reverendkjr:
Overclocked to 1000MHz, Quadrant gives a consistent 1250-1300 score, which is what I have been getting from other builds as well.
[Milestone XT720 Android Development] Woody:
That is about what I am getting too, with minimal tweaks. Think I got close to 1400 but that was OC'd at 1100. Somehow LibertyMonger is getting consistantly close to 1600 on the Special. Not sure how but on this ROM, the more I tweak it the better Quadrant results I get.

As I have said before, I don't put much stock in Quadrant scores b/c I was getting 700-900 on 2.1 and it was just as snappy and sometime faster as everything we have now.
[Milestone XT720 Android Development] khalpowers:
when saw this thread think need to fix my xt soon...:)...
[Milestone XT720 Android Development] mchlbenner:
I have mine right know only overclocked to 650 and fast as hell no lag at all no memory leaks this the BEST ROM i have ever used.

Ps. Battery life is great.
[Milestone XT720 Android Development] B_e_n:
I m the only one who see the haptic feedback menu in cyanogen mod settings!!!???

You can test it at all power of feedbck... (I put 25 for me)
[Milestone XT720 Android Development] molohov:
I have been running this ROM all day and it is incredible! Very stable, very fast with no overclocking. Also, great to see all the little CM features which are super useful ;)

Not to get too off topic here, but regarding themes I've been experimenting with a few meant for CM6 HDPI devices and they have been unsuccessful. I will probably start a new thread in the Themes/Apps forum if I can get any results. If anyone has any success, please let us know!

Thanks Mioze7Ae for this excellent rom. I will continue to monitor this with great interest!
[Milestone XT720 Android Development] mchlbenner:
I don't think so use j.y.daddy builds they were built for motoroi.
[Milestone XT720 Android Development] creamoncrop:
Ok. Thank you.

Sent from my Motoroi XT720 locked. :(
[Milestone XT720 Android Development] eejin2:
3g mobile hotspot and USB tether doesn't work on my phone....
[Milestone XT720 Android Development] donovanx3:
I've been using this rom for a while now (and i like it) but ever since I started using it (6.3.0 RC3) when I take a picture with the camera, the phone freezes and the camera app crashes. What can I do? Thanks.
[Milestone XT720 Android Development] space4ace:
Do you have the latest build (6.3.6.2)?

6.3.6.2

New test build

NOTABLE CHANGES:

Updated to latest AOSP froyo release (2.2.3)

build: Platform bumped to 2.2.3

dalvik: "Blacklist diginotar root and cross-signed certs"

libpng: "update to 1.2.46 to fix a few vulnerabilities"

Browser: "Prevent webview reuse"

Browser: "Prevent loading javascript: uris in existing tabs"

core: "Validate sender credentials on netlink msg receive"

netd/vold: "Enable the SO_PASSCRED socket option"

system/wlan/ti: "bind to loopback interface only"

Some other updates between 2.2.1 and 2.2.3 had already been merged in CM6

Fix control of LCD backlight and hardware button backlight

FM radio loudness should be improved

Toggle 2G/3G re-added

KNOWN ISSUES:

Hardware button backlights seem to not behave correctly -- workaround: disable button backlight see post #1106 below

Selecting 1% battery will break your mother's heart. You wouldn't want to break her heart, would you? 1% battery option deleted

HD (720p) video recording not available -- workaround: pretend D1 is HD because D1=720×480 and 720 implies HD

8MP wide not available -- workaround: crop the image by hand

Phone orientation not stored correctly in photos/videos -- workaround: neck brace, move to ISS, reject society's imposed notions of "correct" orientation

Orientation incorrect on modxt720 sbf -- workaround: disable auto-rotation Use sensor fix for modxt720 sbf here: http://xdaforums.com/show...6&postcount=48

Screenshot doesn't work

DOWNLOADS:

update-cm-6.3.6.2-MilestoneXT720-KANG-signed.zip (73.63 MB)

Milaq's gapps-hdpi-20111001-signed.zip (17.92 MB) multiupload mirror

Instructions (fresh install):

Place update-cm-6.3.6.2-MilestoneXT720-KANG-signed.zip and gapps-hdpi-20111001-signed.zip in /sdcard/OpenRecovery/updates

Boot to OpenRecovery

(recommended, optional) OR > nandroid > backup

OR > Apply update > update-cm-6.3.6.1-MilestoneXT720-KANG-signed.zip

OR > Apply update > gapps-hdpi-20111001-signed.zip

OR > Wipe Data / Factory Reset

Reboot

Upgrading from 6.3.5.3 and earlier:

Untested. Possibly issues because of the gapps swap.
[Milestone XT720 Android Development] 3rdstring:
I would try reformatting the sd card. Most of the issues I've had go away with a freshly formatted card. (Make sure to back up anything you want to keep)

I think 6.3.6.2 is the most recent build.
[Milestone XT720 Android Development] space4ace:
3rdstring: Doh!!! :eek:

I just fixed the reply to 6.3.6.2.

Thanks!
[Milestone XT720 Android Development] donovanx3:
Ok thanks. I will reformat my SD card and try to update to 6.3.6.2. Currently my rom reads 2.2.1 not 2.2.3 and the build number is R.U.R.1920. It only says CM6 6.3.0 RC3 so will I have a problem updating through open recovery and do I also have to update my gapps? Thanks
[Milestone XT720 Android Development] 3rdstring:
You will have to re-flash a gapps package & you might have to do a Factory reset coming from 6.3.0.
[Milestone XT720 Android Development] donovanx3:
Ok thanks!
[Milestone XT720 Android Development] eejin2:
@mz I remember from the very long ago cm6 builds,we could adjust the screen brightness in the settings to its minimum (totally dark), and I like that cos I use my phone in the dark.is there any way you can put it back?
[Milestone XT720 Android Development] Mioze7Ae:
Yeah, I've noticed that problem lately, too. My assumption has been that the problem is related to xt720modsbf. Are you running xt720modsbf? I'm also having a lot of trouble with the autobrightness.
[Milestone XT720 Android Development] brianlili:
Hi, Mio, are you going to port moto's camera into this rom?

And one more thing, can you release a deodex version at the same time?:)
[Milestone XT720 Android Development] Mioze7Ae:
Yes, that's what I'm working on mostly. But as your second question hints at you might imagine I haven't yet figured out what changes were made by wqy88. Mostly because I haven't figured out how to separate the changes caused by deodexing from the actual smali edits that are important. ;)

But, yes it would be easy for me to build both a deodex and an odex version. Maybe I'll just go ahead and do that today even though there aren't many major changes. Basically the only noticeable change is that long press on the notification power menu works as a shortcut to the relevant settings panel as in CM7 and the new sensorfix for xt720mod.sbf. I've fixed the smali incorporation with odex builds, but we don't have many smali injections yet so that's more of a back-end thing not very noticeable to users.
[Milestone XT720 Android Development] brianlili:
I know how to work out all stock rom's stuff through smali editting, but I don't know if all your framework files are compile from source, if so, I can give you java sourcecode.
[Milestone XT720 Android Development] Mioze7Ae:
Yes, just about all of it's from source. The only things that we don't have source for are the files here https://github.com/CyanogenModXT720/android_vendor_motorola_sholest/tree/froyo/proprietary

So currently all of the CM6.3 framework/*.jar comes from java except for a few very small injections related to the location service and spellchecker https://github.com/CyanogenModXT720/android_device_motorola_sholest/tree/froyo/smali (these were inherited from nadlabak/milaq's umts_sholes CM6 and I haven't really paid much attention to them)
[Milestone XT720 Android Development] brianlili:
Ok, so let's do it.

First, in framework folder, add com.motorola.android.camera.jar, **.mediasync.jar, **.aui.jar. all of them took from motoroi's rom. and add permissions in /system/etc/permissions/platform.xml. I think Peshovec have figour it out already.

Then, add moto's components to framework.jar. all classes inside two folder named "motorola", and all classes begin with "camera" in /android/hardware need to be added in(or replace). I mean take them from motoroi's framework.jar too.

Third, make android.policy.jar send media_key broadcast. I still don't know how to define a keycode yet, but we can use existing one like "NUM". add "key 112 NUM WAKE_DROPPED" to files of /usr/keylayout.

That is all mods in framework, I think.

Librarys part:

libpanorama_jni.so, libpanorama.so, libcaps.so, libscalado.so,libmot_led.so,libcamera.so, libcameraservice.so, all lib in /system/lib/dsp/, all lib begin with libOMX.TI.* and libopencore* in /system/lib, libmediaservice.so.

Other files: /system/etc/media_profiles.xml， /system/etc/01_Vendor_ti_omx.cfg，/system/etc/cameraCalFileDef.bin

Now, all things should working good:)
[Milestone XT720 Android Development] Mioze7Ae:
Ok, I'll try it this evening :D

Just to clarify, you replace these files with version from motoroi?

framework.jar android/hardware/Camera$Size.smali

framework.jar android/hardware/Camera$Parameters.smali

framework.jar android/hardware/Camera$OnZoomChangeListener.smali

framework.jar android/hardware/Camera.smali

framework.jar android/hardware/Camera$AutoFocusCallback.smali

framework.jar android/hardware/Camera$PreviewCallback.smali

framework.jar android/hardware/Camera$EventHandler.smali

framework.jar android/hardware/Camera$1.smali

framework.jar android/hardware/Camera$ErrorCallback.smali

framework.jar android/hardware/Camera$PictureCallback.smali

framework.jar android/hardware/CameraSwitch.smali

framework.jar android/hardware/Camera$FaceDetectCallback.smali

framework.jar android/hardware/Camera$ShutterCallback.smali

framework.jar android/hardware/HtcFrontFacingCamera.smali

framework.jar android/graphics/Camera.smali

framework.jar android/media/CameraProfile.smali

Edit: after more careful reading
[Milestone XT720 Android Development] eejin2:
yes, im on modsbf with part 2. I dont use auto brightness though. I just liked how I was able to adjust the brightness to very dim for use in the dark. do you think the problem will be fixed if i go back to a regular sbf?
[Milestone XT720 Android Development] Mioze7Ae:
I'm not sure. I sort of expect that if you were using the part 2 method, then it should be the same as running on a regular sbf because it should have the correct kernel and devtree for the hardware. But it's entirely possible that there's another piece I haven't found yet. On my phone I've been using sensorfix.ko lately instead of the part2. I just can't remember when the brightness problem started... I was so focused on the rotation. Sorry. I'll get to it eventually.

I know at one point there was a strange thing where you could use the advanced settings to set the lowest brightness, but you had to turn the screen off for a few seconds before the new setting would kick in. But I can't remember if I was doing that on part2 or sensorfix. Anyway check your settings in

Settings > CyanogenMod settings > User interface > Automatic backlight > Use custom & Screen dim level

That setting defaults to 20 and seems to define the lowest value you can use. IIRC manual setting was working fine (after turning off the screen once), it was the automatic that wasn't working correctly. I kind of also like CM7's drag-on-the-notification-bar-to-set-brightness so that may appear at some point.
[Milestone XT720 Android Development] brianlili:
Yes, all recourses took from motoroi's stock froyo. you are right, last three files no need to be take care, leave them alone.
[Milestone XT720 Android Development] eejin2:
okay thanks! that was just what i was looking for! now i can dim my screen brightness much lower than the default one. :D

I look forward to that too! Keep it up on the good work!
[Milestone XT720 Android Development] Mioze7Ae:
I'm having the darndest time with this. I've been stuck at (M) for a while. I think I did everything except for I did not do this part yet:

I also added CameraMoto.apk and Camera.apk from 50R. I couldn't find libmediaservice.so but I think you meant libmediaplayerservice.so.

Anyway, here's a deodexed version built yesterday without any moto-camera-related changes (does boot and works fine):

update-cm-6.3.6.3-MilestoneXT720-KANG-signed.zip (deodexed, 73mb)

http://depositfiles.com/files/ynx39rgw3

And here's the update I've been working on (useless so far, gets stuck at (M)):

cm6-motocamera-20120315-2008.zip (10.6mb)

http://depositfiles.com/files/g2vrugyxf

I've been testing by:

1) flash update-cm-6.3.6.3-MilestoneXT720-KANG-signed.zip

2) flash gapps-hdpi-20111001-signed.zip

3) flash cm6-motocamera-20120315-2008.zip

4) wipe & reboot
[Milestone XT720 Android Development] brianlili:
That is weird, I did it twice with froyo and gigerbread， they both work well. Is there any differences between smali compile and source compile?
[Milestone XT720 Android Development] Mioze7Ae:
Well, in this case I also did smali after compile. Maybe my baksmali/smali are messed up.

I also noticed that the libraries and such in ChronosX aren't all from 50R, so maybe that's part of it. I'll keep at it.
[Milestone XT720 Android Development] brianlili:
Thanks. I'm downloading them. Have you try to remove framework.jar from the update pack? I think lib won't cause "stuck M", wrong lib will cause error in taking photo or video record.

when download finish, I can try it too.

Edit: I just noticed, framework.jar from update pack have the size of 6.5MB, not a good sign:)
[Milestone XT720 Android Development] Mioze7Ae:
I think you're right-- A baksmali/smali loop with no changes is turning a 2.9mb file into a 6.4mb file. So something's wrong with my tools. Thanks for noticing that!

Edit: DOH! I always forget that you can "baksmali framework.jar -o framework" but "smali framework -o framework.jar" creates a classes.dex named framework.jar NOT classes.dex inside a jar. UGH. Someday I will remember this.
[Milestone XT720 Android Development] brianlili:
Yep, I make a working one.

http://depositfiles.com/files/1goip2806
[Milestone XT720 Android Development] Mioze7Ae:
You're awesome!
[Milestone XT720 Android Development] brianlili:
Cann't wait for your perfect release:)

And It seems I have a little question, I flashed deodex 6.3.6.3 version(update-cm-6.3.6.3-MilestoneXT720-KANG-signed.zip), phoneprovider, hiddenmenu asking for root permission, is that normal?
[Milestone XT720 Android Development] Mioze7Ae:
I noticed that too. I don't remember that happening before. I'm not sure if it's related to Toggle2G... it used to always show up as "radio" requesting superuser permissions. I changed the way Toggle2G is added by the build system--previously I signed it by hand, but now it gets signed by the build process. But it could be something else. I need to investigate it further.
[Milestone XT720 Android Development] DarkMD:
can someone share themes for cm6.3.6? xD
[Milestone XT720 Android Development] Mioze7Ae:
I don't think it's toggle2g anymore. It's the motorola proprietary applications (PhoneConfig.apk, ProgramMenu.apk, ProgramMenuSystem.apk). They must detect that su is around and try to do things. I don't remember it before but it must have been there in the past. Those apps are there because they were there on milaq's CM6. But they're not included in fjfalcon's CM7, so probably they can be purged... I just deleted them on my phone and I haven't experienced any problems yet.

I've got the stock Camera and MediaGallery integrated in the build, but I haven't debugged HD recording yet--it records and the preview overlay during the recording looks fine, it's just the saved videos are garbled. Adding the ro.media properties to build.prop didn't seem to have any effect.
[Milestone XT720 Android Development] peshovec:
I am planing to add choice for my test build.

native: use cm camera (default)

e.g. as build

update script: purge (if have to) cm camera, replace framework cameras smalis, use motoCamera

e.g. modify the framework.jar (replacing with motocamera's smali's) and provide the change as update script.

however, i still did not figure how to "decompile" the odexed framework.jar (or how to easy grab non-odexed copy). My goal is to leave the odexed build, then automate the generation of the update script ( smali replacing , etc..)

Do somebody have any idea how to achieve that (if possible avoiding generating non-odexed framework.jar, but deodexing existing one, modify and odexing will be fine)