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

Root [DEV] Continuing Triumph ICS Development

I'm currently resyncing the ics build, and the git is pulling down everything it seems. It looks crazy. We'll see what happens in the morning. Hopefully I won't have the entire git sitting on my home folder. :/
 
tusing said:
Oh, thanks! Didn't know.

Edit:

Are there any other phones that have the same Ardeno 205 and msm7x30 chip as we do? If their community has CM9 fully working, we can just visit their Github pages and look through the files to see what we are missing.


Huawei Honor/Glory /Mercury use the same chipset as the Triumph. Huawei released a version of ICS for these phones.
The Mercury is a CDMA phone on Cricket.
Click to expand...
 
skarni said:
tusing said:
Oh, thanks! Didn't know.

Edit:

Are there any other phones that have the same Ardeno 205 and msm7x30 chip as we do? If their community has CM9 fully working, we can just visit their Github pages and look through the files to see what we are missing.


Huawei Honor/Glory /Mercury use the same chipset as the Triumph. Huawei released a version of ICS for these phones.
The Mercury is a CDMA phone on Cricket.
Click to expand...


Then why not use that source for the Adreno 205 and our processor? And kernel 3.0 (would have to rewrite less drivers?)
Sorry if this has been asked before. Just trying to figure out how this stuff works.
Click to expand...
 
Each manufacturer adds their own modifications to the linux kernel to work with the combination of hardware included. Even the FB0 devices have different touchscreens & wifi drivers as an example. Various manufacturer phones using the same Qualcomm chip have even more differences.
 
Whyzor said:
Each manufacturer adds their own modifications to the linux kernel to work with the combination of hardware included. Even the FB0 devices have different touchscreens & wifi drivers as an example. Various manufacturer phones using the same Qualcomm chip have even more differences.
Click to expand...

Did you talk to Isaac about the (CAF msm I assume) 3.0 kernel he has building? Can he upload it to github? I was thinking of giving it a go, but if he's already merged some fb0 changes in, so much the better. EDIT: never mind, just saw Isaac's comment on github...
 
Apparently he has never worked on a 3.0 kernel, only provided a link to a CAF version. There is history of what Motorola changed in one of his previous commits for the ICS kernel.
 
hey guys great job with this rom I'm loving it thanks to all who helped in this I was wondering if there would be a way to have the soft keys enabled on this rom I really like those for some reason and was just wondering if it could be done thanks again guys and keep up the good work I will definately be donating
 
Ok, so I updated the kernel for data usage tracking. Needs to be tested first but assuming it all works, will add it to the repo and push it tomorrow. As a preliminary test, it looks like everything is working. If you want to build your own kernel, I already pushed the changes up for that. But i won't push the prebuilt to the device repo for now.
 
Twizted6789 said:
hey guys great job with this rom I'm loving it thanks to all who helped in this I was wondering if there would be a way to have the soft keys enabled on this rom I really like those for some reason and was just wondering if it could be done thanks again guys and keep up the good work I will definately be donating
Click to expand...


you mean those 3 buttons on the galaxy nexus?

well the thing about it is that the Triumphs screen is 16:10 aspect ratio, not tall enough. it would squish every app down.

the galaxy nexus and some other phones have a 16:9 display which is actually long enough to have those keys not impact any of the app space.

the triumph is 480x800, but if you made it true 16:9, it would be 480x854 and those 54 pixels would completely cover the 4 buttons we have there now.

easier to use the ones we already have and keep the screen real estate.
 
mantera said:
Ok, so I updated the kernel for data usage tracking. Needs to be tested first but assuming it all works, will add it to the repo and push it tomorrow. As a preliminary test, it looks like everything is working. If you want to build your own kernel, I already pushed the changes up for that. But i won't push the prebuilt to the device repo for now.
Click to expand...

This will be a flashable kernel zip like an austrie kernel right? Could you do that? I'm liking 6.0 as of now and don't want to keep wiping.. I'll wait for more major changes..
 
Raptor5150 said:
This will be a flashable kernel zip like an austrie kernel right? Could you do that? I'm liking 6.0 as of now and don't want to keep wiping.. I'll wait for more major changes..
Click to expand...

you could just pull it from the rom zip and replace the current one in the one you have now and reflash if you wanted or go into bootloader and do it on your computer. And I'm taking about the boot.img (aka the kernel)
 
Raptor5150 said:
This will be a flashable kernel zip like an austrie kernel right? Could you do that? I'm liking 6.0 as of now and don't want to keep wiping.. I'll wait for more major changes..
Click to expand...


You don't have to wipe every time you install a new ROM or kernel. Just wipe the cache, Dalvik cache, and repair permissions (just in case) and install the zip. It takes like 20 minutes at the most to do this.
 
Raptor5150 said:
This will be a flashable kernel zip like an austrie kernel right? Could you do that? I'm liking 6.0 as of now and don't want to keep wiping.. I'll wait for more major changes..
Click to expand...

You shouldn't have to wipe. You can just install over the previous build. You still need to reflash GAPPS also though.

If you run into issues, then do a full wipe, etc.
 
Twizted6789 said:
hey guys great job with this rom I'm loving it thanks to all who helped in this I was wondering if there would be a way to have the soft keys enabled on this rom I really like those for some reason and was just wondering if it could be done thanks again guys and keep up the good work I will definately be donating
Click to expand...

There is not currently a setting that will just enable the 3 softkeys without making a separate build with them enabled.

I did read that at some point CM is supposed to add a setting so a user can toggle them on/off but I have not seen it come down the pipe yet.
 
konspiracy said:
Im sorry guys I went back through the old thread and got it confused.

All he did was backport the genlock driver and some other stuff

http://androidforums.com/triumph-al...nly_-building-ics-source-isaacs-github-5.html


All of this stuff is in the experimental version of his kernel.
Click to expand...

was it just the modified stock kernel, or something else? Like the .39 maybe?

*edit* I saw something about edowar having possible camera working? Is this something we could use as well?
 
sharpe351 said:
was it just the modified stock kernel, or something else? Like the .39 maybe?

*edit* I saw something about edowar having possible camera working? Is this something we could use as well?
Click to expand...

No, he hasn't yet--at least the last comment that I saw from him anyways a day or two ago. And he was just pointing to another dev that had gotten it to work. But we already have the same things in our build and, as you can see, it doesn't work. I wish it had been that simple though.
 
Mantera, here is a logcat of exactly what my phone is doing when trying to activate the Camera app. It appears that it is looking for a file that doesn't exist (?). Looks like we are missing the HAL module? I'm new at this, just thought it might be useful to you guys. Pastebin has the logcat, didn't want to post it, the file is long... logcat...CameraActionICS - Pastebin.com
 
I have been working on some kernel source for a while and haven't been on the forum. I finally have gotten it to build after about 2 weeks of troubleshooting. Basically I have pulled mantera's .config from his edited kernel from Motorola Source and built using that. My question is how do I incorporate the zImage to mantera's ICS source code?

My guess is I rename the zImage located in /arch/arm/boot to kernel and replace the kernel file located in mantera's android/device/motorola/triumph is that correct? If that is the case what about the recovery_kernel?

I was trying to use fastboot to test out my zImage but it doesn't look like our phone is setup to do fastboot? I tried the command fastboot devices from the recovery mode, the volume down boot mode, and with the normal boot up with no love.
 
g60madman said:
I have been working on some kernel source for a while and haven't been on the forum. I finally have gotten it to build after about 2 weeks of troubleshooting. Basically I have pulled mantera's .config from his edited kernel from Motorola Source and built using that. My question is how do I incorporate the zImage to mantera's ICS source code?

My guess is I rename the zImage located in /arch/arm/boot to kernel and replace the kernel file located in mantera's android/device/motorola/triumph is that correct? If that is the case what about the recovery_kernel?

I was trying to use fastboot to test out my zImage but it doesn't look like our phone is setup to do fastboot? I tried the command fastboot devices from the recovery mode, the volume down boot mode, and with the normal boot up with no love.
Click to expand...

If you put it in device/motorola/triumph/kernel, & rebuild ROM, it'll automatically use it as the OS kernel. As for recovery, I wouldn't worry about that. I spend little time in recovery mode (just flashing new ROMs or kernels), users probably spend even less time, so as long as it's stable and works, no need to update recovery image or kernel.

Building Kernel from source - CyanogenMod Wiki

To build a flashable .zip, download either TheOC flashable zip or one of my CM7 kernel flashable zips, then using the same 'mkbootimg' line that's generated by the ROM building towards the end. Tell it which ramdisk to use and zImage and it'll produce a boot.img, replace that boot.img into the flashable zip and you can flash just the kernel onto an existing ROM. This is faster way of testing than rebuilding & flashing the ROM every time.
 
g60madman said:
I have been working on some kernel source for a while and haven't been on the forum. I finally have gotten it to build after about 2 weeks of troubleshooting. Basically I have pulled mantera's .config from his edited kernel from Motorola Source and built using that. My question is how do I incorporate the zImage to mantera's ICS source code?

My guess is I rename the zImage located in /arch/arm/boot to kernel and replace the kernel file located in mantera's android/device/motorola/triumph is that correct? If that is the case what about the recovery_kernel?

I was trying to use fastboot to test out my zImage but it doesn't look like our phone is setup to do fastboot? I tried the command fastboot devices from the recovery mode, the volume down boot mode, and with the normal boot up with no love.
Click to expand...

If you build a flashable zip for the up to date kernel share the love :) plz and thank you ^_^ (I know mantera. . I know...)
 
This is copied from another thread! But hell try it. There is a guy using our fixes on a non msm device

I'm going to drop by and pass along some little info that might help with the camera, cant guarantee anything but its worth a shot, hell i don't even know if you even have tried this yet but here it is

http://forum.xda-developers.com/showpost.php?p=21734698&postcount=125

might have to fix some of the permissions in the init.rc too

for the shift the additions to the init.rc looks like this:
Code: 
 #Add permissions for camera access
chmod 0666 /dev/msm_camera/config0

chmod 0666 /dev/msm_camera/control0

chmod 0666 /dev/msm_camera/frame0

chmod 0666 /dev/graphics/fb0

of course the intercept will be different but I'm sure you get the idea

here is addition info on the camera HAL, i know this is for other phones but some of it could help get you in the right direction.

http://forum.xda-developers.com/showthread.php?t=1427030
 
ziggy46 said:
This is copied from another thread! But hell try it. There is a guy using our fixes on a non msm device

I'm going to drop by and pass along some little info that might help with the camera, cant guarantee anything but its worth a shot, hell i don't even know if you even have tried this yet but here it is

http://forum.xda-developers.com/showpost.php?p=21734698&postcount=125

might have to fix some of the permissions in the init.rc too

for the shift the additions to the init.rc looks like this:
Code: 
 #Add permissions for camera access
chmod 0666 /dev/msm_camera/config0

chmod 0666 /dev/msm_camera/control0

chmod 0666 /dev/msm_camera/frame0

chmod 0666 /dev/graphics/fb0

of course the intercept will be different but I'm sure you get the idea

here is addition info on the camera HAL, i know this is for other phones but some of it could help get you in the right direction.

http://forum.xda-developers.com/showthread.php?t=1427030
Click to expand...

Good find Ziggy, hopefully we can make good use of it. Did you get your homework done before you started searching around?
 
You must log in or register to reply here.
Back
Top Bottom