• 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

tusing said:
So, it boils down to this?

  • There must be something off with the current kernel, which is why hardware acceleration isn't working fully
  • If it's not that, then it would be nearly impossible to hand-code all of the material needed for a 3.0 kernel (unless we march with fire and pitchforks to Moto's HQ)?
Click to expand...

Just a thought,

Are you sure its just not the launcher that's being laggy by itself? I always thought the GB launcher was laggy, especially the app drawer scrolling. I would just always install launcher pro over it and things would be much smoother.
 
wanfaltm said:
Just a thought,

Are you sure its just not the launcher that's being laggy by itself? I always thought the GB launcher was laggy, especially the app drawer scrolling. I would just always install launcher pro over it and things would be much smoother.
Click to expand...

I doubt the UI could be that laggy, but I could be wrong. We have a 1 GHz processor like the Nexus S, yet Android 4.0 is smooth as butter on that.
 
tusing said:
So, it boils down to this?

  • There must be something off with the current kernel, which is why hardware acceleration isn't working fully
  • If it's not that, then it would be nearly impossible to hand-code all of the material needed for a 3.0 kernel (unless we march with fire and pitchforks to Moto's HQ)?
Click to expand...

Ok, here's a little something to back this... A while ago, I had a ViewSonic Gtab. The devs there spent 6+ months with 10 or more people trying to hand code the drivers for the 2.6.36.x kernal. The project was eventually partially abandoned due to the difficulty involved in porting everything that makes the tablet function. The hardest, if memory serves, was hardware acceleration. The Tegra 2 processor is a beast. It works great and has little to complain about. The kernals, without open source access (like ours and ViewSonic's), tend to make things really screwy when trying to make something work without anything to go by. I moved on to the Asus Transformer (TF101) from the Gtab, but things are easier on the TF front as they have released the kernal source. Everything on the ICS port there has been easier to conquer (from 2.6.36.x to 2.6.39.x kernal replacement) due to open source for drivers and such.

Here's the dilemma, IF we go into uncharted territory with the 3.0 kernal, we're looking at hand coding ALL the drivers to make the ROM function. This could take a GOD in the dev world at least a year to code, working on it full time. We don't have the manpower as a collective to hand code functioning drivers for the kernal. I like the work that has gone on here, using our available resources to get things working. Things like the camera may take longer to get functioning, but it is possible in our current kernal. My friend said that at the rate we are progressing, the other issues are small potatoes compared to what we'd deal with on a kernal port. He also went on to say that the ROM, as it stands should be at beta stage within a month or two. Not sure what he meant there, but I'm merely relaying information. I think he's read through the dev thread a few times. He said he might be some help, but things at his job have ramped up for some big project and he also has NO time lately to do any extracurricular programming, and no phone to work with.
 
sharpe351 said:
Ok, here's a little something to back this... A while ago, I had a ViewSonic Gtab. The devs there spent 6+ months with 10 or more people trying to hand code the drivers for the 2.6.36.x kernal. The project was eventually partially abandoned due to the difficulty involved in porting everything that makes the tablet function. The hardest, if memory serves, was hardware acceleration. The Tegra 2 processor is a beast. It works great and has little to complain about. The kernals, without open source access (like ours and ViewSonic's), tend to make things really screwy when trying to make something work without anything to go by. I moved on to the Asus Transformer (TF101) from the Gtab, but things are easier on the TF front as they have released the kernal source. Everything on the ICS port there has been easier to conquer (from 2.6.36.x to 2.6.39.x kernal replacement) due to open source for drivers and such.

Here's the dilemma, IF we go into uncharted territory with the 3.0 kernal, we're looking at hand coding ALL the drivers to make the ROM function. This could take a GOD in the dev world at least a year to code, working on it full time. We don't have the manpower as a collective to hand code functioning drivers for the kernal. I like the work that has gone on here, using our available resources to get things working. Things like the camera may take longer to get functioning, but it is possible in our current kernal. My friend said that at the rate we are progressing, the other issues are small potatoes compared to what we'd deal with on a kernal port. He also went on to say that the ROM, as it stands should be at beta stage within a month or two. Not sure what he meant there, but I'm merely relaying information. I think he's read through the dev thread a few times. He said he might be some help, but things at his job have ramped up for some big project and he also has NO time lately to do any extracurricular programming, and no phone to work with.
Click to expand...


So if we can just port kernel 2.6.39.x things will be easier for us?
 
wanfaltm said:
Just a thought,

Are you sure its just not the launcher that's being laggy by itself? I always thought the GB launcher was laggy, especially the app drawer scrolling. I would just always install launcher pro over it and things would be much smoother.
Click to expand...


I have go launcher n having no problems
 
ziggy46 said:
So if we can just port kernel 2.6.39.x things will be easier for us?
Click to expand...

not totally sure. That will be my next email. I think that without source any port will be difficult. It might be less dificult, but we would need some semblance of source to go by.

He also said that there is problems in the AOSP source from Google. There are bits and pieces missing for a full build, so that may be part of the problem with CyanogenMod.
 
sharpe351 said:
Ok, here's a little something to back this... A while ago, I had a ViewSonic Gtab. The devs there spent 6+ months with 10 or more people trying to hand code the drivers for the 2.6.36.x kernal. The project was eventually partially abandoned due to the difficulty involved in porting everything that makes the tablet function. The hardest, if memory serves, was hardware acceleration. The Tegra 2 processor is a beast. It works great and has little to complain about. The kernals, without open source access (like ours and ViewSonic's), tend to make things really screwy when trying to make something work without anything to go by. I moved on to the Asus Transformer (TF101) from the Gtab, but things are easier on the TF front as they have released the kernal source. Everything on the ICS port there has been easier to conquer (from 2.6.36.x to 2.6.39.x kernal replacement) due to open source for drivers and such.

.
Click to expand...

sharpie-Just to let you know that ICS port for the gTab has been released with hardware acceleration.It is still a bit buggy but just about everything,other than camera, works. I believe the team built the kernel and the ROM from ground up.
 
Can anyone give me some clues as to go about maybe coming up with a Camera fix? I'm thinking some hardware files (obviously) but could it be kernel related as well?
 
viskon said:
sharpie-Just to let you know that ICS port for the gTab has been released with hardware acceleration.It is still a bit buggy but just about everything,other than camera, works. I believe the team built the kernel and the ROM from ground up.
Click to expand...

Yea, I kept up with it a little bit, and yes, they did manage to build one, but the same team has been working on Honeycomb for longer and esentially walked away. I understood that a bit "buggy" may be an understatement due to the need to force reset the tablet after the processor goes to full tilt overclock on a whim. There are still issues, but I applaud their work. Those guys worked for months to get that going, and there has been no reference to a 3.0 kernel.

My friend says the 3.0 kernal offers better stability, but his system using said kernal is still acting strange from time to time.
 
Motorola released the Triumph kernel source code sometime back
Does that make it easier to port the kernel drivers to kernel 3.0?
 
hellosiva said:
Motorola released the Triumph kernel source code sometime back
Does that make it easier to port the kernel drivers to kernel 3.0?
Click to expand...

where is it? That would make it easier. I understood that they only released the driver source for the camera.
 
marc12868 said:
This? Triumph WX435 / Home / Home
Click to expand...

Is this the complete package? A dev would have to look at it to know. If this is the source, then yes, if not we're screwed. I looked at the files available, but it doesn't seem to look complete. It may be what they said about releasing only the camera stuff. Can yumbrad or Whyzor confirm this?

*edit* I see that most everything is here needed to build, but I would recommend going along the lines of the 2.6.36 --or .39.x build. It may be more stable than trying to setup for 3.0. Source makes things easier. It also appears to be a more up to date kernal. Can someone compile it and see what spits out the other end?
 
yumbrad said:
Getting haptics working with the capacitive buttons was indeed a pretty easy fix. While I was at it, I made sure to understand what input devices we actually have, what keys each can generate, and I cleaned up the keylayouts, which had a bunch of misleading mappings. Devices that only apply to qualcomm evaluation hardware, kitchen sink mappings in devices that only generate one or two events, etc.. I'll push it up and send a pull request, mantera.
Click to expand...

I reverted this fix for now. It broke the HOME button long press for recent apps.
 
sharpe351 said:
Is this the complete package? A dev would have to look at it to know. If this is the source, then yes, if not we're screwed. I looked at the files available, but it doesn't seem to look complete. It may be what they said about releasing only the camera stuff. Can yumbrad or Whyzor confirm this?
Click to expand...

That is not the whole set of files. Only a select set. And there's nothing in there for camera stuff. I would bet that if there were, tickerguy would have used it.
 
mantera said:
That is not the whole set of files. Only a select set. And there's nothing in there for camera stuff. I would bet that if there were, tickerguy would have used it.
Click to expand...

figured as much. Is it updated? Changelog looks to be edited quite a bit.
 
This is the source for the current kernel that we're already using. It is even older than what the phones are shipping with (.39 vs .38). We need newer source for either the MT or an FB0 board phone. I heard Doomlord or TjStyle had a newer version of source (2.35.x). Havent looked into it much.
 
Okay guys, Isaac has already ported a 3.0 kernel but he never uploaded it to github.
He gave it to me for testing but genlock was keeping it from booting.


Mantera or Whyzor if you could get his email off of github and send him a message he said he would be checking that from time to time.

If he can upload what he has got then we the "Triumph" community will have alot more to work off of.
 
konspiracy said:
Okay guys, Isaac has already ported a 3.0 kernel but he never uploaded it to github.
He gave it to me for testing but genlock was keeping it from booting.


Mantera or Whyzor if you could get his email off of github and send him a message he said he would be checking that from time to time.

If he can upload what he has got then we the "Triumph" community will have alot more to work off of.
Click to expand...

If Issac already ported the 3.0 kernel, then why didn't someone say something before? Is the genlock issue the only thing not functioning properly, or is there more to it than that?
 
You must log in or register to reply here.
Back
Top Bottom