• 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]

buzzcon said:
When I first flashed to this ROM, I installed ADW Launcher Ex and it didn't play well with CM9. It did something to the touch screen and made it so I had to hit an icon 5-6 times to get it to work. Switched to Launcher Pro Plus and that seems to work just fine.

Keep in mind, this is not a complaint, I am just reporting my experiences in case it might help someone else. I am running SmartassV2 and the battery life has improved greatly.

Does ICS have different graphics drivers? It just seems to have better response with screen transitions and such.
Click to expand...
I don't really know about the graphics drivers, they seem faster but are still buggy. Keep in mind that this is still an alpha, though. Might want to ask g60 about that one. I don't know about the graphics drivers as I'm not doing the coding. ;) ADW Launcher (yes, even the EX version) hasn't been updated in ages. I'm wondering if it's abandonware, as CyanogenMod ditched bundling it after already using it for so long. I stopped using it myself. I recommend either 360 launcher or Holo Launcher (but since you're on ICS, the default launcher is way more modern and lean than Holo, since it is basically mostly the same as Holo, and ADW is just too old). I've noticed this lack of updates with Zeam and LauncherPro as well. But there are some cool ICS+ launchers like Nova and Apex. Might want to check those out. Also, I know you want to help, but please (not picking on you) but nobody report any issues yet as this is an alpha. I done the same thing, only to later read in red print and caps lock that issue reporting time is not now. Alpha means that the code is still rapidly changing, so an issue this week could be gone or made worse the next week. So as soon as you see the beta tag, feel free to report bugs. :D

rodgman15 said:
You think? Is it possible that maybe you could help contribute to something instead of having silly posts spamming up pages everywhere?
Click to expand...

Please, guys, don't add any stress. When there's a post that you think is spam, don't feed the fire. Best to ignore it. If it's a little mess up, don't report it. If it's a flame, report it. I don't want to see anyone get banned, but we have to help the admins in keeping this place clean. They can't watch us 24/7, as there are more complicated issues around here, and they already have enough flames to clean up already. We all get immature from time to time, though. Nobody's perfect.

rodgman15 said:
On another note, Chrome hasn't worked for me either, just switched back to Dolphin since that's what i'm used to. There have been a few other bugs, notifications, lock screen, small things that i'll wait to elaborate on, but G60Madman and the MTDEV team have hit back to back HR's with their CM7.2 and now this CM9!!! Keep up the great work gentlemen, I know a lot of people are truly enjoying the MT's now that you've been able to breathe new life into them. Can't wait to see continuing development!
Click to expand...

Guys, I'm pretty sure the MTDEV team knows that Chrome and Firefox are having issues due to the Adreno (or lack of Adreno) GPU drivers. They are doing their best and I am certain they will do all in their power and ability to fix this when they get around to it. I reported the same thing a while back, and when it hits beta, I will do what I can to look into it. (I can bug test, but not code). Perhaps I can upload a logcat of Chrome and Firefox when they crash once we get to beta. As a work around, use any browser that does not have hardware acceleration (such as stock, Dolphin, Maxthon, etc.) for the time being until this is fixed. But thank you for your praise.
 
g60madman said:
So to keep it simple it looks like we need to upgrade the kernel to get the camera to work. We may have another option but right now it looks we need a newer kernel.

Yes HDMI code is include in CM9. There was HDMI observer code included in CM7 but only works with specific HDMI devices. To get HDMI to work with CM9 its going to take editing some of the code to work specifically with our device.

To be clear I don't have all the answers as we are paving our own road. Basically because Motorola did not offer any files accept for the stock froyo kernel we are basically flying blind trying different things to make it work.

Right now each build takes roughly 35 minutes and if it doean't work we make tweaks to the code and try again. This is the work of all developers. I would love to tell you there is a big manual sitting on a shelf that has all the answers but that is not the case. Its simply trial and error, and sadly more error and fail than you know. If you have more questions please feel free to drop a line.
Click to expand...

Yeah I wish I knew more of what is going on! From a uneducated standpoint I honestly don't see why cm9 couldn't communicate to our camera through the 2.6.32 kernel given the right tweaks to the kernel code and stuff. There are other phones using outdated kernels running ics with the camera working so I don't see why we couldn't get it to work.

Unfodtunatley for us, the only part of Android released under the public friendly gnu gpl v2 is the kernel. Everything else is Apache which h doesn't require them to release changesade to it. They could have been nicer and gave us some of the camera lib c code and wifi driver code(they gave us the Bluetooth code) but they don't have too. And they released kernel code very fast actually which is surprising! The HTC Evolution V is still waiting on kernel code! So its not like Motorola is breaking laws but they just ain't helping as much as they should. But even with camera lib code that would have been for it to work on froyo so we would have still had to mess with it to work with ics granted it would be 100 times easier!!!
 
Idk about different graphics drivers, but Ice Cream sandwich does have hardware acceleration built into it by default (the GPU is used to help process tasks and free up the processor).
 
b_randon14 said:
Yeah I wish I knew more of what is going on! From a uneducated standpoint I honestly don't see why cm9 couldn't communicate to our camera through the 2.6.32 kernel given the right tweaks to the kernel code and stuff. There are other phones using outdated kernels running ics with the camera working so I don't see why we couldn't get it to work.

Unfodtunatley for us, the only part of Android released under the public friendly gnu gpl v2 is the kernel. Everything else is Apache which h doesn't require them to release changesade to it. They could have been nicer and gave us some of the camera lib c code and wifi driver code(they gave us the Bluetooth code) but they don't have too. And they released kernel code very fast actually which is surprising! The HTC Evolution V is still waiting on kernel code! So its not like Motorola is breaking laws but they just ain't helping as much as they should. But even with camera lib code that would have been for it to work on froyo so we would have still had to mess with it to work with ics granted it would be 100 times easier!!!
Click to expand...
The beta ICS for the Xperia Play uses the 2.6.32 kernel, I was trying to get it to build for our device, but had to get back to the kernel for the Sharp ROM, I plan on looking at it further to see what can be done. But that device has the same SOC as us. Just figured I 'd put this out there.
 
Another note, not sure if this is obvious, like, front camera related, but the light sensor for automatic screen brightness settings is off; sensor value is stuck at -1. It's ok, since we have "slide status bar for brightness" to handle that whenever we want, but I thought it should go on the list of things that don't work.

EDIT: FWIW, my wifi also does not autoconnect, tried on both n and g routers.

Also, I'm having a tough time getting ICS to auto-detect stuff from my SD card, basically remnants I've used for all of CM 4-7; stuff like Notifications/ringtones/alarms i moved from /media/(whatever) to /(whatever), but after detecting once they disappeared, and my gallery doesn't detect any pictures other than my google+ photo. Does anybody have an easy solution to this? Not a real issue, but sometimes it's hard for me to recognize my own phone if I don't hear megaman sfx for notifications
 
IkarugaDC said:
Another note, not sure if this is obvious, like, front camera related, but the light sensor for automatic screen brightness settings is off; sensor value is stuck at -1. It's ok, since we have "slide status bar for brightness" to handle that whenever we want, but I thought it should go on the list of things that don't work.

EDIT: FWIW, my wifi also does not autoconnect, tried on both n and g routers.

Also, I'm having a tough time getting ICS to auto-detect stuff from my SD card, basically remnants I've used for all of CM 4-7; stuff like Notifications/ringtones/alarms i moved from /media/(whatever) to /(whatever), but after detecting once they disappeared, and my gallery doesn't detect any pictures other than my google+ photo. Does anybody have an easy solution to this? Not a real issue, but sometimes it's hard for me to recognize my own phone if I don't hear megaman sfx for notifications
Click to expand...

Easy fix is to back up your SD, format and restore. Should work fine.
 
Urfreaky said:
Is it just me or does google now not work with voice? Sorry if this has been answered
Click to expand...

I think that the voice not working is a common issue with folks trying to get Google Now working on ICS, at least that's what I remember seeing when I first started seeing posts about it having been ported from JB.
 
Honestly I don't need Google now. I had a horrible experience with siri and I'd much rather have a working camera.

BTW I will be donating as soon as the camera's are working.
 
that the right hash number or md5sum or whatever it is called? I checked it and got .something totally different. I'm downloading again just in case
 
corance said:
that the right hash number or md5sum or whatever it is called? I checked it and got .something totally different. I'm downloading again just in case
Click to expand...

I believe I copied the right md5 was late when I posted it but I'm sure I did.
 
As it stands Google Now will install but the audio is messed up and doesn't work properly using the mic for input. In the logcat there has been some identified issues with audio. Though audio works properly there is still an issues going on with it. Since this ROM is not full cooked there is still lots of things to work out. Hopefully in future builds we will get closer with identifying and resolving this and other issues.
 
Ok do the one I downloaded earlier was 9.0 so that's why I thought the md5 was wrong so I downloaded 9.1 and they are the same...neither match the one listed.
 
g60madman said:
As it stands Google Now will install but the audio is messed up and doesn't work properly using the mic for input. In the logcat there has been some identified issues with audio. Though audio works properly there is still an issues going on with it. Since this ROM is not full cooked there is still lots of things to work out. Hopefully in future builds we will get closer with identifying and resolving this and other issues.
Click to expand...

Still pretty sweet to have at least some of the Google Now functionality in CM9!
 
Any one else having problems with "superuser" and es file explorer.
I try to enable "Root Explorer", It failed and told me the feature cannot run on my phone.
 
piper_ said:
Any one else having problems with "superuser" and es file explorer.
I try to enable "Root Explorer", It failed and told me the feature cannot run on my phone.
Click to expand...

Go into SuperUser, swipe over to the info tab, and tap where it says "tap to check for updates". Then click update. Fixed the root issue for me.

I found after flashing Google Now, apps weren't able to detect root, and that fixed it.
 
You must log in or register to reply here.
Back
Top Bottom