• 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

aaronfitz said:
Wow guys, I'm impressed! I stopped getting emails from the forums about a month ago when it looked like development was stagnant and the ICS kernel still wasn't booting. I hopped on here planning to start poking at the kernel again since I got a new machine, and the work is much farther than I expected! Great work guys!

I just pulled all of the current source and have an image which booted right up on my phone. Note to any Arch Linux users out there though--I got almost all the way to the end of the build and OpenJDK6 segfaulted. I had to go pull the Oracle jre6/jdk6 from AUR.

I saw someone saying their Wifi still wasn't working after the Wifi fixes got merged. I just wanted to check in that Wifi is working on my phone just fine. I'm only seeing ~7Mbps on the Speedtest.net app (I have a 25Mbps connection), but my cable has been a little wonky today so it might not be the phone causing the slowdown there.

I do kernel/driver development at work (not Android though) so I'd like to chip in and get m y hands dirty with something low priority (I'm also married and working towards a Masters so I don't have a ton of free time). I see the cameras and MMS aren't working, but those are probably too critical for me.. is anyone looking at HDMI yet? I might order a cable and start looking there. I had a logcat going during my first boot of the ROM and saw the HDMI service attempted to start, at least.
Click to expand...

If you could look into getting hdmi working that would be a God send thanks!!
 
Had to switch back. the ROM kept rebooting after lockscreen for 15 minutes. Also when I tried to turn on wifi after 2 reboots.
 
Whyzor said:
I just commited a new version of the touchscreen driver that actually uses my re-write, tested to work with ICS. Prior to this, it was based on Isaac's re-write, which added some bloat to what should be a quick interrupt service. His version & mine are functionally the same, he re-wrote it in preparation for some future improvements that never materialized.

https://github.com/Whyzor/triumph-kernel-msm7x30/commit/5e7882d8a9fa32feeb451193ed805db5691cd353

BTW I highly recommend switching to the SIO scheduler for the kernel as default, so it doesn't block other threads when there's a lot of I/O as in the NOOP scheduler.
Click to expand...

I just tried your new driver and the screen response is AMAZING! Excellent work.

I pushed everything up now.
 
The remaining issues with the touchscreen is the extreme sensitivities requires steady hands. Seems like it could use a stronger noise filter, but I'm afraid it could take a performance hit even if implemented in C code in the driver.

Also there is the occasional missed touch or swipe. If you turn on the dev setting to see the touch points, they register, just that there must be some problem processing all the input events. Since I noticed this in CM7 and CM9 but not on other phones, I believe it lies somewhere in the kernel-to-android input interface.

Another new option to play with is the bi041p.idc file that supposedly has adjustable calibration values.
 
There should probably be a link to this thread from the ROM one for those who can contribute code fixes or development discussion.

Also any code fixes that's put into repos other than device_motorola_triumph makes it less likely CM9 will be officially supported in the future. (I'm guessing they don't want to hardcode fixes into other parts of the source tree for specific devices. So using overlay settings is recommended.

Finally I think the bug tracker doesn't need its own repo. Just enable "issues" in the android_device_motorola_triumph repo.
 
I did a build last night, my first, to see if my computer could handle it. Woke up this morning to a completed build with no errors as far as I could tell, other than many lines of "please install optipng" or two other options. Installed optipng, but as far as I can tell the build went smoothly. Do I need to build again with optipng installed?

I had a hell of a time copying the rom to my /home, even after setting permissions, but I dragged it to my File System drive, and it let me copy it from there to my desktop. I'm new to Linux/Ubuntu, so I don't know if I've even done everything right. Should I have to jump through all these hoops just to move a file from root? Took me awhile to figure out gksu nautilus to get access to the root folder in the first place.

Any advice would be helpful. I'd like to help out with development if at all possible. I just need to know where on my box any file editing is taking place after a repo sync.
 
zajrik said:
I did a build last night, my first, to see if my computer could handle it. Woke up this morning to a completed build with no errors as far as I could tell, other than many lines of "please install optipng" or two other options. Installed optipng, but as far as I can tell the build went smoothly. Do I need to build again with optipng installed?

I had a hell of a time copying the rom to my /home, even after setting permissions, but I dragged it to my File System drive, and it let me copy it from there to my desktop. I'm new to Linux/Ubuntu, so I don't know if I've even done everything right. Should I have to jump through all these hoops just to move a file from root? Took me awhile to figure out gksu nautilus to get access to the root folder in the first place.

Any advice would be helpful. I'd like to help out with development if at all possible. I just need to know where on my box any file editing is taking place after a repo sync.
Click to expand...

optipng is one of many non-critical errors probably, since CM9 is still in alpha stage too. I use a simple ftp server script on the Ubuntu end, google for 'ftpserver.py', then use FileZilla FTP client on windows to transfer files between the two. As for editing source code, most of what affects the MT are in device/motorola/triumph and the kernel (triumph-msm7x30). The rest of the repos may need some tweaking for our devices (like the RIL & Wifi), but CM's intent is to keep those areas as generic as possible and make device specific fixes in the device repo.
 
Whyzor said:
optipng is one of many non-critical errors probably, since CM9 is still in alpha stage too. I use a simple ftp server script on the Ubuntu end, google for 'ftpserver.py', then use FileZilla FTP client on windows to transfer files between the two. As for editing source code, most of what affects the MT are in device/motorola/triumph and the kernel (triumph-msm7x30). The rest of the repos may need some tweaking for our devices (like the RIL & Wifi), but CM's intent is to keep those areas as generic as possible and make device specific fixes in the device repo.
Click to expand...

Awesome. I imagine I would have been made aware of any critical errors, then.

I'm going to take a look at everything then. See what I can sort out. Thank you for the advice.
 
Whyzor said:
There should probably be a link to this thread from the ROM one for those who can contribute code fixes or development discussion.

Also any code fixes that's put into repos other than device_motorola_triumph makes it less likely CM9 will be officially supported in the future. (I'm guessing they don't want to hardcode fixes into other parts of the source tree for specific devices. So using overlay settings is recommended.

Finally I think the bug tracker doesn't need its own repo. Just enable "issues" in the android_device_motorola_triumph repo.
Click to expand...

Good idea on the link. I added it to the op of the alpha thread.

As for code fixes being put in other repos, unfortunately some things can't be helped. I suppose we can add ifdefs in there and then submit it for inclusion down the road. However, I seriously doubt that we'll ever get official cm support. Heck having "official" status doesn't really mean much since we would need our own developers to really keep it updated.

Also a good idea on enabling "issues" in that repo. I'll do that. But for now, I don't think we need bug reports just yet while we still have major functions not working. People are free to list what they find in the alpha thread and anyone is free to to work on them. But I personally would prefer not to have many little bugs added until we get to a beta stage--i.e. all of the major functions working.
 
Is hardware acceleration being worked on? It's a great ROM, but I get like 5-15 fps at max with a live wallpaper.
It's still my daily :)
If there's any way I can contribute (logcats, etc) just ask.
 
why are you guys so awesome! i want an answer now!!!! :D JK

but yea, is HW accel working fully? or is it just a lil bit working? :confused:


EDIT: also... mantera, yumbrad, whyzor, etc. you guys would all make perfect renaissance men! like a jack-of-all-trades! :P
 
You must log in or register to reply here.
Back
Top Bottom