• 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

On another note, after updating my ROM I decided not to load my backup just to keep things as clean as possible. I went from having 82 apps listed in the Play Store to 48 now. I know lots of problems with "Android" are really app-caused... and any OS runs better when kept trim, IMO. Soraso753 posted a list of issues above. So far, after 1-2 days of using 11.13 I've only experienced the reboot issue during games a couple of times (playing "250+ Solitaire Collection"). At least the phone is rebooted & ready for use in less than 1 minute from rebooting.

I don't have a lot of Android experience yet... is it normal for the OS to misbehave more when memory is low and lots of apps are installed? Is my estimation of "less apps = better running phone" about right?
 
AnakiMana said:
On another note, after updating my ROM I decided not to load my backup just to keep things as clean as possible. I went from having 82 apps listed in the Play Store to 48 now. I know lots of problems with "Android" are really app-caused... and any OS runs better when kept trim, IMO. Soraso753 posted a list of issues above. So far, after 1-2 days of using 11.13 I've only experienced the reboot issue during games a couple of times (playing "250+ Solitaire Collection"). At least the phone is rebooted & ready for use in less than 1 minute from rebooting.

I don't have a lot of Android experience yet... is it normal for the OS to misbehave more when memory is low and lots of apps are installed? Is my estimation of "less apps = better running phone" about right?
Click to expand...

Yes just like a computer if your running multiple of thing without enough ram to handle it your computer will start to get slow and crash. same goes with a phone if u don't have enough ram ur phone will get slow.the fewest amount of apps running in the background means more ram ur phone has to spare.
 
marcusi23 said:
Yes just like a computer if your running multiple of thing without enough ram to handle it your computer will start to get slow and crash. same goes with a phone if u don't have enough ram ur phone will get slow.the fewest amount of apps running in the background means more ram ur phone has to spare.
Click to expand...

It's been my experiace that it has less to do with the number of app vs. the likely hood that the app you have installed is holding something up. I have had some apps that just don't close out properly, check a server too often, or won't release the rotation lock (very anoying). Then there are some that will just crash out the phone. There are stratagies that should keep your phone with enough memory like hitting the back button to close an app. That will trigger a full close (onStop() ). That's one of the things that some apps don't do properly.

Anyway, I feel a ramble coming on, so I'll leave it at that.
 
tonestertm said:
Sorry, did you mean holding/long-pressing the Back button?
Click to expand...

No, I just meant a normal press. That's why I put the "call" in there. The way Google (as I understand it) intended the apps to work is when you press the back button the app should close in most cases. The problem is a lot of developers intercept the back button and make it do something else, like go to the apps home screen. That's fine, but a subsuquent press should close the app and move on from there. On some apps they don't allow the app to stop. They reopen or leave some services going that don't need to run.

I'm still just getting started myself, so I can't speak from tons of experiance. Although that much I have touched uppon.
 
Quick question - what's the difference between the two beta builds? Is one starshipifyed and the other based off MTDEV CM7? If so, which is which?
 
MikeRL said:
Quick question - what's the difference between the two beta builds? Is one starshipifyed and the other based off MTDEV CM7? If so, which is which?
Click to expand...

He had it posted back a page or two. I think the main difference is the choice of device files he used. I know he's trying to find the right combonation of files.
 
I like test build A better. With test build B, the camera refuses to connect. I will post more info if I can find any issues with test build A. Chairshot, what particularly do you want compared between the two ROMs? I also need to update that FAQ. Someone was helping me with it, but then they dropped off the face of the Earth. I hope they come back... Also, at least on test build A Portable Wifi hotspot will not work. Hope this helps.
 
The biggest differences between Test_A and B besides what had been posted previously are,


In test_B I ported the system apps for GPS found in Stock & all of Bsydz Varient Ports. I also added the files needed for these apk's to actually work. Mainly "qualcomm.location.vzw_library", permissions in "etc", "loc_api_app" binary and Sharp 2.3.5 "libloc" libraries tested in the previous few test builds. Took the APK's and "qualcomm.location.vzw_library" from Andro-id 3.3 based on the odex thing. Otherwise if you just placed the apk's in system/app without these additions they will not install or show in the application settings or any other app like system tuner. Once I got the apps to install I started seeing things in the logcat like permissions for accessing agps through these apps along with calls for Extra downloads in places that before installing the apps would instead list Extra download disabled or Extra download failed. Also in System Tuner when viewing these apps can see they not only have permission for Extra & agps but are actually using them. Finding System Tuner to be probably the most useful app for developing ever. Even has a setting when viewing each installed app that when selected will give you a filtered logcat only showing lines that pertain to that particular app. Anyhow with all this said in the short amount of time I had tested I hadn't notice much of an increase in performance other then a slight increase in overall accuracy. I generally test using "GPS Test" free from the Market. I first start the app and then turn on GPS via the statousbar and will then start counting until GPS Test gets a fix and accuracy reading drops below the 150 Mark apps like Maps look for before starting up Navigation. Im sure every individual counts at a different rate but in doing a comparison between two Roms it probably doesn't matter. Also seems the first fix after flashing is a bit longer then any time after so after the first fix I turn of GPS & Mobile data then reboot the phone before doing any testing. I do this in case there could be some bit of information stored somewhere from the first fix after flashing that could could make the next test faster then when used in a normal everyday situation. I turn off Mobile data to insure even the mobile location is lost. Unchecking the box for use mobile data in the location & security settings would probably be just the same. Assuming any of it is actually nessisary.


The other difference is that after looking over a few dozen different BoardConfig files I made an adjustment in our file. So for example if Im looking over device files from developers on Github and notice their BoardConfig is practically 90% the same as ours except a few variations or additional lines that are common among a majority of the different files I looked at. I tested two additional lines, one additional line in each ROM so if one Rom behaves differently or has a bug or improvement not found in the other it would be easier to pick out the cause.

Otherwise other then updating the AMSS version, adding missing dependency's for the media files and adding the updated code for Bionic from Cyanogen including the Scorpion Optimizations the differences between these two new test Roms and the 10.15 build are minimal.
 
Thanks for all the info. Crap, you've done a lot of work! I gotta commend you for all the patience and free time you have given the Triumph! However, besides device files, I still wish to see a Starship variant of these ROMs one day. Performance on Gingerbread in general (for any phone, especially the Triumph with the little RAM it has) lacking. Also, changing Performace settings to allow purging of assets results in the settings not sticking after reboot. Since this setting frees up RAM, could you look into it and see what's causing it not to stick? Otherwise, I can send you a logcat (if I do that, could you please tell me if system tuner allows me to test the settings app, since it's technically part of the OS) and you could investigate the issue when done with those device files. It seems that test build B is faster, but something in it is causing the camera to not connect. Also, hotspot toggling sometimes coughs up a generic error in the stable and test builds. G60's earlier builds were perfect with the hotspot functionality. Perhaps we should look into this. I had issues with the GPS and I also recommend you try FasterGPS. It made my GPS faster on CM9. I've found some issues, and perhaps I should assist you sometime soon as I will have plenty of free time in a week or two. After college finals, the semester ends and we have several weeks off. Then, I can assist you in testing. No more madman (for now) but at least you have some help. I may drop in a little Christmas donation so MTDEV doesn't run dry. I also plan on working on that FAQ during my break. I will have several weeks off, so I plan on taking at least one of these weeks to help keep the MTDEV boat afloat over these rough waters. Any tests you want then, give them to me. I will happily assist. Wifi also still has some issues on the stable builds. Hopefully we can get something done for the community before the holidays.
 
MikeRL said:
Thanks for all the info. Crap, you've done a lot of work! I gotta commend you for all the patience and free time you have given the Triumph! However, besides device files, I still wish to see a Starship variant of these ROMs one day. Performance on Gingerbread in general (for any phone, especially the Triumph with the little RAM it has) lacking. Also, changing Performace settings to allow purging of assets results in the settings not sticking after reboot. Since this setting frees up RAM, could you look into it and see what's causing it not to stick? Otherwise, I can send you a logcat (if I do that, could you please tell me if system tuner allows me to test the settings app, since it's technically part of the OS) and you could investigate the issue when done with those device files. It seems that test build B is faster, but something in it is causing the camera to not connect. Also, hotspot toggling sometimes coughs up a generic error in the stable and test builds. G60's earlier builds were perfect with the hotspot functionality. Perhaps we should look into this. I had issues with the GPS and I also recommend you try FasterGPS. It made my GPS faster on CM9. I've found some issues, and perhaps I should assist you sometime soon as I will have plenty of free time in a week or two. After college finals, the semester ends and we have several weeks off. Then, I can assist you in testing. No more madman (for now) but at least you have some help. I may drop in a little Christmas donation so MTDEV doesn't run dry. I also plan on working on that FAQ during my break. I will have several weeks off, so I plan on taking at least one of these weeks to help keep the MTDEV boat afloat over these rough waters. Any tests you want then, give them to me. I will happily assist. Wifi also still has some issues on the stable builds. Hopefully we can get something done for the community before the holidays.
Click to expand...

I can't get the camera to connect in 10.15 either. Tried force stopping / wiping / clearing yada yada... tried different camera apps (barcode scanner, instagram, facebook...) none of them can get the camera to work, just black screen that eventually asks to forceclose the camera app.
 
tridge said:
I can't get the camera to connect in 10.15 either. Tried force stopping / wiping / clearing yada yada... tried different camera apps (barcode scanner, instagram, facebook...) none of them can get the camera to work, just black screen that eventually asks to forceclose the camera app.
Click to expand...

I'm going to check my it out when I get home. I think I had this running before I broke the DEV phone. I wasn't testing the camera so I didn't check, but I think I should be able to check it out.
 
I've found that my camera issues are somehow related to wifi.

If I turn off wifi and reboot, my cameras start functioning.

I don't know why, but I can reproduce this on the last few test builds.

If wifi is off, and camera is working, wifi won't turn on, and connect correctly until I reboot with wifi on, but then I lose camera again.

Ymmv.
 
dsmryder said:
I'm going to check my it out when I get home. I think I had this running before I broke the DEV phone. I wasn't testing the camera so I didn't check, but I think I should be able to check it out.
Click to expand...



Isn't it weird how different user's have different experiences. I wish I could figure out why? I have never experienced a failure to connect to the camera in either the 10/15 or latest test builds. With that said I do at least once a flash, usually the first time I try, get a FC when switching to the FFC that requires wiping the Camera data in application settings followed by wiping the caches in recovery before opening the Camera again to fix. What is even stranger is after it happens and I do the above fix I for the life of me cant get the thing to crash on me again. Could switch the camera back and forth 100 times randomly taking pictures and recording video in-between switching back and forth and still doesn't crash again. I have had similar experiences going all the way back to TG Reloaded over now 3 different phones. A few things I have considered doing to see if any differences can be made is one, just trying pure stock code for the Camera App from Cyanogen adding back in as few edits as possible. I honestly have never really looked at the Camera code for the App itself outside of the images when I did the Starship theme so may be a job better suited for dsmryder as he has at least some experience. Another option I have actually played around with is seeing if using TJ_Styles Camera Hardware code would make a difference. I have used it before and the Camera worked perfectly fine but breaks GPS entirely. Could though do a Meld comparison between his code and ours and maybe try replacing any GPS references in his code with ours. Otherwise I am kind of stumped. I know TG had originally started making changes in the Framework to use the Stock Froyo Camera libs that had never been removed after finding the Cherry Libs worked. Could also try the libs from the other variants also. All will work except Sharp 2.3.5 and after G60 showed me a few new tricks he picked up recently working on the CM9 camera have picked out the parameters from each variants "libcamera.so" and there are a some significant differences. I'm kind of rambling at this point but now knowing how this can be done could either check each variants parameters and pick the libs from whatever variant is the most in line with those found in the CM7 code and add in whatever parameters are missing. I don't at least think any of the past CM7 devs had done this as I believe G60 has himself just recently learned how.

I think MTDEV needs a donated DeLorean along with 1.21 gigawatts, so much work and so little time. Health has also been an issue the last month or so as far as time for working on the Rom goes.
 
Chairshot, why don't you and the rest of MTDEV take the rest of this week off. I don't think I've said that for... several months LOL. Time to take a break. I feel like the slave overseer here. MTDEV has been pumping out ROMs for months on end. Maybe even take two weeks off. Madman went for months and nearly crashed until I (along with his wife nagging him) told him to take a break. How long have you been at it? Perhaps now is a good time to stop for a week or two. Just saying... Not just you, either. We need to put the hacking to recess unless anyone wants to continue at least for say two weeks. In addition, I suggest we start a beer/coffee fund for MTDEV. Nobody here is rich but we at least owe you guys a beer or cup of coffee. Not rot gut or nasty black royal farms/7-11 coffee. I mean expensive Starbucks imported blend. From some country in South America the size of Rhode Island that exports el primo beans. We used to have a tip fund. I suggest starting a separate donation for MTDEV for the holidays in the form of a beer/coffee fund. We can all chip in $5-10 and buy all of you guys caffeine and or liquid happiness.
 
Chairshot215 said:
Isn't it weird how different user's have different experiences. I wish I could figure out why? I have never experienced a failure to connect to the camera in either the 10/15 or latest test builds. With that said I do at least once a flash, usually the first time I try, get a FC when switching to the FFC that requires wiping the Camera data in application settings followed by wiping the caches in recovery before opening the Camera again to fix. What is even stranger is after it happens and I do the above fix I for the life of me cant get the thing to crash on me again. Could switch the camera back and forth 100 times randomly taking pictures and recording video in-between switching back and forth and still doesn't crash again. I have had similar experiences going all the way back to TG Reloaded over now 3 different phones. A few things I have considered doing to see if any differences can be made is one, just trying pure stock code for the Camera App from Cyanogen adding back in as few edits as possible. I honestly have never really looked at the Camera code for the App itself outside of the images when I did the Starship theme so may be a job better suited for dsmryder as he has at least some experience. Another option I have actually played around with is seeing if using TJ_Styles Camera Hardware code would make a difference. I have used it before and the Camera worked perfectly fine but breaks GPS entirely. Could though do a Meld comparison between his code and ours and maybe try replacing any GPS references in his code with ours. Otherwise I am kind of stumped. I know TG had originally started making changes in the Framework to use the Stock Froyo Camera libs that had never been removed after finding the Cherry Libs worked. Could also try the libs from the other variants also. All will work except Sharp 2.3.5 and after G60 showed me a few new tricks he picked up recently working on the CM9 camera have picked out the parameters from each variants "libcamera.so" and there are a some significant differences. I'm kind of rambling at this point but now knowing how this can be done could either check each variants parameters and pick the libs from whatever variant is the most in line with those found in the CM7 code and add in whatever parameters are missing. I don't at least think any of the past CM7 devs had done this as I believe G60 has himself just recently learned how.

I think MTDEV needs a donated DeLorean along with 1.21 gigawatts, so much work and so little time. Health has also been an issue the last month or so as far as time for working on the Rom goes.
Click to expand...
Well I just ported the Cherry kernel over to our phone and everything seems to be working, even baseband and bluetooth. I have to work back in a few things as I was trying to get BT working, but it runs like a dream on the Sharp ROM. I reworked it against my Sharp kernel so it already has all the bells and whistles along with the updated camera drivers and a bunch of other stuff. It would probably be a good match for CM7. Our version of the kernel was updated 2011/03/25 and this was updated 2011/06/09 with almost 6000 lines of changes after ours, according to History_LINUX.text in the kernels. I'll post a link when I get it worked out. If you have any questions let me know.
 
Chairshot215 said:
Isn't it weird ... I honestly have never really looked at the Camera code for the App itself outside of the images when I did the Starship theme so may be a job better suited for dsmryder as he has at least some experience. Another option I have actually played around with is seeing if using TJ_Styles Camera Hardware code would make a difference. ...

I think MTDEV needs a donated DeLorean along with 1.21 gigawatts, so much work and so little time. Health has also been an issue the last month or so as far as time for working on the Rom goes.
Click to expand...
I didn't do much to the camera. I just switched the file names for the focus ring so the ring would go green when it was focused. If could be something that could be truely fixed in the future, with the DeLorean of corse.

MikeRL said:
Chairshot, why don't you and the rest of MTDEV take the rest of this week off. I don't think I've said that for... several months LOL. Time to take a break. I feel like the slave overseer here. MTDEV has been pumping out ROMs for months on end. Maybe even take two weeks off. Madman went for months and nearly crashed until I (along with his wife nagging him) told him to take a break. How long have you been at it? Perhaps now is a good time to stop for a week or two. Just saying... Not just you, either. We need to put the hacking to recess unless anyone wants to continue at least for say two weeks. In addition, I suggest we start a beer/coffee fund for MTDEV. Nobody here is rich but we at least owe you guys a beer or cup of coffee. Not rot gut or nasty black royal farms/7-11 coffee. I mean expensive Starbucks imported blend. From some country in South America the size of Rhode Island that exports el primo beans. We used to have a tip fund. I suggest starting a separate donation for MTDEV for the holidays in the form of a beer/coffee fund. We can all chip in $5-10 and buy all of you guys caffeine and or liquid happiness.
Click to expand...

I can tell you the truth. When I get frustrated with a project (like CM6) I change gears and try another one. I have been reading how to code in Java and I think I might be able to do some of the ideas that I was thinking of. If I get burned out, I just hang with the family and appreciate them. It doesn't take much. And I still have to find something to do at night before I go to bed, hence the constant stream of "ROM support".
And as far as coffe money, I'm good. If you want to donate to the other guys I know the appreciate it.

BSydz said:
Well I just ported the Cherry kernel over to our phone and everything seems to be working, even baseband and bluetooth. I have to work back in a few things as I was trying to get BT working, but it runs like a dream on the Sharp ROM. I reworked it against my Sharp kernel so it already has all the bells and whistles along with the updated camera drivers and a bunch of other stuff. It would probably be a good match for CM7. Our version of the kernel was updated 2011/03/25 and this was updated 2011/06/09 with almost 6000 lines of changes after ours, according to History_LINUX.text in the kernels. I'll post a link when I get it worked out. If you have any questions let me know.
Click to expand...

Cool! What version of Linux is it, 2.6.10? It shouldn't be hard to "update" the kernel. I wonder if it's worth it though.
 
dsmryder said:
Cool! What version of Linux is it, 2.6.10? It shouldn't be hard to "update" the kernel. I wonder if it's worth it though.
Click to expand...
It is the exact same kernel, just updated, I uploaded an edited kernel history with just the changes after our history stopped, and the make file just so you can see the version. I have narrowed the changes needed down to a few files, to get BT and baseband correct and just need to test a few more things til I put it on my github.

Then, we may be able to use a lot of the native GB files from the other phones, possibly without any glitches, or more. :D

The only thing I have to figure out is how to change the capacitive buttons inside the kernel. I know how to change them with the key layout files, but I need to find where in the kernel it is changed.

History_LINUX.zip
 
BSydz said:
It is the exact same kernel, just updated, I uploaded an edited kernel history with just the changes after our history stopped, and the make file just so you can see the version. I have narrowed the changes needed down to a few files, to get BT and baseband correct and just need to test a few more things til I put it on my github.

Then, we may be able to use a lot of the native GB files from the other phones, possibly without any glitches, or more. :D

The only thing I have to figure out is how to change the capacitive buttons inside the kernel. I know how to change them with the key layout files, but I need to find where in the kernel it is changed.

History_LINUX.zip
Click to expand...

Take a look at Whyzor's work. I think it's incoporated into the screen driver (if that's what you mean). He rewrote the driver and made changes to the relationship to stop silly things like when you toss a bird it doesn't respond to a back button or what ever.
 
BSydz said:
It is the exact same kernel, just updated, I uploaded an edited kernel history with just the changes after our history stopped, and the make file just so you can see the version. I have narrowed the changes needed down to a few files, to get BT and baseband correct and just need to test a few more things til I put it on my github.

Then, we may be able to use a lot of the native GB files from the other phones, possibly without any glitches, or more. :D

The only thing I have to figure out is how to change the capacitive buttons inside the kernel. I know how to change them with the key layout files, but I need to find where in the kernel it is changed.

History_LINUX.zip
Click to expand...

dsmryder said:
Take a look at Whyzor's work. I think it's incoporated into the screen driver (if that's what you mean). He rewrote the driver and made changes to the relationship to stop silly things like when you toss a bird it doesn't respond to a back button or what ever.
Click to expand...
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
 
You must log in or register to reply here.
Back
Top Bottom