• 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

Have you tried pushing /system/bin/vold from CM7 to ICS? That's how they fixed the SD Card on the Kindle Fire ICS ROM. I would try but this laptop is a piece of crap and it would take forever to build ICS. I'm building a new PC in about a week though so I will try to help :)
EDIT: Someone already posted it :x whoops.
 
Question - where did the EGL binary blobs come from in your repo mantera? Did anyone ever try any EGL libs from the xperia play or other leaked ICS roms? Is that what edowar is using?

We're currently not using any proprietary blobs. Just the video drivers in the kernel. Basically, I had to comment out the lines that copied over the proprietary blobs that we had since they were causing bootloops. See the device_triumph.mk file.

Although I just saw that I commented out two files that may be needed. I'll try including them in my next build and seeing if they make any difference for the video.

Here's our problem with the phone startup:

https://github.com/CyanogenMod/android_frameworks_base/commit/92768571ff4871198f45bd1726bd8b4b05dc186b

in CM7 they used that class name as a generic string to match on, officially only for "samsung," but TickerGuy used the same pathway to work around Qualcomm-specific problems. Shouldn't be too hard to fix, don't have time right now so feel free to look at it.. (Probably want to use samsung as a model, as I assume they updated that to use the new reflection).

I haven't had a chance to look into it much either. So if you do get a chance to do that, good luck!
 
Just leaving this out there. If anyone needs "building" let me know. I'm new to this, but I can do it. My rig is more than powerful enough to compile.

PII X4 3.2Ghz
Radeon 6870
8GB DDR3 1600
20Mbs Internet.

Shouldn't take much to build. Let me know.

Just wanna give back to the community.
 
Take a look at this guys

xda-developers - View Single Post - [DEV][WiP][ROM] CyanogenMod 9! - The TE4M - Build 1 UP [21-01-12]

So it looks like we need to add our version to the build prop.

Earlier in this thread, Yumbrad had found that commenting out that line in the build.prop stops the fc's. However, even after doing that, you still don't have the radio working. We still have no service. So there's more stuff needed.

But it sounds like that line just needs to go in general. So I'll comment that out and push it up later to the repo.

EDIT: On a good note, I'm happy to report that it looks like I now have the sdcard mounting and the USB mount works now! Woohoo! It needs a little more testing but I'll push up my latest changes tonight.
 
That's why I thought it was a radio issue. It can't create the triumph telephony class and so it's crashing. But I could be wrong about that. Anyone else?

Thats exactly what the problem is

im gonna try setting the telephony app back t the original way. will post back if it fixes anything.
 
Earlier in this thread, Yumbrad had found that commenting out that line in the build.prop stops the fc's. However, even after doing that, you still don't have the radio working. We still have no service. So there's more stuff needed.

But it sounds like that line just needs to go in general. So I'll comment that out and push it up later to the repo.

EDIT: On a good note, I'm happy to report that it looks like I now have the sdcard mounting and the USB mount works now! Woohoo! It needs a little more testing but I'll push up my latest changes tonight.

Sweet!
I was gonna ask did you get the kernel changes from edowars stuff?
I cherry picked his stuff from doomlord and the kernel actually built. But i didnt know if you had already done that...
 
Sweet!
I was gonna ask did you get the kernel changes from edowars stuff?
I cherry picked his stuff from doomlord and the kernel actually built. But i didnt know if you had already done that...

Yep. That should already be in there unless you're referring to something committed in the last few days.
 
So you already have the kgsl driver in there?
So why does hwAcceleration work for the ideos and not us?

No idea, off-hand. It needs more research. I wanted to get the sdcard working first so I can actually move files on/off while the rom was loaded so I didn't have to keep flashing back to a different rom or taking my SD card out just to load files.
 
No idea, off-hand. It needs more research. I wanted to get the sdcard working first so I can actually move files on/off while the rom was loaded so I didn't have to keep flashing back to a different rom or taking my SD card out just to load files.

Ya i tried a couple build.prop edits but It just says sdcard is safe to remove. lol
 
So you already have the kgsl driver in there?
So why does hwAcceleration work for the ideos and not us?

At least one part of the problem is the mismatch I mentioned before between msm_mdp.h in the kernel (older) and userspace (a bit newer). I was planning to backport the msm mdp display code from the msm-2.6.38 kernel if the 2.3.35.7 sources from tjstyle are too difficult to bring up, or don't have the newer version.
 
At least one part of the problem is the mismatch I mentioned before between msm_mdp.h in the kernel (older) and userspace (a bit newer). I was planning to backport the msm mdp display code from the msm-2.6.38 kernel if the 2.3.35.7 sources from tjstyle are too difficult to bring up, or don't have the newer version.

Well maybe we can look far enough back and figure out how isaac had gotten hardware accel to run enough that the phase wallpaper could run.

Also have you tried looking into porting the mdp.h from the ideos 8150? it uses the same kernel right?

Im going to try cherry picking some stuff from the thunderbolt. as they seem to have H.Acc working perfect.
 
Earlier in this thread, Yumbrad had found that commenting out that line in the build.prop stops the fc's. However, even after doing that, you still don't have the radio working. We still have no service. So there's more stuff needed.

But it sounds like that line just needs to go in general. So I'll comment that out and push it up later to the repo.

EDIT: On a good note, I'm happy to report that it looks like I now have the sdcard mounting and the USB mount works now! Woohoo! It needs a little more testing but I'll push up my latest changes tonight.

might I ask how? It interests me. Lol
 
This may seem a little dumb, but I'm fairly new at this. Is there a specific area within the source (certain folders or sub folders) where most of the changes we need to make to get things like wifi, data, and everything else working? Or is it more of an allover the place sort of thing?

Or are there at least some directories we know we wont need to mess with so we can rule them out in the hunt for fixes.
 
Well maybe we can look far enough back and figure out how isaac had gotten hardware accel to run enough that the phase wallpaper could run.

Also have you tried looking into porting the mdp.h from the ideos 8150? it uses the same kernel right?

Im going to try cherry picking some stuff from the thunderbolt. as they seem to have H.Acc working perfect.

It's tricky to say, since things were changing REALLY fast (they're only kind of fast now) in ics/CM9 when Isaac was bringing it up, and some things were more similar to gingerbread/CM7 than they are now.

What's interesting is there are various HW accel'd pieces (copybit, overlay, gralloc, etc..), and it seems that the qcom display libraries fallback to software rendering successfully if one or more pieces don't work. So I think devices probably have a range of HW acceleration working at this point, and none of the ones closest to ours that I've checked out have everything working - for instance all the ideos ports (including edowar's) seem to have the mismatch that would disable overlay - but copybit may be working, I don't know. The good news is that ICS may run very fast on the adreno once we have all the elements working. I'll take a look at the thunderbolt, haven't looked at their code.
 
This may seem a little dumb, but I'm fairly new at this. Is there a specific area within the source (certain folders or sub folders) where most of the changes we need to make to get things like wifi, data, and everything else working? Or is it more of an allover the place sort of thing?

Or are there at least some directories we know we wont need to mess with so we can rule them out in the hunt for fixes.

If CM9 didn't have bugs, all we would have to worry about are device/motorola/triumph and the kernel. But things are far from perfect.
 
Just a quick question from me... is thee the possibility of you guys getting BT to work? Apparently Onlive only supports 4.0 with use of the controller I just got... makes me wanna get tablet now :/

It just isn't fair... sigh ill be waiting to try that first beta build I assure you lol but I'm just curious about the bluetooth

Thanks :)
 
Just a quick question from me... is thee the possibility of you guys getting BT to work? Apparently Onlive only supports 4.0 with use of the controller I just got... makes me wanna get tablet now :/

It just isn't fair... sigh ill be waiting to try that first beta build I assure you lol but I'm just curious about the bluetooth

Thanks :)


BT works now as far as I can tell. I'm able to pair a headset to it. But audio doesn't work yet so I can't test beyond that so that's why it's not on the working list.
 
If CM9 didn't have bugs, all we would have to worry about are device/motorola/triumph and the kernel. But things are far from perfect.

well aside from the random CM9 issues, would that be where to start working to get all of the hardware components working?
 
Back
Top Bottom