Root [DEV] Continuing Triumph ICS Development

[Dr. Dank]

so this is pretty close to done?

 

[konspiracy]

so this is pretty close to done?

No we still have alot of the little things to tweak to perfection.

 

[piper_]

I know HAL was built on top of udev.
HAL is now deprecated on *most* modern GNU/Linux systems since last year

How does this affect android since android uses the linux kernel ?

 

[mantera]

I know HAL was built on top of udev.
HAL is now deprecated on *most* modern GNU/Linux systems since last year

How does this affect android since android uses the linux kernel ?

It doesn't. Mainstream linux and android are two separate branches at this time that are moving in parallel. They will probably meet together in the future but probably not any time soon. It would take a lot of dev time to merge them from what I've read. Basically, Google made a lot of decisions when they forked Android that a lot of mainstream linux devs didn't like, things like wakelocks.

 

[sharpe351]

It doesn't. Mainstream linux and android are two separate branches at this time that are moving in parallel. They will probably meet together in the future but probably not any time soon. It would take a lot of dev time to merge them from what I've read. Basically, Google made a lot of decisions when they forked Android that a lot of mainstream linux devs didn't like, things like wakelocks.

alot of purists say that android uses a hacked version of Linux. There was a project on xda a while back trying to make a pure Linux phone, but I think the project was abandoned due to problems with hand written drivers.

 

[konspiracy]

alot of purists say that android uses a hacked version of Linux. There was a project on xda a while back trying to make a pure Linux phone, but I think the project was abandoned due to problems with hand written drivers.

Thats the biggest problem period. Drivers are the one thing that we constantly are working against. If we could have more open source drivers then we could really do some amazing things.

 

[lanceg]

I think when we figure out how to get the 3G to stop dropping after a couple hours then it will be a beta.

Stock did this a lot too, and I recall TickerGuy doing something in CM7 to fix it. That would probably have to be replicated in ICS

 

[mantera]

Stock did this a lot too, and I recall TickerGuy doing something in CM7 to fix it. That would probably have to be replicated in ICS

I have not had any drops since 0.6.4.

 

[progmanos]

Update: I am running into a problem when trying to get the picture size in the Camera app.

02-13 11:01:42.281: I/QualcommCameraHardware(3266): HAL_getCameraInfo: cameraId=0,orientation=90
02-13 11:01:42.281: D/CameraHAL(3266): camera_get_camera_info: id:0 faceing:0 orientation: 90
02-13 11:01:42.285: W/dalvikvm(3234): threadid=11: thread exiting with uncaught exception (group=0x2b4b11f8)
02-13 11:01:42.285: E/AndroidRuntime(3234): FATAL EXCEPTION: Thread-103
02-13 11:01:42.285: E/AndroidRuntime(3234): java.lang.RuntimeException: failed to get value of size.width
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera.updateCameraParametersPreference(Camera.java:1958)
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera.setCameraParameters(Camera.java:2086)
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera.startPreview(Camera.java:1853)
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera.access$3100(Camera.java:87)
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera$5.run(Camera.java:1112)
02-13 11:01:42.285: E/AndroidRuntime(3234): at java.lang.Thread.run(Thread.java:856)
02-13 11:01:42.285: E/AndroidRuntime(3234): Caused by: java.lang.NullPointerException
02-13 11:01:42.285: E/AndroidRuntime(3234): at com.android.camera.Camera.updateCameraParametersPreference(Camera.java:1955)
02-13 11:01:42.285: E/AndroidRuntime(3234): ... 5 more
02-13 11:01:42.305: W/ActivityManager(245): Force finishing activity com.android.camera/.Camera

 

[Whyzor]

Update: I am running into a problem when trying to get the picture size in the Camera app.

Might be getting incompatible values from device/motorola/triumph/files/etc/media_profiles.xml. That file can also be tweaked during runtime & rebooting.

 

[progmanos]

I'll just print out the entire mMap HashMap from frameworks/base/core/java/android/hardware/Camera.java and try to figure out why KEY_PICTURE_SIZE is not being added.

 

[progmanos]

So, mMap only contains one key value pair, namely recording-hint=false, by the time the value for KEY_PICTURE_SIZE is requested.

So I'm curious as to why the other parameters are not being populated in the mMap.

 

[michambers1994]

With a very good stable release, (0.6.5) I will now be testing, and using this version since all of the main things work. If their are any problems I will post them. Thank-You to all of the developers that are contributing to this work of art!

 

[lifeblows10]

I have a question for the devs:

What GPU drivers are we using? The reason I ask is because on Edowar's ICS, graphics ran super smooth, all because he was using the newer drivers.... and last night I thought about it and was curious.


Here are the supposed drivers: [DEV] Adreno 205 EGL(Graphic) Driver Update (30/12/2011) - xda-developers

 

[michambers1994]

.

 

[tusing]

I have a question for the devs:

What GPU drivers are we using? The reason I ask is because on Edowar's ICS, graphics ran super smooth, all because he was using the newer drivers.... and last night I thought about it and was curious.


Here are the supposed drivers: [DEV] Adreno 205 EGL(Graphic) Driver Update (30/12/2011) - xda-developers

Seconded... What GPU drivers are we using?

 

[MotoTriu]

I believe we are using the Adreno 200 GPU drivers

 

[mantera]

We're using the same ones that edowar is using.

 

[DrakonVolk]

Loving the 0.6.5 build... Great work, guys! You are the MEN!! :-]

 

[bobloadmire]

I believe we are using the Adreno 200 GPU drivers

classic

 

[mantera]

At stock speeds using the updated Quadrant standard v2, I'm getting about 2012 as my score. Which according to their chart is only slightly behind the samsung galaxy tab which looks to be around 2300.

Edit: Also, in Nenamark2, I'm getting about 23.8 fps.

 

[mantera]

Removed out/target/product/triumph and still got that error. It may have something to do with the new qcom_gps repo being tracked is out of sync with the rest of CM9's repos.

@whyzor - did you figure out the cm9 repo sync issues you were having? Just curious.

 

[Whyzor]

@whyzor - did you figure out the cm9 repo sync issues you were having? Just curious.

Yes, thank you. there was a manifest_local.xml in my .repo dir with an odd device_motorola_triumph entry for some reason. I removed it and it's working fine. Apparently 1 bad (local) entry can block the rest of the repo sync from completing successfully, which is what caused my build break originally (or I was just unlucky during both of my syncs and picked up incomplete changes from CM9.)

 

[Xerpocalypse]

I'm no dev, but I would like to bring up that video playback/streaming (oddly only in standard or low-quality) in the latest build is decidedly choppy. Again, I'm not nagging for it to be fixed, however, I had not seen it posted elsewhere so I thougnht I might as well present it here.

I am truly sorry if this is bothersome in some way or another.

 

[SuperMandroid3]

I'm no dev, but I would like to bring up that video playback/streaming (oddly only in standard or low-quality) in the latest build is decidedly choppy. Again, I'm not nagging for it to be fixed, however, I had not seen it posted elsewhere so I thougnht I might as well present it here.

I am truly sorry if this is bothersome in some way or another.

Yea they know...Netflix too. And all my porn sites that's not HD...lol.