yashsingh1/xdaforums huggingface dataset:
[Milestone XT720 Android Development] Mioze7Ae:
Ah, too small max heap size is what keeps angry birds from running. At 24mb it won't start, but it does start at 32mb+.

Elsewhere (well, a discussion on HN by android developers about "android fragmentation" and the challenges of writing an app that performs well in both froyo and gingerbread) I've seen the expectation that froyo has maxheap no smaller than 24mb and gingerbread no smaller than 32mb. There wasn't really a reference in that discussion, but it seemed to be accepted knowledge and it wasn't challenged. So, anyway, I wouldn't be surprised if angry birds also makes the assumption that gingerbread has a 32mb heap.
[Milestone XT720 Android Development] peshovec:
if that's not just the wifi, but also the data connection, it can be some proxydns race ...

as this race is affecting some phones, and not other it is hard to debug and fix...

so i personally use the following workaround:

in the init.rc file (/system/etc/rootfs/init.rc) i have added

export ANDROID_DNS_MODE local

near the other exports.

which bypasses the dnsproxy and since then i have no issues with connections

@mio about heap size and angry birds, sometimes angrybirds starts with 24 heap, sometimes doesn't . probably you are right about the vm sizes (anyway, nfs shift doesn't start regradless of the vmheap size value...)
[Milestone XT720 Android Development] B_e_n:
No it works with the data connection it s just the wifi... I never had disconnection with the data

Maybe it s just me but i think i had this problem on all the CM7 rom which the notification wifi icon change from green to white...

I try zepellinrox wifi fix but no change...
[Milestone XT720 Android Development] peshovec:
try the above dns anyway...

trying to slide the above onscreen
[Milestone XT720 Android Development] B_e_n:
To make you happy i m gonna try it

But it can be it i know i m still a noob but this is simply logic...

When it s connected to the wifi it seems to stay connected but don t work (so it can be the dns) but when the wifi is on but no connected (when you re out for example) and you get your wifi network it can see all the network around but cannot connect (it block at the authentificating step and after the 3 attemps it stay disconnected...)

It s not always happening but very often when the wifi is on for a long time
[Milestone XT720 Android Development] acrobat69:
Yep, what I call "the WIFI/3G switching problem" was what prevented me from going any further with this rom. I didn't post anything in this thread because a. I was already yapping about it in General and b. I saw noone else with the issue and figured "it's just me". So I'm not happy that others are experiencing it but maybe there is something to be fixed here. I'd love to give this rom a further workout but without that issue fixed it's a no-go for me.
[Milestone XT720 Android Development] AllGamer:
perhaps this might be useful

on WEP, WPA and WPA2 from regular home level access point / routers it works fine

however on enterprise level WPA2 with additional security options, it behaves erractic

basically it works for like 2 minutes, then it dies, even though it still shows that it's connected

so you have to manually disconnect WiFi, and connect it again, the it stays for another 2 minutes and it hangs again

however on my other 3 phones connecting to the same enterprise WiFi, using the same credentials, same everything, it can stay on forever without disconnecting.

does the CM7 WiFi have any cookie or proxy or some sort of hidden expiry timer thing/setting we can set to a longer period of time?

that's the result after testing it at 2/3 different locations

on coffee shops without passwords or with password, it works fine as well

seems to only affect business/enterprise level authentication WPA2, it comes from a CISCO box, not sure about the exact model

but if anything it might be similar to the WPA2 Enterprise available in the DD-WRT routers

hope those 2 clues help to find the real issue behind the disconnections :)
[Milestone XT720 Android Development] acrobat69:
Interesting...I was not using enterprise WPA2 on my old d-link when I tested this rom. Just plain ol' WPA personal. But it was a d-link, so there's that.

Think I'll give this one a whirl soon using my new router, and see what happens. That one is set to WPA2-Personal so that the laptops can take advantage of the 300 mbps speed..

Anything I should know about a 2nd partition and this rom? I tried to create a 2nd one in MiniTool to use with an MIUI rom but link2sd couldn't see it. Hope I don't run into a similar thing on this one...I'm just making 2 FAT32 partitions as from what I could gather reading the various threads 2.2 and up roms can use FAT32 aok with no need for the ext2.ko fix.. (true?)
[Milestone XT720 Android Development] Mioze7Ae:
acrobat69, the CM 6.3.6.1 test build I just put up finishes some changes to the wifi stack. If you're up for it can you test if wifi/3G's giving you problems there? If not, I'll port the wifi changes to the CM7 branch.
[Milestone XT720 Android Development] acrobat69:
Absolutely! If you want, port them to the CM7 branch also, and I'll test both.

I was actually going to go back and try that one again also now that I have the new router.

Can you help me a bit with the whole ext/2nd partition thing? I'm using Minitool, setting approx 14 gb of my 16gb card to Primary FAT32, and leaving cluster size at Default. I then create a second partition with the remaining space (about 2 gb), also FAT32 and Primary. MiniTool reports the following message: "The newly partitioned disk cannot be used in Windows.." I just accepted that and continued on. Later, however, when Link2SD was installed, it couldn't "see" the second partition. Have I missed something?
[Milestone XT720 Android Development] Mioze7Ae:
A few comments/tips you may or may not have seen that may or may not be relevant:

(1) never partition using USB mode with the card in the phone--put the card directly into the PC using a card reader etc.

(2) all partitions must be primary partitions--our kernel doesn't grok extended partitioning.

(3) supposedly, the first (main FAT) partition must be "active"/"bootable"
[Milestone XT720 Android Development] acrobat69:
Ok got it up and running..and turned off the backlights ;)

WiFi: seems to be stable now. If you recall tho I was having problems with being able to have WiFI, or 3G, but not both (consistently). I noticed a few times that when using WiFi I lost 3G connection. However, it isn't happening every time, and so I'm putting it down to being a "bad Wind period" for now.

I also successfully got Link2SD up on it. (yay!) I think your advice to do the partitioning and formatting via card reader was the clincher. At any rate, when I flashed 6.3.6, manually created a directory in sd-ext called "link2sd", installed Link2SD and then rebooted, the app worked and I was able to link over Gmail, Facebook, and every other app that I downloaded. Key there is uninstalling the app first if it comes in the rom by default, and then re-downloading from the market. Then you have control over it.

One thing of note: Last night when doing all this stuff, mind you while charging, my battery went to 42 degrees and took a LONG time to come down..it was scorching. I had to unplug it and put it in Airplane mode just to get it down to 40, so finally I just shut the phone down completely for the night. I hadn't even overclocked yet. This was because I was using 3G to download and install apps. So the 3G data connection causing extreme hot conditions still persists the same as it did with stock. I don't know if it's been reported or if there's anything you can do about it but it is worrisome! As I type right now, with 3G data off and WiFi on, the phone is charging and my battery temp is hovering between 36-38 degrees. I'm overclocked to 1000mhz, 60v, with Interactive scaling.

So so far so good, I was able to take videos and pictures no problems, browse, put apps where I wanted them etc. The only thing I haven't done is actually make a phone call (yet).

I think you should port over your WiFi fix to 7.1! I'd love to try that one out, also!
[Milestone XT720 Android Development] rs_nuke:
USB Driver/Problems?

Wihth Cyanogen 7.1.0 (Dec 19) I cannot get the XT720 to connect in USB mode with my PC... Adb list no devices... Heck USB driver on windows doesn't recognize anything is plug in... argh...

Nor does the XT720... normally it would give me a chose to charge or have card access... nothing...

Any ideas why? I see alot about usb.apk (opensource) which is included in 7.1.0... can I put something else? The only other time I have USB working was with Dextors Android 2.2 ROM...
[Milestone XT720 Android Development] nrgaway:
Plug USB into computer; unplug it; then plug it back in again. Computer will not see it the first time it is plugged in. Wait a few seconds or more between steps
[Milestone XT720 Android Development] Mioze7Ae:
I went to go look into making a baseband update for Wind and I realised I already made one. ;) Do you use it?

If you're using OpenRecoveryXT720 (link in sig), you can select the Wind baseband update via

OR > Change baseband > XT720-Canada-Wind.zip.

If you're using the original OpenRecovery or Androidiani OpenRecovery, you can download the baseband update as an update here: http://xdaforums.com/showthread.php?t=1241685
[Milestone XT720 Android Development] acrobat69:
I don't think I've changed my baseband. ETA: I see in your thread that you described making a nandroid of /system, I'm assuming this is where my current baseband is located. I will do this, for sure ;)

Also, just out of curiousity, why did you create an update for the Wind baseband, was it related to 3G issues?
[Milestone XT720 Android Development] Mioze7Ae:
The baseband update just changes files inside /system/etc/motorola (i.e. system.img) so I think it's no more risky than flashing any custom ROM and a nandroid of system.img will let you go back. I created it because I was sometimes having problems with Cincinnati Bell (sometimes when the signal was low, my phone would get really hot and drain battery like crazy and android would report cell standby as using all the power). Milestone A853 has baseband updates, so I created an update for Cincinnati Bell's baseband files and it seemed to work. So I did the same thing for all the other sbf's (for Wind I used S7ticky's nandroid since we don't have the original sbf).

There is a separate baseband software partition but the only way I know to modify it is to flash a sbf. I personally don't ever touch that partition except when flashing a sbf. It's listed in nandroid in Androidani and regular OpenRecovery but it always errors when trying to back it up. It could be because the baseband is actually running in bootstrapped recovery. Anyway, I wouldn't touch it. There's some other wierd stuff going on that I don't understand, for instance the cust.img contains a copy of /system/etc/motorola and on some phones that gets mounted as /system/etc/motorola but the stock system.img also has an identical copy of those files and stock doesn't mount cust.img (at least on the stock XT720 ROM I was studying). It's weird and the update works for CBW which is the only one I can actually test so I just don't touch the rest.
[Milestone XT720 Android Development] fjfalcon:
Hey, i not say it's finished.

I have many thing to do.

Next build plan:

usb working,

media key working(without led, maybe with leds)

torch,

will also try to once again fix camera =)
[Milestone XT720 Android Development] mchlbenner:
The GPS doesn't work it crashes.
[Milestone XT720 Android Development] peshovec:
just checked

my testing are ok (e.g. compiled:)

i was trying to "backport" the motorola 720 capabilites in the hardware omap3

good news, the changes did not break the build:)

the bad news, did not test the build....

the build setup is

android from nadlabak

https://github.com/nadlabak/android

(repo synced today)

android_device_motorola_sholest from my git

(actually it is almost the same as fjfalcons, synced up to date at the moment)

https://github.com/fjfalcon/android_device_motorola_sholest

(my relevant changes are some settings about brightness level and other minors in xmls....)

android_hardware_ti_omap3 from my git

(forked nadlabaks, and "meld-et" manually the moto originals)

https://github.com/peshovec/android_hardware_ti_omap3

honestly i am not sure what are the difference with fjfalcons build

i am uploading the build now in the playground area at my git

p.s. i have edited my previous post, but who looks old posts? so...

in the moto stock ecalir /system/bin/bootanimation there is code which enables the touchscreen, e.g. the stokc bootanimation binary do the job of the touchroi binary... this code fragments (checked with strings grep qts_dev) are not present elsewhere

edit:

the previous build dosent include the hardware omap3 :)

figured it out, included, fixed the build (git pushed) and the playground update file reuploaded (or at least upload now)
[Milestone XT720 Android Development] SickBeast:
From my experience with the other CyanogenMod 7 ROM, Android 2.3 does not run well on the XT720.

I'm going back to CyanogenMod 6.3, personally. It's much faster overall.

Cyanogen 7 seemed fast at first, but after a week of usage I'm not impressed with it at all. It takes way longer to even do basic things like make phone calls or pull up the keyboard.

Hopefully this new ROM is more optimized, but I'm going to wait it out for a bit and let you guys be the guinea pigs this time. :)
[Milestone XT720 Android Development] mchlbenner:
Well experience the 6.3 kernal leaks real bad cm7 is alot faster than 6.3.

This cm7 being built for are phone.

The notorious was not built for are phone.

Cm7 will be far superior to cm6.
[Milestone XT720 Android Development] J.Y.Daddy:
touchroi binary srouce

Hi, fjfalcon!

Here is the touchroi binary source.

Source is very simple. :p

But it has spent too much time trying to figure out. :D

main.c

#include <stdio.h>

int main()
{
FILE *fp=fopen("/dev/qts_dev","r");
fclose(fp);
return 0;
}

Cheers on your build work!! ;)

Good Luck!
[Milestone XT720 Android Development] Mioze7Ae:
Thanks!!!!
[Milestone XT720 Android Development] B_e_n:
The ext4 don t work for me

I don t read anything about it...

Thanks for the good work fjfalcon!
[Milestone XT720 Android Development] AA1973:
***

Edit: forget what I wrote-the answer is just underneath :)

***

Make a nandroid for sd-data, so you'll have an ext2 backup that you can restore.

I don't know if app2ext is already supported as I am just following this thread and haven't tested this build.

BTW big thanks to fjfalcon for your work!

CM7.1.0-11.10.12 (odexed) - Milestone XT720
[Milestone XT720 Android Development] fjfalcon:
I haven't enabled ext* modules at all...

Later..
[Milestone XT720 Android Development] peshovec:
compass

compas wrong north is fixed for me

https://github.com/peshovec/android...mmit/0ebadf55923164b3f0f432bbb37712c5f208fc73

now work well in maps, elixir 2, gps status toobox

the sensor.sholest.so library is attached (tar.bz2 -ed, but renamed due to upload restriction)
[Milestone XT720 Android Development] fwals:
usb ok

and ext ok

The usb on the system \ app to modify the permissions to restart

The ext.zip into openrecovery \ updata under

Do not know the gps does not help you there

By the way, how to cancel dalvik-cache to cache?
[Milestone XT720 Android Development] syrenz:
I downloaded the ROM in first post. Android Market force closes on me everytime, even after a reboot and a reinstallation of the whole ROM. Any fixes?
[Milestone XT720 Android Development] fjfalcon:
http://xt720.ru/Files/Mods/cm7/update-cm-7.1.0-MilestoneXT720-alpha-10162011-signed.zip

gps working, usb working, camera working, mediabutton opens gallery.

Added touchroi binary code to bootanimation.
[Milestone XT720 Android Development] Knoedelkopf:
no more camera freezes ?
[Milestone XT720 Android Development] fjfalcon:
Don't know, how to repeat them?
[Milestone XT720 Android Development] Mioze7Ae:
It might be better to keep it separate. One of the problems with having it inside bootanimation is that things that replace bootanimation (e.g. chainfire's live dmesg and live logcat) will break touch.

Actually, I wonder if we can just add something to sh_hijack.sh (maybe "cat", "dd" or "head"). I wonder if this works:

head -n 0 /dev/qts_dev
[Milestone XT720 Android Development] fjfalcon:
Thanks, will check head in next build
[Milestone XT720 Android Development] ashish7350:
Camera is working but not saving the pics..... any fix for this
[Milestone XT720 Android Development] tharan.a:
I know the Motoroi CM7 port has been giving people some trouble. But since this is being built from source, would that imply it would be near if not better than Mioze's CM6?
[Milestone XT720 Android Development] acrobat69:
Hmm..sounds like similar fun I get with 3G...I live in a weak signal type house and the phone really has to work hard to keep 3G alive. It loses signal all the time in fact.

So did you actually change anything in the Wind sbf? From what I recall S7ticky is a Torontonian + Wind customer as I am, so wouldn't it be highly likely that his nandroid is just identical to what shipped with my phone, which is also a Toronto Wind phone? I'm just not clear whether or not there's any difference...or..wait..is the issue that I've actually wiped out my stock baseband by applying a rom such as 6.3.6, and I now need to restore my original baseband, which is the same/very close to the one you posted? Sorry if I just missed an obvious piece of logic there, twas a verrry long night..
[Milestone XT720 Android Development] Mioze7Ae:
Yes. Exactly. The default baseband stuff in system.img in 6.3.6 and CM7 are either korean or UK/dexter--I can't remember which because we've jumped back and fourth a few times. Flashing a ROM replaces everything in system.img. I don't think there is a one-size-fits-all /system/etc/motorola baseband config.
[Milestone XT720 Android Development] acrobat69:
Ok..so I'm getting closer to understanding this.

Sounds like doing this would be a good idea. I do, however, have a nandroid taken from right after I got the phone, so it's completely stock. Could I merely restore the system.img in order to get my old baseband back, or I guess there's probably additional stuff in system.img that I don't want to restore, right? Applying your baseband update would hit just the baseband part, in other words, whereas a restore of my nandroid would be baseband++stuff I don't want..

Have I got that right?
[Milestone XT720 Android Development] Mioze7Ae:
Nandroid restore would replace the entire ROM the same way as a full ROM update does. The baseband updates aren't full ROMs, they are are just zip files that only change the baseband part (and the ril library because that was needed for some reason--see Dexter's porting thread). I'm pretty sure that the Wind baseband update is already identical to what's in your system.img nandroid, but you can send me your original Wind system.img if you want me to verify that.
[Milestone XT720 Android Development] acrobat69:
Sure, why not, it would be good to verify that and for future knowledge for other Canadian Wind customers, right? Grab it here: http://www.megaupload.com/?d=XFVSIYV8
[Milestone XT720 Android Development] Mioze7Ae:
I was wrong about how 2nd-init works. It *does* cause motorola's /init to be reloaded from the ramdisk so we can replace the ramdisk's /init with our own version before running 2nd-init to replace Motorola's. I read this a long time ago and didn't fully understand what's being said here: http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works

Now that I've read it again, it clears up some other things I've been puzzling over (i.e. what the other devices are up to with their hijacks inside device/motorola/common and why they don't have something like /system/etc/rootfs). The other devices seem to hijack logwrapper whereas we hijack sh. I need to do some testing to see which is executed first: logwrapper or sh. Dexter used to hijack mot_boot_mode and sh hijack is definitely earlier than mot_boot_mode on XT720, so the question is: is logwrapper even earlier than sh...
[Milestone XT720 Android Development] Mioze7Ae:
Ok this makes sense now. In CM7 (not sure whether this is a CM modification or if it's present in AOSP--it's not in the CM6 tree) the /init binary (source in system/core/init) is a multi-call executable that includes both init and ueventd: https://github.com/CyanogenMod/android_system_core/tree/gingerbread/init So, if we were to build our own ramdisk, I'm pretty sure it would contain the /sbin/ueventd -> /init symbolic link.

Back to nadlabak's patch: https://github.com/nadlabak/android...mmit/87ed6c90320a613b2fb225d3ad58c288ba9c3d59

First, nadlabak modified the squisher (a script that runs after the build process to do all sorts of surgery to the update.zip) to make a copy of the ramdisk's /init binary inside /system/etc/rootfs/init (the ramdisk copy is discarded otherwise since we can't change the ramdisk). Everything inside /system/etc/rootfs/ is already used to replace the ramdisk before 2nd-init, so the contents of the new init will automatically replace the existing /init. Next nadlabak changed the sh_hijack.sh to set correct permissions for /init after it's been replaced and also to create the missing symbolic link for /sbin/ueventd. All of this should work fine for XT720, assuming ueventd doesn't have some incompatibility with 2.6.29...

The UIDs stuff has to do with this https://github.com/CyanogenMod/android_system_core/commit/073b6b19da1e0c6ccf1b3261fca766f5516122ec which I think just defines name-to-uid mapping inside /init.
[Milestone XT720 Android Development] Mioze7Ae:
Yup, for all intents and purposes, it's identical to the one I had. The wind baseband update matches your nandroid.
[Milestone XT720 Android Development] peshovec:
new experimental build (at the usual place)

for bigger icons, replace both lcd_density 160 to 240

experimental + arm_ldrex_strex + armv7 strlen + ifneq external v8, synced 2012.01.04

synced today, has to have no issues with web based application (phone crash, or application force close), cherry picked optimized for armv7 strlen, cherry picked ldrex and strex arm cpu features

just started myself testing (booted fine:)
[Milestone XT720 Android Development] mchlbenner:
Trying this out.

One issue I had was no 3g connection but I flash over a different cm7 and then it work.
[Milestone XT720 Android Development] acrobat69:
Excellent, thanks for letting me know!! I'm going to try the baseband update, then. My 3G issues have been increasing slightly, so hopefully this will help.
[Milestone XT720 Android Development] acrobat69:
MZ, sorry if this is a dumb question, but should I have done any wipes after installing the baseband update?
[Milestone XT720 Android Development] Mioze7Ae:
Wipes shouldn't be necessary.