• 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

mantera said:
In case anyone cares, I just pushed up my latest kernel changes.
Click to expand...

You can pick up my commit for touchscreen driver updates:

https://github.com/Whyzor/triumph-kernel-msm7x30/commit/71012d2327ec632494bd610e5fe12269ba2380d8

It supports other FB0 device capacitive button layout, and less erratic finger releases. It has other changes too that I haven't tested on ICS (only CM7), if you just want the more stable finger releases, delete lines 168, 169, 184, 185.

Code: 
input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 0);
- input_report_abs(bi041p.input, ABS_MT_POSITION_X, XCORD1(buffer));
- input_report_abs(bi041p.input, ABS_MT_POSITION_Y, TS_MAX_Y - YCORD1(buffer));
input_report_abs(bi041p.input, ABS_MT_PRESSURE, 0);

input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 0);
- input_report_abs(bi041p.input, ABS_MT_POSITION_X, XCORD2(buffer));
- input_report_abs(bi041p.input, ABS_MT_POSITION_Y, TS_MAX_Y - YCORD2(buffer));
input_report_abs(bi041p.input, ABS_MT_PRESSURE, 0);
 
Whyzor said:
You can pick up my commit for touchscreen driver updates:

https://github.com/Whyzor/triumph-kernel-msm7x30/commit/71012d2327ec632494bd610e5fe12269ba2380d8

It supports other FB0 device capacitive button layout, and less erratic finger releases. It has other changes too that I haven't tested on ICS (only CM7), if you just want the more stable finger releases, delete lines 168, 169, 184, 185.

Code: 
input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 0);
- input_report_abs(bi041p.input, ABS_MT_POSITION_X, XCORD1(buffer));
- input_report_abs(bi041p.input, ABS_MT_POSITION_Y, TS_MAX_Y - YCORD1(buffer));
input_report_abs(bi041p.input, ABS_MT_PRESSURE, 0);

input_report_abs(bi041p.input, ABS_MT_TOUCH_MAJOR, 0);
- input_report_abs(bi041p.input, ABS_MT_POSITION_X, XCORD2(buffer));
- input_report_abs(bi041p.input, ABS_MT_POSITION_Y, TS_MAX_Y - YCORD2(buffer));
input_report_abs(bi041p.input, ABS_MT_PRESSURE, 0);
Click to expand...

I'll pull it in and try it out. And funny you mention this because I was just thinking of doing this and going to search on your github for it. :) Saves me the trouble.
 
mantera said:
I'll pull it in and try it out. And funny you mention this because I was just thinking of doing this and going to search on your github for it. :) Saves me the trouble.
Click to expand...

Try cherry-pick the whole changeset, I remember on the xda FB0 thread some others have complained recent CM7 roms for them broke things, not sure if it's because edowar picked up my most recent commits or he did something else to their ROM, but for us it should be fine.
 
agentc13 said:
OK, it doesn't seem to be doing as well with my home wifi. I think my work is WEP and home is WPA/WPA2 if that makes any difference. It worked superbly all day long at work though. :confused:
Click to expand...

It shouldn't make a difference. My wifi is wpa2 and it's been working mostly ok all day. Did you try rebooting to see if that makes a difference?
 
Whyzor said:
Try cherry-pick the whole changeset, I remember on the xda FB0 thread some others have complained recent CM7 roms for them broke things, not sure if it's because edowar picked up my most recent commits or he did something else to their ROM, but for us it should be fine.
Click to expand...

Just did it. building now and then will test.
 
Whyzor said:
Try cherry-pick the whole changeset, I remember on the xda FB0 thread some others have complained recent CM7 roms for them broke things, not sure if it's because edowar picked up my most recent commits or he did something else to their ROM, but for us it should be fine.
Click to expand...

Looks like something in that commit totally hosed the touchscreen. Now to figure out which part did it.

Edit: and by "totaly hosed", I mean it doesn't register any touches anymore.
 
mantera said:
It shouldn't make a difference. My wifi is wpa2 and it's been working mostly ok all day. Did you try rebooting to see if that makes a difference?
Click to expand...

OK, it is working with my other home wifi, there must just be an issue with the other one for some reason. Probably related to that router.
 
Whyzor said:
Lol, oh well. that's weird, it works on CM7. Maybe just want to delete the lines I wrote above to get the stable touch-release fixed at least. I can look into it when I get some time (or if you want to dig around, I suspect it's the register shifts & bitwise-or that I changed).
Click to expand...

Yeah, I think I'll just delete those lines and move on for now. I can look into it further at some point if you haven't done it before me.
 
mantera said:
Repo sync and try again. It looks like there were some updates upstream to frameworks/base. I just pulled in all of the updates and pushed them up.
Click to expand...

I did a repo sync and the same error, but then I deleted android and bin folders and started fresh ... Success :)

Code: 
piper@x1:~$ inxi -F
System:    Host: x1 Kernel: 3.2-7.towo.2-siduction-amd64 x86_64 (64 bit) 
           Desktop: KDE 4.7.4 Distro: siduction 11.1 One Step Beyond - pipers-kde-stripped - (201201080443)                      
Machine:   Mobo: Gigabyte model: GA-MA770-S3 version: x.x Bios: Award version: F6 date: 01/05/2009                        
CPU:       Dual core AMD Athlon 64 X2 4200+ (-MCP-) cache: 1024 KB flags: (lm nx sse sse2 sse3 svm)                       
           Clock Speeds: 1: 1000.00 MHz 2: 1000.00 MHz                                                                    
Graphics:  Card: nVidia GF106 [GeForce GTS 450] X.Org: 1.11.3.901 driver: nvidia Resolution: 1920x1200@50.0hz             
           GLX Renderer: GeForce GTS 450/PCIe/SSE2 GLX Version: 4.2.0 NVIDIA 295.20                                       
Audio:     Card-1: ATI SBx00 Azalia (Intel HDA) driver: snd_hda_intel Sound: ALSA ver: 1.0.24                             
           Card-2: nVidia GF106 High Definition Audio Controller driver: snd_hda_intel                                    
Network:   Card: Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller driver: r8169                              
           IF: eth0 state: up speed: 100 Mbps duplex: full mac: 00:1d:7d:d8:0e:cf                                         
Drives:    HDD Total Size: 2320.5GB (59.6% used) 1: /dev/sda ST3320620AS 320.1GB                                          
           2: /dev/sdc ST31000528AS 1000.2GB 3: /dev/sdb ST31000528AS 1000.2GB                                            
Partition: ID: / size: 187G used: 38G (21%) fs: reiserfs ID: swap-1 size: 1.07GB used: 0.10GB (9%) fs: swap               
Sensors:   System Temperatures: cpu: 18.0C mobo: N/A gpu: 31C
 
One Big issue is the gaming for me ive tried doing everything as said but after playing a game for awhile the game randomly forcloses and sometimes only plays for 5 mins take in note thsi game doesnt require large cpu speeds or anything.
 
Earlier today Lord clockan and existz got omx video decoding working for the desire hd, which has a very similar chip to the triumph.

I've been following their work and believe i understand what they did. I was trying to merge it into our source last night and kept getting build errors. I got past a few errors last night but the build was still failing.

This morning I found and fixed that build error but had to leave for work before the build finished.

So when i get home, I'll either find a completed build or a new error. if it did build successfully, i have no idea if the fixes will actually work.

I'll post an update in about 6 hours. Wish me luck
 
NateMckn said:
Earlier today Lord clockan and existz got omx video decoding working for the desire hd, which has a very similar chip to the triumph.

I've been following their work and believe i understand what they did. I was trying to merge it into our source last night and kept getting build errors. I got past a few errors last night but the build was still failing.

This morning I found and fixed that build error but had to leave for work before the build finished.

So when i get home, I'll either find a completed build or a new error. if it did build successfully, i have no idea if the fixes will actually work.

I'll post an update in about 6 hours. Wish me luck
Click to expand...

very nice. good luck.
 
MotoTriumphGuy said:
One Big issue is the gaming for me ive tried doing everything as said but after playing a game for awhile the game randomly forcloses and sometimes only plays for 5 mins take in note thsi game doesnt require large cpu speeds or anything.
Click to expand...

Is it one game? or every game? I personally haven't noticed any particular app force closing on my phone in a while.

It's possible that it's just that app that needs to be updated by the app's dev for ics.
 
Can someone that has a headset with media controls try flashing the attached zip in cwm and then test to see if the media controls work afterwards? Thanks.
 
Mantera, I'm not sure if anyone ever tried that app you suggested to give you button numbers, but I just did it. I have a headset with one button that would typically act as a play/pause/answer call button, and it's showing as key number 226.
 
wsimon said:
You guys may already know this but I just found out about this as I was pulling apart the andro-id rom trying to get a hdmi fix.

There is a kernel logging daemon that will intercept kernel messages and log them so you can see them in logcat. See klogd - Linux Command - Unix Command

Here is the one I grabbed from the andro-id rom: klogd

Just adb push it to /system/bin/ then give it permissions to execute and run it. You will then see the kernel messages in the logcat.

Its helping me narrow down the hdmi problem so I figured it might be able to help you guys as well.
Click to expand...
I finally got a chance to sit down with my new HDMI cables and start poking around with it. Went to search through this thread and just now made the connection that it was your computer that died :(

Looks like the phone is detecting my TV is 720p, but hdmid wont start because of a missing symbol -

Code: 
root@android:/ # /system/bin/hdmid
reloc_library[1314]:  5341 cannot locate '_ZN7android21SurfaceComposerClient16enableHDMIOutputEi'...
CANNOT LINK EXECUTABLE
Is this similar to how you started? Do you have any pointers in the direction you went?
 
NateMckn said:
Earlier today Lord clockan and existz got omx video decoding working for the desire hd, which has a very similar chip to the triumph.

I've been following their work and believe i understand what they did. I was trying to merge it into our source last night and kept getting build errors. I got past a few errors last night but the build was still failing.

This morning I found and fixed that build error but had to leave for work before the build finished.

So when i get home, I'll either find a completed build or a new error. if it did build successfully, i have no idea if the fixes will actually work.

I'll post an update in about 6 hours. Wish me luck
Click to expand...


Update: So my build from this morning completed. I flashed it to test out video, only to learn i broke sound. And video doesn't work (i suspect due to the broken sound).

I think i found the problem and am recompiling now

Edit: Fixed sound but video decoding still doesn't work. Hmm...
 
aaronfitz said:
I finally got a chance to sit down with my new HDMI cables and start poking around with it. Went to search through this thread and just now made the connection that it was your computer that died :(

Looks like the phone is detecting my TV is 720p, but hdmid wont start because of a missing symbol -

Code: 
root@android:/ # /system/bin/hdmid
reloc_library[1314]:  5341 cannot locate '_ZN7android21SurfaceComposerClient16enableHDMIOutputEi'...
CANNOT LINK EXECUTABLE
Is this similar to how you started? Do you have any pointers in the direction you went?
Click to expand...

Yes, I was getting this too on CM9 and CM7 built from Mantera's github. Tickerguy's CM7, however, does not have problems starting and running hdmid.
Mantera, is it possible you removed something that could be causing this? I didn't look into this much so I have no idea why it wouldn't be starting on your version.

I was trying to grab the working pieces from the Andro-id rom which is here: http://androidforums.com/triumph-all-things-root/403007-rom-andro-id-v-3-3-rc2.html#post3150518
That is a gingerbread based rom (for another phone) that has working hdmi when flashed on our phone. I was trying to first get it to work on CM7 first because that rom is GB based.

That Andro-id rom has a different hdmi daemon that you can grab, but it is more than just that. There are also some changes that need to be made in the boot.img. I tore apart its boot.img by doing this: HOWTO: Unpack, Edit, and Re-Pack Boot Images - Android Wiki
I grabbed some of the changes dealing with hdmi (such as in the init.rc file) found in the boot.img and I was trying to build Tickerguy's CM7 with those changes when my computer died. I am not sure if Tickerguy's CM7 is in a buildable state though because I was getting some errors, some of which I got past, but I don't know if I got past them all.


I did find out it was my power supply that was the problem (even though everything was powering on and seemed to be running fine) so I have got a new one (with a shiny new tower :)) on its way.
 
You must log in or register to reply here.
Back
Top Bottom