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

Root [ROM] MTDEV-CM7 build 2013-03-03

BSydz said:
It is Mi410_v3.18D_kernel_source_2.6.32.9, it is the only stock kernel source I could find, of any of the other phones. All the GSM variants use the same kernel(zImage), but bluetooth and the base band would not work. I have been running the kernel in the Sharp ROM on my dev phone since yesterday and all day today on my good phone and everything seems to be working just fine, just a few bugs like auto focus on the camera, but I didn't change any libs just the zImage. I figure that if CM7 is using the Cherry camera libs, that it may fix some of the quirks with the camera. And also may give us a higher platform to start with trying to work out CM9 and CM10, since we readily have all the files from most of the variant phones. And I'm sure that Chairshot has quite a bit of time spent with most of them. I have compared the MTDEV CM7 kernel with this kernel and a bunch of stuff is different. Since there were fewer differences between this and stock, I figured I would go that route and pin point some things, like why all the other variant ROMs with stock kernels would boot and work just fine but BT and the baseband would not show up. And of course the data wouldn't work but that is a ramdisk and system problem not the kernel, as I have found. Anyway...

This is only for those, that know what they are doing, it is not a flashable kernel, it is a zImage do not try to flash this. This boots and works just fine, the ramdisk is what is going to be important for it to work with what ever system correctly. This is still being worked on but might be useful for testing purposes.
Triumph_Mi410_v3.18D_kernel_2.6.32.9_zImage1.zip
Click to expand...


This is actually pretty awesome. I have spent countless hours with the Sharp 2.3.5 Kernel and still stuck with half functioning ADB. Have always believed that if I could get full ADB I could make it work. Anyhow I started again looking at some of the other Kernels from your variants as I believe moving to a more Stock Kernel would help with many bugs and issues. I think Whyzor & others have done some nice work but with the additional knowledge gained over time partly thanks to you and your ports believe many of the changes or workaround attempts are actually hurting us in some situations from finding actual fixes. One example is I have a Rom using TG's beta 3 Kernel that can deep sleep with wifi turned on. I have made numerous attempts at reverting the eventually added wakelock but it will not work with the current Kernel and so many other changes have been made it makes my head spin trying to figure out what's what. My limited experience working on the Kernel doesn't help much either. Think I just over the weekend had a conversation with dsmryder about restarting the Kernel again over from scratch.Also think I now at least have a good understanding of what's what on the Rom side of things so think it would also be a good start in overall learning progression.
 
Chairshot215 said:
This is actually pretty awesome. I have spent countless hours with the Sharp 2.3.5 Kernel and still stuck with half functioning ADB. Have always believed that if I could get full ADB I could make it work. Anyhow I started again looking at some of the other Kernels from your variants as I believe moving to a more Stock Kernel would help with many bugs and issues. I think Whyzor & others have done some nice work but with the additional knowledge gained over time partly thanks to you and your ports believe many of the changes or workaround attempts are actually hurting us in some situations from finding actual fixes. One example is I have a Rom using TG's beta 3 Kernel that can deep sleep with wifi turned on. I have made numerous attempts at reverting the eventually added wakelock but it will not work with the current Kernel and so many other changes have been made it makes my head spin trying to figure out what's what.
Click to expand...
Thanks. I am just now figuring out that our zImage can basically work across the board with all the systems, but the ramdisk is where the system integration happens. It is so hard to step in to the game after all of the changes that have been made by so many people. It is damn near impossible to track down all the changes. It is a great base of reference and I thank all that were involved, but it took me hours to figure out what yumbrad did to get the data to work, to see if I could apply it to CM10.

Ok, so I narrowed it down and figured I would just post the links to the source and the fix. I'll setup my github with the Sharp setup with everything added in the next few days. The zImage I posted earlier has all the OC and other goodies all built in.


I have narrowed the fixes down to these files:
arch/arm/mach-msm/fxx_info.c
arch/arm/mach-msm/smd.c
arch/arm/mach-msm/smd_private.h
drivers/usb/gadget/msm72k_udc.c
include/linux/fih_hw_info.h

Stock Kernel Source:
Mi410_v3.18D_kernel_source_2.6.32.9.7z

Fix for baseband and bluetooth for the Triumph:
Triumph-Mi410_v3.18D_kernel_source_2.6.32.9-fix.zip
 
chilz said:
does the hdmi work on this kernal if so ill flash right now to cm7 with it
Click to expand...

The HDMI needs kernel and ROM support. We package both together, but they could be seperate. Anyway, no HDMI wouldn't work, even if the kernel side did. I know it was one of the things that g60 wanted to get working.
 
I have added in the boot sound finally. I know I tried to get it to build before, but I got it now.

Next on my list is the data control settings I have been studying for. Wish me luck on that one.

P.S. The ROM is to be considered a tester! I have loaded it up on the DEV phone, but the first randition locked it up. This is another one that has the same code and shouldn't be any different. The lock up may be caused by what ever has been causing the lockups before. That and I don't know what experemental stuff chairshot has tossed into the repository. I'll let him post up an official build.
 
Izzard said:
So, this kernel is cooked and better for CM7 ?
Click to expand...
chilz said:
does the hdmi work on this kernal if so ill flash right now to cm7 with it
Click to expand...
That is a link to my github with the kernel source code. I have not built a full boot.img for anything other than the Sharp ROM. Our phones boot.img is actually 2 parts the zImage, which is actually the kernel, and the ramdisk, which is what is used as an initiator and translator between the operating system and the kernel. A zImage can be used with any OS for the most part, but the ramdisk is system specific.
dsmryder said:
The HDMI needs kernel and ROM support. We package both together, but they could be seperate. Anyway, no HDMI wouldn't work, even if the kernel side did. I know it was one of the things that g60 wanted to get working.
Click to expand...
Yes, you are correct. I started working with this kernel to see what it could do for CM7 and built a few tests before I started actually working on the kernel. I had some display issues, so I switched paths to work on just the kernel. I figure that chairshot has a pretty good grasp on what libs do what and some ideas beyond what I tried in the couple hours I spent messing around. It did have an error about hdmi in the logcat, but can't remember now. So it was trying to connect to the hdmi, but I didn't plug it in or anything. Any way gotta go to work...
 
A few things.
1. This is the best CM7 (20121015 build) I've ever run on my Triumph. When Running TG-Reloaded my phone would freeze on almost every app run, many apps would show up improperly, etc. This almost never slows down and has yet to disappoint, great work!
2. I've noticed that the above mentioned switching to FFC FC bug also screws with my Notification Power Widget.. e.g. when turning wifi off, it turns back on, changing brightness will go back to what it was at previously after shutting off/on the screen, and the auto-rotation plain won't do anything (the icon doesn't change at all). All it takes is an app cache wipe/reboot to fix, but I have to do that maybe once a day as this problem occurs quite often. I've tested and seen that this usually happens when I use an app such as snapchat before the camera itself and switching to the FFC. Don't know if any of this info helps, but I'm so grateful for this ROM that I want to give a bit of feedback to help improve it more!
3. I'm a new user, so I can't post a screenshot/image of this problem, but when I use search functions on apps (such as typing in the address bar on the stock browser, or typing in spotify) the app will "disappear", leaving a view of my keyboard, and my wallpaper. If I press anything on the keyboard the app will reappear. A small thing that bothers me, just seeing if this, too, is common or if known fix to this.
4. Is MMS sending a known issue? I'm using GoSMS Pro which runs just fine in most instances, but when sending pictures to certain people (typically iPhone users) the MMS won't go through until I send another MMS. Not sure if it's just a problem with the service in my area or something else. Actually, I just tried this and the MMS wouldn't go through for 15 minutes, even with 3 bars of service, and then sending another MMS made them both go through almost instantly.

I think that's all I've got..
Any and all help/answers are appreciated!
Keep up the good work :)
 
Snaxtax said:
A few things.
1. This is the best CM7 (20121015 build) I've ever run on my Triumph. When Running TG-Reloaded my phone would freeze on almost every app run, many apps would show up improperly, etc. This almost never slows down and has yet to disappoint, great work!
2. I've noticed that the above mentioned switching to FFC FC bug also screws with my Notification Power Widget.. e.g. when turning wifi off, it turns back on, changing brightness will go back to what it was at previously after shutting off/on the screen, and the auto-rotation plain won't do anything (the icon doesn't change at all). All it takes is an app cache wipe/reboot to fix, but I have to do that maybe once a day as this problem occurs quite often. I've tested and seen that this usually happens when I use an app such as snapchat before the camera itself and switching to the FFC. Don't know if any of this info helps, but I'm so grateful for this ROM that I want to give a bit of feedback to help improve it more!
3. I'm a new user, so I can't post a screenshot/image of this problem, but when I use search functions on apps (such as typing in the address bar on the stock browser, or typing in spotify) the app will "disappear", leaving a view of my keyboard, and my wallpaper. If I press anything on the keyboard the app will reappear. A small thing that bothers me, just seeing if this, too, is common or if known fix to this.
4. Is MMS sending a known issue? I'm using GoSMS Pro which runs just fine in most instances, but when sending pictures to certain people (typically iPhone users) the MMS won't go through until I send another MMS. Not sure if it's just a problem with the service in my area or something else. Actually, I just tried this and the MMS wouldn't go through for 15 minutes, even with 3 bars of service, and then sending another MMS made them both go through almost instantly.

I think that's all I've got..
Any and all help/answers are appreciated!
Keep up the good work :)
Click to expand...

Well, thanx for the feedback. I don't know what to say about the camera issues or the bug where settings won't stick. The only thing I can say is I know on my own personal phone I haven't had that yet. I also know that chairshot has had some issues simular to that. I might add to this later, gotta go.
 
Snaxtax said:
I use search functions on apps (such as
typing in the address bar on the stock
browser, or typing in spotify) the app will
"disappear", leaving a view of my keyboard,
and my wallpaper. If I press anything on
the keyboard the app will reappear.
Click to expand...

This sounds like an issue with your theme.
If you are using one, try changing it to a stock one and see if that fixes it.

Just a shot in the dark... If you're not using a custom theme... Never mind. :D
 
thangfish said:
This sounds like an issue with your theme.
If you are using one, try changing it to a stock one and see if that fixes it.

Just a shot in the dark... If you're not using a custom theme... Never mind. :D
Click to expand...

I knew I forgot to mention something haha
I'm using the Ultimate ICS from MTDEV currently

Trying out a different theme to see right now..
Same problem with all other themes (Cyanbread, Androidian, System)
 
Snaxtax said:
I knew I forgot to mention something haha
I'm using the Ultimate ICS from MTDEV currently

Trying out a different theme to see right now..
Same problem with all other themes (Cyanbread, Androidian, System)
Click to expand...

That is a documented bug in the Ultimate Ics theme, that was held over from the theme G60 made it from... (forgot the name). Not a ROM issue.

Maybe a reboot will clear or up for you.
 
Camera fv 5 lite does not capture pics but acts like it does, regular camera works fine. Not sure if anyone's mentioned this or not. Love this rom on everything else I use though. Haven't tried a or b yet. Thanks for all you developers do to make my phone run better... MUCH better than it ever was out of the box.
 
Works fine here.
Photos are saved in DCIM/100_CFV5/ by default.
You can change it in the settings. Maybe you have disallowed that folder in your gallery, or whatever you use to view with?
 
since installing test a version, i decided to mess around with themes a little. any theme i install when i go to apply i get --- sorry this theme is missing assets for your devices screen size...apply anyway or bummer ...any ideas...also when i uninstall an non working theme it force closes app (the application themes provider (process com.tmobile.thememanager) has stopped unexpectedly. please try again) but it uninstalls them.
 
thangfish said:
Works fine here.
Photos are saved in DCIM/100_CFV5/ by default.
You can change it in the settings. Maybe you have disallowed that folder in your gallery, or whatever you use to view with?
Click to expand...


Can't see the folder for some reason.. the camera 'cross hairs' go orange after taking a shot and stay orange afterwards. I hear a click when pics are taken too. I had this app with another rom so I have an existing folder just no new pics. Tried reinstall, reboot, renamed that folder, nothing seems to work. hm.
 
arcticfix said:
since installing test a version, i decided to mess around with themes a little. any theme i install when i go to apply i get --- sorry this theme is missing assets for your devices screen size...apply anyway or bummer ...any ideas...also when i uninstall an non working theme it force closes app (the application themes provider (process com.tmobile.thememanager) has stopped unexpectedly. please try again) but it uninstalls them.
Click to expand...

Make sure the themes you apply are for hdpi devices, but almost all (if not every single one) of the themes I have installed give the"missing assets" error and it should be safe to ignore and install anyway.
 
Just a general fyi to anyone...

Sometimes strange errors can be addressed by fixing permissions, either in CWM, or some other app that has that function.

Worth a try, anyway.
 
thangfish said:
Make sure the themes you apply are for hdpi devices, but almost all (if not every single one) of the themes I have installed give the"missing assets" error and it should be safe to ignore and install anyway.
Click to expand...


Yeah I pretty much do the same thing and they usually work. Like thangfish said it generally means the theme uses mdpi and not hdpi images. Just a note but mdpi images are used more in devices with low resolution.
 
What's up everybody?

I've been working on kernels lately and found some differences that may be able to help. I took MTDEV-KERNEL-CM7-master, and added a few things.
1. Added camera functions: need to see if this fixes the issues with FFC, both switching to, and autofocus click.
2. Updated the touch screen drivers: updated drivers this should also fix the lines in the screen on wake up that some phones experience.
3. Added filesystem support. (details in the config diff below)
4. Enabled a bunch of debugging, so hopefully we can get some more info to see what is happening in the kernel. I think I missed some debug flags this time around but all in due time.

This is a test and should be treated as such, I will continue work as things progress and we get some feedback.

This is a flashable zip, just boot to recovery and flash as normal.
BSydz-MTDEV-CM7-Kernel-Camera-Touch-test-1

NOTES:

I used my Sharp custom kernel defconfig and added any missing settings from the supplied config.
Differences in the defconfig:
[HIGH]
CONFIG_FIH_BUILDTYPE_DEBUG=y
CONFIG_FIH_TOUCHSCREEN_BU21018MWV=y
CONFIG_FIH_TOUCHSCREEN_INNOLUX=y
CONFIG_FIH_SUSPEND_RESUME_LOG=y
CONFIG_FIH_PANIC2MODEM=y
CONFIG_FIH_PANIC_LOG=y
CONFIG_FIH_POWER_LOG=y
CONFIG_FIH_FLOG=y
CONFIG_FIH_LAST_ALOG=y
CONFIG_FIH_MLOG=y
CONFIG_FIH_REMOVE_SERIAL_DYNAMICALLY=y
CONFIG_MSM_RPC_SDIO_DEBUG=y
CONFIG_MSM_SMD_DEBUG=y
CONFIG_MSM_SDIO_CTL_DEBUG=y
CONFIG_MSM_CPU_FREQ_MIN=122880
CONFIG_ARM_THUMBEE=y
CONFIG_SWP_EMULATE=y
CONFIG_FPE_FASTFPE=y
CONFIG_NET_SCH_SFB=y
CONFIG_DM_DEBUG=y
CONFIG_DEBUG_GPIO=y
# CONFIG_USB_GADGET_DEBUG is not set
CONFIG_RTC_DEBUG=y
CONFIG_REISERFS_FS=y
CONFIG_REISERFS_CHECK=y
CONFIG_REISERFS_PROC_INFO=y
CONFIG_REISERFS_FS_XATTR=y
CONFIG_REISERFS_FS_POSIX_ACL=y
CONFIG_REISERFS_FS_SECURITY=y
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y
CONFIG_UDF_NLS=y
CONFIG_NTFS_FS=y
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
CONFIG_QNX4FS_FS=y
CONFIG_CIFS=y
CONFIG_CIFS_STATS=y
CONFIG_CIFS_STATS2=y
CONFIG_CIFS_XATTR=y
CONFIG_CIFS_POSIX=y
CONFIG_CIFS_DEBUG2=y
CONFIG_CIFS_EXPERIMENTAL=y
CONFIG_NLS_UTF8=y
CONFIG_DEBUG_KERNEL=y
CONFIG_TIMER_STATS=y
CONFIG_DEBUG_BUGVERBOSE=y
CONFIG_DEBUG_INFO=y
CONFIG_DYNAMIC_DEBUG=y
# CONFIG_KGDB is not set
CONFIG_DEBUG_ERRORS=y
# CONFIG_DEBUG_STACK_USAGE is not set
[/HIGH]
 
running super smooth on 1015 build and switching between cameras are super smooth good job bsyds im loving it do u plan on porting the mi410 rom if all works out
 
thangfish said:
Just a general fyi to anyone...

Sometimes strange errors can be addressed by fixing permissions, either in CWM, or some other app that has that function.

Worth a try, anyway.
Click to expand...

I also find this to be true but recommend an app like Rom Manager, Yeah I said it. Only because they are updated depending on what recovery is used. At least this is what I have read in a few different places.
 
You must log in or register to reply here.
Back
Top Bottom