• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM] MTDEV-CM9 build 20130120 [BETA]

Did you install the Offline version or the Online version of GoogleNow? The version I included in the ROM originally was Offline and should leave you with about 20MB and or so.

Repartitiong would be nice, but I would imagine to be very dangerous, then we would have to repartition back when installing the stock rom. Ill look into seeing how ro repartition a emmc device like ours but I can't promise anything! I wish you could combine three partitions together as one!
 
Repartitiong would be nice, but I would imagine to be very dangerous, then we would have to repartition back when installing the stock rom. Ill look into seeing how ro repartition a emmc device like ours but I can't promise anything! I wish you could combine three partitions together as one!

Yeah I edit the updater-script to add the GoogleNow into the hidden partition and link back to the system but could not get it to work. Good luck man! It would be sweet if you could figure it out but I agree it's dangerous.
 
Yeah I edit the updater-script to add the GoogleNow into the hidden partition and link back to the system but could not get it to work. Good luck man! It would be sweet if you could figure it out but I agree it's dangerous.

Yeah I just mounted both spare partitions one as /hidden (/dev/block/mmcblk0p9) which has about 25mb free formatted as ext3 and the iteration as /hdata (/dev/block/mmcblk0p10) which has like 67mb free.

So maybe if we have the script format those as ext4, then have our init mount it as /hidden and /hdata at boot. Then in our update script have some of the less complicated but still large apps from the system copied to one of those partitions and symlink to /system/app. Kinda like Motorola and vm did with their apps on the stock rom. Or move ringtones over to their as well!.

We just need to make the update script fool proof no matter what recovery you are using. Because my new cwm recovery makes /hidden and /hiddendata at boot but does not mount the partitions automatically. And on my twrp2.3 it makes directories /hidden and /hdata at boot.

But you could just have the script run umount on all those directories, then have it handle the making mountpoints and mounting itself.
And if your using my cwm or twrp then those will get backed up.as ext3 on stock and ext4 using cm9 making it easy to switch back and fourth.
 
Yeah I just mounted both spare partitions one as /hidden (/dev/block/mmcblk0p9) which has about 25mb free formatted as ext3 and the iteration as /hdata (/dev/block/mmcblk0p10) which has like 67mb free.

So maybe if we have the script format those as ext4, then have our init mount it as /hidden and /hdata at boot. Then in our update script have some of the less complicated but still large apps from the system copied to one of those partitions and symlink to /system/app. Kinda like Motorola and vm did with their apps on the stock rom. Or move ringtones over to their as well!.

We just need to make the update script fool proof no matter what recovery you are using. Because my new cwm recovery makes /hidden and /hiddendata at boot but does not mount the partitions automatically. And on my twrp2.3 it makes directories /hidden and /hdata at boot.

But you could just have the script run umount on all those directories, then have it handle the making mountpoints and mounting itself.
And if your using my cwm or twrp then those will get backed up.as ext3 on stock and ext4 using cm9 making it easy to switch back and fourth.

Yeah I am not sure how much time we want to spend on this as I am trying to keep the ROM's as small as possible. I maybe able to free up some more space but not sure what else I can cut off. Plus CM10 will be around the corner soon. If we can solve the camera there is really nothing stopping us from using source code from AOSP either. Be nice to run straight Jelly Bean from Google. If the petition goes anywhere we can build what ever version of Android we want for the phone as we could manipulate the code for anything.
 
I usually overclock to 1209 figuring a little won't hurt. Not so on the 1113 version. App lockups, freezing and battery pulls, lol
 
You want to use the offline version, that link will offer a link to GoogleNow commands also. I would recommend installing the ROM, GoogleNow, and then GoogleApps

Has anybody been able to get GoogleNow working with the 11/13 ROM?

When I flash the 11/13 ROM, GoogleNow, then GoogleApps my home and search buttons don't work. They still vibrate when they are pressed, but single presses and long presses don't do anything. I rewiped and got the same result a second time. GoogleNow does work though.

When I rewiped and tried to flash GoogleApps first, and then GoogleNow the buttons work, but GoogleNow just closes whenever I try to start it (including voice search and regular search). Also, the ususal welcome setup doesn't come up after initial boot, but I was able to log in to sync my Google account by opening contacts. I also rewiped and ran through these steps again and got the same results.

When I wipe and install just the ROM and GoogleApps I notice that I only have 7 MB free on my System partition, but I noticed that the GoogleNow install instructions say that it needs 60 MB free? Could that have something to do with what is causing these problems?
 
Folks,
Thanks for all the effort in creating this. I installed this on my MT phone but I keep getting 3G/Wireless signal issues/lack of connection. The only way to get a connection is by rebooting. I read through this thread and my understanding is that this issue is resolved.
Do you have any thoughts on what else to try to fix this?
Thanks,
Deepak

I have the same problem. I asked before but didn't get an answer for it either...
 
As far as a data loss that's resolved by a reboot, would toggling the data widget or cycling through airplane mode work?

Toggling through widget doesn't do anything, I haven't tried airplane mode. Still it's annoying to be having to reboot to fix data (that also includes calls, SMS/MMS - reboot for them to go in, pending to go out). What could be causing it?
 
Toggling through widget doesn't do anything, I haven't tried airplane mode. Still it's annoying to be having to reboot to fix data (that also includes calls, SMS/MMS - reboot for them to go in, pending to go out). What could be causing it?

I'll look into this ands see if I may have missed any fixes from Mantera.
 
Toggling through widget doesn't do anything, I haven't tried airplane mode. Still it's annoying to be having to reboot to fix data (that also includes calls, SMS/MMS - reboot for them to go in, pending to go out). What could be causing it?

Did you restore backups of any system or google apps after flashing the rom? I had some weird problems when i restored data for some of the google apps using titanium backup.

If you reflash the rom again, check whether you have the same issues right after you flash and before restoring anything else - or whether they only start after you start restoring your backups.
 
Anyone have an idea why Google play music stops working as soon as I open it

It may be a bad download. I had some issues a while back with Google Play Music (on Gingerbread at any rate), where it would take forever to open, then freeze and force close.

I wound up uninstalling it, rebooting the phone, then reinstalling it, which seemed to remedy the problem. I don't know if rebooting is absolutely necessary, but I do it for good measure when I encounter issues.
 
Did you restore backups of any system or google apps after flashing the rom? I had some weird problems when i restored data for some of the google apps using titanium backup.

If you reflash the rom again, check whether you have the same issues right after you flash and before restoring anything else - or whether they only start after you start restoring your backups.

I never restore anything, start fresh again.
 
Back
Top Bottom