Android OS Forum banner
41 - 60 of 79 Posts

·
Average Android
Joined
·
89 Posts
You always want to wipe cache and dalvik when flashing a new build. All of the CM9 builds after 03/31 are based on ICS 4.0.4 for you should be fine with without wiping data. There is a newer gapps version (03/17) that can be downloaded here: http://goo.im/gapps
You actually only need to wipe cache partition. If you watch while you run your install, davlik cache gets wiped during install.

Also, once you wipe the cache partition, it also wipes davlik again, really if you just run that after the install, you're all good.
 

·
Registered
Joined
·
114 Posts
Any current builds having few issues with the data? My data has been awful lately, needing to wipe cache 2 times a day lately.
All the ICS builds still have data issues to my knowledge. Seems really hit and miss for people. I think it has a lot to do with how strong the signal is in your area, how much you travel, moving between towers, stuff like that. I'm actually running Eclipse now. Data has been rock solid for me on that for 5 days now. It's not ICS but it is really stable, debloated, a slick. I'm going to throw a post up about it here since no one else has.
 

·
Registered
Joined
·
114 Posts
So yesterday's build that showed up here:
http://rombot.droidh...s/maserati/cm9/
is larger than all the previous ones, any idea what has changed and what issues still remain or things have been fixed? This forum seems pretty dead, are there updates posted elsewhere I should be looking??
Can't tell you what's up with CM9 on the D4 as I have been running Eclipse for a while now. You are right about this place being dead though. Not sure why. This was the happening place for the D2! DroidForums and XDA-Developers seems to be where it's at for the D4. Both of those forums are pretty active.
 

·
Registered
Joined
·
88 Posts
Definitely dead on this thread. How about a little action?

So far, the build I compiled and flashed yesterday seems pretty solid. Haven't lost the data connection or had any issues except after boot. Seems to take excessively long to finally get the data up, but if that's all that's wrong I'm sure I can live with that for a while.

With the actual ICS leaks out, is there another GIT repo in progress that's using the new kernel/drivers for ICS?
 

·
Registered
Joined
·
10 Posts

·
Registered
Joined
·
88 Posts
I will be posting some new information on ICS leak based builds shortly.

But the local_manifest.xml that you're looking for is here:
https://github.com/STS-Dev-Team/android_local_STS/tree/ics-leak
Thanks hash, but I already ended up finding it, syncing repo, updating to 211, compiling a tweaked rom and flashing. The only real problems I have are the inability to switch the sdcards (vold.fstab switch-a-roo results in neither mounting) around (and the arrow keys not rotating when the qwerty is out.

Thanks for the hard work, looking good.
 

·
Registered
Joined
·
88 Posts
Hey Hashcode, what's different with the new ICS-LEAK roms that's not allowing me to switch the SDcards around in vold.fstab? Worked fine on ICS-GB but not now. Even if I just rem one out (either one) the device goes into a boot loop on the boot ani. I spent a few hours yesterday trying all kinds of different configurations, but the only one that works is stock. Thanks in advance and for the work done thus far.
 

·
Registered
Joined
·
88 Posts
If you figure it out, please do, but I have a feeling it's more deeply embedded in the D4 than in the D2.
I actually did. Grab the init.mapphone_cdma.rc from /system/etc/rootfs and change the following section:

Code:
<br />
# USB Mass Storage configuration<br />
on [URL=property:sys.usb]property:sys.usb[/URL].config=mass_storage<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4365<br />
	write /sys/module/g_android/parameters/cdrom 1<br />
	write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	setprop sys.usb.state $sys.usb.config<br />
# USB Mass Storage configuration, with adb<br />
on [URL=property:sys.usb.config=mass_storage]property:sys.usb.config=mass_storage[/URL],adb<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4366<br />
	write /sys/module/g_android/parameters/cdrom 1<br />
	write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage,adb"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	start adbd<br />
	setprop sys.usb.state $sys.usb.config<br />
to:

Code:
<br />
# USB Mass Storage configuration<br />
on [URL=property:sys.usb]property:sys.usb[/URL].config=mass_storage<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4365<br />
	#write /sys/module/g_android/parameters/cdrom 1<br />
	#write /sys/module/g_android/parameters/cdrom_switch<br />
	write /sys/class/android_usb/android0/functions "mass_storage"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	setprop sys.usb.state $sys.usb.config<br />
# USB Mass Storage configuration, with adb<br />
on [URL=property:sys.usb.config=mass_storage]property:sys.usb.config=mass_storage[/URL],adb<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4366<br />
	#write /sys/module/g_android/parameters/cdrom 1<br />
	#write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage,adb"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	start adbd<br />
	setprop sys.usb.state $sys.usb.config<br />
It's almost all the way to the bottom.

There's also some other interesting stuff regarding mount points in this file. Maybe we could figure out a way to switch around the sdcard's as well, but this is a good start. :D

I'm pretty sure this is a fairly safe edit to make since recovery comes up before that file is run so you should always be able to fix it.

From the build side of things, this file can be located at /device/motorola/maserati/root and edited before compiling (tested and confirmed).

Update: After making this change, I went for the vold.fstab edits again. This time they worked! I have no more fucking Moto cdrom drive and the first drive that mounts is the external since it is mounted to mnt/sdcard. Gonna try and throw these in my build files and see how that goes.
 

·
Mindless Build Bot
Joined
·
438 Posts
I actually did. Grab the init.mapphone_cdma.rc from /system/etc/rootfs and change the following section:

Code:
<br />
# USB Mass Storage configuration<br />
on [URL=property:sys.usb]property:sys.usb[/URL].config=mass_storage<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4365<br />
	write /sys/module/g_android/parameters/cdrom 1<br />
	write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	setprop sys.usb.state $sys.usb.config<br />
# USB Mass Storage configuration, with adb<br />
on [URL=property:sys.usb.config=mass_storage]property:sys.usb.config=mass_storage[/URL],adb<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4366<br />
	write /sys/module/g_android/parameters/cdrom 1<br />
	write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage,adb"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	start adbd<br />
	setprop sys.usb.state $sys.usb.config<br />
to:

Code:
<br />
# USB Mass Storage configuration<br />
on [URL=property:sys.usb]property:sys.usb[/URL].config=mass_storage<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4365<br />
	#write /sys/module/g_android/parameters/cdrom 1<br />
	#write /sys/module/g_android/parameters/cdrom_switch<br />
	write /sys/class/android_usb/android0/functions "mass_storage"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	setprop sys.usb.state $sys.usb.config<br />
# USB Mass Storage configuration, with adb<br />
on [URL=property:sys.usb.config=mass_storage]property:sys.usb.config=mass_storage[/URL],adb<br />
	write /sys/class/android_usb/android0/enable 0<br />
	write /sys/class/android_usb/android0/idVendor 22b8<br />
	write /sys/class/android_usb/android0/idProduct 4366<br />
	#write /sys/module/g_android/parameters/cdrom 1<br />
	#write /sys/module/g_android/parameters/cdrom_switch 0<br />
	write /sys/class/android_usb/android0/functions "mass_storage,adb"<br />
	write /sys/class/android_usb/android0/enable 1<br />
	start adbd<br />
	setprop sys.usb.state $sys.usb.config<br />
It's almost all the way to the bottom.

There's also some other interesting stuff regarding mount points in this file. Maybe we could figure out a way to switch around the sdcard's as well, but this is a good start. :D

I'm pretty sure this is a fairly safe edit to make since recovery comes up before that file is run so you should always be able to fix it.

From the build side of things, this file can be located at /device/motorola/maserati/root and edited before compiling (tested and confirmed).

Update: After making this change, I went for the vold.fstab edits again. This time they worked! I have no more fucking Moto cdrom drive and the first drive that mounts is the external since it is mounted to mnt/sdcard. Gonna try and throw these in my build files and see how that goes.
Awesome, I finally managed to get a build to compile last night, so I'll see about integrating those changes sometime.
 
41 - 60 of 79 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top